<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">Le 25/04/2025 à 12:03, Simon McVittie a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:aAtd2apLSdqqMvw-@remnant.pseudorandom.co.uk">
<pre wrap="" class="moz-quote-pre">Control: tags 1100481 + pending
On Mon, 21 Apr 2025 at 15:18:49 +0200, Chris Hofstaedtler wrote:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">On Fri, Mar 14, 2025 at 12:53:26PM +0200, Adrian Bunk wrote:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">On Sat, Dec 31, 2022 at 07:24:51PM +0100, Jakub Wilk wrote:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">This package has "libunwind-dev" in Provides, but it's not fully compatible
with the real libunwind-dev package. Notably, it lacks the pkg-config file,
and there are quite a few users of that:
<a class="moz-txt-link-freetext" href="https://codesearch.debian.net/search?q=%5CbPKG_CHECK_MODULES%5Cb.%2A%5Cblibunwind%5Cb">https://codesearch.debian.net/search?q=%5CbPKG_CHECK_MODULES%5Cb.%2A%5Cblibunwind%5Cb</a>
...
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
This is a constant source of confusion and FTBFS, e.g.:
<a class="moz-txt-link-freetext" href="https://buildd.debian.org/status/logs.php?pkg=frr&ver=10.2.1-4">https://buildd.debian.org/status/logs.php?pkg=frr&ver=10.2.1-4</a>
Please remove the Provides: libunwind-dev before trixie.
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
Will this happen for trixie? If not, is this bug (and #1027451,
#1100481, #1100483) really release-critical?
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
I see that commit 1585b88b "Remove "Provides: libunwind-dev"
(Closes: #1100481)" has been staged in llvm-toolchain git in the 18
branch, so I'm marking that bug as pending. Is the intention that its
fix will be uploaded before trixie?
</pre>
</blockquote>
<p>yeah, i was waiting to have more contents before upload but I
will just go ahead today.</p>
<blockquote type="cite"
cite="mid:aAtd2apLSdqqMvw-@remnant.pseudorandom.co.uk">
<pre wrap="" class="moz-quote-pre">
The 19 branch doesn't appear to have an equivalent commit, which would
resolve #1100482. If llvm-toolchain-19 might also need an upload for
#1095866, perhaps that would be a good opportunity to fix #1100482 in
the same upload?
</pre>
</blockquote>
sure
<blockquote type="cite"
cite="mid:aAtd2apLSdqqMvw-@remnant.pseudorandom.co.uk">
<pre wrap="" class="moz-quote-pre">
#1027451 is the equivalent bug for llvm-toolchain-17, which the
maintainers and release team are trying to remove (#1081250) in order to
reduce proliferation of versions, but that removal seems to be blocked
by reinstating the AMD gcn offload target (#1092643) so that
amdgcn-tools, which is required by gcc-13, can upgrade to LLVM 18 or 19
(#1084066). So fixing this in the 17 branch as well might be best.
</pre>
</blockquote>
<p>ok, i will have a look to fix #<span
style="white-space: pre-wrap">1092643
</span></p>
<p>S</p>
<p><br>
<span style="white-space: pre-wrap"></span></p>
</body>
</html>