| -queuebot:#ubuntu-release- New binary: nordugrid-arc [s390x] (plucky-proposed/universe) [6.21.1-2] (no packageset) | 00:09 | |
| -queuebot:#ubuntu-release- New binary: nordugrid-arc [armhf] (plucky-proposed/universe) [6.21.1-2] (no packageset) | 00:13 | |
| -queuebot:#ubuntu-release- New binary: nordugrid-arc [arm64] (plucky-proposed/universe) [6.21.1-2] (no packageset) | 00:20 | |
| -queuebot:#ubuntu-release- New binary: nordugrid-arc [amd64] (plucky-proposed/universe) [6.21.1-2] (no packageset) | 00:27 | |
| -queuebot:#ubuntu-release- New binary: nordugrid-arc [ppc64el] (plucky-proposed/universe) [6.21.1-2] (no packageset) | 00:33 | |
| -queuebot:#ubuntu-release- New binary: courier [amd64] (plucky-proposed/none) [1.3.13-1] (no packageset) | 05:42 | |
| -queuebot:#ubuntu-release- New binary: gnucash [amd64] (plucky-proposed/none) [1:5.10-0.1] (no packageset) | 05:47 | |
| -queuebot:#ubuntu-release- New binary: courier [s390x] (plucky-proposed/none) [1.3.13-1] (no packageset) | 05:50 | |
| -queuebot:#ubuntu-release- New binary: courier [armhf] (plucky-proposed/none) [1.3.13-1] (no packageset) | 05:54 | |
| -queuebot:#ubuntu-release- New binary: courier [arm64] (plucky-proposed/none) [1.3.13-1] (no packageset) | 05:55 | |
| -queuebot:#ubuntu-release- New binary: gnucash [s390x] (plucky-proposed/none) [1:5.10-0.1] (no packageset) | 05:57 | |
| -queuebot:#ubuntu-release- New binary: courier [ppc64el] (plucky-proposed/universe) [1.3.13-1] (no packageset) | 06:02 | |
| -queuebot:#ubuntu-release- New binary: gnucash [armhf] (plucky-proposed/universe) [1:5.10-0.1] (no packageset) | 06:04 | |
| -queuebot:#ubuntu-release- New binary: gnucash [arm64] (plucky-proposed/universe) [1:5.10-0.1] (no packageset) | 06:04 | |
| -queuebot:#ubuntu-release- New binary: gnucash [ppc64el] (plucky-proposed/universe) [1:5.10-0.1] (no packageset) | 06:17 | |
| -queuebot:#ubuntu-release- New binary: nordugrid-arc [riscv64] (plucky-proposed/universe) [6.21.1-2] (no packageset) | 07:00 | |
| -queuebot:#ubuntu-release- New: accepted nordugrid-arc [amd64] (plucky-proposed) [6.21.1-2] | 07:01 | |
| -queuebot:#ubuntu-release- New: accepted nordugrid-arc [armhf] (plucky-proposed) [6.21.1-2] | 07:01 | |
| -queuebot:#ubuntu-release- New: accepted nordugrid-arc [riscv64] (plucky-proposed) [6.21.1-2] | 07:01 | |
| -queuebot:#ubuntu-release- New: accepted nordugrid-arc [arm64] (plucky-proposed) [6.21.1-2] | 07:01 | |
| -queuebot:#ubuntu-release- New: accepted nordugrid-arc [s390x] (plucky-proposed) [6.21.1-2] | 07:01 | |
| -queuebot:#ubuntu-release- New: accepted nordugrid-arc [ppc64el] (plucky-proposed) [6.21.1-2] | 07:01 | |
| -queuebot:#ubuntu-release- New: accepted courier [amd64] (plucky-proposed) [1.3.13-1] | 07:02 | |
| -queuebot:#ubuntu-release- New: accepted courier [armhf] (plucky-proposed) [1.3.13-1] | 07:02 | |
| -queuebot:#ubuntu-release- New: accepted courier [s390x] (plucky-proposed) [1.3.13-1] | 07:02 | |
| -queuebot:#ubuntu-release- New: accepted gnucash [arm64] (plucky-proposed) [1:5.10-0.1] | 07:02 | |
| -queuebot:#ubuntu-release- New: accepted gnucash [ppc64el] (plucky-proposed) [1:5.10-0.1] | 07:02 | |
| -queuebot:#ubuntu-release- New: accepted courier [arm64] (plucky-proposed) [1.3.13-1] | 07:02 | |
| -queuebot:#ubuntu-release- New: accepted gnucash [amd64] (plucky-proposed) [1:5.10-0.1] | 07:02 | |
| -queuebot:#ubuntu-release- New: accepted gnucash [s390x] (plucky-proposed) [1:5.10-0.1] | 07:02 | |
| -queuebot:#ubuntu-release- New: accepted courier [ppc64el] (plucky-proposed) [1.3.13-1] | 07:02 | |
| -queuebot:#ubuntu-release- New: accepted gnucash [armhf] (plucky-proposed) [1:5.10-0.1] | 07:02 | |
| -queuebot:#ubuntu-release- New binary: barbican [amd64] (plucky-proposed/main) [2:19.0.0+git2025011509.55c758eb-0ubuntu1] (openstack) | 09:21 | |
| -queuebot:#ubuntu-release- New: accepted barbican [amd64] (plucky-proposed) [2:19.0.0+git2025011509.55c758eb-0ubuntu1] | 10:05 | |
| ricotz | hello, is there some progress to the autopkgtest infra working properly again? I am seeing things like "Cannot write: No space left on device" and random crashes | 11:52 |
|---|---|---|
| ricotz | I am mostly concerned about the libreoffice SRU for oracular which is blocked https://ubuntu-archive-team.ubuntu.com/proposed-migration/oracular/update_excuses.html#libreoffice | 11:53 |
| halves | hello ubuntu-archive, could someone please help me remove https://launchpad.net/ubuntu/+source/os-prober/1.83ubuntu2~ppa1 from plucky? that's a test upload meant for a PPA, apologies for not catching it in time. I've cancelled the builds, so it shouldn't have gone out to users at least | 12:39 |
| -queuebot:#ubuntu-release- Unapproved: backport-iwlwifi-dkms (oracular-proposed/universe) [1:0~89.12325-git36c5be1a-0ubuntu1 => 1:0~89.12325-git36c5be1a-0ubuntu2] (kernel-dkms) | 14:13 | |
| enr0n | halves: Since it's already in -proposed, I think the best action now is to just upload again with the chnage reverted | 14:13 |
| waveform | ubuntu-archive -- could someone have a look at the rpi-eeprom bug in LP: #2085903 ? Specifically, it splits out the firmware binaries into their own package (rpi-eeprom-firmware) which is now NEW. Looks like I forgot to subscribe ubuntu-archive to the bug, so the rpi-eeprom package is now in -proposed, but can't work until the rpi-eeprom-firmware package has gotten an AA's ack | 14:17 |
| -ubottu:#ubuntu-release- Launchpad bug 2085903 in rpi-eeprom (Ubuntu Oracular) "[SRU] Please merge rpi-eeprom 26" [High, Fix Committed] https://launchpad.net/bugs/2085903 | 14:17 | |
| -queuebot:#ubuntu-release- Unapproved: accepted backport-iwlwifi-dkms [source] (oracular-proposed) [1:0~89.12325-git36c5be1a-0ubuntu2] | 14:23 | |
| -queuebot:#ubuntu-release- Unapproved: accepted smifb2 [source] (noble-proposed) [2.2.6.3.gbbd2e82-1ubuntu0.2] | 14:24 | |
| === fuseteam1 is now known as fuseteam | ||
| === fuseteam1 is now known as fuseteam | ||
| schopin | waveform: it's been on my radar, I was hoping to use it as a case study for my education. | 16:05 |
| schopin | waveform: I'll try to track down a more experienced AA to guide me through its review. | 16:06 |
| schopin | waveform: I don't think you need to subscribe the team to packages going through NEW, though ;) | 16:10 |
| waveform | no? I thought it was generally desired for anything that required an explicit AA review? | 16:10 |
| waveform | (it's certainly been requested for source NEW packages in the past) | 16:11 |
| schopin | Really? | 16:11 |
| waveform | happy to be told otherwise, but that was my understanding (certainly on source NEW, but that's just the most common situation that's come up during patch pilot in the past) | 16:11 |
| * schopin goes looking for the documentation on brand new packages | 16:12 | |
| schopin | AFAICT nothing in the documentation (or my own experience) tells me to tag the bugs. | 16:18 |
| === fuseteam1 is now known as fuseteam | ||
| === mfo_ is now known as mfo | ||
| tsimonq2 | schopin: In Debian, ITPs are a hard requirement, as you probably already know. In Ubuntu I've always seen it as de facto best practice, but if I'm uploading to Debian and Ubuntu source NEW at the same time, I just keep the same Debian ITP bug. | 17:50 |
| tsimonq2 | It's useful if an AA needs to reject it. They can explain why in the bug report which already exists. | 17:51 |
| tsimonq2 | (It's veryveryrare that I see an Ubuntu AA reject something that a Debian FTP Master will accept.) | 17:51 |
| schopin | tsimonq2: I'm not saying you don't need a bug, I'm saying you don't need to subscribe the AA team to it. | 17:54 |
| tsimonq2 | Ahhh, okay. | 17:54 |
| tsimonq2 | schopin: If someone then responds with a good argument as to why the AA is wrong, or wants to keep the discussion going, again in the case of rejects, it does seem useful. | 17:54 |
| schopin | Well, sure, but that's after the reject, and assuming that the AA didn't leave a reply on the bug yelling at me because I did it wrong. | 17:57 |
| tsimonq2 | Since the benefits are pretty clear, do you see any obvious downsides to doing things that way? (Subscribing an AA?) | 17:58 |
| schopin | It clutters the happy path. | 17:58 |
| schopin | (and the list of bugs clamouring for AA love) | 17:59 |
| schopin | man getaddrinfo | 18:12 |
| schopin | whoops, -EWINDOW | 18:12 |
| * Eickmeyer points finger and laughs at schopin 😁 | 18:13 | |
| -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (noble-proposed/main) [1:24.04.23 => 1:24.04.24] (core) | 18:16 | |
| Eickmeyer | ubuntu-sru: ubuntustudio-default-settings for noble and oracular is past 7 days in -proposed and verified, and ubuntustudio-menu for oracular, noble, and jammy is 7 days in -proposed and verified. Move to -updates please? 🥺 | 18:21 |
| Eickmeyer | Also, that ubuntu-release-upgraderupload (thanks enr0n!) fixes jammy -> noble upgrades for Ubuntu Studio. | 18:23 |
| Eickmeyer | So, fairly urgent as we want people upgrading to noble as Ubuntu Studio 22.04 goes EOL relatively soon. | 18:24 |
| jbicha | tsimonq2: technically I wouldn't say ITPs are a hard requirement in Debian. ftpmasters appear to not need them. Perhaps it's "best practice". | 18:33 |
| tsimonq2 | jbicha: Huh. Might have to look more closely, then. My sponsors usually rejected without ITPs so I got into the habit. :) | 18:34 |
| jbicha | https://ftp-master.debian.org/new.html the Rust team in particular usually doesn't use them | 18:35 |
| tsimonq2 | That I could guess without looking. ;P | 18:35 |
| liushuyu | I can confirm Debian Rust team does not use ITP (and maybe so does JavaScript team) | 18:36 |
| tsimonq2 | I certainly won't be the one to ask debian-devel why. :P | 18:36 |
| jbicha | the Developers Reference said you should use an ITP but it's not as firm as Policy is | 18:38 |
| tsimonq2 | Yeah, then I suppose it's best practice. | 18:38 |
| liushuyu | I believe sticking to hard to ITP would be a huge disaster for Rust/JavaScript/Haskell sub-ecosystems in Debian | 18:40 |
| liushuyu | * too hard | 18:40 |
| liushuyu | (or any modern programming langauges that come with their own package managers) | 18:40 |
| mwhudson | halves: can i interest you in my dput wrapper that helps avoid that sort of thing? :) https://github.com/mwhudson/dput-wrap | 20:31 |
| halves | mwhudson yes! I normally have dput-ng profiles to catch this sort of thing, but it failed me this time (or rather, I failed myself by not propagating my config into a container). I'll take a look, thank you! | 21:19 |
| -queuebot:#ubuntu-release- New binary: plakativ [amd64] (plucky-proposed/universe) [0.5.2-3.1] (no packageset) | 23:36 | |
| -queuebot:#ubuntu-release- New binary: pysensibo [amd64] (plucky-proposed/none) [1.0.36-1] (no packageset) | 23:36 | |
| -queuebot:#ubuntu-release- New binary: python-plexwebsocket [amd64] (plucky-proposed/none) [0.0.14-1] (no packageset) | 23:36 | |
| -queuebot:#ubuntu-release- New binary: pycoolmasternet-async [amd64] (plucky-proposed/none) [0.2.0-1] (no packageset) | 23:36 | |
| -queuebot:#ubuntu-release- New binary: python-uvcclient [amd64] (plucky-proposed/none) [0.11.1-1] (no packageset) | 23:36 | |
| -queuebot:#ubuntu-release- New binary: python-opensky [amd64] (plucky-proposed/none) [1.0.1-1] (no packageset) | 23:36 | |
| -queuebot:#ubuntu-release- New binary: golang-ptutil [amd64] (plucky-proposed/none) [0.0~git20240710.6c4d8ed-1] (no packageset) | 23:37 | |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!