[09:43] <AnAnt> hello
[09:54] <AnAnt> test
[09:55] <AnAnt> bye
[11:18] <dosaboy> sil2100: hi, is there any way you could review the neutron upload in https://launchpad.net/ubuntu/cosmic/+queue?queue_state=1
[11:19] <dosaboy> im keen to get the regressed prior sru all sorted with the new patch
[11:19] <dosaboy> sahid: ^^
[11:24] <sil2100> dosaboy: o/ on a sprint here, but I think I can do that today no problem
[11:25] <dosaboy> sil2100: many thanks
[11:25] <sahid> dosaboy: i don't have the privilege :)
[11:25] <dosaboy> sahid: i know, was just adding you for awareness ;)
[11:25] <sahid> ok cool thanks :)
[12:42] <xnox> zyga, should python-guacamole be removed from debian/ubuntu? it seems to have only been used by checkbox&friends.
[12:42] <zyga> yes
[12:43] <xnox> zyga, is it "stable" and used from the archive?
[12:43] <zyga> please
[12:43] <xnox> zyga, ack.
[12:43] <zyga> I don't think it got picked up by anything, I'm no longer interested in it
[13:04] <cyphermox> tsimonq2: packageset> sure; but I'd be careful with that part; there are a few reasons why golang was showing up there.
[13:05] <tsimonq2> cyphermox: More than just ubuntu-report?
[13:06] <cyphermox> IIRC yes
[13:06] <cyphermox> or was it for ubuntu-mate?
[13:07] <cyphermox> anyway, I'll update and see
[13:07] <cyphermox> that said, I don't think you should compromise on things you want to include on the image because some other bits are showing up in the packageset list
[13:08] <cyphermox> (assuming you care about ubuntu-report)
[13:57] <teward> does anyone knokw if there's a way to have an at-boot SystemD unit that can be interrupted with a specific keypress?
[13:57] <teward> asking because of something that was asked of me from the Lubuntu guys
[14:02] <cjwatson> Maybe something involving plymouth watch-keystroke?
[14:02] <cjwatson> Will likely involve some assembly
[14:37] <bdmurray> infinity, vorlon: I forget where does sarnold's bug belong? bug 1824597
[14:38] <infinity> bdmurray: It's a non-bug.
[14:39] <bdmurray> infinity: but is there a project for archive type issues?
[14:40] <infinity> launchpad?
[14:48] <cjwatson> I agree that's a non-bug, and it would be Launchpad yes.
[14:48] <cjwatson> I'll reassign and close
[14:49] <cjwatson> (maybe should've been wontfix, but either way)
[14:53] <cyphermox> Laney: need help with casper?
[14:53] <Laney> cyphermox: definitely
[14:54] <Laney> I got distracted but also I don't have much clue anyway
[14:54] <cyphermox> ok
[14:54] <cyphermox> I'm not sure I'll have much more of a clue, but willing to have a look
[14:54] <Laney> what's a good way to be able to do stuff in that environment?
[14:54] <Laney> like why does plymouth show the completed message but not the in-progress ones? it is a mystery to me
[14:56] <Laney> but I don't know how to poke at stuff in there either so it's hard to get started
[14:57] <cyphermox> yeah
[15:00] <tsimonq2> cyphermox: ubuntu-report> We have no userspace tool that uses it, and I'm not sure why I seeded it in the first place.
[15:00] <cyphermox> tsimonq2: *shrugs*
[15:01] <tsimonq2> cjwatson: involving some assembly> Sounds fun. Is there anything particularly notable about implementing such a program, or do I just dig in Plymouth libraries? Our goal here (at least, a tentative idea for what we'd like to see) is here: https://phab.lubuntu.me/T32
[15:03] <tsimonq2> tl;dr every time someone comes to #lubuntu with failed installation problems, we usually ask them to verify the checksum of their media, and that's the problem a lot of the time. Therefore, making it automatic where verification is done on boot (and can be exited via the Esc key) would theoretically reduce installation problems.
[15:03] <tsimonq2> Fedora already implements this; I haven't actually looked at how they implement it, but it seems possible if you don't think it's an insane idea.
[15:05] <tsimonq2> (Of course, this is something to look at post-release, and Lubuntu would drive development/testing of it, but if it would be cool if it could be more generally used.)
[15:21] <sil2100> mvo: hmmm, looking at the snapd SRU humm
[15:29] <mvo> sil2100: you don't like it?
[15:30] <sil2100> mvo: strangely, the xenial snapd package FTBFS on powerpc (re-run didn't help, let me look at the build-log)
[15:30] <sil2100> mvo: we probably wouldn't care normally, but we did build for that arch previously
[15:30] <mvo> sil2100: yeah, its a sad story, there is no go-1.10 for powerpc
[15:31] <mvo> sil2100: I talked to vorlon about this too, the agreement was that powerpc for snaps was always not really supproted, we don't have a powerpc core snap for example. so we ignore the powerpc failure
[15:31] <mvo> sil2100: its unfortunate, I wish I could keep it alive
[15:32] <sil2100> mvo: ah, now I actually see that we indeed don't have it for that arch, ok
[15:34] <mvo> sil2100: sorry for the confusion
[15:34] <pedahzur> rbasak: You around? I finally have some time to work on the SRU for https://bugs.launchpad.net/ubuntu/+source/adcli/+bug/1821242
[15:36] <infinity> mvo: I think from the POV of making migration tools less grumpy (but also a bit of a best practice for making packages clearly "unsupported") you should produce empty packages on powerpc.
[15:37] <rbasak> pedahzur: what do you need?
[15:37] <infinity> Althought, vorlon seems to have made britney happy somehow.
[15:37] <infinity> "happy"
[15:38] <mvo> infinity: indeed, I can do that
[15:38] <infinity> Ahh, fuaxpackages.
[15:38] <infinity> faux.
[15:39] <infinity> mvo: Yeah, I think empty packages would be better than the FauxPackages entry in britney.
[15:39] <infinity> mvo: But certainly can wait for the next release.
[15:40] <mvo> infinity: yeah, thanks for the suggestions, thats totally reasonable
[15:43] <pedahzur> We had talked the other day about walking through the SRU process for that bug. It's all new to me. I've never submitted a deb-diff, etc.  If there are docs I've missed, feel free to point me in that direction. :)
[15:45] <tsimonq2> pedahzur: The (lowercase c) canonical docs for SRUs are here: https://wiki.ubuntu.com/StableReleaseUpdates
[15:46] <xnox> slashd, jamespage - what am i missing about https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1822872 ? =)
[15:47] <xnox> slashd, jamespage - libssl/libcrypto 1.0 and 1.1 are coinstallable and both are support in bionic, in main from now and until forever.
[15:47] <xnox> so what's broken?
[15:48] <pedahzur> tsimonq2: Thanks I have read through that. Most of it makes sense. Creating the deb diff is something I've never done. Is there a HOWTO for that?
[15:48] <xnox> slashd, jamespage - sound slike load_dll should be dll opening libcrypto.so.1.0 if that's what it expects?
[15:50] <xnox> slashd, jamespage - imho we should builddepend on libssl1.0 and set CIVETWEB_SSL_SSL_LIB and CIVETWEB_SSL_CRYPTO_LIB to versioned sonames of libssl.so.1.0 and libcrypto.so.1.0
[15:51] <tsimonq2> pedahzur: I don't think so; the manpage should have details, but the short of it is, you have the dsc and associated files for the package in the archive, and after you run debuild with your changes and new version, have another set of files. You just run debdiff EXISTING.dsc NEW.dsc - that's the gist of it.
[15:52] <jamespage> xnox, slashd: tbh I think that's fine
[15:52] <jamespage> I'm easy either way - slashd are you ok to SRU that?
[15:53] <slashd> jamespage, yeah I can SRU the libssl-dev downgrade to 1.0
[15:53] <xnox> jamespage, well reading the code, it sounds slightly harder. cause WITH_RADOSGW tries to build with SSL_INCLUDE_DIR
[15:53] <jamespage> slashd: great
[15:53] <slashd> jamespage xnox thanks
[15:54] <xnox> slashd, if it works. cause it does look that radosgw, rgw, civetweb all need to use libssl1.0-dev then.
[15:55] <xnox> slashd, ah, and that's all that does ssl there, so it's fine.
[16:01] <cjwatson> tsimonq2: I dunno, sorry, just wanted to give an initial pointer
[16:03] <slashd> xnox, jamespage : what about this https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589 do you think it might be a problem ?
[16:04] <xnox> slashd, that's intentional yes. won't fix.
[16:04] <slashd> ok
[16:04] <xnox> slashd, and we reverted and forced to use libssl1.0-dev with nodejs 8 in bionic
[16:05] <xnox> slashd, and one should use libssl-dev (aka 1.1) with nodejs in disco.
[16:05] <slashd> xnox, ok
[16:05] <xnox> vorlon, infinity ^^^^
[16:05] <slashd> xnox, no regression came up of nodejs ?
[16:05] <pedahzur> tsimonq2: OK. I'll see what I can figure out. Thanks!
[16:06] <xnox> slashd, everywhere, including upstream uses 1.0 for 8.x series, and 1.1 for 11.x series (or whatever the new lts series is)
[16:06] <vorlon> yeah, I had already wontfixed that bug and someone reopened it for bogus reasons and I didn't bother fighting it
[16:07] <vorlon> the only regression is that the set of packages whose build-dependencies are coinstallable is reduced
[16:09] <tsimonq2> pedahzur: No problem! Let me know if you have any other questions :)
[17:09] <vorlon> seb128: have I filed LP: #1824855 in the right place?
[17:34] <seb128> vorlon, hey, good enough, it's more likely to be gnome-shell which does the rendering but I guess Daniel will reassign tomorrow when he does his daily triaging round ... do you have an idea of the number of notifications you had? were they mostly from the same source? (jouirnal log might be useful maybe also) (why diddn't apport attach it?)
[17:35] <vorlon> seb128: journal> no idea, maybe it would've attached something different if I'd filed it against gnome-shell instead?  number of notifications> well my desktop is configured to produce a notification for every single IRC highlight, so I guess several
[17:36] <vorlon> seb128: 141 of those since my last reobot
[17:36] <vorlon> reboot
[20:20] <vorlon> seb128: hi, another fun bug: LP: #1824874
[20:22] <seb128> vorlon, screenshot/screencast done from your phone could be useful, looks like probably a shell issue (journal log could be useful as well)
[20:23] <vorlon> seb128: screenshot attached
[20:24] <vorlon> what exactly do you want out of the journal?
[20:24] <seb128> vorlon, I couldn't reproduce the notification issue, I tried with a for loop with notify-send -u critical (so they show on the lock screen) and some hundred notifications, the unlock prompt displays like in a second on a slow inspiron 11 machine
[20:24] <seb128> vorlon, gnome-shell potential warnings
[20:26] <vorlon> seb128: ok I'll wait and see if I can reproduce the lock screen issue again
[20:58] <DurkeyWorm> is there any documentation on how the iso files are generated?
[20:58] <DurkeyWorm> the ones for public release?