[04:11] <mwhudson> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[04:12] <flocculant> yea
[04:12] <mwhudson> slangasek: some of the failures preventing python-scipy from migrating are probably real problems in scipy
[04:13] <mwhudson> but the python-scipy build does not run the tests
[04:13] <mwhudson> it attempts to run the tests and then ignore the results (...) but it doesn't even do that
[04:13] <mwhudson> /<<PKGBUILDDIR>>/debian/tests/python3: 7: /<<PKGBUILDDIR>>/debian/tests/python3: AUTOPKGTEST_TMP: parameter not set
[04:14] <mwhudson> and the autopkgtests have always failed on s390x so that's no help either
[04:14]  * mwhudson goes home in a grump
[04:33] -queuebot:#ubuntu-release- New binary: cpp-hocon [s390x] (cosmic-proposed/universe) [0.1.7-1] (no packageset)
[04:34] -queuebot:#ubuntu-release- New binary: cpp-hocon [ppc64el] (cosmic-proposed/universe) [0.1.7-1] (no packageset)
[04:35] -queuebot:#ubuntu-release- New: accepted cpp-hocon [ppc64el] (cosmic-proposed) [0.1.7-1]
[04:35] -queuebot:#ubuntu-release- New: accepted ros-bond-core [amd64] (cosmic-proposed) [1.8.3-1]
[04:35] -queuebot:#ubuntu-release- New: accepted cpp-hocon [s390x] (cosmic-proposed) [0.1.7-1]
[04:35] -queuebot:#ubuntu-release- New: accepted ros-bond-core [ppc64el] (cosmic-proposed) [1.8.3-1]
[05:11] <tsimonq2> Oooh, I figured out doit. pytest + doit should migrate on the next Britney run or two.
[05:11] -queuebot:#ubuntu-release- Unapproved: snapd-glib (bionic-proposed/main) [1.41-0ubuntu0.18.04.1 => 1.43-0ubuntu0.18.04.1] (kubuntu, ubuntu-desktop, ubuntu-server)
[05:19] <tsimonq2> ...you could say, I "did it." </terrible pun>
[05:32] <tsimonq2> slangasek: Could you badtest php-text-password/1.2.1-2? It has an RC bug open in Debian and it fails when retried against itself with the same error: http://autopkgtest.ubuntu.com/packages/p/php-text-password/cosmic/amd64
[05:36] <slangasek> tsimonq2: done
[05:36] <tsimonq2> slangasek: Thanks.
[05:38] <tsimonq2> slangasek: Same situation with php-analog/1.0.7-2.
[05:39] <slangasek> tsimonq2: nah I just removed that package
[05:40] <tsimonq2> slangasek: How 'bout php-pimple/3.0.2-2ubuntu1?
[05:41] <slangasek> tsimonq2: where's the evidence that it fails against the release pocket?  (I have just triggered exactly this test to check, but the results aren't available yet)
[05:43] <tsimonq2> slangasek: Same error, RC bug, looks just like the aforementioned packages. Thanks for triggering the test, it should confirm it.
[05:44] <slangasek> tsimonq2: ok.  test results are in, and it confirms
[05:44] <slangasek> I triggered release-pocket-only tests of everything that's blocking php-defaults
[05:44] <tsimonq2> ack, so we *are* looking at the same thing. ;)
[05:45] <slangasek> and they're all badtestable (done)
[05:45] <tsimonq2> Awesome.
[05:45] <slangasek> and now I'm not looking at any more of these tonight ;)
[05:46] <tsimonq2> hehe
[05:46] <tsimonq2> http://autopkgtest.ubuntu.com/packages/d/doit/cosmic/arm64 lolwat
[05:47]  * tsimonq2 can't tell if it's an autopkgtest bug or if it's an oversight in the submission syntax...
[05:49] <slangasek> tsimonq2: did you trigger that test before doit 0.31.1-1ubuntu3 was actually published?
[05:51] <tsimonq2> slangasek: No, I waited until it was published.
[05:51] <tsimonq2> slangasek: But I did do it immediately after I confirmed it was in LP so ... race condition somewhere?
[05:51] <slangasek> well, the error looks to me like the autopkgtest runner couldn't find it on the internal archive server
[05:51] <tsimonq2> Huh.
[05:52] <slangasek> yes, 'published' in launchpad means that a launchpad api call has finished wrt that package, not that the publishing run is complete
[05:52] <tsimonq2> slangasek: fflas-ffpack badtest on armhf? Looks like you retried against release: http://autopkgtest.ubuntu.com/packages/f/fflas-ffpack/cosmic/armhf
[05:52] <tsimonq2> Ah, got it.
[05:53] <tsimonq2> How long should I expect to wait for the publishing run?
[05:53] <slangasek> I'd give it about 5 minutes generally
[05:53] <tsimonq2> OK
[05:54] <slangasek> fflas-ffpack> I'm really not looking at any more of these tonight
[05:54] <tsimonq2> OK ;)
[05:54]  * tsimonq2 waits for some UK folks.
[05:54] <tsimonq2> Thanks slangasek.
[05:56] <ginggs> tsimonq2: now you can send your doit fix to debian and impress your AM ;)
[05:57] <tsimonq2> ginggs: ahaha
[05:57] <tsimonq2> I haven't got an email from them yet...
[05:57] <tsimonq2> I was going to anyway, after I confirm pytest migrated.
[05:58] <slangasek> tsimonq2: but if /you/ wanted to look at other things, you could tell me why the telepathy-logger-qt/ppc64el acc failure isn't reproducible for me
[05:58] <tsimonq2> slangasek: Sure thing, I'll see if I can make heads or tails of it.
[05:59] <tsimonq2> ginggs: Wait a minute ... I KNEW I recognized the name from somewhere!
[05:59] <ginggs> tsimonq2: you got it!
[06:01] <tsimonq2> ginggs: Somehow I wonder if frontdesk is lurking in here and just decided to assign me that AM... :P
[06:33] -queuebot:#ubuntu-release- Unapproved: unbound (bionic-proposed/main) [1.6.7-1ubuntu2.1 => 1.6.7-1ubuntu2.2] (ubuntu-server)
[08:25] <LocutusOfBorg> sil2100, thanks for rejecting vbox-ext-pack :) the problem was that people are keeping reporting the same bug over and over, without prior doing apt-get update, so they keep using the version in release... -.-' I then fixed twice the same bug and of course the resulting (working) upload was a no-op
[08:25] <LocutusOfBorg> LOL
[08:26] <LocutusOfBorg> (I asked here to reject some seconds after the upload, but nobody did it)
[08:26] <LocutusOfBorg> sorry for wasting your time! we should probably gain a "reject your uploaded package by yourself" button
[09:03] <xnox> jbicha, slangasek, infinity - ehhh if rust is busted, and firefox is busted, it means gjs is busted too, and hence no gnome-shell and no display/login-manager either, no?!
[09:03] <xnox> cause it's all gnome-shell these days? or is gdm3 somehow not js? i thought it is....
[09:03]  * xnox wonders if everything is busted on arm64 then if gdm doesn't come up
[09:04]  * xnox goes to dig deeper.
[09:14] <tkamppeter> I have synced cups-filters 1.21.1 on Monday and now it is hanging in -proposed with
[09:14] <tkamppeter> Invalidated by dependency
[09:14] <tkamppeter> Depends: cups-filters glibc (not considered)
[09:14] <tkamppeter> Depends: cups-filters poppler
[09:15] <tkamppeter> What does this mean? Do I have to no-change-upload it? Or simply wait until a problem of the glibc package gets solved?
[09:21] <LocutusOfBorg> tkamppeter, fixing xpdf might help :p
[10:06] <jbicha> xnox: I don't think gjs is using rust yet, see https://salsa.debian.org/gnome-team/mozjs60 (uploaded to Debian NEW)
[10:09] <xnox> jbicha, ah, interesting, thanks.
[10:09] <xnox> tkamppeter, it means this thing picked up a dependency on the newer glibc; which itself is not yet ready to migrate.
[10:09] <xnox> tkamppeter, meaning you already gained a new abi
[10:10] <jbicha> new versions of librsvg do use rust though
[10:18] <rbalint> hi, please sync ruby-concurrent it should fix autopkgtest
[10:40] <LocutusOfBorg> .
[11:08] <ahasenack> infinity: hi, good morning/afternoon/evening, I guess with the glibc upload, you are all busy and can't take a look at squid in new? :)
[11:45] <xnox> jbicha, so, gdm3 looks fine to me in arm64 vm, if it has a video graphics card provided, a virtio one for example.
[11:50] <xnox> slangasek, do you use grab-merge from MoM? i think we need to fix it to correctly unpack and preserve executable bits
[11:50] <xnox> slangasek, it looks like it doesn't. and e.g. apt-setup and ifupdown were bitten by that recently
[11:50] <xnox> it is a recurring thing.
[11:50] <xnox> mwhudson, too
[13:10] <oSoMoN> hi all, I filed bug #1789240 yesterday to request a feature freeze exception for libreoffice 6.1, and it was marked confirmed because someone said this bug affects them, should I reset the status to New to ensure the release team sees it?
[13:12] <LocutusOfBorg> archive admins, can I please make insighttookit4 build only on amd64 and i386? there is no point on "building everywhere and discard failures" this is a medical image processing tool, upstream refuses to maintain anything non x86 unless somebody provides patches, and we shouldn't give users a false sense of good package being installed
[13:12] <LocutusOfBorg> slangasek, ^^ since you too don't like test being ignored :)
[13:12] <LocutusOfBorg> it requires a bunch of removals on other architectures for reverse-deps
[13:17] <LocutusOfBorg> apw, ^^
[13:22] <tkamppeter> cpdb-libs has a problem with the autopgk test. The test passes on all architectures except arm64. On arm64 I get:
[13:22] <tkamppeter> autopkgtest [09:21:04]: test text_frontend_vs_cups_backend: [-----------------------
[13:22] <tkamppeter> autopkgtest [09:21:19]: test text_frontend_vs_cups_backend: -----------------------]
[13:22] <tkamppeter> autopkgtest [09:21:19]: test text_frontend_vs_cups_backend:  - - - - - - - - - - results - - - - - - - - - -
[13:22] <tkamppeter> text_frontend_vs_cups_backend FAIL non-zero exit status 139
[13:22] <tkamppeter> Meaning that before the script outputs anything on stderr or stdout it exits with status 139. What does this mean.
[13:23] <tkamppeter> ?
[13:29] <seb128> could someone review ffe bug #1789380 which is a simple GNOME app update?
[13:56] -queuebot:#ubuntu-release- Unapproved: fonts-noto-color-emoji (bionic-proposed/main) [0~20180424-0ubuntu1 => 0~20180810-0ubuntu1] (ubuntu-desktop)
[14:30] -queuebot:#ubuntu-release- Unapproved: nova-lxd (bionic-proposed/main) [17.0.0-0ubuntu1 => 17.0.1-0ubuntu1] (ubuntu-server)
[14:39] <sil2100> seb128: on it in a moment
[14:42] <slangasek> xnox: I don't know about rust itself being busted; I know that there are bunches of rust library packages with impossible dependencies
[14:43] <slangasek> xnox: yes, I use grab-merge from MoM, and yes, it would be nice if it didn't drop +x :/
[14:50] <slangasek> tjaalton: dogtag-pki's autopkgtests still aren't looking very healthy, but at least it's not hanging now?
[14:54] <tjaalton> slangasek: right, pushed a new httpcomponents-client to fix a failure installing pki-kra, but the autopkgtest failure is something else..
[14:55] <tjaalton> everything installs fine here, dunno what that encoding error is about
[14:55] <slangasek> tjaalton: well, on the test runners, stdout is a file not a pipe, so python's locale handling defaults to ascii; you can probably reproduce this by redirecting stdout locally
[14:56] <sil2100> seb128: have you already tested the new gnome-calendar on cosmic in some PPA or such?
[14:56] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-34.37] (core, kernel)
[14:57] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-34.37] (core, kernel)
[14:58] <tjaalton> slangasek: hmm could be that it was trying to print out the error then? maybe wait and see if new libhttpclient-java fixes this too
[15:02] <seb128> sil2100, no, but it's in Debian and it's a sync, the upstream changes are small and it got local testing
[15:02] <seb128> also it's only an app, not a session component
[15:02] <seb128> we still have plenty of time to catch any regression and fix it
[15:04] <sil2100> seb128: approved this time, but please remember there are procedures that need to be followed for every FFe: https://wiki.ubuntu.com/FreezeExceptionProcess#FeatureFreeze_Exceptions
[15:06] <oSoMoN> sil2100, on the topic of FFe, did you see my question in this channel earlier?
[15:06] <seb128> sil2100, thx, and will do, r-t member got less stricts over the cycle on having a diff etc when requests are trivial like that one so I got lazy as well, but I will remember to include the details for the next one
[15:06] <oSoMoN> wondering whether the status of bug #1789240 should be set to New
[15:09] <sil2100> seb128: yw! In practice I also feel not all of the points should be required, but for now let's try not to create double standards, as current procedures state those as needed ;)
[15:09] <sil2100> (and maybe think about tweaking it some official manner)
[15:09] <seb128> right
[15:09] <sil2100> oSoMoN: I'll look at it in a minute as well
[15:10] <oSoMoN> thanks!
[15:14] -queuebot:#ubuntu-release- Unapproved: magnum (bionic-proposed/universe) [6.1.0-0ubuntu1 => 6.1.1-0ubuntu0.18.04.1] (no packageset)
[15:14] -queuebot:#ubuntu-release- Unapproved: magnum (bionic-proposed/universe) [6.1.0-0ubuntu1 => 6.1.1-0ubuntu0.18.04.1] (no packageset)
[15:15] -queuebot:#ubuntu-release- Unapproved: magnum (bionic-proposed/universe) [6.1.0-0ubuntu1 => 6.1.1-0ubuntu0.18.04.1] (no packageset)
[15:16] <coreycb> whoa, sorry about that. ^^ please just choose one, they're all the same.
[15:17] <coreycb> 2 attempts at a PPA upload with reversed arguments
[15:17] <teward> coreycb: oopsies?
[15:18] <coreycb> teward: ya
[16:17] -queuebot:#ubuntu-release- New: accepted ndctl [source] (bionic-proposed) [61.2-0ubuntu1~18.04.1]
[16:18] -queuebot:#ubuntu-release- New: accepted pmdk [source] (bionic-proposed) [1.4.1-0ubuntu1~18.04.1]
[16:20] -queuebot:#ubuntu-release- New binary: ndctl [amd64] (bionic-proposed/none) [61.2-0ubuntu1~18.04.1] (no packageset)
[16:22] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-34.37]
[16:22] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-34.37]
[16:27] -queuebot:#ubuntu-release- New: accepted ndctl [amd64] (bionic-proposed) [61.2-0ubuntu1~18.04.1]
[16:41] <oSoMoN> thanks sil2100!
[16:42] <sil2100> yw!
[16:45] <slangasek> tsimonq2: I see a new upload of telepathy-logger-qt, but considering the existing ppc64el failure wasn't reproducible for me locally, I'm unsurprised that it also didn't fix the problem?
[16:46] <slangasek> tjaalton: printing out an error> why does the error message contain non-ascii chars, either? :)
[16:59] <tsimonq2> slangasek: Yeah, it was a shot in the dark.
[17:25] -queuebot:#ubuntu-release- New binary: pmdk [amd64] (bionic-proposed/universe) [1.4.1-0ubuntu1~18.04.1] (no packageset)
[17:52] -queuebot:#ubuntu-release- New: accepted pmdk [amd64] (bionic-proposed) [1.4.1-0ubuntu1~18.04.1]
[18:23] -queuebot:#ubuntu-release- Unapproved: magnum (bionic-proposed/universe) [6.1.0-0ubuntu1 => 6.1.1-0ubuntu0.18.04.1] (no packageset)
[18:40] <tjaalton> slangasek: good question..
[18:45] -queuebot:#ubuntu-release- New binary: libminc [s390x] (cosmic-proposed/universe) [2.4.03-1] (no packageset)
[18:46] -queuebot:#ubuntu-release- New binary: libminc [ppc64el] (cosmic-proposed/universe) [2.4.03-1] (no packageset)
[18:47] -queuebot:#ubuntu-release- New binary: libminc [i386] (cosmic-proposed/universe) [2.4.03-1] (no packageset)
[18:48] -queuebot:#ubuntu-release- New binary: libminc [arm64] (cosmic-proposed/universe) [2.4.03-1] (no packageset)
[18:49] -queuebot:#ubuntu-release- New binary: libminc [armhf] (cosmic-proposed/universe) [2.4.03-1] (no packageset)
[18:50] -queuebot:#ubuntu-release- New binary: libminc [amd64] (cosmic-proposed/universe) [2.4.03-1] (no packageset)
[19:42] <tsimonq2> slangasek: telepathy-logger-qt> It fails when retried against itself (as you might have seen)... hint?
[19:43] <tsimonq2> oh
[19:43] <tsimonq2> I can read...
[19:43] <tsimonq2> Yeah, that's not against -release, but it's still weird...
[19:44] -queuebot:#ubuntu-release- New binary: libreoffice [s390x] (cosmic-proposed/main) [1:6.1.0-0ubuntu1] (kubuntu, ubuntu-desktop)
[19:51]  * tsimonq2 just can't seem to figure out what error 25 means.
[20:50] -queuebot:#ubuntu-release- New binary: libreoffice [ppc64el] (cosmic-proposed/main) [1:6.1.0-0ubuntu1] (kubuntu, ubuntu-desktop)
[20:54] <mwhudson> xnox: i haven't actually done much merging recently, just fixing fallout from the bugs you mentioned
[20:57] <xnox> mwhudson, right but i think it was grab-merge induced loss of +x not human error
[20:57] <xnox> in apt-setup
[21:01] <mwhudson> yeah, certainly
[21:01] <mwhudson> well grab-merge or mom itself?
[21:02] <slangasek> grab-merge doesn't meddle with file perms
[21:02] <slangasek> it's a MoM bug
[23:14] -queuebot:#ubuntu-release- New binary: libreoffice [i386] (cosmic-proposed/main) [1:6.1.0-0ubuntu1] (kubuntu, ubuntu-desktop)
[23:56] -queuebot:#ubuntu-release- New binary: libreoffice [amd64] (cosmic-proposed/main) [1:6.1.0-0ubuntu1] (kubuntu, ubuntu-desktop)