Ruby (grave) [fixed]

Unread post by **ivanovnegro** » Mon Apr 07, 2014 5:36 am

The explanation would be from the BTS:

badly handles transition away from alternatives, breaks dependant packages.

Does not sound sexy, so wait with the d-u or just hold *ruby*.

Reference

Unread post by **ivanovnegro** » Sun Apr 13, 2014 1:58 pm

Done.

Unread post by **machinebacon** » Mon Apr 14, 2014 10:35 am

Thanks DD, got hit by this in the middle of a huge upgrade, hat to remove the whole ruby before skipping the versions, so maybe it's a good idea for those who come from a year-old install to first remove ruby (and also python and apt-listbugs), perform upg, and then add the packages again. I mention this only because else the user gets into an endless cycle in which he has to fuck around with dpkg's database.

Unread post by **GekkoP** » Mon Apr 14, 2014 2:28 pm

Thanks for this and for the workaround. It's been a while since I have dist-upgraded Sidbang, I'll pay attention.

LinuxBBQ

Ruby (grave) [fixed]

Ruby (grave) [fixed]

Re: Ruby (grave) [fixed]

Re: Ruby (grave) [fixed]

Re: Ruby (grave) [fixed]