Hi all,(as an unregular reader of debian-devel, please Cc: me so that I don't miss your replies)
I have uploaded libjpeg-turbo 2.0.x to experimental several months ago (August 2019). I feel, it is time to get 2.0.x into testing/unstable now.
However, I have never really done a transition of such a core'ish shared library package and I'd love to receive some guidance with this before I do the actual upload.
First of all, I don't think that a classical transition is required as there has not been an SONAME change for the shared libs in libjpeg-turbo. Package names haven't changed, either.
Simply uploading and waiting for things to break (at runtime) is neither a good approach, I sense. I have done some usual smoke tests (running this and that desktop environment, viewing JPEG images, etc.), but that feels insufficient.
People experienced with transitions of core packages with libjpeg testings, how would you approach sanity checks of libjpeg-turbo 2.0.x before uploading?
https://salsa.debian.org/debian/libjpeg-turbo Thanks in advance for any kind of input, Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunweaver@debian.org, http://sunweavers.net
Attachment:
pgp6qHclrdi3L.pgp
Description: Digitale PGP-Signatur