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

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.

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.

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

Thank you for your work updating and maintaning jpeg-xl!

Jeremy Bícha

Reply via email to