Re: Drop UBUNTU_CODENAME from /etc/os-release

On Tue, May 7, 2024 at 7:09 AM Benjamin Drung wrote: > > Hi everyone, > > Bug #1520154 introduced UBUNTU_CODENAME, but the final name that landed > in the os-release specification is VERSION_CODENAME. Ubuntu specifies > VERSION_CODENAME since Ubuntu 16.04 "xenial" (see bug #1598212). > > So let's

Re: Is there a good solution for this: release-upgrade with dependency moved to universe

Hi, > I guess something in do-release-upgrade could be run to, when encountering > such a situation, automatically select bin:samba-vfs-modules-extra for the > upgrade as well? Is it worth it? Is there a precedence for something like > this? And how would this be done in a more generic/general

Re: Migrating to deb822 sources on upgrade to Mantic

> As a part of the effort to use deb822 sources by default in Ubuntu[1], > on upgrades to Mantic, ubuntu-release-upgrader will migrate > /etc/apt/sources.list to /etc/apt/sources.list.d/ubuntu.sources, and > /etc/apt/sources.list.d/foo.list to > /etc/apt/sources.list.d/foo.sources. This change has

+1 maintenance report

Hi, I was on +1 maintenance this week. Given the US public holiday on Monday and some other distractions, I did not cover as much as I would have liked. My report is below. ### golang-github-form3tech-oss-jwt-go (LP: #2034390) This package is blocked by failing autopkgtests in

Migrating to deb822 sources on upgrade to Mantic

Hi, As a part of the effort to use deb822 sources by default in Ubuntu[1], on upgrades to Mantic, ubuntu-release-upgrader will migrate /etc/apt/sources.list to /etc/apt/sources.list.d/ubuntu.sources, and /etc/apt/sources.list.d/foo.list to /etc/apt/sources.list.d/foo.sources. This change has been

+1 maintenance report

Hi, Here is my report from +1 maintenance this week. I have annotated a few items at the bottom that require assistance. # git-credential-oauth The arm64 FTBFS appeared to be due to a network issue, so we retried the build and it succeeded. # nsscache (LP 2025178) The autopkgtests were

+1 maintenance report

Hi, Here is my +1 report from this week. ### zeal missing builds on several arches LP: #2006621 The latest Debian upload restricted the arches to where qtwebengine5 is available[1]. We need to remove zeal on those arches. The LP above is a removal request. ### openlibm FTBFS on armhf LP:

Re: PSA: autopkgtest environment behavior change

On Fri, Feb 3, 2023 at 2:38 PM Brian Murray wrote: > Finally, one benefit of this is that it became somewhat easier to find a > bunch of packages that would pass if given more memory. I've > investigated several of them and added them to 'big_packages'. If the > developers on +1 maintenance next

Re: +1 maintenance report

On Tue, Aug 16, 2022 at 7:13 PM Steve Langasek wrote: > > On Tue, Aug 16, 2022 at 11:29:34AM -0400, Nick Rosbrook wrote: > > > ## libxsmm FTBFS (https://pad.lv/1984111) > > > This FTBFS with an undefined reference to pthread_yield. Upstream > > already has fixes for

+1 maintenance report

Hi, I was on +1 last week. Due to some ISP issues on Friday, my report is delayed and there are a few loose ends in this report. ## hfst dep-wait on libfst-dev This package needs libfst-dev (>= 1.7.9) from src:openfst, which is not able to autosync from Debian because of Ubuntu delta. However,

+1 maintenance report

Hi, I was on +1 last week. Here is my report: ### python-llfuse autopkgtest regression on armhf This was caused by a 32-bit integer overflow in one of the tests. I changed the offending test value to fit in 32-bit, and forwarded the patch upstream. William sponsored an upload that resolved

Re: systemd-oomd issues on desktop

On Tue, Jun 14, 2022 at 4:54 AM Lukas Märdian wrote: > > Am 14.06.22 um 01:22 schrieb Nick Rosbrook: > > On Mon, Jun 13, 2022 at 8:19 AM Lukas Märdian wrote: > >> I wonder if we could use a more selective approach, though, using > >> "OOMScoreAdjust=" in

Re: systemd-oomd issues on desktop

On Mon, Jun 13, 2022 at 8:19 AM Lukas Märdian wrote: > I wonder if we could use a more selective approach, though, using > "OOMScoreAdjust=" in the systemd.exec environment (i.e. Gnome-Shell > launcher in Ubuntu's context, as sd-oomd is currently only enabled on > Ubuntu Desktop) [2], to reduce

systemd-oomd issues on desktop

Hi, During the 22.04 cycle, we enabled systemd-oomd [1] by default on desktop. Since then, there have been reports of systemd-oomd killing user applications too frequently (e.g. browsers, IDEs, and gnome-shell in some cases). In addition to a couple of LPs [2][3], I have heard these reports by

+1 maintenance report

Hi, I was on +1 last week. Here is my report: ### golang-github-valyala-fasthttp Regressed on s390x because 32-bit tests are running when they should not be. I submitted a fix on LP: #1965134 [1], and upstreamed the patch. William sponsored my patch, and the package has migrated. ###