Why won't you just rename the package back to "libjpeg-progs"? Without this nonsense migration, there won't be any issues. The reason for libjpeg-turbo-progs, those "waaah hijack" complaints don't hold any water anymore as libjpeg9 is gone, and I don't think the Release Team is going to ever allow it back.
An end-user doesn't care which source a binary comes from, so encoding such an implementation detail in the name is a disservice. Even worse if it causes RC bugs as well. Thus, having just "libjpeg-progs" only would be the simplest solution. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
