Hi,
On Wed, 16 Oct 2024 10:12:18 +0200 Guido =?iso-8859-1?Q?G=FCnther?=
<a...@sigxcpu.org> wrote:
Hi,
thanks for looking into this.
On Wed, Oct 16, 2024 at 02:50:15PM +0800, zhangdandan wrote:
> 3. Solution
> Please take care of the d/control file in phoc packages.
> ```
> libwlroots-dev (>= 0.17.0),
> libwlroots-dev (<< 0.18~),
> ```
How would that change anything? There is not libwlroots-dev >= 0.18.0.
Looks like the only solution would be to reintroduce wlroots 0.17 source
package as wlroots-0.17 so both source packages can live in parallel,
right?
No, that's not what should happen. Instead, every reverse-dependency should be
updated to build-depend on the new libwlroots-*-dev package, patched to look for
the renamed wlroots-0.18.pc file, and adapted to the new API.
Unless this was a rewrite of the API, largely incompatible with the previous
version, the idea of renaming everything is bad, as it causes every rdep to have
to change all the build scripts (e.g. configure.ac) for the new version. And
likely for every version thereafter, including changes to debian/control, so
just a round of binNMUs for every reverse-dependency is no longer possible. And
there's no reason to ship two wlroots in Debian for just a handful of rdeps. RC
bugs should be filed to upgrade to the new version, and those that can't be
ported in time will have to be left out of trixie I'm afraid. That, or revert to
the previous version, and coordinate the update to the new one once patches have
been prepared, etc.
btw next time, it'd be nice to file a transition bug beforehand and receive
feedback (and an ACK) from the release team.
https://release.debian.org/transitions/html/auto-wlroots.html
Cheers,
Emilio
