public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] @preserved-rebuild gone in a loop
@ 2013-12-15  9:51 Mick
  2013-12-15 12:31 ` [gentoo-user] " Nikos Chantziaras
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: Mick @ 2013-12-15  9:51 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: Text/Plain, Size: 6133 bytes --]

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 all caused by some hack I have in my local portage for app-
antivirus/avast4workstation-1.3.0-r2.  No matter how many times I run 
@preserved-rebuild the libs in question keep coming up:

======================================================
# emerge @preserved-rebuild
Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) app-antivirus/avast4workstation-1.3.0-r2 from x-portage
 * avast4workstation-1.3.0.tar.gz RMD160 SHA1 SHA256 size ;-) ...          [ 
ok ]
>>> Unpacking source...
>>> Unpacking avast4workstation-1.3.0.tar.gz to /var/tmp/portage/app-
antivirus/avast4workstation-1.3.0-r2/work
>>> Source unpacked in /var/tmp/portage/app-antivirus/avast4workstation-1.3.0-
r2/work
>>> Compiling source in /var/tmp/portage/app-
antivirus/avast4workstation-1.3.0-r2/work/avast4workstation-1.3.0 ...
>>> Source compiled.
>>> Test phase [not enabled]: app-antivirus/avast4workstation-1.3.0-r2

>>> Install avast4workstation-1.3.0-r2 into /var/tmp/portage/app-
antivirus/avast4workstation-1.3.0-r2/image/ category app-antivirus
>>> Completed installing avast4workstation-1.3.0-r2 into /var/tmp/portage/app-
antivirus/avast4workstation-1.3.0-r2/image/

 * QA Notice: This package installs one or more .desktop files that do not
 * pass validation.
 * 
 *      /usr/share/applications/avast.desktop: error: (will be fatal in the 
future): value "avastgui.png" for key "Icon" in group "Desktop Entry" is an 
icon name with an extension, but there should be no extension as described in 
the Icon Theme Specification if the value is not an absolute path
 *      /usr/share/applications/avast.desktop: warning: value 
"Application;Security;System;" for key "Categories" in group "Desktop Entry" 
contains a deprecated value "Application"
 * 
strip: i686-pc-linux-gnu-strip --strip-unneeded -R .comment -R 
.GCC.command.line -R .note.gnu.gold-version
   opt/avast4workstation/lib/esmtp-plugins/sasl-cram-md5.so
   opt/avast4workstation/lib/esmtp-plugins/sasl-login.so
   opt/avast4workstation/lib/esmtp-plugins/sasl-plain.so
ecompressdir: bzip2 -9 /opt/avast4workstation/share/man

>>> Installing (1 of 1) app-antivirus/avast4workstation-1.3.0-r2
 * QA Notice: Symbolic link 
/opt/avast4workstation/share/doc/avast4workstation-1.3.0/helpfiles points to 
/opt/avast4workstation/lib/avast4workstation/share/avast/help which does not 
exist.
 * After the update on 3/29/2010, AVAST isn't able to initialise.
 * See following link for more details and solution:
 * http://forum.avast.com/index.php?topic=57812.0

 * Messages for package app-antivirus/avast4workstation-1.3.0-r2:

 * After the update on 3/29/2010, AVAST isn't able to initialise.
 * See following link for more details and solution:
 * http://forum.avast.com/index.php?topic=57812.0
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

 * GNU info directory index is up-to-date.

!!! 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
 *      used by /opt/avast4workstation/bin/avastgui (app-
antivirus/avast4workstation-1.3.0-r2)
Use emerge @preserved-rebuild to rebuild packages using these libraries
======================================================


This is all the libpango on this box:
======================================================
# ls -la /usr/lib/libpango*
lrwxrwxrwx 1 root root     24 Dec 14 12:54 /usr/lib/libpango-1.0.so -> 
libpango-1.0.so.0.3400.1
lrwxrwxrwx 1 root root     24 Dec 14 12:54 /usr/lib/libpango-1.0.so.0 -> 
libpango-1.0.so.0.3400.1
-rwxr-xr-x 1 root root 300988 Dec 14 12:54 /usr/lib/libpango-1.0.so.0.3400.1
lrwxrwxrwx 1 root root     29 Dec 14 12:54 /usr/lib/libpangocairo-1.0.so -> 
libpangocairo-1.0.so.0.3400.1
lrwxrwxrwx 1 root root     29 Dec 14 12:54 /usr/lib/libpangocairo-1.0.so.0 -> 
libpangocairo-1.0.so.0.3400.1
-rwxr-xr-x 1 root root  46948 Dec 14 12:54 
/usr/lib/libpangocairo-1.0.so.0.3400.1
lrwxrwxrwx 1 root root     27 Dec 14 12:54 /usr/lib/libpangoft2-1.0.so -> 
libpangoft2-1.0.so.0.3400.1
lrwxrwxrwx 1 root root     27 Dec 14 12:54 /usr/lib/libpangoft2-1.0.so.0 -> 
libpangoft2-1.0.so.0.3400.1
-rwxr-xr-x 1 root root  79944 Dec 14 12:54 
/usr/lib/libpangoft2-1.0.so.0.3400.1
lrwxrwxrwx 1 root root     24 Dec 14 14:54 /usr/lib/libpangomm-1.4.so -> 
libpangomm-1.4.so.1.0.30
lrwxrwxrwx 1 root root     24 Dec 14 14:54 /usr/lib/libpangomm-1.4.so.1 -> 
libpangomm-1.4.so.1.0.30
-rwxr-xr-x 1 root root 179364 Dec 14 14:54 /usr/lib/libpangomm-1.4.so.1.0.30
lrwxrwxrwx 1 root root     25 Feb 28  2013 /usr/lib/libpangox-1.0.so.0 -> 
libpangox-1.0.so.0.3000.1
-rwxr-xr-x 1 root root  51104 Feb 28  2013 /usr/lib/libpangox-1.0.so.0.3000.1
lrwxrwxrwx 1 root root     27 Dec 14 12:54 /usr/lib/libpangoxft-1.0.so -> 
libpangoxft-1.0.so.0.3400.1
lrwxrwxrwx 1 root root     27 Dec 14 12:54 /usr/lib/libpangoxft-1.0.so.0 -> 
libpangoxft-1.0.so.0.3400.1
-rwxr-xr-x 1 root root  30292 Dec 14 12:54 
/usr/lib/libpangoxft-1.0.so.0.3400.1
======================================================

And this is the hacked ebuild I've been using (for some years now):
======================================================
$ eix -l avast                      
[I] app-antivirus/avast4workstation [1]
     Available versions:  
       (~)  1.3.0-r2  ^m
     Installed versions:  1.3.0-r2^m[?](09:41:23 15/12/13)
     Homepage:            http://www.avast.com/eng/avast-for-linux-workstation.html
     Description:         avast! Linux Home Edition

[1] /usr/local/portage
======================================================

Other than removing the ebuild and looking for another antivirus, is there 
something I can do to clear this @repserved-rebuild loop?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [gentoo-user] Re: @preserved-rebuild gone in a loop
  2013-12-15  9:51 [gentoo-user] @preserved-rebuild gone in a loop Mick
@ 2013-12-15 12:31 ` Nikos Chantziaras
  2013-12-15 12:32 ` [gentoo-user] " Neil Bothwick
  2013-12-15 16:37 ` Benjamin Block
  2 siblings, 0 replies; 6+ messages in thread
From: Nikos Chantziaras @ 2013-12-15 12:31 UTC (permalink / raw
  To: gentoo-user

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 all caused by some hack I have in my local portage for app-
> antivirus/avast4workstation-1.3.0-r2.  No matter how many times I run
> @preserved-rebuild the libs in question keep coming up:

Yes, that's to be expected. Avast is a binary, it's not built from 
sources, so there's no link step involved that would link against the 
new pango libs.

I'm not sure if it'll work, by try emerging x11-libs/pangox-compat. If 
that doesn't help, then your only option is to downgrade your pango 
version to the version that doesn't exhibit the problem and mask all 
newer versions.



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] @preserved-rebuild gone in a loop
  2013-12-15  9:51 [gentoo-user] @preserved-rebuild gone in a loop Mick
  2013-12-15 12:31 ` [gentoo-user] " Nikos Chantziaras
@ 2013-12-15 12:32 ` Neil Bothwick
  2013-12-15 16:37 ` Benjamin Block
  2 siblings, 0 replies; 6+ messages in thread
From: Neil Bothwick @ 2013-12-15 12:32 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 684 bytes --]

On Sun, 15 Dec 2013 09:51:39 +0000, Mick wrote:

> !!! 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
>  *      used by /opt/avast4workstation/bin/avastgui (app-
> antivirus/avast4workstation-1.3.0-r2)
> Use emerge @preserved-rebuild to rebuild packages using these libraries
> ======================================================

It's installed in /opt, does that mean this is a binary package? If so,
no amount of reinstalling it will cause it to be linked against a
different library version.


-- 
Neil Bothwick

Become a gynaecologist, look up a friend today.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] @preserved-rebuild gone in a loop
  2013-12-15  9:51 [gentoo-user] @preserved-rebuild gone in a loop Mick
  2013-12-15 12:31 ` [gentoo-user] " Nikos Chantziaras
  2013-12-15 12:32 ` [gentoo-user] " Neil Bothwick
@ 2013-12-15 16:37 ` Benjamin Block
  2013-12-16  4:04   ` [gentoo-user] " eroen
  2 siblings, 1 reply; 6+ messages in thread
From: Benjamin Block @ 2013-12-15 16:37 UTC (permalink / raw
  To: gentoo-user

On 09:51 Sun 15 Dec     , 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 all caused by some hack I have in my local portage for app-
> antivirus/avast4workstation-1.3.0-r2.  No matter how many times I run 
> @preserved-rebuild the libs in question keep coming up:
> 

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


- Benjamin


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [gentoo-user] Re: @preserved-rebuild gone in a loop
  2013-12-15 16:37 ` Benjamin Block
@ 2013-12-16  4:04   ` eroen
  2013-12-16  9:28     ` Mick
  0 siblings, 1 reply; 6+ messages in thread
From: eroen @ 2013-12-16  4:04 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]

On Sun, 15 Dec 2013 17:37:53 +0100
Benjamin Block <bebl@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.

-- 
eroen

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] Re: @preserved-rebuild gone in a loop
  2013-12-16  4:04   ` [gentoo-user] " eroen
@ 2013-12-16  9:28     ` Mick
  0 siblings, 0 replies; 6+ messages in thread
From: Mick @ 2013-12-16  9:28 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: Text/Plain, Size: 2431 bytes --]

On Monday 16 Dec 2013 04:04:34 eroen wrote:
> On Sun, 15 Dec 2013 17:37:53 +0100
> 
> Benjamin Block <bebl@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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2013-12-16  9:29 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-15  9:51 [gentoo-user] @preserved-rebuild gone in a loop Mick
2013-12-15 12:31 ` [gentoo-user] " Nikos Chantziaras
2013-12-15 12:32 ` [gentoo-user] " Neil Bothwick
2013-12-15 16:37 ` Benjamin Block
2013-12-16  4:04   ` [gentoo-user] " eroen
2013-12-16  9:28     ` Mick

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox