/srv/irclogs.ubuntu.com/2019/11/05/#ubuntu-release.txt

-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
vorlonLocutusOfBorg: when should we reintroduce opencv 4?  ros-opencv-apps currently ftbfs because it needs new opencv01:03
-queuebot:#ubuntu-release- Unapproved: grub2-signed (xenial-proposed/main) [1.66.22 => 1.66.23] (core)01:14
xnoxi 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
vorlonxnox: yes, that is the reason.  NBS packages in -proposed require some manual gardening06:02
-queuebot:#ubuntu-release- Unapproved: grub2 (eoan-proposed/main) [2.04-1ubuntu12 => 2.04-1ubuntu12.1] (core)06:03
vorlonand perhaps someone has done this now06: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
LocutusOfBorgvorlon, 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
LocutusOfBorge.g. can you please kick vlfeat out? reason is: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92585306:23
ubot5Debian bug 925853 in src:vlfeat "vlfeat: ftbfs with GCC-9" [Serious,Open]06:23
LocutusOfBorgneeds sourceful upload and blocks transition06:23
LocutusOfBorgplplot is fixed now with swig fixes06:33
infinityLocutusOfBorg: Define "fixed" and "now".06:46
infinityLocutusOfBorg: A retry still failed everywhere.06:46
LocutusOfBorginfinity, swig is not yet published :D06:47
infinityLocutusOfBorg: So "now" was a bit premature.  Check.06:47
LocutusOfBorgyep, but don't worry I already scheduled rebuilds once the archive is good :)06:48
LocutusOfBorgI'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
LocutusOfBorgsigh^^ that one was left out07:32
LocutusOfBorgplease accept that one...07:41
mwhudsondoes anyone want to think about http://autopkgtest.ubuntu.com/packages/p/psi4/focal/armhf08:02
-queuebot:#ubuntu-release- New: accepted plplot [arm64] (focal-proposed) [5.15.0+dfsg-4build1]09:08
dokomwhudson: did you look how they fail?09:18
mwhudsondoko: i did earlier but i forget the details09:19
mwhudsonRunning test scf-property... FAILED09:19
mwhudsonthanks09:19
mwhudson(that's the entire output for the failing test)09:19
mwhudsonthe package has exactly 1 reverse recommend it seems09:21
mwhudsoni think we could safely stop building it on armhf and exactly noone would notice09:21
dokojust want to exclude that this is a bus error09:21
mwhudsonno evidence of that09:21
dokono rdeps09:22
dokomwhudson: but it's triggered by other packages as well, failures on other archs09:24
dokoand RC in debian, removing09:24
mwhudsonah good10:15
mwhudsonjust pandas then for numpy to migrate :/10:15
dokoyep, wondering if we should follow rebecca's roadmap to the new version10:15
dokoit's easier, because we already removed the python-panda package10:16
mwhudsonthe plan makes sense to me in general terms10:30
mwhudsoni don't know her timescale, can we want for her to do it and sync, or should we just push ahead10:30
mwhudson?10:30
mwhudsonoh we can just sync from experimental i guess10:32
dokoyes, and then following-up on her analysis10: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
dokohttp://autopkgtest.ubuntu.com/packages/p/python-scipy/focal/i38612:18
dokohow do I trigger that correctly? needs a trigger for the numpy and python-scipy in proposed12:19
dokoof course we can update the python-scipy/i386 hint12:20
dokosil2100, Laney: ^^^12:20
Laneydon't specify the same package twice12:21
Laneytry apt-cache showsrc python-scipy python-scipy >/dev/null12:22
Laneyit's a weird apt behaviour / bug (not sure)12:22
dokojuliank: ^^^12:24
juliankLaney, doko: he, fascinating12:25
juliank*heh12:25
juliankLaney: it's a feature to avoid showing duplicates, so it does not find any new entries for the second argument...12:40
juliankit might make sense to avoid showing duplicates per argument12: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
dokoPreparing to unpack .../322-python-statsmodels-doc_0.9.0-6ubuntu4_all.deb ...14:00
dokoUnpacking python-statsmodels-doc (0.9.0-6ubuntu4) ...14:00
dokodpkg: 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-6ubuntu414:00
dokodpkg-deb: error: paste subprocess was killed by signal (Broken pipe)14:00
dokovorlon, ginggs: where should the examples go?14:00
ginggsdoko: hmm, vorlon did "Also pass --doc-main-package to dh_installexamples." in ubuntu3, to fix ftbfs in ubuntu214:05
xnoxdoko:  only the doc package imho. But should not be compressed, i think.14:09
dokothen you can't run them ;p14:09
ginggsdoko: the debian packaging puts them in python-statsmodels-doc14:15
ginggs(only)14:17
ginggsdoko: statsmodels 0.10.1 (python3 only) is in experimental, shall i sync/merge that?14:22
dokoginggs: sure, if it fixes things. the current one migrated14:23
dokoa bigger problem however is xarray14:23
-queuebot:#ubuntu-release- Unapproved: systemd (eoan-proposed/main) [242-7ubuntu3 => 242-7ubuntu3.2] (core)15:25
ddstreetsil2100 rbalint reuploaded systemd to eoan with -v242-7ubuntu3, sorry15:25
ddstreetsil2100 i also have systemd uploads in x/b/d, the bionic uploads are starting to pile up fixes, any chance you can approve them15:27
bdmurraysil2100, infinity: Has this, from the New Release Cycle Process, "Notify Gerfried Fuchs (Rhonda) to update packages.ubuntu.com." happened?15:48
bdmurrayddstreet: Are any of them ipv6 MTU changes?15:48
bdmurrayAlso eoan-updates and eoan-backports are missing on packages.ubuntu.com15:49
cjwatsonUgh, need to update that name15:50
Laneybleh, yes15:51
cjwatson(Done.  Contact is still the same AFAIK but we should use the correct name)15:51
bdmurrayIs this out of date too? https://packages.ubuntu.com/about/15:52
bdmurraycjwatson: Could you explain to me what was done?15:52
cjwatsonNot sure, sorry15:52
cjwatsonbdmurray: Will do by /msg15:53
bdmurraycjwatson: thanks15: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
vorlonyeah, that's something to give warm fuzzies in a debian/rules19: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
infinityvorlon: Is the build-dep also conditional?19:34
infinity(Also, perhaps they've never heard of "!")19:34
vorloninfinity: no.  so a packaging error in python3-numpy would cause a misbuild instead of a build failure19:34
infinityvorlon: 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
bdmurrayinfinity: I've just verified bug 1825655 so I think ubuntu-release-upgrader can be released for 19.10 early.20:21
ubot5bug 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/182565520:21
infinitybdmurray: Okay, but I'll have to check with my manager.20:22
infinitybdmurray: In an hour or so, you'll probably want to flip meta-release to point to updates (or I can).20:24
infinitybdmurray: 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
infinitybdmurray: 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
bdmurrayhaving it check updates first shouldn't be too hard he said20:29
ginggsdoko: python-xarray regressed in debian testing, which is why it migrated there (migration-reference). it has also regressed in ubuntu release20:33
=== msalvatore_ is now known as msalvatore
infinitybdmurray: http://archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dist-upgrader-all/21:19
bdmurrayinfinity: thanks21:20
vorlondoko: 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
vorlonoctave transition should be done with the next full britney run, owing to aggressive removals22: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
vorlongdcm is entangled enough (gdcm -> vtk7 -> ffmpeg) that it looks to me like we should JFDI the gdcm transition also22:39
vorlonLocutusOfBorg: ^^ 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
dokovorlon: no23:27
vorlonoctave transition done23:30
vorlondoko: 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!