Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: transition X-Debbugs-Cc: libwa...@packages.debian.org Control: forwarded -1 https://release.debian.org/transitions/html/auto-libwacom.html
src:libwacom was recently updated from libwacom2 to libwacom9, starting a transition. I don't see any indication that this was approved by the release team, so I'm opening this transition tracking bug (my apologies if there is already a transition-tracker that I missed). https://release.debian.org/transitions/html/auto-libwacom.html looks like it is tracking this transition correctly. Because libwacom2 and libwacom9 both depend on a matching libwacom-common, this makes affected packages such as mutter uninstallable in unstable. How big are the API/ABI breaks? Are dependent packages expected to compile and work successfully without code changes? In addition to rebuilding reverse-dependencis, src:libwacom will need a source-only upload to unstable so that it will be allowed to migrate. It is usually best for transitions to happen by uploading NEW packages to experimental, then opening a transition-tracking bug like this one and getting release team approval, and finally re-uploading to unstable after approval has been received, particularly if the transition is an all-or-nothing one like this. smcv
