[06:33] <cpaelzer> rbasak: yes I knew about the DPDK MRE ack, sil also did the wiki update
[06:33] <cpaelzer> rbasak: was there a follow on action I missed?
[06:34] <cpaelzer> rbasak: or was this "just" still on your personal todo and I should have let you know that it is done?
[06:35] <cpaelzer> rbasak: just checked the mail he sent and (now checking receipients more closely) see that it was only me and dpb1
[07:38] <slangasek> looks like ubuntu-budgie builds are going to be broken for a bit, since they pull in linux-tools-*, which is the package we broke to let the mpfr4 transition finish.  But why does Budgie install linux-tools, anyway?
[07:50] <LocutusOfBorg> folks, with guile fixed, I plan to land ticket 3141 in 10h if nobody complains
[07:51] <LocutusOfBorg> the rebuilds have worked correctly, and silo is happy with the diffs
[08:20] -queuebot:#ubuntu-release- Unapproved: accepted util-linux [source] (xenial-proposed) [2.27.1-6ubuntu3.5]
[09:56] <rbasak> cpaelzer, sil2100: I just figured out what happened. Christian's email to ubuntu-release@ on Jan 4 only got delivered to my inbox yesterday. So I thought he didn't know it was approved.
[09:56] <rbasak> Perhaps due to moderation?
[09:56] <rbasak> I thought he didn't know it was approved> i didn't know it was approved either as I hadn't seen the IRC conversation
[09:56] <rbasak> So I thought it was still with sil2100
[10:08] <bdrung_work> the test failure for salt-formula-ceilometer on i386 is a false positive (VirtSubproc.Timeout). The failed test runs for the salt dependencies salt-formula-* should be rerun since i fixed the regressions yesterday with new uploads. where is the correct place to report this?
[10:09] <cpaelzer> rbasak: ok
[10:09] <cpaelzer> rbasak: confusion resolved now at least :-)
[10:09] <cpaelzer> rbasak: I replied to the list again so that it is known there, but that might take another 4 weeks :-)
[10:10] <rbasak> cpaelzer: I seem to have got that one straight away
[10:14] <sil2100> oh
[10:15] <rbasak> Oh. No I didn't.
[10:15] <rbasak> (get it straight away)
[10:15] <rbasak> Anyway.
[10:15] <rbasak> :)
[10:18] -queuebot:#ubuntu-release- New: accepted libgweather [amd64] (bionic-proposed) [3.27.4-1]
[10:18] -queuebot:#ubuntu-release- New: accepted libgweather [armhf] (bionic-proposed) [3.27.4-1]
[10:18] -queuebot:#ubuntu-release- New: accepted libgweather [ppc64el] (bionic-proposed) [3.27.4-1]
[10:18] -queuebot:#ubuntu-release- New: accepted libgweather [arm64] (bionic-proposed) [3.27.4-1]
[10:18] -queuebot:#ubuntu-release- New: accepted libgweather [s390x] (bionic-proposed) [3.27.4-1]
[10:18] -queuebot:#ubuntu-release- New: accepted libgweather [i386] (bionic-proposed) [3.27.4-1]
[10:20] <LocutusOfBorg> jbicha, just to be clear, export V=1 makes gtk-doc fail to build also in Debian :)
[10:20] <LocutusOfBorg> so, the problem is not an Ubuntu only, but probably an even upstream one
[10:21] <LocutusOfBorg> maybe forwarding to upstream developers might help, also having a better error message, to avoid other linux distro having the same issue
[10:24] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (artful-proposed) [2.02~beta3-4ubuntu7.2]
[10:25] <jbicha> is "V=1" a convention?
[10:26] <jbicha> ok, I see it's an automake thing
[10:29] <LocutusOfBorg> jbicha, it is exported by ubuntu buildds, but in any case, I think docbook-xls is evaluating it
[10:29] <LocutusOfBorg> upstream should probably be doing V=0 in testsuite, not Debian or Ubuntu
[10:33] -queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [source] (artful-proposed) [1.85.2]
[10:33] <LocutusOfBorg> jbicha, https://patchwork.kernel.org/patch/7699771/
[10:34] -queuebot:#ubuntu-release- Unapproved: grub2 (artful-proposed/main) [2.02~beta3-4ubuntu7.1 => 2.02~beta3-4ubuntu7.2] (core)
[10:54] <sil2100> rbasak: I see you have commented/discussed on the libzstd SRU - should I leave it on your plate as you have the most context?
[10:57] -queuebot:#ubuntu-release- Unapproved: accepted ceph [source] (artful-proposed) [12.2.2-0ubuntu<IP_ADDRESS>]
[11:00] <rbasak> sil2100: ack. Ah - I see it's in the queue.
[11:04] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (artful-proposed) [2.02~beta3-4ubuntu7.2]
[11:07] -queuebot:#ubuntu-release- Unapproved: grub2 (artful-proposed/main) [2.02~beta3-4ubuntu7.2 => 2.02~beta3-4ubuntu7.2] (core)
[11:09] -queuebot:#ubuntu-release- Unapproved: accepted pulseaudio [source] (artful-proposed) [1:10.0-2ubuntu3.1]
[11:13] -queuebot:#ubuntu-release- Unapproved: rejected pulseaudio [source] (xenial-proposed) [1:8.0-0ubuntu3.8]
[11:13] -queuebot:#ubuntu-release- Unapproved: pulseaudio (xenial-proposed/main) [1:8.0-0ubuntu3.7 => 1:8.0-0ubuntu3.8] (core)
[11:17] -queuebot:#ubuntu-release- Unapproved: rejected linux-firmware [source] (xenial-proposed) [1.157.17]
[11:22] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [source] (xenial-proposed) [0.8.3-0ubuntu2]
[11:23] -queuebot:#ubuntu-release- Unapproved: accepted pulseaudio [source] (xenial-proposed) [1:8.0-0ubuntu3.8]
[11:26] -queuebot:#ubuntu-release- Unapproved: rejected libzstd [source] (xenial-proposed) [1.3.1+dfsg-1~ubuntu<IP_ADDRESS>]
[11:29] <sil2100> smb: hey! I'm looking at your iscsitarget SRU upload for trusty right now
[11:30] <sil2100> smb: I remember it for xenial, but hm, the new upload is for fixing an ADT test - but I don't see any failures for the iscsitarget package that's currently in trusty-proposed - is it only because those ran a long long time ago?
[11:31] <smb> sil2100, yes? That one is a combo. The part I did is only the test, the other part is from what alrady was in proposed
[11:31] <sil2100> smb: does it mean that if the tests were re-run right now without the fix, they would fail?
[11:31] <smb> sil2100, The dep8 failure is racy
[11:31] <smb> So accidentally sometimes did work
[11:31] <sil2100> Ah, ok, guess better to have it than not
[11:31] <sil2100> Thanks
[11:32] -queuebot:#ubuntu-release- Unapproved: accepted libzstd [source] (xenial-proposed) [1.3.1+dfsg-1~ubuntu<IP_ADDRESS>]
[11:32] <smb> sil2100, For detail, when checking for the daemon being running it sometimes took the start script as the running daemon (if system was slow enough)
[11:32] -queuebot:#ubuntu-release- Unapproved: accepted libzstd [source] (artful-proposed) [1.3.1+dfsg-1ubuntu0.1]
[11:32] -queuebot:#ubuntu-release- Unapproved: accepted iscsitarget [source] (trusty-proposed) [<IP_ADDRESS>+svn499-0ubuntu2.5]
[11:40] -queuebot:#ubuntu-release- New binary: libzstd [s390x] (artful-proposed/universe) [1.3.1+dfsg-1ubuntu0.1] (ubuntustudio)
[11:41] -queuebot:#ubuntu-release- New binary: libzstd [ppc64el] (artful-proposed/universe) [1.3.1+dfsg-1ubuntu0.1] (ubuntustudio)
[11:42] <rbasak> ahasenack: ^ that's confusing
[11:42] <rbasak> I wasn't expecting a new binary called libzstd
[11:43] <rbasak> It's not in debian/control
[11:43] <ahasenack> isn't that the source name?
[11:44]  * LocutusOfBorg is ready to land ticket 3141
[11:44] <rbasak> Oh
[11:44] <rbasak> That's the name of the source, not the new binary
[11:44] <ahasenack> I think so
[11:44] <rbasak> https://launchpad.net/ubuntu/+source/libzstd/1.3.1+dfsg-1ubuntu0.1/+build/14353830 has what I expected
[11:44] <ahasenack> cool
[11:45] <rbasak> Never mind. Sorry!
[11:45] <ahasenack> np :)
[11:50] -queuebot:#ubuntu-release- New binary: libzstd [s390x] (xenial-proposed/universe) [1.3.1+dfsg-1~ubuntu<IP_ADDRESS>] (no packageset)
[11:53] -queuebot:#ubuntu-release- New binary: libzstd [arm64] (artful-proposed/universe) [1.3.1+dfsg-1ubuntu0.1] (ubuntustudio)
[11:55] -queuebot:#ubuntu-release- New binary: libzstd [armhf] (artful-proposed/universe) [1.3.1+dfsg-1ubuntu0.1] (ubuntustudio)
[11:56] <LocutusOfBorg> how ofter does britney run on bileto?
[11:56] -queuebot:#ubuntu-release- New binary: libzstd [powerpc] (xenial-proposed/universe) [1.3.1+dfsg-1~ubuntu<IP_ADDRESS>] (no packageset)
[11:57] -queuebot:#ubuntu-release- New binary: libzstd [amd64] (artful-proposed/universe) [1.3.1+dfsg-1ubuntu0.1] (ubuntustudio)
[11:59] -queuebot:#ubuntu-release- New binary: libzstd [i386] (xenial-proposed/universe) [1.3.1+dfsg-1~ubuntu<IP_ADDRESS>] (no packageset)
[12:01] -queuebot:#ubuntu-release- New binary: libzstd [i386] (artful-proposed/universe) [1.3.1+dfsg-1ubuntu0.1] (ubuntustudio)
[12:08] -queuebot:#ubuntu-release- New binary: libzstd [arm64] (xenial-proposed/universe) [1.3.1+dfsg-1~ubuntu<IP_ADDRESS>] (no packageset)
[12:10] -queuebot:#ubuntu-release- New binary: libzstd [amd64] (xenial-proposed/universe) [1.3.1+dfsg-1~ubuntu<IP_ADDRESS>] (no packageset)
[12:11] -queuebot:#ubuntu-release- New binary: libzstd [ppc64el] (xenial-proposed/universe) [1.3.1+dfsg-1~ubuntu<IP_ADDRESS>] (no packageset)
[12:18] -queuebot:#ubuntu-release- New binary: libzstd [armhf] (xenial-proposed/universe) [1.3.1+dfsg-1~ubuntu<IP_ADDRESS>] (no packageset)
[12:56] -queuebot:#ubuntu-release- Unapproved: open-vm-tools (artful-proposed/main) [2:10.1.10-3 => 2:10.1.10-3ubuntu0.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[12:56] -queuebot:#ubuntu-release- Unapproved: open-vm-tools (xenial-proposed/main) [2:10.0.7-3227872-5ubuntu1~16.04.1 => 2:10.0.7-3227872-5ubuntu1~16.04.2] (edubuntu, ubuntu-cloud, ubuntu-server)
[12:57] -queuebot:#ubuntu-release- Unapproved: open-vm-tools (trusty-proposed/main) [2:9.4.0-1280544-5ubuntu6.2 => 2:9.4.0-1280544-5ubuntu6.3] (ubuntu-cloud, ubuntu-server)
[13:31] -queuebot:#ubuntu-release- Unapproved: linux-firmware (xenial-proposed/main) [1.157.16 => 1.157.17] (core, kernel)
[13:56] <LocutusOfBorg> why libunistring from silo didn't end up in binNEW queue?
[13:56] <LocutusOfBorg> is publishing from silo something that avoids the queue? seems strange
[13:57] <jbicha> LocutusOfBorg: yes
[13:58] <LocutusOfBorg> wow, I don't understand the rationale for this but yeah
[14:02] -queuebot:#ubuntu-release- Unapproved: walinuxagent (artful-proposed/main) [2.2.21-0ubuntu1~17.10.1 => 2.2.21+really2.2.20-0ubuntu1~17.10.1] (ubuntu-cloud, ubuntu-server)
[14:02] -queuebot:#ubuntu-release- Unapproved: walinuxagent (xenial-proposed/main) [2.2.21-0ubuntu1~16.04.1 => 2.2.21+really2.2.20-0ubuntu1~16.04.1] (ubuntu-cloud, ubuntu-server)
[14:02] -queuebot:#ubuntu-release- Unapproved: walinuxagent (trusty-proposed/main) [2.2.21-0ubuntu1~14.04.1 => 2.2.21+really2.2.20-0ubuntu1~14.04.1] (ubuntu-cloud, ubuntu-server)
[14:06] <LocutusOfBorg> ack thanks
[14:16] <jbicha> it's a bug
[14:17] <apw> LocutusOfBorg, this is why releasing from biletto is meant to involve an AA doing the new review beforehand if there are any new binaries
[14:49] <superm1> Hi, can an archive admin please help review unapproved today?  fwupdate is blocking fwupd build and migration
[15:27] -queuebot:#ubuntu-release- Unapproved: libsmbios (xenial-backports/universe) [2.3.0-0ubuntu1.1 => 2.4.0-1~ubuntu16.04.1] (no packageset)
[15:42] -queuebot:#ubuntu-release- Unapproved: libsmbios (trusty-backports/universe) [2.2.28-2 => 2.4.0-1~ubuntu14.04.1] (no packageset)
[16:44] <nacc> slangasek: if you have a moment: LP: #1749745
[16:44] <nacc> that's at least one, which is currently blocking php-defaults
[16:48] <slangasek> nacc: how is php-crypt-chap blocking?  it has a FTBFS but only Recommends: php-mcrypt
[16:48] <nacc> slangasek: it build-depends on it
[16:49] <slangasek> a build-depend doesn't block migration
[16:49] <nacc> slangasek: we can't build it with php-defaults for 7.2
[16:49] <nacc> as there is no php-mcrypt
[16:49] <slangasek> and php-crypt-chap is arch: all
[16:49] <slangasek> with no interesting dependencies that would block a transition
[16:49] <nacc> the tests fail at runtime becuase it tries to load mcrypt
[16:49] <nacc> (well, use mcrypt)
[16:49] <slangasek> tests> right, that's the rationale I was looking for
[16:49] <nacc> i don't know why it's a reverse-recommends only , as it seems like a hard dependency :)
[16:50] <slangasek> howso?
[16:50] <nacc> slangasek: as in, the code uses mcrypt explicitly
[16:50] <nacc> afaict
[16:50] <slangasek> it's reasonable for a testsuite to cover things that are optional
[16:50] <slangasek> hmm ok
[16:50] <nacc> slangasek: i didn't dig into it too much
[16:50] <nacc> but afaict, if something is still using mcrypt (per ondrej) it's probably cruft
[16:50] <nacc> even if optionally
[16:51] <slangasek> yes, but that alone is not a rationale for us to remove it in advance of Debia
[16:51] <nacc> slangasek: i guess i should have been clearer: a rebuild of php-crypt-chap will fail eventually (due to missing php-mcrypt) and the tests will always fail with PHP7.2
[16:51] <slangasek> hngh and then I go and remove the wrong package
[16:51] <slangasek> hi please trust me with your archive
[16:52] <nacc> somehow it doesn't change my trust level :)
[16:52]  * slangasek puts php-horde-passwd back
[16:53] -queuebot:#ubuntu-release- New sync: php-horde-passwd (bionic-release/primary) [5.0.7-1]
[16:56] <slangasek> nacc: any idea why serious bugs haven't been filed in Debian for these yet? (ex: yubikey-ksm)
[16:56] <nacc> slangasek: i really don't know. the Debian side of this transition has been ... poor, IMO this time
[16:57] <nacc> slangasek: lots (most) faililng dep8 all over
[16:57] <nacc> some ftbfs
[16:57] <nacc> slangasek: it's possible it's coming, or they will just be removed eventually
[16:57] <nacc> slangasek: oh wait, i know why
[16:57] <nacc> slangasek: debian has 7.1 and 7.2
[16:57] <nacc> and i think 7.1 is the default (so php-mcrypt points there)
[16:58] <slangasek> k
[16:58] <nacc> xnox: have you checked the new php-doctrine-cache works?
[17:03] <xnox> nacc, no! but i have high hopes; since upstream dropped the test suite =)
[17:07] <nacc> xnox: lol
[17:09] -queuebot:#ubuntu-release- Unapproved: debian-installer (xenial-proposed/main) [20101020ubuntu451.19 => 20101020ubuntu451.20] (core)
[18:15] <bdmurray> balloons: So can bug 1744968 be considered verification-done?
[18:16] <balloons> bdmurray, I was wanting cyphermox to chime in as well, so I didn't change the tags
[18:16] <balloons> bdmurray, but I suppose netplan is waiting on juju, and there isn't any reason to hold juju.
[18:18] <balloons> bdmurray, set to verification-done
[18:42] -queuebot:#ubuntu-release- Unapproved: rejected salt [source] (artful-proposed) [2017.7.2+dfsg1-1ubuntu1]
[18:45] -queuebot:#ubuntu-release- Unapproved: accepted open-vm-tools [source] (artful-proposed) [2:10.1.10-3ubuntu0.1]
[18:48] -queuebot:#ubuntu-release- Unapproved: accepted open-vm-tools [source] (xenial-proposed) [2:10.0.7-3227872-5ubuntu1~16.04.2]
[18:49] -queuebot:#ubuntu-release- Unapproved: accepted open-vm-tools [source] (trusty-proposed) [2:9.4.0-1280544-5ubuntu6.3]
[18:54] -queuebot:#ubuntu-release- Unapproved: accepted walinuxagent [source] (artful-proposed) [2.2.21+really2.2.20-0ubuntu1~17.10.1]
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted walinuxagent [source] (xenial-proposed) [2.2.21+really2.2.20-0ubuntu1~16.04.1]
[18:57] -queuebot:#ubuntu-release- Unapproved: accepted walinuxagent [source] (trusty-proposed) [2.2.21+really2.2.20-0ubuntu1~14.04.1]
[19:07] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (xenial-proposed) [20101020ubuntu451.20]
[19:42] <wmww> Is this the place to bring up a package issue in 18.04?
[19:51] <nacc> wmww: #ubuntu+1
[19:51] <nacc> wmww: presuming you mean a bug or so
[19:54] <wmww> nacc: Clang won't install due to dependency issue. I'll report it there.
[19:58] <nacc> slangasek: if you could also look at LP: #1749783 when you get a chance.
[20:03] <nacc> slangasek: also just updated to include the debian bugs fo rhte same
[20:04] <nacc> i'm assuming whoever is doing the debian builds may be bootstrapping them in, which is leading to this mess on our side
[20:34] -queuebot:#ubuntu-release- New binary: gnome-desktop3 [s390x] (bionic-proposed/main) [3.27.90-1ubuntu1] (ubuntu-desktop)
[20:36] -queuebot:#ubuntu-release- New binary: gnome-desktop3 [ppc64el] (bionic-proposed/main) [3.27.90-1ubuntu1] (ubuntu-desktop)
[20:36] -queuebot:#ubuntu-release- New binary: gnome-desktop3 [i386] (bionic-proposed/main) [3.27.90-1ubuntu1] (ubuntu-desktop)
[20:37] -queuebot:#ubuntu-release- New binary: gnome-desktop3 [amd64] (bionic-proposed/main) [3.27.90-1ubuntu1] (ubuntu-desktop)
[20:38] -queuebot:#ubuntu-release- New binary: gnome-desktop3 [arm64] (bionic-proposed/main) [3.27.90-1ubuntu1] (ubuntu-desktop)
[20:38] -queuebot:#ubuntu-release- New binary: gnome-desktop3 [armhf] (bionic-proposed/main) [3.27.90-1ubuntu1] (ubuntu-desktop)
[21:12] -queuebot:#ubuntu-release- Unapproved: rejected gcc-4.8 [sync] (trusty-proposed) [4.8.4-2ubuntu1~14.04.4]
[21:27] -queuebot:#ubuntu-release- Unapproved: gcc-4.8 (trusty-proposed/main) [4.8.4-2ubuntu1~14.04.3 => 4.8.4-2ubuntu1~14.04.4] (core) (sync)
[21:39] -queuebot:#ubuntu-release- Unapproved: accepted gcc-4.8 [sync] (trusty-proposed) [4.8.4-2ubuntu1~14.04.4]
[21:42] <flocculant> infinity: re this  “minimal install” option - how's that going to pan out for flavours? also reminding that we've been trying to get a Xubuntu minimal going for some cycles now
[21:42] <flocculant> bluesabre: ^^
[21:50] <superm1> flocculant, at least from the way it looks like it's been implemented in the PR it's a simple flat file that calls out what you want ripped out of your livefs while installing
[21:51] <flocculant> PR ?
[21:52] <flocculant> sorry - I do QA for us not coding :p
[21:52] <superm1> flocculant, https://code.launchpad.net/~didrocks/ubiquity/minimal-install/+merge/337698 that's the merge request for it
[21:53] <superm1> currently it points to everything in a file /usr/share/ubiquity/manifests/minimal_install_removal
[21:53] <flocculant> superm1: oh right - I have enough trouble getting around bzr and mp - not a clue what PR is :D
[21:53] <superm1> so I would expect the best thing for a flavor to do is dpkg-divert that and provide a list of what they want out
[21:53] <flocculant> superm1: we've been looking at a completely seperate iso to do that
[21:54] <superm1> you should probably discuss with didrocks and xnox specifically on the best way they want to see flavors do it
[21:54] <superm1> but that seems like a plausibly good way to me
[21:54] <flocculant> mmm
[21:56] <infinity> superm1: Eh?  There's nothing to dpkg-divert.  The removal file doesn't come from ubiquity.
[21:57] <superm1> infinity, it will though I thought
[21:57] <superm1> i mean i guess nothing is accepted yet and it can change
[21:57] <infinity> superm1: If the removal file isn't supplied during the image build, that's a massive and glaring bug. :P
[21:57] <infinity> (And I'd push back hard on such a "design")
[21:58] <flocculant> infinity: evening :)
[21:58] <superm1> https://code.launchpad.net/~didrocks/ubiquity/minimal-package-list/+merge/337700
[21:58] <infinity> Gross.
[21:59] <tsimonq2> Oh jeez.
[21:59] <tsimonq2> Please don't tell me that's a hardcoded list...
[22:00] <infinity> It sure is.
[22:02] <flocculant> so glad I'm just qa ...
[22:02] <flocculant> if you can call - asking and being ignored that ;)
[22:04] <infinity> flocculant: Sorry, not maliciously ignoring you, just literally have no answer.
[22:05] <infinity> flocculant: Or, rather "the Canonical Desktop team landing hackish temporary features doesn't really have much impact on flavours".
[22:05] <infinity> (Assuming the claim that they plan to ditch ubiquity entirely comes to fruition)
[22:06] <slangasek> I don't understand that claim
[22:06] <infinity> slangasek: I don't either, but it's right there in the MP. :P
[22:06] <slangasek> yeah
[22:06] <slangasek> I blame xnox
[22:06] <slangasek> (by which I mean, "I summon xnox")
[22:06] <infinity> slangasek: Now, I could dissect the claim as "we intend to use subiquity-style fs-stacking in ubiquity", which isn't the world's worst idea.
[22:07] <flocculant> infinity: ack - never would assume you would do such a thing, if you wanted to - make it obvious :)
[22:07] <infinity> And would neatly reduce the live removal stage of both ubiquity and live-installer to a no-op.
[22:07] <cjwatson> An idea with a decade's pedigree
[22:07] <infinity> cjwatson: Indeed.
[22:07] <cjwatson> Which nobody ever got to work before, but that shouldn't stop people trying :)
[22:08] <infinity> Well, the big problem is booting a functional desktop with stacked livefses.
[22:08] <infinity> Where one was bad enough.
[22:08] <tsimonq2> It doesn't help that OMG! Ubuntu! misinterpreted the commit message that Didier wrote, and since some people decide to pick that apart, the rumor has spread that Desktop is now switching to subiquity.
[22:08] <tsimonq2> FTR.
[22:08] <infinity> But things have matured a lot since the bad old days.
[22:08] <infinity> tsimonq2: Yes, well.  Let's not let the press dictate our plans. :)
[22:08] <tsimonq2> infinity: Stacked squashfses is something interesting.
[22:08] <cjwatson> The big problem back then was unavoidable file overlaps between the livefses (e.g. /var/lib/dpkg/status), but yeah, filesystem technology has moved on.
[22:08] <infinity> Right, and they almost mostly work now.
[22:09] <tsimonq2> infinity: I agree, but in more than one channel this morning people lolwat'ted at that :)
[22:09] <infinity> cjwatson: Well, if you're intentionally stacking linearly, that's not an issue.
[22:09] <tsimonq2> infinity: stacked squashfses> Oh, that's cool. I'd hate to ask for an ETA, but will it land before Feature Freeze?
[22:09] <infinity> cjwatson: ie: base > desktop > desktop-fat > live, then you peel back in inverse order.
[22:09] <cjwatson> Yeah.
[22:10] <infinity> cjwatson: It all goes to hell when people want to use that to define packagesets.
[22:10]  * slangasek nods
[22:10] <cjwatson> desktop-lardons, if you will
[22:10] <cjwatson> (you probably won't)
[22:11] <slangasek> desktop-evoo
[22:13] <infinity> desktop-chubby?
[22:14] <tsimonq2> desktop-apps maybe?
[22:14] <infinity> However, I'm not sure if either the current hack or stacked fses addresses what Xubuntu wanted, which was a smaller image, not just a smaller install footprint.
[22:15] <infinity> If they don't care about image size, then I think stacking is the right answer for everyone to be working on.
[22:15] <infinity> (Or, rather, if the back down on the image size thing, despite caring?)
[22:15] <infinity> s/the/they/
[22:16] <infinity> A single image with two install options is much less hassle to QA as well.
[22:16] <tsimonq2> Talking about image size reminds me to tell you infinity -- I tried removing no-follow-recommends on Lubuntu Next and it pulled in a Plasma desktop... :P so I guess I'll have to play with the recommends more on things, but 18.10 might see us lifting that, finally, for Lubuntu Next. I don't think we care about image size anymore as long as it's not ridiculous.
[22:17] <flocculant> infinity: I can't answer that - though iirc we were looking more at a step between a mini.iso and the current full fat Xubuntu - bluesabre Ukikie are the people who could answer more speciffically
[22:17] <tsimonq2> And Lubuntu Next might use stacking, I think that's a great idea, honestly.
[22:19] <infinity> tsimonq2: Yeah, you might be able to enlist jbicha's help with your recommends issues (if he's up for it, I don't want to volunteer him).  He's very familiar with the tricks we had to pull when ubuntu-desktop and ubuntu-gnome had to somehow magically coexist without pulling each other in.
[22:20] <tsimonq2> infinity: That sounds like that would have been *super* fun. /s
[22:20] <infinity> tsimonq2: It was a bit of a headache making sure unity didn't pull in GNOME and GNOME didn't pull in unity, yes, but it kinda mostly worked most of the time. :P
[22:20] <tsimonq2> :D
[22:22] <tsimonq2> infinity: So, speaking of images as well... Lubuntu Next won't have an Alternate image. We might play with Calamares' netboot functionality but as far as direct d-i goes, we're likely going to be done with that. But we sort of need Lubuntu's Alternate images to work, for one last release, so we can ship them. :P
[22:22] <tsimonq2> infinity: I mean, it would help if it could pull a kernel in :P *ahem*
[22:23] <tsimonq2> (bug 1746807)
[22:24] <tsimonq2> infinity: Something landed between the ISO landing on January 31st and February 1st that broke things, and I can't figure out what.
[22:24] <tsimonq2> (s/landing/spinning up/ on that second occurrence :P)
[22:25] <flocculant> tsimonq2: does that mean that eventually other people won't get asked to test Lubuntu Alternates right at the last minute when you run out of time :D
[22:25] <tsimonq2> flocculant: It will, yes :D
[22:25] <flocculant> ha ha
[22:26] <tsimonq2> hahaha
[22:26]  * flocculant waits ... but is available if necessary till then ;)
[22:26] <tsimonq2> Right, we gotta get the LTS out.
[22:26] <tsimonq2> Then we can cut the cruft.
[22:27] <tsimonq2> (Well, we're already *kinda* doing that, but we aren't touching the LXDE edition except for bugfixes :) )
[22:42] <flocculant> :)
[22:43] <flocculant> what I'm trying to aim for is for us to only sign up to fix 'not diabolical' bugs which get reported on the tracker
[22:44] <flocculant> I can then turn up 4 times a year and say we have no bugs unless I found them :D
[22:45] <flocculant> I find more things in places like qemu than xfce packages
[22:51] <xnox> slangasek, what did you mean by stacked squashfs? you mean like doing overlayfs and packing each layer as squashfs?
[22:52] <xnox> slangasek, or am I out-of-date and squashfs naturally supports stacking somehow?
[23:00] <slangasek> xnox: overlay between multiple squashes
[23:04] <bdmurray> slangasek: Can you set the phased-update-percentage for compiz to 0 see #ubuntu-devel.
[23:04] <bdmurray> ? for good measure
[23:05] <xnox> slangasek, and we have tooling to build those? could be fun.
[23:05] <slangasek> xnox: we effectively already do this for subiquity
[23:05] <slangasek> it's only a two-deep stack
[23:06] <slangasek> bdmurray: source package is compiz? which release?
[23:06] <nacc> slangasek: compiz on xenial
[23:06] <slangasek> nacc, bdmurray: done
[23:06] <nacc> looks to have migrated about 4 hours ago?
[23:07] <xnox> slangasek, ok.
[23:07] <slangasek> xnox: and this is what we were talking about for the maas install options?
[23:08] <nacc> slangasek: thanks
[23:08] <xnox> slangasek, i thought so, yeah
[23:08] <xnox> ?!
[23:08] <slangasek> bdmurray, nacc: what's the follow-through? unity needs rebuilt and pushed?  does it need revalidated?
[23:08] <slangasek> xnox: yes, that's why I'm surprised you didn't know we had tooling :)
[23:08] <nacc> slangasek: i think unity at a minimum needs a rebuild
[23:09] <nacc> it's the only reverse build-depends?
[23:09] <bdmurray> there is a unity in -proposed
[23:09] <xnox> slangasek, i was not involved in the subiquity livecd-rootfs stuff
[23:09] <nacc> so they just need to migrate together, bdmurray ?
[23:09] <slangasek> xnox: ack, I failed to give you context on the current state then
[23:09] -queuebot:#ubuntu-release- New binary: ddnet [s390x] (bionic-proposed/universe) [11.0.3-1] (no packageset)
[23:09] -queuebot:#ubuntu-release- New binary: mbedtls [s390x] (bionic-proposed/universe) [2.7.0-2] (no packageset)
[23:10] <slangasek> bdmurray: I should let you follow it up then?
[23:10] <bdmurray> slangasek: I'm looking into it fwiw
[23:11] <bdmurray> enabling -proposed makes the upgrade not want to remove unity
[23:12] -queuebot:#ubuntu-release- New binary: ddnet [amd64] (bionic-proposed/universe) [11.0.3-1] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: mbedtls [amd64] (bionic-proposed/universe) [2.7.0-2] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: ddnet [i386] (bionic-proposed/universe) [11.0.3-1] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: mbedtls [i386] (bionic-proposed/universe) [2.7.0-2] (no packageset)
[23:13] -queuebot:#ubuntu-release- New: rejected ukui-power-manager [source] (bionic-proposed) [1.1.0-0ubuntu1]
[23:13] -queuebot:#ubuntu-release- New binary: ddnet [armhf] (bionic-proposed/universe) [11.0.3-1] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: ddnet [arm64] (bionic-proposed/universe) [11.0.3-1] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: mbedtls [arm64] (bionic-proposed/universe) [2.7.0-2] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: mbedtls [armhf] (bionic-proposed/universe) [2.7.0-2] (no packageset)
[23:15] <xnox> slangasek, could you please process openssl1.0 through new?
[23:16] -queuebot:#ubuntu-release- New: accepted ddnet [amd64] (bionic-proposed) [10.8.6-3]
[23:16] -queuebot:#ubuntu-release- New: accepted ddnet [ppc64el] (bionic-proposed) [10.8.6-3]
[23:16] -queuebot:#ubuntu-release- New: accepted ddnet [arm64] (bionic-proposed) [11.0.3-1]
[23:16] -queuebot:#ubuntu-release- New: accepted ddnet [i386] (bionic-proposed) [11.0.3-1]
[23:16] -queuebot:#ubuntu-release- New: accepted iraf-rvsao [amd64] (bionic-proposed) [2.8.3-1]
[23:16] -queuebot:#ubuntu-release- New: accepted iraf-rvsao [armhf] (bionic-proposed) [2.8.3-1]
[23:16] -queuebot:#ubuntu-release- New: accepted iraf-rvsao [ppc64el] (bionic-proposed) [2.8.3-1]
[23:16] -queuebot:#ubuntu-release- New: accepted jsonrpc-glib [arm64] (bionic-proposed) [3.27.90-1]
[23:16] -queuebot:#ubuntu-release- New: accepted jsonrpc-glib [i386] (bionic-proposed) [3.27.90-1]
[23:16] -queuebot:#ubuntu-release- New: accepted jsonrpc-glib [s390x] (bionic-proposed) [3.27.90-1]
[23:16] -queuebot:#ubuntu-release- New: accepted ddnet [arm64] (bionic-proposed) [10.8.6-3]
[23:16] -queuebot:#ubuntu-release- New: accepted ddnet [armhf] (bionic-proposed) [11.0.3-1]
[23:16] -queuebot:#ubuntu-release- New: accepted iraf-rvsao [arm64] (bionic-proposed) [2.8.3-1]
[23:16] -queuebot:#ubuntu-release- New: accepted jsonrpc-glib [amd64] (bionic-proposed) [3.27.90-1]
[23:16] -queuebot:#ubuntu-release- New: accepted jsonrpc-glib [ppc64el] (bionic-proposed) [3.27.90-1]
[23:16] -queuebot:#ubuntu-release- New: accepted libgeo-shapelib-perl [amd64] (bionic-proposed) [0.22-2]
[23:16] -queuebot:#ubuntu-release- New: accepted libgeo-shapelib-perl [armhf] (bionic-proposed) [0.22-2]
[23:16] -queuebot:#ubuntu-release- New: accepted libgeo-shapelib-perl [ppc64el] (bionic-proposed) [0.22-2]
[23:16] -queuebot:#ubuntu-release- New: accepted libgpiod [armhf] (bionic-proposed) [1.0-1]
[23:16] -queuebot:#ubuntu-release- New: accepted mbedtls [arm64] (bionic-proposed) [2.7.0-2]
[23:16] -queuebot:#ubuntu-release- New: accepted ddnet [amd64] (bionic-proposed) [11.0.3-1]
[23:16] -queuebot:#ubuntu-release- New: accepted iraf-rvsao [i386] (bionic-proposed) [2.8.3-1]
[23:16] -queuebot:#ubuntu-release- New: accepted libgeo-shapelib-perl [amd64] (bionic-proposed) [0.22-1]
[23:16] -queuebot:#ubuntu-release- New: accepted libgeo-shapelib-perl [i386] (bionic-proposed) [0.22-2]
[23:16] -queuebot:#ubuntu-release- New: accepted mbedtls [amd64] (bionic-proposed) [2.7.0-2]
[23:16] -queuebot:#ubuntu-release- New: accepted mbedtls [s390x] (bionic-proposed) [2.7.0-2]
[23:16] -queuebot:#ubuntu-release- New: accepted python3-precis-i18n [amd64] (bionic-proposed) [1.0.0-1]
[23:16] -queuebot:#ubuntu-release- New: accepted ddnet [s390x] (bionic-proposed) [11.0.3-1]
[23:16] -queuebot:#ubuntu-release- New: accepted libgeo-shapelib-perl [arm64] (bionic-proposed) [0.22-2]
[23:16] -queuebot:#ubuntu-release- New: accepted mbedtls [i386] (bionic-proposed) [2.7.0-2]
[23:16] -queuebot:#ubuntu-release- New: accepted texhyphj [amd64] (bionic-proposed) [1.2+dfsg-1]
[23:16] -queuebot:#ubuntu-release- New: accepted jsonrpc-glib [armhf] (bionic-proposed) [3.27.90-1]
[23:16] -queuebot:#ubuntu-release- New: accepted minidb [amd64] (bionic-proposed) [2.0.2-1]
[23:16] -queuebot:#ubuntu-release- New: accepted libgeo-shapelib-perl [s390x] (bionic-proposed) [0.22-2]
[23:16] -queuebot:#ubuntu-release- New: accepted ddnet [s390x] (bionic-proposed) [10.8.6-3]
[23:16] -queuebot:#ubuntu-release- New: accepted libgpiod [arm64] (bionic-proposed) [1.0-1]
[23:16] -queuebot:#ubuntu-release- New: accepted libgpiod [ppc64el] (bionic-proposed) [1.0-1]
[23:16] -queuebot:#ubuntu-release- New: accepted libgpiod [amd64] (bionic-proposed) [1.0-1]
[23:16] -queuebot:#ubuntu-release- New: accepted libgpiod [s390x] (bionic-proposed) [1.0-1]
[23:16] -queuebot:#ubuntu-release- New: accepted libgpiod [i386] (bionic-proposed) [1.0-1]
[23:18] <bdmurray> slangasek: Yes, we just need the version of unity from -proposed
[23:19] <slangasek> xnox: rationale for an openssl1.0 binary package that doesn't seem to exist in Debian?
[23:19] <xnox> slangasek, security team must have openssl1.0 binary for SRU and security regression to support openssl1.0 in main
[23:20] <xnox> slangasek, there is an LP bug linked....
[23:20] <xnox> slangasek, hence i shipped them, non-coflicting, in /usr/lib/ssl1.0/ which should be good enough for security team.
[23:20] <slangasek> xnox: got it, thanks
[23:21] <slangasek> xnox: and I assume there's no requirement to seed this binary package into main
[23:22] -queuebot:#ubuntu-release- New: accepted openssl1.0 [amd64] (bionic-proposed) [1.0.2n-1ubuntu3]
[23:22] -queuebot:#ubuntu-release- New: accepted openssl1.0 [armhf] (bionic-proposed) [1.0.2n-1ubuntu3]
[23:22] -queuebot:#ubuntu-release- New: accepted openssl1.0 [ppc64el] (bionic-proposed) [1.0.2n-1ubuntu3]
[23:22] -queuebot:#ubuntu-release- New: accepted openssl1.0 [arm64] (bionic-proposed) [1.0.2n-1ubuntu3]
[23:22] -queuebot:#ubuntu-release- New: accepted openssl1.0 [s390x] (bionic-proposed) [1.0.2n-1ubuntu3]
[23:22] -queuebot:#ubuntu-release- New: accepted openssl1.0 [i386] (bionic-proposed) [1.0.2n-1ubuntu3]
[23:26] <xnox> slangasek, don't think so.
[23:40] <bdmurray> slangasek: What else needs to happen with the compiz / unity xenial issue?
[23:41] <bdmurray> unity has two unverified bugs
[23:44] <slangasek> bdmurray: under the circumstances, with 20 verified bugs, 2 unverified bugs, and a critical regression, I was inclined to release without verification of the last 2
[23:45] <bdmurray> slangasek: we could test for a regression in bug 1666359 using what is given
[23:47] <slangasek> bdmurray: could; but I think it's better to release the current package now and not block on further verifications
[23:47] <bdmurray> slangasek: okay


[16:00] -SwissBot:#ubuntu-news- ::Planet:: Julian Andres Klode: Ubuntu 2022v1 secure boot key rotation and friends @ https://blog.jak-linux.org/2023/02/01/ubuntu-key-rotation/
[16:00] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: Multipass 1.11 brings enhanced performance for Linux on Mac and Windows @ https://ubuntu.com//blog/multipass-1-11-brings-enhanced-performance-for-ubuntu-on-mac-and-windows


[07:32] <mojonixon> we'll I can duplicate it....  Looks like the install is complete but aptitude is zombied.
[07:32] <mojonixon> If I kill it's parent process, the install completes w/o problems....
[08:26] <tepsipakki> mojonixon: I've seen that too
[08:27] <tepsipakki> but only on certain machines (which are identical to others)
[08:27] <tepsipakki> I haven't seen it with edgy/feisty
[09:12] <mojonixon> I can duplicate the problem on a vmware machine on physical hardware under dapper.
[09:23] <tepsipakki> mojonixon: what package makes it hang?
[03:29] <cjwatson> evand: ok, there's a daily alternate build of gutsy up now
[03:29] <cjwatson> evand: kernel installation will break though - see the linux-meta upload I just did, which should unbreak that
[03:30] <evand> ok, thanks
[03:30] <cjwatson> oh, meh, udeb seeds are busted too
[03:30] <cjwatson> excuse me while I fix up a load of stuff
[03:30] <cjwatson> :-)
[03:30] <cjwatson> evand: do you have a seed checkout? (http://wiki.ubuntu.com/SeedManagement)
[03:31] <evand> haha
[03:31] <cjwatson> we need to update the Kernel-Version bits in the installer seed each time d-i is uploaded for a new kernel version
[03:31] <cjwatson> kernel ABI, rather
[03:31] <evand> negative, I'll take care of that now
[03:31] <cjwatson> you'll be able to write to it once you're in ubuntu-core-dev
[03:32] <evand> ok
[03:39] <cjwatson> ok, seeds are happy, linux-meta will take two publisher cycles
[03:47] <evand> cjwatson: link to the linux-meta upload? I'm having a hard time finding it.
[03:49] <cjwatson> evand: only just uploaded, so may not be visible yet
[03:50] <evand> ah, gotcha
[03:50] <cjwatson> evand: https://lists.ubuntu.com/archives/gutsy-changes/2007-May/002430.html
[03:51] <evand> thanks
[03:59] <evand> is the d-i daily build process documented anywhere?
[04:06] <evand> cjwatson: also, what was wrong with the udeb seeds?  Sorry if I'm being overly inquisitive
[04:08] <cjwatson> evand: build process> the place to start there is probably by checking out http://people.ubuntu.com/~cjwatson/bzr/cdimage/mainline/ and also each of the pieces in configs/devel once you've checked that out
[04:08] <cjwatson> there's a README in there with some information, and then RTFS :)
[04:08] <cjwatson> inquisitive> you cannot be overly inquisitive ;-)
[04:08] <cjwatson> udeb seeds> the Kernel-Version was set to 2.6.20-15, so feisty's kernel udebs were still being pulled in
[04:08] <evand> wonderful
[04:08] <cjwatson> onto the CD
[04:09] <evand> oh ok, that's where I got confused
[04:10] <mojonixon> aptitude hangs (zombie) after installing all packages...
[04:13] <mojonixon> sorry  that las message was a reply to one from about 7hrs ago...
[04:14] <tepsipakki> mojonixon: but the log should tell you which one it was installing (alt+F4)
[04:15] <mojonixon> actually the last package installed was openssh-server, but it is fully installed.
[04:17] <tepsipakki> ok, here it always hung when installing some package, and it was always the same package for that machine
[04:17] <cjwatson> yeah, it was right at the end of the process
[04:17] <cjwatson> somebody needs to strace it to figure out what's failing to reap it
[04:17] <cjwatson> probably strace -f -s 1024 the whole pkgsel process, dumping to a file on disk as it'll be a lot of output
[04:17] <tepsipakki> at least the counter fell behind every time
[04:17] <mojonixon> If I change the package list it still failes.
[04:21] <mojonixon> If you'll give me a clue as how to strace the pkgsel process, I'll do it and send the results.
[04:22] <mojonixon> I can get the machine back to that stage of the install fairly quickly...
[04:22] <cjwatson> one sec
[04:28] <cjwatson> mojonixon: so, you're going to have to be fairly quick, although not superman-speed
[04:28] <mojonixon> np....  I've got the command lines of the process tree leading up to the failure if that helps.
[04:29] <cjwatson> mojonixon: run through the install until the "Installing the base system" step starts
[04:29] <cjwatson> mojonixon: as soon as that starts, switch to tty2 and look through 'ps x' for the main-menu process, and get its process id
[04:29] <cjwatson> then 'strace -f -s 1024 -o /target/tmp/main-menu.trace -p PID' where PID is that process id
[04:30] <cjwatson> the next two things main-menu does after that point are apt-setup and pkgsel, so if you leave that running until the failure you should have an adequate trace
[04:30] <cjwatson> it is of course possible that it will go away under strace :-/
[04:31] <mojonixon> ok...  I'll add debconf/priority select low to the preseed and try  it...
[04:31] <mojonixon> Of course it will go away under trace :)
[04:33] <cjwatson> no, please don't use expert mode
[04:33] <cjwatson> I'm not sure what other subtle things that might affect
[04:34] <mojonixon> the failure happens the same either way.....
[04:34] <cjwatson> ok
[04:34] <cjwatson> in that case that would give you a better window, yes
[04:34] <cjwatson> you could just start the strace right before selecting "Select and install software"
[04:36] <mojonixon> ok...
[04:43] <mojonixon> ok, I gotta zombie...
[04:43] <mojonixon> I also got a [tcb table full]  message from strace.
[04:45] <mojonixon> ok, I  got 2.9MB of trace, where do you want it?
[04:48] <mojonixon> you should be able to get the trace here.... http://www.vircio.com/main-menu.trace.bz2
[04:50] <cjwatson> thanks, grabbing
[04:50] <mojonixon> please let me know what you're looking for so that I can follow along....
[04:52] <cjwatson> that's odd, I don't think that's complete
[04:52] <cjwatson> there's no mention of aptitude in there
[04:53] <cjwatson> well, no non-trivial mention
[04:54] <mojonixon> ok, I can try it again....
[04:56] <mojonixon> this is the command I used to generate the trace:
[04:56] <mojonixon> where 2051 is the pid of /usr/bin/main-menu
[05:03] <mojonixon> Actually aptitude is mentioned under process 2544
[05:04] <cjwatson> yes, but not relevantly
[05:04] <cjwatson> I'm looking for an execve of aptitudde
[05:04] <cjwatson> aptitude
[05:04] <mojonixon> ko...
[05:04] <cjwatson> as in, the process actually running
[05:05] <cjwatson> the tcb thing is very weird, and possibly an strace bug, which is less than convenient
[05:05] <cjwatson> try -f -F ?
[05:05] <cjwatson> (without the ?)
[05:06] <mojonixon> ok...  will do give me a sec.
[05:14] <mojonixon> of course it didn't fail this time....  I'll do it again....
[05:19] <mojonixon> I got a 329MB trace file though :)
[05:22] <cjwatson> sounds better
[05:22] <cjwatson> but yeah, would need it to fail
[05:23] <mojonixon> of course
[05:35] <mojonixon> interesting....  did a snapshot of the machine at the "Select and install software point"
[05:36] <mojonixon> Then, I continued on without strace and the install hung.
[05:36] <mojonixon> Now, I'm running strace -F f and the install works....  dohh...
[05:39] <mojonixon> Then, I reverted the machine to the snapshot and tried again w/o strace and it hangs.
[05:41] <cjwatson> annoying
[05:43] <mojonixon> If I use strace -F (without -f) it hangs but of course the trace is useless.
[05:55] <mojonixon> ok any suggestions, I cannot get it to fail with strace -F -f
[06:25] <mojonixon> how do I install the strace udeb?  I've got the following in my preseed.cfg but it doesn't work
[06:26] <mojonixon> d-i anna/choose_modules multiselect openssh-client-udeb, strace-udeb
[06:31] <blackskad> cjwatson: can I safely reject bug 68298 ?
[06:31] <blackskad> cjwatson: the initial reporter can't reproduce it anymore
[06:31] <blackskad> cjwatson: but bdmurray said you might be able to do something with the logs that are already attached
[06:44] <evand> cjwatson: any chance of getting another cd out today since linux-meta finished building?
[06:51] <cjwatson> mojonixon: you could run 'anna-install strace-udeb' on tty2
[06:51] <cjwatson> it was in universe in dapper, though
[06:51] <cjwatson> what I always used to do was 'udpkg -i /cdrom/pool/main/s/strace/strace_*.deb'
[06:51] <cjwatson> (which is horrible, but works)
[06:52] <cjwatson> blackskad: yeah, it was really a kernel bug but we already got a slew of bugs crashing in zlib_inflate and I think we fixed that
[06:53] <cjwatson> it's probably dependent on CD read errors, hence the poor reproducibility
[06:53] <cjwatson> feel free to reject that one
[06:53] <blackskad> cjwatson: ok, thanks :)
[06:53] <cjwatson> evand: sure, one moment
[06:53] <evand> thanks
[06:53] <cjwatson> I was busy doing interviews
[06:54] <cjwatson> hmm, linux-meta doesn't seem to have been accepted on all architectures
[06:54] <mojonixon> got it... thx.
[06:54] <evand> whoops
[06:56] <cjwatson> evand: never mind, my mistake, it's there
[06:56] <cjwatson> CDs building
[06:56] <evand> great
[07:09] <evand> hrm, what exactly is the standard procedure for translated strings conflicts in merges?
[07:10] <cjwatson> run in circles, scream and shout
[07:10] <cjwatson> the Ubuntu changes are typically Ubuntu branding of some sort
[07:10] <cjwatson> so s/Debian/Ubuntu/ - normally, I take the new Debian side and re-brand it
[07:11] <cjwatson> unfortunately some languages transliterate, decline, or otherwise mangle the word "Debian"
[07:11] <cjwatson> https://wiki.ubuntu.com/DistributionDefaultsAndBranding records (down at the end) some of the lore I've picked up about this
[07:11] <evand> haha
[07:12] <evand> thanks
[07:12] <cjwatson> after a bzr merge conflict, .OTHER is the Debian side
[07:13] <cjwatson> if you use vim, I have some vim macros to help
[07:13] <cjwatson> map ,u RUbuntu<Esc>
[07:13] <cjwatson> map ,z :let savelast=@/<CR>j?^msgid<CR>:let @/=savelast<CR>O#, fuzzy<Esc>
[07:13] <cjwatson> ,u just replaces the next six characters with Ubuntu (a surprising time-saver), while ,z marks the current string as fuzzy in case you don't know how to deal with the branding (that's the case for a lot of Arabic and Indic languages)
[07:14] <evand> nice!
[07:14] <evand> any particular reason why you don't maintain (or haven't published) kbd-chooser in bzr?
[07:15] <cjwatson> it's obsoleted by console-setup, so I just haven't bothered to import it
[07:15] <cjwatson> I basically just ignore it :)
[07:16] <evand> heh
[07:17] <cjwatson> one of these days I will either do something with the merge or remove the package entirely, but it's not worth much attentioon
[07:17] <cjwatson> -o
[07:18] <cjwatson> evand: new alternate dailies built
[07:18] <evand> great!
[08:13] <evand> heh, I probably should've read this first: http://cdimages.ubuntu.com/daily/20070530.2/report.html
[09:20] <cjwatson> actually neither of those should be a serious problem
[09:20] <cjwatson> (also, cdimages.u.c is deprecated, cdimage. is preferred)
[09:20] <cjwatson> -amd64-generic is a transitional metapackage, and gnome-orca is optional
[09:23] <evand> ah, I'll remember that for future reference.  It dies on gnome-orca.
[09:27] <evand> To clarify: gnome-orca depends on libgnome-speech3 but is not installable -> broken packages -> aptitude failed (100)
[10:52] <cjwatson> evand: mm, odd that it's being installed unless you asked for accessibility though
[10:55] <evand> I don't believe I did
[11:04] <evand> hrmm, it might be working this time around.  Odd.
[11:04] <evand> I stand corrected
[11:05] <evand> same problem
[11:05] <cjwatson> clearly gnome-orca ought to be fixed either way
[11:06] <cjwatson> evand: does the newt interface seem unusually laggy to you?
[11:06] <cjwatson> I'm wondering whether it's just this vmware run
[11:06] <evand> no, quite quick actually
[11:06] <cjwatson> odd
[11:06] <cjwatson> it seems to lag in responding to keystrokes
[11:06] <cjwatson> relative to feisty, I mean
[11:07] <cjwatson> oh, gnome-orca is a recommends of desktop
[11:07] <cjwatson> my bad
[11:08] <evand> I blame vmware
[11:08] <evand> about the lag, not the dependencies
[11:09] <cjwatson> gnome-orca has weird hardcoded dependency lines
[11:10] <cjwatson> I'm going to run away from this and ask dholbach about it next time I see him
[11:10] <evand> haha, ok
[11:10] <evand> had a chance to look over that email?
[11:20] <cjwatson> evand: mailed you back now
[11:23] <evand> thanks!


[08:02] <diplo> Still being built :( - first forgot a cpu cooler, then found out with Ryzen machines you can't use onboard gfx - so last delivery today hopefully and it'll be alive!
[08:20] <brobostigon> morning boys and girls.
[11:51] <daftykins> wowzer, just had my new phone line done - my router now syncs at 61Mb for my 60Mb service (instead of 52 to 58 tops before) and my download speed has gone from 6.3MB/sec to 6.9 :D
[12:11] <diddledan> daftykins: might want to get them to reset the exchange training thing to get your line to retrain itself to the new conditions rather than waiting an age for it to stabilise (resetting the training means it will profile more aggressively IIRC)
[12:12] <daftykins> nah it was a whole new copper run from end to end, i'm probably in a totally different linecard now
[12:12] <diddledan> gotcha
[12:12] <daftykins> it's been instantly as good as it's gonna get \o/
[12:12] <diddledan> \o/
[12:12] <daftykins> well, might still creep up i suppose once it settles :>
[12:12] <daftykins> engineer pulled the power cable out of my server, hah
[12:13] <diddledan> "how can one insulated wire bring so much happiness?!"
 Good news everybody: https://www.windowscentral.com/microsoft-edge-beta-ios-picks-ipad-support
[15:59] <diddledan> another Ruskie dead?! http://www.bbc.co.uk/news/uk-43433552


[00:40] <jphilips> our docs mention installing the xubuntu-restricted-extras package, but we don't have such a package in 20.04, though it is there in 18.04
[00:40] <jphilips> bluesabre: ^^^
[00:40] <jphilips> Unit193: ^^^
[00:41] <Unit193> s/x//
[00:58] <jphilips> yes i saw the ubuntu-restricted-extras and kubuntu and lubuntu still have their restricted-extras, but was wondering why the xubuntu package was removed
[01:03] <Unit193> https://launchpad.net/ubuntu/+source/ubuntu-restricted-extras/66 - https://launchpad.net/ubuntu/+source/ubuntu-restricted-addons/24 the Lubuntu one is transitional too.
[01:03] <Unit193> !info lubuntu-restricted-extras
[01:05] <Unit193> There's no difference, why update the same thing in 3+ pleaces when you can do it once?  Means things don't get forgotten/neglected.
[01:13] <jphilips> so will the xubuntu-restricted-addons package also be removed, as its also just pointing to the ubuntu one?
[01:46] <jphilips> bluesabre: i think i found the reason for that catfish but i mentioned to you before https://gitlab.xfce.org/apps/catfish/-/issues/31
[10:40] <bluesabre> jphilips: please add any findings to the bug report :)
[10:43] <Unit193> G'day.
[10:48] <bluesabre> Hey there Unit193
[10:48] <bluesabre> How's it going?
[10:48] <Unit193> Can't sleep.
[10:57] <bluesabre> :(
[15:21] <jphilips> bluesabre: not sure what you mean by findings
[15:23] <bluesabre> jphilips: you said you think you found the reason for the catfish bug, add that info to the bug report :)
[15:26] <jphilips> bluesabre: the reason is in the bug report. :D
[15:27] <jphilips> search a path and if another path has the same base path in it, it shows results from that path as well
[17:00] <bluesabre> oh, that wasn't clear from just looking at the description
[17:00] <bluesabre> Added that note to the bug report
[18:01] <jphilips> oh okay. thought the description was clear enough :D
[18:01] <jphilips> bluesabre: reminder to send out for voting on telegram
[18:44] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: Apply translations in pt_BR @ https://github.com/Xubuntu/xubuntu-default-settings/commit/a7f93acb778289db1c6cb62919087a692df6dd64 (by transifex-integration)
[18:44] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: Translate /usr/bin/po/thunar-print.pot in pt_BR @ https://github.com/Xubuntu/xubuntu-default-settings/commit/e5a26d7ece352dbe2f3549e0a9ccfcbfc3896e94 (by transifex-integration)
[18:44] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: Apply translations in pt_BR @ https://github.com/Xubuntu/xubuntu-default-settings/commit/d19172d99b1e0333c47d845b34e6b811b03c3e55 (by transifex-integration)
[22:39] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: libxfce4ui 4.15.3 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-libxfce4ui-4-15-3-released-tp59213.html (by Simon Steinbeiss)


[02:44] <deef> hello folks, is there any workaround to make touch take a bluetooth keyb and mouse both at the same time?
[04:45] <tastybuds> Hello! Can I ask what is the freedom status of the Ubuntu phone products that are currently available on the market, concerning software and hardware?
[05:50] <deef> hello, anyone experienced bluetooth devices appearing and dissapearing directly when searching? They worked yesterday, ... :-(
[06:04] <duflu> mvo: Saw your name in the credits at the end of http://timescapes.org/ ... coincidence?
[06:48] <wolfmoon> !ubuntu
[06:48] <wolfmoon> !xubuntu
[06:49] <wolfmoon> !Xfce
[06:49] <wolfmoon> !Arch
[06:49] <wolfmoon> !archlinux
[06:49] <wolfmoon> !Linux
[07:22] <mvo> duflu: yes, movie looks awesome
[07:22] <mvo> duflu: but unfortunately I was not involved
[07:22] <duflu> Fair enough
[07:58] <jamesh> mardy: hi.  We discovered a memory leak in online-accounts-api today: https://bugs.launchpad.net/online-accounts-api/+bug/1617180
[07:59] <jamesh> mardy: it's a weird one: the code doesn't look obviously wrong, and the leaked memory should all be managed within Qt itself
[08:00] <jamesh> I haven't done enough investigation yet to blame Qt though
[08:26] <kaisoz> hi
[08:37] <davmor2> kaisoz: hello
[09:23] <gb_mks> I´m having a error with ubuntu-sdk-ide related with click-review package, is this the right place to ask?
[09:28] <matv1> gb_mks i would probably also try channel #ubuntu-app-devel
[09:28] <gb_mks> matv1: thanks :D
[09:28] <matv1> np!
[10:47] <Tahvok> Hey guys!
[10:47] <Tahvok> First time trying ubuntu touch on my oneplus one
[10:48] <Tahvok> Has anyone been successfull with making to partition writable?
[11:13] <popey> Tahvok: sure, but what's the goal? We generally discourage making the partition read/write because that can break future updates
[11:14]  * ogra_ looks forward to snappy based phones :)
[11:15] <ogra_> there wont be any more "making writabble" then ;)
[11:15] <ogra_> *writable
[11:25] <popey> no, there will be other new and interesting discussions to have
[14:53] <kaisoz> hi there :)
[14:59] <mimecar> evening kaisoz
[16:11] <mcphail_quassel> Has anyone got the quassel client in the store to work? It doesn't seem to send text for me
[16:18] <davmor2> mcphail_quassel: and yet we see text here how odd ;)
[16:18] <davmor2> mcphail_quassel: did you read the description?
[16:19] <mcphail_quassel> davmor2: I'm currently running my own server on the phone, but typing from a client on my desktop. I just get "no text to send" if I use the store client
[16:20] <mcphail_quassel> davmor2: I can join and part from the store client, but not send text
[16:21] <davmor2> mcphail_quassel: hmmm no idea then I know it gave a bunch of warnings in the description hence asking if you'd read the description but that seems to of been updated since I last looked at it
[16:22] <mcphail_quassel> davmor2: hmm. Perhaps the warnings were justified ;)
[17:17] <grasstype> alright, I'm now slightyl more in love with the terminal
[17:17] <grasstype> anyone know what happened to xchat for ubuntu touch btw? it dissappeared off my tablet
[17:18] <grasstype> went to re-install, assuming I deleted it or something, and didn't see it in the store
[17:23] <SebthreeBQM10HD> hi
[17:23] <grasstype> hi
[17:23] <SebthreeBQM10HD> grasstype, hi
[17:24] <grasstype> what are you up to SebthreeBQM10HD
[17:25] <SebthreeBQM10HD> grasstype, not much was trying to find suitable Creative Commons background music for my event,  I guess a bit better luck this time
[17:25] <grasstype> ooo, that sounds fun
[17:25] <SebthreeBQM10HD> also I got a intersting issue with Ubuntu touch to report I guess
[17:25] <SebthreeBQM10HD> well probably not really Ubuntu touches fault but yeah
[17:25] <grasstype> what issue?
[17:25] <SebthreeBQM10HD> grasstype, in fact you could try to see if you get the sme error page about the  browser not beig supported like i got like two days ago
[17:26] <SebthreeBQM10HD> grasstype, can you browse ebay in the native default browser? didn't work for me on th uk versibion got  a page about browsr not being supported instead
[17:26] <SebthreeBQM10HD> grasstype, browser as in search for something and have the results come up
[17:27] <grasstype> hmm... seems to be working for me
[17:27] <SebthreeBQM10HD> which version ?
[17:27] <SebthreeBQM10HD> well it was tow days go
[17:27] <SebthreeBQM10HD> ago
[17:27] <SebthreeBQM10HD> I haven't treid again ye
[17:27] <SebthreeBQM10HD> might work now
[17:27] <dobey> grasstype: xchat? it never was in the store afaik. you'd need to install it in libertine if you want to use that. chatter would be an irc client in the phone app store though
[17:28] <grasstype> Maybe ebay changed? there hasn't been any updates I know of
[17:28] <grasstype> dobey: I don't THINK I installed with apt-get...
[17:28] <grasstype> anyways, I tried and didn't like chatter, so I'm actually using weechat in the terminal in a chroot
[17:29] <SebthreeBQM10HD> still gottting the eror page
[17:29] <SebthreeBQM10HD> dobey,  seaching http://ebay.co.uk for tizen not working
[17:29] <SebthreeBQM10HD> geiting   a browser unsupported pge now
[17:29] <SebthreeBQM10HD> in the default broser
[17:29] <dobey> i don't know about that
[17:30] <SebthreeBQM10HD> yeah, but tht's oe of those things that hmm
[17:30] <dobey> there's a thread on the mailing list about ebay
[17:30] <SebthreeBQM10HD> popey, you getting that to, if you try ?
[17:30] <SebthreeBQM10HD> dobey, oh is there
[17:30] <SebthreeBQM10HD> got  link altough linksdon't work like this chat, xchta gnome libertine
[17:30] <dobey> probably ebay changed the supported browsers in their user-agent check, and our browser got knocked out as a result
[17:30] <SebthreeBQM10HD> dobey, yep exactly bingo
[17:30] <SebthreeBQM10HD> tht's what I thought basically before to or whtaever
[17:30] <SebthreeBQM10HD> the libertine Firefox still works
[17:32] <leaftype> bah, bluetooth keyboard seems to still stop working on window switch sometimes
[17:32] <leaftype> oh well, now in chatter
[17:33] <leaftype> yeah, I think the ebay think might be specific to the uk version
[17:36] <SebthreeBQM10HD> leaftype, what are you trying to do?
[17:36] <leaftype> SebthreeBQM10HD, nothing in particular right now. I've been playing around a LOT in a chroot though
[17:37] <leaftype> my biggest problem is learning c++, I'm trying to see if there is a better way to limit frame rate in ncurses than checking to see if a second has passed yet
[17:37] <SebthreeBQM10HD> leaftype, I thought your thing was t o do with irc maybe ?
[17:38] <leaftype> oh, that was just an aside since I don't have xchat anymore. alt-tabbing and alt-tabbing back in for some reason occasionally disables the keyboard
[17:38] <leaftype> it did it in xchat, and it does it in the terminal sometimes
[17:39] <leaftype> It might be a bug with chroots in the terminal or just the terminal itself, or who the hell knows what else
[17:40] <leaftype> hah, it did it in the terminal again
[17:40] <leaftype> closing and restarting it solves the problem though, for whatever that is worth
[18:59] <Tahvok> What could be the reason clicking on install on any app inside the store to do nothing?
[19:03] <dobey> Tahvok: what do you mean exactly by "do nothing" ?
[19:07] <Tahvok> I guess it started working now..
[19:07] <Tahvok> I meant that the button was like not working at all
[19:07] <Tahvok> Anyway, I have some other problem. I can't unlock the phone. It blinks with the screen for a second, and then goes locked again and turns of the screen
[19:09] <Tahvok> Also, I can't seem to open the browser. It opens for a seconds, and turns off again
[19:18] <kaisoz> hi!