On Fri, Dec 27, 2019 at 10:52:27PM +0530, Pirate Praveen wrote: > > > On 2019, ഡിസംബർ 27 5:47:23 PM IST, Daniel Leidert <dleidert@debian.org> wrote: > >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. > > May be something got fixed in gem2deb? ruby-i18n 1.5.3-1 was built with gem2deb 0.40 and somehow wrongly created i18n-0.7.0.gemspec i18n 1.5.3-2 was built with gem2deb 0.45 and correctly generated i18n-1.5.3.gemspec > > Between these versions --gem-install became default and that might have fixed the earlier bug in gemspec file generation. note that this new default only affects what gets procuded in debian/rules by dh-make-ruby. it only affects existing packages if the person updating them decides to update the packaging.
Attachment:
signature.asc
Description: PGP signature