** Merge proposal linked:
https://code.launchpad.net/~liushuyu-011/ubuntu/+source/jackd2/+git/jackd2/+merge/462267
** Changed in: jackd2 (Ubuntu)
Assignee: (unassigned) => Zixing Liu (liushuyu-011)
--
You received this bug notification because you are a member of Desktop
Packa
Public bug reported:
jackd2 is now unbuildable after Python 3.12 due to a very outdated WAF
build system inside.
The upstream has already fixed the issue in a recent commit, we need to
introduce this as a patch.
** Affects: jackd2 (Ubuntu)
Importance: Undecided
Assignee: Zixing Liu
> Actually that had failed on the 32-bit ARMv7. ARMv8 had failed because
of connection and I didn't care to trigger it again so I assumed it
would fail for the same reason.
I think it's very difficult to locate the issue, given this log.
The issue looks like two Rust toolchains of different
> I.e., is there an increased risk in using RUSTC_BOOTSTRAP in a
non-nightly compiler (the proposed case for us downstream) in comparison
to using the unstable options in a nightly compiler (what upstream does)?
Normally, it is not. Rust compilers, even in the stable channel, include
the complete
> Since I encountered the same error before and was able to overcome it
by manually removing all instances of that unstable option from the
build files, I'll try that strategy again. It is in general a boring
process because those options are generated during build and I couldn't
track down their
It looks like this issue mostly affects Snap apps.
Please see the font config debug output attached.
** Attachment added: "font config debug output"
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5665442/+files/fc-debug.log
--
You received this bug
6 matches
Mail list logo
