tsimonq2 | slangasek: Ah. Thanks. | 00:20 |
---|---|---|
-queuebot:#ubuntu-release- New: accepted astropy-regions [amd64] (cosmic-proposed) [0.2-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted astropy-regions [armhf] (cosmic-proposed) [0.2-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted astropy-regions [ppc64el] (cosmic-proposed) [0.2-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted cftime [arm64] (cosmic-proposed) [1.0.0~b1-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted cftime [i386] (cosmic-proposed) [1.0.0~b1-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted goodvibes [amd64] (cosmic-proposed) [0.3.6-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted goodvibes [armhf] (cosmic-proposed) [0.3.6-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted node-normalize.css [amd64] (cosmic-proposed) [8.0.0-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted python-pallets-sphinx-themes [amd64] (cosmic-proposed) [1.0.1-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted smenu [arm64] (cosmic-proposed) [0.9.12-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted astropy-regions [arm64] (cosmic-proposed) [0.2-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted cftime [amd64] (cosmic-proposed) [1.0.0~b1-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted cftime [ppc64el] (cosmic-proposed) [1.0.0~b1-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted goodvibes [i386] (cosmic-proposed) [0.3.6-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted smenu [amd64] (cosmic-proposed) [0.9.12-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted smenu [i386] (cosmic-proposed) [0.9.12-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted stlink [amd64] (cosmic-proposed) [1.5.0+ds-2] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted stlink [armhf] (cosmic-proposed) [1.5.0+ds-2] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted tmux-themepack-jimeh [amd64] (cosmic-proposed) [0+git20170413-748b16-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted tpm2-abrmd [arm64] (cosmic-proposed) [1.3.1-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted astropy-regions [i386] (cosmic-proposed) [0.2-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted goodvibes [arm64] (cosmic-proposed) [0.3.6-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted smenu [armhf] (cosmic-proposed) [0.9.12-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted stlink [arm64] (cosmic-proposed) [1.5.0+ds-2] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted tpm2-abrmd [amd64] (cosmic-proposed) [1.3.1-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted tpm2-abrmd [i386] (cosmic-proposed) [1.3.1-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted volatildap [amd64] (cosmic-proposed) [1.1.0+ds.1-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted cftime [armhf] (cosmic-proposed) [1.0.0~b1-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted starjava-dpac [amd64] (cosmic-proposed) [1.0+2018.03.22-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted tpm2-abrmd [armhf] (cosmic-proposed) [1.3.1-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted python-base58 [amd64] (cosmic-proposed) [1.0.0-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted tpm2-abrmd [ppc64el] (cosmic-proposed) [1.3.1-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted stlink [i386] (cosmic-proposed) [1.5.0+ds-2] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted astropy-regions [s390x] (cosmic-proposed) [0.2-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted goodvibes [ppc64el] (cosmic-proposed) [0.3.6-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted smenu [ppc64el] (cosmic-proposed) [0.9.12-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted stlink [ppc64el] (cosmic-proposed) [1.5.0+ds-2] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted cftime [s390x] (cosmic-proposed) [1.0.0~b1-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted smenu [s390x] (cosmic-proposed) [0.9.12-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted goodvibes [s390x] (cosmic-proposed) [0.3.6-1] | 00:23 | |
-queuebot:#ubuntu-release- New: accepted stlink [s390x] (cosmic-proposed) [1.5.0+ds-2] | 00:23 | |
-queuebot:#ubuntu-release- New binary: oca-core [amd64] (cosmic-proposed/universe) [11.0.20180420-1] (no packageset) | 00:40 | |
-queuebot:#ubuntu-release- Unapproved: lubuntu-meta (bionic-proposed/universe) [0.94 => 0.94.1] (lubuntu) | 02:06 | |
tsimonq2 | infinity, slangasek: Can I get some help with that lubuntu-meta upload? ^ | 02:14 |
tsimonq2 | We missed a dep in the metapackage before release. | 02:14 |
-queuebot:#ubuntu-release- Unapproved: accepted lubuntu-meta [source] (bionic-proposed) [0.94.1] | 03:52 | |
tsimonq2 | One additional note: I would argue for waiving the seven day aging period. | 03:53 |
tsimonq2 | People can't use apport at the moment to report bugs. | 03:53 |
tsimonq2 | (Not with the default suite of packages, anyway.) | 03:53 |
tsimonq2 | Either wxl or myself can test soonish. | 03:54 |
wxl | thx infinity | 04:04 |
=== maclin1 is now known as maclin | ||
-queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.32.5 => 2.32.9] (desktop-core, ubuntu-server) | 08:29 | |
-queuebot:#ubuntu-release- Unapproved: snapd (artful-proposed/main) [2.32.5+17.10 => 2.32.9+17.10] (desktop-core, ubuntu-server) | 08:30 | |
-queuebot:#ubuntu-release- Unapproved: snapd (bionic-proposed/main) [2.32.8+18.04 => 2.32.9+18.04] (desktop-core, ubuntu-server) | 08:32 | |
-queuebot:#ubuntu-release- Unapproved: snapd (trusty-proposed/universe) [2.32.5~14.04 => 2.32.9~14.04] (no packageset) | 08:34 | |
-queuebot:#ubuntu-release- Unapproved: util-linux (artful-proposed/main) [2.30.1-0ubuntu4.1 => 2.30.1-0ubuntu4.2] (core) | 10:51 | |
-queuebot:#ubuntu-release- Unapproved: util-linux (xenial-proposed/main) [2.27.1-6ubuntu3.5 => 2.27.1-6ubuntu3.6] (core) | 10:51 | |
-queuebot:#ubuntu-release- Unapproved: util-linux (bionic-proposed/main) [2.31.1-0.4ubuntu3 => 2.31.1-0.4ubuntu3.1] (core) | 10:52 | |
juliank | ^ these 3 are to fix bug 1771345 so we can hopefully get bug 1732865 working | 10:53 |
ubot5 | bug 1771345 in util-linux (Ubuntu Bionic) "lscpu possible crash in min/max frequency" [High,Triaged] https://launchpad.net/bugs/1771345 | 10:53 |
ubot5 | bug 1732865 in The Ubuntu-power-systems project "[LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies" [High,Fix committed] https://launchpad.net/bugs/1732865 | 10:53 |
sil2100 | juliank: if the vanguard doesn't take care of those today, I'll pick them up tomorrow for sure | 11:13 |
rbasak | juliank: how do you intend to perform SRU verification on that? | 13:00 |
ginggs | doko: re openmpi, see debian #896886 - and armhf doesn't look good in debian either, maintainers are doing this: https://packages.qa.debian.org/l/lammps/news/20180515T163856Z.html - fortunately there's a 3.1.0 bugfix release | 13:13 |
ubot5 | Debian bug 896886 in src:openmpi "openmpi: upstream version 3.0.1 makes lots of autopkgtests flaky" [Normal,Open] http://bugs.debian.org/896886 | 13:13 |
juliank | rbasak: That's a good question, I'm not sure we can actually verify anything there. But if IBM can verify 1732865, we would know it's enough. I'd treat this more as a "make code more defensive" rather than "fix concrete bug" | 13:14 |
juliank | Unless you have an AMD system where you can disable a CPU that produces the bug, then you're lucky | 13:14 |
doko | ginggs: is this disabled for the autopkg tests as well? | 13:15 |
juliank | or the POWER8 which apparently also does on some systems | 13:15 |
-queuebot:#ubuntu-release- New: accepted oca-core [amd64] (cosmic-proposed) [11.0.20180420-1] | 13:15 | |
juliank | rbasak: I guess we can also produce test cpuinfo files that trigger it, but I'm not sure how that all works | 13:18 |
juliank | I just thought about that now, that would have been a good way to get the other bug reproducable | 13:18 |
juliank | Got it | 13:23 |
ginggs | doko: well the ones that run tests during the build FTBFS, and the ones that run tests during autopkgtest fail there :( | 13:27 |
ginggs | doko: in the case of lammps, I guess it is going to fail autopkgtests once it builds | 13:28 |
rbasak | juliank: OK. Let me know once you've updated everything then, and I'll take another look? | 13:29 |
juliank | rbasak: done | 13:33 |
juliank | I wonder why upstream did not add a test for that to their testsuite... | 13:36 |
ginggs | doko: mckinstry responded on the openmpi bug | 14:09 |
doko | ginggs: which one? | 14:16 |
-queuebot:#ubuntu-release- Unapproved: gnutls28 (trusty-proposed/universe) [3.2.11-2ubuntu1.1 => 3.2.11-2ubuntu1.2] (no packageset) | 14:18 | |
juliank | um, we now have two gnutls28 3.2.11-2ubuntu1.2 in the queue for trusty, the older one should probably go away | 14:19 |
Odd_Bloke | rbasak: arges: The cloud-init in bionic-proposed has been verified and waiting around for a while; would one of you be able to release it? | 14:20 |
Odd_Bloke | dpb1: ^, FYI | 14:20 |
arges | Odd_Bloke: sure | 14:21 |
Odd_Bloke | Thanks! | 14:21 |
arges | Odd_Bloke: done | 14:22 |
Odd_Bloke | \o/ | 14:23 |
* rbasak is still trying to figure out juliank's util-linux SRUs | 14:23 | |
juliank | rbasak: but they're so tiny! | 14:24 |
juliank | :) | 14:24 |
rbasak | There are rather a large number of bug comments, uploads and patches for something so tiny :) | 14:25 |
rbasak | I like your segvtest case | 14:26 |
juliank | rbasak: Oh, on the IBM one, yes, but that one is just carried over from the one currently in proposed. | 14:26 |
rbasak | dep3 origin headers would have been nice :-/ | 14:28 |
juliank | rbasak: Um, yeah, but I just git formatted them from the upstream repo, and quilt imported them | 14:30 |
juliank | and did quilt refresh | 14:30 |
rbasak | You can do that but still add dep3 headers | 14:30 |
rbasak | dep3 was designed with that use case in mind | 14:30 |
rbasak | Do you have a pointer to the upstream VCS please? | 14:30 |
juliank | it's https://github.com/karelzak/util-linux | 14:31 |
rbasak | Thanks | 14:31 |
mdeslaur | is there a publisher problem? I publish three packages 3 hours ago, and half the binary packages are still missing... | 14:32 |
mdeslaur | ie: http://security.ubuntu.com/ubuntu/pool/main/d/dpdk/librte-eal17.05_17.05.2-0ubuntu1.1_i386.deb | 14:32 |
apw | mdeslaur, half of them missing? that seems unexpected | 14:32 |
cjwatson | The weekly publisher DB vacuuming has cycled round to this time of the week | 14:33 |
cjwatson | So it'll sort itself out once that's done | 14:33 |
cjwatson | half> presumably those for whichever architectures built later | 14:33 |
mdeslaur | thanks cjwatson | 14:34 |
apw | cjwatson, can we not control when that thing happens? make it happen more and at a consistent time or something | 14:34 |
cjwatson | apw: infinity was going to work on that | 14:36 |
apw | ahh ok :) | 14:36 |
-queuebot:#ubuntu-release- Unapproved: accepted util-linux [source] (xenial-proposed) [2.27.1-6ubuntu3.6] | 14:55 | |
-queuebot:#ubuntu-release- Unapproved: accepted util-linux [source] (artful-proposed) [2.30.1-0ubuntu4.2] | 14:56 | |
rbasak | juliank: that was rather complicated because of the previous SRU in Xenial and the other subtle differences between the releases. Looks like you've done it all correctly though, thanks. | 14:56 |
-queuebot:#ubuntu-release- Unapproved: accepted util-linux [source] (bionic-proposed) [2.31.1-0.4ubuntu3.1] | 14:56 | |
slangasek | Laney, sil2100, juliank: so now that I'm receiving emails, I notice a pattern that s390x nodes are failing much more than other architectures. Do we know why? Do we think this is a priority to fix? | 14:59 |
Laney | slangasek: I didn't look into it yet. Seems to be mostly bos01 which is new, and bos02 is working fine, so this isn't a top priority for me. Feel free to have a look though. If it were me I'd run a manual job through bos01 and see what happens. | 15:03 |
Laney | Congratulations on your emailhood. | 15:03 |
slangasek | Laney: confirmed, all the ones I'm seeing over the past 24h are bos01. Do you think I should escalate it to axino? | 15:05 |
juliank | slangasek: I see a lot of instance quota exceeded | 15:05 |
juliank | So we should lower our number of instances or get the quota raised | 15:06 |
Laney | Dunno, I would find out what the problem is first. | 15:06 |
juliank | Apparently the quota limit is 10 | 15:06 |
Laney | If it's quota, give that ticket a score bump | 15:06 |
slangasek | juliank: you don't see that in the emails, do you? I'm not finding anything about quotas there | 15:06 |
juliank | and we configure 16? | 15:06 |
juliank | in journalctl | 15:07 |
slangasek | it's not clear to me that 'raise the quota' is correct here, this is bos01 that we're still doing burn-in testing on | 15:07 |
slangasek | and has less compute available | 15:07 |
Laney | We set our limits based on the compute that IS told us was there | 15:07 |
slangasek | ah | 15:08 |
juliank | but there was some miscommunication on #instances | 15:08 |
slangasek | ...what is this channel | 15:08 |
juliank | s/#/number of/ | 15:08 |
juliank | :) | 15:08 |
slangasek | oh :) | 15:08 |
Laney | what miscommunication is that? | 15:09 |
Laney | there's some miscommunication if there is miscommunication that is not being communicated to the team | 15:09 |
juliank | Laney: with them thinking we had lower number of workers on bos02, and giving us lower limits? | 15:10 |
juliank | which you suggested we go higher, I don't think they actually replied to that | 15:10 |
Laney | oh right, I think the quota is just not set up properly yet | 15:10 |
Laney | that's why I suggest a score bump to get that done rather than fiddling on our side | 15:10 |
ginggs | doko: debian #896886 | 15:14 |
ubot5 | Debian bug 896886 in src:openmpi "openmpi: upstream version 3.0.1 makes lots of autopkgtests flaky" [Normal,Open] http://bugs.debian.org/896886 | 15:14 |
slangasek | Laney: RT#? | 15:26 |
Laney | 1stuff | 15:26 |
Laney | slangasek: 111085 | 15:27 |
slangasek | ticket nudged | 15:28 |
Laney | neat | 15:29 |
doko | ginggs: does 3.1 have another soname bump? | 15:36 |
ginggs | doko: I haven't checked, but I believe it is just bug fixes | 15:37 |
-queuebot:#ubuntu-release- Unapproved: llvm-defaults (bionic-proposed/universe) [0.41~exp4 => 0.41~exp5~ubuntu1] (no packageset) | 16:20 | |
-queuebot:#ubuntu-release- Unapproved: python-pip (bionic-proposed/universe) [9.0.1-2 => 9.0.1-2.3~ubuntu1] (no packageset) | 16:31 | |
-queuebot:#ubuntu-release- New binary: python-os-service-types [amd64] (cosmic-proposed/main) [1.2.0-0ubuntu1] (ubuntu-server) | 16:37 | |
-queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.31] | 16:43 | |
ahasenack | hi, I need some help with my apache2 migration. It's a valid candidate, but failing because of: | 16:45 |
ahasenack | trying: apache2 | 16:45 |
ahasenack | skipped: apache2 (0, 56, 7) | 16:45 |
ahasenack | got: 15+0: a-8:a-1:a-1:i-1:p-3:s-1 | 16:45 |
ahasenack | * ppc64el: libapache2-mod-proxy-uwsgi-dbg, libapache2-mod-shib2 | 16:45 |
ahasenack | it's not ppc64 specific, I can see that in an amd64 container | 16:45 |
ahasenack | thing is, that problem is already the case in current cosmic | 16:45 |
ahasenack | libapache2-mod-shib2 wants libxmltooling7 which pulls in libcurl3 | 16:45 |
ahasenack | instead of libcurl4 | 16:45 |
ahasenack | and I think it's because it has to be be built against openssl1.0, not 1.1, and libcurl-openssl1.0-dev pulls in libcurl3 | 16:46 |
-queuebot:#ubuntu-release- Unapproved: clamfs (bionic-proposed/universe) [1.0.1-3build2 => 1.0.1-3build3] (no packageset) | 16:46 | |
-queuebot:#ubuntu-release- Unapproved: gpsshogi (bionic-proposed/universe) [0.7.0-2build4 => 0.7.0-2build5] (no packageset) | 16:47 | |
-queuebot:#ubuntu-release- Unapproved: ros-class-loader (bionic-proposed/universe) [0.3.8-1build2 => 0.3.8-1build3] (no packageset) | 16:47 | |
ahasenack | xmltooling has this as its last changelog entry: | 16:47 |
ahasenack | * Switch back to openssl1.0 via newly-added libcurl-openssl1.0-dev, since | 16:47 |
ahasenack | libxml-security is not ported to openssl1.1. | 16:47 |
-queuebot:#ubuntu-release- Unapproved: sitplus (bionic-proposed/universe) [1.0.3-5.1build5 => 1.0.3-5.1build6] (no packageset) | 16:47 | |
slangasek | ahasenack: so, what has changed in apache that would cause this to be incompatible now? Was apache2 not already linked against openssl 1.1 in bionic? | 16:47 |
ahasenack | I'm seeing that in cosmic's apache, 2.4.29-1ubuntu4.1, which is the same as in bionic-updates | 16:48 |
ahasenack | I think what changed is libxmltooling7 being build with openssl1.0 after apache was uploaded | 16:48 |
ahasenack | libapache2-mod-shib2 -> libxmltooling7 -> libcurl3 | 16:49 |
slangasek | ahasenack: that would not increase the count of uninstallable packages, which is what proposed-migration cares about | 16:49 |
ahasenack | xmltooling was built with openssl1.1 for a while | 16:49 |
ahasenack | slangasek: you mean, if this was the case before, proposed-migration would have ignored this error? | 16:50 |
slangasek | ahasenack: correct | 16:50 |
ahasenack | what is the diff now, is it exactly libapache2-mod-proxy-uwsgi-dbg and libapache2-mod-shib2? | 16:50 |
ahasenack | and apache didn't change, I'm seeing libapache2-mod-shib2 not being installable in normal cosmic. I think what changed is xmltooling7, as that would not try to install apache to test | 16:51 |
ahasenack | I mean, would the xmltooling7 migration test that libapache2-mod-shib2 is installable? | 16:52 |
slangasek | it would, yes | 16:52 |
ahasenack | well, it isn't | 16:52 |
slangasek | ahasenack: in cosmic, libapache2-mod-shib2 is installable (though not coinstallable with other things) | 17:00 |
ahasenack | like apache itself :) | 17:01 |
slangasek | ahasenack: in cosmic-proposed, it is not installable because apache2-bin now depends on libcurl4 where it did not previously | 17:01 |
ahasenack | oh, hm | 17:01 |
ahasenack | ok, that gives me enough to go on | 17:02 |
ahasenack | thanks | 17:02 |
-queuebot:#ubuntu-release- Unapproved: rejected clamfs [source] (bionic-proposed) [1.0.1-3build3] | 17:17 | |
-queuebot:#ubuntu-release- Unapproved: rejected ros-class-loader [source] (bionic-proposed) [0.3.8-1build3] | 17:17 | |
-queuebot:#ubuntu-release- Unapproved: rejected gpsshogi [source] (bionic-proposed) [0.7.0-2build5] | 17:17 | |
-queuebot:#ubuntu-release- Unapproved: rejected sitplus [source] (bionic-proposed) [1.0.3-5.1build6] | 17:17 | |
ahasenack | slangasek: ok, it's this new experimental module that is enabled by default: https://httpd.apache.org/docs/2.4/mod/mod_md.html | 18:06 |
ahasenack | slangasek: so my choices are disabling it (adding a delta with debian) or getting libxmltooling7 to use libcurl4 instead of libcurl3, I think | 18:06 |
ahasenack | or something more complicated | 18:06 |
ahasenack | and we have libapache2-mod-md in the archive already, from somewhere else | 18:32 |
* ahasenack will think about this | 18:32 | |
slangasek | ahasenack: nothing is more complicated than getting libxmltooling7 to use libcurl4 | 18:39 |
ahasenack | I see | 18:39 |
slangasek | what about splitting mod_md out into a separate binary package? I don't see why a new experimental module should cause the apache core packages to depend on libcurl | 18:40 |
ahasenack | it's a module we have already in the archive at an older version, as a source package, just like debian | 18:40 |
ahasenack | so maybe to that, split it out (as it's already like this in a way) | 18:41 |
ahasenack | and obsolete the old mod-md source | 18:41 |
ahasenack | it will just add to the debian delta, though | 18:41 |
ahasenack | I was about to check what debian does with libxmltooling7 | 18:41 |
ahasenack | oh, wait a sec | 18:45 |
slangasek | libxmltooling7 has a horrible dependency tree of xmlsec stuff that needs upstream porting to openss1.1 before that stack can be switched | 18:46 |
ahasenack | huh, in debian libcurl.so.4 is in the libcurl3 package | 18:51 |
ahasenack | lrwxrwxrwx 1 root root 12 Jan 24 20:27 /usr/lib/x86_64-linux-gnu/libcurl.so.3 -> libcurl.so.4 | 18:52 |
ahasenack | weirddd... | 18:52 |
slangasek | it's because a determination was made that it shouldn't be considered an ABI break for Debian even though upstream considered it one | 18:59 |
ahasenack | in or case, we can't install libcurl3 simultaneously with libcurl4, we have an explicit conflicts | 19:00 |
-queuebot:#ubuntu-release- New binary: rustc [s390x] (cosmic-proposed/universe) [1.25.0+dfsg1+llvm-0ubuntu3] (no packageset) | 19:00 | |
slangasek | yes | 19:00 |
slangasek | basically the same thing that Debian is meant to have soonish | 19:01 |
ahasenack | hm, in ubuntu we do something similar in libcurl3-gnutls. It includes this symlink: libcurl-gnutls.so.3 -> libcurl-gnutls.so.4 | 19:18 |
ahasenack | curl sounds like a complicated package | 19:18 |
infinity | "Complicated" is a very kind description. | 19:23 |
tsimonq2 | infinity, slangasek: Moar Lubuntu Classic cleanup: https://code.launchpad.net/~wxl/ubiquity-slideshow-ubuntu/delete-lubuntu/+merge/345637 | 19:34 |
-queuebot:#ubuntu-release- Unapproved: x11-xkb-utils (bionic-proposed/main) [7.7+3 => 7.7+3ubuntu1] (desktop-core) | 19:45 | |
slangasek | tsimonq2: merged | 19:47 |
slangasek | and uploaded | 19:47 |
tsimonq2 | Thanks! | 19:48 |
tsimonq2 | wxl: ^ | 19:48 |
-queuebot:#ubuntu-release- New binary: rustc [ppc64el] (cosmic-proposed/universe) [1.25.0+dfsg1+llvm-0ubuntu3] (no packageset) | 20:13 | |
slangasek | Laney, sil2100, juliank: hmmm, mininet/i386 autopkgtests are failing with timeouts; that's irritating and I'm investigating, but what's surprising is they're allowed to take 6h to time out instead of 10000s, has anything changed in configs? http://autopkgtest.ubuntu.com/packages/m/mininet/cosmic/i386 | 20:27 |
juliank | slangasek: hmm | 20:29 |
slangasek | juliank: probably not a recent config change, looking at bionic history I see a similar timeout from 17Apr | 20:29 |
juliank | slangasek: it timed out properly after 10k seconds, but it took 3 hours to clean up the instance | 20:35 |
juliank | autopkgtest [13:47:34]: test simpe: [ | 20:36 |
juliank | autopkgtest [16:34:14]: ERROR: timed out | 20:36 |
slangasek | oh fun | 20:36 |
juliank | autopkgtest-virt-ssh [19:54:14]: ERROR: Removing temporary files on testbed timed out | 20:36 |
slangasek | so where does that timeout need to be lowered? ;) | 20:37 |
juliank | slangasek: It's supposed to be a 300s timeout in AUTOPKGTEST_VIRT_COPY_TIMEOUT in VirtSubproc.p | 20:39 |
juliank | y | 20:39 |
juliank | if cleanup_paths: | 20:39 |
juliank | VirtSubproc.check_exec(['rm', '-rf'] + cleanup_paths, downp=True, | 20:39 |
juliank | timeout=VirtSubproc.copy_timeout) | 20:39 |
juliank | though for that only | 20:39 |
juliank | it also calls VirtSubproc.downtmp_remove() before that | 20:39 |
juliank | but that should have the same timeout | 20:39 |
juliank | Maybe we increased AUTOPKGTEST_VIRT_COPY_TIMEOUT somewhere? | 20:41 |
juliank | ok, that one is set from --timeout-copy apparently | 20:42 |
juliank | which is nuts, because we pass --timeout-copy=6000 | 20:42 |
slangasek | 6000s seems a bit excessive :) | 20:42 |
juliank | so we have 1.6 hours to remove downtmp, and then 1.6 hours to remove cleanup_paths | 20:43 |
slangasek | dates to the origin of the git repo, so no particular rationale there | 20:44 |
juliank | my suggestion: https://paste.ubuntu.com/p/j7fWRBmZzY/ | 20:44 |
slangasek | I think the copy timeout should also be lowered, though certainly we should have a different timeout value for removal vs copying | 20:45 |
-queuebot:#ubuntu-release- Unapproved: initramfs-tools (trusty-proposed/main) [0.103ubuntu4.10 => 0.103ubuntu4.11] (core) | 20:46 | |
slangasek | ototh why is 'ssh rm -rf [...]' hanging for 1h? do we have some terrible retry handling in there? | 20:47 |
juliank | does not seem like it | 20:50 |
juliank | but there's some weird wrapper that kills processes | 20:51 |
-queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (artful-proposed/universe) [20180129+dfsg1-0ubuntu1~17.10.0 => 20180510+dfsg1-0ubuntu2~17.10.0] (ubuntu-cloud) | 21:03 | |
-queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (xenial-proposed/universe) [20180129+dfsg1-0ubuntu1~16.04.0 => 20180510+dfsg1-0ubuntu2~16.04.0] (ubuntu-cloud) | 21:03 | |
-queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (bionic-proposed/universe) [20180129+dfsg1-0ubuntu3 => 20180510+dfsg1-0ubuntu2~18.04.0] (ubuntu-cloud) | 21:04 | |
-queuebot:#ubuntu-release- New binary: rustc [amd64] (cosmic-proposed/universe) [1.25.0+dfsg1+llvm-0ubuntu3] (no packageset) | 21:09 | |
slangasek | jbicha: it appears network-manager-gnome has now migrated from libappindicator to libayatana-appindicator. The libappindicator package in main was owned by ~dx-packages, which is effectively no more; do you know if ubuntu-desktop means to own ayatana-appindicator? | 21:23 |
jbicha | slangasek: I pinged seb128 about that this week and it's on his todo list to look into that MIR | 21:25 |
slangasek | jbicha: I wouldn't expect to need an MIR since this is effectively a package rename and a straight swap in main, but I do need to know what team will own maintenance | 21:26 |
jbicha | could you follow up with Seb about that? | 21:27 |
slangasek | provided I catch him on IRC :) | 21:28 |
xnox | slangasek, there is s390x in bos01?! news to me. | 21:35 |
slangasek | xnox: yes; it's the new bos01 | 21:35 |
xnox | cool. | 21:36 |
wxl | infinity et al are multiple verifications required for https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1764399 or are we good to go? i've changed verification-needed-bionic per the instructions but did not change verification-needed. | 21:40 |
ubot5 | Ubuntu bug 1764399 in lubuntu-meta (Ubuntu Cosmic) "running apport in terminal doesn't work, as python3-launchpadlib is not installed by default in Lubuntu Bionic" [Critical,Fix committed] | 21:40 |
bdmurray | wxl: verification-needed doesn't actually do anything | 21:48 |
wxl | bdmurray: okie dokie. do i need to round up additional testers? | 21:49 |
bdmurray | the description talks about crash reports but apport-collect is for bug reports | 21:50 |
bdmurray | Anyway, enough being pedantic. It seems straight forward no additional testing is needed. | 21:51 |
wxl | i blame tsimonq2 :) | 21:52 |
-queuebot:#ubuntu-release- New binary: rustc [i386] (cosmic-proposed/universe) [1.25.0+dfsg1+llvm-0ubuntu3] (no packageset) | 21:55 | |
slangasek | ginggs: if you would like a SIGBUS to diagnose, seqan2's current build failure /is/ reproducible with bionic: https://paste.ubuntu.com/p/NVHbJhfstC/ | 22:41 |
-queuebot:#ubuntu-release- New binary: rustc [armhf] (cosmic-proposed/universe) [1.25.0+dfsg1+llvm-0ubuntu3] (no packageset) | 23:17 | |
-queuebot:#ubuntu-release- New binary: gitless [amd64] (cosmic-proposed/universe) [0.8.6-1] (no packageset) | 23:21 | |
-queuebot:#ubuntu-release- New binary: hbci4java [amd64] (cosmic-proposed/universe) [3.0.15+dfsg-2] (no packageset) | 23:28 | |
-queuebot:#ubuntu-release- New: accepted gitless [amd64] (cosmic-proposed) [0.8.6-1] | 23:45 | |
-queuebot:#ubuntu-release- New: accepted hbci4java [amd64] (cosmic-proposed) [3.0.15+dfsg-2] | 23:45 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!