Re: [gentoo-user] Re: @preserved-rebuild gone in a loop

2013-12-16 Thread Mick
On Monday 16 Dec 2013 04:04:34 eroen wrote:
 On Sun, 15 Dec 2013 17:37:53 +0100
 
 Benjamin Block b...@zlug.org 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-references in question and add new ones.
  
  So, this should do the trick:
  emerge -C app-antivirus/avast4workstation
  emerge -1 app-antivirus/avast4workstation
 
 This will make the message from portage and the old library version go
 away, yes. It will also cause the program that used the library
 (/opt/avast4workstation/bin/avastgui in OP's case) crash when you try
 to run it, due to the old library version not being installed.
 
 The correct solution to this is to add the specific (old) version of the
 library to the dependencies (in the ebuild) of the (binary) package that
 uses it. This will prevent an upgrade that uninstalls the old library
 version. Sometimes the maintainer of the library will add a slotted
 version of it, so that non-binary users of it do not have to use the
 outdated version.
 
 If the binary package is not an ebuild, you can manually add the newer
 library version to package.mask, or make sure that the slot for the
 older version is installed if the library is slotted.
 
 Better yet (in all cases), get a more recent version of the binary
 package that is built against the newer version of the library.
 Complain to the vendor if none is available :-)
 
 The preserve-libs feature in portage is intended to let things keep on
 working short-term for source-distributed packages. In that case, the
 currently installed program is linked against the old library version,
 and when the program is rebuilt (with @preserved-rebuild) it will be
 linked against the newer version.

Thank you for a detailed explanation, which makes sense to me.  You are right, 
uninstalling, running @preserved-rebuild and reinstalling this package breaks 
the avastgui because of the missing libpangox-1.0.so.0 library.  Thankfully, 
the command line function is unaffected.

I wouldn't want to keep old libraries around unnecessarily, so I may have to 
chase the dev for this package and see if he's still interested to look after 
it.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Re: @preserved-rebuild

2009-09-28 Thread Neil Bothwick
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?
 
 revdep-rebuild comes back clean. Check with another tool?

revdep-rebuild checks for binaries built against non-existent
libraries, you are looking for surlpus libraries,so it won't help. You're
already using the correct tool, qfile.

 I already synced and updated, do again?
 
 
 snip
 /usr/lib64/python2.6/site-packages/_xmlplus/dom/html/HTMLElement.pyo 
 snip
 /usr/lib64/libblas.a
 /usr/lib64/libruby.so

Ignore the .pyo and.pyc files, they are created by ebuilds after
installation, so don't show up in the packages' contents. The .so files
certainly look guilty, but move them somewhere rather than deleting,
then run revdep-rebuild.


-- 
Neil Bothwick

Error reading FAT record: Try the SKINNY one? (Y/N)


signature.asc
Description: PGP signature


Re: [gentoo-user] Re: @preserved-rebuild

2009-09-27 Thread Marc Joliet
Am Sun, 27 Sep 2009 18:20:52 +0200
schrieb Francesco Talamona francesco.talam...@know.eu:

 On Sunday 27 September 2009, James wrote:
  Neil Bothwick neil at 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*)
 
  bash: /usr/bin/qfile: Argument list too long
 
 
  Now what? I look at the man page for qfile and tried
  all the -m option, but still get the same error?
 
 
  ideas?
 
 
  James
 
 for i in $(find /lib* /usr/lib*) ; do qfile -o $i ; done
 
 Ciao
   Francesco
 

It would be much faster to use

find /lib* /usr/lib* | qfile -o -f -

instead (see man qfile).

HTH
-- 
Marc Joliet
--
Lt. Frank Drebin: It's true what they say: cops and women don't mix. Like
eating a spoonful of Drāno; sure, it'll clean you out, but it'll leave you
hollow inside.


signature.asc
Description: PGP signature


Re: [gentoo-user] Re: @preserved-rebuild

2009-09-26 Thread Neil Bothwick
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.  
 
 OK, so now I just have to root it out manually.?

Yes, qfile will help here

qfile -o $(find /lib* /usr/lib*)


-- 
Neil Bothwick

Windows Error #01: No error... ...yet.


signature.asc
Description: PGP signature