On Monday 16 Dec 2013 04:04:34 eroen wrote:
> On Sun, 15 Dec 2013 17:37:53 +0100
>
> Benjamin Block wrote:
> > Most of the times, when some binary packages on my systems do cause
> > something like this, then I just unemerge the package that keeps
> > recompiling and emerge it again afterwards. T
On Sun, 15 Dec 2013 17:37:53 +0100
Benjamin Block wrote:
> Most of the times, when some binary packages on my systems do cause
> something like this, then I just unemerge the package that keeps
> recompiling and emerge it again afterwards. This will cause the
> portage to drop the library-referen
On 15/12/13 11:51, Mick wrote:
Not sure why, but for some reason running emerge @preserved-rebuild does not
seem to fix some preserved libs links:
!!! existing preserved libs:
package: x11-libs/pango-1.34.1
* - /usr/lib/libpangox-1.0.so.0
* - /usr/lib/libpangox-1.0.so.0.3000.1
This is a
On Mon, 28 Sep 2009 12:53:11 + (UTC), James wrote:
> for i in $(find /lib* /usr/lib*) ; do qfile -o $i ; done
>
> It worked like a charm, except there is a huge list?
> It overfilled my scroll back, so below is a tiny snippet.
> I'm weary of removing so many files?
> rm these files?
>
> rev
Neil Bothwick digimed.co.uk> writes:
> > > No apparent ill effects. You now have the old, orphaned version of the
> > > library on your system and unknown to portage. Portage deletes these
> > > after emerge @preserved-rebuild has successfully re-emerged packages
> > > depending on it.
> > O
Am Sun, 27 Sep 2009 18:20:52 +0200
schrieb Francesco Talamona :
> On Sunday 27 September 2009, James wrote:
> > Neil Bothwick digimed.co.uk> writes:
> > >>> Portage deletes these
> > >>>
> > > > > after emerge @preserved-rebuild has successfully re-emerged
> > > > > packages depending on it.
> >
On Sunday 27 September 2009, James wrote:
> Neil Bothwick digimed.co.uk> writes:
> >>> Portage deletes these
> >>>
> > > > after emerge @preserved-rebuild has successfully re-emerged
> > > > packages depending on it.
> > >
> > > OK, so now I just have to root it out manually.?
> >
> > qfile -
Neil Bothwick digimed.co.uk> writes:
>>> Portage deletes these
> > > after emerge @preserved-rebuild has successfully re-emerged packages
> > > depending on it.
> > OK, so now I just have to root it out manually.?
> qfile -o $(find /lib* /usr/lib*)
qfile -o $(find /lib* /usr/lib*)
b
On Sat, 26 Sep 2009 01:23:31 + (UTC), James wrote:
> > No apparent ill effects. You now have the old, orphaned version of the
> > library on your system and unknown to portage. Portage deletes these
> > after emerge @preserved-rebuild has successfully re-emerged packages
> > depending on it.
Neil Bothwick digimed.co.uk> writes:
> No apparent ill effects. You now have the old, orphaned version of the
> library on your system and unknown to portage. Portage deletes these
> after emerge @preserved-rebuild has successfully re-emerged packages
> depending on it.
OK, so now I just have
Robin Atwood attglobal.net> writes:
> I had exactly the same problem. I solved it by deleting
> /var/lib/portage/preserved_libs_registry with no ill effects (since revdep-
> rebuild was clean).
I did this as well as the previous suggestions.
I also rebuilt xulrunner, in an attempt to emerge
op
Jonathan Callen (ABCD gentoo.org> writes:
> > Rather than rebuilding kalgebra, unmerge it completely then emerge it
> > again. It might be a problem with the emerge process for that package
> > not using the latest version for some reason, so it is rebuilding
> > against the old libs (which there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Hartman wrote:
> On Thu, Sep 24, 2009 at 1:25 PM, James wrote:
>> Hello,
>>
>>
>> I keep getting this mesaage on one particulary system:
>>
>> existing preserved libs:
>> package: sys-libs/readline-6.0_p3
>> * - /lib64/libreadline.so
>> * -
13 matches
Mail list logo
