Your message dated Thu, 2 Jan 2014 21:31:37 +0100
with message-id
<cajg5+z2x5+4vftdjdcvpcvyd1etn+7exu_u5juvj2e-7aw-...@mail.gmail.com>
and subject line ruby-carrierwave: FTBFS with ruby2.0: Build killed with signal
TERM after 60 minutes of inactivity
has caused the Debian Bug report #720248,
regarding ruby-carrierwave: FTBFS with ruby2.0: Build killed with signal TERM
after 60 minutes of inactivity
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 [email protected]
immediately.)
--
720248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720248
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby-carrierwave
Version: 0.8.0-2
Severity: important
Tags: jessie sid
User: [email protected]
Usertags: ruby2-ftbfs-20130818 ruby2-ftbfs
Justification: FTBFS on amd64 with ruby2.0
Hi,
During a rebuild of all packages that build depends on gem2deb
using the new ruby2.0 interpreter, your package failed to build
on amd64.
Relevant part (hopefully):
> ERROR: Test "ruby2.0" failed. Exiting.
> dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/ruby-carrierwave
> returned exit code 1
> make[1]: *** [override_dh_auto_install] Error 1
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> make: *** [binary] Error 2
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status
> 2
> 130817 11:00:04 [Note] /usr/sbin/mysqld: Normal shutdown
>
> libfakeroot, when sending message: Invalid argument
> 130817 11:00:04 [Note] Event Scheduler: Purging the queue. 0 events
> 130817 11:00:04 InnoDB: Starting shutdown...
> 130817 11:00:05 InnoDB: Shutdown completed; log sequence number 1693135
> libfakeroot, when sending message: Invalid argument
> 130817 11:00:05 [Note] /usr/sbin/mysqld: Shutdown complete
>
> Build killed with signal TERM after 60 minutes of inactivity
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/ruby2.0/ruby-carrierwave_0.8.0-2_unstable_ruby2.log
This build is part of an effort to add gem2deb support for ruby2.0.
Information about is available at https://wiki.debian.org/Teams/Ruby/Jessie.
About the rebuild: The rebuild was done on EC2 VM instances from Amazon Web
Services,
using a clean, minimal and up-to-date chroot, plus gem2deb and ruby2.0 packages
from
the repository at http://people.debian.org/~terceiro/packages/. The gem2deb
version
in that repository does not pull ruby1.8 as a dependency anymore, and builds
packages
against ruby1.9.1 and ruby2.0. Every failed build was retried once to eliminate
random
failures.
The version of gem2deb used for this rebuild, as well as ruby2.0,
will be uploaded to unstable soon.
--- End Message ---
--- Begin Message ---
Now builds OK, closing it.
--- End Message ---
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
