Re: autopkgtest Rubygems dependency resolution: "No such file or directory - dpkg-parsechangelog"

2019-02-03 Thread Georg Faerber
Hi all, On 19-02-03 14:10:40, Georg Faerber wrote: > Any ideas? This was due to dpkg-parsechangelog not being available in the container. It's shipped via dpkg-dev; gem2deb depends on devscripts, which in turn depends on dpkg-dev, so I'm unsure why was / is that. IIRC, I've just encountered

Re: autopkgtest Rubygems dependency resolution: "No such file or directory - dpkg-parsechangelog"

2019-02-03 Thread Georg Faerber
Hi all, On 18-12-16 18:32:50, Georg Faerber wrote: > Checking Rubygems dependency resolution on ruby2.5 > > /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:161:in ``': No such file or > directory - dpkg-parsechangelog (Errno::ENOENT) > from

Re: autopkgtest Rubygems dependency resolution: "No such file or directory - dpkg-parsechangelog"

2018-12-19 Thread Pirate Praveen
On 12/20/18 2:33 AM, Georg Faerber wrote: > Hi, > > On 18-12-19 10:12:06, Pirate Praveen wrote: >> If you can push your changes, I can upload it. > > This would be great, I already pushed all the changes to the following > branches: > > ruby-gpgme: debian/2.0.18-1 > ruby-sequel: debian/5.15.0-1

Re: autopkgtest Rubygems dependency resolution: "No such file or directory - dpkg-parsechangelog"

2018-12-19 Thread Georg Faerber
Hi, On 18-12-19 10:12:06, Pirate Praveen wrote: > If you can push your changes, I can upload it. This would be great, I already pushed all the changes to the following branches: ruby-gpgme: debian/2.0.18-1 ruby-sequel: debian/5.15.0-1 In case any changes are necessary, and if you're willing

Re: autopkgtest Rubygems dependency resolution: "No such file or directory - dpkg-parsechangelog"

2018-12-18 Thread Pirate Praveen
On 2018, ഡിസംബർ 19 5:54:00 AM IST, Georg Faerber wrote: >Hi, > >On 18-12-18 17:05:18, Pirate Praveen wrote: >> This is probably a transient failure. I'm not able to reproduce it >> today. > >Did you check one of the two mentioned packages? I'm still running into >this error. Yes, I checked

Re: autopkgtest Rubygems dependency resolution: "No such file or directory - dpkg-parsechangelog"

2018-12-18 Thread Georg Faerber
Hi, On 18-12-18 17:05:18, Pirate Praveen wrote: > This is probably a transient failure. I'm not able to reproduce it > today. Did you check one of the two mentioned packages? I'm still running into this error. Cheers, Georg signature.asc Description: Digital signature

Re: autopkgtest Rubygems dependency resolution: "No such file or directory - dpkg-parsechangelog"

2018-12-18 Thread Pirate Praveen
On 12/17/18 12:02 AM, Georg Faerber wrote: > Hi all, > > Today I've worked on two packages, ruby-gpgme and ruby-sequel, and ran into > the > following error for both of them during autopkgtest: > > Checking Rubygems dependency resolution on ruby2.5 │ > >

autopkgtest Rubygems dependency resolution: "No such file or directory - dpkg-parsechangelog"

2018-12-16 Thread Georg Faerber
Hi all, Today I've worked on two packages, ruby-gpgme and ruby-sequel, and ran into the following error for both of them during autopkgtest: Checking Rubygems dependency resolution on ruby2.5 │ /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:161:in ``': No such file or