Your message dated Fri, 08 Apr 2016 08:00:45 +
with message-id
and subject line Bug#820178: fixed in re2 20160401+dfsg-2
has caused the Debian Bug report #820178,
regarding new upload broke ruby-re2 (in turn broke gitlab)
to be marked as done.
This means that you claim that the problem has
Control: reassign -1 libre2-1v5
Control: found -1 20160401+dfsg-1
Control: notfound -1 20160201+dfsg-1
Control: block -1 by 820349
Control: retitle -1 new upload broke ruby-re2 (in turn broke gitlab)
libre2-1v5 upload should have ensured reverse dependencies are not
broken during new upload. And a
Downgrading libre2-1v5 fixes this issue. Some ruby libraries may need a rebuild.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Hi,
let me also give you the list of the packages I have installed:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Hi,
after having removed the package libruby2.1, the original error is gone.
Instead I now get the error that can be seen below just after the database was
populated. Nevertheless, this already means that some package does not cope
well with libruby2.1 and libruby2.3 being installed at the same ti
Package: gitlab
Version: 8.5.8+dfsg-4
Severity: grave
Justification: renders package unusable
Hi,
on a Debian unstable system with all packages upgraded, following is
happening when I try installing the gitlab package:
Using sass-rails 5.0.3
Using redis-rails 4.0.0
Using turbolinks 2.5.3
Using d
6 matches
Mail list logo
