[07:46] <oSoMoN> can someone with upload rights for kopano-webapp trigger an autopkgtest run for eoan/amd64 ? I'd like to verify that my chromium snap patch fixed bug #1834052 indeed
[07:46] <ubottu> bug 1834052 in chromium-browser (Ubuntu) "autopkgtest failures: Chromium-Related in Tests" [Medium,Fix released] https://launchpad.net/bugs/1834052
[07:51] <seb128> LocutusOfBorg, hey, did you see that your iputils upload has a autopkgtest issue?
[07:56] <Unit193> Debian 931491
[07:56] <ubottu> Debian bug 931491 in src:iputils "iputils: FTBFS in sid (missing dependency on setcap)" [Serious,Fixed] http://bugs.debian.org/931491
[07:59] <seb128> Unit193, was that supposed to in reply to what I wrote?
[07:59] <Unit193> seb128: Sorry, not precisely.  It was referenced in the Debian changelog, that's the remaining delta in Ubuntu.
[08:02] <seb128> Unit193, I'm unsure what you are trying to tell me there?
[08:02] <Unit193> seb128: Heh, don't mind it.  It's only loosely related.
[08:03] <seb128> Unit193, I was pointing out the iputils entry on https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages
[08:03] <seb128>     newpid/10: amd64 (log, history), armhf (log, history), i386 (log, history), ppc64el (log, history), s390x (log, history)
[08:04] <seb128> Unit193, our upload didn't fail to build/doesn't have that Debian FTBFS and I don't know about the delta with Debian :)
[08:04] <seb128> but thx for the info still? :)
[08:05] <Unit193> G'morning, anyway. :)
[08:05] <seb128> indeed! :)
[08:13] <Gargoyle> Mornin'
[08:15] <Gargoyle> Laney: Can I DM you sometime today re the Desktop Software Engineer role?
[08:20] <Laney> Gargoyle: Yes, but don't hang around too long
[08:21] <LocutusOfBorg> to answer seb128, I'm in contact with upstream wrt iputils, since some days :D
[08:21] <Unit193> You can't answer him, he left.
[08:21] <LocutusOfBorg> hopefully he might read backlog anyway :)
[08:21] <LocutusOfBorg> or I can just repaste once he is back
[08:24] <Unit193> seb128: < LocutusOfBorg> to answer seb128, I'm in contact with upstream wrt iputils, since some days :D
[08:25] <LocutusOfBorg> that one :) that was the reason lol
[08:28] <LocutusOfBorg> seb128, I don't want to "just update the test with "ping:" before the other expected result, because such changes easily break userspace applications when they are parsing tools' outputs
[08:28] <LocutusOfBorg> so, better ask upstream before uploading
[08:28] <LocutusOfBorg> same for postgresql-11 ppc64el and s390x test failures
[08:34] <LocutusOfBorg> stgraber, hello, there is a question on #release channel for you... wrt docker.io and i386 test failure
[08:35] <seb128> LocutusOfBorg, right, I was just checking you saw it since those don't trigger notifcations (out of the 'is for <n> days in proposed')
[08:42] <LocutusOfBorg> seb128, thanks, I usually open a browser tab when I upload, so I don't miss them, but sometimes they require some more time :)
[08:43] <LocutusOfBorg> seb128, thanks, I usually open a browser tab when I upload, so I don't miss them, but sometimes they require some more time :)
[08:43] <LocutusOfBorg> I usually miss them in SRUs :)
[08:43] <LocutusOfBorg> but thanks for the ping, it is always appreciated!
[08:43] <seb128> yw! thx for follow up with upstream on the issue :)
[08:51] <oSoMoN> xnox, would you mind triggering again http://autopkgtest.ubuntu.com/packages/kopano-webapp/eoan/amd64 ? I'd like to make sure my chromium snap fix did the trick
[08:51] <LocutusOfBorg> oSoMoN, I did it :)
[08:51] <oSoMoN> oh, thanks!
[09:16] <Laney> oSoMoN: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/k/kopano-webapp/20190708_085852_354bf@/log.gz \o\ /o/
[09:18] <oSoMoN> \o/
[09:19] <oSoMoN> thanks Laney
[09:21] <Laney> well done
[09:24] <oSoMoN> Laney, can you revert https://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu/revision/3744 ?
[09:24] <Laney> yes!
[09:24] <Laney> (how do you revert in bzr?)
[09:25] <oSoMoN> bzr merge . -r 3744..3743 IIRC
[09:25] <oSoMoN> or something like that
[09:25] <Laney> bzr merge . -r3744..3743
[09:25] <Laney> works
[09:26] <oSoMoN>  cheers
=== ricab is now known as ricab|lunch
[13:33] <ricotz> sil2100, hi, debian/control wasn't updated in rustc - 1.35.0+dfsg0.1+llvm-0ubuntu1~ppa1
[13:34] <sil2100> ricotz: I know, just re-uploaded
[13:34] <ricotz> good
=== ricab|lunch is now known as ricab
[14:43] <ddstreet> juliank any chance you had time to start review on https://code.launchpad.net/~ddstreet/software-properties/+git/software-properties/+merge/367276
[14:44] <ddstreet> let me know if you have any feedback
[14:46] <juliank> ddstreet: Not yet, I forgot about it, I added a trello card to keep track of it now
[14:46] <ddstreet> thanks
[16:35] <jackpot51> The new AMD Ryzen 3000 series processors are out, and there are serious issues on Ubuntu versions newer than 18.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809
[16:35] <ubottu> Launchpad bug 1835809 in systemd (Ubuntu) "AMD Ryzen 3000 series fails to boot" [Undecided,New]
=== kerneltoast_ is now known as kerneltoast
[17:27] <sumitcn> where is the .css file where I can change the purple color of ubuntu to black
[17:27] <sumitcn> anyone ?
[19:29] <tfgbd_> Why does Ubuntu crash on my PC
[19:31] <tomreyn> also the wrong place, see /topic
[19:50] <CarlFK> tomreyn: -Disco needs updating ;
[20:10] <tfgbd_> I'm using mint now
[21:44] <tomreyn> CarlFK: why?
[21:45] <cjwatson> That range has classically been the currently-supported versions, as opposed to the in-development version (which at least used to be directed to #ubuntu+1), so -Disco seems correct
[21:46] <tomreyn> and surprisingly there's no topic protection on this channel
[21:46] <cjwatson> Sometimes we +t if there's an active problem, otherwise wiki-style lets people be useful
[21:47] <cjwatson> It's mostly not a big deal
[21:47] <tomreyn> i like it (as long as it's not getting abused)
[21:49] <kyrofa> Hey cjwatson, how often do you folks typically go through the proposed unapproved queue? We have a no-change rebuild to python-pygraphviz that we've very much like to get in
[21:49] <cjwatson> kyrofa: I don't at all, it hasn't been adjacent to my duties for over four years
[21:49] <cjwatson> Ask somebody else :)
[21:51] <cjwatson> (I'm still in ~ubuntu-sru for vestigial tool maintenance reasons but don't actually do SRU processing)
[21:52] <kyrofa> Ah, okay
[21:54] <kyrofa> Just curious if there's some sort of established process for this, I guess
[21:54] <kyrofa> Some of those have been there a while
[21:56] <cjwatson> There may well be, I know there's been some kind of recently instituted regular team meeting to try to get through things, but honestly I'm pretty out of the loop
[21:56] <cjwatson> Sometimes process or no process there just isn't enough time ...
[21:57] <CarlFK> tomreyn: opps, my bad.  I thought Eoan was released.  never mind
[21:57] <kyrofa> Darn, I hate annoying people :(
[22:00] <kyrofa> vorlon, can you help me get insight to how the unapproved queue is handled? We have a no-change rebuild to python-pygraphviz queued up for bionic
[22:01] <vorlon> kyrofa: it is roughly FIFO, with no particular SLA on time to review, and if you have something urgent you should ping the SRU team member du jour listed on https://wiki.ubuntu.com/StableReleaseUpdates#Publishing
[22:03] <kyrofa> vorlon, ah excellent, I thought that was only once it was verified, missed that it also covered unapproved, thank you
=== CarlFK1 is now known as CarlFK