/srv/irclogs.ubuntu.com/2018/08/28/#ubuntu-release.txt

mwhudsonaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa04:11
flocculantyea04:12
mwhudsonslangasek: some of the failures preventing python-scipy from migrating are probably real problems in scipy04:12
mwhudsonbut the python-scipy build does not run the tests04:13
mwhudsonit attempts to run the tests and then ignore the results (...) but it doesn't even do that04:13
mwhudson/<<PKGBUILDDIR>>/debian/tests/python3: 7: /<<PKGBUILDDIR>>/debian/tests/python3: AUTOPKGTEST_TMP: parameter not set04:13
mwhudsonand the autopkgtests have always failed on s390x so that's no help either04:14
* mwhudson goes home in a grump04:14
-queuebot:#ubuntu-release- New binary: cpp-hocon [s390x] (cosmic-proposed/universe) [0.1.7-1] (no packageset)04:33
-queuebot:#ubuntu-release- New binary: cpp-hocon [ppc64el] (cosmic-proposed/universe) [0.1.7-1] (no packageset)04:34
-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]04:35
tsimonq2Oooh, 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:11
tsimonq2...you could say, I "did it." </terrible pun>05:19
tsimonq2slangasek: 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/amd6405:32
slangasektsimonq2: done05:36
tsimonq2slangasek: Thanks.05:36
tsimonq2slangasek: Same situation with php-analog/1.0.7-2.05:38
slangasektsimonq2: nah I just removed that package05:39
tsimonq2slangasek: How 'bout php-pimple/3.0.2-2ubuntu1?05:40
slangasektsimonq2: 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:41
tsimonq2slangasek: Same error, RC bug, looks just like the aforementioned packages. Thanks for triggering the test, it should confirm it.05:43
slangasektsimonq2: ok.  test results are in, and it confirms05:44
slangasekI triggered release-pocket-only tests of everything that's blocking php-defaults05:44
tsimonq2ack, so we *are* looking at the same thing. ;)05:44
slangasekand they're all badtestable (done)05:45
tsimonq2Awesome.05:45
slangasekand now I'm not looking at any more of these tonight ;)05:45
tsimonq2hehe05:46
tsimonq2http://autopkgtest.ubuntu.com/packages/d/doit/cosmic/arm64 lolwat05:46
* tsimonq2 can't tell if it's an autopkgtest bug or if it's an oversight in the submission syntax...05:47
slangasektsimonq2: did you trigger that test before doit 0.31.1-1ubuntu3 was actually published?05:49
tsimonq2slangasek: No, I waited until it was published.05:51
tsimonq2slangasek: But I did do it immediately after I confirmed it was in LP so ... race condition somewhere?05:51
slangasekwell, the error looks to me like the autopkgtest runner couldn't find it on the internal archive server05:51
tsimonq2Huh.05:51
slangasekyes, 'published' in launchpad means that a launchpad api call has finished wrt that package, not that the publishing run is complete05:52
tsimonq2slangasek: fflas-ffpack badtest on armhf? Looks like you retried against release: http://autopkgtest.ubuntu.com/packages/f/fflas-ffpack/cosmic/armhf05:52
tsimonq2Ah, got it.05:52
tsimonq2How long should I expect to wait for the publishing run?05:53
slangasekI'd give it about 5 minutes generally05:53
tsimonq2OK05:53
slangasekfflas-ffpack> I'm really not looking at any more of these tonight05:54
tsimonq2OK ;)05:54
* tsimonq2 waits for some UK folks.05:54
tsimonq2Thanks slangasek.05:54
ginggstsimonq2: now you can send your doit fix to debian and impress your AM ;)05:56
tsimonq2ginggs: ahaha05:57
tsimonq2I haven't got an email from them yet...05:57
tsimonq2I was going to anyway, after I confirm pytest migrated.05:57
slangasektsimonq2: 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 me05:58
tsimonq2slangasek: Sure thing, I'll see if I can make heads or tails of it.05:58
tsimonq2ginggs: Wait a minute ... I KNEW I recognized the name from somewhere!05:59
ginggstsimonq2: you got it!05:59
tsimonq2ginggs: Somehow I wonder if frontdesk is lurking in here and just decided to assign me that AM... :P06:01
-queuebot:#ubuntu-release- Unapproved: unbound (bionic-proposed/main) [1.6.7-1ubuntu2.1 => 1.6.7-1ubuntu2.2] (ubuntu-server)06:33
=== ogra_ is now known as ogra
LocutusOfBorgsil2100, 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-op08:25
LocutusOfBorgLOL08:25
LocutusOfBorg(I asked here to reject some seconds after the upload, but nobody did it)08:26
LocutusOfBorgsorry for wasting your time! we should probably gain a "reject your uploaded package by yourself" button08:26
xnoxjbicha, 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
xnoxcause 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 up09:03
* xnox goes to dig deeper.09:04
tkamppeterI have synced cups-filters 1.21.1 on Monday and now it is hanging in -proposed with09:14
tkamppeterInvalidated by dependency09:14
tkamppeterDepends: cups-filters glibc (not considered)09:14
tkamppeterDepends: cups-filters poppler09:14
tkamppeterWhat does this mean? Do I have to no-change-upload it? Or simply wait until a problem of the glibc package gets solved?09:15
LocutusOfBorgtkamppeter, fixing xpdf might help :p09:21
jbichaxnox: I don't think gjs is using rust yet, see https://salsa.debian.org/gnome-team/mozjs60 (uploaded to Debian NEW)10:06
xnoxjbicha, ah, interesting, thanks.10:09
xnoxtkamppeter, it means this thing picked up a dependency on the newer glibc; which itself is not yet ready to migrate.10:09
xnoxtkamppeter, meaning you already gained a new abi10:09
jbichanew versions of librsvg do use rust though10:10
rbalinthi, please sync ruby-concurrent it should fix autopkgtest10:18
LocutusOfBorg.10:40
ahasenackinfinity: 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:08
xnoxjbicha, so, gdm3 looks fine to me in arm64 vm, if it has a video graphics card provided, a virtio one for example.11:45
xnoxslangasek, do you use grab-merge from MoM? i think we need to fix it to correctly unpack and preserve executable bits11:50
xnoxslangasek, it looks like it doesn't. and e.g. apt-setup and ifupdown were bitten by that recently11:50
xnoxit is a recurring thing.11:50
xnoxmwhudson, too11:50
oSoMoNhi 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:10
ubot5bug 1789240 in libreoffice (Ubuntu) "[FFe] libreoffice 6.1.0" [Undecided,Confirmed] https://launchpad.net/bugs/178924013:10
LocutusOfBorgarchive 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 installed13:12
LocutusOfBorgslangasek, ^^ since you too don't like test being ignored :)13:12
LocutusOfBorgit requires a bunch of removals on other architectures for reverse-deps13:12
LocutusOfBorgapw, ^^13:17
tkamppetercpdb-libs has a problem with the autopgk test. The test passes on all architectures except arm64. On arm64 I get:13:22
tkamppeterautopkgtest [09:21:04]: test text_frontend_vs_cups_backend: [-----------------------13:22
tkamppeterautopkgtest [09:21:19]: test text_frontend_vs_cups_backend: -----------------------]13:22
tkamppeterautopkgtest [09:21:19]: test text_frontend_vs_cups_backend:  - - - - - - - - - - results - - - - - - - - - -13:22
tkamppetertext_frontend_vs_cups_backend FAIL non-zero exit status 13913:22
tkamppeterMeaning that before the script outputs anything on stderr or stdout it exits with status 139. What does this mean.13:22
tkamppeter?13:23
seb128could someone review ffe bug #1789380 which is a simple GNOME app update?13:29
ubot5bug 1789380 in gnome-calendar (Ubuntu) "[ffe] Update to 3.29.92" [Wishlist,New] https://launchpad.net/bugs/178938013:29
-queuebot:#ubuntu-release- Unapproved: fonts-noto-color-emoji (bionic-proposed/main) [0~20180424-0ubuntu1 => 0~20180810-0ubuntu1] (ubuntu-desktop)13:56
-queuebot:#ubuntu-release- Unapproved: nova-lxd (bionic-proposed/main) [17.0.0-0ubuntu1 => 17.0.1-0ubuntu1] (ubuntu-server)14:30
sil2100seb128: on it in a moment14:39
slangasekxnox: I don't know about rust itself being busted; I know that there are bunches of rust library packages with impossible dependencies14:42
slangasekxnox: yes, I use grab-merge from MoM, and yes, it would be nice if it didn't drop +x :/14:43
slangasektjaalton: dogtag-pki's autopkgtests still aren't looking very healthy, but at least it's not hanging now?14:50
tjaaltonslangasek: right, pushed a new httpcomponents-client to fix a failure installing pki-kra, but the autopkgtest failure is something else..14:54
tjaaltoneverything installs fine here, dunno what that encoding error is about14:55
slangasektjaalton: 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 locally14:55
sil2100seb128: 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:56
-queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-34.37] (core, kernel)14:57
tjaaltonslangasek: hmm could be that it was trying to print out the error then? maybe wait and see if new libhttpclient-java fixes this too14:58
seb128sil2100, no, but it's in Debian and it's a sync, the upstream changes are small and it got local testing15:02
seb128also it's only an app, not a session component15:02
seb128we still have plenty of time to catch any regression and fix it15:02
sil2100seb128: approved this time, but please remember there are procedures that need to be followed for every FFe: https://wiki.ubuntu.com/FreezeExceptionProcess#FeatureFreeze_Exceptions15:04
oSoMoNsil2100, on the topic of FFe, did you see my question in this channel earlier?15:06
seb128sil2100, 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 one15:06
oSoMoNwondering whether the status of bug #1789240 should be set to New15:06
ubot5bug 1789240 in libreoffice (Ubuntu) "[FFe] libreoffice 6.1.0" [Undecided,Confirmed] https://launchpad.net/bugs/178924015:06
sil2100seb128: 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
seb128right15:09
sil2100oSoMoN: I'll look at it in a minute as well15:09
oSoMoNthanks!15:10
-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:14
-queuebot:#ubuntu-release- Unapproved: magnum (bionic-proposed/universe) [6.1.0-0ubuntu1 => 6.1.1-0ubuntu0.18.04.1] (no packageset)15:15
coreycbwhoa, sorry about that. ^^ please just choose one, they're all the same.15:16
coreycb2 attempts at a PPA upload with reversed arguments15:17
tewardcoreycb: oopsies?15:17
coreycbteward: ya15:18
-queuebot:#ubuntu-release- New: accepted ndctl [source] (bionic-proposed) [61.2-0ubuntu1~18.04.1]16:17
-queuebot:#ubuntu-release- New: accepted pmdk [source] (bionic-proposed) [1.4.1-0ubuntu1~18.04.1]16:18
-queuebot:#ubuntu-release- New binary: ndctl [amd64] (bionic-proposed/none) [61.2-0ubuntu1~18.04.1] (no packageset)16:20
-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:22
-queuebot:#ubuntu-release- New: accepted ndctl [amd64] (bionic-proposed) [61.2-0ubuntu1~18.04.1]16:27
oSoMoNthanks sil2100!16:41
sil2100yw!16:42
slangasektsimonq2: 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:45
slangasektjaalton: printing out an error> why does the error message contain non-ascii chars, either? :)16:46
tsimonq2slangasek: Yeah, it was a shot in the dark.16:59
-queuebot:#ubuntu-release- New binary: pmdk [amd64] (bionic-proposed/universe) [1.4.1-0ubuntu1~18.04.1] (no packageset)17:25
-queuebot:#ubuntu-release- New: accepted pmdk [amd64] (bionic-proposed) [1.4.1-0ubuntu1~18.04.1]17:52
-queuebot:#ubuntu-release- Unapproved: magnum (bionic-proposed/universe) [6.1.0-0ubuntu1 => 6.1.1-0ubuntu0.18.04.1] (no packageset)18:23
tjaaltonslangasek: good question..18:40
-queuebot:#ubuntu-release- New binary: libminc [s390x] (cosmic-proposed/universe) [2.4.03-1] (no packageset)18:45
-queuebot:#ubuntu-release- New binary: libminc [ppc64el] (cosmic-proposed/universe) [2.4.03-1] (no packageset)18:46
-queuebot:#ubuntu-release- New binary: libminc [i386] (cosmic-proposed/universe) [2.4.03-1] (no packageset)18:47
-queuebot:#ubuntu-release- New binary: libminc [arm64] (cosmic-proposed/universe) [2.4.03-1] (no packageset)18:48
-queuebot:#ubuntu-release- New binary: libminc [armhf] (cosmic-proposed/universe) [2.4.03-1] (no packageset)18:49
-queuebot:#ubuntu-release- New binary: libminc [amd64] (cosmic-proposed/universe) [2.4.03-1] (no packageset)18:50
tsimonq2slangasek: telepathy-logger-qt> It fails when retried against itself (as you might have seen)... hint?19:42
tsimonq2oh19:43
tsimonq2I can read...19:43
tsimonq2Yeah, that's not against -release, but it's still weird...19:43
-queuebot:#ubuntu-release- New binary: libreoffice [s390x] (cosmic-proposed/main) [1:6.1.0-0ubuntu1] (kubuntu, ubuntu-desktop)19:44
* tsimonq2 just can't seem to figure out what error 25 means.19:51
-queuebot:#ubuntu-release- New binary: libreoffice [ppc64el] (cosmic-proposed/main) [1:6.1.0-0ubuntu1] (kubuntu, ubuntu-desktop)20:50
mwhudsonxnox: i haven't actually done much merging recently, just fixing fallout from the bugs you mentioned20:54
xnoxmwhudson, right but i think it was grab-merge induced loss of +x not human error20:57
xnoxin apt-setup20:57
mwhudsonyeah, certainly21:01
mwhudsonwell grab-merge or mom itself?21:01
slangasekgrab-merge doesn't meddle with file perms21:02
slangasekit's a MoM bug21:02
-queuebot:#ubuntu-release- New binary: libreoffice [i386] (cosmic-proposed/main) [1:6.1.0-0ubuntu1] (kubuntu, ubuntu-desktop)23:14
-queuebot:#ubuntu-release- New binary: libreoffice [amd64] (cosmic-proposed/main) [1:6.1.0-0ubuntu1] (kubuntu, ubuntu-desktop)23:56

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