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

Bug#1002288: marked as done (mesa: migration to llvm-toolchain-13 looks viable at this time)

Your message dated Sat, 9 Apr 2022 15:58:51 +0300
with message-id <d004c75b-1694-2fc1-931e-35ea24e01ad1@debian.org>
and subject line Re: Bug#1002288: mesa: migration to llvm-toolchain-13 looks viable at this time
has caused the Debian Bug report #1002288,
regarding mesa: migration to llvm-toolchain-13 looks viable at this time
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.)


-- 
1002288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002288
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: mesa
Version: 21.2.6-1
Severity: normal

This bug also affects 21.3.0~rc5-1 in experimental.

Llvm-toolchain-13 now appears to be ready for armel, i386, mipsel,
mips64el, which were a problem the last time migration was attempted
(Bug #995835).

https://buildd.debian.org/status/package.php?p=llvm-toolchain-13

No urgency, or course, I'd just like to support Sylvestre's efforts to
reduce the number of LLVM versions in bookworm :-) Maybe building
against LLVM 13 can be enabled for 21.3 in experimental to test if
it's truly viable at this time?

Regards,
Nicholas

--- End Message ---
--- Begin Message --- 
Nicholas D Steeves kirjoitti 27.3.2022 klo 18.08:

Hi,

It looks like 21.3.7-1 in testing has been building with
llvm-toolchain-13 since January 2022, so maybe all the issues have been
resolved, and this bug can be closed?

Best,
Nicholas


indeed, I missed this bug when migrating to llvm-13.

--
t

--- End Message ---
Reply to: