[05:31] <RAOF> Aaargh. How do I convince Launchpad that my gpg key is not expired? keyserver.ubuntu.com sees my keys with an expiry of 2019-06-07!
[05:40] <jamesh> RAOF: try pushing your key to keyserver.ubuntu.com?
[05:40] <jamesh> oh.  It already has the up to date version
[05:41] <RAOF> Yup! It's been up there for a number of weeks.
[06:21] <jamesh> RAOF: are you able to remove and re-add the key?
[06:21] <jamesh> I'm just wondering if it stops checking the key once it believes it is expired
[06:23] <RAOF> jamesh: not on launchpad. I can deactivate, and then fall to reactivate because launchpad considers the key expired, though 🤦‍♂️
[06:26] <RAOF> There's apparently an ongoing failure with key server replication.
[06:30] <jamesh> My memory was that the gpg code in LP would always start by importing the key, so it shouldn't be a stale version of the key in a ~/.gnupg directory on the app server
[07:05] <RAOF> popey https://bugs.launchpad.net/snapcraft/+bug/1817553 is the `nodejs` plugin failing to handle the simplified case of a single binary; if you can mangle the package.json you can work around it by turning it into the equivalent dictionary.
[11:00] <lesshaste> is it technically possible to boot off a USB stick (say) from a running linux install? This would be to save having to reboot through a BIOS you can't reconfigure for example
[11:11] <SwedeMike> lesshaste: https://linux.die.net/man/8/kexec ?
[11:30] <lesshaste> SwedeMike, that looks exactly it.. thank you
[11:31] <lesshaste> SwedeMike, well it solves the problem of changing kernel.. Now I have to work out how to actually go through the whole boot process
[16:09] <tomreyn> after a chromium-browser crash whoopsie states it cannot report it because "BFD: warning: /tmp/apport_core[..] is truncated" - the core file was indeed truncated. should ubuntu raise those limits in general if some RAM heavy apps are becoming more and more common?
[16:10] <doko> oSoMoN: when do you plan the next lo upload for bionic?
[16:24] <teward> anyone know why debuild and such can't verify my new PGP key that I'm using for things, even though I have the private key and such in my keyring...? o.O
[16:26] <ahasenack> hi, any idea why the backuppc dep8 tests didn't run for trusty? http://people.canonical.com/~ubuntu-archive/proposed-migration/trusty/update_excuses.html#backuppc
[16:26] <seb128> teward, did you use -k<...> or change the default?
[16:26] <ahasenack> this is an update that added them
[16:26] <ahasenack> it worked in the xenial case (http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#backuppc)
[16:26] <LocutusOfBorg> teward, ~/.devscripts ?
[16:26] <teward> seb128: shouldn't it inherit DEBSIGN_KEYID from devscripts?
[16:27] <teward> 'cause the key i'm signing with and it's prompting for my passcode for *is* the key i've stated in that in devscripts
[16:27] <seb128> what error do you get?
[16:28] <LocutusOfBorg> somewhere I exported also DEB_SIGN_KEYID
[16:28] <teward> seb128: ahhh I see, it's when i dput and it tries to sig-verify it fails
[16:28] <teward> but debuild works without issue and DOES sign with the key
[16:28] <teward> *needs more coffee*
[16:29] <teward> still interesting that dput won't verify the signature with the key that's in my keyring :|
[16:30] <teward> or does it use a different keyring?
[16:34] <teward> ahhh i see what happened
[16:34] <teward> seb128: looks like when gpg created my new private and public key pair I'm using, it didn't set the local trust to 'ultimate'.  WHoopsies?
[16:34] <teward> (verification errors have since ceased)
[16:40] <oSoMoN> doko, can do today, shall I use bug #1814133 in the changelog ?
[16:51] <doko> oSoMoN: sure
[16:51] <doko> oSoMoN: I already prepared writer2latex
[16:52] <oSoMoN> ok, I'll prepare an upload soon
[16:56] <doko> oSoMoN: please let me know where I can find it. Need to build it against the security pocket
[17:04] <CarlFK> what are the chances of 50MB being added to http://cdimage.ubuntu.com/ubuntu-server/daily/pending/disco-server-amd64.iso  752M
[17:05] <sladen> 50MB(?)(!)
[17:05] <CarlFK> which will then bump into bug 1807047
[17:06] <CarlFK> \wondering about translation strings or whatever isn't there now but was there for http://cdimage.ubuntu.com/ubuntu/releases/18.04/release/ubuntu-18.04.2-server-amd64.iso 883M
[17:16] <bdmurray> jbicha: Why were these patches dropped in gnome-desktop3 for cosmic?
[17:34] <oSoMoN> doko, https://people.canonical.com/~osomon/libreoffice-6.0.7/
[17:43] <jbicha> bdmurray: because they were included in the new release
[17:47] <bdmurray> jbicha: Got it, I can read now.
[17:56] <doko> oSoMoN: ta, could you upload to ppa:openjdk-11-transition/apps
[17:57] <oSoMoN> doing
[18:10] <oSoMoN> d’oh, my uploads were rejected because they target the security pocket…
[19:37] <vorlon> xnox: do your comments on LP: #1815691 mean you believe the bug is invalid?
[19:48] <bdmurray> vorlon: There's no way for an ordinary user to see that kernel message so I think it should be surfaced better.
[19:48] <vorlon> bdmurray: did making the firmware config change solve the problem for you?
[19:49] <bdmurray> vorlon: I haven't tested that but guess I probably could w/o losing anything.
[19:59] <vorlon> kees, stgraber, mdeslaur, infinity: TB meeting ping
[20:03] <vorlon> bdmurray: if you now have timeouts in apport for gdb hangs, is there anything further to do on https://bugs.launchpad.net/apport/+bug/1760207 ?
[20:40] <bdmurray> vorlon: No, I think I missed flipping it to Fix Released when updating the retracers.
[20:44] <bdmurray> vorlon: although it'd still be best if apport were to install the libc6 version from the crash report as the gdb dep if the gdb dep is unversioned.
[20:47]  * vorlon nods
[20:51] <bdmurray> vorlon: I'll make that a separate bug though
[20:51] <vorlon> ok