/srv/irclogs.ubuntu.com/2018/09/13/#ubuntu-release.txt

stgraberhmm, so the latest LXD upload effectively switches from 3 binary packages per-arch to a single arch-all package, is there any way to make proposed-migration happy enough with that so it starts running autopkgtests?03:11
stgraberlooking at docs, looks like the solution to unstick this is to remove those binaries from the release pocket, but that'd break people at this point...03:11
stgraber(I'm fine doing the package removal from the release pocket once I know that the new package will migrate within the hour, but right now I specifically don't want it to migrate yet I want adt to do its thing)03:12
-queuebot:#ubuntu-release- Unapproved: qemu (xenial-proposed/main) [1:2.5+dfsg-5ubuntu10.31 => 1:2.5+dfsg-5ubuntu10.32] (ubuntu-server, virt)05:07
apwstgraber, do those break the originals ?07:34
apwetc07:34
apwstgraber, could you not make both of those going away binaries transitionals, and would this both allow this to migrate _and_ effectivly deinstall the now redundant packages07:40
apwthen they would be removable in -release in a subsequent upload07:45
apwas nothing is in them07:45
-queuebot:#ubuntu-release- New binary: linux-signed [amd64] (trusty-proposed/main) [3.13.0-159.209] (core, kernel)08:58
-queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-136.162~14.04.1] (kernel)09:00
-queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-136.162~14.04.1]09:11
-queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-159.209]09:11
cpaelzersil2100: you are on SRU duty right now correct?09:24
cpaelzerI wanted to ask if you could cancel 1:2.11+dfsg-1ubuntu7.6 from bionic unapproved09:24
cpaelzerit is good, but I have two more changes complete and want to minimize how often people have to update09:25
cpaelzerso I'd want to bundle those two more changes and re-upload09:25
cpaelzerbut be careful, there also is an upload in xenial-unapproved, do not cancel that one (it is unrelated)09:26
sil2100cpaelzer: ok!09:32
cpaelzerthank you sil210009:33
sil2100Done ;)09:33
-queuebot:#ubuntu-release- Unapproved: rejected qemu [source] (bionic-proposed) [1:2.11+dfsg-1ubuntu7.6]09:34
dokoLocutusOfBorg: your automake 1.16 update broke dozens of builds ...09:37
LocutusOfBorgdoko, can I see them?09:45
dokoe.g. newt. currently running the test rebuild09:49
LocutusOfBorgjuliank, ^^ please merge it?09:53
juliankum09:53
juliankbetter cancel the automake update?09:53
LocutusOfBorgafter it has been removed from the archive and the new package migrated?09:54
juliankWell, I don't know what you did09:55
LocutusOfBorgmigrated 20 days ago...09:55
LocutusOfBorgjuliank, followed the change from automake 1.15 to 1.1609:55
LocutusOfBorgand some bad programs doing bad things, hardcoding stuff, breaks09:55
rbasaksil2100, bdmurray: I didn't manage to get back to gnome-software in Xenial unapproved yesterday. I'll finish it off now.09:55
LocutusOfBorgjuliank, I can steal newt if you want09:56
LocutusOfBorgthe fix is two lines09:56
juliankI'd like to figure out why you merge automake 1.16 after the feature freeze09:57
LocutusOfBorgI asked here, and I got "ok to go"09:57
LocutusOfBorgbecause there was still time to fixup stuff09:57
juliankWell, ok09:58
LocutusOfBorgand there aren't new "features" in new automake, just bugfixes09:58
LocutusOfBorgstuff is not breaking because of actual changes, but because "export AUTOMAKE 1.15" and similar09:58
cjwatsonDid you?  I see you asking, but no explicit yes09:58
juliankSo packages have missing Depends: automake (<< 1.16)09:59
cjwatsonWell, it would have required somebody to process NEW, but that's a different headspace09:59
juliank(that's what they should have so you can actually notice them)09:59
juliankCan someone run a search for 1.15 in the archive?10:00
juliankso we know what breaks?10:00
LocutusOfBorgjuliank, do you have any idea about how to do it?10:00
LocutusOfBorgcjwatson, actually automake has been uploaded in early august in debian, for some reasons really obscure to me, it didn't get autosyncd10:01
LocutusOfBorgand it was 24 hours after the freeze, yes10:01
juliankI think security team has a script for greeping source packages10:01
LocutusOfBorgoh... lets move there maybe10:01
cjwatsonDoesn't seem obscure, you even pasted the reason10:01
cjwatson<LocutusOfBorg> automake-1.16_1:1.16.1-1 is trying to override modified binary automake_1:1.15.1-3ubuntu2.  OK (y/N)?  n10:01
cjwatsonSources that would produce binary packages that currently have Ubuntu deltas don't get autosynced for what I would hope would be entirely clear reasons10:02
LocutusOfBorgok so I don't remember anymore after 20 days, and my irc history doesn't go that far10:02
LocutusOfBorgcjwatson, probably I remember "why the hell the delta is a stupid 2 line autopkgtestsuite and nobody ever pushed it to debian in years"10:02
LocutusOfBorgand then I filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=90691910:03
ubot5Debian bug 906919 in automake-1.16 "automake-1.16: please enable testsuite [PATCH]" [Important,Open]10:03
sil2100rbasak: ok!10:03
sil2100rbasak: thanks for the heads up10:03
juliankLocutusOfBorg: FWIW; I don't see anybody responding to you, but someone did let it pass NEW10:04
LocutusOfBorgbtw, the "dozen" might be actual 3 packages10:04
LocutusOfBorghttps://codesearch.debian.net/search?q=1%5C.15+path%3Adebian%2Frules10:04
cjwatsonSounds like doko has more examples?10:05
LocutusOfBorgI hope so10:05
LocutusOfBorgand the package above results in the search10:05
julianklibjpeg9: export AUTOMAKE = automake-1.1510:06
juliankugh10:06
juliankShould add a lintian check "hardcoded autotools versions"10:06
juliankekg210:06
juliankicecast2 are the others10:06
LocutusOfBorgnewt "libjpeg9?" (not sure) ekg2 and icecast210:07
LocutusOfBorgyes, exactly10:07
juliankWhen bumping to 1.16, it would make sense to add proper Build-Depends: automake (<< 1.17)10:08
juliankso things get noticed more easily10:08
cjwatsonOr just unhardcode10:08
LocutusOfBorgdo you care to file a bug?10:08
juliankThat would be nicer10:08
LocutusOfBorgright now I'm fixing ekg2 to stop hardcoding10:09
juliankHow?10:09
juliankAre you using dpkg to query version of automake and then sed it correclty?10:09
julianki.e. AM_VERSION=$(shell dpkg-query -f '\${source:Upstream-Version}' -W automake | egrep -o '^[0-9]+\.[0-9]+')10:11
juliankor just hardcode AUTOMAKE = automake10:11
juliankwell, remove the vars10:11
-queuebot:#ubuntu-release- Unapproved: rejected freshplayerplugin [source] (xenial-proposed) [0.3.9-0ubuntu0~16.04.1]10:12
-queuebot:#ubuntu-release- Unapproved: freshplayerplugin (xenial-proposed/multiverse) [0.3.4-3ubuntu0.1 => 0.3.9-0ubuntu0.16.04.1] (no packageset)10:12
-queuebot:#ubuntu-release- Unapproved: accepted freshplayerplugin [source] (xenial-proposed) [0.3.9-0ubuntu0.16.04.1]10:15
-queuebot:#ubuntu-release- Unapproved: metacity (bionic-proposed/universe) [1:3.28.0-1 => 1:3.28.0-1ubuntu0.1] (ubuntu-desktop)10:19
LocutusOfBorgjuliank, the latter10:19
LocutusOfBorgekg2 is fixed for real now10:21
juliankI send the $(shell) invocation to Debian for newt10:21
juliankI did not check quoting, though10:21
LocutusOfBorgthanks!10:22
LocutusOfBorgicecast2 is good now10:22
rbasaksil2100, bdmurray: gnome-software looks good to me, except that there's one change with no bug reference that enables a patch that was supposed to be added in a previous SRU but never functionally landed (missing from series). The changelog says "Add patch that seemed to get missed in 3.20.5-0ubuntu0.16.04.10". That previous upload listed two bugs that were marked verification-done, but AFAICT that10:22
rbasakwas false since the patch was never enabled. So should I ask for those two bugs to be reopened and the changelog to include them so they can be reverified? Opinions?10:22
rbasakI don't see robert_ancell online - out of time zone I guess.10:23
juliankIt's actually10:23
juliankAM_VERS:=$(shell dpkg-query -f '$${source:Upstream-Version}' -W automake | egrep -o '^[0-9]+\.[0-9]+')10:23
LocutusOfBorgwhat about dropping that variable?10:24
LocutusOfBorg        cp /usr/share/automake-$(AM_VERS)/install-sh ./install-sh10:25
LocutusOfBorgseriosly because of this^10:25
LocutusOfBorg?10:25
juliankLocutusOfBorg: Well, it's clearly needed here10:26
LocutusOfBorgcp /usr/share/automake-*/install-sh ./install-sh10:27
juliankReplacing $(AM_VERS) with * would work sometime10:27
juliankbut not if you have automake-1.11 installed I guess10:27
LocutusOfBorgyes I know it doesn't with automake 1.11 and 1.1510:27
LocutusOfBorgI'm trying to find if --add-missing or whatever works10:27
LocutusOfBorgyou know, there is some obscure automake stuff10:27
LocutusOfBorgfor this10:27
juliankbug 90873910:27
ubot5bug 908739 in Odoo Addons (MOVED TO GITHUB) "web : compagin ugly screen" [Low,Fix released] https://launchpad.net/bugs/90873910:27
juliankin debian10:27
juliankhttps://bugs.debian.org/90873910:27
ubot5Debian bug 908739 in src:newt "newt: Do not hardcode automake version" [Normal,Open]10:28
juliankthere we go10:28
LocutusOfBorgnice!10:28
LocutusOfBorgI hope to find a better solution btw :)10:28
juliankI don't know why I had to use $(strip) around the dpkg-query | egrep10:28
juliankor why I did not use cut -1-2 -d.10:28
juliankoh well, this probably works better in case of an alpha or stuff10:29
LocutusOfBorgjuliank, please10:29
LocutusOfBorgAUTOMAKE_FLAGS="--add-missing --copy"10:29
LocutusOfBorgend of the story10:29
juliankLocutusOfBorg: Tell the bug report10:29
LocutusOfBorgmmm didn't work :/10:29
juliank:)10:29
* LocutusOfBorg tries with a bigger hammer10:30
juliankLocutusOfBorg: Where does _FLAGS come from?10:31
juliankAUTOMAKE=automake --add-missing --copy10:31
juliankis what I'd do10:31
juliankthat's what autoreconf(1) documents10:31
juliankLocutusOfBorg: Ah, duh, there's no automake in the build10:32
juliankonly a Makefile.in, no Makefile.am10:33
juliankLocutusOfBorg: That said, it seems wrong to have the file in the first place10:36
juliankI mean, Makefile.in defines an install-sh target for install shared library10:36
dokocpaelzer: online? pmdk10:36
juliankand the Makefile does not use install-sh10:37
juliankI mean, it uses AC_PROG_INSTALL in configure10:38
juliankbut then it has to use $(INSTALL), not install10:38
LocutusOfBorgI feel so dirty10:39
LocutusOfBorgbut doing this works10:39
LocutusOfBorgAUTOMAKE=/usr/bin/automake --add-missing --copy --foreign10:39
LocutusOfBorg$(AUTOMAKE) || true10:39
LocutusOfBorgin configure, because automake fails, but after having copied the file :)10:40
juliankFWIW, python-newt should be called python-snack, it provides a snack module, no newt module10:40
juliankLocutusOfBorg: The cp is cleaner than that, though10:40
LocutusOfBorgsure juliank :) I want to hide in a cave10:40
juliankLocutusOfBorg: Patching out the check for AC_PROG_INSTALL is even easier10:41
juliankSince Makefile.in does not use $(INSTALL)...10:41
juliankI think it's a bug in autoconf10:42
juliankautoconf should copy install-sh as needed10:42
juliankIt can't rely on libtool or automake to do it10:42
LocutusOfBorgI confirm, removing PROG_INSTALL works... mind to update the bug report? :)10:43
LocutusOfBorgand do the upload if you can, so I can focus on libjpeg910:43
LocutusOfBorg(the last one for me)10:43
juliankLocutusOfBorg: I already did the newt merge so we're good for now, I'm not introducing a delta for this10:45
julianks/introducing/increasing/10:45
LocutusOfBorgack but maybe adding a patch to the bug report?10:46
juliankWell, he can remove a line himself10:47
juliankI also reported a bug to merge the built -> build change in python{3,}-newt10:48
juliank:)10:49
LocutusOfBorgnice, indeed!10:49
juliankLocutusOfBorg: Probably file an RC bug in Debian then with the libjpeg9 fix10:49
LocutusOfBorglibjpeg9 is fine without anything of that hardcoding https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/1545300910:50
LocutusOfBorgsure, an RC is what I plan to do10:50
cpaelzerdoko: I was out for lunch10:55
cpaelzerwhat is up with pmdk?10:55
cpaelzerwould be ahasenack btw, but he is out until the sprint10:55
cpaelzerdoko: saw your questions on the bug10:56
cpaelzerall the questions are fine to be answered at the sprint next week I think10:57
cpaelzerthanks for taking a look10:57
cpaelzerjemalloc being bundled in there is interesting, didn't realize that before10:58
cpaelzerI'm not trying to half-answer the questions, I'm sure it will be better if I do so together with ahasenack10:58
LocutusOfBorgjuliank, debian bug: #90874111:27
ubot5Debian bug 908741 in src:libjpeg9 "libjpeg9: do not hardcode automake version" [Serious,Open] http://bugs.debian.org/90874111:27
dokohttp://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180911-cosmic.html11:39
dokoLocutusOfBorg: ^^^11:39
LocutusOfBorgwhy is pkg-stripfiles so slow since yesterday? https://launchpad.net/ubuntu/+source/ekg2/1:0.4~pre+20120506.1-14ubuntu1/+build/1545290111:39
LocutusOfBorghours to finish a job of seconds...11:39
LocutusOfBorgdoko, ack11:39
dokoof course, not yet finished11:41
LocutusOfBorgI only found one possible, I looked at all main logs11:48
LocutusOfBorg(only logs where failure was in every architectures, since autoreconf is a problem everywhere)11:49
LocutusOfBorgjuliank, dpkg fails for a similar reason, do you think it is sane to change aclocal.m4 into ./aclocal.m4:[am__api_version='1.16'12:00
LocutusOfBorg./aclocal.m4:m4_if([$1], [1.16], [],12:00
LocutusOfBorg ?12:00
juliankaclocal should be regenerated12:00
juliankIs dpkg not running dh-autoreconf or overriding aclocal?12:00
LocutusOfBorgdebian/rules:autoreconf -v -i12:01
LocutusOfBorgno aclocal overrides12:01
LocutusOfBorgnice, works  in debian...12:02
juliankodd stuff12:02
-queuebot:#ubuntu-release- Unapproved: gnome-flashback (bionic-proposed/universe) [3.28.0-1ubuntu1.1 => 3.28.0-1ubuntu1.2] (edubuntu)12:30
dokojbicha, seb128: why isn't xdg-desktop-portal seeded anywhere?12:31
jbichadoko: my guess is that we're waiting for bug 1750069 to be approved12:32
ubot5bug 1750069 in xdg-desktop-portal-gtk (Ubuntu) "[MIR] xdg-desktop-portal-gtk" [Undecided,Confirmed] https://launchpad.net/bugs/175006912:32
dokoahh, ok12:33
dokojamespage: any update on https://bugs.launchpad.net/aodh/+bug/1737989 ?12:37
ubot5Ubuntu bug 1737989 in ujson (Ubuntu) "[MIR] ujson?" [Undecided,Incomplete]12:37
stgraberapw: so yeah, I can introduce two empty packages just to make britney happy, seems like a bit of a hack though as those wouldn't be transitional packages, they'd literally be empty packages13:44
stgraberapw: they wouldn't be transitional because the "lxd" package does not actually provide the content of lxd-tools13:45
apwstgraber, except in essence it does, because the installation of lxd installs the snap which brings you the contents, in some sense13:47
acheronukonly a temporary requirement anyway ^^ ?13:51
-queuebot:#ubuntu-release- Unapproved: accepted nautilus [source] (bionic-proposed) [1:3.26.4-0~ubuntu18.04.1]13:54
stgraberapw: well, that's true for the lxd-client package and lxd package, that isn't true for the lxd-tools package which has no equivalent post-deb13:58
stgraberanyway, that's easy enough to do so I'll just add two transitional packages for now and then make a subsequent upload on Monday to remove them both from the archive13:59
rbalinthi, do i need FFe for LP: #1317164 and LP: #1791931 ?14:01
ubot5Launchpad bug 1317164 in update-manager (Ubuntu) "Show reason of TransactionFailed and let the user try again instead of crashing" [High,In progress] https://launchpad.net/bugs/131716414:01
ubot5Launchpad bug 1791931 in update-manager (Ubuntu) "Update-manager crashes in _show_transaction due to packages being already removed" [High,In progress] https://launchpad.net/bugs/179193114:02
rbalintthe first one is a bit of a user interface improvement but prior crashes were not considered to be u-m issues per the bug's old text14:04
rbalinti guess that's a no for requiring FFe :-)14:15
-queuebot:#ubuntu-release- Unapproved: qemu (bionic-proposed/main) [1:2.11+dfsg-1ubuntu7.5 => 1:2.11+dfsg-1ubuntu7.6] (ubuntu-server, virt)14:39
-queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-35.38] (core, kernel)14:52
acheronuksil2100: hi. is there any chance you could do the cosmic packageset update for Kubuntu?15:15
sil2100acheronuk: hey! Yes, the scripts are running15:17
sil2100Will take a moment I suppose15:17
acheronuksil2100: great. thanks. sorry to ping more than once15:17
acheronuksil2100: got your email. can I see the diff anywhere to check?15:50
acheronukif not I've saved my current one and will diff when it updates15:53
-queuebot:#ubuntu-release- Unapproved: accepted python3.6 [source] (bionic-proposed) [3.6.6-1~18.04]15:57
sil2100acheronuk: http://paste.ubuntu.com/p/pkGrpwbDZk/16:00
-queuebot:#ubuntu-release- Packageset: 448 entries have been added or removed16:01
-queuebot:#ubuntu-release- Unapproved: accepted python3.7 [source] (bionic-proposed) [3.7.0-1~18.04]16:03
acheronukslangasek: thanks. what I needed is in, and nothing vital dropped :)16:04
slangasekacheronuk: was that directed at sil2100 ?16:12
acheronukslangasek: yup. apologies16:13
dokoslangasek, ogra: https://bugs.launchpad.net/ubuntu/+source/ubuntu-core-meta/+bug/1572539  where should that be seeded?16:37
ubot5Ubuntu bug 1572539 in ubuntu-core-meta (Ubuntu) "[MIR] ubuntu-core-libs" [Critical,Fix committed]16:37
ogradoko, probably just in supported ... though i'm not sure the archive package has even the recent packagelist16:38
ogranot sure who worked on that16:38
ogra(the bug is 2 years old and i have moved teams twice since i filed it ... with each move moving me further away from any archive related work sadly)16:41
-queuebot:#ubuntu-release- Unapproved: accepted binutils [source] (bionic-proposed) [2.30-21ubuntu1~18.04]16:46
-queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-35.38~16.04.1] (kernel)17:04
slangasekstgraber: the snapd we rather badly need for fixing regressions in cosmic is blocking on lxd autopkgtest failures; "accept4: too many open files; retrying in 1s" --> timeout.  Do you know what this is?17:05
-queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-35.38~16.04.1] (kernel)17:08
tsimonq2infinity, slangasek: Could wxl please get livefs FTBFS nag emails as well?18:09
tsimonq2Also, gilir left the project, I don't know if he still wants to be nagged. :P18:09
stgraberslangasek: hi, sorry, was in a meeting, looking now18:09
slangasektsimonq2: email address?18:09
tsimonq2slangasek: wxl@ubuntu.com18:09
slangasektsimonq2: added.  and if gilir doesn't want to be nagged, he knows where to find us18:10
tsimonq2slangasek: ack :)18:10
tsimonq2Thanjs.18:10
tsimonq2*Thanks18:10
stgraberslangasek: all 3 failures appaear to be some kind of race in clustering code, amd64 was retried and is now green, just retried the other two18:11
stgraberslangasek: so snapd isn't breaking LXD (not sure why it even triggered the lxd test in the first place), feel free to hint if urgent18:12
slangaseko18:12
slangasekok18:12
-queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-35.38~16.04.1]18:14
-queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-35.38~16.04.1]18:14
-queuebot:#ubuntu-release- New: accepted protobuf [amd64] (xenial-proposed) [2.6.1-1.3ubuntu1]18:23
-queuebot:#ubuntu-release- New: accepted protobuf [ppc64el] (xenial-proposed) [2.6.1-1.3ubuntu1]18:23
-queuebot:#ubuntu-release- New: accepted protobuf [arm64] (xenial-proposed) [2.6.1-1.3ubuntu1]18:23
-queuebot:#ubuntu-release- New: accepted protobuf [s390x] (xenial-proposed) [2.6.1-1.3ubuntu1]18:23
wxlslangasek: is that something another user could do on their own? (sign up for livefs failure notices)18:23
slangasekit is not18:23
slangasekthe configuration currently lives in the private 'production' branch for cdimage18:24
slangasekthis bit probably doesn't need to be private, but otoh you also probably don't want notification emails from any other random people who try to run cdimage18:24
wxlright. sounds good18:25
wxlin other news it seems that the lubuntu bionic alternate images haven't built since april.. uhhh?18:25
wxland the amd64 died due to unmet depends with linux. i'm assuming this will resolve itself once 4.15.0-35.38 migrates? https://launchpadlibrarian.net/388239221/buildlog_ubuntu_bionic_amd64_lubuntu_BUILDING.txt.gz18:29
slangasekalternate> are they supposed to be building?  there are no emails about build failures, so that appears to be intentional18:29
wxl(amd64 desktop)18:29
slangasekit resolves itself when linux+linux-signed+linux-meta are all built and published in -proposed18:29
wxlslangasek: i would expect the alternates to continue to build. we're certainly on the hook to continue to support them for bionic :)18:30
slangasekyet no one mentioned them being absent for the point release?18:30
wxlweird. they were in the original release. let me look into that further18:31
stgraberslangasek: oh, just thought of something for the magic lxd deb-to-snap package, I need a Pre-Depends on snapd don't I? For the unlikely case where snapd isn't already installed.18:32
slangasekthe history is in lp:ubuntu-cdimage; infinity dropped lubuntu alternate builds on 2 May, and enabled bionic daily builds in a later commit the same day18:32
stgraberwe have a Depends right now, but that won't be good enough since we do things from preinst18:33
slangasekstgraber: you need a pre-depends only if you need to talk to snapd from the deb's preinst package; do you?18:33
slangasekok then yes18:33
wxllike i said, i'll investigate further. no worries on that front, slangasek.18:33
wxlthanks for your help :)18:33
infinitywxl: Look back, we don't do the alternates for point releases, because representing the changes in the seeded sets for the HWE stack is somewhere between difficult and impossible.18:51
infinitywxl: This isn't new. :P18:51
wxlinfinity: tsimonq2 reminded me. i disabled them. he should have done that, but he's a bad boy, as i'm sure you already know18:52
tsimonq2But I thought infinity had access to do that. :P18:53
tsimonq2wxl: So don't blame me, blame Adam. :P18:54
wxloh no, you had access, too, mr. release manager :)18:54
tsimonq2You're supposed to regularly looking at the tracker, Mr. QA Lead. ;)18:55
wxli'm too busy sorting through all the bugs you make :)18:55
* wxl *slap fight*18:55
* tsimonq2 *slap fight*18:55
tsimonq2Love you too, wxl.18:56
wxlhttps://v.gd/zMrzy318:57
tsimonq2You're the short one. :P18:58
wxlwhatever. that hat looks ridiculous.18:58
tsimonq2hahahahahaha18:58
tsimonq2wxl: I would propose we have #ubuntu-release-offtopic but I don't think anyone would join. :P18:59
wxlXD18:59
wxlit would give adam something else to roll his eyes at18:59
tsimonq2¯\_(ツ)_/¯19:00
teward*rolls eyes*19:02
* tsimonq2 throws teward into /dev/null19:07
slangasekLaney: do you know why amd64,arm64,i386 are taking so long to clear the autopkgtest backlog?19:17
slangasekthey're now a full day behind the other archs, which is exceptional19:18
tsimonq2slangasek: Thoughts on vnstat's arm* tests? Seems like somethingbadtestable.19:38
tsimonq2*something badtestable19:38
-queuebot:#ubuntu-release- Unapproved: fonts-liberation2 (bionic-proposed/main) [2.00.1-5 => 2.00.1-7~18.04.1] (kubuntu, personal-gunnarhj, ubuntu-desktop)19:45
-queuebot:#ubuntu-release- Unapproved: fonts-liberation (bionic-proposed/main) [1:1.07.4-5 => 1:1.07.4-7~18.04.1] (desktop-core, personal-gunnarhj)19:45
-queuebot:#ubuntu-release- Unapproved: accepted fonts-liberation [source] (bionic-proposed) [1:1.07.4-7~18.04.1]20:02
-queuebot:#ubuntu-release- Unapproved: accepted fonts-liberation2 [source] (bionic-proposed) [2.00.1-7~18.04.1]20:05
mfoslangasek, sil2100: hey, tomorrow could one of you please review the nodejs openssl change for cosmic? (the issue of abi breakage w/ upstream nodejs) there's a debdiff in LP #1779863, which fixes that plus the test-case failure seen in all archs in the version currently in cosmic-proposed.  thanks!20:05
ubot5Launchpad bug 1779863 in nodejs (Ubuntu Cosmic) "Ubuntu nodejs package isn't ABI compatible with mainline nodejs." [Medium,In progress] https://launchpad.net/bugs/177986320:05
slangasektsimonq2: it didn't look badtestable to me, it looked like a version in -proposed that had regressed the tests on these archs.  What do you see that suggests otherwise?20:19
slangasekmfo: done20:21
mfoslangasek, thanks! :) that was fast.20:21
slangasekmfo: ftbfs on s390x20:51
slangasekpossibly going to ftbfs elsewhere and s390x is just first20:51
mfoslangasek, hm. i'll go check it.20:51
tsimonq2slangasek: vnstat's arm* tests> I say that because the tests have regressed in the same way as all other arches.20:52
slangasektsimonq2: from what I see, we previously had a test, that made buggy assumptions about the host interface names so only passed on some architectures; now we have a different test, which makes different buggy assumptions, and is broken on all archs.21:01
slangasek"test is now equally crappy on all architectures" is not in this case a reason to badtest, I think21:01
mfoslangasek, just checked the nodejs ftbfs on s390x.  it is s390x specific and not a regression. looking at the build logs of the *previous* version (...ubuntu1), that test-case failure already happened in s390x and only in s390x.  the other test-case failure in all archs has been fixed in this upload (ubuntu2).  i'm happy to debug it on s390x and see if i can fix that too.. do you know where/whom can i get access to s390x within Canonical?21:05
tsimonq2slangasek: ack, makes sense.21:07
slangasekmfo: when you say 'not a regression', nodejs 8.11.2~dfsg-1 certainly built on s390x.  as for access, let me see what I can do; we unfortunately don't have a porter box set up the way we do for other archs21:07
mfoslangasek, yes, that is the previous-previous version.  i mean it's not a regression caused by this upload. :)21:07
mfoslangasek, it turns out that 8.11.2~dfsg-1 was built back on May iirc, then 8.11.2~dfsg-1ubuntu1 is recent (and had these test-case failures). then 8.11.2~dfsg-1ubuntu2 (this upload) should resolve the test-case failure that is common to all archs (e.g., ppc64el built successfully), but this s390x specific test-case failure I hadn't seen yet, but it is present in the build log of 8.11.2~dfsg-1ubuntu1 (previous version). that's what I mean :)21:09
slangasekmfo: fair enough; still keeps the package from reaching the release pocket anyway21:10
mfoslangasek, right, i undertand. that's why i'm offering to debug it. :)  and thanks for checking on s390x access, i understand it might be hard to get, unfrotunately.21:10
mfoslangasek, i have to leave for the day, but can continue working on this tomorrow. thanks again for your help.21:12
-queuebot:#ubuntu-release- Unapproved: accepted plymouth [source] (bionic-proposed) [0.9.3-1ubuntu7.18.04.1]21:36

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!