Mailing List Archive

rfc: jpeg upgrade news item
I've been asked to write a news item for jpeg upgrade by few developers.
Personally I don't see it's required, it's a default library upgrade,
but here's my attempt:

Title: Upgrade from media-libs/jpeg 6b to 7
Author: Samuli Suominen <ssuominen@gentoo.org>
Content-Type: text/plain
Posted: 2009-09-22
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: media-libs/jpeg

Since media-libs/jpeg-7 the .so version changed from libjpeg.so.62
to libjpeg.so.7. This will break temporarily a lot of packages,
including environments like Gnome, Xfce4 or KDE. You will need to run
revdep-rebuild from gentoolkit package.

Installing media-libs/jpeg-compat isn't the correct solution because
the package is meant to be used only with binary only applications like
games-strategy/savage2-bin where recompiling isn't an option.

You can temporarily install media-libs/jpeg-compat to get libjpeg.so.62
back so you'll be able to run applications again but it will most likely
cause you random crashing issues. [1].

For more information see [2] and [3].

[1] http://bugs.gentoo.org/show_bug.cgi?id=279227
[2] http://bugs.gentoo.org/show_bug.cgi?id=285598
[3] http://forums.gentoo.org/viewtopic-t-792906.html
Re: rfc: jpeg upgrade news item [ In reply to ]
Samuli Suominen <ssuominen@gentoo.org> writes:
> I've been asked to write a news item for jpeg upgrade by few developers.
> Personally I don't see it's required, it's a default library upgrade,
> but here's my attempt:
[…]
> to libjpeg.so.7. This will break temporarily a lot of packages,
> including environments like Gnome, Xfce4 or KDE. You will need to run
> revdep-rebuild from gentoolkit package.

FWIW, I appreciate notices like this. As an end user, I only know that
I'll need to build the ~dozen or so packages `emerge -pvuD world` lets
me know about. Anything that lets me know that I need to allocate time
for (and factor in the risk of) rebuilding all of, say, GNOME is good.
I don't know that GLEP 42 items are the most appropriate way of doing
this, but they seem to be the best way, at present.

Similarly for updates where there's any sort of upgrade guide or manual
process required (e.g., TeX live, Gnome 2.22, GCC, &c.), as there's no
indication from emerge output that such a guide exists.


> Display-If-Installed: media-libs/jpeg

"<media-libs/jpeg-7", perhaps?

--
...jsled
http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo ${a}@${b}
Re: rfc: jpeg upgrade news item [ In reply to ]
Josh Sled wrote:
>
>
>> Display-If-Installed: media-libs/jpeg
>
> "<media-libs/jpeg-7", perhaps?
>

Yes there should be such a restriction to avoid hitting people who have
already upgraded.

Regards,
Petteri
Re: rfc: jpeg upgrade news item [ In reply to ]
>>>>> On Tue, 22 Sep 2009, Petteri Räty wrote:

>> "<media-libs/jpeg-7", perhaps?

> Yes there should be such a restriction to avoid hitting people who
> have already upgraded.

I don't think that there should be a version restriction. People may
have upgraded but not have followed the advice in the news item.

Ulrich
Re: rfc: jpeg upgrade news item [ In reply to ]
On Tuesday 22 of September 2009 18:24:11 Ulrich Mueller wrote:
> >>>>> On Tue, 22 Sep 2009, Petteri Räty wrote:
> >>
> >> "<media-libs/jpeg-7", perhaps?
> >
> > Yes there should be such a restriction to avoid hitting people who
> > have already upgraded.
>
> I don't think that there should be a version restriction. People may
> have upgraded but not have followed the advice in the news item.
>
> Ulrich

If they had upgraded, they also probably have it fixed already.
Re: rfc: jpeg upgrade news item [ In reply to ]
>>>>> On Tue, 22 Sep 2009, Dawid Węgliński wrote:

>> People may have upgraded but not have followed the advice in the
>> news item.

> If they had upgraded, they also probably have it fixed already.

So for everybody it's obvious how to fix it? If you argue like this,
then you don't need the news item at all. ;-)

Ulrich
Re: rfc: jpeg upgrade news item [ In reply to ]
Ulrich Mueller wrote:
>>>>>> On Tue, 22 Sep 2009, Dawid Węgliński wrote:
>
>>> People may have upgraded but not have followed the advice in the
>>> news item.
>
>> If they had upgraded, they also probably have it fixed already.
>
> So for everybody it's obvious how to fix it? If you argue like this,
> then you don't need the news item at all. ;-)
>
> Ulrich
>

Without a version restriction I think Portage will show it for new
installs too.

Regards,
Petteri