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. n > > emerge --update --pretend why pretend? > > I'm warned in advance if a portage update is available. It seems that > emerge is able to warn about critical updates. only about portage updates. > > 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. > 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. > > 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? > > Of course, this mailing list is not the proper place for such > suggestions. Can anybody tell me whom I should ask? bugzilla. Feature request. -- #163933
