Am Freitag, den 27.12.2019, 13:07 +0530 schrieb Pirate Praveen: > On 2019, ഡിസംബർ 27 2:45:14 AM IST, Daniel Leidert <dleidert@debian.org> > wrote: > > Hi there, > > > > I recently saw one of my packages failing debci/autopkgtest with this > > error: > > > > > /usr/lib/ruby/2.5.0/rubygems/specification.rb:2327:in > > `raise_if_conflicts': Unable to activate jekyll-3.8.3, because > > i18n-1.5.3 conflicts with i18n (~> 0.7) (Gem::ConflictError) > > > > Looking deeper into this the recent upload of ruby-i18n causes the > > issue and it > > seems to affect more packages: https://bugs.debian.org/927339 > > This upstream version of ruby-i18n was in archive from 2019-02-03. Recent > upload just triggered the autopkgtest. I really wonder because the autopkgtests of the packages in question did not raise an error before (and this is 4 weeks ago): https://salsa.debian.org/ruby-team/ruby-jekyll-mentions/-/jobs/430666 (passed) https://salsa.debian.org/ruby-team/ruby-jekyll-mentions/-/jobs/475859 (errored) The changelog entry does not explain it. > Jekyll should be fixed to work with the new version. ruby-stringex might need a fix too. Regards, Daniel
Attachment:
signature.asc
Description: This is a digitally signed message part