Package: bundler
Version: 1.5.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After updating/upgrading a machine running Debian Testing, gitlab
doesn't start
any more:
$ sudo service gitlab start
Starting GitLab SidekiqThe Sidekiq job dispatcher is already running
with pid 26122, not restarting
/usr/local/bin/bundle:23:in `load': cannot load such file --
/usr/share/rubygems-integration/1.9.1/gems/bundler-1.5.0/bin/bundle
(LoadError)
from /usr/local/bin/bundle:23:in `<main>'
..............................Waited 30s for the processes to write
their pids, something probably went wrong.
On December 2nd, with the then current software packages from Debian Testing
everything still worked as expected.
To reproduce it suffices to call bundle:
$ bundle
/usr/local/bin/bundle:23:in `load': cannot load such file --
/usr/share/rubygems-integration/1.9.1/gems/bundler-1.5.0/bin/bundle
(LoadError)
from /usr/local/bin/bundle:23:in `<main>'
Best regards,
Chris
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bundler depends on:
ii ruby 1:1.9.3
ii ruby-net-http-persistent 2.9-1
ii ruby-thor 0.18.1-1
ii ruby1.9.1 [ruby-interpreter] 1.9.3.484-1
Versions of packages bundler recommends:
ii build-essential 11.6
ii less 458-2
ii ruby-dev 1:1.9.3
ii rubygems-integration 1.2
ii sudo 1.8.8-2
bundler suggests no packages.
-- no debconf information
If you want to provide additional information, please wait to receive
the bug
tracking number via email; you may then send any extra information to
n...@bugs.debian.org (e.g. 999...@bugs.debian.org), where n is the bug number.
Normally you will receive an acknowledgement via email including the bug
report
number within an hour; if you haven't received a confirmation, then the bug
reporting process failed at some point (reportbug or MTA failure, BTS
maintenance, etc.).
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
