Am Montag, 20. August 2012, 01:00:34 schrieb Reinhard Kotucha: > On 2012-08-19 at 01:02:24 +0200, Volker Armin Hemmann wrote: > > Am Sonntag, 19. August 2012, 00:37:36 schrieb Reinhard Kotucha: > > > Hi, > > > I'm using Gentoo for a couple of years and am quite amazed how good it > > > works. So thanks to all involved in its develpoment. > > > > > > However, after today's update, when I run revdep-rebuild, I get the > > > message > > > > > > * Checking dynamic linking consistency > > > * broken /usr/lib64/libogrove.la (requires -lstdc++) > > > * broken /usr/lib64/libospgrove.la (requires -lstdc++) > > > * broken /usr/lib64/libostyle.la (requires -lstdc++) > > > > so, find out which package these three belong to - and remove them. > > Ok, will do. > > > > emerge --update --pretend > > > > why pretend? > > Because whenever I see that there is an Xorg update, I nowadays make a > full backup before I do the actual update. >
that is what --ask is made for ;) > > > On the other hand it happpened several times that *after* an update > > > I've been told that my system is completely broken and will not > > > re-boot unless I compile a new kernel. > > > > really? never saw that. Only with xorg-drivers after a xorg-server > > update. > > Presumably because you already were using a newer kernel. It was the > kernel version number what mattered, not the configuration. I have been sticking around with 3.0 for a long time. > > > > It would be nice if I can be warned *before* I run emerge without > > > the --pretend option. Then I could postpone the update to the > > > next weekend, when I have more time. > > > > so you want portage to read every single ebuild, making the > > operation A LOT longer? I am sorry but I am not willing to waste so > > much time. > > Maybe a news item would be sufficient. > > > > My propsal is to add a warning similar to that I get when portage > > > updates are available, so that users know in advance that a > > > particular update will break the system. > > > > please enlighten me which update breaks a system. Can't remember > > one. Hm, back with libss&co maybe? > > Last time it happened after an udev update. After the update I've > been told that my kernel was too old. If I have to build a new kernel > the next day, I can only hope that there is no power failure > meanwhile and would rather postpone the update. okay, there is a reason I masked udev updates a long time ago ;) -- #163933
