[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: JPEG 8 transition



Andreas Barth <aba@not.so.argh.org> writes:
> * Sune Vuorela (nospam@vuorela.dk) [100214 21:32]:
>> I currently think roll-back, doing things properly, going ahead, is the
>> way forward.
> I fear I need to agree with you. We should have libjpeg62 with
> symbols, recompile every package build-depending on libjpeg*-dev after
> that till the release, and then move to libjpeg8 (or whatever it is)
> at the begining of the squeeze+1-cycle (and we can be sure nothing
> breaks because of the symbols).

I think we might even do this before releazing squeeze. Once we have
versioned symbols, the transition won't hurt as much.

The current situation is quite problematic, as we can't foresee how many
package can break after partial upgrades. We know at least of one issue
when kdm loads both libjpeg62 and libjpeg8, but there will probably
dozens of other problems.

> In other words, please rollback libjpeg-dev to point again to
> libjpeg62-dev, and add symbol versions to libjpeg62 (the second can
> happen later, but as sooner it happens the better it is). After
> libjpeg-dev points again to libjpeg62-dev, we need to binNMU all
> affected programs.

ACK.

Marc
-- 
BOFH #202:
kernel panic: write-only-memory (/dev/wom0) capacity exceeded.

Attachment: pgpDtJz078JYI.pgp
Description: PGP signature


Reply to: