[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1081535: marked as done (nmu: llvm-toolchain-15_1:15.0.6-4+b1)

Your message dated Wed, 16 Oct 2024 11:42:39 +0200
with message-id <d04c9be4-854f-49a7-ad4e-8f34d6da28d5@debian.org>
and subject line Re: Bug#1081535: nmu: llvm-toolchain-15_1:15.0.6-4+b1
has caused the Debian Bug report #1081535,
regarding nmu: llvm-toolchain-15_1:15.0.6-4+b1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1081535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081535
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: llvm-toolchain-15@packages.debian.org
Control: affects -1 + src:llvm-toolchain-15

Apparently, llvm-toolchain-15 in bookworm has been
bin-NMUed on mips64el the same way as it's been done
on all other architectures, while switching python3
defaults.

However, all other builds has made it into the archive,
while mips64el +b1 build has been rejected:

20230130081946|clean-queues|dak|move file to 
 morgue|Incoming/REJECT|libllvm15_15.0.6-4+b1_mips64el.deb|
 /srv/ftp-master.debian.org/morgue/queues/2023/01/30

It's been a few months before actual bookworm release.

So the current situation is that on mips64el, the version
of llvm-toolchain-15 is different from all the other
architectures.  This, at least, breaks multi-arch setups
where one of the architectures is mips64el.

Now, I'm not sure this the right bug form to use here,
since apparently the situation needs to be investigated
first, - what happened, why the bin-NMU has been rejected
in the first place, - and maybe that old build should
be re-uploaded.  But just in case, here it is:

nmu llvm-toolchain-15_1:15.0.6-4+b1 . mips64el . bookworm . -m "Rebuild with Python 3.11 as default"

Thanks,

/mjt

--- End Message ---
--- Begin Message --- 
Hi,

On 12/09/2024 15:58, Michael Tokarev wrote:

Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: llvm-toolchain-15@packages.debian.org
Control: affects -1 + src:llvm-toolchain-15

Apparently, llvm-toolchain-15 in bookworm has been
bin-NMUed on mips64el the same way as it's been done
on all other architectures, while switching python3
defaults.

However, all other builds has made it into the archive,
while mips64el +b1 build has been rejected:

20230130081946|clean-queues|dak|move file to
  morgue|Incoming/REJECT|libllvm15_15.0.6-4+b1_mips64el.deb|
  /srv/ftp-master.debian.org/morgue/queues/2023/01/30

It's been a few months before actual bookworm release.

So the current situation is that on mips64el, the version
of llvm-toolchain-15 is different from all the other
architectures.  This, at least, breaks multi-arch setups
where one of the architectures is mips64el.

Now, I'm not sure this the right bug form to use here,
since apparently the situation needs to be investigated
first, - what happened, why the bin-NMU has been rejected
in the first place, - and maybe that old build should
be re-uploaded.  But just in case, here it is:

nmu llvm-toolchain-15_1:15.0.6-4+b1 . mips64el . bookworm . -m "Rebuild with Python 3.11 as default"
Sorry for the delay. llvm-toolchain-15 has been removed from sid (and should be removed from testing soon), so this is no longer an issue. Closing. 

Cheers,
Emilio

--- End Message ---
Reply to: