-queuebot:#ubuntu-release- Packageset: Removed dvisvgm from i386-whitelist in focal | 01:07 | |
-queuebot:#ubuntu-release- Packageset: Removed ipython from i386-whitelist in focal | 01:07 | |
-queuebot:#ubuntu-release- Packageset: Removed ipython-genutils from i386-whitelist in focal | 01:07 | |
-queuebot:#ubuntu-release- Packageset: Removed lapack from i386-whitelist in focal | 01:07 | |
-queuebot:#ubuntu-release- Packageset: Removed matplotlib from i386-whitelist in focal | 01:07 | |
-queuebot:#ubuntu-release- Packageset: Removed numpy from i386-whitelist in focal | 01:07 | |
-queuebot:#ubuntu-release- Packageset: Removed pexpect from i386-whitelist in focal | 01:07 | |
-queuebot:#ubuntu-release- Packageset: Removed pickleshare from i386-whitelist in focal | 01:07 | |
-queuebot:#ubuntu-release- Packageset: Removed prompt-toolkit from i386-whitelist in focal | 01:07 | |
-queuebot:#ubuntu-release- Packageset: Removed ptyprocess from i386-whitelist in focal | 01:07 | |
-queuebot:#ubuntu-release- Packageset: Removed python-decorator from i386-whitelist in focal | 01:07 | |
-queuebot:#ubuntu-release- Packageset: Removed python-scipy from i386-whitelist in focal | 01:07 | |
-queuebot:#ubuntu-release- Packageset: Removed traitlets from i386-whitelist in focal | 01:07 | |
-queuebot:#ubuntu-release- Packageset: Added spirv-tools to i386-whitelist in focal | 01:37 | |
RAOF | Hm. I suspect that `sru-release --no-act` does not quite do nothing | 01:41 |
---|---|---|
-queuebot:#ubuntu-release- New binary: ruby2.7 [amd64] (focal-proposed/universe) [2.7.0-1] (no packageset) | 05:27 | |
-queuebot:#ubuntu-release- New binary: ruby2.7 [ppc64el] (focal-proposed/universe) [2.7.0-1] (no packageset) | 05:28 | |
-queuebot:#ubuntu-release- New: accepted backport-iwlwifi-dkms [source] (bionic-proposed) [7906-0ubuntu3~18.04.1] | 05:50 | |
-queuebot:#ubuntu-release- New binary: backport-iwlwifi-dkms [amd64] (bionic-proposed/none) [7906-0ubuntu3~18.04.1] (no packageset) | 05:52 | |
RikMills | is someone on the failing ISO builds? 2nd days they have failed now | 05:56 |
jibel | sforshee, ^ could it be the removal of signed kernel transitional packages? | 07:05 |
=== andrewc is now known as Guest92192 | ||
-queuebot:#ubuntu-release- Unapproved: accepted fwupd [amd64] (focal-proposed) [1.3.6-1] | 09:23 | |
-queuebot:#ubuntu-release- Unapproved: accepted fwupd [armhf] (focal-proposed) [1.3.6-1] | 09:23 | |
-queuebot:#ubuntu-release- Unapproved: accepted fwupd [arm64] (focal-proposed) [1.3.6-1] | 09:23 | |
-queuebot:#ubuntu-release- New: accepted ruby2.7 [amd64] (focal-proposed) [2.7.0-1] | 10:31 | |
-queuebot:#ubuntu-release- New: accepted ruby2.7 [ppc64el] (focal-proposed) [2.7.0-1] | 10:31 | |
-queuebot:#ubuntu-release- New: accepted linux-signed-oem-osp1 [amd64] (bionic-proposed) [5.0.0-1034.39] | 10:45 | |
=== andrewc is now known as Guest82295 | ||
=== andrewc is now known as Guest42948 | ||
-queuebot:#ubuntu-release- New binary: gdal [s390x] (focal-proposed/universe) [3.0.2+dfsg-1] (kubuntu) | 11:35 | |
-queuebot:#ubuntu-release- New binary: gdal [amd64] (focal-proposed/universe) [3.0.2+dfsg-1] (kubuntu) | 11:43 | |
-queuebot:#ubuntu-release- New binary: gdal [ppc64el] (focal-proposed/universe) [3.0.2+dfsg-1] (kubuntu) | 11:47 | |
-queuebot:#ubuntu-release- New binary: gdal [armhf] (focal-proposed/universe) [3.0.2+dfsg-1] (kubuntu) | 12:13 | |
-queuebot:#ubuntu-release- New binary: gdal [arm64] (focal-proposed/universe) [3.0.2+dfsg-1] (kubuntu) | 12:29 | |
Laney | can someone please reject the two oldest mutter uploads in eoan/proposed unapproved? | 13:33 |
apw | Laney, looking | 13:33 |
-queuebot:#ubuntu-release- Unapproved: mutter (eoan-proposed/main) [3.34.1+git20191107-1ubuntu1~19.10.1 => 3.34.3-1ubuntu1~19.10.1] (desktop-core, desktop-extra) | 13:33 | |
-queuebot:#ubuntu-release- Unapproved: rejected mutter [source] (eoan-proposed) [3.34.2-1ubuntu1~19.10.1] | 13:34 | |
-queuebot:#ubuntu-release- Unapproved: rejected mutter [source] (eoan-proposed) [3.34.3-1ubuntu1~19.10.1] | 13:34 | |
apw | Laney, ^ | 13:34 |
Laney | apw: merci! | 13:35 |
-queuebot:#ubuntu-release- New: accepted gdal [amd64] (focal-proposed) [3.0.2+dfsg-1] | 14:00 | |
-queuebot:#ubuntu-release- New: accepted gdal [armhf] (focal-proposed) [3.0.2+dfsg-1] | 14:00 | |
-queuebot:#ubuntu-release- New: accepted gdal [s390x] (focal-proposed) [3.0.2+dfsg-1] | 14:00 | |
-queuebot:#ubuntu-release- New: accepted gdal [arm64] (focal-proposed) [3.0.2+dfsg-1] | 14:00 | |
-queuebot:#ubuntu-release- New: accepted gdal [ppc64el] (focal-proposed) [3.0.2+dfsg-1] | 14:00 | |
=== andrewc is now known as Guest31120 | ||
-queuebot:#ubuntu-release- Unapproved: yaru-theme (eoan-proposed/main) [19.10.4 => 19.10.5] (desktop-core) | 14:41 | |
-queuebot:#ubuntu-release- Unapproved: gnome-shell (eoan-proposed/main) [3.34.1+git20191024-1ubuntu1~19.10.1 => 3.34.3-1ubuntu1~19.10.1] (desktop-extra, mozilla, ubuntu-desktop) | 14:42 | |
Laney | I'd ideally like to copy forward that yaru-theme with binaries, would be nice if someone could review it with that in mind | 14:42 |
-queuebot:#ubuntu-release- Unapproved: bluez (eoan-proposed/main) [5.50-0ubuntu4 => 5.50-0ubuntu5] (ubuntu-desktop) | 14:58 | |
-queuebot:#ubuntu-release- Unapproved: bluez (bionic-proposed/main) [5.48-0ubuntu3.2 => 5.48-0ubuntu3.3] (ubuntu-desktop) | 14:59 | |
-queuebot:#ubuntu-release- Unapproved: accepted pulseaudio [source] (eoan-proposed) [1:13.0-1ubuntu1.1] | 15:19 | |
LocutusOfBorg | xnox, can I reupload boost with the fixes in -17? | 16:08 |
LocutusOfBorg | I have the upload ready to go | 16:09 |
xnox | LocutusOfBorg: please do | 16:13 |
xnox | LocutusOfBorg: but yeah, i haven't refactored the numpy stuff to make it "syncable" | 16:13 |
xnox | yet | 16:13 |
LocutusOfBorg | https://launchpad.net/ubuntu/+source/boost1.67/1.67.0-17ubuntu1 | 16:23 |
vorlon | doko: removing python-bzrlib made juju-deployer uninstallable, it still depends on it; and that's why the autopkgtests are failing | 16:32 |
doko | ugh, but how to get bzr migrate then? | 16:33 |
vorlon | doko: well since the binary is gone, juju-deployer test is clearly broken in release, so I'm badtesting that. And I've retried mercurial/s390x; and then we should figure out why only linux-kvm autopkgtests are not being ignored | 16:36 |
vorlon | oh, I guess that's linux + linux-kvm | 16:36 |
vorlon | doko: but I was giving you a heads up that there's a new uninstallable :) | 16:36 |
doko | well, ok. looking at that | 16:37 |
LocutusOfBorg | doko, python-numpy is not building, probably because of some dh-python changes... | 16:37 |
LocutusOfBorg | SUPPORTED_INTERPRETERS = {'python', 'python3', 'python-dbg', 'python3-dbg', | 16:37 |
doko | without removing the packages you wouldn't have triggered the tests | 16:37 |
LocutusOfBorg | that python-dbg should be replaced... | 16:38 |
doko | LocutusOfBorg: and probably python too | 16:38 |
doko | can you do that? | 16:38 |
LocutusOfBorg | unfortunately even changing that is not sufficient to make python-numpy build | 16:39 |
LocutusOfBorg | the build doesn't even start | 16:39 |
LocutusOfBorg | :/ | 16:39 |
LocutusOfBorg | this is from debian log: | 16:39 |
LocutusOfBorg | pyversions: missing debian/pyversions file, fall back to supported versions | 16:39 |
LocutusOfBorg | python-dbg setup.py build --force | 16:39 |
LocutusOfBorg | cp /usr/bin/python2-dbg /usr/bin/python-dbg <-- this works, not sure where else it has to be changed | 16:40 |
xnox | erw | 16:42 |
doko | ahasenack, jamespage: want a bug report for juju-deployer? | 16:42 |
ahasenack | wat | 16:42 |
doko | LocutusOfBorg: python-dbg is gone | 16:43 |
LocutusOfBorg | python2-dbg exists | 16:43 |
LocutusOfBorg | and something is trying to call python-dbg to make numpy build | 16:43 |
LocutusOfBorg | this is why the cp works | 16:43 |
ahasenack | doko: if you have details, sure | 16:43 |
LocutusOfBorg | of coruse we have to change that call to python2-dbg | 16:44 |
doko | ahasenack: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/j/juju-deployer/20200108_123842_7fa37@/log.gz | 16:45 |
doko | LocutusOfBorg: yes, that's what I mean | 16:46 |
ahasenack | doko: and what's the story with bzrlib? It's gone? | 16:46 |
tumbleweed | well python3-breezy presumably replaced it | 16:47 |
doko | ahasenack: yes, maybe talk to jelmer directly | 16:48 |
-queuebot:#ubuntu-release- Unapproved: network-manager (eoan-proposed/main) [1.20.4-2ubuntu2.1 => 1.20.4-2ubuntu2.2] (desktop-core) | 16:58 | |
ahasenack | tumbleweed: thanks, python3-breezy has the same workingtree module that juju-deployer imports, maybe it works as a direct replacement | 17:30 |
LocutusOfBorg | doko, https://launchpadlibrarian.net/459723129/dh-python_4.20191017ubuntu2_4.20191017ubuntu3.diff.gz | 17:31 |
LocutusOfBorg | this is an incomplete and possibly wrong patch | 17:31 |
LocutusOfBorg | I'm stopping there, I know zero about that package :/ | 17:32 |
cjwatson | ahasenack: You can often do one-for-one replacements although the details often differ slightly. https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/373805 may be somewhat illustrative ... | 17:34 |
ahasenack | cjwatson: lp switched to breezy? | 17:34 |
cjwatson | Partly | 17:34 |
cjwatson | Not deployed to production yet, and in any case there's still more to do - there are some problems with Subversion support that are blocking switching code imports over | 17:35 |
ahasenack | thanks for the pointer, I added it to the bug | 17:35 |
cjwatson | ahasenack: Another thing that may be helpful is that the latest version of juju-deployer on PyPI doesn't use bzrlib any more; it just uses the bzr command line instead | 17:37 |
cjwatson | ahasenack: That would be easy to backport, I think | 17:37 |
cjwatson | ahasenack: https://paste.ubuntu.com/p/cWvYVYDGvq/ is a reduced diff that's probably enough | 17:38 |
ahasenack | hm, I thought lp was the upstream | 17:38 |
ahasenack | https://launchpad.net/juju-deployer/ I mean | 17:39 |
cjwatson | It is | 17:39 |
cjwatson | That change was part of https://bazaar.launchpad.net/~juju-deployers/juju-deployer/trunk/revision/174 | 17:40 |
cjwatson | But the Ubuntu package is behind | 17:40 |
cjwatson | Probably best to just package the current upstream version unless there's a good reason not to ... | 17:40 |
ahasenack | ok | 17:40 |
ahasenack | sounds good | 17:42 |
jamespage | doko: its not maintained so lets RM it | 17:52 |
ahasenack | jamespage: #is uses it via mojo? | 17:55 |
xnox | i sponsored upload for mom@ubuntu.com | 18:17 |
* xnox facepalms | 18:17 | |
-queuebot:#ubuntu-release- Unapproved: xdg-desktop-portal (eoan-proposed/main) [1.4.2-2 => 1.4.2-2ubuntu1] (ubuntu-desktop, ubuntugnome) | 18:36 | |
bdmurray | xnox: would it be naive to retest systemd w/ util-linux for eoan/i386? http://autopkgtest.ubuntu.com/packages/s/systemd/eoan/i386 | 18:45 |
gQuigs | is the python-ldap SRU going to block on the two autopkgtest failures? http://autopkgtest.ubuntu.com/packages/b/barbican/disco/armhf and http://autopkgtest.ubuntu.com/packages/s/salt/eoan/s390x ? looks like they were re-run and still failed, so real failures? | 18:55 |
mfo | Could someone please remove makedumpfile from the upload queue for Bionic/Eoan? (and Disco too, since it's going EOL before the 7-days in proposed criterion) they're all dated 2019-12-20. The reason is that re-spinned debdiffs came in w/ a new fix. And I'm not asking the SRU vanguard for today directly bcz it's ~8PM his time. Thanks! | 19:55 |
mfo | (the upload in Xenial's upload queue is OK, not to be removed.) | 19:56 |
gQuigs | what date does Disco go EOL? /me ponders if it just makes sense to have that date in the announce email (there hasn't been a Going EOL email yet to ubuntu-annouce) | 20:05 |
mfo | gQuigs, on my Eoan laptop this prints 10 (days): $ ubuntu-distro-info --series=disco --days=eol | 20:19 |
gQuigs | mfo: so it does, that's neat | 20:23 |
xnox | bdmurray: only fsckd test failed, which is known to be flakey in the past. I guess we can rerun it, or even release it as is. | 20:26 |
xnox | scheduled rerun | 20:26 |
bdmurray | xnox: thanks! | 20:28 |
xnox | gQuigs: those failures should not hold up releasing python-ldap on bionic for example. any SRU team member should be able to release other series, e.g. bdmurray | 20:28 |
xnox | gQuigs: barbican looks very odd | 20:28 |
xnox | jamespage: do we support barbican on disco on armhf? and it fails oddly: | 20:29 |
xnox | autopkgtest [02:30:37]: test barbican-daemons: [----------------------- | 20:29 |
xnox | OK | 20:29 |
xnox | OK | 20:29 |
xnox | autopkgtest [02:30:39]: test barbican-daemons: -----------------------] | 20:29 |
xnox | autopkgtest [02:30:41]: test barbican-daemons: - - - - - - - - - - results - - - - - - - - - - | 20:29 |
xnox | barbican-daemons FAIL non-zero exit status 127 | 20:29 |
xnox | as if something got killed? | 20:29 |
xnox | do you know who can look into it? | 20:29 |
vorlon | mfo: done | 20:30 |
-queuebot:#ubuntu-release- Unapproved: rejected makedumpfile [source] (bionic-proposed) [1:1.6.5-1ubuntu1~18.04.4] | 20:30 | |
-queuebot:#ubuntu-release- Unapproved: rejected makedumpfile [source] (disco-proposed) [1:1.6.5-1ubuntu1.4] | 20:30 | |
-queuebot:#ubuntu-release- Unapproved: rejected makedumpfile [source] (eoan-proposed) [1:1.6.6-2ubuntu1.1] | 20:30 | |
xnox | gQuigs: re:salt => looks like zeromq is busted. But i thought zeromq was fixed to work on s390x, not sure if it was in eoan already. | 20:30 |
xnox | gQuigs: also does not appear to be a problem with python-ldap and should be releasable even on eoan. | 20:31 |
mfo | vorlon, thank you. | 20:31 |
xnox | gQuigs: which series do you care about to have python-ldap to be released on? | 20:31 |
gQuigs | xnox: only care about 18.04 - which doesn't have any regressions listed :) | 20:32 |
xnox | gQuigs: so bug SRU team to release it there. | 20:33 |
xnox | gQuigs: it was explicitely stated, that per-series SRUs are independent of each other and there are no ordering requirements to release eoan, before disco, before bionic. | 20:34 |
xnox | gQuigs: feel free to include the salesforce reference when pinging sru team | 20:34 |
gQuigs | xnox: oh, I thought there was some requirement like that, thanks! | 20:34 |
gQuigs | vorlon: mind releasing python-ldap to 18.04 per above^? this is for IBM and also track in SF. | 20:43 |
vorlon | gQuigs: done; who's responsible for following through on the disco and eoan autopkgtest regressions? | 20:53 |
vorlon | I don't mind them being released out of order - I do mind people not following through on the interim releases and leaving stuff clogging up -proposed :) | 20:54 |
gQuigs | vorlon: thanks! if no one else responds today - I'll follow up and make sure the others don't get lost in -proposed | 20:58 |
-queuebot:#ubuntu-release- New binary: open-font-design-toolkit [amd64] (focal-proposed/none) [1.8] (no packageset) | 23:14 | |
-queuebot:#ubuntu-release- Packageset: Removed haskell-devscripts from i386-whitelist in focal | 23:22 | |
-queuebot:#ubuntu-release- Packageset: Removed pandoc from i386-whitelist in focal | 23:22 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!