[00:45] <tsimonq2> slangasek: Do you typically require bugs for demotion to -proposed?
[00:45] <tsimonq2> slangasek: node-grunt-contrib-concat should be demoted so node-source-map can migrate (along with a few rdeps).
[00:45] <tsimonq2> slangasek: Debian bug 878337, https://github.com/gruntjs/grunt-contrib-concat/issues/188
[00:45] <gitbot> gruntjs issue 188 in grunt-contrib-concat "update for source-map 0.7.x" [Open]
[00:45] <ubot5> Debian bug 878337 in src:node-grunt-contrib-concat "node-grunt-contrib-concat: FTBFS and Debci failure with node-source-map 0.6" [Serious,Open] http://bugs.debian.org/878337
[00:47] <tsimonq2> https://launchpad.net/ubuntu/+source/node-d3-request/1.0.6-3/+build/14813077 O_o wat?
[00:47] <tsimonq2> "Build for superseded Source"
[00:48] <tsimonq2> slangasek: Perhaps even completely remove node-d3-request and node-d3-hierarchy, depending on what this error is. :P
[00:49] <tsimonq2> vim-youcompleteme could be removed as well; ycmd doesn't look like it'll be fixed anytime soon (isn't even in Cosmic at all).
[00:51] <cjwatson> The build must have been superseded when it was previously removed from cosmic-proposed.
[00:51] <cjwatson> Retrying such a build works now that it has an active publishing record again, though.  I've done that.
[00:52] <tsimonq2> Huh.
[00:52] <tsimonq2> That's a new one (for me).
[00:52] <cjwatson> The package was probably removed when the build wasn't in a terminal state.
[00:52] <cjwatson> Somewhat unusual but happens occasionally.
[00:52] <tsimonq2> Ah.
[00:53] <cjwatson> (Or, more specifically, when it was in "Needs building".)
[00:54] <cjwatson> That state more usually happens when the source package is superseded by a newer version (hence the name) before the previous builds had been dispatched.
[00:55] -queuebot:#ubuntu-release- New binary: node-d3-request [amd64] (cosmic-proposed/universe) [1.0.6-3] (no packageset)
[00:57] -queuebot:#ubuntu-release- New: accepted node-d3-request [amd64] (cosmic-proposed) [1.0.6-3]
[00:59] <tsimonq2> cjwatson: Could you do binary NEW processing on the other package when it goes in the queue as well?
[00:59] <tsimonq2> node-d3-hierarchy
[01:04] -queuebot:#ubuntu-release- New binary: node-d3-hierarchy [amd64] (cosmic-proposed/universe) [1.1.5-2] (no packageset)
[01:55] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-7 [amd64] (cosmic-proposed) [1:7~+rc2-1~exp2]
[01:55] -queuebot:#ubuntu-release- New: accepted node-d3-hierarchy [amd64] (cosmic-proposed) [1.1.5-2]
[03:52] <slangasek> tsimonq2: I don't typically /do/ demotions to proposed; if it's bad enough to be removed from release I usually don't want it hanging around in -proposed either
[03:52] <tsimonq2> slangasek: Ah.
[04:03] <slangasek> tsimonq2: node-grunt-contrib-concat has 5 reverse-build-dependencies, I'm not going to remove it without a plan for sorting those
[04:04] <tsimonq2> slangasek: ack
[07:02] -queuebot:#ubuntu-release- Unapproved: tkblt (bionic-proposed/universe) [3.2.7-1 => 3.2.7-1ubuntu1] (no packageset)
[07:20] <acheronuk> [07:20] <acheronuk> slangasek: suddenly getting some armhf tests fail with "mkdir: cannot create directory ‘//.config’: Permission denied"
[07:20] <acheronuk> another http://autopkgtest.ubuntu.com/packages/k/kcoreaddons/cosmic/armhf
[07:21] <acheronuk> thinking home is / by the looks of it
[07:21] <acheronuk> something amiss with armhf runners
[07:24] <jibel> The pending sru report is out of date (last update 2 days ago), could someone have a look?
[07:26] <tsimonq2> cjwatson: ^ This wouldn't happen to be related to MoM, would it?
[07:43] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (bionic-proposed) [4.15.0-1023.24]
[07:43] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (xenial-proposed) [4.15.0-1023.24~16.04.1]
[08:27] <cjwatson> tsimonq2: no, they're pretty independent
[08:28] <cjwatson> jibel: I've killed the stuck run, so it should recover soon
[08:30] <jibel> cjwatson, thanks
[08:50] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (bionic-proposed/main) [1.1ubuntu1.18.04.5 => 1.1ubuntu1.18.04.6] (desktop-core, ubuntu-server)
[10:43] <LocutusOfBorg> infinity, hello, diaspora-installer is regressed testsuite, because of glibc
[10:43] <LocutusOfBorg> unfortunately testsuite is downloading a gem file from internet, and there is no new upstream version...
[10:43] <LocutusOfBorg> what do you propose?
[10:43] <LocutusOfBorg> the result seems clear: linux_sigar.c:1177:22: error: called object ‘major’ is not a function or
[10:44] <LocutusOfBorg> of course release pocket is fine because of old glibc
[10:45] <LocutusOfBorg> I'm testing diaspora-installer from debian
[10:52] -queuebot:#ubuntu-release- Unapproved: rejected magnum [source] (bionic-proposed) [6.1.1-0ubuntu0.18.04.1]
[10:52] -queuebot:#ubuntu-release- Unapproved: rejected magnum [source] (bionic-proposed) [6.1.1-0ubuntu0.18.04.1]
[10:52] -queuebot:#ubuntu-release- Unapproved: rejected magnum [source] (bionic-proposed) [6.1.1-0ubuntu0.18.04.1]
[11:03] -queuebot:#ubuntu-release- Unapproved: accepted base-files [source] (bionic-proposed) [10.1ubuntu2.3]
[11:20] <slashd> o/ sil2100, can you please release gdm3 for 'X' when you have a moment today | LP: #1782152 ?
[11:20] <ubot5> Launchpad bug 1782152 in gdm3 (Ubuntu Bionic) "GDM blocks SIGUSR1 used in PAM scripts" [Medium,Fix committed] https://launchpad.net/bugs/1782152
[11:21] <slashd> sil2100, and 'python-urllib3' for 'X' as well | LP: #1771988
[11:21] <ubot5> Launchpad bug 1771988 in Ubuntu Cloud Archive mitaka "certificate validation with IP address based SAN's fails" [High,In progress] https://launchpad.net/bugs/1771988
[11:34] <sil2100> slashd: hey! I'll take a look after lunch, my problem with gdm3 when I was doing releases in the morning was that bionic isn't verified yet - e.g. there's 3 bugs in it but 2 not verified yet
[11:34] <sil2100> slashd: usually we want later series to be released - not a hard rule though
[11:42] -queuebot:#ubuntu-release- Unapproved: libreoffice (bionic-proposed/main) [1:6.0.3-0ubuntu1 => 1:6.0.6-0ubuntu0.18.04.1] (kubuntu, ubuntu-desktop)
[12:07] -queuebot:#ubuntu-release- Unapproved: ubuntu-report (bionic-proposed/main) [1.2.0~bionic => 1.3.0~18.04] (no packageset)
[12:13] -queuebot:#ubuntu-release- Unapproved: libreoffice-l10n (bionic-proposed/main) [1:6.0.3-0ubuntu1 => 1:6.0.6-0ubuntu0.18.04.1] (ubuntu-desktop)
[12:19] <slashd> sil2100, tks for python-urllib3
[12:21] <sil2100> slashd: as for gdm3... I would prefer to wait for bionic in this case, especially that it's a new upstream release
[12:21] <sil2100> So even though small, there's a risk it might introduce some regressions and actually get removed from -proposed
[12:22] <sil2100> Problem is I think Lan_ey is away this week still, so someone else would have to verify it
[12:23] <slashd> sil2100, ack thanks
[12:23] <slashd> dgadomski, fyi ^
[12:28] -queuebot:#ubuntu-release- Unapproved: accepted maas [source] (bionic-proposed) [2.4.2-7034-g2f5deb8b8-0ubuntu1]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (bionic-proposed) [18.04.14.8]
[12:55] -queuebot:#ubuntu-release- Unapproved: accepted qtdeclarative-opensource-src [source] (bionic-proposed) [5.9.5-0ubuntu1.1]
[13:01] <Trevinho> sil2100: hey, could you please accept glib from bionic queue?
[13:02] <Trevinho> actually I've an extra fix on https://bileto.ubuntu.com/#/ticket/3393 but needs to be published first
[13:08] <sil2100> Trevinho: ok, I'll get to it in a minute
[13:12] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (bionic-proposed/main) [2.525.7 => 2.525.8] (desktop-core)
[13:13] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (bionic-proposed) [2.525.8]
[13:16] <LocutusOfBorg> any AA wants to fix this? https://bugs.launchpad.net/ubuntu/+source/anbox/+bug/1780655
[13:16] <ubot5> Ubuntu bug 1780655 in anbox (Ubuntu) "RoM: please remove this from ubuntu, doesn't work" [Undecided,New]
[13:19] <Trevinho> sil2100: thanks
[13:19] <Trevinho> also if you can land that ppa would be nice :)
[13:19] <Trevinho> so we get both in a shot
[13:25] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (bionic-proposed) [2.525.8]
[13:35] <sil2100> Trevinho: so just to know for sure, you want to overwrite the upload that's in Unapproved with the one in the silo?
[13:36] <Trevinho> sil2100: if that's possible yes, otherwise we can reiterate later
[13:36] <Trevinho> but I was waiting upstream to apply that patch before adding it, now it's merged, so...
[13:45] <sil2100> I need to see how the .changes file looks
[13:46] <sil2100> Since I guess right now if I publish this, the SRU tools will miss the previous upload
[13:47] <sil2100> Because the .changes file was generated without -v, so no mention of .1 in it
[13:48] -queuebot:#ubuntu-release- Unapproved: accepted unbound [source] (bionic-proposed) [1.6.7-1ubuntu2.2]
[13:51] <sil2100> Trevinho: ok, in this case I can either review the one that's already in the queue or I guess I'd have to ask you prepare a new upload that would include both the fixes
[13:51] <sil2100> (or have both versions mentioned in the .changes file)
[13:54] <Trevinho> sil2100: well, so go with queue, I'll prepare the sru of the other later
[13:54] <Trevinho> as i also wanted to mention the commit in the dep
[14:08] <sil2100> Trevinho: ok!
[14:09] -queuebot:#ubuntu-release- Unapproved: binutils (xenial-proposed/main) [2.26.1-1ubuntu1~16.04.6 => 2.26.1-1ubuntu1~16.04.7] (core)
[14:15] -queuebot:#ubuntu-release- New binary: vmware-nsx [amd64] (cosmic-proposed/universe) [13.0.0-0ubuntu1] (no packageset)
[14:15] <seb128> Trevinho, it reminds me we need to reupload your nautilus SRU that got rejected because the version was not "standard enough" :/
[14:16] <Trevinho> seb128: at this point if you want to wait for the search fix....
[14:16] <seb128> no
[14:16] <seb128> because that's another set of packages
[14:16] <seb128> and I don't want to make the SRU too complicated
[14:16] <seb128> I would prefer the search fix set to be that onlu
[14:16] <seb128> only
[14:17] <Trevinho> ok
[14:17] <seb128> Trevinho, can you "fix"/amend the bionic branch in git to what it should
[14:17] <seb128> your git foo is better than mine, I would probably manage after some googling and poking around, but "uncommit" is not something I know how to do properly yet
[14:18] <seb128> shrug, it's annoying that we delay fixes for our LTS users and create work for ourself just to be pedentic of versioning
[14:18] <seb128> but oh well, let's keep the ranting for another day
[14:23] <ahasenack> any idea why txtorcon is "missing build"? 18.0.2-2 build on Aug 21st http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#txtorcon
[14:24] <ahasenack> oh, it's looking for a "python-txtorcon" deb...
[14:24] <seb128> ahasenack, because it is, see the changelog on https://launchpad.net/ubuntu/+source/txtorcon/18.0.2-2
[14:24] <seb128>   * No longer builds a Python 2 package (Closes: #905253)
[14:24] -queuebot:#ubuntu-release- Unapproved: grub2-signed (bionic-proposed/main) [1.93.4 => 1.93.5] (core)
[14:25] <seb128> that binary needs to be deleted from cosmic if it has no rdepends
[14:25] <ahasenack> so it needs a manual poke when a deb goes missing
[14:25] <seb128> reverse-depends lists ooniprobe though
[14:25] <seb128> so that might need to be fixed first
[14:26] <sergiusens> sil2100: evening! I have a request for you if you can spare the moment, mind taking a look at getting snapcraft into the -updates (LP: #1787419)?
[14:26] <ubot5> Launchpad bug 1787419 in snapcraft (Ubuntu Bionic) "[SRU] New stable micro release 2.43" [Undecided,Fix committed] https://launchpad.net/bugs/1787419
[14:26] <ahasenack> seb128: thanks
[14:26] <seb128> ahasenack, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905211 is a request to remove that one from Debian, maybe the path to go
[14:26] <ubot5> Debian bug 905211 in ftp.debian.org "RM: ooniprobe -- ROM; not easily maintained; too many js deps" [Normal,Open]
[14:26] <seb128> yw!
[14:27] <ahasenack> that is blocking twisted now
[14:27] <ahasenack> after a long chain of deps
[14:27] <ahasenack> iiuic
[14:29] <sil2100> sergiusens: sure!
[14:29] <ahasenack> twisted -> foolscap -> txtorcon
[14:34] <seb128> should be fine to rm ooniprobe and python-txtorcon
[14:42] <sergiusens> sil2100: as always, thank you very much!
[14:50] <slangasek> acheronuk: tests shouldn't be writing to $HOME anyway, this would be a buggy test, not a broken test runner
[14:51] <slangasek> acheronuk: if the software requires $HOME to be set somewhere sane, then it should be pointed somewhere in the tree by the test itself
=== chrisccoulson_ is now known as chrisccoulson
[15:27] <acheronuk> slangasek: it is https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kcoreaddons/tree/debian/tests/testsuite?h=kubuntu_cosmic_archive
[15:28] <acheronuk> but clearly the armhf runners have changed so if is skipping that with a home of / it can't write to
[15:30] <acheronuk> slangasek: test for update manager on armf are also sometimes getting the same
[15:30] <acheronuk> slangasek: mkdir() failed: '[Errno 13] Permission denied: '/.cache''.
[15:36] <slangasek> acheronuk: yes, it's categorically wrong to use a $HOME from the environment in a package build or autopkgtest
[15:37] <acheronuk> slangasek: I can change kde tests not to, but I can't for update-manager
[15:37] <slangasek> well, Foundations should certainly fix our bug also :)
[15:37] <slangasek> bdmurray: ^^ ?
[15:39] <bdmurray> slangasek: update-manager uses $HOME in its autopkgtests is that correct?
[15:39] <acheronuk> bdmurray: it's filing some tests with "mkdir() failed: '[Errno 13] Permission denied: '/.cache''."
[15:40] <acheronuk> *failing
[15:40] <slangasek> bdmurray: sounds like it's relying on $HOME from the caller environment yes, and it shouldn't; it should set its own local $HOME for use
[15:41] <acheronuk> not sure of the package's fault or somthing like pytest/nose
[15:42] <acheronuk> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/update-manager/20180829_133612_1ecf1@/artifacts.tar.gz
[15:42] <acheronuk> nose-tests-stout with the error
[15:43] <acheronuk> again, only on armhf
[15:44] <acheronuk> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/update-manager/20180829_133612_1ecf1@/log.gz
[16:45] -queuebot:#ubuntu-release- Unapproved: debian-installer (trusty-proposed/main) [20101020ubuntu318.43 => 20101020ubuntu318.44] (core)
[17:55] <bdmurray> xnox: Can you add SRU info to bug 1781242?
[17:55] <ubot5> bug 1781242 in Ubuntu on IBM z Systems "as segfault with invalid -march= option" [Low,In progress] https://launchpad.net/bugs/1781242
[18:27] -queuebot:#ubuntu-release- Unapproved: accepted glib2.0 [sync] (bionic-proposed) [2.56.2-0ubuntu0.18.04.1]
[18:38] -queuebot:#ubuntu-release- Unapproved: accepted network-manager-openconnect [source] (bionic-proposed) [1.2.4-1ubuntu1]
[18:40] <jbicha> bdmurray: sorry about the ridiculous 16.4 MB diff for fonts-noto-color-emoji/bionic
[18:42] <bdmurray> jbicha: Its so ridiculous I'm going to save it for last
[18:42] -queuebot:#ubuntu-release- Unapproved: accepted nova-lxd [source] (bionic-proposed) [17.0.1-0ubuntu1]
[18:43] <jbicha> no problem
[19:10] -queuebot:#ubuntu-release- Unapproved: accepted avahi [source] (bionic-proposed) [0.7-3.1ubuntu1.1]
[19:15] -queuebot:#ubuntu-release- Unapproved: accepted fpc [source] (bionic-proposed) [3.0.4+dfsg-18ubuntu2]
[19:19] -queuebot:#ubuntu-release- Unapproved: accepted tkblt [source] (bionic-proposed) [3.2.7-1ubuntu1]
[19:24] <bdmurray> rbalint: Can you add SRU info to bug 1785093?
[19:24] <ubot5> bug 1785093 in unattended-upgrades (Ubuntu) "RecursionError error in call_adjusted() when package is pinned < 100" [Undecided,Fix released] https://launchpad.net/bugs/1785093
[19:34] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-report [source] (bionic-proposed) [1.3.0~18.04]
[19:46] <bdmurray> jbicha: Could you add some more details to the regression potential of that fonts-noto-color-emoji bug?
[19:49] <jbicha> do you have suggestions? that part of an SRU is the hardest for me to come up with something that feels useful
[19:51] <jbicha> my point there was that Google ships this to their customers. But we are rebuilding it so our version isn't necessarily exactly what they test and release
[20:28] <rbalint> bdmurray, updated the SRU, but the test is missing for now because i suspected pinning to be the trigger but it turned reading (down-)pinning did not work in python-apt basically at all
[20:53] <bdmurray> jbicha: What could go wrong in the rebuild process? How would we know something was busted?
[20:53] <jbicha> there is a test case
[20:53] <jbicha> I've never seen a problem building it yet
[20:56] <jbicha> do you like the regression potential in bug 1766736? 🤠 (it was accepted before release so wasn't an SRU)
[20:56] <ubot5> bug 1766736 in fonts-noto-color-emoji (Ubuntu Bionic) "Update Noto Emoji to April 2018" [Low,Fix released] https://launchpad.net/bugs/1766736
[20:58] <bdmurray> jbicha: The Regression Potential is an estimate of severity or likelihood rather what could go wrong and how can we watch out for it.
[20:58] <bdmurray> s/is/isn't/
=== sergiusens_ is now known as sergiusens
[21:23] <jbicha> I added a sentence now. Sorry if I seem to be making this difficult :(
[21:37] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (cosmic-proposed/main) [4.18.0-7.8] (core, kernel)
[21:39] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (cosmic-proposed/main) [4.18.0-7.8] (core, kernel)
[22:05] <slangasek> someone here know why lubuntu images failed with a complaint that libreoffice-kde4 is not installable (which indeed it is not, it is only in cosmic-proposed)?
[22:05] <slangasek> has someone been removing binaries that have revdeps?
[22:06] <slangasek> perhaps this was meant to be removal of the NBS libreoffice-kde4 binary that's in cosmic-proposed
[22:07]  * slangasek attempts to resuscitate
[22:07] <tsimonq2> That's interesting, because we depend on libreoffice-kde, not kde4, because the kde5 one should (!) land either in this cycle or next.
[22:07] <tsimonq2> Thanks slangasek.
[22:09] <tsimonq2> Oh, so it *did* land, and it's in -proposed...
[22:09] <tsimonq2> Nice.
[22:09] <slangasek> yeah, seb128 removed the wrong one by mistake (https://launchpad.net/ubuntu/cosmic/amd64/libreoffice-kde4)
[22:09] <tsimonq2> Ah.
[23:11] <acheronuk> linux-image-generic/amd64 unsatisfiable Depends: linux-image-4.18.0-7-generic
[23:11] <acheronuk> not good
[23:12] <slangasek> why are you pulling from cosmic-proposed?
[23:15] <acheronuk> pulling what?
[23:17] <slangasek> acheronuk: linux-image-generic
[23:17] <acheronuk> was a test failure: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/a/akonadi-search/20180830_223519_e60a9@/log.gz
[23:18] <slangasek> ok
[23:18] <slangasek> so pulling from cosmic-proposed because --all-proposed, fair enough :)
[23:18] <slangasek> should be fixable with a retry
[23:21] <acheronuk> well, I triggered against several package versions in -proposed instead. but if that fixing itself anyway, then :)