[00:03] -queuebot:#ubuntu-release- New binary: libzbd [riscv64] (jammy-proposed/universe) [2.0.2-1] (no packageset)
[00:06] -queuebot:#ubuntu-release- New binary: gh [riscv64] (jammy-proposed/universe) [2.4.0+dfsg1-1] (no packageset)
[00:07] -queuebot:#ubuntu-release- New binary: msc-generator [arm64] (jammy-proposed/universe) [7.1-1] (no packageset)
[00:07] -queuebot:#ubuntu-release- New binary: msc-generator [armhf] (jammy-proposed/universe) [7.1-1] (no packageset)
[00:26] <xnox> https://code.launchpad.net/~xnox/ubuntu-archive-tools/+git/ubuntu-archive-tools/+merge/414355 needs review and merge
[00:32] -queuebot:#ubuntu-release- New: accepted libtree [amd64] (jammy-proposed) [3.0.2-1]
[00:32] -queuebot:#ubuntu-release- New: accepted libtree [armhf] (jammy-proposed) [3.0.2-1]
[00:32] -queuebot:#ubuntu-release- New: accepted libtree [riscv64] (jammy-proposed) [3.0.2-1]
[00:32] -queuebot:#ubuntu-release- New: accepted libzbd [amd64] (jammy-proposed) [2.0.2-1]
[00:32] -queuebot:#ubuntu-release- New: accepted libzbd [armhf] (jammy-proposed) [2.0.2-1]
[00:32] -queuebot:#ubuntu-release- New: accepted libzbd [riscv64] (jammy-proposed) [2.0.2-1]
[00:32] -queuebot:#ubuntu-release- New: accepted mdnsd [amd64] (jammy-proposed) [0.11-2]
[00:32] -queuebot:#ubuntu-release- New: accepted mdnsd [armhf] (jammy-proposed) [0.11-2]
[00:32] -queuebot:#ubuntu-release- New: accepted mdnsd [riscv64] (jammy-proposed) [0.11-2]
[00:32] -queuebot:#ubuntu-release- New binary: ace [amd64] (jammy-proposed/universe) [7.0.6+dfsg-2] (no packageset)
[00:32] -queuebot:#ubuntu-release- New: accepted libtree [arm64] (jammy-proposed) [3.0.2-1]
[00:32] -queuebot:#ubuntu-release- New: accepted libtree [s390x] (jammy-proposed) [3.0.2-1]
[00:32] -queuebot:#ubuntu-release- New: accepted libzbd [ppc64el] (jammy-proposed) [2.0.2-1]
[00:32] -queuebot:#ubuntu-release- New: accepted mdnsd [arm64] (jammy-proposed) [0.11-2]
[00:32] -queuebot:#ubuntu-release- New: accepted mdnsd [s390x] (jammy-proposed) [0.11-2]
[00:32] -queuebot:#ubuntu-release- New binary: ace [s390x] (jammy-proposed/universe) [7.0.6+dfsg-2] (no packageset)
[00:32] <xnox> https://code.launchpad.net/~xnox/ubuntu-archive-tools/+git/ubuntu-archive-tools/+merge/415638 fixing kernel-sru-review which imho looks broken right now
[00:32] -queuebot:#ubuntu-release- New source: gjots2 (jammy-proposed/primary) [3.1.9-0ubuntu1]
[00:32] -queuebot:#ubuntu-release- New binary: obs-transition-table [amd64] (jammy-proposed/universe) [0.2.1-2] (no packageset)
[00:32] -queuebot:#ubuntu-release- New binary: rocm-cmake [amd64] (jammy-proposed/universe) [5.0.0-1] (no packageset)
[00:32] -queuebot:#ubuntu-release- New: accepted libtree [ppc64el] (jammy-proposed) [3.0.2-1]
[00:32] -queuebot:#ubuntu-release- New: accepted libzbd [s390x] (jammy-proposed) [2.0.2-1]
[00:32] -queuebot:#ubuntu-release- New binary: ace [ppc64el] (jammy-proposed/universe) [7.0.6+dfsg-2] (no packageset)
[00:32] -queuebot:#ubuntu-release- New source: libzdnn (jammy-proposed/primary) [0.4.0-0ubuntu1]
[00:32] -queuebot:#ubuntu-release- New: accepted libzbd [arm64] (jammy-proposed) [2.0.2-1]
[00:32] -queuebot:#ubuntu-release- New source: bismuth (jammy-proposed/primary) [2.3.0-0ubuntu1]
[00:32] -queuebot:#ubuntu-release- New: accepted mdnsd [ppc64el] (jammy-proposed) [0.11-2]
[00:32] -queuebot:#ubuntu-release- New binary: obs-transition-table [ppc64el] (jammy-proposed/universe) [0.2.1-2] (no packageset)
[00:33] -queuebot:#ubuntu-release- New: accepted ace [amd64] (jammy-proposed) [7.0.6+dfsg-2]
[00:33] -queuebot:#ubuntu-release- New: accepted ace [armhf] (jammy-proposed) [7.0.6+dfsg-2]
[00:33] -queuebot:#ubuntu-release- New: accepted ace [riscv64] (jammy-proposed) [7.0.6+dfsg-2]
[00:33] -queuebot:#ubuntu-release- New: accepted nvidia-egl-gbm [amd64] (jammy-proposed) [1.1.0-1]
[00:33] -queuebot:#ubuntu-release- New: accepted nvidia-egl-gbm [ppc64el] (jammy-proposed) [1.1.0-1]
[00:33] -queuebot:#ubuntu-release- New: accepted qdjango [amd64] (jammy-proposed) [0.6.2-3.2]
[00:33] -queuebot:#ubuntu-release- New: accepted ace [arm64] (jammy-proposed) [7.0.6+dfsg-2]
[00:33] -queuebot:#ubuntu-release- New: accepted ace [s390x] (jammy-proposed) [7.0.6+dfsg-2]
[00:33] -queuebot:#ubuntu-release- New: accepted poke [amd64] (jammy-proposed) [2.1+dfsg-2]
[00:33] -queuebot:#ubuntu-release- New: accepted ace [ppc64el] (jammy-proposed) [7.0.6+dfsg-2]
[00:33] -queuebot:#ubuntu-release- New: accepted nvidia-egl-gbm [arm64] (jammy-proposed) [1.1.0-1]
[00:33] -queuebot:#ubuntu-release- New: accepted budgie-control-center [amd64] (jammy-proposed) [0.4-1]
[00:33] -queuebot:#ubuntu-release- New: accepted budgie-control-center [armhf] (jammy-proposed) [0.4-1]
[00:33] -queuebot:#ubuntu-release- New: accepted budgie-control-center [s390x] (jammy-proposed) [0.4-1]
[00:33] -queuebot:#ubuntu-release- New: accepted budgie-control-center [arm64] (jammy-proposed) [0.4-1]
[00:33] -queuebot:#ubuntu-release- New: accepted budgie-control-center [ppc64el] (jammy-proposed) [0.4-1]
[00:34] -queuebot:#ubuntu-release- New: accepted gvfs [amd64] (jammy-proposed) [1.48.1-3]
[00:34] -queuebot:#ubuntu-release- New: accepted gvfs [armhf] (jammy-proposed) [1.48.1-3]
[00:34] -queuebot:#ubuntu-release- New: accepted gvfs [ppc64el] (jammy-proposed) [1.48.1-3]
[00:34] -queuebot:#ubuntu-release- New: accepted gvfs [s390x] (jammy-proposed) [1.48.1-3]
[00:34] -queuebot:#ubuntu-release- New: accepted gvfs [arm64] (jammy-proposed) [1.48.1-3]
[00:34] -queuebot:#ubuntu-release- New: accepted gvfs [riscv64] (jammy-proposed) [1.48.1-3]
[00:34] -queuebot:#ubuntu-release- New: accepted gvfs [i386] (jammy-proposed) [1.48.1-3]
[00:36] -queuebot:#ubuntu-release- New: accepted gh [amd64] (jammy-proposed) [2.4.0+dfsg1-1]
[00:36] -queuebot:#ubuntu-release- New: accepted gh [armhf] (jammy-proposed) [2.4.0+dfsg1-1]
[00:36] -queuebot:#ubuntu-release- New: accepted gh [riscv64] (jammy-proposed) [2.4.0+dfsg1-1]
[00:36] -queuebot:#ubuntu-release- New: accepted gh [arm64] (jammy-proposed) [2.4.0+dfsg1-1]
[00:36] -queuebot:#ubuntu-release- New: accepted gh [s390x] (jammy-proposed) [2.4.0+dfsg1-1]
[00:36] -queuebot:#ubuntu-release- New: accepted gh [ppc64el] (jammy-proposed) [2.4.0+dfsg1-1]
[00:36] <RAOF> Eickmeyer: Looks like the MITish license in bismuth is a match for the Expat license (which is the preferred name when it matches, because there are a bunch of different MITish licenses). Non-blocking, I'll file a bug afterwards if I accept it. (Still reviewing)
[00:36] -queuebot:#ubuntu-release- Unapproved: glibc (focal-proposed/main) [2.31-0ubuntu9.5 => 2.31-0ubuntu9.6] (core, i386-whitelist)
[00:37] -queuebot:#ubuntu-release- New: accepted go-sendxmpp [amd64] (jammy-proposed) [0.1.2-1]
[00:37] -queuebot:#ubuntu-release- New: accepted go-sendxmpp [armhf] (jammy-proposed) [0.1.2-1]
[00:37] -queuebot:#ubuntu-release- New: accepted go-sendxmpp [riscv64] (jammy-proposed) [0.1.2-1]
[00:37] -queuebot:#ubuntu-release- New: accepted luckyluks [amd64] (jammy-proposed) [2.0.1-1]
[00:37] -queuebot:#ubuntu-release- New: accepted python-bracex [amd64] (jammy-proposed) [2.2.1-1]
[00:37] -queuebot:#ubuntu-release- New: accepted go-sendxmpp [arm64] (jammy-proposed) [0.1.2-1]
[00:37] -queuebot:#ubuntu-release- New: accepted go-sendxmpp [s390x] (jammy-proposed) [0.1.2-1]
[00:37] -queuebot:#ubuntu-release- New: accepted go-sendxmpp [ppc64el] (jammy-proposed) [0.1.2-1]
[00:37] -queuebot:#ubuntu-release- New: accepted node-parse-srcset [amd64] (jammy-proposed) [1.0.2-1]
[00:40] -queuebot:#ubuntu-release- New: accepted baconqrcode [amd64] (jammy-proposed) [2.0.6-1]
[00:40] -queuebot:#ubuntu-release- New: accepted obs-transition-table [arm64] (jammy-proposed) [0.2.1-2]
[00:40] -queuebot:#ubuntu-release- New: accepted obs-transition-table [ppc64el] (jammy-proposed) [0.2.1-2]
[00:40] -queuebot:#ubuntu-release- New: accepted pyqt6-sip [arm64] (jammy-proposed) [13.2.1-2]
[00:40] -queuebot:#ubuntu-release- New: accepted pyqt6-sip [ppc64el] (jammy-proposed) [13.2.1-2]
[00:40] -queuebot:#ubuntu-release- New: accepted pyqt6-sip [s390x] (jammy-proposed) [13.2.1-2]
[00:40] -queuebot:#ubuntu-release- New: accepted obs-transition-table [amd64] (jammy-proposed) [0.2.1-2]
[00:40] -queuebot:#ubuntu-release- New: accepted pyqt6-sip [amd64] (jammy-proposed) [13.2.1-2]
[00:40] -queuebot:#ubuntu-release- New: accepted pyqt6-sip [riscv64] (jammy-proposed) [13.2.1-2]
[00:40] -queuebot:#ubuntu-release- New: accepted obs-transition-table [armhf] (jammy-proposed) [0.2.1-2]
[00:40] -queuebot:#ubuntu-release- New: accepted rocm-cmake [amd64] (jammy-proposed) [5.0.0-1]
[00:40] -queuebot:#ubuntu-release- New: accepted pyqt6-sip [armhf] (jammy-proposed) [13.2.1-2]
[00:40] -queuebot:#ubuntu-release- New: accepted ignition-physics [arm64] (jammy-proposed) [5.1.0+ds1-4]
[00:40] -queuebot:#ubuntu-release- New: accepted ignition-physics [riscv64] (jammy-proposed) [5.1.0+ds1-4]
[00:40] -queuebot:#ubuntu-release- New: accepted ignition-physics [armhf] (jammy-proposed) [5.1.0+ds1-4]
[00:40] -queuebot:#ubuntu-release- New: accepted tpm2-openssl [sync] (jammy-proposed) [1.0.1-1]
[00:42] -queuebot:#ubuntu-release- New binary: freeart [riscv64] (jammy-proposed/universe) [3.3.0+ds1-2] (no packageset)
[00:45] -queuebot:#ubuntu-release- New binary: tpm2-openssl [amd64] (jammy-proposed/none) [1.0.1-1] (no packageset)
[00:45] -queuebot:#ubuntu-release- New binary: tpm2-openssl [s390x] (jammy-proposed/none) [1.0.1-1] (no packageset)
[00:45] -queuebot:#ubuntu-release- New binary: tpm2-openssl [ppc64el] (jammy-proposed/none) [1.0.1-1] (no packageset)
[00:48] -queuebot:#ubuntu-release- New binary: tpm2-openssl [arm64] (jammy-proposed/none) [1.0.1-1] (no packageset)
[00:49] -queuebot:#ubuntu-release- New: accepted tpm2-openssl [amd64] (jammy-proposed) [1.0.1-1]
[00:49] -queuebot:#ubuntu-release- New: accepted tpm2-openssl [ppc64el] (jammy-proposed) [1.0.1-1]
[00:49] -queuebot:#ubuntu-release- New: accepted tpm2-openssl [arm64] (jammy-proposed) [1.0.1-1]
[00:49] -queuebot:#ubuntu-release- New: accepted tpm2-openssl [s390x] (jammy-proposed) [1.0.1-1]
[00:49] -queuebot:#ubuntu-release- New: accepted freeart [amd64] (jammy-proposed) [3.3.0+ds1-2]
[00:49] -queuebot:#ubuntu-release- New: accepted freeart [armhf] (jammy-proposed) [3.3.0+ds1-2]
[00:49] -queuebot:#ubuntu-release- New: accepted freeart [riscv64] (jammy-proposed) [3.3.0+ds1-2]
[00:49] -queuebot:#ubuntu-release- New: accepted freeart [arm64] (jammy-proposed) [3.3.0+ds1-2]
[00:49] -queuebot:#ubuntu-release- New: accepted freeart [ppc64el] (jammy-proposed) [3.3.0+ds1-2]
[00:52] -queuebot:#ubuntu-release- New binary: msc-generator [riscv64] (jammy-proposed/universe) [7.1-1] (no packageset)
[00:53] -queuebot:#ubuntu-release- New binary: tpm2-openssl [armhf] (jammy-proposed/none) [1.0.1-1] (no packageset)
[00:53] -queuebot:#ubuntu-release- New: accepted msc-generator [amd64] (jammy-proposed) [7.1-1]
[00:53] -queuebot:#ubuntu-release- New: accepted msc-generator [armhf] (jammy-proposed) [7.1-1]
[00:53] -queuebot:#ubuntu-release- New: accepted msc-generator [riscv64] (jammy-proposed) [7.1-1]
[00:53] -queuebot:#ubuntu-release- New: accepted tpm2-openssl [armhf] (jammy-proposed) [1.0.1-1]
[00:53] -queuebot:#ubuntu-release- New: accepted msc-generator [arm64] (jammy-proposed) [7.1-1]
[00:53] -queuebot:#ubuntu-release- New: accepted msc-generator [s390x] (jammy-proposed) [7.1-1]
[00:53] -queuebot:#ubuntu-release- New: accepted msc-generator [ppc64el] (jammy-proposed) [7.1-1]
[01:16] <RAOF> Oooh! You've got an ITP-ish bug that I can document on. Yay! Thanks!
[01:25] -queuebot:#ubuntu-release- New binary: golang-gitlab-yawning-edwards25519-extra [amd64] (jammy-proposed/universe) [0.0~git20211229.2f91fcc-1] (no packageset)
[01:25] -queuebot:#ubuntu-release- New binary: python-wcmatch [amd64] (jammy-proposed/universe) [8.3-1] (no packageset)
[01:25] -queuebot:#ubuntu-release- Packageset: Added libeatmydata to i386-whitelist in jammy
[01:28] -queuebot:#ubuntu-release- New binary: node-sanitize-html [amd64] (jammy-proposed/universe) [2.6.1-1] (no packageset)
[01:33] -queuebot:#ubuntu-release- New: accepted golang-gitlab-yawning-edwards25519-extra [amd64] (jammy-proposed) [0.0~git20211229.2f91fcc-1]
[01:33] -queuebot:#ubuntu-release- New: accepted python-wcmatch [amd64] (jammy-proposed) [8.3-1]
[01:33] -queuebot:#ubuntu-release- New: accepted node-sanitize-html [amd64] (jammy-proposed) [2.6.1-1]
[01:34] <Eickmeyer> RAOF: Got your message. Interesting, when I ran licensecheck it said MIT not expat?
[01:35] <RAOF> Eickmeyer: licensecheck just picks up the string “MIT” from the SPDX header.
[01:35] <Eickmeyer> Ah. So, it's not specific.
[01:37] <RAOF> Correct.
[01:37] <RAOF> Also, while I have you here: where did you get the copyright for `img/*`?
[01:37] <RAOF> As far as I can tell, none of those images have embedded copyright information. How was it determined that they were CC-BY-4.0?
[01:38] <Eickmeyer> Oh, that was the original author of the debian/ directory.
[01:39] <Eickmeyer> I kindof took a lazy way with that, the original author there seemed to be pretty proficient in packaging as it wasn't just a blanket copyright file.
[01:39] <Eickmeyer> RAOF: Mostly likely they got it from the LICENSES directory.
[01:40] <Eickmeyer> And since it only applies to artwork, it makes sense.
[01:40] -queuebot:#ubuntu-release- Packageset: Added binfmt-support to i386-whitelist in jammy
[01:40] -queuebot:#ubuntu-release- Packageset: Added strace to i386-whitelist in jammy
[01:41] <RAOF> +
[01:41] <RAOF> Some of the svgs are LGPL 🤪
[01:42] <Eickmeyer> Right.
[01:44] <RAOF> I also wonder where `2016-2019 Yuxuan Shui<EMAIL_ADDRESS>given that name appears nowhere in the source?
[01:45] <Eickmeyer> I have reason to believe that's from the project it was forked from (Khronkite).
[01:47] <Eickmeyer> Except I can't find that there either.
[01:50] <RAOF> Yeah, I was just looking through the git commits. 🤷♀
[01:51] <Eickmeyer> Ha! Exactly what I'm doing.
[01:53] <Eickmeyer> RAOF: Yeah, that's the only spot I can find the name mentioned as well.
[01:54] <Eickmeyer> Also, just be thankful I didn't leave the Files: * License line as "MIT or GPL-3 or LGPL-3.0-or-later or CC-BY-4.0"
[01:55] <RAOF> Well, at least that would be an easy reject 😛
[01:56] <RAOF> debian/rules is a little weird, too. Is there a reason to explicitly not build dbgsym packages?
[01:57] <RAOF> And the `compile_commands.json` stuff *looks* like it's there to make upstream development out of the source package easier?
[01:57] <Eickmeyer> Yeah, that is a little weird, and an oversight on my part.
[01:58] <Eickmeyer> Yeah, it does appear that way.
[02:01] -queuebot:#ubuntu-release- New binary: rocm-device-libs [riscv64] (jammy-proposed/universe) [5.0.0-1] (no packageset)
[02:04] <Eickmeyer> RAOF: Looks like a lot of it was taken from the scripts/*.sh to make the d/rules file.
[02:07] <RAOF> I *suspect* you should actually use `dh_auto_configure` rather than calling cmake directly, so as to get all the default cmake policy stuff.
[02:08] <RAOF> …and then you could drop all the `override_dh_` overrides.
[02:09] <Eickmeyer> Let me try it and see how it builds. There does appear to be a reason for the "compile_commands.json" as it only exists after the initial build, so I'm a little leery of removing that.
[02:10] <dbungert> paride: subiquity build to candidate.  see https://github.com/canonical/subiquity/releases/tag/untagged-8c00b7f18f92d2a57661 for highlights.  Let me know if I can help on any lingering concerns.  I do have one more feature to track down, complex enough that I don't want to delay this release but easy enough that I have no concerns about it done in time for 20.04.4
[02:17] <Eickmeyer> RAOF: Your suspicions were right. I commented out everything in the rules file beyond "dh $@" and it built just fine.
[02:18] <RAOF> You *might* want to manually do a `dh_auto_configure -- -DUSE_TSC=OFF -DUSE_NPM=OFF` in an override, but that would be it.
[02:19] <Eickmeyer> Sure.
[02:20] <Eickmeyer> I probably want to specify archs in a new upload because it does FTBFS on armhf, and ppc64el and s390x are dep-waits.
[02:21] <Eickmeyer> RAOF ^
[02:21] <Eickmeyer> Actually, RAOF, I take it all back: I was looking at the wrong build.
[02:22] <RAOF> :)
[02:22] <Eickmeyer> Complete FTBFS.
[02:23] <Eickmeyer> All archs.
[02:31] <RAOF> Ah. It's 1:30. That's why I'm hungry!
[02:31] <Eickmeyer> Eat. LUL
 "Complete FTBFS." <- The package as-uploaded, or without the overrides?
[02:31] <Eickmeyer> RAOF: without the overrides.
[02:32] <Eickmeyer> as-uploaded is fine on amd64 and arm64.
[02:38] -queuebot:#ubuntu-release- New binary: strace [i386] (jammy-proposed/main) [5.16-0ubuntu2] (core, i386-whitelist)
[02:40] -queuebot:#ubuntu-release- New: accepted rocm-device-libs [riscv64] (jammy-proposed) [5.0.0-1]
[02:40] -queuebot:#ubuntu-release- New: accepted strace [i386] (jammy-proposed) [5.16-0ubuntu2]
[03:01] <Eickmeyer[m]> RAOF (he/his): Looks like bismuth builds just fine with the one dh_auto_configure override.
[04:06] <RAOF> Eickmeyer: Shall I reject the current upload and do a quick re-review on a new upload?
[04:07] <Eickmeyer[m]> RAOF (he/his): Sure, we can do it that way. Also did the fixes in d/copyright and d/control to specify build archs.
[04:10] <Eickmeyer[m]> RAOF (he/his): New upload is up.
[04:10] -queuebot:#ubuntu-release- New: rejected bismuth [source] (jammy-proposed) [2.3.0-0ubuntu1]
[04:11] -queuebot:#ubuntu-release- New source: bismuth (jammy-proposed/primary) [2.3.0-0ubuntu1]
[04:29] <RAOF> Eickmeyer: `dpkg-source: warning: unexpected end of diff 'bismuth-2.3.0/debian/patches/hide-tray-icon'` on source unpack? What's that?
[04:29] <Eickmeyer[m]> That's weird, hadn't seen that before.
[04:30] <Eickmeyer[m]> Lemme see if it's even needed.
[04:31] <RAOF> The patch looks ok on disc.
[04:31] <Eickmeyer[m]> I agree, it seems odd that it broke like that.
[04:31] <Eickmeyer[m]> I mean, it's only a warning, but the patch seems fine.
[04:34] <Eickmeyer[m]> RAOF (he/his): Is that a blocker? Just seems odd that it came back like that after a source build which applies/unapplies all patches.
[04:35] <Eickmeyer[m]> If it is a blocker, I'm OK with omitting the patch.
[04:36] <RAOF> It's not a blocker, I just don't know what it's about.
[04:36] <RAOF> It's surprising!
[04:36] <Eickmeyer[m]> Yeah, it sure is surprising! Especially considering the patch looks completely sane.
[04:53] -queuebot:#ubuntu-release- New: accepted bismuth [source] (jammy-proposed) [2.3.0-0ubuntu1]
[04:57] -queuebot:#ubuntu-release- New binary: bismuth [arm64] (jammy-proposed/universe) [2.3.0-0ubuntu1] (no packageset)
[04:59] -queuebot:#ubuntu-release- New binary: bismuth [amd64] (jammy-proposed/universe) [2.3.0-0ubuntu1] (no packageset)
[06:30] -queuebot:#ubuntu-release- New binary: qt6-base [armhf] (jammy-proposed/universe) [6.2.2+dfsg-5] (no packageset)
[09:19] -queuebot:#ubuntu-release- New: accepted bismuth [amd64] (jammy-proposed) [2.3.0-0ubuntu1]
[09:19] -queuebot:#ubuntu-release- New: accepted bismuth [arm64] (jammy-proposed) [2.3.0-0ubuntu1]
[10:04] <sil2100> rbasak: hey! Just a heads up: I wanted to do a review of the glibc SRU in the focal Unapproved queue if you don't mind
[11:03] <cjwatson> Did somebody recently re-enable the manage-builders job running as ubuntu-archive@snakefruit?
[11:04] <cjwatson> I've disabled it again.  Please don't re-enable it without informing Mattermost ~launchpad as per the comment immediately above it (it's currently disabled because lcy02 is broken)
[11:05] <sil2100> Not me!
[11:08] <sil2100> waveform: heeey, could you fetch the latest raspi focal daily image and give it a spin on some pi's? It should be using the new gadget tree
[11:08] <sil2100> waveform: http://cdimage.ubuntu.com/ubuntu-server/focal/daily-preinstalled/20220216/
[11:08] <waveform> sil2100, on it
[11:16] <sil2100> Thank you!
[11:17] <rbasak> sil2100: sure, thanks
[11:29] <paride> sil2100, hi! How difficult would it be to produce live-server daily ISOs with subiquity from latest/candidate?
[11:30] <paride> in https://launchpadlibrarian.net/586323711/buildlog_ubuntu_focal_amd64_ubuntu-server-live_BUILDING.txt.gz I see stuff like:
[11:30] <paride> + local CHANNEL=
[11:30] <paride> + CHANNEL=stable/ubuntu-20.04
[11:30] <paride> so maybe there's a way to override the automatic channel selection mechanism?
[11:41] -queuebot:#ubuntu-release- Unapproved: accepted gtk+3.0 [source] (focal-proposed) [3.24.20-0ubuntu1.1]
[12:01] <sil2100> paride: hmm hmm
[12:06] <sil2100> paride: currently we don't have any easy means to do this. I think we'd need to tweak livecd-rootfs...
[12:07] <sil2100> paride: do you need it for .4? Or more like a thing for the future?
[12:09] -queuebot:#ubuntu-release- New binary: qt6-base [riscv64] (jammy-proposed/universe) [6.2.2+dfsg-5] (no packageset)
[12:22] <paride> sil2100, well it would be nice to have it for .4 already but I can see there isn't much time. But for the future I think we should try to have this
[12:48] -queuebot:#ubuntu-release- Unapproved: linux-meta-oem-5.14 (focal-proposed/main) [<IP_ADDRESS>3.20 => <IP_ADDRESS>3.21] (no packageset) (sync)
[12:51] <waveform> sil2100, .4 images looking good -- armhf and arm64 booted out of the box on 3B, 4B, and Pi Zero 2, wifi working, bluetooth working. I'll start filling in the focal daily iso tracker in a bit
[12:53] <xnox> sil2100:  vorlon: for the point release we should ship ISO images with oem-5.14 kernel as the default -oem-20.04 which we forgot to do. I have updated variants, rebuilt linux-meta-oem-5.14, and uploaded it. Please review and accept the above in-cycle linux-meta-oem-5.14 meta-only respin, such that focal ISOs will get the correct oem-5.14 on them
[12:57] <xnox> cause focal dailies still have odd amounts of oem kernels, let me try to double check how come obsolete oem-5.6 modules still end up on the iso
[13:05] <xnox> sil2100:  vorlon: also it appears that hwe-20.04-edge is unexpectedly getting pulled into focal daily isos. https://code.launchpad.net/~xnox/ubuntu-seeds/+git/ubuntu-seeds/+merge/415668 this should resolve that
[13:05] <xnox> ideally the pool on ship-live should only have hwe-20.04 & oem-20.04 and nothing else (no edge, no suffix letters)
[13:38] <sil2100> waveform: thanks! I'll release it and prepare for switching focal dailies to use -updates only
[13:39] <sil2100> xnox: reviewing the meta!
[13:39] <sil2100> xnox: also, wow, good catch with the seeds!
[13:41] <xnox> sil2100:  if you give the ack on the seeds, i'll push it.
[13:41] <xnox> but yeah no wonder our isos are so large given how much dangling unreferenced stuff is pulled in
[13:42] <xnox> or i'll just quote this irc message =)
[13:43] <sil2100> hm, I asked bdmurray to take a look at that a while back, but then I forgot to follow up if he found something ;)
[13:46] <sil2100> xnox: yeah, approved, please proceed!
[13:50] <sil2100> xnox: btw. just while we're at the -oem metapackage review, I just need to ask: I see there are some -oem-20.04d packages there, what does the 'd' stand for?
[13:50] <sil2100> In general in all the oem packages
[13:50] <xnox> sil2100:  the 4th oem kernel. given oem-5.6 was retrospectively called 20.04a, and we had others in between. You can see those in the kernel-series.yaml, one sec.
[13:51] <xnox> sil2100:  https://git.launchpad.net/~canonical-kernel/+git/kteam-tools/tree/info/kernel-series.yaml#n2017
[13:52] <xnox> oem-5.13 was -20.04c and oem-5.14 is -20.04d
[13:52] <sil2100> xnox: ok, good to know!
[13:52] <xnox> sil2100:  normally there are only two active at the time, i.e. "current one" and "edge/wip one". But oem vendors do not like "edge" and that it keeps changing.
[13:53] <xnox> sil2100:  hence literary for the sake of clarity we tell we will enable this nintendo-n64 with the oem-20.04c, and ps4 will be with oem-20.04d. and it will become default by this point release.
[13:53] <xnox> sil2100: granted oem-20.04d should be the last one. but we already have oem-22.04a in jammy
[13:55] <sil2100> xnox: hm, so just to make sure, since looking at the old linux-meta-oem-5.10 that we had, the linux-*-oem-20.04 metapackages were transitional packages that only depended on the -oem-20.04b variants. But the ones you add to linux-meta-oem-5.14 aren't dep-only on -oem-20.04d - is that intentional?
[14:11] <sil2100> xnox: so yeah, -meta-oem-5.14 looks basically good to go but I'd like to make sure the way it's done in the upload is the 'correct way'
[14:11] <sil2100> As per ^
[14:25] <xnox> sil2100:  yes it is intentional. it has been a two year long oversight of not making oem-20.04 an everlasting flavour.
[14:26] <xnox> sil2100:  i.e. it should have done the same thing that we do for "aws"/"aws-edge", "hwe"/"hwe-edge". but the first roll from oem to oem-wip to oem-20.04b was done incorrectly; and repeated a few times.
[14:27] <xnox> sil2100: hence everything is rolling over to oem-20.04 now, and we will have transitional from oem-20.04 -> (oem-22.04 or hwe) in jammy.
[14:27] <xnox> sil2100: but we wouldn't want to have 20.04(a..d) transitionals in jammy.
[14:27] <xnox> so fixing past mistakes really here.
[14:27] <xnox> it is bringing oem stuff in line with other kernels.
[14:39] <sil2100> ACK!
[14:44] <sil2100> xnox: ok, should be accepted
[14:48] -queuebot:#ubuntu-release- Unapproved: klibc (bionic-proposed/main) [2.0.4-9ubuntu2 => 2.0.4-9ubuntu<IP_ADDRESS>] (core)
[15:47] <xnox> sil2100:  now i "just" need to respin lrm stuff correctly for it
[15:47] -queuebot:#ubuntu-release- Unapproved: accepted gallery-dl [source] (focal-backports) [1.20.5-1~bpo20.04.1]
[15:49] -queuebot:#ubuntu-release- Unapproved: accepted gramps [source] (impish-backports) [5.1.4-1~bpo21.10.1]
[16:18] <cjwatson> Re-enabled manage-builders cron job now that lcy02 is fixed.
[16:46] <athos> Hi! We are moving towards removing python-oauth from the archive in LP: #1118815; is there any other action needed from my side other than subscribing ubuntu-archive in the bug?
[16:49] <bdmurray> athos: running a check of the reverse depends for jammy would be good
[17:03] <athos> Thanks, bdmurray :) I added a comment to the bug with the verification results
[17:05] <bdmurray> athos: That's great, thanks.
[17:33] -queuebot:#ubuntu-release- New binary: fonts-national-park [amd64] (jammy-proposed/none) [0.0~20220205-1] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: golang-github-bettercap-nrf24 [amd64] (jammy-proposed/none) [0.0~git20190219.aa37e6d-1] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: golang-github-wader-readline [amd64] (jammy-proposed/none) [0.0~git20220118.692d84c-2] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: golang-github-pbnjay-memory [amd64] (jammy-proposed/none) [0.0~git20210728.7b4eea6-1] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: pyparsing2 [amd64] (jammy-proposed/none) [2.4.7-3] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: lambdaisland-uri-clojure [amd64] (jammy-proposed/none) [1.13.95-1] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: simple-whip-server [amd64] (jammy-proposed/none) [0.0~git20220204-2] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: valgrind-if-available [amd64] (jammy-proposed/none) [3.18.1] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: simple-whip-client [amd64] (jammy-proposed/none) [0.0~git20211111-3] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: toml11 [amd64] (jammy-proposed/none) [3.7.0-2] (no packageset)
[17:38] -queuebot:#ubuntu-release- New binary: python-jose [amd64] (jammy-proposed/universe) [3.3.0+dfsg-1] (no packageset)
[17:38] -queuebot:#ubuntu-release- New binary: wsdd [amd64] (jammy-proposed/universe) [2:0.7.0-1] (no packageset)
[17:38] -queuebot:#ubuntu-release- New binary: wireguard-go [amd64] (jammy-proposed/universe) [0.0.20220117-1] (no packageset)
[17:38] -queuebot:#ubuntu-release- New binary: yubikey-agent [amd64] (jammy-proposed/universe) [0.1.4-1] (no packageset)
[17:38] -queuebot:#ubuntu-release- New binary: valgrind-if-available [ppc64el] (jammy-proposed/universe) [3.18.1] (no packageset)
[17:39] -queuebot:#ubuntu-release- New binary: wireguard-go [ppc64el] (jammy-proposed/universe) [0.0.20220117-1] (no packageset)
[17:39] -queuebot:#ubuntu-release- New binary: yubikey-agent [ppc64el] (jammy-proposed/universe) [0.1.4-1] (no packageset)
[17:39] -queuebot:#ubuntu-release- New binary: simple-whip-client [ppc64el] (jammy-proposed/universe) [0.0~git20211111-3] (no packageset)
[17:41] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-tesla-510 [amd64] (jammy-proposed/multiverse) [510.47.03-1] (no packageset)
[17:41] -queuebot:#ubuntu-release- New binary: valgrind-if-available [s390x] (jammy-proposed/universe) [3.18.1] (no packageset)
[17:42] -queuebot:#ubuntu-release- New binary: wireguard-go [s390x] (jammy-proposed/universe) [0.0.20220117-1] (no packageset)
[17:43] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-tesla-510 [ppc64el] (jammy-proposed/multiverse) [510.47.03-1] (no packageset)
[17:43] -queuebot:#ubuntu-release- New binary: yubikey-agent [s390x] (jammy-proposed/universe) [0.1.4-1] (no packageset)
[17:49] <waveform> sil2100, the focal images don't use the seed, correct?
[18:07] -queuebot:#ubuntu-release- New binary: valgrind-if-available [arm64] (jammy-proposed/universe) [3.18.1] (no packageset)
[18:07] -queuebot:#ubuntu-release- New binary: valgrind-if-available [armhf] (jammy-proposed/universe) [3.18.1] (no packageset)
[18:07] -queuebot:#ubuntu-release- New binary: simple-whip-client [armhf] (jammy-proposed/universe) [0.0~git20211111-3] (no packageset)
[18:07] -queuebot:#ubuntu-release- New binary: wireguard-go [arm64] (jammy-proposed/universe) [0.0.20220117-1] (no packageset)
[18:08] -queuebot:#ubuntu-release- New binary: simple-whip-client [arm64] (jammy-proposed/universe) [0.0~git20211111-3] (no packageset)
[18:08] -queuebot:#ubuntu-release- New binary: yubikey-agent [arm64] (jammy-proposed/universe) [0.1.4-1] (no packageset)
[18:08] -queuebot:#ubuntu-release- New binary: wireguard-go [armhf] (jammy-proposed/universe) [0.0.20220117-1] (no packageset)
[18:11] -queuebot:#ubuntu-release- New binary: yubikey-agent [armhf] (jammy-proposed/universe) [0.1.4-1] (no packageset)
[18:16] -queuebot:#ubuntu-release- New binary: valgrind-if-available [riscv64] (jammy-proposed/universe) [3.18.1] (no packageset)
[18:21] -queuebot:#ubuntu-release- New binary: wireguard-go [riscv64] (jammy-proposed/universe) [0.0.20220117-1] (no packageset)
[18:23] -queuebot:#ubuntu-release- New binary: yubikey-agent [riscv64] (jammy-proposed/universe) [0.1.4-1] (no packageset)
[18:32] -queuebot:#ubuntu-release- New binary: simple-whip-client [riscv64] (jammy-proposed/universe) [0.0~git20211111-3] (no packageset)
[18:35] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-tesla-510 [arm64] (jammy-proposed/multiverse) [510.47.03-1] (no packageset)
[21:32] -queuebot:#ubuntu-release- Unapproved: openssl (focal-proposed/main) [1.1.1f-1ubuntu2.10 => 1.1.1f-1ubuntu2.11] (core, i386-whitelist)
[22:57] <bdmurray> RAOF: Are you about and able to sru-release partman-auto for Focal? bug 1959971
[23:00] <RAOF> We're ok with releasing that before we've decided how we're going to fix it in jammy?
[23:01] <bdmurray> RAOF: With my release team hat on yes. ;-) The compression method might change in Jammy and increasing the /boot partition size will help with the larger initrd size with the jammy kernel and also takes into account the nvidia modules (something we hadn't done).
[23:03] <RAOF> 👍
[23:03] <bdmurray> RAOF: actually, I guess its more important to release ubiquity. I didn't want to do it b/c I verified it too.
[23:04] <RAOF> I was going to release both, because you tested both, right?
[23:04] <bdmurray> Yes.
[23:04] <RAOF> The live image you tested contains both updates, and wouldn't work if either of the updates failed.
[23:06] <bdmurray> ubiquity includes partman-auto in it
[23:06] <bdmurray> https://launchpadlibrarian.net/585375463/ubiquity_<IP_ADDRESS>_<IP_ADDRESS>.diff.gz
[23:11]  * RAOF should really fix sru-release to not add the “we've released this update” comment when run with --no-act.
[23:12] <bdmurray> That's amazing and I'm probably to blame.
[23:25] <bdmurray> RAOF: Could you fully phase those two packages too?
[23:28]  * RAOF briefly wonders why he can't set the phasing for partman-auto in jammy-updates to 100 🤦♀
[23:30] <RAOF> Enjoy your fully-phased installer components.
[23:30] <bdmurray> RAOF: Sorry python-apt too please
[23:31] <bdmurray> It's at 90% and might get phased soon but why wait?
[23:35] -queuebot:#ubuntu-release- New binary: nfs-utils [amd64] (jammy-proposed/main) [1:2.6.1-1~exp1ubuntu1] (core)
[23:35] -queuebot:#ubuntu-release- New binary: nfs-utils [armhf] (jammy-proposed/main) [1:2.6.1-1~exp1ubuntu1] (core)
[23:35] -queuebot:#ubuntu-release- New binary: nfs-utils [s390x] (jammy-proposed/main) [1:2.6.1-1~exp1ubuntu1] (core)
[23:36] -queuebot:#ubuntu-release- New binary: nfs-utils [arm64] (jammy-proposed/main) [1:2.6.1-1~exp1ubuntu1] (core)
[23:36] -queuebot:#ubuntu-release- New binary: nfs-utils [ppc64el] (jammy-proposed/main) [1:2.6.1-1~exp1ubuntu1] (core)
[23:44] <bdmurray> I'm retrying the ubuntu-drivers-common builds for Focal to try and get that package released.


[17:53] <dmfrey> I can't seem to get mythbuntu-control-centre to update the repos to pull in the v29 release. the dialog says an error occurred downloading the db. Is there anything I can do to fix this?
[18:20] <tgm4883> dmfrey: what distro are you on?
[18:20] <tgm4883> dmfrey: The v29 builds are broken at the moment, although I'm hoping they will be fixed this week
[19:24] <dmfrey> tgm4883: still on 14.04. cool, thanks, i will wait then. I am heading back out on a business trip tomorrow. I will hold off until next week.
[19:25] <dmfrey> it told me it had an error downloading repos.db, which i found in ~/.mythbuntu in my home directory


[00:26] <valorin> Can someone give this bug some loving? It's really annoying and I'd like to get it seen by the right people: https://bugs.launchpad.net/unity/+bug/834248
[00:27] <valorin> It's been present since Natty: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/755842
[00:37] <apw> are we aware of compiz going into a flat spin consuming 100% CPU on login?
[00:45] <kscloud> unabashed self-promotion if someome might want to look it over: https://lists.launchpad.net/ayatana/msg06519.html
[01:26] <valorin> Can someone give this bug some loving? It's really annoying and I'd like to get it seen by the right people: https://bugs.launchpad.net/unity/+bug/834248
[02:10] <Victor_> Unity is taking really long to compile. How long [in average] does it take on your machines?
[05:29] <valorin> Anyone around to take a look at a bug for me?
[05:48] <didrocks> good morning
[06:09] <valorin> Anyone around to take a look at a bug for me?
[08:58] <Andy80> 'morning
[09:07] <ephan> morning Andy80
[09:16] <oier> hi, I am looking for some kind of guideline or specification document about indicators status colors
[09:16] <oier> AFAIK the informative status for oneiric has changed to blue, I would like to know which kind of blue it is for instance
[09:17] <oier> and lastly, since I maintain an indicator, if the one in Natty should turn green and the Oneiric version blue
[09:20] <sbte> hi, is it possible to change the behaviour of a launcher entry itself through the launcher API?
[10:21] <kamstrup> sbte: no - or depends what you have in mind exactly...
[10:57] <kamstrup> didrocks: so lp:compiz-core/oneiric FTBFS... is it you or smspillaz I need to punk?
[10:59] <didrocks> kamstrup: this branch is smspillaz
[10:59] <didrocks> kamstrup: I'm lp:compiz
[10:59] <kamstrup> didrocks: not lp:compiz-core?
[11:00] <didrocks> not that one :) all that are smspillaz's projects
[11:00] <kamstrup> dude... there are so many lp:compiz* branches and projects... it's a jungle
[11:04] <sbte> kamstrup, I want the launcher entry to unhide a hidden instance instead of starting a new one
[11:05] <didrocks> kamstrup: the project is a jungle itself :)
[11:05] <didrocks> kamstrup: smspillaz created an upstream project for every plugin IIRC
[11:05] <sbte> the quicklist is there on the entry, so it's at least aware that the program is started
[11:06] <kamstrup> sbte: ah so you want some way to raise your app similarly to when the launcher icon is clicked?
[11:06] <sbte> no, clicking the icon currently starts a new instance
[11:07] <sbte> because the app is hidden
[11:07] <sbte> in the messaging menu actually
[11:07] <sbte> i want clicking the icon to show the hidden instance instead of starting a new one
[11:09] <jjardon> rodrigo_: ping
[11:11] <rodrigo_> jjardon, pong
[11:11] <jjardon> rodrigo_: hey, I wonder if you have problem loading the datetime panel in g-c-c
[11:12] <jjardon> problems*
[11:12] <rodrigo_> jjardon, let me try
[11:13] <rodrigo_> jjardon, works fine, but this is in gnome-shell
[11:13] <rodrigo_> jjardon, you mean the upstream one, or the indicator-datetime one?
[11:13] <jjardon> rodrigo_: oh, I mean the unity datetime, the indicator-datetime
[11:13] <rodrigo_> let me try that one
[11:14] <jjardon> stop working here and maybe is because some change upstream
[11:14] <jjardon> or something is wrong in my system ;)
[11:14] <rodrigo_> jjardon, it loads ok also
[11:14] <rodrigo_> jjardon, this is with the very latest g-c-c (3.1.91)
[11:15] <rodrigo_> jjardon, any output on the terminal related to that?
[11:22] <kamstrup> sbte: sounds mostly like BAMF has problems detecting that your app is already running - do you have a .desktop file for it?
[11:22] <kamstrup> (that you can maybe pastebin?)
[11:23] <sbte> kamstrup, yep, and there's also an option to run it single instance, but I want only the launcher to trigger that option
[11:24] <sbte> kamstrup, /usr/share/emesene/emesene/data/share/applications/emesene.desktop
[11:24] <sbte> that's the desktop file
[11:24] <sbte> if you have emesene installed
[11:26] <sbte> problem is that it's started, but that it doesn't have any active windows
[11:26] <sbte> so the launcher doesn't know that it's there
[11:27] <sbte> but most people tend to lock it to the launcher
[11:27] <kamstrup> sbte: Are you certain that is the problem? And not fx. that you are changing the process name?
[11:27] <sbte> and click the icon multiple times, starting multiple instances of emesene without knowing
[11:28] <sbte> kamstrup, yes, we allow multiple instances, and there's a command line option to disable it, but I want to disable it only for the unity launcher
[11:28] <kamstrup> sbte: you could also have a switch to the executable like --show that checked for a running instance and then showed that?
[11:28] <kamstrup> then put emesene --show in the .desktop
[11:28] <sbte> other distros/oses/starting options should be able to use the multiple instance option by default
[11:29] <rodrigo_> jjardon, I need to go now for a bit, try to look for some message in the output, and if you don't find the cause, ping me later, ok?
[11:29] <sbte> kamstrup, we already have the -s option, but we don't want to enable it by default
[11:29] <sbte> our problem is just people that have emesene locked in their launcher and wonder why they get 50 notification when someone talks to them
[11:30] <sbte> hence my question if you can change the behaviour of the launcher only by using the launcher API
[11:31] <sbte> we DON'T want to change the desktop file, because that will affect other distributions too where this is no issue, because the unity launcher/messaging menu aren't used
[11:41] <kamstrup> sbte: ok, i see. I don't have a solution then... you could request that the ubuntu packages be distro patched to add -s to the .desktop file, but I guess that's not exactly the solution you had hoped for
[11:47] <kamstrup> smspillaz: right now - when I run 'unity' inside my jhbuild env, it looks mostly like compiz starts without any plugins...
[11:47] <jjardon> rodrigo_: thanks, but It was a problem in my system. Sorry for bother you
[11:48] <smspillaz> kamstrup: ah
[11:48] <smspillaz> kamstrup: you're using lp:compiz-core right ?
[12:52] <htorque> Trevinho: bug 841609 → sure, but do you mean today, this week, month?
[13:07] <JohnLea> andyrock; has your patch for https://bugs.launchpad.net/ayatana-design/+bug/727901 landed?
[13:07] <andyrock> JohnLea, no...
[13:08] <andyrock> i'm waiting DBO's answer
[13:08] <DBO> uhm
[13:08] <DBO> let me find an answer for you
[13:09] <andyrock> JohnLea, btw thx for the clarifications about devices managament in the bug report :)
[13:09] <JohnLea> np, thx for fixing
[13:10] <andyrock> just one quick question: if a virtual device is blacklisted but "mounted" it should not be shown in dash right?
[13:10] <njpatel> cdbs, has the apt-daemon side of your merge proposal for SC been merged and in Oneiric?
[13:12] <jcastro> hey cdbs
[13:13] <jcastro> you had a list of quicklists for oneiric, is the spec up to date with what was accomplished?
[13:17] <JohnLea> andyrock; if a user has chosen to not have a mounted device in the Launcher, it should not be displayed in the Launcher.  However *all* mounted devices should always be displayed in the Dash File Lens 'folders' category header.  This how users can add them to the Launcher if they choose, or add them back to the launcher if they earlier removed them and then changed their mind.
[13:18] <JohnLea> andyrock; does that make sense?
[13:18] <andyrock> JohnLea, just one note
[13:19] <andyrock>  However *all* mounted devices should always be displayed in the Dash File Lens 'folders'
[13:19] <andyrock> maybe
[13:19] <andyrock> all mounted removable (or virtual devices)
[13:19] <andyrock> the un-removable devices imho should be always shown
[13:20] <JohnLea> andyrock; yes, basically everything that is currently accessible should always be shown in the Dash file lens
[13:20] <JohnLea> that includes un-removable devices
[13:20] <andyrock> ok ok...
[13:20] <andyrock> now i've the I have the full picture ;)
[13:21] <JohnLea> but not a usb key that is currently in your pocket, or a CD that is not in the drive
[13:21] <JohnLea> cool ;-)
[13:21] <JohnLea> andyrock; one other question...
[13:21] <JohnLea> just reviewing bug https://bugs.launchpad.net/ayatana-design/+bug/764460 but it is impossible to test because bug https://bugs.launchpad.net/ayatana-design/+bug/764641 as not yet been implemented.  Should I revert to triaged?
[13:22] <andyrock> DBO is merging this branch right now :)
[13:22] <andyrock> if it find some problems with my branch you change this bug status to invalid (or triaged i don't really know)
[13:23] <andyrock> however it's not totally fixed so fix-committed is not the best bug status
[13:23] <andyrock> there still is a small race condition
[13:24] <andyrock> an xdnd problem, other toolkits have the same problem
[13:24] <andyrock> so i think that triaged is the best bug status :)
[13:58] <jcastro> hey njpatel
[14:01] <njpatel> hey jcastro
[14:01] <jcastro> njpatel: lenses api!
[14:02] <njpatel> jcastro, kamstrup is working on making python work, and I'm doing a app developer thing on Friday, so basically, it'll be done by then very latest
[14:02] <jcastro> jawesome dude
[14:09] <roignac> guys, a question on lenses api
[14:10] <roignac> will libunity-4.0 be available in natty - or devs will have to wite two versions of lenses for oneiric and natty?
[14:34] <Cimi> njpatel: ping
[14:35] <Cimi> njpatel: remember the issue with the menubar/indicator items? I added 1px offset to them, but after seeing the indicator session menuitem (you can see there's 1px offset on the right, before the end of the panel), I had the real feeling that the dropdown menu was misplaced
[14:36] <Cimi> njpatel: andyrock told me that in unity-panel-service there's 1px of offset, which confirms my theory
[14:36] <Cimi> njpatel: and it's weird
[14:36] <njpatel> Cimi, okay, patch it?
[14:36] <Cimi> njpatel: my proposal is to remove the offset from unity drawing code
[14:37] <Cimi> njpatel: and explain me why there's a 1px of offset here
[14:37] <Cimi> in unity-panel-service
[14:37] <andyrock> Cimi: not in unity-panel-service
[14:37] <andyrock> :)
[14:37] <Cimi> andyrock: where?
[14:37] <andyrock> in PanelIndicatorObjectEntryView
[14:37] <Cimi> ok njpatel ^
[14:37] <njpatel> Cimi, I don't know, it's been too long since I've worked on that
[14:37] <andyrock> but the real drawing is in unity-panel-service
[14:37] <njpatel> there is probably a comment there if there is a magic number
[14:40] <andyrock> njpatel, 142
[14:40] <andyrock> void PanelIndicatorObjectEntryView::Activate()
[14:40] <andyrock> 143
[14:40] <andyrock> {
[14:40] <andyrock> 144
[14:40] <andyrock>   proxy_->ShowMenu(GetAbsoluteGeometry().x + 1, //cairo translation FIXME: Make this into one function
[14:40] <andyrock> 145
[14:40] <andyrock>                    GetAbsoluteGeometry().y + PANEL_HEIGHT,
[14:40] <andyrock> 146
[14:40] <andyrock>                    time(NULL),
[14:40] <andyrock> 147
[14:40] <andyrock>                    1);
[14:40] <andyrock> 148
[14:40] <andyrock> }
[14:40] <njpatel> if it's no longer needed, just remove it?
[14:41] <Cimi> http://paste.ubuntu.com/683587/
[14:42] <Cimi> andyrock: could you pls test it?
[14:42] <Cimi> andyrock: feel free to take the code and merge request it, I can approve it
[14:42] <Cimi> (if works)
[14:43] <andyrock> Cimi, there is another "+ 1" in the same file...
[14:43] <andyrock> i will do it
[14:43] <Cimi> uh
[14:43] <Cimi> andyrock: so, remove that +1 too
[14:43] <andyrock> there is a bug on #lp?
[14:43] <andyrock> LP
[14:43] <Cimi> no
[14:44] <Cimi> http://paste.ubuntu.com/683588/
[15:00] <ach1m_> njpatel, hi, is that bug on your "radar" https://bugs.launchpad.net/ubuntu/+bug/837432 ?
[15:05] <Cimi> ach1m_: it's such a small bug, leave it for the future weeks
[15:06] <ach1m_> Cimi, okay :-)
[15:06] <Cimi> andyrock: did I kill your unity?
[15:07] <andyrock> Cimi, unity compilation time is huge :)
[15:07] <andyrock> i've a dual core
[15:07] <Cimi> me too
[15:08] <andyrock> done...
[15:08] <andyrock> i've to post a screenshot here?
[15:08] <andyrock> but for me it looks good
[15:09] <Trevinho> htorque: I guess as soon as possible...
[15:10] <Trevinho> htorque: however I just I've to to use another partition to check it?
[15:11] <Andy80> andyrock: lucky me... it takes a couple of minutes with Unity-2d :D
[15:11] <andyrock> Andy80, 6-7 minutes for me... :(
[15:12] <Andy80> andyrock: even less if I only modify 1-2 files
[15:13] <Trevinho> Andyrock did you play with some indicators related code?
[15:13] <andyrock> Trevinho, why? :)
[15:14] <Trevinho> Because something could change there.... https://code.launchpad.net/~3v1n0/unity/indicators-redesign/+merge/70818
[15:15] <Trevinho> Ah... OK I saw that
[15:16] <Trevinho> andyrock: the plus one thing fixes the event issue on first pixel?
[15:17] <andyrock> Trevinho, i think not...
[15:17] <andyrock> it's a cimi work btw
[15:18] <Trevinho> ah, ok
[15:18] <Trevinho> Ah, also if I guess it's just related to the entry menu position
[15:18] <Cimi> Trevinho: you always do enormous patches, these are more difficult to review
[15:19] <Trevinho> Cimi: I know that, but that is a complete redesign
[15:19] <Cimi> ok then
[15:19] <Trevinho> it needs lots of things to be adjusted
[15:19] <Cimi> ok
[15:19] <Cimi> andyrock: if the patch works, I can approve it
[15:20] <andyrock> http://img109.imageshack.us/img109/707/screenshot20at202011090.png
[15:20] <Cimi> os ri can do the merge
[15:20] <andyrock> Cimi, ^^^
[15:20] <andyrock> and https://code.launchpad.net/~andyrock/unity/removes-plus-one/+merge/74244
[15:20] <Cimi> andyrock: topright indocator touches the screen^
[15:20] <Cimi> ?
[15:20] <Cimi> the gear
[15:20] <Trevinho> andyrock: you still have the network menu as last item... ohoh... :P
[15:20] <andyrock> Trevinho, why^
[15:21] <Cimi> andyrock: ?
[15:21] <andyrock> Cimi, yes
[15:21] <Cimi> ok, perfect then
[15:21] <andyrock> let me post another screen
[15:23] <andyrock> Cimi, http://img850.imageshack.us/img850/707/screenshot20at202011090.png
[15:23] <andyrock> the cut cursor is a screenshot bug :)
[15:24] <andyrock> not a unity problem...
[15:24] <Trevinho> andyrock: new order http://imageshack.us/photo/my-images/703/indicatorsreordered.png/ :P
[15:24] <Cimi> yep
[15:24] <Cimi> cool
[15:24] <Cimi> Trevinho: use geany
[15:24] <andyrock> Trevinho, great!
[15:24] <Cimi> Trevinho: it kicks gedit's ass
[15:25] <andyrock> Trevinho, add a gsettings option to change indicator position too
[15:25] <Trevinho> andyrock: I would like that
[15:25] <Trevinho> but I don't know if it's something requested
[15:25] <andyrock> to make ubuntu more flame free
[15:25] <Trevinho> or that can be handled easier yet
[15:26] <Trevinho> The fact is that actually only the indicators based on libappindicator have a name to be used to easily order them
[15:26] <Trevinho> otherwise I should use in the settings the tuple libraryname,indicator-name
[15:26] <Trevinho> and that sucks
[15:26] <Trevinho> maybe in next cycle I'll add that.
[15:27] <Trevinho> Cimi: I know I should use that... I used for some time, then I don't put it in my devel machine
[15:27] <Trevinho> however Cimi does it support for dynamic ctags right now?
[15:27] <Trevinho> Once I had to update my ctags file everytime
[15:28] <Cimi> Trevinho: not in realtime I'd say
[15:28] <Cimi> Trevinho: after a bit
[15:29] <Trevinho> Mh, ok... It's still good
[15:30] <Trevinho> also if in that role Eclipse would beat every IDE ever.... The problem is that I'd need other 8GB of ram to use it!
[15:30] <htorque> Trevinho: yeah, should work with a second ext4 partition or from an external drive
[15:30] <Trevinho> htorque: also another kind of partition?
[15:31] <htorque> ext4, ntfs, vfat on a flash drive worked for me
[15:31] <Trevinho> ok
[15:31] <Trevinho> I'll try
[15:31] <htorque> just pick two bigger files and it should fail like in the screenshot
[15:37] <Trevinho> htorque: ok, found
[15:38] <htorque> :)
[15:38] <Trevinho> it also happens when computing the size
[15:51] <nigelb> njpatel: Hey
[15:51] <njpatel> nigelb, hey dude
[15:51] <nigelb> All set for the session?
[15:51] <nigelb> oh wait, you cancelled...
[15:51] <njpatel> nigelb, it's been moved to friday :)
[15:52] <nigelb> njpatel: Yeah, just got told. Updating :)
[17:45] <smoser> is this a known bug ?
[17:45] <smoser> i hit alt-f2, the dialog comes up, but i can't launch anything from it.
[17:46] <smoser> usually it works the first time after login, and then it seems like it works sometimes, but most of the time not.
[17:46] <smoser> (unity-2d)
[18:24] <jderose> what's the correct, modern way to save/restore window positions and sizes?
[20:09] <sbte> jcastro, any chance this bug will get fixed before 11.10? https://bugs.launchpad.net/ubuntu/+source/unity/+bug/732997
[20:10] <sbte> Because otherwise I need to submit a critical patch for emesene
[20:11] <jcastro> smspillaz is the one to poke
[20:13] <sbte> jcastro, ok thanks, i guess you just did that :P
[20:23] <jcastro> DBO: unless that bug is your fault? or is it compiz?
[20:23] <DBO> file against unity
[20:23] <DBO> assign to smspillaz
[20:40] <czajkowski> Aloha
[20:40] <jcastro> DBO: hey ^^^^
[20:40] <jcastro> does alt-tab window get stuck sometimes?
[20:40] <DBO> no in my experience but if it does let me know
[20:40] <czajkowski> what happens is the menu comes across the screen where I alt tab through applications
[20:40] <czajkowski> and then won't go away
[20:40] <czajkowski> so I alt tab to a terminal
[20:40] <czajkowski> I cant get to it
[20:40] <czajkowski> the menu bar will not go away
[20:41] <DBO> so its the menu bar getting stuck
[20:41] <DBO> not alt-tab
[20:41] <czajkowski> yes
[20:42] <czajkowski> it won't vanish
[20:43] <DBO> czajkowski, I'll look at it when I can
[20:43] <DBO> my system is kinda fucked up right now :)
[20:43] <czajkowski> DBO: I can file a bug
[20:43] <czajkowski> just not sure what to file it against
[20:43] <DBO> unity
[21:08] <htorque> hey all! i just tested the latest fix for alt-tab and dash corners. looks miles better than before, but can it still be improved? http://img.xrmb2.net/images/675518.png
[21:17] <Andy80> Kaleo: are you still here?
[21:25] <om26er> htorque, i'll be testing it soonish if it build fine in my ppa and screenshot wont open
[21:25] <om26er> imagebin plz ;)
[21:26] <htorque> om26er:  http://imagebin.org/index.php?mode=image&id=171316
[21:27] <htorque> i hope i picked the right "imagebin" - there are lots of them ;-)
[21:27] <om26er> DBO, that would be one way to make it "stuck" bug 832033
[21:28] <DBO> thats not really stuck but I see the problem
[21:28] <DBO> also seriously, who alt-tab's with Onboard?
[21:28]  * om26er is clueless
[21:28] <DBO> fundamentally that is pretty broken
[21:28] <om26er> DBO, maybe this case might fix the other as well
[21:29] <DBO> not really related :)
[21:29] <om26er> htorque, thats zoomed i'll see how it looks in real size
[21:31] <om26er> https://bugs.launchpad.net/unity/+bug/832033/comments/3 might be another way to reproduce the problem
[21:31] <om26er> or https://bugs.launchpad.net/unity/+bug/832033/comments/6
[21:36] <htorque> heh, yeah that works - can you make it unstuck? :)
[22:19] <jono> DBO, yo
[22:20] <jono> remember the bug we found when moving your mouse slowly to the left edge of the screen and the launcher not showing?
[22:50] <Trevinho> htorque: around?
[22:50] <htorque> ya
[22:50] <Trevinho> Well, I've looked at that nautilus issue
[22:50] <Trevinho> but I can't reproduce it anymore using my own compiled version
[22:51] <Trevinho> If i push it to a branch could you test it?
[22:51] <htorque> sure
[22:51] <Trevinho> fine, so wait few minutes and I'll put it online
[23:01] <Trevinho> htorque: sorry, but I ask you to wait other few minutes... Unfortunately I've lost the copy of nautilus i was working on... Damn! I always put things on /tmp... :(
[23:01] <htorque> oh no :(
[23:03] <Trevinho> Not that bad since I just changed few details, but I've to remember what... :P
[23:51] <Trevinho> htorque: still here? :)
[23:52] <htorque> yes
[23:52] <Trevinho> ok
[23:52] <Trevinho> htorque:  try this version: lp:~3v1n0/+junk/nautilus-unity-debug
[23:52] <Trevinho> (it's sitll uploading :P)
[23:53] <Trevinho> however, just compile it, killall nautilus before running it
[23:53] <Trevinho> and run nautilus launching it from a terminal
[23:53] <Trevinho> it should print some informations on the terminal while copying the files.
[23:53] <Trevinho> So, please send me the output you get when the error occurs
[23:53] <htorque> sure :)
[23:54] <Trevinho> Thanks
[23:54] <htorque> does that branch contain packaging info so that i just can run debuild?
[23:54] <Trevinho> yes
[23:54] <htorque> cool
[23:54] <Trevinho> you can use debuild as well
[23:54] <thumper> boom, boom, boom... another one bites the dust
[23:54] <thumper> memory leak that is...
[23:56] <htorque> thumper: i guess not the one in indicator-applications or the way worse (probably) in indicator-appmenu? ;-)
[23:56] <thumper> htorque: no, unity and nux
[23:57] <htorque> too bad, anyways: keep putting 'em down! :-)


[19:55] <ibeardslee> morning
[20:26] <mwhudson> morning
[21:22] <olly> morning
[21:27] <ajmitch> morning


[04:56] <hikiko> Hi
[05:50] <pitti> Good morning
[06:23] <desrt> hi pitti!
[06:23] <pitti> hey desrt, how are you? In .de already?
[06:24] <desrt> yup.  and because of that, i am feeling particularly great :)
[06:24] <desrt> the long-distance relationship has ended
[06:24] <pitti> ♥
[06:25] <desrt> indeed.
[06:25]  * desrt is stupidly happy
[06:26] <pitti> *hug*, sounds great!
[06:26] <pitti> phone
[07:26] <willcooke> o/
[07:33] <seb128> hey willcooke, starting early today!
[07:41] <pitti> bonjour seb128, hey willcooke! happy Yakkety day!
[07:41] <seb128> hey pitti, happy yakkety day to you as well!
[07:49] <TheMuso> Hey folks.
[07:50] <TheMuso> willcooke: You will be pleased to know that I found what I think is the source of the bluetooth issues that people have been seeing, related to the touch patches. I've asked folks to test on the relevant bugs, and will be preparing SRUs tomorrow all being well...
[07:55] <willcooke> TheMuso, \m/ great stuff
[07:55] <willcooke> seb128, pitti mornig :)
[07:55] <willcooke> Thought I'd check in before taking boy #1 to school
[07:55] <willcooke> Looks like we're on track
[07:56] <seb128> yeah
[08:02] <Laney> HI THARE
[08:02] <pitti> OH HAI Laney!
[08:03] <seb128> hello mr lane
[08:03] <Laney> hey pitti
[08:03] <Laney> hey seb128!
[08:03] <Laney> dnsmasq broke again this morning ;-)
[08:03] <seb128> :-/
[08:03] <Laney> I killed all the instances
[08:03] <Laney> there were some old looking lxd ones
[08:04] <Laney> what-ever-r-r-r-r
[08:04] <Laney> it's release day
[08:04] <Laney> seb128: pitti: how are you?
[08:05] <pitti> Laney: much better, thanks! had a good night's sleep after two really bad ones
[08:05] <Laney> ah good!
[08:05] <Laney> do you know if anythign was causing it?
[08:05] <seb128> good, though feeling like I'm dealing with a start of cold for some days, hope I get over it before it starts being a real one
[08:06] <Laney> /o\
[08:07] <pitti> Laney: brain didn't shut down; but two hours of basketball obviously helped :)
[08:09] <Laney> pitti: excellent
[08:09] <Laney> argh, speaking of brain
[08:09] <Laney> firefox losing its is seriously annoying
[08:09] <Laney> nbs.html TAB TAB TAB WHY
[08:10] <seb128> does it restore it after a restart?
[08:10] <seb128> or is that like you had a crash and the db is corrupted and it deleted it?
[08:10] <Laney> dunno
[08:10] <Laney> is that a thing?
[08:10] <seb128> I had that happening once this year
[08:11] <Laney> I would have to find my keys to get into lastpass again :P
[08:12] <Laney> too annoying
[08:12]  * Laney does it
[08:12] <flexiondotorg> Morning peeps
[08:12] <desrt> morning, all
[08:12] <flexiondotorg> desrt, o/
[08:13] <seb128> hey flexiondotorg, desrt
[08:13] <seb128> desrt, in Europe or just on the t.z?
[08:13] <desrt> here now until christmas
[08:13] <Laney> AH HMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM maybe it's just vimperator that broke
[08:13] <Laney> hey flexiondotorg & desrt
[08:14]  * flexiondotorg gets tea...
[08:16] <Laney> https://github.com/vimperator/vimperator-labs/issues/538
[08:16] <Laney> oho
[08:18] <Laney> yessssssss, winning
[08:18] <Laney> I was reading an article the other day about how too much automation can erode your skills
[08:18]  * Laney coughs
[08:21] <Laney> https://launchpad.net/ubuntu/+source/gnome-software/3.20.1+git20161013.0.d77d6cf-0ubuntu1 ruh roh ;-)
[08:25] <seb128> Laney, build-depends requirement not bumped to the new snapd-glib version I guess
[08:25] <seb128> I was surprised to see those accepted
[08:26] <seb128> we are not respinning right? e.g that's SRU material?
[08:26] <seb128> e.g -> i.e
[08:26] <Laney> there's not even any build-depends
[08:26] <Laney> You don't have to look, I can handle it
[08:26] <Laney> and yes
[08:26] <Laney> sru
[08:27] <seb128> k, thanks
[08:28] <seb128> do you know if we can move the package to main in a SRU?
[08:28] <Laney> checking for SNAP... no -> but it still tried to build the plugin
[08:28] <Laney> yeah
[08:28] <Laney> you can't change it in a frozen suite (release), but proposed -> updates should be cool
[08:30] <seb128> good
[08:30] <davmor2> Laney: have another broncho stop :P
[08:31] <Laney> davmor2: I discovered that they don't go well with tea
[08:31] <davmor2> Laney: hahahaha
[09:19] <willcooke> wheeeee
[09:35] <davmor2> willcooke: you really should use the toilet for that rather than your keyboard
[09:36] <willcooke> It's quicker this way
[09:36] <willcooke> plus all my pop bottles are full
[09:57] <Laney> I saw something weird float to the top of my cup of coffee, but now I can't find it in there
[09:57] <Laney> must have dissolved
[09:57]  * Laney retches
[10:16] <flexiondotorg> My bouncer didn't recover from the netsplit. Just poked it.
[14:18] <hikiko> I forgot the nick again :p
[14:27] <seb128> hey hikiko, how are you?
[14:53] <hikiko> hi seb128
[14:53] <hikiko> I am fine you?
[14:53] <seb128> I'm good thanks
[15:03] <qengho> I uploaded a new $browser snap. Beware that snap "refresh"es break running programs.
[15:03] <willcooke> That's it,
[15:03] <willcooke> the website is updated, so it's real now
[15:03] <willcooke> As a reward take a short holiday
[15:04] <willcooke> did you enjoy it?  Back to work
[15:11] <qengho> We don't have a xdg-utils snap-to-outside bridge, do we?
[15:11] <seb128> we do
[15:11] <qengho> Ooo!
[15:11] <seb128> but it's not installed by default
[15:11] <seb128> snapd-xdg-open
[15:12] <qengho> Awesome. Thanks, seb.
[15:12] <seb128> well that's the host side helper
[15:12] <qengho> Er, oh.
[15:12] <seb128> then the ubuntu-core snap has a /usr/bin/local/xdg-open script
[15:12] <seb128> which sends a dbus message
[15:12] <qengho> Ah!
[15:12] <qengho> Sweet.
[15:12] <seb128> that the helper listen to
[15:13] <seb128> you might have an issue with that directory not being in the standard path though
[15:13] <seb128> that was being discussed on #snappy yesterday
[15:13] <qengho> Right.
[17:01] <Laney> ttfn
[17:01] <Laney> see you in the real world
[17:01] <Laney> whatever that is
[17:03] <Laney> (off tomorrow)
[17:05] <seb128> Laney, have a nice w.e, see you on sunday!
[17:05] <seb128> enjoy the beer festival
[17:05] <seb128> calling it a day as well
[17:05] <seb128> oh and congrats everyone on 16.10!
[17:47] <willcooke> night all - thanks for 16.10
[21:18] <ricotz> 16.10 \o/


[07:32] <dholbach> good morning
[14:55] <dholbach> highvoltage, do you have time to check the schooltool packages today? I won't
[14:55] <dholbach> and if we don't get them in today we will need a FF exception
[14:55] <dholbach> ...which should be easy to get
[15:20] <highvoltage> dholbach: I can make some time for it
[15:20] <dholbach> excellent
[15:20] <highvoltage> dholbach: I looked at the wiki page last night and it seemed pretty much clear, I guess there's been some new uploads since then :)
[15:21] <dholbach> last time I checked the 2 packages were alright, minus a small thing in debian/copyright
[15:21] <dholbach> but it should be good now
[15:22] <highvoltage> ok


[22:16] <Unit193> rbasak: Howdy.  Anything else I should fix, re: ruby-simplecov?
[23:08] <rbasak> Unit193: context please?
[23:09] <Unit193> rbasak: LP 1666988, wondered if there was anything else before I upload a new debdiff with the changelog fixes.
[23:11] <rbasak> Unit193: are you planning to look after the package until it's in sync again please?
[23:12] <rbasak> Unit193: but yeah, I don't see anything else I said not covered by a changelog fix then, thanks.
[23:12] <Unit193> rbasak: I don't know ruby well, I'd expect it to get in sync next cycle again though.  But yeah, certainly.
[23:12] <rbasak> Thanks :)
[23:12] <Unit193> rbasak: You can take a look at ruby-trello for what I'm talking about regarding the issue, though.
[23:13] <rbasak> Look at it how?
[23:13] <Unit193> For example, try building it without this fix.
[23:14] <rbasak> I'd rather believe what you say :)
[23:14] <rbasak> I don't see a ruby-trello package in Ubuntu though?
[23:16] <Unit193> It's not, https://launchpad.net/~unit193/+archive/ubuntu/test/+packages?field.name_filter=ruby&field.status_filter=published&field.series_filter=zesty
[23:21] <Unit193> rbasak: Thanks for taking a look, updated the bug.
[23:26] <rbasak> Unit193: I can take a look tomorrow (UTC working hours) for you. Ping me if I forget please.
[23:26] <Unit193> Sure, thanks.


[08:12] <tsdgeos> Mirv: can you click the ♻ button for unity8 in update_excuses? https://autopkgtest.ubuntu.com/request.cgi?release=zesty&arch=i386&package=unity8&trigger=unity8%2F8.15%2B17.04.20170131.1-0ubuntu1
[08:12] <tsdgeos> the regression there is 99,9999% a flacky test
[08:12] <tsdgeos> since this landing is doing nothing regarding to that test
[08:14] <om26er> duflu: ping
[08:15] <duflu> om26er: pong. I'm working on it :)
[08:15] <duflu> https://bugs.launchpad.net/mir/+bug/1661128
[08:15] <om26er> duflu: great ;)
[08:16] <om26er> Broadwell, in my case.
[08:16] <duflu> om26er: Yeah it's a general problem with nested servers. Just didn't notice because our test servers are an order of magnitude faster than u8
[08:17] <duflu> But I can reproduce it using just Mir now
[08:18] <om26er> duflu: good to know. Hopefully we won't need to revert any new goodies.
[08:19] <duflu> om26er: But the lag is gone :)
[08:41] <Mirv> tsdgeos: opened your link, which was the direct retry url
[08:42] <tsdgeos> Mirv: ah sorry, sil2100 had already clicked it, not sure if that means it's rebuilding again
[08:42] <tsdgeos> i guess it doesn't matter
[08:42] <tsdgeos> seb128: i updated the geonames branch
[08:43] <seb128> tsdgeos, hey, thanks, I'm going to have another look, did you see that the designers discuted it and that matthew commented on the bug?
[08:43] <tsdgeos> yes
[09:26] <duflu> om26er: It was just that bug you were going to ask about, right?
[09:27] <om26er> duflu: yep, had updated mir after reading about the latest improvements somewhere, so thought to give that a try.
[09:27] <duflu> om26er: Manual testing of the fix on zesty is done and working. Just automating testing now and then done


[08:40] <joelkraehemann_> https://bugs.launchpad.net/bugs/1762143
[13:41] <joelkraehemann> http://autopkgtest.ubuntu.com/packages/gsequencer/bionic/s390x
[13:41] <joelkraehemann> ^^ it passes, now.
[18:49] <joelkraehemann> Why is it building against libinstpatch-1.0.0-6 instead of libinstpatch-1.0.0-7?
[18:49] <joelkraehemann> http://autopkgtest.ubuntu.com/packages/gsequencer/bionic/s390x
[23:05] <nacc> slangasek: figured out the issue with cryptsetup -- it's not a bug in git-ubuntu itself, pristine-tar (via gbp-import-orig) is not able to integrate the ubuntu tarball
[23:06] <nacc> my guess is a non-standard xz flag


[02:24] <nhaines> Well, the OCLUG talk went well.  But the sponsor never showed so no one could get into the classroom.  Everyone was lined up in the hallway when I got there.
[02:24] <nhaines> Fortunately, someone brought a monitor to troubleshoot his laptop, so I plugged it into my desktop computer and did the presentation that way.
[02:24] <nhaines> I started off with "Sorry I'm late, I got held up at the bank.  I'm talking about Unity today and I had to make sure my check from Canonical cleared."
[02:51] <jbermudes> hahaha
[02:52] <jbermudes> and next time you can say "sorry I'm late, after reviewing unity for my talk I decided that perhaps it's time to test other distros and lost track of time" :P
[03:36] <nhaines> jbermudes: haha
[03:36] <nhaines> I was suprised... no negative comments about Unity during the talk.  Everyone seems to think it has potential, even if they don't want to use it themselves.
[03:37] <jbermudes> yeah, it'll be interesting to see what it will become regardless of what kinks it might currently have
[03:38] <jbermudes> If anything they should at least be appreciated for trying something new
[03:40] <philipballew> nhaines, Do you use unity?
[03:51] <nhaines> philipballew: yup.
[03:51] <philipballew> nhaines, me as well. I like it a lot
[03:52] <nhaines> I said as much in the talk: I thought I'd use it for 2 weeks, learn it real well so I could answer questions, and then go back go GNOME2 Desktop and never worry about it again, but I found that I really liked it.
[03:53] <philipballew> I see that staying with gnome 2 is something that is not possible in many ways. Its a dead project in most respects
[03:53] <philipballew> but just a thought
[03:54] <nhaines> Well, this was in March.
[03:56] <philipballew> Ah yes. Unity has come a long way since then to
[04:25] <akk> Anybody submitted to SCALE (or know about their system)? Is there a way to get line/paragraph breaks in talk proposals?
[04:26] <akk> There are instructions at the top of the page saying to use <!--break--> but that just shows up verbatim if I preview.
[06:06] <jtatum> +++ATH0
[06:07] <Faqtotum> OK
[06:11] <jtatum> ATZ
[06:11] <seidos> no carrier
[06:15] <MarkDude> TWIT studios rocked. Good bbq. Got to Meet John Dvorak and Veronica Belmont- yay
[06:15] <jtatum> neat
[06:16]  * MarkDude thanked Tom Merit for talking about Linux
[06:16] <jtatum> i like dvorak's early work :) (speaking of modems) i read his pc guide to telecommunication cover to cover. and i liked the column he did on the back page of.. pc computing or something
[06:16] <MarkDude> He is EXACTLY like you think he would be
[06:17] <MarkDude> Persnickety
[06:17] <jtatum> hm, is that good thing? :)
[06:17] <jtatum> ah
[06:17] <MarkDude> Well sure, he sorta just plays himself in real life
[06:18] <MarkDude> VEry funny, even more so - when they are not doing recorded show
[06:20] <MarkDude> The studio is great, I would say geeks should go
[06:20] <MarkDude> well even non geeks would have fun
[22:25] <philipballew_> how hard is it to make a custom live cd with only the apps I see that I want
[22:34]  * philipballew_ hugs seidos
[22:35] <MarkDude> hello there seidos
[22:36]  * MarkDude hopes I will be able to see you at Scale
[22:36] <MarkDude> And ALL of you folsk in this channel there too
[22:37] <broder> philipballew_: it's not impossible. https://help.ubuntu.com/community/LiveCDCustomization
[22:42] <philipballew_> broder, thanks. I am contemplating what is better. that mathod or installing from scratch and making a live image from my harddrive
[22:43] <broder> philipballew_: if you're going to do that, you might want to look into live-build. it knows everything needed to build an ubuntu image, and should be customizable...let me see if i can find the docs on how
[22:46] <philipballew_> alright, broder its for work. Im making lubuntu images for computers to donate to Africa :)
[22:48] <seidos> hi everybody
[22:48] <broder> philipballew_: grr. the docs used to be at http://live.debian.net/manual/en/html/managing-a-configuration.html but that's throwing a 404 at the moment
[23:16] <philipballew_> broder, crazy debian. Its all good, I can look into it in a day or two


[00:37] <hallyn> pmatulis: yeah
[00:38] <hallyn> pmatulis: for now i guess i'm ok just running it in a lightweight vnc.  But it doesn't seem like I should have to.  Tried under my own dbus session launched from python, but that wasn't enough :)
[00:44] <tntc> yikes. my scrollback isn't long enough
[02:02] <pmatulis> hallyn: install ubuntuone-client (ubuntuone-syncdaemon) and away you go?
[02:20] <pmatulis> hallyn: actually, i'm not sure how to authenticate on a non-graphical system.  anyone?
[02:21] <maskedmakrel> Hello.  ubuntuone is flooding my router somehow and disrupting my network.
[02:22] <maskedmakrel> I tried uninstalling it under UNR 10.10 but it is still happening.
[02:22] <maskedmakrel> I uninstalled under the software manager.
[02:22] <maskedmakrel> Any suggestions as to how to get ubuntuone under control?
[02:25] <maskedmakrel> Any suggestions as to how to get ubuntu one off of UNR 10.10 completely?
[02:26] <maskedmakrel> Or do I just reinstall everything for the hundredth time...
[16:00] <hallyn> all right, so now i'm becoming pretty sure tht it's ubuntuone that is making my laptop (natty with 8G) frequently hang.
[16:01] <hallyn> in the past i had thought it was the video card, bc if i didn't log in (except remotely) it didn't hang.  But when I log in, it hangs within 24 hours
[16:01] <hallyn> but i finally just started a vnc session to start ubuntu one to make the files sync, and it hung again last night
[16:01] <hallyn> there's nothing interesting in the logs so i don't know how to report this
[16:15] <hallyn> don't suppose it's possible to just rsync to ubuntu one?


[00:04] <barry> rockstar: thanks for the comments.  i feel the same way, but i wanted to explore this option.
[00:05] <rockstar> barry, yea, exploring this is pretty cheap, so we should see all the options.
[00:07] <maxb> mwhudson: Hi
[00:07] <mwhudson> rockstar: how much work is involved in getting some bug-status like love for merge proposal status?
[00:07] <mwhudson> rockstar: (just curious, really)
[00:07] <mwhudson> maxb: hello
[00:08] <mwhudson> maxb: i wonder why i was pinging you :-)
[00:08] <maxb> :-)
[00:08] <mwhudson> oh right, that was it
[00:08] <rockstar> mwhudson, thumper's working on it, and I was told not to do it for him.  :)
[00:09] <mwhudson> maxb: i think it would be a good thing to copy a few packages from karmic to the ~launchpad ppa (python-launchpadlib & dependencies) and have launchpad-developer-dependencies depend on them
[00:09] <mwhudson> maxb: does that sound sane?
[00:09] <mwhudson> i've just installed a bunch of karmic packages on jaunty, seems to be working, dunno about hardy...
[00:09] <mwhudson> rockstar: heh heh
[00:10] <maxb> hm. What are they needed for?
[00:10] <wgrant> That doesn't sound like a good idea.
[00:11] <wgrant> Won't it just break everything on the other releases with the lazr.* setuptools mess?
[00:11] <rockstar> mwhudson, I know he's got the branch status stuff in review right now, and that deryck has reviewed it.
[00:11] <mwhudson> maxb: 'ec2 land' does stuff with launchpadlib and can't use the eggs we have because launchpad is still stuck on 2.4
[00:11] <mwhudson> maybe the real fix is to get launchpad on 2.5 asap
[00:11] <rockstar> maxb, mwhudson, wgrant, I might point out that it's been a habit that l-d-d tends to break in awkward ways every time we switch versions.
[00:12] <mwhudson> barry: hello
[00:12] <mwhudson> barry: Launchpad.  Python 2.5.  know what's going on there?
[00:12] <rockstar> mwhudson, I think gary was working on that.
[00:12]  * wgrant thought maxb was.
[00:12] <maxb> mwhudson: erm "can't use the eggs we have" - hmm?
[00:12] <wgrant> Current 2.5 test failures are at https://dev.launchpad.net/LaunchpadOnKarmic
[00:12] <rockstar> Although it seems like gary is working on a lot of things, which may explain why it's slow going.
[00:13] <mwhudson> wgrant: oh that's a very useful page :)
[00:14] <maxb> rockstar: um, you can point that out, but what does that mean for the current discussion?
[00:14] <mwhudson> maxb: well, can't us /bin/py at least, because boto depends on python 2.5
[00:14] <barry> mwhudson: hi.  i don't.  i'd love to help this along
[00:14] <barry> mwhudson: /me -> dinner
[00:14] <maxb> mwhudson: ah, ok- that makes sense
[00:15] <maxb> Status of LP on Python 2.5 is that people, me included, need to work on whittling the list on LaunchpadOnKarmic
[00:16] <maxb> If 'ec2 land' requires a system-python launchpadlib newer than available in older ubuntus, normally I would be all for a backport.
[00:16] <rockstar> maxb, LaunchpadOnKarmic is a misleading name, since I'm running Launchpad on Karmic right now.
[00:16] <maxb> However, the namespace package mess is a major blocker
[00:16] <maxb> You are right, the wiki page is now poorly named.
[00:16] <maxb> When I started it, I assumed that 2.4 on karmic was not a possibility
[00:17] <rockstar> maxb, I point this out in saying that we did this exact same thing with this same package on the Intrepid->Jaunty jump that caused breakages, but we weren't too concerned since it worked for Launchpad.
[00:17] <maxb> huh? 'exact same thing'
[00:17] <maxb> ?
[00:18]  * mwhudson lunches
[02:19] <mwhudson> wgrant: i think i have just thumped into the "setuptools lazr namespace package" issue
[02:19] <mwhudson> wgrant: do you know a workaround?
[02:20] <mwhudson> oh, i think there's one on that handy wiki page
[02:28] <mwhudson> oh man W T F
[02:28] <mwhudson> apache is broken on my machine because fricking WINDMILL chokes on import if $PATH isn't set
[02:29] <mwhudson> well not broken, but unhappy
[02:30] <wgrant> mwhudson: I don't have any real breakage from the lazr setuptools issue.
[02:30] <wgrant> Apart from a few tests.
[02:30] <mwhudson> wgrant: i didn't have lazr.enum installed system wide
[02:31] <mwhudson> which seemed to break scripts/mirror-branch.py rather thoroughly
[02:32] <wgrant> mwhudson: Yep, codehosting script tests are broken.
[02:32] <wgrant> Fortunately I haven't had cause to touch codehosting much lately.
[02:32]  * wgrant lunches.
[03:26] <mwhudson> thumper: come back, it's too quiet here
[03:29] <MTecknology> You should all feel sorry for me..
[03:29] <MTecknology> I'm about to make a sync from Launchpad to Drupal...
[03:29] <MTecknology> for 4 projects
[03:36] <wgrant> This side of the world is rapidly running out of LP engineers.
[03:39] <MTecknology> wgrant: I'll be trying to do some LP dev pretty soon
[03:41] <wgrant> MTecknology: You are not on my side of the world!
[03:42] <MTecknology> wgrant: I could be
[03:46] <MTecknology> more and more, cvs irks me
[03:47] <MTecknology> I know I made changes - but cvs won't listen
[05:38] <mwhudson> hmm
[05:38] <mwhudson> make build is failing on the python2.5 branch
[06:02]  * mwhudson EOWs
[06:17] <al-maisan> Good morning!
[06:23] <mwhudson> hello al-maisan
[06:24] <al-maisan> hello mwhudson :)
[08:27] <adeuring> good morning
[08:51] <thumper> morning
[08:51] <thumper> mwhudson: back soon :)
[08:52] <wgrant> How is the team lead thingy going?
[09:04] <thumper> wgrant: interestingly
[09:05] <thumper> wgrant: there'll be some email sent to the dev list at the end of today I expect
[09:05] <mrevell> Morning
[09:06] <thumper> mrevell: morning
[09:54] <henninge> Hi, I found out that I can do this to use a TAL formatter in view code: http://paste.ubuntu.com/283641/
[09:55] <henninge> Is that a "legal" use of the API or should I access the formatter in some other way?
[09:55] <henninge> jtv: ^?
[09:56] <jtv> henninge: all I can say is it's clever and simple.  :)
[09:56] <henninge> jtv: thanks ;) So you'd let that through on a review? I guess that is what I am asking ...
[09:57] <jtv> henninge: curtis is the real person to ask imho
[09:57] <jtv> but I would allow that, yes.
[09:57] <henninge> jtv: oh, and he's in our time zone atm ... ;)
[09:57] <jtv> or close to it
[09:58] <henninge> sinzui: Hi! Is it OK to do this in a view? http://paste.ubuntu.com/283641/
[10:29] <bigjools> wgrant: hey there - did you ever get anywhere with the download counters for PPAs?
[10:30] <wgrant> bigjools: The refactoring of the existing log parser is done, so the PPA backend is very very easy.
[10:30] <wgrant> But it needed discussion, so I decided to wait until post-3.0.
[10:30] <wgrant> (the refactoring is done and merged, that is)
[10:30] <bigjools> awesome
[10:31] <bigjools> we'd like it to work with the partner archive too :)
[10:32] <wgrant> So I saw.
[10:37] <al-maisan> hello code hosting guys :)
[10:37] <al-maisan> diffs in merge proposals seem to be off quite a bit
[10:37] <al-maisan> see e.g. https://code.edge.launchpad.net/~al-maisan/launchpad/cmsg-425800/+merge/12774
[10:37] <al-maisan> and http://pastebin.com/m4c94727b
[10:37] <sinzui> henninge: sorry I am sprinting. I think your pastebin, if fine. I have used tales in code several times.
[10:38] <henninge> sinzui: I am aware of you sprinting ... ;) Thanks for taking the time to look at my pastebin.
[10:38] <noodles775> al-maisan, you're aware that you've targeted db-devel there?
[10:39] <al-maisan> noodles775: oops, my fault then.
[10:40] <al-maisan> I apologise to the code hosting guys ;P
[10:40] <noodles775> al-maisan, I've done that too... start a branch when devel is closed and forget later :)
[10:40]  * al-maisan needs some coffee
[10:40] <al-maisan> bbiab
[10:55] <wgrant> bigjools: My quick PPA BPR counter implementation from several weeks ago is only about 300 lines of diff.
[10:58] <noodles775> wgrant or bigjools: could one of you take a look at my comments at the bottom of https://answers.edge.launchpad.net/launchpad/+question/84457 ?
[10:58] <noodles775> I'm confused why the Packages file would be empty rather than simply containing the previous versions?
[11:00] <wgrant> Lessee.
[11:02] <wgrant> Hmm.
[11:02] <wgrant> That is a good question.
[11:03] <wgrant> Hm.
[11:03] <wgrant> Looks like it never built on Hardy.
[11:04] <wgrant> I can't find a successful Hardy build (they're all superseded), while the rest are fine.
[11:04] <wgrant> I presume it keeps depwaiting.
[11:04] <wgrant> We'll see in a minute or two.
[11:05] <noodles775> wgrant, https://launchpad.net/~inkscape-nightly/+archive/ppa/+build/841006
[11:05] <noodles775> (and thanks for taking a look)
[11:07] <wgrant> noodles775: Ah.
[11:07] <wgrant> So it did succeed months ago.
[11:07] <wgrant> But.
[11:07] <wgrant> It was deleted.
[11:07] <wgrant> 0.46+devel~nightly8.04-7213-1 was the last success.
[11:07] <wgrant> The subsequent upload failed.
[11:07] <wgrant> Both were deleted.
[11:07] <wgrant> So the binaries vanished.
[11:08] <wgrant> No later upload succeeded, so there are still no binaries.
[11:08] <noodles775> Ah - great.... thanks wgrant .
[11:10] <wgrant> The DASBP views make that pretty easy to see, but it's rather more convoluted for a PPA.
[11:10] <noodles775> Yeah.
[14:11] <barry> noodles775: hi!  would you be able to do a quick ui review of some screen shots?
[14:13] <noodles775> barry, sure - if it gives me a break from CHR project reviewing :)
[14:13] <barry> noodles775: :)
[14:13] <barry> noodles775: can you take a look at the last two screen shots in bug 440220
[14:13] <mup> Bug #440220: registering slot interferes with watermark <post-ui-3-cleanup> <Launchpad Registry:In Progress by barry> <https://launchpad.net/bugs/440220>
[14:14] <noodles775> looking
[15:16] <EdwinGrubbs> lifeless: ping
[15:17] <EdwinGrubbs> beuno: ping
[15:18] <beuno> EdwinGrubbs, hi
[15:18] <beuno> jml, http://paste.ubuntu.com/283879/
[15:25] <EdwinGrubbs> beuno: can you give me your feedback on the mockups in bug 399554
[15:25] <mup> Bug #399554: timeline series data is very hard to access <post-3-ui-cleanup> <ui> <Launchpad Registry:In Progress by edwin-grubbs> <https://launchpad.net/bugs/399554>
[15:27] <beuno> let me try
[15:29] <beuno> EdwinGrubbs, it's nice
[15:29] <beuno> it's a good idea
[15:29] <beuno> although removing the dates is... well, I don't know
[15:33] <jml> beuno, thanks. as discussed, mainline commits are more interesting.
[15:34] <beuno> "patches welcome", I hear
[15:36] <EdwinGrubbs> beuno: statik had the idea of just hiding the dates when the graph is in a portlet. I could also do something where depending on your zoom level it would hide/show the dates, or I could add a checkbox next to the zoom buttons.
[15:37] <beuno> EdwinGrubbs, ah, could be a good idea
[15:37] <beuno> EdwinGrubbs, lets have a call next week about it
[15:37] <beuno> would that work for you?
[15:41] <EdwinGrubbs> beuno: sure. I'll set that up after I get some feedback from lifeless.
[15:41] <beuno> EdwinGrubbs, great, thanks
[15:54] <thumper> can anyone swap CHR with me for the 7th?
[16:03] <mrevell> thumper: I'm down for the 14th. Do you wanna take that and I'll take your 7th?
[16:03] <thumper> mrevell: sounds great, thanks
[16:03] <mrevell> thumper: I'll update the calendar
[16:04] <thumper> mrevell: ta
[17:13] <mrevell> Hmm, I'm getting a traceback on ec2 test today but it was fine yesterday. Anyone else seen that?
[17:26] <gmb> Argh. Why am I getting "AttributeError: 'thread._local' object has no attribute 'interaction'"?
[23:00] <lifeless> EdwinGrubbs: yo?
[23:01] <EdwinGrubbs> lifeless: hi, did you see the mockups in the bug you opened
[23:02] <lifeless> EdwinGrubbs: hi, yes been thinking
[23:02] <lifeless> EdwinGrubbs: I think they are better
[23:10] <EdwinGrubbs> lifeless: The main differences between the mockups and the old textual display of series/milestones/releases are that the graph doesn't wrap milestones/releases in large series and that it limits both the height and width of the displayed data.
[23:11] <EdwinGrubbs> lifeless: it might improve the usability of the graph it was possible to optionally hide/display milestones and releases based on what you interested in.
[23:17] <kiko> ahoy there
[23:17] <kiko> it's KARMIC UPGRADE day
[23:17] <kiko> wooo
[23:18]  * wgrant quickly uploads some change to break kiko's machine.
[23:18] <kiko> somebody already did that
[23:18] <wgrant> :(
[23:18] <kiko> maybe you could upload a fix though!
[23:19] <kiko> what's with the splash screen coming after all the boot messages
[23:19] <wgrant> It's probably because it has to wait for KMS to initialise. Keybuk was working on that sort of thing, and it's a lot better than it was a month ago.
[23:20] <wgrant> I presume it will get quieter before release.
[23:20] <james_w> you get all boot messages?
[23:20] <james_w> or just some apparmor/modprobe/fsck stuff
[23:20] <james_w> and then a few "starting" messages?
[23:20] <Fly-Man-> Hooray, Karmic is here
[23:21] <wgrant> Maybe I misunderstood the full magnitude of the issue. I just get a few lines at the start.
[23:25] <kiko> james_w: I only get like 10 lines after some 2 screen flashes, but it kinda upsets the smooth experience
[23:25] <kiko> james_w: starting with fsck and then some other stuff
[23:25] <james_w> yeah
[23:25] <kiko> the boot is so fast
[23:25] <james_w> I think true smoothness will be next release
[23:25] <kiko> that having the flash and switch just steals victory
[23:26] <james_w> I think there's work to do to quieten things down without giving no information when the boot fails
[23:30] <kiko> sure, but the boot doesn't fail for me!


[10:55] <kelemengabor> hi dpm, got a minute?
[10:55] <dpm> hi kelemengabor, sure
[10:56] <kelemengabor> I'm looking at the UDS schedule - there is nothing on i18n/l10n, or is it just me?
[10:57] <dpm> kelemengabor, there isn't anything on it, no, as this time round I'm leading the app dev track. However, if there are people interested in translations sessions I'll organize a roundtable
[10:58] <dpm> I should probably do it anyway, as we need to discuss who'll take care of the i18n infrastructure for language packs, now that pitti has moved from the desktop team to QA
[10:59] <kelemengabor> that would be a good start... I'm still going to go there to talk about i18n :)
[11:00] <kelemengabor> do we, for example, have langpack update schedule? Someone asked yesterday and I could not cound any.
[11:00] <kelemengabor> this could be a topic for a "sustainable translations" session
[11:01] <dpm> kelemengabor, no we don't have a schedule yet - I put up a skeleton page for 12.10 the other day, but it's just a copy of 12.04 for now: https://wiki.ubuntu.com/Translations/ReleaseSchedule
[11:01] <dpm> kelemengabor, will you be there in person?
[11:01] <kelemengabor> yes!
[11:01] <dpm> ah, awesome!
[11:02] <dpm> you got sponsored?
[11:02] <kelemengabor> do you know about other localizers going?
[11:02] <kelemengabor> yes
[11:02]  * dpm didn't look at the sponsored attendees list this time round
[11:02] <dpm> I don't know of any, I wasn't involved in sponsoring this time around
[11:02] <dpm> let me just send an e-mail to the translators list
[11:03] <kelemengabor> thanks
[11:04] <kelemengabor> I saw Sergio Zanchetta in the CC list of the sponsorship mails, but not others
[14:54] <dpm> trijntje, good work with the translations session :)


[01:55] <ibeardslee> interesting .. it seems that the 3 main ubuntu mirrors in NZ (plus the one at work) are giving me very similar results in pings and mtr
[01:56] <ibeardslee> certainly not taking the overseas trip to get back to nz.archive.ubuntu.com
[01:56] <ibeardslee> will do a check again tonight though
[02:01] <G> ibeardslee: iirc nz.archive.ubuntu.com (citylink as I recall) offload requests from ISPs that don't peer locally to SFO, what is the 'this-node-???' file in the directory listing?
[02:03] <G> (if I remember rightly the rationale was it's cheaper that way to provide a free service, and chances are ISPs that didn't peer well would still be travelling overseas to get back, so what is the point
[02:04] <ibeardslee> well looking at my previous tests in Nov 2010, I was getting 150ms pings to nz.auc with 14 hops
[02:04] <ibeardslee> now it's 9 hops with a 23ms ping
[02:05] <ibeardslee> .. actually take two hops of each those, that includes my internal network ;)
[02:05] <G> ibeardslee: have you tried ucmirror?
[02:05] <G> http://ucmirror.canterbury.ac.nz
[02:05] <ibeardslee> yes
[02:06] <G> it's actually a bit crazy, but even in Auckland I've found UC to be the most reliable mirror
[02:06] <ibeardslee> snap are introducing lost packet
[02:06] <G> (in terms of speed, stability and up to date-ness)
[02:07] <ibeardslee> but pings times are better
[02:13] <olly> it's handy they offload requests if you go overseas and don't update the mirror you use!
[02:13] <G> oh yeah, I'd certainly agree with that
[02:13] <olly> ping isn't always totally indicative of what performance you'll actually get
[02:14] <olly> especially as ping packets may be dropped in favour of other packets by some routers
[02:14] <ibeardslee> not totally, but a good indication that a connection is likely to be slow, have latency
[02:15] <ibeardslee> hmmm
[02:15] <olly> for a mirror, throughput tends to matter more than latency
[02:15] <olly> it's not a great sign if there's packet loss with ping though
[17:58] <olly> morning
[18:49]  * olly frees over 1GB by purging old kernels
[19:57] <ibeardslee> morning
[20:04] <snail> nice. they're testing the fire alarms today. It's now been running for 40 minutes and my earplugs are starting to itch
[20:41] <ajmitch> morning
[21:41] <chilts> morning
[21:44] <thumper> morning
[21:48] <snail> is there anyone in new zealand who does regular or semi regular linux training?
[22:15] <hads> morning
[22:21] <snail> the definition of stability: the package's news page still has their y2k compliance statement
[23:32] <G> snail: only ones I really know of are Auldhouse and iirc they mainly focus on the Red Hat Curriculum
[23:34] <G> (so I'd imagine not much help/doesn't really fit in)


[17:22] <nady> יש מישהו
[17:35] <nady> ?
[18:25] <lousygarua> nady, now there is
[18:33] <blackred> yea sure
[19:28] <lousygarua> blackred, state your name and your ubuntu happiness rate
[19:30] <blackred> ha?
[19:30] <lousygarua> blackred, just haven't seen you here before, would like to get to know the ubuntuers around better
[19:31] <blackred> lol ok..
[19:31] <blackred> amm happiness rate? around 7
[19:32] <lousygarua> are you "blackred" on the forums too?
[19:32] <lousygarua> how long have you been using ubuntu?
[19:34] <blackred> no. and just recently. i used fedora and open SUSE before.
[19:36] <blackred> and you?
[19:49] <lousygarua> i've been ubuntuing since 2006
[19:49] <lousygarua> never used anything else serisouly
[19:49] <lousygarua> just installed fedora on a virtualbox to play around a little and can't get the guest additions to work
[19:51] <blackred> i didn't touch it for some tine
[19:51] <blackred> i'm working with the win mostly i'm afraid, but i needed to learn linux again lately and ubuntu have better guids on the net
[19:52] <blackred> i'm wandering why am i writing in english