[Desktop-packages] [Bug 2057704] Re: jackd2 FTBFS due to waflib incompatible with Python 3.12
** 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 Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/2057704 Title: jackd2 FTBFS due to waflib incompatible with Python 3.12 Status in jackd2 package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2057704/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2057704] [NEW] jackd2 FTBFS due to waflib incompatible with Python 3.12
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 (liushuyu-011) Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/2057704 Title: jackd2 FTBFS due to waflib incompatible with Python 3.12 Status in jackd2 package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2057704/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049493] Re: Newer rustc version needed in jammy to build chromium updates
> 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 versions were used to compile Chromium/v8. I suggest building the Chromium using `ninja -v` to see the command line used to invoke the compiler. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2049493 Title: Newer rustc version needed in jammy to build chromium updates Status in chromium-browser package in Ubuntu: New Status in rustc package in Ubuntu: New Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049493] Re: Newer rustc version needed in jammy to build chromium updates
> 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 logic of a nightly compiler. The logic is disabled by default during the runtime when the compiler is in the stable channel. The reason why the variable is called "RUSTC_BOOTSTRAP" is that this functionality is usually required when building the next version of the Rust compiler. In this case, the Rust compiler needs to understand newer syntax unavailable in the previous version. I hope my explanation makes sense. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2049493 Title: Newer rustc version needed in jammy to build chromium updates Status in chromium-browser package in Ubuntu: New Status in rustc package in Ubuntu: New Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049493] Re: Newer rustc version needed in jammy to build chromium updates
> 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 originators; they are not to be found literally in the source files, and so I removed them iteratively with a ad-hoc (and rather embarrassing :p) You have an easy option here: There is a somewhat undocumented rustc feature where you could trick it into thinking it is a nightly compiler: just add `RUSTC_BOOTSTRAP: 1` under the `environment` section in your YAML file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2049493 Title: Newer rustc version needed in jammy to build chromium updates Status in chromium-browser package in Ubuntu: New Status in rustc package in Ubuntu: New Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017076] Re: default Chinese font is ugly
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 notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font is ugly Status in fontconfig package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
