Antonio Terceiro wrote on 05/29/2015 12:49: > Control: reassign -1 dpkg > > On Mon, May 25, 2015 at 02:07:37PM +0200, Jörg-Volker Peetz wrote: >> Antonio Terceiro wrote on 05/25/2015 13:48: >> <snip> >> >>> I'm sorry but I cannot see what is the problem; did you forget to >>> include the actual error messages? >>> >> Hi Antonio, >> >> it's further down: >> >> Setting up ruby-activesupport (2:4.1.10-1) ... >> dpkg: cycle found while processing triggers: >> chain of packages whose triggers are or may be responsible: >> redmine -> redmine >> packages' pending triggers which are or may be unresolvable: >> libc-bin: ldconfig >> redmine: /usr/lib/ruby/vendor_ruby >> dpkg: error processing package libc-bin (--configure): >> triggers looping, abandoned >> dpkg: cycle found while processing triggers: >> chain of packages whose triggers are or may be responsible: >> redmine -> redmine -> redmine >> packages' pending triggers which are or may be unresolvable: >> redmine: /usr/lib/ruby/vendor_ruby >> dpkg: error processing package redmine (--configure): >> triggers looping, abandoned >> >> ... >> >> Errors were encountered while processing: >> libc-bin >> redmine >> E: Sub-process /usr/bin/dpkg returned an error code (1) >> Failed to perform requested operation on package. Trying to recover: >> Setting up libc-bin (2.19-18) ... > > That looks like a problem in dpkg. Did you try upgrading dpkg before > upgrading the rest of the system? Or trying again after the above > happened? > On May 25 I encountered the problem when upgrading ruby-rails. I used and am still using dpkg version 1.18.0. I upgraded to this version from version 1.17.25 on May 19. -- Regards, Jörg.
-- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
