[05:22] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (disco-proposed) [1.178.2]
[05:26] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (cosmic-proposed) [1.175.6]
[05:28] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (bionic-proposed) [1.173.8]
[08:38] <rbalint> rbasak could you please release cosmic's initramfs-tools today? there is a new one in unapproved and i'd also like to piggyback on it with LP: #1814355
[08:38] <ubot5> Launchpad bug 1814355 in snapd (Ubuntu) "snapd remove /usr/local/bin from the PATH for all systemd unit (bionic SRU regression)" [High,Confirmed] https://launchpad.net/bugs/1814355
[08:40] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (cosmic-proposed/main) [0.131ubuntu15.2 => 0.131ubuntu15.3] (core)
[08:46] <xnox> https://launchpad.net/ubuntu/cosmic/+queue?queue_state=1&queue_text=initramfs-tools
[08:46] <xnox> the one from 6 minutes ago, superseeds the unapproved upload from 11th of june
[09:02] <rbasak> rbalint: I'm out this morning. I'll try and look this afternoon for you.
[09:10] <rbalint> rbasak, thanks!
=== pieq_ is now known as pieq
[10:25] -queuebot:#ubuntu-release- Unapproved: linux-signed-hwe-edge (bionic-proposed/main) [5.0.0-19.20~18.04.1 => 5.0.0-19.20~18.04.1] (kernel) (sync)
[10:31] -queuebot:#ubuntu-release- Unapproved: linux-signed-hwe-edge (bionic-proposed/main) [5.0.0-19.20~18.04.1 => 5.0.0-19.20~18.04.1] (kernel) (sync)
[10:39] -queuebot:#ubuntu-release- Unapproved: rejected linux-signed-hwe-edge [sync] (bionic-proposed) [5.0.0-19.20~18.04.1]
[10:39] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed-hwe-edge [sync] (bionic-proposed) [5.0.0-19.20~18.04.1]
[11:04] -queuebot:#ubuntu-release- Unapproved: linux-signed-hwe-edge (bionic-proposed/main) [5.0.0-19.20~18.04.1 => 5.0.0-19.20~18.04.1] (kernel) (sync)
[11:05] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed-hwe-edge [sync] (bionic-proposed) [5.0.0-19.20~18.04.1]
[11:17] -queuebot:#ubuntu-release- Unapproved: linux-signed-hwe-edge (bionic-security/main) [5.0.0-19.20~18.04.1 => 5.0.0-19.20~18.04.1] (kernel) (sync)
[11:17] -queuebot:#ubuntu-release- Unapproved: linux-signed-hwe-edge (bionic-updates/main) [5.0.0-19.20~18.04.1 => 5.0.0-19.20~18.04.1] (kernel) (sync)
[11:34] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed-hwe-edge [sync] (bionic-security) [5.0.0-19.20~18.04.1]
[11:34] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed-hwe-edge [sync] (bionic-updates) [5.0.0-19.20~18.04.1]
[11:41] -queuebot:#ubuntu-release- Unapproved: linux-signed (disco-security/main) [5.0.0-20.21 => 5.0.0-19.20] (core, kernel) (sync)
[11:41] -queuebot:#ubuntu-release- Unapproved: linux-signed (disco-updates/main) [5.0.0-20.21 => 5.0.0-19.20] (core, kernel) (sync)
[11:45] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed [sync] (disco-security) [5.0.0-19.20]
[11:45] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed [sync] (disco-updates) [5.0.0-19.20]
=== jdstrand_ is now known as jdstrand
[11:47] -queuebot:#ubuntu-release- New binary: jsonnet [s390x] (eoan-proposed/universe) [0.13.0+ds-1ubuntu1] (no packageset)
[11:49] -queuebot:#ubuntu-release- New binary: jsonnet [amd64] (eoan-proposed/universe) [0.13.0+ds-1ubuntu1] (no packageset)
[11:49] -queuebot:#ubuntu-release- New binary: jsonnet [ppc64el] (eoan-proposed/universe) [0.13.0+ds-1ubuntu1] (no packageset)
[11:49] -queuebot:#ubuntu-release- New binary: jsonnet [i386] (eoan-proposed/universe) [0.13.0+ds-1ubuntu1] (no packageset)
[11:52] -queuebot:#ubuntu-release- New binary: jsonnet [armhf] (eoan-proposed/universe) [0.13.0+ds-1ubuntu1] (no packageset)
[11:53] -queuebot:#ubuntu-release- New binary: jsonnet [arm64] (eoan-proposed/universe) [0.13.0+ds-1ubuntu1] (no packageset)
[12:57] -queuebot:#ubuntu-release- Unapproved: gnome-control-center (disco-proposed/main) [1:3.32.2-0ubuntu1 => 1:3.32.2-0ubuntu1.1] (ubuntu-desktop)
[13:04] -queuebot:#ubuntu-release- New binary: linux-signed-oem-osp1 [amd64] (bionic-proposed/universe) [5.0.0-1012.13] (no packageset)
[13:07] -queuebot:#ubuntu-release- New: accepted linux-signed-oem-osp1 [amd64] (bionic-proposed) [5.0.0-1012.13]
[13:09] -queuebot:#ubuntu-release- Unapproved: systemd (xenial-proposed/main) [229-4ubuntu21.21 => 229-4ubuntu21.22] (core)
[13:10] <ddstreet> ubuntu-sru team, please reject my systemd upload in xenial unapproved queue from 1 month ago, i just re-uploaded with an additional patch from rbalint
[13:15] -queuebot:#ubuntu-release- Packageset: Removed gnome-control-center from desktop-core in disco
[13:15] -queuebot:#ubuntu-release- Packageset: Added gnome-control-center to ubuntu-desktop in disco
[13:44] -queuebot:#ubuntu-release- Unapproved: rejected systemd [source] (xenial-proposed) [229-4ubuntu21.22]
[13:44] <apw> ddstreet, ^
[14:07] <ddstreet> apw thanks, hopefully new uplaod won't be in unapproved for a month :)
[14:09] <apw> changing systemd is always mentally challenging
[14:09] <apw> its unreliable enough as it is
[15:35] -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.39.2 => 2.39.2ubuntu0.1] (desktop-core, ubuntu-server)
[15:47] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.39.2ubuntu0.1]
[16:42] <tsimonq2> [2019-06-26 16:36:21] lb_chroot_hooks
[16:42] <tsimonq2> P: Begin executing hooks...
[16:42] <tsimonq2> ...
[16:42] <tsimonq2> AttributeError: 'Package' object has no attribute 'section'
[16:43] <tsimonq2> Ooh, fun.
[16:43] <tsimonq2> Who broke the archive? :P
[16:57]  * tsimonq2 wonders if this is an apt issue.
[17:21] -queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (bionic-proposed/main) [4.15.0-1045.50] (kernel)
[17:51] <tsimonq2> It doesn't seem like it's an apt issue; reverting to an older version of apt in a PPA and then doing a test livefs build shows the same error.
[17:51] <tsimonq2> (known good version of apt, that is)
=== mapreri_ is now known as mapreri
[18:18] <tsimonq2> Aha! https://launchpad.net/ubuntu/+source/python-apt/1.9.0 says "- Remove Package.section attributes" which is relevant because "pkg       is the python-apt Package object for this package"
[18:24] <tsimonq2> vorlon, juliank: The latest update to python-apt broke apt-xapian-index by removing the (admittedly legacy) Package.section attribute. This is a problem because it's included by default on Lubuntu images (and probably more), and is causing the ISO build to fail. I see there being two potential solutions here: 1) Fix the apt-xapian-index build in eoan-proposed and fix apt-xapian-index itself
[18:24] <tsimonq2> (either by doing Ubuntu-specific changes or via Debian in the bug I'm about to file); 2) Revert the commit removing those attributes in python-apt for now until 1) is in place.
[18:25] <tsimonq2> 2) is easy for now, but I don't want to touch python-apt without talking to juliank first.
[18:29] <tsimonq2> I'm absolutely exploring why this wasn't caught during p-m.
[18:30] <tsimonq2> That will be another bug I file in Debian, because this should have been caught earlier.
[18:34] <tsimonq2> Oh, it's orphaned. Coooool.
[19:00] <tsimonq2> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931133 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931132
[19:00] <ubot5> Debian bug 931133 in apt-xapian-index "apt-xapian-index: unusable after recent python-apt update due to usage of deprecated Package.section attribute" [Important,Open]
[19:00] <ubot5> Debian bug 931132 in apt-xapian-index "apt-xapian-index: please enable autopkgtests" [Important,Open]
[19:05] <teward> tsimonq2: > orphaned since 1243 days. < yeah probably not going to get fixed heh
[19:06] <tsimonq2> teward: Become a DD and then adopt it. :P
[19:06] <tsimonq2> Or a DM.
[19:06] <teward> tsimonq2: no thanks I don't want it :P
[19:28] <Eickmeyer> Can anybody shed light on why Studio's build failed? https://launchpadlibrarian.net/430720022/buildlog_ubuntu_eoan_amd64_ubuntustudio_BUILDING.txt.gz
[19:28] <Eickmeyer> I don't know if it's related to tsimonq2's apt-xapian-index bug or not.
[19:29] <tsimonq2> Eickmeyer: Yes it is.
[19:29] <Eickmeyer> tsimonq2: kthx. :)
[19:30] <wxl> ah they are similar with
[19:30] <wxl> AttributeError: 'Package' object has no attribute 'section'
[19:34] -queuebot:#ubuntu-release- New binary: linux-signed-gcp-edge [amd64] (bionic-proposed/main) [4.18.0-1015.16~18.04.1] (kernel)
[19:34] <wxl> https://salsa.debian.org/apt-team/python-apt/commit/fedd51be48be53d00d386c45eab8f63f462db202#faf51da27adfc87e2950af44dc159112540aed75_0_10
[19:34] <wxl> * The `section` attribute has been removed from :class:`apt_pkg.Package`
[19:34] <wxl>   and :class:`apt.package.Package`
[19:36] <tsimonq2> Yeah, it's the same bug.
[19:53] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp-edge [amd64] (bionic-proposed) [4.18.0-1015.16~18.04.1]
[19:53] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1045.50]
[20:09] <juliank> tsimonq2: We need to fix reverse depends. The python-apt change cannot be reverted, it is following apt's removal of that field
[20:09] <juliank> Eickmeyer: I fixed that yesterday, but livecd-rootfs got stuck in proposed and pyython-apt migrated
[20:09] <tsimonq2> juliank: ack
[20:11] <juliank> If somebody could hint that ubuntu-image failure that's blocking livecd-rootfs, image building will be back on
[20:12] <juliank> I don't have the repo on this machine, and finding it, branching it, and pushing it back seems like it's a lot of work right now :)
[20:14] <Eickmeyer> juliank: ack, but can't do the hint.
[20:14] <juliank> tsimonq2: I filed the other apt 1.9 migration bugs as normal in Debian, not important, as the move to unstable is still way off; I also attach patches to them all :)
[20:15] <juliank> But maybe I missed some
[20:16] <tsimonq2> juliank: ok, feel free to adjust my bug reports :)
[20:17] <juliank> tsimonq2: If you see other such issues and forward them, it'd be nice if you could User: deity@lists.debian.org\nUsertags: apt-1.9.0 :)
[20:18] <juliank> tsimonq2: I'll have a look at apt-xapian-index shortly and see if I can add static typing information, that could cover any future API breaks at least - though not sure when to run them yet, gotta work on a solution for automatic python type testing, as there are regressions due to mypy updates and semantic changes all the time :/
[20:18] <tsimonq2> juliank: ack, thanks
[20:19] <juliank> I added the usertag to your bug btw
[20:19] <juliank> tracking list: https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=deity@lists.debian.org;tag=apt-1.9.0
[20:21] <tsimonq2> Sweet
[20:21] <juliank> So, like PEP8 tests we don't want to run mypy tests during autopkgtests or build I think, as it can regress due to changes in mypy
[20:22] <juliank> -> example: 0.710 complains if I re-define a variable with the same type, 0.670 does not
[20:22] <juliank> the question is: if we don't want to do this, how can we ensure to catch type failures?
[20:23] <juliank> OTOH, if the tests depend on mypy, a new mypy will only migrate after all tests are fixed, so maybe we are good?
[20:31] <juliank> oh ffs, ubuntu-image fails in different places in different runs
[20:35] <juliank> here's the hint: https://code.launchpad.net/~juliank/britney/hints-ubuntu--livecd-rootfs-2-598/+merge/369363
[20:36] <juliank> skiptested livecd-rootfs upload as the ubuntu-image failure is super weird and i did not want to badtest it
[20:36] <juliank> please merge!
[20:39]  * juliank also retried it a second time and hopes either thing happens before the next image build
=== msalvatore_ is now known as msalvatore