[00:31] -queuebot:#ubuntu-release- Unapproved: widelands (bionic-proposed/universe) [1:19+repack-4build4 => 1:19+repack-4ubuntu0.18.04.1] (no packageset) [00:32] * tsimonq2 really thinks glibc needs to be kicked through... [00:32] hmm [01:08] -queuebot:#ubuntu-release- Unapproved: gnome-games-app (bionic-proposed/universe) [3.28.0-1 => 3.28.0-1ubuntu1] (no packageset) [01:09] tsimonq2: yeah i think so too [01:09] about to write a mail about the two test failures in fact [01:09] Yeah. [01:09] this has involved learning more about the x87 than i ever wanted to know :) [01:34] tsimonq2: https://lists.ubuntu.com/archives/ubuntu-devel/2018-September/040480.html [01:34] mwhudson: Yup, I saw :) [01:34] Wonderful. [01:34] all hail the x87 [01:37] hahaha [01:40] oh god what is happening with python-cffi on ppc64el now [01:47] mwhudson: It's FTBFS in -proposed. [01:48] Might be the same as Debian's FTBFS, might not be. [01:48] ¯\_(ツ)_/¯ [01:58] -queuebot:#ubuntu-release- Unapproved: gnome-software (xenial-proposed/main) [3.20.5-0ubuntu0.16.04.11 => 3.20.5-0ubuntu0.16.04.12] (ubuntu-desktop) [02:02] well yes it ftbfs and it involves floats [02:03] and yes looks the same as debian [02:03] ppc64el isn't as gratuitously strange about floats as i386 though [03:46] i hope this isn't a compiler bug :( [04:05] well it doesn't happen with gcc-7 or with gcc-8 at -O0 but it happens at -O1 or higher [04:18] i think it's a compiler bug :( [05:40] LocutusOfBorg: sure; why is this '~build1' though? === RAOF is now known as Guest49550 [07:35] slangasek, because I'll upload a "final version" as soon as I'm happy :) === SynchronE is now known as aleks_bogdanov [07:35] and meh, I don't want a same version coming from debian and different content [07:35] so, in case I'll try to push in Debian too [07:36] apw, can you please clean up this NBS-proposed foo? old binaries left on amd64: libc++-7-helpers (from 1:7~+rc2-1~exp2ubuntu1) [07:36] it is not even part of release === Guest49550 is now known as RAOF [07:53] LocutusOfBorg, done [08:14] thanks apw ! [08:15] can I please ask you an hint? [08:15] [12:48:22] folks, please ignore symfony tests on armhf and s390x, they always failed, I did ignore test results because of deprecation warnings, and they started passing because of this reason... when I discovered that it was too late [08:15] it passed on armhf and s390x because I ignored test results, so not a regression at all [08:15] (and if you hint, I promise I'll try to sort also the failing architectures, but this seems to be really non trivial) === ogra_ is now known as ogra [08:54] -queuebot:#ubuntu-release- New source: smc-tools (cosmic-proposed/primary) [1.1.0-0ubuntu1] [10:24] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-snapshot [amd64] (cosmic-proposed) [1:8~svn340819-1] [10:24] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-snapshot [i386] (cosmic-proposed) [1:8~svn340819-1] [10:24] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-snapshot [arm64] (cosmic-proposed) [1:8~svn340819-1] [10:24] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-snapshot [ppc64el] (cosmic-proposed) [1:8~svn340819-1] [10:24] -queuebot:#ubuntu-release- New: accepted neutron-taas [amd64] (cosmic-proposed) [4.0.0~a1~git2018083141.84846d5-0ubuntu1] [10:24] -queuebot:#ubuntu-release- New: accepted vmware-nsx [amd64] (cosmic-proposed) [13.0.0-0ubuntu1] [12:25] hi guys, I'm adding dep8 tests to the sssd package, it has none currently [12:25] but I'm being hit by the glibc migration. My bileto dep8 tests use the release pocket, not proposed, and dependencies are uninstallable [12:26] and I can't retrigger the sssd tests because, since there were never any, the state is "always failed" [12:26] so I can't mangle the url to include proposed [12:26] any ideas? Just wait for the glibc migration to complete? Or upload anyway and hope for the best? [12:26] https://bileto.ubuntu.com/excuses/3399/cosmic.html ticket in question [12:31] ahasenack, I retried against proposed [12:31] https://autopkgtest.ubuntu.com/request.cgi?release=cosmic&arch=s390x&package=freeipa&trigger=sssd%2F1.16.3-1ubuntu1~ppa2&ppa=ci-train-ppa-service%2Fstable-phone-overlay&ppa=ci-train-ppa-service%2F3399&all-proposed=1 [12:31] this seems to have worked [12:31] oh, cool, [12:32] will https://bileto.ubuntu.com/excuses/3399/cosmic.html refresh eventually, or is that retry invisible to bileto? [12:32] oh, I retried freeipa :/ [12:32] well, that one would need a retry too, but it had tests already [12:33] retry-autopkgtest-regressions --ticket NNNN --series cosmic --state ALWAYSFAIL [12:33] FYI [12:33] --bileto not --ticket [12:33] Laney: where is that script? [12:33] ubuntu-archive-tools [12:33] lp: [12:33] bzr [12:33] -queuebot:#ubuntu-release- Unapproved: sshuttle (xenial-proposed/universe) [0.76-1 => 0.76-1ubuntu1] (no packageset) [12:33] * Laney writes easy to understand lines [12:33] yoda master :) [12:34] -queuebot:#ubuntu-release- Unapproved: sshuttle (bionic-proposed/universe) [0.78.3-1 => 0.78.3-1ubuntu1] (no packageset) [12:34] ahasenack, I would have uploaded a version with exit 0 in testsuite just to have a previous success :) [12:34] LocutusOfBorg: interesting idea. Would that have worked with the bileto ticket as well? [12:34] I guess so :) [12:34] LocutusOfBorg: but in this case, the dependencies won't install [12:34] it doesn't even start the test [12:36] Laney, it can't work [12:36] because it creates a invalid trigger [12:36] You submitted an invalid request: Package sssd does not have any test results [12:36] ./retry-autopkgtest-regressions --bileto 3399 --series cosmic --state ALWAYSFAIL [12:36] https://autopkgtest.ubuntu.com/request.cgi?release=cosmic&arch=amd64&package=sssd&trigger=sssd%2F1.16.3-1ubuntu1%7Eppa2&ppa=ci-train-ppa-service%2Fstable-phone-overlay&ppa=ci-train-ppa-service%2F3399 [12:40] weird, it clearly does [12:40] feel free to debug that [13:24] hi release team, I got an email about my samba sru kicking in the phasing stop trigger, https://errors.ubuntu.com/?release=Ubuntu%2014.04&package=samba&period=day&version=2%3A4.3.11%2Bdfsg-0ubuntu0.14.04.17 [13:25] if my reading of that is correct, there were just two new crashes? I see "2 U" in https://errors.ubuntu.com/bucket/?id=/usr/sbin/winbindd%3A6%3Adump_core%3Asmb_panic_s3%3Asmb_panic%3Awinbind_messaging_context%3Amain [13:26] the crashes seem to be about something very basic, like /var/lib/samba not existing, or an apparmor profile denying access to that dir, so I would need logs to debug [13:26] given there are just two, I think we should let the phasing continue [14:48] bdmurray: hi, when you have a moment, about the samba trusty sru phasing alert that I wrote above [14:50] ahasenack: looking [15:01] ahasenack: Okay, I'll get the phasing to continue. [15:02] bdmurray: it looks good on xenial, and it's the same version of samba with the same fix. But different build environment, of course [15:08] -queuebot:#ubuntu-release- New binary: intel-processor-trace [i386] (cosmic-proposed/main) [2.0-0ubuntu1] (no packageset) [15:10] -queuebot:#ubuntu-release- New binary: intel-processor-trace [amd64] (cosmic-proposed/main) [2.0-0ubuntu1] (no packageset) [15:10] -queuebot:#ubuntu-release- New binary: rust-syn [amd64] (cosmic-proposed/universe) [0.14.6-1] (no packageset) [15:12] -queuebot:#ubuntu-release- New: accepted intel-processor-trace [amd64] (cosmic-proposed) [2.0-0ubuntu1] [15:12] -queuebot:#ubuntu-release- New: accepted rust-syn [amd64] (cosmic-proposed) [0.14.6-1] [15:12] -queuebot:#ubuntu-release- New binary: rust-syn [s390x] (cosmic-proposed/universe) [0.14.6-1] (no packageset) [15:12] -queuebot:#ubuntu-release- New: accepted intel-processor-trace [i386] (cosmic-proposed) [2.0-0ubuntu1] [15:12] -queuebot:#ubuntu-release- New binary: rust-syn [ppc64el] (cosmic-proposed/universe) [0.14.6-1] (no packageset) [15:14] -queuebot:#ubuntu-release- New: accepted rust-syn [ppc64el] (cosmic-proposed) [0.14.6-1] [15:14] -queuebot:#ubuntu-release- New: accepted rust-syn [s390x] (cosmic-proposed) [0.14.6-1] [15:21] -queuebot:#ubuntu-release- Unapproved: accepted brltty [source] (bionic-proposed) [5.5-4ubuntu2.0.1] [15:30] -queuebot:#ubuntu-release- New binary: rust-serde-derive [ppc64el] (cosmic-proposed/universe) [1.0.70-1] (no packageset) [15:31] -queuebot:#ubuntu-release- New binary: rust-serde-derive [s390x] (cosmic-proposed/universe) [1.0.70-1] (no packageset) [15:31] -queuebot:#ubuntu-release- New binary: rust-serde-derive [amd64] (cosmic-proposed/universe) [1.0.70-1] (no packageset) [15:32] -queuebot:#ubuntu-release- New binary: rust-serde-derive [armhf] (cosmic-proposed/universe) [1.0.70-1] (no packageset) [15:33] -queuebot:#ubuntu-release- New binary: rust-serde-derive [i386] (cosmic-proposed/universe) [1.0.70-1] (no packageset) [15:35] -queuebot:#ubuntu-release- New binary: rust-serde-derive [arm64] (cosmic-proposed/universe) [1.0.70-1] (no packageset) [15:41] -queuebot:#ubuntu-release- New: accepted rust-serde-derive [amd64] (cosmic-proposed) [1.0.70-1] [15:41] -queuebot:#ubuntu-release- New: accepted rust-serde-derive [armhf] (cosmic-proposed) [1.0.70-1] [15:41] -queuebot:#ubuntu-release- New: accepted rust-serde-derive [ppc64el] (cosmic-proposed) [1.0.70-1] [15:41] -queuebot:#ubuntu-release- New: accepted rust-serde-derive [arm64] (cosmic-proposed) [1.0.70-1] [15:42] -queuebot:#ubuntu-release- New: accepted rust-serde-derive [s390x] (cosmic-proposed) [1.0.70-1] [15:42] -queuebot:#ubuntu-release- New: accepted rust-serde-derive [i386] (cosmic-proposed) [1.0.70-1] [15:43] slangasek: does bug 1766575 still feel appropriate to you for someone to SRU to bionic? [15:43] bug 1766575 in gnome-control-center (Ubuntu Bionic) "Drop libnss-myhostname recommends" [Low,Triaged] https://launchpad.net/bugs/1766575 [15:46] jbicha: I'm not sure I can justify it now [15:46] ok, I'll wontfix it there, but at least it's fixed in cosmic [16:32] -queuebot:#ubuntu-release- New binary: s390-tools [s390x] (cosmic-proposed/main) [2.6.0-0ubuntu4] (core) [16:51] -queuebot:#ubuntu-release- New binary: tboot [amd64] (cosmic-proposed/universe) [1.9.7-0ubuntu1] (no packageset) [16:51] -queuebot:#ubuntu-release- New: accepted s390-tools [s390x] (cosmic-proposed) [2.6.0-0ubuntu4] [16:51] -queuebot:#ubuntu-release- New: accepted tboot [amd64] (cosmic-proposed) [1.9.7-0ubuntu1] [17:10] hi, the general advice for packages stuck in migration due to "Invalidated by dependency" because of glibc, is to wait for glibc to migrate? [17:17] ahasenack: or if you prefer, fix the r-cran-rgenoud autopkgtest regression ;) [17:17] let me check [17:17] ahasenack: I mean, see the thread on ubuntu-devel first, mwhudson already took a swing at it [17:17] isn't that what mwhudson emailed ubuntu-devel [17:17] yeah [17:17] the python one seems to have been fixed upstream [17:17] after mwhudson's poke [17:18] there is a gpg2 failure too, but that seems to just need -proposed enabled for its run [17:19] infinity: based on mwhudson's analysis, I think it's correct for us to badtest python-cffi 1.11.5-1build1 (we've confirmed it's a bad test, fixing it is only blocked on the ppc64el build failure). What do you think of r-cran-rgenoud? [17:20] ahasenack: there's no gpg2 failure blocking glibc [17:20] hmm [17:20] or there WASN'T [17:20] autopkgtest for gnupg2/2.2.8-3ubuntu1: amd64: Regression ♻ , i386: Pass [17:20] one of the reds [17:20] this was a never-passed-before test that has now failed [17:20] so I will bypass that as necessary [17:21] oh, and it is using proposed [17:22] yeah the problem specifically is that once p-m sees a passing result for a test, it considers all other failures to be "regressions", even if the pass happens at a later point in time and with a later package version [17:27] and the gnupg2 autopkgtest fails because it's trying to install i386 multiarch packages, what the hell [17:28] so r-cran-arglebargle is the only blocker from my POV [17:28] $ reverse-depends src:r-cran-arglebargle [17:28] reverse-depends: Error:

Unknown package

[17:30] -rgenoud? no rdeps, could be removed [17:31] yes, rgenoud but it's pronounced 'arglebargle' [17:31] yes it could be removed [17:31] "it could be removed" != "we're confident this isn't a bug in glibc" [18:01] slangasek: I'm going to upload a python-cffi that passes its testsuite, my opinion on r-cran-genoud is that it's a crap test, based on reading scrollback from various people trying to understand it better. :P [18:02] I think I'm okay just badtesting it (or demoting it if the testsuite also runs in the build and this makes it FTBFS now) [18:15] slangasek, infinity: r-cran-rgenoud doesn't run its testsuite during the build and doesn't FTBFS now. I emailed upstream yesterday, but no response yet. [18:17] ok [18:19] infinity: ^^ based on all the above, I'm going to badtest the existing failures to unblock glibc, and python-cffi fix can land when it lands [18:21] slangasek: WFM, py-cffi is uploading now, but it would be another coupe of hours for all the test turnaround. [18:22] That's right, a two door car filled with hours. [18:22] -queuebot:#ubuntu-release- Unapproved: python-cffi (bionic-proposed/main) [1.11.5-1 => 1.11.5-2ubuntu1] (kubuntu, ubuntu-desktop, ubuntu-server) [18:22] Erm. [18:22] I live in the past. [18:23] -queuebot:#ubuntu-release- Unapproved: rejected python-cffi [source] (bionic-proposed) [1.11.5-2ubuntu1] [18:29] slangasek: All in all, I can't tell for sure if it's because our tests are slowly getting less crap or glibc just didn't break many people this time around by becoming more standards-compliant, but this felt rather smooth. [18:40] infinity: indeed [18:41] Oh, FFS upstream, really? [19:26] -queuebot:#ubuntu-release- Unapproved: gnu-efi (bionic-proposed/main) [3.0.4-2 => 3.0.8-0ubuntu1~18.04.1] (core) [19:30] LocutusOfBorg: I'm surprised by the NMU of a-c-c, my patch was not particularly good. What was it impacting in Debian to warrant such a speedy NMU? [19:30] -queuebot:#ubuntu-release- Unapproved: gnu-efi (xenial-proposed/main) [3.0.2-1ubuntu1 => 3.0.8-0ubuntu1~16.04.1] (core) [19:32] Thanks for glibc! [19:33] -queuebot:#ubuntu-release- Unapproved: gnu-efi (trusty-proposed/main) [3.0u+debian-1ubuntu2 => 3.0.8-0ubuntu1~14.04.1] (core) === kstenerud is now known as kstenerud-lunch === kstenerud-lunch is now known as kstenerud [20:03] slangasek, the fact that I don't want to have a delta for such package, I also forwarded all the patches upstream (with your authorship), so they can merge/improve and then sync back [20:03] ... [20:03] I don't see the reason for such a delta, we have the toolchain in sync [20:03] I had to do lots of ubuntu uploads in the past, they have been pita [20:04] 4 of 5 patches were upstreamable as-is [20:04] well, I think that's a questionable rationale for an NMU but that's between you and the maintainer then [20:04] lowNMU threshold, the maintainer *never* answered to me in *years* [20:05] I did 4-5 NMUs for it [20:05] with the delay, and now I stopped caring, I'm basically maintaining it with NMUs in Debian :) [20:06] ok [20:06] slangasek, question: I see ganeti has a test failure on ppc64el, but this "autopkgtest [16:48:37]: test unittests: preparing testbed" is somewhere a new test... [20:07] oh indeed, maybe we can just skip it, it has been probably failing since the begin [20:07] * LocutusOfBorg will double check tomorrow [20:07] * LocutusOfBorg g'night! [20:08] anyway, my patch was a quick-n-dirty implementation that was good enough to unblock autopkgtests but not something I would suggest committing upstream as-is, so hopefully we get some feedback [20:08] new test... yeah that's a bug in how p-m interprets "regression" [20:09] ack, seems legit [20:09] infinity, I'm really worried about glibc and libidn2... [20:09] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905448 [20:09] Debian bug 905448 in src:libidn "libidn: Please package libidn2 2.0.5" [Wishlist,Open] [20:09] glibc 2.28 has replaced its own internal forked idn implementation by [20:09] libidn2. However it requires at least version 2.0.5, while the version [20:09] in Debian testing/unstable is 2.0.4. [20:09] should we sync libidn2? [20:10] LocutusOfBorg: Yes, yes we should. I was waiting for that upload, but didn't notice it happening. [20:10] LocutusOfBorg: "Really worried" is a bit far, mind you. :) [20:11] LocutusOfBorg: But yes, we should sync to a version that doesn't suck. [20:12] * infinity does so. [20:12] LocutusOfBorg: Done. [20:13] * infinity goes to grab food. [20:37] -queuebot:#ubuntu-release- Unapproved: shim (bionic-proposed/main) [13-0ubuntu2 => 15+1533136590.3beb971-0ubuntu1] (core) (sync) [20:37] -queuebot:#ubuntu-release- Unapproved: shim (xenial-proposed/main) [13-0ubuntu2 => 15+1533136590.3beb971-0ubuntu1] (core) (sync) [21:01] infinity: so now that python-cffi built, glibc should migrate in the next few hours? [21:01] or will there be stuff that needs rebuilding still [21:03] mwhudson: already migrated [21:03] I badtested old python-cffi [21:03] oh [21:03] awesomesauce [21:03] since we established it was a bad test [21:03] and I'm a literalist [21:04] heh [21:04] oh that makes sense [21:04] the one in proposed was busted [21:04] but the one in release was just a bogus test [21:06] -queuebot:#ubuntu-release- Unapproved: shim-signed (bionic-proposed/main) [1.34.9.2 => 1.37~18.04.1] (core) [21:08] Woo, below 500 packages in -proposed! \o/ [21:09] 470 as of a few mins ago... [21:11] gnupg2 should probably migrate once the freeipa/4.7.0~pre1+git20180411-2ubuntu2/i386 test passes; it was depwait because of some python-cffi fun Adam and Steve already dealt with. [21:13] Bad snapd tests are bad, no wonder why they fail: [21:13] # cd .; git clone https://github.com/snapcore/spread /tmp/go/src/github.com/snapcore/spread [21:13] Cloning into '/tmp/go/src/github.com/snapcore/spread'... [21:13] fatal: unable to access 'https://github.com/snapcore/spread/': Operation timed out after 300027 milliseconds with 0 out of 0 bytes received [21:13] The real question is why this hasn't failed before... [21:14] But that should get systemd to migrate... [21:16] slangasek, could you please skiptest systemd? it is all green, but snapd. [21:16] slangasek, the snapd in cosmic-release tests regressed due to changes in core/base snaps. [21:16] slangasek, the snapd in proposed appears to be regressed for other reasons at the moment. [21:16] Ah :) [21:17] xnox: Jinx? :) [21:17] tsimonq2, i do not read your messages, no. =) [21:17] xnox: hehe [21:18] i simply noticed emails re:glibc being pushed through. [21:18] Right. [21:18] xnox: Plus my hacky graph showed it :) https://pmstats.lubuntu.me/ [21:34] xnox: done [22:29] what's stopping twisted migrating now? [22:29] oh maybe it just went [22:29] yep [22:37] rbalint: well done :) [23:16] -queuebot:#ubuntu-release- Unapproved: vlc (bionic-proposed/universe) [3.0.3-1-1ubuntu1 => 3.0.4-1ubuntu0.1] (kubuntu, mozilla)