Source: ticgit
Version: 1.0.2.17-1
Severity: serious
Tags: jessie sid
User: [email protected]
Usertags: qa-ftbfs-20131128 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_auto_install
> /usr/lib/ruby/vendor_ruby/gem2deb.rb:17: warning: setting 
> Encoding.default_external
>   Entering dh_ruby --install
> install -d /«PKGBUILDDIR»/debian/ticgit/usr/bin
> install -D -m755 /«PKGBUILDDIR»/bin/ticgitweb 
> /«PKGBUILDDIR»/debian/ticgit/usr/bin/ticgitweb
> install -D -m755 /«PKGBUILDDIR»/bin/ti /«PKGBUILDDIR»/debian/ticgit/usr/bin/ti
> install -d /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/cli.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/cli.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/version.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/version.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/ticket.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/ticket.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/comment.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/comment.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/tag.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/tag.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/sync.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/sync.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/state.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/state.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/show.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/show.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/recent.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/recent.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/points.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/points.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/new.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/new.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/milestone.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/milestone.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/list.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/list.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/init.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/init.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/help.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/help.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/comment.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/comment.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/checkout.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/checkout.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/attach.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/attach.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/command/assign.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/command/assign.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/base.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/base.rb
> install -D -m644 /«PKGBUILDDIR»/lib/ticgit-ng/attachment.rb 
> /«PKGBUILDDIR»/debian/ticgit/usr/lib/ruby/vendor_ruby/ticgit-ng/attachment.rb
> /usr/lib/ruby/vendor_ruby/gem2deb.rb:52:in `system': can't convert nil into 
> String (TypeError)
>       from /usr/lib/ruby/vendor_ruby/gem2deb.rb:52:in `run'
>       from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:138:in 
> `run_tests_for_version'
>       from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:129:in `block in 
> run_tests'
>       from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:128:in `each'
>       from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:128:in `run_tests'
>       from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:72:in `install'
>       from /usr/bin/dh_ruby:69:in `block (2 levels) in <main>'
>       from /usr/lib/ruby/1.9.1/optparse.rb:1360:in `call'
>       from /usr/lib/ruby/1.9.1/optparse.rb:1360:in `block in parse_in_order'
>       from /usr/lib/ruby/1.9.1/optparse.rb:1347:in `catch'
>       from /usr/lib/ruby/1.9.1/optparse.rb:1347:in `parse_in_order'
>       from /usr/lib/ruby/1.9.1/optparse.rb:1341:in `order!'
>       from /usr/lib/ruby/1.9.1/optparse.rb:1432:in `permute!'
>       from /usr/lib/ruby/1.9.1/optparse.rb:1453:in `parse!'
>       from /usr/bin/dh_ruby:73:in `<main>'
> Rewriting shebang line of /«PKGBUILDDIR»/debian/ticgit/usr/bin/ti
> Rewriting shebang line of /«PKGBUILDDIR»/debian/ticgit/usr/bin/ticgitweb
>  -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb
> dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/tmp returned exit 
> code 1
> make[1]: *** [override_dh_auto_install] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/11/28/ticgit_1.0.2.17-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to