Bug#650601: How to proceed with libpng transition
Dear all,
it is high time that we go forward with transitioning libpng-dev
to version 1.6. That means, not only uploading libpng1.6, but
*replacing* libpng in unstable with the new version.
If we plan to have this ready for November freeze of jessie, we
need to get started *now*!
> Major package of most is the state that can be migrated to libpng1.6.
I agree, for TeX Live building purposes I have rebuilt several
package with libpng1.6, namely libgd2, freetype, cairo, jbig2dec,
and ghostscript (all the deps necessary for texlive building).
There were no problems with that.
I am also volunteering to rebuild and test other packages, but
as long as there is no declared wish of the libpng developers
it is wasted times.
So, please, let me know, *what* are your plans concerning jessie?
Should jessie ship with libpng 1.6 as default or 1.2?
If you want to transition, what are the next steps? My suggestion is:
* upload a libpng-dev (NOT libpng16) replacement to *experimental*
* test all packages for binNMU
* try to fix the failed packages, mass bug filing
* give some head way
* upload to unstable
I think the *first* and *most*important* step is that we upload a
replacement libpng-dev based on 1.6 to *experimental*. This is a
sign that we are planning to transition.
But again, libpng developers, please let me know your plans!
I *really* want to help to get this transition going!
Thanks
Norbert
------------------------------------------------------------------------
PREINING, Norbert http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
------------------------------------------------------------------------
Reply to: