[gentoo-user] Safe to install libpng-1.2.44?

[gentoo-user] Safe to install libpng-1.2.44?

[Graham Murray]

After an emerge --sync on an ~x86 system, the upgrade to opera-10.60
wants to install libpng-1.2.44 in a new slot. Considering all of the
problems surrounding the upgrade to  libpng-1.4.3, is it safe to let
portage install libpng-1.2.44?

Re: [gentoo-user] Safe to install libpng-1.2.44?

[Keith Dart]

=== On Fri, 07/02, Graham Murray wrote: ===
> After an emerge --sync on an ~x86 system, the upgrade to opera-10.60
> wants to install libpng-1.2.44 in a new slot. Considering all of the
> problems surrounding the upgrade to  libpng-1.4.3, is it safe to let
> portage install libpng-1.2.44?

===

Yes, but be prepared for some extra work and a lengthy upgrade (half
your system will be recompiled). However, I have not tried Opera, but
it should work.

See flameeye's blog first. But ignore the part about
the libpng-1.4.x-update.sh script being a hack. I found that necessary
and it worked for me. 


-- Keith Dart

-- 

-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   Keith Dart <keith@dartworks.biz>
   public key: ID: 19017044
   <http://www.dartworks.biz/>
   =====================================================================

Re: [gentoo-user] Safe to install libpng-1.2.44?

[Dale]

Keith Dart wrote:
> === On Fri, 07/02, Graham Murray wrote: ===
>    
>> After an emerge --sync on an ~x86 system, the upgrade to opera-10.60
>> wants to install libpng-1.2.44 in a new slot. Considering all of the
>> problems surrounding the upgrade to  libpng-1.4.3, is it safe to let
>> portage install libpng-1.2.44?
>>      
> ===
>
> Yes, but be prepared for some extra work and a lengthy upgrade (half
> your system will be recompiled). However, I have not tried Opera, but
> it should work.
>
> See flameeye's blog first. But ignore the part about
> the libpng-1.4.x-update.sh script being a hack. I found that necessary
> and it worked for me.
>
>
> -- Keith Dart
>
>    

This appears to be the opposite of a upgrade.  He has a package that 
wants the OLD slotted version of libpng not the NEW slotted version.  If 
I understand that correctly, he has already done the upgrade but now 
something needs the old package installed in addition to the new one.

OP, my thinking is this.  Be prepared for some packages to rebuild when 
you run revdep-rebuild.  Part of me says that there won't be any but one 
can never be certain of these things.   Also, when I did my upgrade I 
had no GUI until it rebuilt the packages.  Again, one can never be 
certain of these things.  I would do this:

emerge opera
run revdep-rebuild -i and say a prayer if you think it will help.
emerge -uvDNa world and hope it comes out clean, provided it was clean 
before you started this.

Wouldn't hurt to have a second puter around to get help here if you run 
into trouble.  ;-)

Dale

:-)  :-)

Re: [gentoo-user] Safe to install libpng-1.2.44?

[Neil Bothwick]

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

On Fri, 02 Jul 2010 17:49:30 -0500, Dale wrote:

> This appears to be the opposite of a upgrade.  He has a package that 
> wants the OLD slotted version of libpng not the NEW slotted version.
> If I understand that correctly, he has already done the upgrade but now 
> something needs the old package installed in addition to the new one.

The joys of running binary software...


-- 
Neil Bothwick

A seminar on time travel will be held 2 weeks ago.

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

[gentoo-user] Re: Safe to install libpng-1.2.44?

[Nikos Chantziaras]

On 07/03/2010 03:13 AM, Neil Bothwick wrote:
> On Fri, 02 Jul 2010 17:49:30 -0500, Dale wrote:
>
>> This appears to be the opposite of a upgrade.  He has a package that
>> wants the OLD slotted version of libpng not the NEW slotted version.
>> If I understand that correctly, he has already done the upgrade but now
>> something needs the old package installed in addition to the new one.
>
> The joys of running binary software...

You have a way of running non-interpreted sources without compiling them 
to binary format first? :P

Re: [gentoo-user] Re: Safe to install libpng-1.2.44?

[Neil Bothwick]

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

On Sat, 03 Jul 2010 15:02:18 +0300, Nikos Chantziaras wrote:

> > The joys of running binary software...  
> 
> You have a way of running non-interpreted sources without compiling
> them to binary format first? :P

Yes, but I'm not telling how :)

You know what I meant!


-- 
Neil Bothwick

PCMCIA: People Can't Memorize Computer Industry Acronyms

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

Re: [gentoo-user] Safe to install libpng-1.2.44?

[Keith Dart]

=== On Fri, 07/02, Dale wrote: ===
> This appears to be the opposite of a upgrade.  He has a package that 
> wants the OLD slotted version of libpng not the NEW slotted version.
> If I understand that correctly, he has already done the upgrade but
> now something needs the old package installed in addition to the new
> one.

===

Oh right, sorry, didn't look closely enough. 

I would recommend avoiding that until Opera is upgraded. I did have for
a while both 1.2 and 1.4 slots installed and some things got dynamically
linked with both of them. That caused me some problems.

Overall, libpng12 to libpng14 was a real pain... But now that's over
with.



-- Keith Dart

-- 

-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   Keith Dart <keith@dartworks.biz>
   public key: ID: 19017044
   <http://www.dartworks.biz/>
   =====================================================================

Re: [gentoo-user] Safe to install libpng-1.2.44?

[Graham Murray]

Dale <rdalek1967@gmail.com> writes:

> This appears to be the opposite of a upgrade.  He has a package that
> wants the OLD slotted version of libpng not the NEW slotted version.
> If I understand that correctly, he has already done the upgrade but
> now something needs the old package installed in addition to the new
> one.

As it happens the issue was moot for me, but I am sure that some people
were caught out. I said 'No' to the 'emerge -auDvN @world' and
waited. Later I saw a new bugzilla entry
(https://bugs.gentoo.org/show_bug.cgi?id=326583) about unneeded opera
dependency on libpng. So I waited until after the fix was announced and
in the tree and resynced, and it no longer wanted to install
libpng-1.2.44. 

Re: [gentoo-user] Safe to install libpng-1.2.44?

[Dale]

Graham Murray wrote:
> Dale<rdalek1967@gmail.com>  writes:
>
>    
>> This appears to be the opposite of a upgrade.  He has a package that
>> wants the OLD slotted version of libpng not the NEW slotted version.
>> If I understand that correctly, he has already done the upgrade but
>> now something needs the old package installed in addition to the new
>> one.
>>      
> As it happens the issue was moot for me, but I am sure that some people
> were caught out. I said 'No' to the 'emerge -auDvN @world' and
> waited. Later I saw a new bugzilla entry
> (https://bugs.gentoo.org/show_bug.cgi?id=326583) about unneeded opera
> dependency on libpng. So I waited until after the fix was announced and
> in the tree and resynced, and it no longer wanted to install
> libpng-1.2.44.
>
>    

That works too.  Should also be better in the long run.  Whew, glad that 
is over.  Nothing worse than having to go through a nasty upgrade just 
to have to do it again later.  ;-)

Dale

:-)  :-)

Re: [gentoo-user] Safe to install libpng-1.2.44?

[Enrico Weigelt]

Hi folks,

<big_snip />


I think the libpng issue shows up a more generic problem: 
we IMHO dont have a way for recording, which version / interface
of some version a package is built against. The need for things
like revdep-rebuild also comes from that.

I'm currently working on an generic design for that, some ideas:
(of course, yet limited to C and similar languages ;-o)

* libraries with (incompatible) interface changes should install
  their headers under some own versioned prefix
* library imports should _always_ happen via pkg-config
  (dont use .la files)
* pkg-config descriptors are extended to declare the API and 
  ABI version and generation, so interface breaks can be 
  determined automatically
* the package management records which version of some imported
  library a package was built against (some kind of revdep-scan
  between compile and merge)
* with that information the package management can do an smooth
  upgrade (w/o temporary breaks until revdep-rebuild finished)


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------

[gentoo-user] Re: Safe to install libpng-1.2.44?

[walt]

On 07/04/2010 06:38 PM, Enrico Weigelt wrote:
> Hi folks,

> * library imports should _always_ happen via pkg-config
>   (dont use .la files)

+1  (Am I allowed +100?)

Re: [gentoo-user] Re: Safe to install libpng-1.2.44?

[Mike Edenfield]

On 7/4/2010 10:05 PM, walt wrote:
> On 07/04/2010 06:38 PM, Enrico Weigelt wrote:
>> Hi folks,
> 
>> * library imports should _always_ happen via pkg-config
>>   (dont use .la files)
> 
> +1  (Am I allowed +100?)

If so, allow me to +1billion

Re: [gentoo-user] Safe to install libpng-1.2.44?

[Dale]

Enrico Weigelt wrote:
> Hi folks,
>
> <big_snip />
>
>
> I think the libpng issue shows up a more generic problem:
> we IMHO dont have a way for recording, which version / interface
> of some version a package is built against. The need for things
> like revdep-rebuild also comes from that.
>
> I'm currently working on an generic design for that, some ideas:
> (of course, yet limited to C and similar languages ;-o)
>
> * libraries with (incompatible) interface changes should install
>    their headers under some own versioned prefix
> * library imports should _always_ happen via pkg-config
>    (dont use .la files)
> * pkg-config descriptors are extended to declare the API and
>    ABI version and generation, so interface breaks can be
>    determined automatically
> * the package management records which version of some imported
>    library a package was built against (some kind of revdep-scan
>    between compile and merge)
> * with that information the package management can do an smooth
>    upgrade (w/o temporary breaks until revdep-rebuild finished)
>
>
> cu
>    

This may be something you should post on -dev.  They are the ones that 
handle this sort of thing.

Things are better there but take a flack jacket.  Never hurts to have 
one just in case you need it.  ;-)

Dale

:-)  :-)