Your message dated Mon, 6 Nov 2017 15:29:02 +0100
with message-id <20171106142902.nbqxssyt57ktfzh4@esfahan>
and subject line Re: Bug#880963: FTBFS: [kwalify.gemspec] isn't a 
Gem::Specification (NilClass instead).
has caused the Debian Bug report #880963,
regarding FTBFS: [kwalify.gemspec] isn't a Gem::Specification (NilClass 
instead).
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
880963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kwalify
Version: 0.7.2-4
Severity: serious
Justification: fails to build from source

Coin,

When trying to rebuild kwalify, I got the following output:


dpkg-buildpackage: info: source package kwalify
dpkg-buildpackage: info: source version 0.7.2-3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Marc Dequènes (Duck) 
<d...@duckcorp.org>
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build kwalify
dpkg-source: info: using options from kwalify/debian/source/local-options: 
--unapply-patches
 fakeroot debian/rules clean
dh clean --buildsystem=ruby --with ruby
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/home/boutil/debian/pkg-ruby-extras/kwalify'
dh_auto_clean
dh_auto_clean: Compatibility levels before 9 are deprecated (level 7 in use)
        dh_ruby --clean
   dh_ruby --clean
[kwalify.gemspec] isn't a Gem::Specification (NilClass instead).
[kwalify.gemspec.gem2deb] isn't a Gem::Specification (NilClass instead).
/usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:124:in `load_gemspec': E: cannot 
load gemspec kwalify.gemspec (RuntimeError)
        from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:34:in `block in 
initialize'
        from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `chdir'
        from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `initialize'
        from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:24:in `new'
        from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:24:in `initialize'
        from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:202:in `new'
        from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:202:in `block in 
installers'
        from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:201:in `map'
        from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:201:in `installers'
        from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:43:in `clean'
        from /usr/bin/dh_ruby:96:in `<main>'
dh_auto_clean: dh_ruby --clean returned exit code 1
debian/rules:31: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 1
make[1]: Leaving directory '/home/boutil/debian/pkg-ruby-extras/kwalify'
debian/rules:18: recipe for target 'clean' failed
make: *** [clean] Error 2

It seems that new versions of gem2deb are unable to parse the gemspec
metadata.

Cheers,

Cédric

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr:en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Dear Adrian,

Thank you for your message. Trying again made me realise it was a
problem on my side, and not in the package. I was trying to build -3
instead which was suffering from this problem (#828165) but has been
fixed for a long time.

I am thus closing this bug. Sorry for the noise!

Cédric

--- End Message ---

Reply via email to