Control: owner 1112763 ! Control: owner 1113348 ! To be honest my heart sank when I saw this in my inbox for both open-ath9k-htc-firmware and carl9170fw: [Timo Röhling] > Severity: serious > User: [email protected] > Usertags: cmake-4 > Tags: ftbfs, forky, sid
If you're not aware, these are both (at least de facto) key packages, being essentially offshoots of firmware-linux-free kept in their own source packages. CMake 4 has apparently been in experimental for a little while; it would've been very helpful if maintainers had lower-severity bug reports before uploading CMake 4 to unstable, especially since correct fixes can require cooperation from upstreams that don't share the urgency. I see (only now) your MBF notice from April at https://lists.debian.org/msgid-search/r7supj4lgmvmbsgv3q7sizcmoee7wq46q2bd5jc52usczmjbsg%40syiriheiaiyc (not on debian-devel-announce) > Trixie will ship with CMake 3.31, so this issue is only relevant for the > Forky release cycle. However, I plan to file forky tagged bugs early, so that > maintainers are aware and can forward the bug to upstream as needed. This sentence (that bugs filed will be to help awareness and time to reach upstream) almost hints at my point that they're a tool for maintainers to get a fix in motion and need not have been RC. CMake 4 is now in unstable, so what's done is done, but I think this could've been done more carefully. Filing a Severity: important bug is the standard for such a big migration, and a formal transition (such as for a shared library) likewise would've required more patience for the almost 1,000 bugs just filed: https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=cmake%40packages.debian.org&tag=cmake-4 Anywho, I'll see if I can prepare fixes shortly.
signature.asc
Description: This is a digitally signed message part
smime.p7s
Description: S/MIME cryptographic signature
