-queuebot:#ubuntu-release- New: accepted django-mailer [amd64] (focal-proposed) [2.0-0ubuntu1] | 00:47 | |
-queuebot:#ubuntu-release- New: accepted hypre [armhf] (focal-proposed) [2.18.2-1] | 00:47 | |
-queuebot:#ubuntu-release- New: accepted hypre [arm64] (focal-proposed) [2.18.2-1] | 00:47 | |
-queuebot:#ubuntu-release- New: accepted hypre [amd64] (focal-proposed) [2.18.2-1] | 00:47 | |
-queuebot:#ubuntu-release- New: accepted hypre [ppc64el] (focal-proposed) [2.18.2-1] | 00:47 | |
-queuebot:#ubuntu-release- New: accepted hypre [i386] (focal-proposed) [2.18.2-1] | 00:47 | |
-queuebot:#ubuntu-release- New: accepted hypre [s390x] (focal-proposed) [2.18.2-1] | 00:48 | |
-queuebot:#ubuntu-release- Unapproved: grub2-signed (xenial-proposed/main) [1.66.22 => 1.66.23] (core) | 00:55 | |
vorlon | LocutusOfBorg: when should we reintroduce opencv 4? ros-opencv-apps currently ftbfs because it needs new opencv | 01:03 |
---|---|---|
-queuebot:#ubuntu-release- Unapproved: grub2-signed (xenial-proposed/main) [1.66.22 => 1.66.23] (core) | 01:14 | |
xnox | i am confused why django-mailer is not a candidate, does AA need to RM python-django-mailer? | 01:31 |
=== s8321414_ is now known as s8321414 | ||
-queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (xenial-proposed) [2.02~beta2-36ubuntu3.23] | 05:43 | |
-queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (xenial-proposed) [2.02~beta2-36ubuntu3.23] | 05:43 | |
-queuebot:#ubuntu-release- Unapproved: rejected grub2-signed [source] (xenial-proposed) [1.66.23] | 05:45 | |
-queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (eoan-proposed) [2.04-1ubuntu12.1] | 05:49 | |
-queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (xenial-proposed) [1:16.04.28] | 05:56 | |
-queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (bionic-proposed) [1:18.04.35] | 05:57 | |
vorlon | xnox: yes, that is the reason. NBS packages in -proposed require some manual gardening | 06:02 |
-queuebot:#ubuntu-release- Unapproved: grub2 (eoan-proposed/main) [2.04-1ubuntu12 => 2.04-1ubuntu12.1] (core) | 06:03 | |
vorlon | and perhaps someone has done this now | 06:03 |
-queuebot:#ubuntu-release- Unapproved: grub2 (eoan-proposed/main) [2.04-1ubuntu12.1 => 2.04-1ubuntu12.1] (core) | 06:17 | |
-queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (eoan-proposed) [2.04-1ubuntu12.1] | 06:20 | |
-queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (eoan-proposed) [2.04-1ubuntu12.1] | 06:20 | |
LocutusOfBorg | vorlon, I would say when octave, proj and ffmpeg migrates? | 06:21 |
-queuebot:#ubuntu-release- Unapproved: accepted zfs-linux [source] (eoan-proposed) [0.8.1-1ubuntu14.1] | 06:22 | |
LocutusOfBorg | e.g. can you please kick vlfeat out? reason is: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925853 | 06:23 |
ubot5 | Debian bug 925853 in src:vlfeat "vlfeat: ftbfs with GCC-9" [Serious,Open] | 06:23 |
LocutusOfBorg | needs sourceful upload and blocks transition | 06:23 |
LocutusOfBorg | plplot is fixed now with swig fixes | 06:33 |
infinity | LocutusOfBorg: Define "fixed" and "now". | 06:46 |
infinity | LocutusOfBorg: A retry still failed everywhere. | 06:46 |
LocutusOfBorg | infinity, swig is not yet published :D | 06:47 |
infinity | LocutusOfBorg: So "now" was a bit premature. Check. | 06:47 |
LocutusOfBorg | yep, but don't worry I already scheduled rebuilds once the archive is good :) | 06:48 |
LocutusOfBorg | I'm still worried about octave-signal and ppc64el... | 06:49 |
-queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [source] (xenial-proposed) [1.66.23] | 06:49 | |
-queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [source] (eoan-proposed) [1.128.1] | 06:55 | |
-queuebot:#ubuntu-release- New binary: remctl [i386] (focal-proposed/universe) [3.16-3ubuntu1] (no packageset) | 07:07 | |
-queuebot:#ubuntu-release- New binary: remctl [s390x] (focal-proposed/universe) [3.16-3ubuntu1] (no packageset) | 07:08 | |
-queuebot:#ubuntu-release- New binary: remctl [amd64] (focal-proposed/universe) [3.16-3ubuntu1] (no packageset) | 07:08 | |
-queuebot:#ubuntu-release- New binary: remctl [ppc64el] (focal-proposed/universe) [3.16-3ubuntu1] (no packageset) | 07:08 | |
-queuebot:#ubuntu-release- New binary: plplot [s390x] (focal-proposed/universe) [5.15.0+dfsg-4build1] (no packageset) | 07:09 | |
-queuebot:#ubuntu-release- New binary: plplot [ppc64el] (focal-proposed/universe) [5.15.0+dfsg-4build1] (no packageset) | 07:10 | |
-queuebot:#ubuntu-release- New binary: remctl [s390x] (focal-proposed/universe) [3.16-3ubuntu2] (no packageset) | 07:10 | |
-queuebot:#ubuntu-release- New binary: remctl [amd64] (focal-proposed/universe) [3.16-3ubuntu2] (no packageset) | 07:10 | |
-queuebot:#ubuntu-release- New binary: plplot [i386] (focal-proposed/universe) [5.15.0+dfsg-4build1] (no packageset) | 07:10 | |
-queuebot:#ubuntu-release- New binary: remctl [ppc64el] (focal-proposed/universe) [3.16-3ubuntu2] (no packageset) | 07:10 | |
-queuebot:#ubuntu-release- New binary: remctl [i386] (focal-proposed/universe) [3.16-3ubuntu2] (no packageset) | 07:10 | |
-queuebot:#ubuntu-release- New binary: remctl [arm64] (focal-proposed/universe) [3.16-3ubuntu2] (no packageset) | 07:12 | |
-queuebot:#ubuntu-release- New binary: remctl [armhf] (focal-proposed/universe) [3.16-3ubuntu2] (no packageset) | 07:12 | |
-queuebot:#ubuntu-release- New binary: plplot [amd64] (focal-proposed/universe) [5.15.0+dfsg-4build1] (no packageset) | 07:16 | |
-queuebot:#ubuntu-release- New binary: plplot [armhf] (focal-proposed/universe) [5.15.0+dfsg-4build1] (no packageset) | 07:25 | |
-queuebot:#ubuntu-release- New: accepted remctl [amd64] (focal-proposed) [3.16-3ubuntu1] | 07:28 | |
-queuebot:#ubuntu-release- New: accepted remctl [ppc64el] (focal-proposed) [3.16-3ubuntu1] | 07:28 | |
-queuebot:#ubuntu-release- New: accepted remctl [amd64] (focal-proposed) [3.16-3ubuntu2] | 07:28 | |
-queuebot:#ubuntu-release- New: accepted remctl [armhf] (focal-proposed) [3.16-3ubuntu2] | 07:28 | |
-queuebot:#ubuntu-release- New: accepted remctl [ppc64el] (focal-proposed) [3.16-3ubuntu2] | 07:28 | |
-queuebot:#ubuntu-release- New: accepted remctl [i386] (focal-proposed) [3.16-3ubuntu1] | 07:28 | |
-queuebot:#ubuntu-release- New: accepted remctl [arm64] (focal-proposed) [3.16-3ubuntu2] | 07:28 | |
-queuebot:#ubuntu-release- New: accepted remctl [s390x] (focal-proposed) [3.16-3ubuntu2] | 07:28 | |
-queuebot:#ubuntu-release- New: accepted remctl [s390x] (focal-proposed) [3.16-3ubuntu1] | 07:28 | |
-queuebot:#ubuntu-release- New: accepted remctl [i386] (focal-proposed) [3.16-3ubuntu2] | 07:28 | |
-queuebot:#ubuntu-release- New: accepted plplot [amd64] (focal-proposed) [5.15.0+dfsg-4build1] | 07:29 | |
-queuebot:#ubuntu-release- New: accepted plplot [i386] (focal-proposed) [5.15.0+dfsg-4build1] | 07:29 | |
-queuebot:#ubuntu-release- New: accepted plplot [s390x] (focal-proposed) [5.15.0+dfsg-4build1] | 07:29 | |
-queuebot:#ubuntu-release- New: accepted plplot [armhf] (focal-proposed) [5.15.0+dfsg-4build1] | 07:29 | |
-queuebot:#ubuntu-release- New: accepted plplot [ppc64el] (focal-proposed) [5.15.0+dfsg-4build1] | 07:29 | |
-queuebot:#ubuntu-release- New binary: plplot [arm64] (focal-proposed/universe) [5.15.0+dfsg-4build1] (no packageset) | 07:31 | |
LocutusOfBorg | sigh^^ that one was left out | 07:32 |
LocutusOfBorg | please accept that one... | 07:41 |
mwhudson | does anyone want to think about http://autopkgtest.ubuntu.com/packages/p/psi4/focal/armhf | 08:02 |
-queuebot:#ubuntu-release- New: accepted plplot [arm64] (focal-proposed) [5.15.0+dfsg-4build1] | 09:08 | |
doko | mwhudson: did you look how they fail? | 09:18 |
mwhudson | doko: i did earlier but i forget the details | 09:19 |
mwhudson | Running test scf-property... FAILED | 09:19 |
mwhudson | thanks | 09:19 |
mwhudson | (that's the entire output for the failing test) | 09:19 |
mwhudson | the package has exactly 1 reverse recommend it seems | 09:21 |
mwhudson | i think we could safely stop building it on armhf and exactly noone would notice | 09:21 |
doko | just want to exclude that this is a bus error | 09:21 |
mwhudson | no evidence of that | 09:21 |
doko | no rdeps | 09:22 |
doko | mwhudson: but it's triggered by other packages as well, failures on other archs | 09:24 |
doko | and RC in debian, removing | 09:24 |
mwhudson | ah good | 10:15 |
mwhudson | just pandas then for numpy to migrate :/ | 10:15 |
doko | yep, wondering if we should follow rebecca's roadmap to the new version | 10:15 |
doko | it's easier, because we already removed the python-panda package | 10:16 |
mwhudson | the plan makes sense to me in general terms | 10:30 |
mwhudson | i don't know her timescale, can we want for her to do it and sync, or should we just push ahead | 10:30 |
mwhudson | ? | 10:30 |
mwhudson | oh we can just sync from experimental i guess | 10:32 |
doko | yes, and then following-up on her analysis | 10:34 |
-queuebot:#ubuntu-release- Unapproved: accepted gcc-5 [sync] (xenial-proposed) [5.4.0-6ubuntu1~16.04.12] | 11:01 | |
=== seb128_ is now known as seb128 | ||
-queuebot:#ubuntu-release- Unapproved: libreoffice (eoan-proposed/main) [1:6.3.2-0ubuntu2 => 1:6.3.3-0ubuntu0.19.10.1] (ubuntu-desktop) | 11:14 | |
=== s8321414_ is now known as s8321414 | ||
doko | http://autopkgtest.ubuntu.com/packages/p/python-scipy/focal/i386 | 12:18 |
doko | how do I trigger that correctly? needs a trigger for the numpy and python-scipy in proposed | 12:19 |
doko | of course we can update the python-scipy/i386 hint | 12:20 |
doko | sil2100, Laney: ^^^ | 12:20 |
Laney | don't specify the same package twice | 12:21 |
Laney | try apt-cache showsrc python-scipy python-scipy >/dev/null | 12:22 |
Laney | it's a weird apt behaviour / bug (not sure) | 12:22 |
doko | juliank: ^^^ | 12:24 |
juliank | Laney, doko: he, fascinating | 12:25 |
juliank | *heh | 12:25 |
juliank | Laney: it's a feature to avoid showing duplicates, so it does not find any new entries for the second argument... | 12:40 |
juliank | it might make sense to avoid showing duplicates per argument | 12:41 |
-queuebot:#ubuntu-release- New binary: getfem++ [s390x] (focal-proposed/universe) [5.2+dfsg1-7ubuntu2] (no packageset) | 13:07 | |
-queuebot:#ubuntu-release- New binary: getfem++ [i386] (focal-proposed/universe) [5.2+dfsg1-7ubuntu2] (no packageset) | 13:11 | |
-queuebot:#ubuntu-release- New binary: getfem++ [amd64] (focal-proposed/universe) [5.2+dfsg1-7ubuntu2] (no packageset) | 13:14 | |
-queuebot:#ubuntu-release- New binary: getfem++ [ppc64el] (focal-proposed/universe) [5.2+dfsg1-7ubuntu2] (no packageset) | 13:14 | |
-queuebot:#ubuntu-release- New: accepted getfem++ [amd64] (focal-proposed) [5.2+dfsg1-7ubuntu2] | 13:27 | |
-queuebot:#ubuntu-release- New: accepted getfem++ [ppc64el] (focal-proposed) [5.2+dfsg1-7ubuntu2] | 13:27 | |
-queuebot:#ubuntu-release- New: accepted getfem++ [i386] (focal-proposed) [5.2+dfsg1-7ubuntu2] | 13:27 | |
-queuebot:#ubuntu-release- New: accepted getfem++ [s390x] (focal-proposed) [5.2+dfsg1-7ubuntu2] | 13:27 | |
doko | Preparing to unpack .../322-python-statsmodels-doc_0.9.0-6ubuntu4_all.deb ... | 14:00 |
doko | Unpacking python-statsmodels-doc (0.9.0-6ubuntu4) ... | 14:00 |
doko | dpkg: error processing archive /tmp/apt-dpkg-install-x5XaOl/322-python-statsmodels-doc_0.9.0-6ubuntu4_all.deb (--unpack): | 14:00 |
doko | trying to overwrite '/usr/share/doc/python3-statsmodels/examples/incomplete/arima.py', which is also in package python3-statsmodels 0.9.0-6ubuntu4 | 14:00 |
doko | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | 14:00 |
doko | vorlon, ginggs: where should the examples go? | 14:00 |
ginggs | doko: hmm, vorlon did "Also pass --doc-main-package to dh_installexamples." in ubuntu3, to fix ftbfs in ubuntu2 | 14:05 |
xnox | doko: only the doc package imho. But should not be compressed, i think. | 14:09 |
doko | then you can't run them ;p | 14:09 |
ginggs | doko: the debian packaging puts them in python-statsmodels-doc | 14:15 |
ginggs | (only) | 14:17 |
ginggs | doko: statsmodels 0.10.1 (python3 only) is in experimental, shall i sync/merge that? | 14:22 |
doko | ginggs: sure, if it fixes things. the current one migrated | 14:23 |
doko | a bigger problem however is xarray | 14:23 |
-queuebot:#ubuntu-release- Unapproved: systemd (eoan-proposed/main) [242-7ubuntu3 => 242-7ubuntu3.2] (core) | 15:25 | |
ddstreet | sil2100 rbalint reuploaded systemd to eoan with -v242-7ubuntu3, sorry | 15:25 |
ddstreet | sil2100 i also have systemd uploads in x/b/d, the bionic uploads are starting to pile up fixes, any chance you can approve them | 15:27 |
bdmurray | sil2100, infinity: Has this, from the New Release Cycle Process, "Notify Gerfried Fuchs (Rhonda) to update packages.ubuntu.com." happened? | 15:48 |
bdmurray | ddstreet: Are any of them ipv6 MTU changes? | 15:48 |
bdmurray | Also eoan-updates and eoan-backports are missing on packages.ubuntu.com | 15:49 |
cjwatson | Ugh, need to update that name | 15:50 |
Laney | bleh, yes | 15:51 |
cjwatson | (Done. Contact is still the same AFAIK but we should use the correct name) | 15:51 |
bdmurray | Is this out of date too? https://packages.ubuntu.com/about/ | 15:52 |
bdmurray | cjwatson: Could you explain to me what was done? | 15:52 |
cjwatson | Not sure, sorry | 15:52 |
cjwatson | bdmurray: Will do by /msg | 15:53 |
bdmurray | cjwatson: thanks | 15:53 |
-queuebot:#ubuntu-release- Unapproved: epiphany-browser (bionic-proposed/universe) [3.28.5-0ubuntu1 => 3.28.6-0ubuntu1] (desktop-extra) | 16:03 | |
-queuebot:#ubuntu-release- New binary: linux-signed-azure-5.3 [amd64] (bionic-proposed/universe) [5.3.0-1006.6~18.04.1] (no packageset) | 16:31 | |
-queuebot:#ubuntu-release- New binary: linux-signed-gcp-5.3 [amd64] (bionic-proposed/universe) [5.3.0-1007.7~18.04.1] (no packageset) | 16:31 | |
-queuebot:#ubuntu-release- New: accepted linux-signed-azure-5.3 [amd64] (bionic-proposed) [5.3.0-1006.6~18.04.1] | 17:17 | |
-queuebot:#ubuntu-release- New: accepted linux-signed-gcp-5.3 [amd64] (bionic-proposed) [5.3.0-1007.7~18.04.1] | 17:17 | |
-queuebot:#ubuntu-release- Unapproved: livecd-rootfs (disco-proposed/main) [2.578.9 => 2.578.10] (desktop-core) | 19:24 | |
vorlon | [ -x /usr/bin/dh_numpy ] && dh_numpy || : | 19:25 |
vorlon | yeah, that's something to give warm fuzzies in a debian/rules | 19:25 |
-queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (disco-proposed) [2.578.10] | 19:26 | |
-queuebot:#ubuntu-release- Unapproved: livecd-rootfs (bionic-proposed/main) [2.525.33 => 2.525.34] (desktop-core) | 19:29 | |
-queuebot:#ubuntu-release- Unapproved: livecd-rootfs (disco-proposed/main) [2.578.9 => 2.578.10] (desktop-core) | 19:29 | |
infinity | vorlon: Is the build-dep also conditional? | 19:34 |
infinity | (Also, perhaps they've never heard of "!") | 19:34 |
vorlon | infinity: no. so a packaging error in python3-numpy would cause a misbuild instead of a build failure | 19:34 |
infinity | vorlon: I'm less concerned about the possibility that the check might fail, and more concerned about the "test && command || true" construct instead of "! test || command" | 19:53 |
bdmurray | infinity: I've just verified bug 1825655 so I think ubuntu-release-upgrader can be released for 19.10 early. | 20:21 |
ubot5 | bug 1825655 in ubuntu-release-upgrader (Ubuntu Eoan) "do-release-upgrade fails with "Your python3 install is corrupted" if /usr/bin/python points to /etc/alternatives/python" [Undecided,Fix committed] https://launchpad.net/bugs/1825655 | 20:21 |
infinity | bdmurray: Okay, but I'll have to check with my manager. | 20:22 |
infinity | bdmurray: In an hour or so, you'll probably want to flip meta-release to point to updates (or I can). | 20:24 |
infinity | bdmurray: I've been thinking about the awkwardness of that and wondering if we shouldn't just mirror release to updates on release day, so we don't have to remember to twiddle it if/when there's an SRU two months later. | 20:25 |
-queuebot:#ubuntu-release- New binary: lskat [amd64] (focal-proposed/universe) [4:19.08.0-2ubuntu1] (kubuntu) | 20:26 | |
infinity | bdmurray: Alternately, make the release-upgrader itself smarter about how it finds the tarball, so it can check updates, then release (and, with a switch, optionally proposed for testing) | 20:27 |
bdmurray | having it check updates first shouldn't be too hard he said | 20:29 |
ginggs | doko: python-xarray regressed in debian testing, which is why it migrated there (migration-reference). it has also regressed in ubuntu release | 20:33 |
=== msalvatore_ is now known as msalvatore | ||
infinity | bdmurray: http://archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dist-upgrader-all/ | 21:19 |
bdmurray | infinity: thanks | 21:20 |
vorlon | doko: examples: I certainly expected them to be contained in the python-statsmodels-doc package and shipped in the /usr/share/doc/python3-statsmodels/examples directory. I don't know what happened to cause them to be in both packages, are you following up on this? | 22:19 |
vorlon | octave transition should be done with the next full britney run, owing to aggressive removals | 22:22 |
-queuebot:#ubuntu-release- Unapproved: amd64-microcode (eoan-proposed/main) [3.20181128.1ubuntu2 => 3.20191021.1ubuntu0.19.10.1] (core) (sync) | 22:27 | |
-queuebot:#ubuntu-release- Unapproved: amd64-microcode (disco-proposed/main) [3.20181128.1ubuntu1.1 => 3.20191021.1ubuntu0.19.04.1] (core) (sync) | 22:29 | |
-queuebot:#ubuntu-release- Unapproved: amd64-microcode (bionic-proposed/main) [3.20181128.1~ubuntu0.18.04.1 => 3.20191021.1ubuntu0.18.04.2] (ubuntu-desktop, ubuntu-server) (sync) | 22:29 | |
-queuebot:#ubuntu-release- Unapproved: amd64-microcode (xenial-proposed/main) [3.20180524.1~ubuntu0.16.04.2 => 3.20191021.1ubuntu0.16.04.1] (no packageset) (sync) | 22:30 | |
=== s8321414_ is now known as s8321414 | ||
vorlon | gdcm is entangled enough (gdcm -> vtk7 -> ffmpeg) that it looks to me like we should JFDI the gdcm transition also | 22:39 |
vorlon | LocutusOfBorg: ^^ just reviewing our discussion before, is this a bad idea because we have to also do the itk4 transition in order to get it to build against new gdcm? | 22:49 |
-queuebot:#ubuntu-release- New binary: golang-github-ssgelm-cookiejarparser [amd64] (focal-proposed/universe) [1.0.0-1] (no packageset) | 23:16 | |
-queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.3-2 => 1.3.3-2] (core) | 23:18 | |
-queuebot:#ubuntu-release- Unapproved: linux-firmware (disco-proposed/main) [1.178.5 => 1.178.6] (core, kernel) | 23:18 | |
-queuebot:#ubuntu-release- Unapproved: linux-firmware (bionic-proposed/main) [1.173.11 => 1.173.12] (core, kernel) | 23:19 | |
-queuebot:#ubuntu-release- Unapproved: linux-firmware (eoan-proposed/main) [1.183.1 => 1.183.2] (core, kernel) | 23:20 | |
-queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.3-2 => 1.3.3-2] (core) | 23:20 | |
-queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.3-2 => 1.3.3-2] (core) | 23:21 | |
-queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.3-2 => 1.3.3-2] (core) | 23:25 | |
doko | vorlon: no | 23:27 |
vorlon | octave transition done | 23:30 |
vorlon | doko: img2pdf has been FTBFS in -proposed for 3 cycles with failures related to jpeg2k. What's the current state of affairs for libjpeg-turbo vs libjpeg8 etc? Is our delta from Debian here still sane? | 23:50 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!