Bug#977814: fixed in llvm-toolchain-11 1:11.0.1-1
In data venerdì 8 gennaio 2021 12:38:20 CET, Gianfranco Costamagna ha scritto: > llvm-toolchain-11 is now fixed, and clazy should be fixed too. No, llvm-toolchain-11 is not fixed yet. > Unfortunately clazy seems to be missing a "break" relationship against old > llvm, and britney uses > the broken testing version to test it. It makes no sense for clazy to break and old llvm, it should be rather the other way round... but it shouldn't be needed. Also, the version in testing is *not* broken. clazy in testing is perfectly working, and it was the llvm-toolchain-11 upload that broke it. > I don't know if we can hint to let it migrate anyway, Considering nothing was actually done to fix the problems I reported earlier in this bug, I don't think that letting the newer llvm-toolchain-11 migrate and break also testing is an acceptable way forward. Even more so when there was *no* attempt by the Debian LLVM Maintainers (of which you are part) to debug what was the issue. All this "fix" did was to apply the diff I mentioned, which was to fix only a small part of the problems I reported. Also, reading it further, even the shlibs of all the other libraries need to be fixed: they all specify old versions (like 9~something) that are satisfied by any llvm-toolchain-11 version available, including prereleases. > Let me know if you have a solution for this issue, The Debian LLVM Maintainers ought to help debug why updating a new version suddently breaks software built against old versions of it. Sorry if I seem harsh: LLVM is a key component in a modern Debian system, so uploading new versions and providing almost no help on problems does not seem like a good idea for the distribution. -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#977814: fixed in llvm-toolchain-11 1:11.0.1-1
control: reopen -1 Hello Pino, llvm-toolchain-11 is now fixed, and clazy should be fixed too. Unfortunately clazy seems to be missing a "break" relationship against old llvm, and britney uses the broken testing version to test it. I don't know if we can hint to let it migrate anyway, or we should reupload with a fixed break relationship to let Britney understand that they have to migrate together. Let me know if you have a solution for this issue, and if we really need the break or not. (I don't know if the old package works only with llvm-* new or its runtime retro-compatible) G. On Wed, 06 Jan 2021 11:50:25 + Debian FTP Masters wrote: > Source: llvm-toolchain-11 > Source-Version: 1:11.0.1-1 > Done: Sylvestre Ledru > > We believe that the bug you reported is fixed in the latest version of > llvm-toolchain-11, which is due to be installed in the Debian FTP archive. > > A summary of the changes between this version and the previous one is > attached. > > Thank you for reporting the bug, which will now be closed. If you > have further comments please address them to 977...@bugs.debian.org, > and the maintainer will reopen the bug report if appropriate. > > Debian distribution maintenance software > pp. > Sylvestre Ledru (supplier of updated llvm-toolchain-11 > package) > > (This message was generated automatically at their request; if you > believe that there is a problem with it please contact the archive > administrators by mailing ftpmas...@ftp-master.debian.org) > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Format: 1.8 > Date: Wed, 06 Jan 2021 09:21:24 +0100 > Source: llvm-toolchain-11 > Architecture: source > Version: 1:11.0.1-1 > Distribution: unstable > Urgency: medium > Maintainer: LLVM Packaging Team > Changed-By: Sylvestre Ledru > Closes: 977814 > Changes: > llvm-toolchain-11 (1:11.0.1-1) unstable; urgency=medium > . >[ Sylvestre Ledru ] >* New stable release > . >[ Gianfranco Costamagna ] >* Drop old patch, upstream now >* Run dh_makeshlibs with -V parameter (Closes: #977814) > Checksums-Sha1: > eecd206b0409aed5b630bf3eef4ee484fe5be632 5975 llvm-toolchain-11_11.0.1-1.dsc > 30d7160c402e88747afe83aef5a45e067bffe9ed 78748920 > llvm-toolchain-11_11.0.1.orig.tar.xz > 364b66028f7187abd4b220e092ae4d01ede114ef 129488 > llvm-toolchain-11_11.0.1-1.debian.tar.xz > f50de002773ff899d9cdbc5dd003b5225ab814a6 26645 > llvm-toolchain-11_11.0.1-1_amd64.buildinfo > Checksums-Sha256: > 74768bfd5fdf35bc73796a102bce654c7ed157b0cfb4b5da530bac6177a521c1 5975 > llvm-toolchain-11_11.0.1-1.dsc > 39ed2924a4bc0e4db79dfdd97f97bca64a26ff398b9128934c3fc7b3186e4c45 78748920 > llvm-toolchain-11_11.0.1.orig.tar.xz > 17bc5ad3b58148eb168f4a2f45fbc1c1188d06b163962a687a82d0dc916d3472 129488 > llvm-toolchain-11_11.0.1-1.debian.tar.xz > b9e5c36cf3c00d2ac301d212bebb4be471b996b5f520266c0fbd329818f588dd 26645 > llvm-toolchain-11_11.0.1-1_amd64.buildinfo > Files: > 127e27b0f27865b4d253080eacd31e3b 5975 devel optional > llvm-toolchain-11_11.0.1-1.dsc > 04f17a9ae5a379fbadb56c306f9d959f 78748920 devel optional > llvm-toolchain-11_11.0.1.orig.tar.xz > 513bdcc906ea9bcc9870c902ed88d5ff 129488 devel optional > llvm-toolchain-11_11.0.1-1.debian.tar.xz > f8bc7db5a0dd5bd974ea1893cd47d6df 26645 devel optional > llvm-toolchain-11_11.0.1-1_amd64.buildinfo
