Hi, I send this email to Mathieu Malaterre <[email protected]>, please help to view this bug report.
在 2026/11/15 14:59, Jeremy Bícha 写道: > On Sun, Nov 15, 2026 at 3:59 AM xiao sheng wen(肖盛文) <[email protected]> wrote: >>> Please restore the Architecture restrictions in debian/control and >>> debian/rules. This will enable jpeg-xl to continue to be built on some >>> Debian ports which now have unsatisfiable Build-Depends: >>> https://buildd.debian.org/status/package.php?p=jpeg-xl >> >> maintain a CPU Architecture restrictions is a hard work for package >> maintainer. This work also larger the debian/control and debian/rules >> files. I hope keep these files simply. >> >> The jpeg-xl package already support Debian official CPU Architecture >> has no problem. > > FTBFS is a Release Critical issue. Ports are not included in Debian > releases, so it makes sense for "FTBFS on ports" bugs to be lower than > RC. I believe "important" is actually a reasonable severity since the > package being unable to be updated or receive security updates has a > "major effect on the usability of [the] package, without rendering it > completely unusable to everyone". See the official bug severity > definitions at https://www.debian.org/Bugs/Developer#severities > After new version jpeg-xl can't build on those ports(i386,etc,.), the jpeg-xl should remove from them(i386,etc,.) from sid, then testing. so it has not sense need to "updated or receive security updates" more. For unofficial ports, DSA don't take care it. I believe "important" is not reasonable severity for "FTBFS on ports". The stable and oldstable on i386 will still being able to be updated or receive security updates. > Neither google-perftools (tcmalloc) nor Java are essential features for > jpeg-xl. > > jpeg-xl is team-maintained which means that there are other > maintainers and their opinions also matter. Your first upload for > jpeg-xl was this year. Please don't undo work from other team members > when they object. The jpeg-xl is team-maintained, you also do many work on this package. But Mathieu Malaterre <[email protected]> is only one Uploaders, I checked the salsa git log, the CPU Architecture restrictions is do by Mathieu several years ago. If Mathieu would continuous maintain the CPU Architecture restrictions list, please tell us. > > If you'd rather not do the work to care about ports, I could submit a > merge request (or even an upload) to restore this functionality. I > agree that debian/control.in is not needed for most packages, so I > appreciate your removal of that part. I'm not care about i386 ports now. IMHO, it still not necessary to maintain the CPU Architecture restrictions list more. Some Debian documents also suggestion it. Build-Depends package don't need Architecture list. If the Mathieu would restore Architecture restrictions, please do it. > > By the way, the Release Team requests filing a bug and waiting for > approval when doing library transitions. The jpeg-xl transition > overlaps with multiple ongoing approved transitions. It looks like > this time will be ok as everything still builds with the new jpeg-xl > and jpeg-xl will be able to migrate to Testing smoothly. > https://wiki.debian.org/Teams/ReleaseTeam/Transitions I'd do some work for symbols on this version update, I checked that it has not the ABI break. This automated library transitions should be ok: https://release.debian.org/transitions/html/auto-jpeg-xl.html Thank you for your work updating and maintaning jpeg-xl! Regards, -- 肖盛文 xiao sheng wen -- Debian Developer(atzlinux) Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40debian.org Debian salsa: https://salsa.debian.org/atzlinux-guest GnuPG Public Key: 0x00186602339240CB
OpenPGP_signature.asc
Description: OpenPGP digital signature

