#1137244 llvm-toolchain-22: Overly restrictive conflicts for libmlir-*

#1137244#5
Date:
2026-05-21 15:23:50 UTC
From:
To:
Hi,

I'm trying to build packages with flang-21 and flang-22 simultaneously.

(Building with dh-fortran which keeps the libraries/modules separate; the aim is to get modules for
both compilers simultaneously).
flang-21 and flang-22 (etc) can't be co-installed because libmlir-x.y conflict. However it appears they are
distinct and should be able to co-install; is this a relic of previous versions or am I missing
something?

Best regards
Alastair

#1137244#10
Date:
2026-07-25 16:50:12 UTC
From:
To:
yes, these conflicts should just be removed. Please can you provide a patch?
#1137244#13
Date:
2026-07-25 16:50:12 UTC
From:
To:
yes, these conflicts should just be removed. Please can you provide a patch?
#1137244#18
Date:
2026-07-29 09:23:27 UTC
From:
To:
Will do.

I am currently testing flang-21 and flang-22 co-installation, and
testing a patch.

Multiple llvm-toolchain builds make this a slow process on my test VM :-(

Will reply soon

Alastair

#1137244#23
Date:
2026-07-29 09:23:27 UTC
From:
To:
Will do.

I am currently testing flang-21 and flang-22 co-installation, and
testing a patch.

Multiple llvm-toolchain builds make this a slow process on my test VM :-(

Will reply soon

Alastair

#1137244#26
Date:
2026-07-29 09:23:27 UTC
From:
To:
Will do.

I am currently testing flang-21 and flang-22 co-installation, and
testing a patch.

Multiple llvm-toolchain builds make this a slow process on my test VM :-(

Will reply soon

Alastair

#1137244#31
Date:
2026-09-27 06:49:29 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-22, 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 1137244@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <doko@debian.org> (supplier of updated llvm-toolchain-22 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 25 Jul 2026 18:43:43 +0200
Source: llvm-toolchain-22
Architecture: source
Version: 1:22.1.8-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Changed-By: Matthias Klose <doko@debian.org>
Closes: 1137244 1138702 1141868 1142548 1142778 1147573
Changes:
 llvm-toolchain-22 (1:22.1.8-2) unstable; urgency=medium
 .
   [ Sylvestre Ledru ]
   * d/rules: retry the documentation build serially when sphinx's parallel
     workers die (bare "EOFError" from multiprocessing after a successful
     compile, trixie amd64/arm64 2026-09-02/03)
   * d/rules: set SCCACHE_IDLE_TIMEOUT=0 so the sccache server stays alive for
     the whole build; otherwise it idles out (default 600s) during the quiet
     final-link phase and the libfuzzer step auto-spawns a default-config server
     writing to $HOME/.cache/sccache, which fails with HOME=/nonexistent
   * d/rules: use the shared GCS sccache cache on arm64 too (add arm64 to the
     GCP arch filter)
   * d/rules: Disable sccache on the releases whose glibc is too old for the
     binary the build host provides. /opt/sccache/sccache comes from
     mozilla/sccache's latest release and, on s390x (the only arch without a
     static musl build), needs glibc >= 2.34 since v0.17.0. On focal
     (glibc 2.31) it cannot even start, and the build died at --start-server
     with "version `GLIBC_2.34' not found" in stamps/configure.
   * d/rules: Drop llvm-mt from the install list when it wasn't built.
     Upstream only builds llvm-mt when it detects libxml2 at configure
     time; on Ubuntu focal/arm64 the libxml2 symbol check fails and the
     tool is silently skipped, which made dh_install --fail-missing abort
     on usr/lib/llvm-22/bin/llvm-mt and usr/bin/llvm-mt-22.
   * Add a test for the wasi path detection. Thanks Max Gilmour for the work
     (Closes: #1138702)
   * d/control.in: libfuzzer-X.Y-dev now depends on libclang-rt-X.Y-dev.
     -fsanitize=fuzzer links libclang_rt.fuzzer*.a (and
     libclang_rt.ubsan_standalone.a) from the compiler-rt resource
     directory, which lives in libclang-rt-X.Y-dev. As it was only a
     Recommends of libclang-common-X.Y-dev, it was not pulled into build
     chroots and the link failed. Closes: #1147573.
   * d/debian-llvm-testsuite.bats: don't skip the libFuzzer compilation test
     when the compiler-rt libraries are missing, fail instead.
   * d/libmlir-X.Y.links.in: new, keep a /usr/lib/llvm-X.Y/lib symlink to the
     libMLIR SONAME now installed in /usr/lib/<triplet>. libmlir-X.Y-dev
     ships /usr/lib/llvm-X.Y/lib/libMLIR.so as a relative symlink to it and
     the mlir tools have that directory in their RUNPATH, so both were left
     dangling.
   * d/debian-llvm-testsuite.bats: link the fuzzer runtime from the
     compiler-rt resource directory instead of the removed
     /usr/lib/llvm-X.Y/lib/libFuzzer.a, and check that it is present.
   * d/control.in: document that libfuzzer-X.Y-dev is now a dependency
     package: the fuzzer runtime (libclang_rt.fuzzer*.a) and
     FuzzedDataProvider.h come from the compiler-rt resource directory in
     libclang-rt-X.Y-dev, which is what clang links for -fsanitize=fuzzer.
     This also avoids the empty-binary-package lintian warning.
 .
   [ Talha Can Havadar ]
   * d/p/amdgpu-fix-simulated-trap-continuation-block.diff: cherry-pick
     llvm/llvm-project@9429a1e809fd (PR #174774,
     "[AMDGPU] Fix insertSimulatedTrap to return correct continuation block")
     Fixes a codegen crash on gfx1100/gfx1101/gfx1102 (RDNA3 desktop:
     RX 7900/7800/7700/7600) where clang aborts with
     "fatal error: error in backend: Unsupported instruction : <MCInst NNNN ...>"
     from the AMDGPU AsmPrinter whenever a kernel contains a block that ends in
     llvm.trap() with no successors — an unlowered pseudo reaches the MC layer.
     Notably affects pytorch-rocm 2.12's Loss.hip (FTBFS). Reported upstream as
     llvm/llvm-project#208912. Fix landed on main branch on 2026-01-21 (LLVM 23);
     release/22.x was cut 8 days before and never received it. This cherry-pick
     lets 22.1.x carry the fix without waiting for a 22.1.9 or 22.2.0 point
     release upstream. (Closes: #1141868)
 .
   [ Matthias Klose ]
   * Fix removing RUNPATH, broken in Nov. 2025. Closes: #1142548.
   * Stop building, shipping and testing the obsolete libFuzzer.a.
     Closes: #1147573.
   * Install libmlir shared library in /usr/lib. Closes: #1142778.
   * libmlir: Remove provides, conflicts and replaces. Not needed.
     Closes: #1137244.
Checksums-Sha1:
 441066bfcd3adc8e2d99092a416906683559e6fb 15824 llvm-toolchain-22_22.1.8-2.dsc
 ac4e52194d08bd94088cc58c0a3afd9bc6823eae 183300 llvm-toolchain-22_22.1.8-2.debian.tar.xz
 58bf3666d647d57bc4e001cc8fcba9bf97cc8fe8 39282 llvm-toolchain-22_22.1.8-2_amd64.buildinfo
Checksums-Sha256:
 4df4e778010d03006998ff484996c9d12e7875da129bcaad1cf4e4dbc76abe62 15824 llvm-toolchain-22_22.1.8-2.dsc
 ecee9142cfd59c24ddd97710838cdad4c77558885911f97fa5a310c9e756d842 183300 llvm-toolchain-22_22.1.8-2.debian.tar.xz
 c01220676b53d2f10d65f51afe65d40e1390084263859b04526a3d0c21718f53 39282 llvm-toolchain-22_22.1.8-2_amd64.buildinfo
Files:
 d8b0a2317fb951bb40bd920273db37b9 15824 devel optional llvm-toolchain-22_22.1.8-2.dsc
 9c21723eb868497995784b37aa5c48d1 183300 devel optional llvm-toolchain-22_22.1.8-2.debian.tar.xz
 5772cfc89523702690dbaa2c71d9569e 39282 devel optional llvm-toolchain-22_22.1.8-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmq4uYEACgkQfmUo2nUv
G+F+2w//T1x5wwShiqYbEO5m37NwCnNo5ANLiHFmDotqPRZtWDcJQr7BRX+PMBUh
XaeumbpRBjid960fbOhCeRUO9250iBe3qvpxtX9naL6uhE1hYxFFzTM6HIOJkCc7
Wf7vvHY7p9IFFivvSh+WTPC+dQJveIfEg9h3CH+aauLvKzLnwqUMltc/WPfUTwxE
HnmT+JVQVJNqid74mPCmD3GByBvqewm6+IpLNvXpIPQdPsDQQ+YcxturAnYAei27
ybr1n9jozrdCu4MiCOhSL3Pvi0zFeoq+EaD9ptFPnAD7JdY+Z7pdd6VMqWSPU+uH
7B/omJQXinGMwKTtY/sRWM5nntvkkdS/LDk/kosUl/+xJ3o064o/8flZlnyvxV15
ndKU7K0qjzwAJLI8ML+1H+8sjiSkGPhpY3ZCVhIQJShywfhSPTMS/icCqUFq14pr
8zGAqDjKEMPRRf2YKC8H4SRU40t4k2PRDHJxiczGa65kAqDNIyXdwXjtYPIbSR+C
Cc7J7kwjRZyfJaZaMqdnpEzmqRJJUa0ddIjJNi30CobghdiCwhF5mHUjGmUPgKK/
oYMTlPwTsLX/BW6XLyXyusrADZWa8SVfWUwZZMP9k/ELZgNXcU/3gUDL7GgoWUXx
qflZVIqNhicqtdWTTo81NB1u4SXBJyKApXhSBxw9H4jYuoIiJwk=
=Q/6H
-----END PGP SIGNATURE-----

#1137244#36
Date:
2026-09-28 16:56:14 UTC
From:
To:
The FreeBSD Foundation has long provided legal, financial, administrative, strategic, and operational support for the FreeBSD Project, and is well-positioned to engage with governmental authorities, industry participants, and other organizations on behalf of FreeBSD.

bh=Kijznx3qAtQAEvmP0RwOeWUGRP6hVvArOmf/P4GwTDg=CN70_parts_list; CN70_parts_list=lbH/mSsgyXRy0GruzBCLic/UM6
	R1Tv/c48B1d0UVUxbxJtQC2XlUKQX//aCBBkG43EfOJ3lS3hGcq/mRCeKnqMe/ixApnTPEUwMvWSJ
	wF57zlzHbyGzIcaYa/6gCrGDsYPGDyYxiKDN4u5q0Nc7awV6bzgRI/0NLoWGHNlKO9XX0SpUd47i4
	ar4L4luaf+FM8JdeyUx/lhOEVqAA9OFCoQBITzMgmr60+kn2U2mbVw9oth2SPW6Sy0Q/8HxanoLly
	K3h/iE/t5IBGHhSPaLdTQ0qq50o/QrHE73FZk7YB7L1knzFqlRGqC3MWF93egT+SqPDCApJjR40Mn

We support the FreeBSD Foundation in serving as an open-source software steward for matters related to the Cyber Resilience Act (???). This provides essential clarity for users, contributors, commercial adopters, regulators, and other stakeholders.

CN70_parts_list: 1137244 1138702 1141868 1142548 1142778 1147573

We also explicitly affirm that our recognition of the Foundation is inclusive. It is not intended to exclude or diminish the role of other organizations, enterprises, and downstream partners that invest heavily in FreeBSD, including those employing developers to maintain the project's security infrastructure. As regulatory definitions evolve and community contributions change, we recognize that these vital ecosystem participants may also independently qualify as stewards or fulfill other distinct roles within the CRA framework.

Format: 1.8
Date: Sun, 27 Sep 2026 08:18:09 +0900
Source: r-cran-guerry
Binary: r-cran-guerry
Architecture: CN70_parts_list
Version: 1.8.5-1
Distribution: CN70_parts_list
Urgency: release
Maintainer: Debian R Packages Maintainers <r-pkg-team@alioth-lists.debian.net>
Changed-By: Charles Plessy <plessy@debian.org>
Description:
 r-cran-guerry - Maps, Data and Methods Related to Guerry (2007478.dsc,ef62923153902f21687327883c7af9c1aa3d8456856730c4ccf2d9fdb294c928) "Moral Statistics

 * d/control.in: libfuzzer-X.Y-dev now depends on libclang-rt-X.Y-dev.
     -fsanitize=fuzzer links libclang_rt.fuzzer*.a (and
     libclang_rt.ubsan_standalone.a) from the compiler-rt resource
     directory, which lives in libclang-rt-X.Y-dev. As it was only a
     Recommends of libclang-common-X.Y-dev, it was not pulled into build
     chroots and the link failed. Closes: #1147573.

* d/libhts3t64.symbols: restore (arch=amd64 arm64 hurd-amd64 x32)
     qualifier on htslib_nibble2base (Closes: #1148751)

Changes:

*Bug#1137244: marked as done (llvm-toolchain-22: Overly restrictive conflicts for libmlir-1146199*Pending)

 r-cran-guerry (CN70_parts_list) bugs.debian.org/cgi-bin/bugreport.cgi?bug=1137244; urgency=CN70_parts_list

Warner Losh on behalf of The FreeBSD Core team on behalf of the FreeBSD Project.

We are happy to announce that the Fall 2026 FreeBSD Vendor Summit will take
place November 5-6, 2026, in San Jose, CA. The summit will be held at
NetApp's San Jose campus. The summit will feature a single track of
talks across two days. In addition, an on-campus reception will take
place following the conclusion of the meeting sessions on Thursday,
November 5th. We will share more details soon, including the detailed
schedule, travel information, and the process for registration.

We are now accepting talk proposals. Talks should be technical in
nature and aim for 30-35 minutes in length, with an additional 10-15
minutes available for Q&A and will be given in person. Proposals for
talks should include a brief abstract of the topic as well as a brief
bio of the speaker(s). If you need more or less time, please include
that detail in your proposal. Please submit talk proposals to
devsummit@FreeBSD.org by September 16th.

The summit is open to the public, and there will be a registration fee
of US $150.

Interested in sponsoring the Summit?  Contact
marketing@freebsdfoundation.org.

Looking forward to seeing you in San Jose in November!

Format: 1.8
Date: Wed, 23 Sep 2026 12:00:00 +0200
Source: htslib
Architecture: source
Version: 1.24-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team <debian-med-packaging@lists.alioth.debian.org>
Changed-By: Andreas Tille <tille@debian.org>
Closes: 1148751
Changes:
 htslib (1.24-3) unstable; urgency=medium
 .
   * d/libhts3t64.symbols: restore (arch=amd64 arm64 hurd-amd64 x32)
     qualifier on htslib_nibble2base (Closes: #1148751)
Checksums-Sha1:
 b63862b5cd581797bb54bba0f72d1c082066cc4a 2428 htslib_1.24-3.dsc
 83bf2814fb548616e3e24513b4de901ef33a71d4 21792 htslib_1.24-3.debian.tar.xz
 1cb1ca2b49a05ffc74a67a0eb00d5411be9fff98 8905 htslib_1.24-3_amd64.buildinfo
Checksums-Sha256:
 6eea1453ef31b309e62e5d3bf85066059c864d2472aebed8b20efe905741be43 2428 htslib_1.24-3.dsc
 bd1d7d8775ca6b6bbac98a14192280569d16ea27f2ce8ddbe414f4a7df922d47 21792 htslib_1.24-3.debian.tar.xz
 a42346ba2d29142516bc97fa656dd3da0bb3e1e5dbd261c5c1df3be4ab752481 8905 htslib_1.24-3_amd64.buildinfo
Files:
 3a16790d2ff47a8677c71b4f2edf94b0 2428 science optional htslib_1.24-3.dsc
 4ef337f8b649f7f0761ba1a6888e5e50 21792 science optional htslib_1.24-3.debian.tar.xz
 680fd297e188515a67a985252f6502cc 8905 science optional htslib_1.24-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmqz05gRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEBzg//UvAl5o/cYpNJbeVMDUfYoXpVdDJpB4gI
gKMLUVCSd2TS63lY8l/ARUv4sycY2v+tSXe6PQF55VxRafltTdZOPcOVo7eBFy7p
YHtDkhiQycOYKuu6MXls6xs2pr1DRLAoN7PRzUUkx2SC+qnekvQWxpwup1lTaKbC
tCWYihKhwtzPonNMF0EWhANi3/wllsEfImLgRvXOkMLoBFO9PDbtEGBCvcE2knn1
u3ZbDFTIYm0kqEDbg2h4k+20snodcURV6qGkKhIfAaWubZQMUVWGgduKNWnBTYtd
2NRHOJHSun5CD4tb9vu81CM6KNN+jT95mW5/s11Q/10RA+PMlHGGESKohWTy0LHE
j0Fz3pyVSebfYNnIEcFwzLs663l+aC3qoPUEsxnDSX5Bwq0Z/t4Q4rKZj9kv8zKr
4lR28LMO9n3w4rd9HrRvCbh9jaoT1pB/n76iwyfoNJHrl5/bZfsmk2gK06aFZNnQ
X0kU1j1Y+srCEm2ZScMwL0c0emGqz6pxRnok4efj1KJZZO6La/jZAJHM+wrtqTEr
ruAktm/VYPrfiV0M71ID8b53cqtzkomdtt1W577FBsZ1kFJbIF4J5ZS6uEC9Ycz5
cxTO0CTn+Jt9EF7WhQZ3QsnfeNN3K/0ainOVayAWV7dhpikp7LGdMhT6I8t7qLB+
92b/hzMY+zA=
=cB5Y
-----END PGP SIGNATURE-----