[00:28] -queuebot:#ubuntu-release- New binary: suitesparse [amd64] (mantic-proposed/main) [1:7.1.0+dfsg-2] (ubuntu-desktop)
[00:28] -queuebot:#ubuntu-release- New binary: suitesparse [ppc64el] (mantic-proposed/main) [1:7.1.0+dfsg-2] (ubuntu-desktop)
[00:30] -queuebot:#ubuntu-release- New binary: suitesparse [arm64] (mantic-proposed/main) [1:7.1.0+dfsg-2] (ubuntu-desktop)
[00:31] -queuebot:#ubuntu-release- New binary: suitesparse [armhf] (mantic-proposed/main) [1:7.1.0+dfsg-2] (ubuntu-desktop)
[00:31] -queuebot:#ubuntu-release- New binary: suitesparse [s390x] (mantic-proposed/main) [1:7.1.0+dfsg-2] (ubuntu-desktop)
[01:55] -queuebot:#ubuntu-release- New binary: suitesparse [riscv64] (mantic-proposed/main) [1:7.1.0+dfsg-2] (ubuntu-desktop)
[03:44] -queuebot:#ubuntu-release- New binary: gnuradio [riscv64] (mantic-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[04:36] -queuebot:#ubuntu-release- New: accepted gnuradio [amd64] (mantic-proposed) [<IP_ADDRESS>-1]
[04:36] -queuebot:#ubuntu-release- New: accepted gnuradio [armhf] (mantic-proposed) [<IP_ADDRESS>-1]
[04:36] -queuebot:#ubuntu-release- New: accepted gnuradio [riscv64] (mantic-proposed) [<IP_ADDRESS>-1]
[04:36] -queuebot:#ubuntu-release- New: accepted node-blueprintjs [amd64] (mantic-proposed) [4.17.8~git20230417213433.6dab069+ds1-3]
[04:36] -queuebot:#ubuntu-release- New: accepted gnuradio [arm64] (mantic-proposed) [<IP_ADDRESS>-1]
[04:36] -queuebot:#ubuntu-release- New: accepted gnuradio [s390x] (mantic-proposed) [<IP_ADDRESS>-1]
[04:36] -queuebot:#ubuntu-release- New: accepted gnuradio [ppc64el] (mantic-proposed) [<IP_ADDRESS>-1]
[04:36] -queuebot:#ubuntu-release- New: accepted rust-tracing-appender [riscv64] (mantic-proposed) [0.2.2-1]
[04:36] -queuebot:#ubuntu-release- New: accepted suitesparse [amd64] (mantic-proposed) [1:7.1.0+dfsg-2]
[04:36] -queuebot:#ubuntu-release- New: accepted suitesparse [armhf] (mantic-proposed) [1:7.1.0+dfsg-2]
[04:36] -queuebot:#ubuntu-release- New: accepted suitesparse [riscv64] (mantic-proposed) [1:7.1.0+dfsg-2]
[04:36] -queuebot:#ubuntu-release- New: accepted suitesparse [arm64] (mantic-proposed) [1:7.1.0+dfsg-2]
[04:36] -queuebot:#ubuntu-release- New: accepted suitesparse [s390x] (mantic-proposed) [1:7.1.0+dfsg-2]
[04:36] -queuebot:#ubuntu-release- New: accepted suitesparse [ppc64el] (mantic-proposed) [1:7.1.0+dfsg-2]
[05:07] <LocutusOfBorg> hello, apparmor in release looks badly interacting with armhf containers,
[05:07] <LocutusOfBorg><EMAIL_ADDRESS>[05:07] <LocutusOfBorg> 164s apparmor_parser: Unable to replace "lsb_release".  Permission denied; attempted to load a profile while confined?
[05:08] <LocutusOfBorg> and then fails the find of how many cpus we have
[05:08] <LocutusOfBorg> why is it installed?
[05:32] <amurray> ive seen this before as well but in this case I suspect it is a red-herring - even on successful runs the same apparmor errors are seen
[05:35] <amurray> i am going to speculate this is due to armhf runners running under lxc whereas for say amd64 they run directly in an openstack vm from what i can see
[05:35] <amurray> s/amd64/arm64/
[05:53] <LocutusOfBorg> in successful runs apparmor is not installed?
[05:53] <LocutusOfBorg> doing cat on cpuinfo works, grep doesn't ... this is strange
[05:53] <LocutusOfBorg> I want to run strace
[05:58] <amurray> apparmor has nothing to do with this failure from what I can see - ie<EMAIL_ADDRESS>is a successful run which also shows the same apparmor related "errors"
[06:01] <LocutusOfBorg> that one might be a lie...
[06:01] <LocutusOfBorg> I did make -j${cpus} || make
[06:01] <LocutusOfBorg> but yes, it should have printed the error and then started again make
[06:01] <LocutusOfBorg> so my first guess is that you are right, but in any case I was scared by that apparmor failure
[08:08] <ricotz> hello, is someone looking into autopkgtests restarting/looping on amd64?
[09:13] <LocutusOfBorg> vorlon, FYI I stole debootstrap merge
[09:14] <LocutusOfBorg> there was a lot of "debian/debootstrap-udev" autogenerated stuff in ubuntu merge
[10:27] <LocutusOfBorg><EMAIL_ADDRESS>[10:27] <LocutusOfBorg> even more strange
[10:27] <LocutusOfBorg> ginggs, ^^
[10:32] <ginggs> LocutusOfBorg: is it flaky now?  does it sometimes work and sometimes not?
[10:38] <LocutusOfBorg> I did just add some debugging code
[10:38] <LocutusOfBorg> like echo "$ncpu" add set -x to script
[10:38] <LocutusOfBorg> and cat /proc/cpuinfo
[10:38] <LocutusOfBorg> meh
[10:40] <ginggs> ricotz: yes, the issue is known, see  https://discourse.ubuntu.com/t/autopkgtest-service/34490
[10:41] -queuebot:#ubuntu-release- New binary: codec2 [amd64] (mantic-proposed/universe) [1.1.1-5ubuntu1] (i386-whitelist, kubuntu)
[10:43] -queuebot:#ubuntu-release- New binary: codec2 [s390x] (mantic-proposed/universe) [1.1.1-5ubuntu1] (i386-whitelist, kubuntu)
[10:43] -queuebot:#ubuntu-release- New binary: codec2 [arm64] (mantic-proposed/universe) [1.1.1-5ubuntu1] (i386-whitelist, kubuntu)
[10:48] <ricotz> ginggs, thanks, I don't have the credentials to see the RT progress
[11:12] -queuebot:#ubuntu-release- New binary: codec2 [armhf] (mantic-proposed/universe) [1.1.1-5ubuntu1] (i386-whitelist, kubuntu)
[11:13] -queuebot:#ubuntu-release- New binary: hunspell [amd64] (mantic-proposed/main) [1.7.2+really1.7.2-10] (desktop-core, i386-whitelist)
[11:19] -queuebot:#ubuntu-release- New binary: codec2 [i386] (mantic-proposed/universe) [1.1.1-5ubuntu2] (i386-whitelist, kubuntu)
[11:24] <ginggs> ricotz: yeah, but at least you can see there Ubuntu QA are aware of it
[11:26] <ginggs> LocutusOfBorg: cat /proc/cpuinfo seems to be flaky on armhf, see results from 2023-07-17 at https://autopkgtest.ubuntu.com/packages/r-cran-parallelmap/mantic/armhf
[11:38] -queuebot:#ubuntu-release- New binary: codec2 [armhf] (mantic-proposed/universe) [1.1.1-5ubuntu2] (i386-whitelist, kubuntu)
[11:47] -queuebot:#ubuntu-release- New binary: codec2 [amd64] (mantic-proposed/universe) [1.1.1-5ubuntu2] (i386-whitelist, kubuntu)
[11:48] -queuebot:#ubuntu-release- New binary: codec2 [ppc64el] (mantic-proposed/universe) [1.1.1-5ubuntu2] (i386-whitelist, kubuntu)
[11:48] -queuebot:#ubuntu-release- New binary: codec2 [arm64] (mantic-proposed/universe) [1.1.1-5ubuntu2] (i386-whitelist, kubuntu)
[12:00] -queuebot:#ubuntu-release- New binary: codec2 [s390x] (mantic-proposed/universe) [1.1.1-5ubuntu2] (i386-whitelist, kubuntu)
[13:38] <schopin> bdmurray: re the glibc vs linux Jammy autopkgtests, the libunwind tests that passed used a different version of the kernel than those you and I triggered for glibc. A subsequent libunwind test hit the same error.
[13:48] -queuebot:#ubuntu-release- Unapproved: mutter (jammy-proposed/main) [42.9-0ubuntu3 => 42.9-0ubuntu4] (desktop-core, desktop-extra)
[14:04] -queuebot:#ubuntu-release- New: accepted codec2 [amd64] (mantic-proposed) [1.1.1-5ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted codec2 [armhf] (mantic-proposed) [1.1.1-5ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted codec2 [amd64] (mantic-proposed) [1.1.1-5ubuntu2]
[14:04] -queuebot:#ubuntu-release- New: accepted codec2 [armhf] (mantic-proposed) [1.1.1-5ubuntu2]
[14:04] -queuebot:#ubuntu-release- New: accepted codec2 [ppc64el] (mantic-proposed) [1.1.1-5ubuntu2]
[14:04] -queuebot:#ubuntu-release- New: accepted hunspell [amd64] (mantic-proposed) [1.7.2+really1.7.2-10]
[14:04] -queuebot:#ubuntu-release- New: accepted codec2 [arm64] (mantic-proposed) [1.1.1-5ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted codec2 [arm64] (mantic-proposed) [1.1.1-5ubuntu2]
[14:04] -queuebot:#ubuntu-release- New: accepted codec2 [s390x] (mantic-proposed) [1.1.1-5ubuntu2]
[14:04] -queuebot:#ubuntu-release- New: accepted codec2 [s390x] (mantic-proposed) [1.1.1-5ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted codec2 [i386] (mantic-proposed) [1.1.1-5ubuntu2]
[14:22] -queuebot:#ubuntu-release- New binary: codec2 [riscv64] (mantic-proposed/universe) [1.1.1-5ubuntu2] (i386-whitelist, kubuntu)
[14:26] -queuebot:#ubuntu-release- New: accepted codec2 [riscv64] (mantic-proposed) [1.1.1-5ubuntu2]
[14:57] -queuebot:#ubuntu-release- Unapproved: ufw (jammy-proposed/main) [0.36.1-4build1 => 0.36.1-4ubuntu0.1] (core)
[15:05] -queuebot:#ubuntu-release- Unapproved: ufw (focal-proposed/main) [0.36-6ubuntu1 => 0.36-6ubuntu1.1] (core)
[15:07] -queuebot:#ubuntu-release- New binary: rust-ab-glyph [amd64] (mantic-proposed/universe) [0.2.21-2] (no packageset)
[15:08] -queuebot:#ubuntu-release- New binary: rust-ab-glyph [arm64] (mantic-proposed/universe) [0.2.21-2] (no packageset)
[15:08] -queuebot:#ubuntu-release- New binary: rust-ab-glyph [ppc64el] (mantic-proposed/universe) [0.2.21-2] (no packageset)
[15:08] -queuebot:#ubuntu-release- New binary: rust-ab-glyph [armhf] (mantic-proposed/universe) [0.2.21-2] (no packageset)
[15:08] -queuebot:#ubuntu-release- New binary: rust-ab-glyph [s390x] (mantic-proposed/universe) [0.2.21-2] (no packageset)
[15:23] <vorlon> fyi I'm seeing a cross-flavor build failure wrt 'cinnamon-l10n : Breaks: nemo (< 5.8~) but 5.6.5-1 is to be installed', in flavors that aren't meant to be seeding cinnamon (so far: unity, budgie)
[15:25] <jbicha> vorlon: budgie & unity do ship nemo. Cinnamon transition is in progress at bug 2027869
[15:26] -ubottu:#ubuntu-release- Bug 2027869 in cinnamon (Ubuntu) "Sync cinnamon 5.8.4-1 (universe) from Debian experimental (main)" [Undecided, Incomplete] https://launchpad.net/bugs/2027869
[15:26] -queuebot:#ubuntu-release- New binary: rust-ab-glyph [riscv64] (mantic-proposed/universe) [0.2.21-2] (no packageset)
[15:26] <vorlon> jbicha: ok
[15:27] <vorlon> doesn't look like a very smooth transition of packages that need to be coinstallable have landed in the release pocket with breaks: between them
[15:27] <vorlon> s/of/if/
[15:28] <jbicha> Cinnamon & MATE use perhaps stricter-than-necessary dependencies in their packages
[15:54] -queuebot:#ubuntu-release- New: accepted rust-ab-glyph [amd64] (mantic-proposed) [0.2.21-2]
[15:54] -queuebot:#ubuntu-release- New: accepted rust-ab-glyph [armhf] (mantic-proposed) [0.2.21-2]
[15:54] -queuebot:#ubuntu-release- New: accepted rust-ab-glyph [riscv64] (mantic-proposed) [0.2.21-2]
[15:54] -queuebot:#ubuntu-release- New: accepted rust-ab-glyph [arm64] (mantic-proposed) [0.2.21-2]
[15:54] -queuebot:#ubuntu-release- New: accepted rust-ab-glyph [s390x] (mantic-proposed) [0.2.21-2]
[15:54] -queuebot:#ubuntu-release- New: accepted rust-ab-glyph [ppc64el] (mantic-proposed) [0.2.21-2]
[17:15] <Trevinho> SRU team: FYI the crash increase we got in gjs is not a new error: it's a gtk4 issue that has always been there and that is now being handled via https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2027986
[17:15] -ubottu:#ubuntu-release- Launchpad bug 2027986 in gtk4 (Ubuntu Jammy) "gjs-console running Extensions Manager crashes with free(): invalid pointer" [Undecided, In Progress]
[17:15] <Trevinho> so that could be probably be ignored for gjs
[17:17] -queuebot:#ubuntu-release- New binary: nanovna-saver [amd64] (mantic-proposed/none) [<IP_ADDRESS>30708-1] (no packageset)
[18:11] -queuebot:#ubuntu-release- Unapproved: gtk4 (jammy-proposed/main) [4.6.6+ds-0ubuntu1 => 4.6.9+ds-0ubuntu<IP_ADDRESS>] (desktop-core, i386-whitelist, ubuntu-desktop)
[19:10] -queuebot:#ubuntu-release- Unapproved: containerd (lunar-proposed/main) [1.6.12-0ubuntu3.2 => 1.6.12-0ubuntu3.3] (ubuntu-server)
[19:12] -queuebot:#ubuntu-release- Unapproved: containerd (kinetic-proposed/main) [1.6.12-0ubuntu1~22.10.3 => 1.6.12-0ubuntu1~22.10.4] (ubuntu-server)
[19:13] -queuebot:#ubuntu-release- Unapproved: containerd (jammy-proposed/main) [1.6.12-0ubuntu1~22.04.4 => 1.6.12-0ubuntu1~22.04.5] (ubuntu-server)
[19:15] -queuebot:#ubuntu-release- Unapproved: containerd (focal-proposed/main) [1.6.12-0ubuntu1~20.04.4 => 1.6.12-0ubuntu1~20.04.5] (no packageset)
[19:20] -queuebot:#ubuntu-release- Unapproved: docker.io (lunar-proposed/universe) [20.10.21-0ubuntu3.1 => 20.10.21-0ubuntu3.2] (no packageset)
[19:21] -queuebot:#ubuntu-release- Unapproved: docker.io (kinetic-proposed/universe) [20.10.21-0ubuntu1~22.10.3 => 20.10.21-0ubuntu1~22.10.4] (no packageset)
[19:23] -queuebot:#ubuntu-release- Unapproved: docker.io (jammy-proposed/universe) [20.10.21-0ubuntu1~22.04.4 => 20.10.21-0ubuntu1~22.04.5] (no packageset)
[19:24] -queuebot:#ubuntu-release- Unapproved: docker.io (focal-proposed/universe) [20.10.21-0ubuntu1~20.04.3 => 20.10.21-0ubuntu1~20.04.4] (no packageset)
[20:38] <ItzSwirlz> hi whats happening?
[20:38] <ItzSwirlz> ill get that cinnamon debdiff gling
[20:38] <ItzSwirlz> *goin
[20:50] -queuebot:#ubuntu-release- Unapproved: golang-github-containers-psgo (focal-proposed/universe) [1.4.0-1 => 1.4.0-1ubuntu0.1] (no packageset)
[20:50] -queuebot:#ubuntu-release- Unapproved: golang-github-containers-storage (focal-proposed/universe) [1.15.8+dfsg1-1ubuntu1 => 1.15.8+dfsg1-1ubuntu2] (no packageset)
[20:51] -queuebot:#ubuntu-release- Unapproved: opengcs (focal-proposed/universe) [0.3.4+dfsg2-0ubuntu<IP_ADDRESS> => 0.3.4+dfsg2-0ubuntu<IP_ADDRESS>] (no packageset)
[20:51] <ItzSwirlz> ugh!! im having patch issues
[20:51] <ItzSwirlz> this is what i hate the most about quilt/diff stuff, the freaking f u z z
[20:53] <kanashiro[m]> vorlon: I needed to update src:containerd and src:docker.io to also remove DEP-8 tests relying on the application (which is not provided by those source packages anymore), and also needed to update some go packages in focal to make them build with Go 1.20 to fix the FTBFS against the newer runc. All those packages are sitting in -unapproved now
[21:03] <vorlon> kanashiro[m]: ok. hopefully another SRU vanguard will review them before my next shift on Friday
[21:05] <ItzSwirlz> Sorry about my mental breakdown over the patches, I was dumb with how I approached patching it
[21:05] <ItzSwirlz> I got a debdiff ready
[21:06] <ItzSwirlz> uploaded to 2027869
[23:16] -queuebot:#ubuntu-release- New binary: rust-ratatui [amd64] (mantic-proposed/none) [0.21.0-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: box64 [amd64] (mantic-proposed/none) [0.2.2+dfsg-2] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: rust-ratatui [s390x] (mantic-proposed/none) [0.21.0-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: rust-ratatui [armhf] (mantic-proposed/none) [0.21.0-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: rust-ratatui [ppc64el] (mantic-proposed/none) [0.21.0-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New: accepted rust-ratatui [armhf] (mantic-proposed) [0.21.0-1]
[23:24] -queuebot:#ubuntu-release- New: accepted rust-ratatui [ppc64el] (mantic-proposed) [0.21.0-1]
[23:25] -queuebot:#ubuntu-release- New: accepted box64 [amd64] (mantic-proposed) [0.2.2+dfsg-2]
[23:25] -queuebot:#ubuntu-release- New: accepted rust-ratatui [amd64] (mantic-proposed) [0.21.0-1]
[23:25] -queuebot:#ubuntu-release- New: accepted nanovna-saver [amd64] (mantic-proposed) [<IP_ADDRESS>30708-1]
[23:25] -queuebot:#ubuntu-release- New: accepted rust-ratatui [s390x] (mantic-proposed) [0.21.0-1]
[23:29] -queuebot:#ubuntu-release- New binary: box64 [ppc64el] (mantic-proposed/none) [0.2.2+dfsg-2] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: rust-ratatui [arm64] (mantic-proposed/none) [0.21.0-1] (no packageset)
[23:30] -queuebot:#ubuntu-release- New: accepted box64 [ppc64el] (mantic-proposed) [0.2.2+dfsg-2]
[23:30] -queuebot:#ubuntu-release- New: accepted rust-ratatui [arm64] (mantic-proposed) [0.21.0-1]
[23:34] -queuebot:#ubuntu-release- New: accepted fonts-ubuntu-classic [source] (mantic-proposed) [0.83-6ubuntu2]
[23:50] -queuebot:#ubuntu-release- New binary: fonts-ubuntu-classic [amd64] (mantic-proposed/none) [0.83-6ubuntu2] (no packageset)
[23:50] -queuebot:#ubuntu-release- New binary: rust-ratatui [riscv64] (mantic-proposed/none) [0.21.0-1] (no packageset)
[23:53] -queuebot:#ubuntu-release- New binary: box64 [riscv64] (mantic-proposed/none) [0.2.2+dfsg-2] (no packageset)


 Hi, just out of curiosity (and to learn), what are modules and headers?
 in this context : https://matterbridge.lubuntu.me/ae30dc61/file_9758.jpg
[05:58] <guiverc> @Rodrigo, kernel modules are optional 'modules' that can be inserted/removed from the running kernel... generally they're what most people call "drivers"... ie. used to access hardware (intel/nvidia etc kernel modules are usually called drivers)
[05:59] <guiverc> I'll refer you to https://unix.stackexchange.com/questions/47330/what-exactly-are-linux-kernel-headers for headers... (not sure how I could easily describe them)


[06:43] <tjaalton> huh, xenial update shut down my desktop midway during upgrade
[06:44] <pitti> Good morning
[07:09] <smb> morning... *sigh* another week another partial upload for grub2 to trusty...
[07:10] <ricotz> hmm, the gcc-5 upgrade in xenial-proposed is quite large, seems it wasn't properly stripped
[07:35] <pitti> ricotz: oh, thanks for pointing out; that's a backporting error
[07:35] <pitti> ricotz: doko often keeps debugging stuff on in devel, but that shouldn't happen in stable
[07:37] <pitti> ricotz: err, is it?
[07:37] <pitti> 8548582 vs. 8548494 bytes, that's not much difference
[07:37] <pitti> oh, cpp-5
[07:38] <ricotz> pitti, yeah, I was referring to the source package
[07:39] <ricotz> so g++-5 and cpp-5 are not stripped
[07:40] <pitti> ricotz: thanks, I adjusted bug 1586673
[08:00] <pitti> jamespage: hey!
[08:01] <pitti> jamespage: is the server team still interested in floodlight? it's been FTBFS for several cycles, not getting along with our current java
[08:01] <pitti> it's not in Debian either
[08:15] <pitti> infinity: yay, latest Debian dpkg now has the Test-Depends: stuff; do you want to do the merge (as you TIL), or want me to?
[08:18] <infinity> pitti: I'll grab it.
[08:19] <flexiondotorg> Morning.
[08:20] <flexiondotorg> Can I request a little help progressing a few SRUs?
[08:21] <flexiondotorg> They are intended for 16.04.
[08:21] <flexiondotorg> I've got a couple of seemingly conflicting feedback. One bug I've been asked to open an additional but, which I'm happy to do although I don't understand what I'm being asked to do.
[08:22] <flexiondotorg> https://bugs.launchpad.net/ubuntu-mate/+bug/1581168
[08:22] <flexiondotorg> And bug I'm being asking to track the SRU in just one bug, not two. Again, happy to do that.
[08:22] <flexiondotorg> https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-settings/+bug/1577706
[08:23] <flexiondotorg> I'd just like to better understand the correct way to progress SRUs in the future.
[08:32] <infinity> pitti: Ooo, lots of reproducibility patches in this upload too.
[08:33] <pitti> infinity: indeed, this looks like "want it"
[08:33] <infinity> pitti: Yeahp, just going over the diff and merging now.  Keynotes don't need my full attention. :P
[08:33] <pitti> infinity: ah, you're at debconf too? enjoy!
[08:34] <infinity> pitti: *nod*
[08:34] <pitti> infinity: our 119kB patch is almost exclusively teh changelog :)
[08:34] <pitti> actual changes are fairly small these days, fortunately
[08:34] <infinity> pitti: I know, I've been TIL for a long time, and I take pride in that diff.
[08:34] <infinity> pitti: It was several MB when I took it over. :P
[08:34] <pitti> *clap* *clap*
[08:39] <infinity> pitti: Was there an LP bug for this, or did I make you file it upstream so we could avoid that?
[08:40] <infinity> Oh, wait, found it.
[08:40] <pitti> infinity: for what?
[08:40] <infinity> https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1491145
[08:40] <pitti> ah, yes, that
[08:40] <pitti> the Debian bug is linked
[08:40]  * infinity nods.
[08:51] <infinity> pitti: Test-building, will upload during the next session.
[10:30] <LocutusOfBorg> broken dpkg makes me saaaaaad
[10:30] <LocutusOfBorg> :(
[10:30] <LocutusOfBorg> infinity, please fix? :)
[10:30] <LocutusOfBorg> hi btw
[10:30] <LocutusOfBorg> https://anonscm.debian.org/cgit/dpkg/dpkg.git/commit/?id=383260e568cef224269ab19d4250f2a87177b778
[10:30] <LocutusOfBorg> this patch is the fix
[10:31] <LocutusOfBorg> getting failures such as https://launchpad.net/ubuntu/+source/mrpt/1:1.4.0-1build2/+build/10315241
[10:31]  * LocutusOfBorg is sorry if it already is reported
[10:37] <pitti> LocutusOfBorg, infinity: uploaded, since this is OMGkittens urgency
[10:38] <pitti> I hope dpkg itself will build now :)
[10:39] <LocutusOfBorg> I guess everywhere except for armhf
[10:39] <LocutusOfBorg> some bootstrap might be needed
[10:39] <LocutusOfBorg> damn I uploaded a fixed mrpt, that is making opencv migrate
[10:39] <LocutusOfBorg> :(
[10:40] <LocutusOfBorg> and it is ftbfs on armhf for this bug
[10:40] <LocutusOfBorg> lets hope to finish the transition by some hours
[10:40] <LocutusOfBorg> and thanks for the quick upload
[10:41] <pitti> https://launchpadlibrarian.net/270800128/buildlog_ubuntu-yakkety-i386.dpkg_1.18.8ubuntu2_BUILDING.txt.gz
[10:41] <pitti> crap
[10:41] <pitti> "pull yourself out of a swamp"  situation
[10:41] <LocutusOfBorg> sad
[10:41] <pitti> ok, hang on; I'll try to remove the previous  dpkg
[10:42] <LocutusOfBorg> oh... you not on -release
[10:42] <LocutusOfBorg> I asked that some minutes ago
[10:42] <pitti> dear remove-package,  I don't want to remove ubuntu2, but ubuntu1
[10:42] <LocutusOfBorg> [12:33:55] <LocutusOfBorg> pretty please kick dpkg out of -proposed? :)
[10:42] <LocutusOfBorg> [12:34:13] <LocutusOfBorg> rationale: debian bug 829542
[10:42] <pitti> ok, done (I think)
[10:43] <pitti> https://launchpad.net/ubuntu/+source/dpkg/+publishinghistory
[10:43] <pitti> infinity: so I guess let's just re-merge 1.18.9?
[10:43] <LocutusOfBorg> <3
[10:43] <LocutusOfBorg> yes, I guess so
[10:44] <infinity> pitti: D'oh.  I hope a test was committed with the fix.
[10:45] <pitti> not in the same commit
[10:45] <infinity> Not at all, actually.  Oh well.
[10:45]  * infinity merges.
[10:45] <pitti> cheers
[10:45] <LocutusOfBorg> thanks you both
[10:46] <pitti> yay for having a little bit of fun in devel :)
[10:46]  * LocutusOfBorg goes back in his cave
[10:46] <LocutusOfBorg> broken dpkg is always fun
[10:46] <infinity> That'll teach me to go to lunch after an upload.
[10:47] <pitti> LocutusOfBorg: btw, I suppose you need to wait ~ 30 mins for retrying your FTBFS, still needs a publisher run
[10:47] <LocutusOfBorg> pitti, I guess so
[10:47] <pitti> infinity: *shrug*, don't we all?
[10:47] <LocutusOfBorg> but meh, I already retried :)
[10:47] <pitti> Friday evening is ZE BEST time to upload systemd *whistle*
[10:47] <Odd_Bloke> Doing `apt-get install python3.4` on xenial doesn't return a non-zero error code (despite the fact that it hasn't found such a package, and nothing has been installed): http://paste.ubuntu.com/18443198/
[10:47] <Odd_Bloke> I'm not sure what I should file a bug for that against.
[10:48] <LocutusOfBorg> pitti, possibly untested ;)
[10:48] <pitti> Note, selecting 'libpython3.4-minimal' for regex 'python3.4'
[10:48] <pitti> Odd_Bloke: apt itself, I suppose
[10:48] <Odd_Bloke> (This is going to break people doing a t->x upgrade where they explicitly install python3.4; their automation isn't going to fall over because apt didn't report an error, and then they'll be unexpectedly running 3.5)
[10:49] <pitti> apt's greedy "try to interpret everything as regexp" has gone on my nerves more than once already
[10:49] <pitti> it's really not helping
[10:49] <infinity> libpython3.4-minimal also isn't in xenial.
[10:50] <pitti> yeah, I suppose it appears in some Breaks: or so
[10:51] <Odd_Bloke> Yeah, it's in findutils' Breaks.
[10:51] <pitti> I really wish apt-get install, apt-cache showsrc etc. would just stick to "do what I said", not "try to second-guess me by interpreting my package name as a RE and then desperately try anything that matches"
[10:56] <smb> FourDollars, slangasek, Just to make sure, are you aware that the upload to grub2 in Trusty will also need a follow-up upload of grub2-signed? (proposed enabled threatens me with the removal of signed grub again)
[10:57] <FourDollars> smb: yes, I am aware that.
[10:59] <FourDollars> smb: Any concern?
[11:00] <smb> FourDollars, ok. So there is hope that there soon will be one, I guess. My concern right now is more that I cannot dist-upgrade without loosing signed. :)
[11:02] <FourDollars> smb: I see.
[11:03] <infinity> pitti: That's weird.  dpkg-buildpackage worked on amd64...
[11:03]  * infinity waits for the publisher to finish before retrying the rest.
[11:09] <pitti> infinity: yeah, my previous ubuntu2 also worked on amd64, not sure why
[11:10] <infinity> pitti: I'm tyring not to think about it.  I'm sure there's a reasonable explanation that will give me an aneurysm on the way to understanding it.
[11:11] <pitti> +1 :)
[11:11] <infinity> My not having .za power is going to get really old, really soon.
[11:12] <FourDollars> pitti: Could you also help to update grub2-signed for https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1591818?
[11:13] <pitti> FourDollars: err, tell me how?
[11:14] <infinity> pitti: pull-lp-source grub2-signed, add changelog entry, change build-deps in debian/control
[11:14] <pitti> ah, just a no-change upload?
[11:14] <infinity> Well, no-change, except for debian/control. :P
[11:14] <infinity> A not-much-change upload.
[11:15] <pitti> right
[11:15] <pitti> wow, current version is against 1.8, we have 1.11 in -proposed; what happened to .9 and .10
[11:15] <pitti> and the build against 1.8 b-deps on >= 1.7
[11:16] <infinity> 1.8 is in updates.
[11:16] <infinity> Looks like proposed keeps getting overwritten.
[11:16] <pitti> FourDollars, infinity: http://paste.ubuntu.com/18444168/ ?
[11:16] <FourDollars> pitti: I am not sure if you can upload grub2-signed or not.
[11:16] <infinity> Or something.
[11:17] <infinity> pitti: Bad version number.
[11:17] <infinity> pitti: Should be 1.34.10
[11:17] <pitti> I can, its binaries will just land in unapproved for another archive admin inspection, AFAIK (at least linux-signed does)
[11:17] <infinity> pitti: Otherwise fine.
[11:17] <pitti> ack, thanks
[11:17] <FourDollars> pitti: thx, it looks OK.
[11:19] <infinity> Err, WTF?
[11:19] <pitti> Rejected:
[11:19] <pitti> File grub2-signed_1.34.10.tar.xz already exists in Primary Archive for Ubuntu, but uploaded version has different contents. See more information about this error in
[11:19] <pitti> meh
[11:19] <infinity> pitti: Hold on.
[11:19]  * pitti checks publishing history and bumps
[11:19] <infinity> pitti: Why did you accept that grub2 upload?
[11:19] <infinity> pitti: It reverted what was in proposed.
[11:20] <pitti> infinity: that's what I thought too
[11:20] <pitti> infinity: and I rejected it
[11:20] <smb> infinity, pitti The versions are missing for a previous attempt to update that got broken by some current softlink not correct and then taken back
[11:20] <pitti> infinity: slangasek then told me that it was deliberately reverted, and that this was ok, so I re-accepted it
[11:20] <infinity> Oh.
[11:20] <infinity> Oookay.
[11:20] <FourDollars> Oops
[11:20] <pitti> ok, 1.34.13 it is
[11:21] <infinity> I hope someone told cyphermox he got trumped.
[11:22] <smb> infinity, I think he know (was some kind of "oh we don't need the grub2 changes after all" thing
[11:22] <infinity> smb: Kay.
[11:24] <pitti> it's diffy now in https://launchpad.net/ubuntu/trusty/+queue?queue_state=1
[11:24] <pitti> but I don't want to self-accept
[11:25] <infinity> pitti: I already got it.
[11:25] <pitti> cheers
[12:48] <Bluefoxicy> lol... ternary DNS
[13:13] <cyphermox> infinity: pitti: grub2> all is good
[13:29] <infinity> cyphermox: Check.
[13:42] <Odd_Bloke> pitti: infinity: Apparently not considered a bug in apt: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1598810
[13:43] <Odd_Bloke> In the classic vein of "I wrote and/or use this every day so I can't see that it's in some ways deficient" with a nice helping of condescension towards the bug reporter.
[13:51] <LocutusOfBorg> pitti, please retry talloc and pptpd? :)
[13:51] <LocutusOfBorg> I should have retried everything that was failing on universe/multiverse
[13:52] <LocutusOfBorg> they are both in main and failed for dpkg
[14:00] <pitti> LocutusOfBorg: done
[14:01] <LocutusOfBorg> <3
[14:01] <LocutusOfBorg> I'll look at them, thanks
[14:01] <LocutusOfBorg> I don't know how to check which packages needs retry, but I think we should be good now
[14:01] <LocutusOfBorg> I looked at excuses for missing builds
[14:02] <LocutusOfBorg> but only to stuff uploaded/syncd today, older builds might have failed
[14:02] <pitti> LocutusOfBorg: https://launchpad.net/ubuntu/yakkety/+builds?build_text=&build_state=failed&arch_tag=all isn't a too bad place to start
[14:02] <pitti> actually, https://launchpad.net/ubuntu/yakkety/+builds?build_text=&build_state=failed&arch_tag=i386 is easier (it should have failed on i386)
[14:03] <pitti> LocutusOfBorg: there are only a handful which failed today, I'll retry them all
[14:03] <LocutusOfBorg> indeed thanks
[14:03] <LocutusOfBorg> but I guess I already retried them
[14:04] <LocutusOfBorg> I'm trying to understand something that was "given back" on a particular architecture only
[14:04] <pitti> nope, that was it, no further victims
[14:04] <LocutusOfBorg> wonderful
[14:05]  * LocutusOfBorg leaves
[14:07] <xnox> slangasek, should initramfs have valid /etc/passwd & /etc/group ? such that e.g.
[14:07] <doko> jamespage, rbasak: python2.7 2.7.10 is now in -proposed. would be nice if you could give it a quick check (openstack)
[14:07] <xnox> people can set non-default user names & groups in mdadm and expect it to work
[14:08] <infinity> xnox: That's certainly never been a design goal.
[14:09] <infinity> xnox: But if mdadm relies on that, it should figure out how to make it work.
[14:09] <xnox> infinity, yes, that's what i'm trying to make work
[14:09] <xnox> the default is "if no config found use: 0 (root), and 6 (disk)"
[14:10] <xnox> the initramfs hooks write out CREATE user=root, group=disk -> which then fails to resolve lol
[14:11] <infinity> xnox: Can the IDs be resolved at hook time, and used numerically at boot time?
[14:12] <rbasak> doko: my team doesn't touch openstack any more. I'll leave to jamespage - not sure if he's in today or not.
[14:12] <xnox> infinity, code does not support that in mdadm at the moment.
[14:12]  * xnox ponders stuff
[14:12] <rbasak> Or maybe beisner can help, but I expect he's on vacation today (US holiday)
[14:13] <xnox> infinity, yeah i need your help =)
[14:18] <infinity> xnox: What are you doing in the next session slot?
[14:18] <xnox> infinity, no idea.
[14:19] <infinity> xnox: Well, if you want to find somewhere to get hacky, we can.
[14:19] <xnox> not doing much now either, would love to have your opinion.
[14:19] <xnox> infinity, where are you?
[14:19] <infinity> xnox: Listening to Vangrant talk about his reproducible build network.
[14:19] <xnox> ack
[14:48] <zyga> pitti: hey, what kind of extra reassurance do you need for snapd to migrate in xenial?
[14:51] <pitti> zyga: 1597329 hasn't been verified, it's only been 4 days, and yakkety is still broken
[15:00] <zyga> pitti: ok, I'm looking at why yakkety may be broken
[15:00] <zyga> pitti: once I unbreak or understand yakkety, what's the next step, just verification?
[15:00] <pitti> zyga: yes
[15:01] <pitti> zyga: y> appreciated; it's been broken since 2.0.2
[15:02] <zyga> pitti: this fits into my "make snappy work everywhere" goal :)
[15:02] <zyga> ubuntu too :)
[15:09] <sil2100> !dmbping
[15:09] <sil2100> !dmb-ping
[15:09] <sil2100> hmmm
[15:09] <sil2100> Ah, no ubottu?
[15:09] <sil2100> No, he's here
[15:23]  * zyga runs autopackagetests for snappy on yakkety, trying to understand the issue
[15:32] <rbasak> Laney, infinity: I added juliank to ~ubuntu-core-dev, which indirectly makes him a member of ~ubuntu-dev. So I don't need to explicitly add him to ~ubuntu-dev, right?
[15:33] <rbasak> (also he was already an Ubuntu member anyway)
[15:34] <infinity> rbasak: Yeah, the implicit membership should be fine.
[15:34] <rbasak> OK, thanks.
[16:08] <juliank> xnox: I'm a core-dev now, we should celebrate!
[22:37] <xnox> yeah =)
[22:37] <xnox> juliank, well done
[23:29] <infinity> pitti: After fallout in several other packages was sorted, you have a dpkg.  Cheers.


[00:11] <maxb> Jesdisciple: erm, what? I'm afraid you really haven't clearly explained what your problem is at all.
[00:15] <maxb> Jesdisciple: To try to clear up some confusion - Launchpad's public SSH key is not published anywhere other than its SSH service itself, because it doesn't need to be
[00:17] <maxb> Jesdisciple: Whilst it's true that you'd need to independently verify the key if you were concerned about the possibility of DNS poisoning or traffic interception, people in general simply *aren't* sufficently concerned about those eventualities for a mechanism of independent verification to exist.
[00:18] <maxb> Jesdisciple: And given that Launchpad primarly deals in open source software anyway, it's hard to see why concern over those kinds of attacks should be warranted.
[00:20] <maxb> Jesdisciple: So, in conclusion, your trust in Launchpad's keys is a separate issue to any connectivity issues you may be having. Be sure to clearly separate the two as you ask for further assistance, for best chance of clear replies
[00:51] <Jesdisciple> maxb: Sorry, was reading.  I was concerned with this message which had bin pastebin'd by another user:
[00:51] <Jesdisciple> Warning: Permanently added 'bazaar.launchpad.net,<IP_ADDRESS>' (RSA) to the list of known hosts.
[00:51] <maxb> Jesdisciple: ok... why are you concerned by it?
[00:52] <Jesdisciple> I now think the issue was simply my misunderstanding of the warning...  I thought warning meant "bad, please fix"...  Apparently proceeding despite the warning results in the proper action (installing the public key)
[00:53] <Jesdisciple> correction: the warning that came before the prompt to which I answered yes, thus triggering that one
[00:53] <maxb> Jesdisciple: It's more of an "hey, if you're paranoid or working in a high-security environment, you may care about this"
[00:54] <Jesdisciple> I always try to clean warnings out of my compiler output, and the warning really wasn't very descriptive.
[00:55] <Jesdisciple> I was quite flabbergasted why none of the rest of the Internet had that problem.
[00:56] <Jesdisciple> In hindsight I should have realized that the warning coming after "yes" referred to a new key.
[00:56] <Jesdisciple> but the message I took away was "bad, please fix"
[00:58] <Jesdisciple> lol... s/bin/been
[01:00] <Jesdisciple> Jesdisciple@world:~$ sudo apt-get install english-alpha-ipa
[13:34] <rick_h> adeuring: taking irc
[13:34] <adeuring> rick_h: thanks
[15:12] <mdeslaur> Could someone please take a look at OOPS-32cbca4d1b6c1e5444444084f2a7c23d
[15:12] <mdeslaur> It's a simple bug, but I can't close it, or make it public or anything without getting a timeout
[15:51] <rick_h> mdeslaur: looking
[15:51] <mdeslaur> rick_h: thanks
[15:59] <rick_h> mdeslaur: I'm not able to pull up that bug at all: 927032 ?
[16:00] <mdeslaur> rick_h: it's a private bug that I would like to make public
[16:00] <mdeslaur> rick_h: and mark as invalid, but I can't
[16:00] <rick_h> mdeslaur: ok, thanks. That helps
[16:03] <lifeless> mdeslaur: the oops is a heat timeout
[16:03] <lifeless> UPDATE Distribution SET max_bug_heat=(SELECT COALESCE(MAX(heat), 0) FROM ((SELECT Bug.heat\n                      FROM
[16:03] <lifeless> ///
[16:03] <niemeyer> Folks, where has the "Active reviews" link for the project gone?
[16:04] <mdeslaur> lifeless: it's a private bug with a single reporter that nobody can view...how is there a heat timeout on it?
[16:04] <lifeless> the heat UI changes have been activated, but we haven't disabled the plumbing (its a little more intrusive, will be going this week I hope)
[16:04] <lifeless> mdeslaur: because it writes to Ubuntu
[16:04] <mdeslaur> lifeless: oh! I see
[16:04] <lifeless> mdeslaur: this is *why* we're doing the heat changes, because as it stands it has huge contention
[16:04] <mdeslaur> lifeless: ok, so if I wait a week or two, the problem will go away by itself?
[16:04] <lifeless> mdeslaur: for now, just keep trying
[16:05] <lifeless> mdeslaur: or wait for a week or so yeah
[16:05] <mdeslaur> lifeless: awesome, thanks!
[16:05] <mdeslaur> thanks rick_h
[16:05] <lifeless> niemeyer: what page is it missing from ?
[16:05] <niemeyer> lifeless: launchpad.net/project
[16:05] <lifeless> niemeyer: thats a disabled project.
[16:05] <lifeless> niemeyer: you shouldn't be able to see it at all
[16:06] <niemeyer> lifeless: Sorry, I mean it should be in the main project page
[16:06] <niemeyer> lifeless: https://launchpad.net/goamz
[16:07] <lifeless> niemeyer: on https://code.launchpad.net/goamz - 'Launchpad does not know where goamz hosts its code.
[16:07] <lifeless> '
[16:07] <lifeless> niemeyer: IIRC this disables merge proposal features and so on
[16:07] <niemeyer> lifeless: Apparently it does.. https://code.launchpad.net/goamz/+activereviews
[16:08] <lifeless> niemeyer: try toggling it to 'hosted on launchpad'
[16:08] <lifeless> niemeyer: there should be a control on the https://launchpad.net/goamz page, right hand side 'project configuration'
[16:09] <niemeyer> lifeless: Nope.. it asks me to link a branch
[16:09] <niemeyer> lifeless: this project uses series only
[16:10] <lifeless> you can rename trunk to something else
[16:11] <lifeless> I don't think having trunk mapped to a branch is needed, there is a different setting
[16:11] <lifeless> IMBW
[16:13] <niemeyer> Ok, Launchpad must be getting lost with series.. we're going to get rid of series usage in this project anyway, since it's getting too messy, so that's fine
[16:14] <lifeless> I suspect something is contingent on either the default series having a branch (which is totally compatible with only using series - just rename trunk to one of your series')
[16:14] <lifeless> or it is contingent on the main 'hosted on lp' setting, which *should* be settable without setting a branch for the default series
[16:15] <niemeyer> lifeless: That'd mean one of the series is more special.. that's not the case
[16:15] <niemeyer> lifeless: They're all in development
[16:15] <lifeless> thats a separate flag for LP
[16:16] <lifeless> project has a pointer to default series, each series has a status development/obsolete etc.
[16:16] <lifeless> this is baked in the model
[16:17] <niemeyer> lifeless: Yeah.. it's just that project default series doesn't make sense in this case
[16:17] <niemeyer> lifeless: It's fine.. we'll stop using series
[16:18] <lifeless> if that works for you, cool. OTOH that may not be enough to get the link back.
[16:19] <niemeyer> lifeless: Don't see why.. we'll simply use a main branch with the project
[16:19] <lifeless> that works by having a default series
[16:19] <lifeless> LP won't let you have no series at all
[16:19] <niemeyer> lifeless: That's fine.. whatever makes it happy
[16:20] <lifeless> heh, ok :)
[16:20] <lifeless> you'll also get faster pushes that way
[16:31] <deryck> rick_h, I've got IRC now.  Sorry I didn't take it earlier.
[16:31] <rick_h> deryck: thanks, let me know when you get a chance to chat JS
[17:52] <nand_nanda_21_> hi. i am not able to import my pgp key to launchpad.
[17:53] <nand_nanda_21_> once i import my key in launchpad, i got a mail from launchpad asking me to decrypt the pgp message.. when i do gpg < message> i am not able to decrypt my message.
[17:53] <nand_nanda_21_> could someone advice my on how to upload pgp key on launchpad?
[17:54]  * mgedmin did that a long time ago and didn't remember having trouble
[17:55] <mgedmin> then again I use Mutt for reading mail, and Mutt supports pgp/mime very nicely
[17:55] <mgedmin> could it be some sort of mime-encoding of the message is interfering with gpg's ability yo decrypt it, if you just paste it raw?
[18:22] <Enlik> hi, is there any known issue about inability to login? I can't (I get error with error code), also I am unable to search bugs - I get an error too and get address ending with null/?<etc.>. If it helps, UI language is Polish.
[18:23] <Enlik> of course I'm talking about Launchpad
[18:25] <Enlik> oh, bug searching worked this time, but login still not (and it's since a few days, at least)
[18:25] <rick_h> Enlik: what browser are you on for the second issue?
[18:27] <Enlik> rick_h: Opera (hm, seems to work in Firefox, but login doesn't in any of the two)
[18:27] <rick_h> Enlik: ok, so the second issue is a known bug with opera.
[18:27] <Enlik> I see
[18:28] <Enlik> will be fixed or is it said to be an "Opera should do something" one?
[18:28] <rick_h> for the login, do you get to the login page and then some error code? what's the url/error?
[18:28] <rick_h> Enlik: it's opera not suporting html5 history and we've got a todo to work on making it work on it, but it's not super high priority
[18:28] <Enlik> (just asking, don't intend to be mean)
[18:29] <Enlik> so it means it won't work in majority of browsers, if I'm not mistaken. Interesting. About the login issue, I'm redirected to https://login.launchpad.net/+login and the error is: 2228carambolalaunchpad810
[18:30] <Enlik> (also, if it helps, I'm not sure I type the right password - been some time since I needed to type it last time…)
[18:30] <rick_h> deryck: what's the sso irc channel?
[18:31] <deryck> rick_h, maybe #ubuntu-sso ?  I'm not sure actually.  let me look and see...
[18:31] <rick_h> deryck: tried that and canonical-sso without luck, searching
[18:31] <Enlik> try /query alis
[18:32] <deryck> maybe it's just the public is channel.
[18:32] <Enlik> (works for non-hidden channels)
[18:32] <dobey> rick_h, deryck: i don't think there's an sso-specific channel.
[18:33] <rick_h> sorry, my mistake then. Thought I saw one during idle at some point. oops
[18:34] <deryck> rick_h, so there are a couple options, see this link:  https://wiki.canonical.com/Launchpad/IRCSupport
[18:35] <rick_h> deryck: ah, that's what I saw. The form there.
[18:36] <rick_h> Enlik: so give this a shot for the login trouble. https://forms.canonical.com/lp-login-support/
[18:39] <cjohnston> Is one project able to be under 2 project groups?
[18:40] <sinzui> cjohnston, no
[18:40] <cjohnston> ok. thanks
[18:40] <sinzui> cjohnston, project groups are about control, not affiliation
[18:40] <TEttinger> I'm getting an error: Permission Denied (publickey).
[18:41] <TEttinger> I'm not sure why, or what is causing it, but I am trying to create a project
[18:41] <TEttinger> (I am new to bazaar in general, but reasonably experienced with git)
[18:42] <TEttinger> I get the error when I try to push to my project's trunk on LP
[18:42] <cjohnston> sinzui: we have a "Community Web Projects" which is a project group.. We have all of the communtiy projects in that project.. There are also multiple Summit projects, which very well would fit under a "Summit Project" project group due to their relation, but also fit inside of Community Web Projects... I'm also assuming it isnt possible for a project group to be nested
[18:43] <sinzui> no
[18:43] <sinzui> project groups are broken by design
[18:44] <cjohnston> ok
[18:44] <sinzui> organisations need nested projects, communities need tags. We did not build either
[18:47] <Enlik> rick_h: done
[18:48] <Enlik> rick_h: thanks for your input
[18:48] <Enlik> (I'm still wondering why using a simple GET searching wasn't enough, but :))
[18:48] <Enlik> s/but/btw./
[18:50] <rick_h> Enlik: the new buglisting stuff does some tricks that involve updating the url and in opera it's not supporting part of that machinery which gets undefined/null values into the url that it then chokes on
[18:50] <abentley> deryck: I relieve you.
[18:51] <TEttinger> abentley, does Help contact mean you help with noob problems like mine?
[18:52] <abentley> TEttinger: That means that none of the SSH public keys you have registered with LP could be used for your push.
[18:52] <Enlik> rick_h: hm, okay
[18:52] <TEttinger> abentley, I saw something about ssh-add
[18:53] <TEttinger> but it wasn't a link, so I wasn't sure where to look it up
[18:53] <abentley> TEttinger: what OS are you using?
[18:54] <TEttinger> Xubuntu 64-bit (in a VM)
[18:55] <abentley> TEttinger: If you type "man ssh-add" in a terminal, that should give you information about the command.
[18:55] <TEttinger> abentley, heh true...
[18:56] <abentley> TEttinger: If you're ~marek-tettinger, it appears that you haven't registered any SSH keys with Launchpad, so that would be one problem.
[18:56] <TEttinger> nope
[18:57] <TEttinger> abentley, I am thomas-ettinger on launchpad
[18:57] <TEttinger> the command I am using:
[18:58] <TEttinger> bzr push lp:~thomas-ettinger/salmon-contrib/trunk
[18:59] <abentley> TEttinger: You do have a key, so it sounds like you need to make SSH aware of it before pushing.
[19:00] <abentley> TEttinger: e.g. with ssh-add, though there are other ways configuring SSH to use a given key.
[19:01] <TEttinger> hmm, I should be using my public key, right?
[19:01] <TEttinger> ~/.ssh/id_rsa.pub
[19:01] <abentley> TEttinger: No, you should be using your private key, typically ~/.ssh/id_rsa
[19:02] <TEttinger> abentley, I should give my private key to LP?
[19:03] <mgedmin> TEttinger, no!
[19:03] <EvilResistance> TEttinger, for SSH, you give the public:
[19:03] <abentley> TEttinger: No, you should use your private key with SSH, so that Launchpad can use your public key to authenticate you.
[19:03] <EvilResistance> id_rsa.pub
[19:03] <mgedmin> you never give your private key to anyone
[19:03] <EvilResistance> abentley, you give LP the public key
[19:03] <EvilResistance> erm
[19:03] <EvilResistance> TEttinger, ^
[19:03] <TEttinger> yeah, i was wondering...
[19:03] <EvilResistance> TEttinger, you keep the private key private and you provide the public key
[19:04] <TEttinger> yeah, that seemed wrong
[19:16] <TEttinger> huh, I might have had the wrong key on LP -- I removed the old one and re-added id_rsa.pub, now it seems to work
[19:16] <abentley> TEttinger: Great.
[19:17] <abentley> TEttinger: Perhaps the old one was from a previous VM.
[19:19] <TEttinger> abentley, yeah that is likely too
[19:19] <TEttinger> oh!
[19:19] <TEttinger> I reinstalled ssh recently
[19:20] <abentley> TEttinger: Installation by itself wouldn't have replaced an existing key.  But maybe you also ran ssh-keygen after that.
[19:45] <buzz_> there have been large wait times for launchpad builders over the last days, and many occasions in the last weeks/months where there have been large queues. Are queue times of a few hours to be considered "the norm" now, or have I somehow just been incredibly unlucky when uploading
[19:45] <buzz_> s/large/long
[19:46] <lifeless> we've had a significant increase in usage and haven't [yet] compensated for that
[19:46] <lifeless> we're doing what we can with the resouces on hand
[19:47] <buzz_> are manual submissions prioritised over auto builds or ?
[19:48] <buzz_> im sure there used to be more builders than are on now though right ?
[19:57] <buzz_> also your machines are all internal / run by you ? i assume it isn't currently possible for users to contribute some cpu cycles etc ?
[19:57] <mgedmin> I suppose there are trust issues that make this complicated
[19:59] <buzz_> hmm yeh, i guess
[20:15] <buzz_> would it be a trust issue if people could submit prebuilt packages directly? as of course, anyone could already submit bad code to be built already.
[20:15] <buzz_> just ideas.
[20:26] <TEttinger> buzz_, have you looked at the OpenSUSE Build Service?  I think they can build .deb packages as well, and maybe it can interact with Launchpad as an external service?
[20:29] <dobey> obs doesn't put built packages into launchpad ppas. i guess perhaps they provide their own archives setup, but it doesn't interact with launchpad in that sense
[21:14] <buzz_> well, i can of course just stick my packages on my own server anyway. just seemed nice to have em on lp anyway and easy for ubuntu users to find, and use
[21:14] <buzz_> lp is nice and convenient
[22:20] <dobey> buzz_: well i wouldn't worry about the seemingly long waits for builds. it's not always that bad. and it is a free service. though commercial options are also available. :)
[22:22] <buzz_> well, it can be slightly annoying to wait 3 hours to find the build failed. heh. I appreciate the server is free. as is my work supporting ubuntu users and fixing ubuntu bugs that ubuntu doesnt get around to fixing :)
[22:24] <tumbleweed> buzz_: if you're doing a fair number of builds, it's worth the effort of setting up pbuilder / sbuild locally. There are times when LP has > 24hr build queues
[22:25] <tumbleweed> (plus, you can debug builds locally. Remote builds you just have a log to stare at)
[22:28] <wgrant> LP isn't a build testing service.
[22:28] <wgrant> It's a package publishing service.
[22:31] <dobey> buzz_: like tumbleweed said; you probably want to setup pbuilder to test the builds locally with.
[22:33] <buzz_> when did i say i was using it to test. sometimes things get overlooked.
[22:34] <tumbleweed> most developers test-build locally, then upload to LP (at least most sensible ones do)
[22:34] <buzz_> i have had pbuilder set up before. I may well just use that solely in the future and host the files as I want to target debian also
[22:34] <buzz_> i do test build locally, albeit not in pbuilder right now.
[22:34] <tumbleweed> ok, then you shouldn't run into problems that often, just missing dependency type issues
[22:35] <buzz_> which is the most common issue when i bump into an issue
[22:36] <tumbleweed> right, I try and match my test-build environment to the target
[22:36] <buzz_> especially with some packages that have 30+ dependencies
[22:36] <buzz_> yeh. as do i. but its not always possible to cover everything. i am as human as the next person
[22:37] <buzz_> why has this gone from launchpad queues to somehow finger pointing at my abilities..
[22:37] <lifeless> confusion I think
[22:38] <buzz_> long waits for builds can be an issue if also for example, an issue in the package arises and you want to push out a fix
[22:38] <lifeless> yes
[22:38] <lifeless> we don't /want/ long waits.
[22:38] <tumbleweed> long waits are certainly a pain. All I was trying to do was offer advice (and yes, we all screw up some uploads :P )
[22:39] <buzz_> yep. well i hope it improves. im sure if there was a way for users to contribute resources, they would..
[22:39] <lifeless> buzz_: the issue with other builders is indeed one of trust
[22:39] <lifeless> bad code -> there is an audit trail with the code visible
[22:39] <lifeless> bad builder -> no audit trail, and the code runs as root on the machine
[22:39] <buzz_> i see
[22:40] <lifeless> if I ran a builder as a VM, I can in principle pause the vm, edit the code being built in-place, unpause, let it finish, edit the code back, and let it calculate the source package.
[22:40] <lifeless> -no- way to prove I have/haven't done that.
[22:40] <lifeless> (short of forensic analysis...)
[22:48] <buzz_> how does debian manage that for the buildd stuff? or they just dont? I'm sure in the past I was running a build machine for pa-risc arch on debian
[22:52] <buzz_> (was a long time ago, memory has faded)
[22:57] <tumbleweed> buzz_: debian has a bunch of buildds http://db.debian.org/machines.cgi (also, each maintainer uploads the binaries that they built themselves. There's talk of finally fixing that soon...)
[22:58] <stgraber> Debian is scary ;)
[22:59] <tumbleweed> we all trust DDs, right? :)
[22:59] <stgraber> if you run Debian, you don't quite have a choice do you? :)
[23:00] <stgraber> at least in Ubuntu all these binary uploads get rebuilt, that's where you discover some issues (had to fix a bunch of FTBFS because our builds don't seem to match the DD's machine ;))
[23:00] <tumbleweed> its true. But we also screw up a bit. (build in stale / dirty environments, or the wrong environment)
[23:01] <buzz_> ubuntu screwups from my experience involve changing a working debian package by adding lots of ubuntu customisations and then realising or not that is is broken
[23:01] <buzz_> hence having to maintain my own mdadm for 2+ years before it was finally fixed up somewhat in ubuntu
[23:51] <hrw> hi


[00:35] <amouge[work]> hey guys, i had a redirect that our previous developer made that was in a vhost.conf file. Im trying to put it in to a .htaccess on the new server but its not working. Heres my .htaccess currently
[00:35] <amouge[work]> http://pastebin.com/uL6s8dqV
[14:30] <reya276> Morning Everyone
[14:31] <reya276> Quick question, Can I install Libre Office from a PPA and will this in turn replace OpenOffice or will I have to remove OpenOffice afterwards
[14:33] <tiemonster> I tried to install from source and it asploded
[14:34] <tiemonster> try it in a VM first and see what happens
[14:56] <maxolasersquad> reya276: There is an official PPA, and you do have to remove OO first.
[15:15] <dantalizing> morning
[15:33] <mhall119> morning
[15:33] <MichelleQ> no.
[16:21] <maxolasersquad> reya276: To install LibeOffice, use the instructions at http://drupal.txwikinger.me.uk/content/libreoffice-now-available-ppa-ubuntu-1010-and-1004
[16:25] <mhall119> itnet7: meeting tonight?
[17:28] <mhall119> itnet7: and anyone else, can you please test http://family.ubuntu-fl.org:8000/meetings/team/1/detail/ for us
[17:28] <mhall119> thanks
[17:32] <tiemonster> mhall119: what about it?
[17:32] <dantalizing> mhall119: works fine ... moderated team though? wtf? -1
[17:36] <maxolasersquad> mhall119: URL is not loading for me.
[17:44] <mhall119> dantalizing: something they forced through launchpad
[17:46] <mhall119> tiemonster: just play with it, try to break it
[17:47] <mhall119> add meetings/agenda items, etc
[17:47] <tiemonster> on a completely unrelated note, does anyone want to help with a LTSP installation?
[17:49] <mhall119> help how?
[17:49]  * mhall119 has never used LTSP
[17:50] <tiemonster> no, probably end of Feb
[17:50] <mhall119> How, not Now
[17:50] <tiemonster> lol
[17:50] <tiemonster> Installing the server and client software
[17:50] <tiemonster> the server is in process of being purchased
[17:50] <tiemonster> mhall119: btw, I got this error: "You can not add a new agenda item for this team meeting. You are not member of the team or on the LoCo Council."
[17:52] <tiemonster> I tried to join, and it said I was already a member
[17:53] <mhall119> tiemonster: what's the username at the bottom of the screen?
[17:54] <mhall119> is it 'tiemonster'?
[17:57] <tiemonster> yep
[17:58] <mhall119> gah, ubuntu SSO is going to drive me nuts
[17:58] <mhall119> it didn't set your team membership
[17:58] <mhall119> one second
[17:58] <mhall119> try adding an agenda item now
[17:59] <tiemonster> yep
[17:59] <tiemonster> works now
[17:59] <mhall119> cool
[18:03] <tiemonster> mhall119: CRU works, but I don't see a way to D
[18:04] <mhall119> CRU?
[18:04] <mhall119> oh, I understand
[18:05] <tiemonster> create-read-update
[18:05] <tiemonster> :-)
[18:05] <mhall119> you don't get "Delete Agenda Item" at the gray nav bar at the top?
[18:06] <tiemonster> oh. well that's not very intuitive...
[18:06] <tiemonster> yes. it works.
[18:06] <mhall119> cool
[18:06] <mhall119> that's where most of LD's action links are
[18:06] <mhall119> I admit, there's some places we're not consistent
[18:07] <tiemonster> the iCal link is broken
[18:41] <mhall119> tiemonster: try again
[18:42] <tiemonster> looks good
[18:43] <mhall119> thanks
[19:06] <reya276> wow Libre Office 3 is fast
[19:07] <reya276> and they seem to have fix some of the issues that the one that originally came with 10.04 had, I can actually open a .docx file without too much document loss
[19:07] <reya276> formating
[19:08] <maxolasersquad> reya276: I'm going to switch all of my computers over tonight.  My work  machine is already switched over.
[20:01] <greiser> so check this out..... last night I was putting some final code touches on my mud codebase (custom, not some open source derived pos) and decided to load it up and give all my mobs random Good/Evil alignments and random weapons, put them all in a dungeon, and let them fight it out.....
[20:02] <greiser> Good prevailed 45% of the time.... Evil... 55% of the time...
[20:02] <greiser> so i guess it's safe to say Evil wins..
[20:03] <greiser> although my Good Knights had a tendency to Decapate a lot... they were also the highed ranked "Flee" class of all of them...
[20:03] <greiser> Peasents were more couragous...
[20:16] <dantalizing> evils wins for some algorithms ... for others, apathy wins
[20:19] <greiser> basic d&d rules with an even distribution of stat points on both sides...
[20:27] <dantalizing> doesnt change the fact that we lack the tools to accurately model the real world, esp with psuedo random "random" algorithms
[20:28] <dantalizing> greiser: does your mud use ansi esc sequences?
[20:28] <dantalizing> can I be a green-blinking hash symbol?
[20:54] <greiser> dantalizing: yes it does
[20:54] <greiser> doing random err... procedural algorithms is somewhat a specialty of mine...
[20:54] <greiser> http://www.freedom-star.com is a procedurally generated universe....
[20:55] <greiser> it's all about math, physics, and modelling real world calculations...
[20:56] <dantalizing> ok, this where the apathy part comes in
[20:56] <greiser> the tests I ran gave each character a weight, a height, the d&d values (str, int, wiz, dex, con, cha), attack ratings, weapon proficiencies, save throws, armor classes, skills, mental states, and alignments...
[20:57] <greiser> apathy does play a part
[20:57] <greiser> but that's why you can't rely on just one test run
[20:57] <dantalizing> i meant minez
[20:57] <dantalizing> that little flipping box on your site is cool
[20:57] <greiser> came with the theme...
[20:57] <greiser> :/
[20:59] <greiser> the game itself runs like a traditional mud (eventually I'll be allowing players to take part) where the game itself "pulses" 4 times a second doing calculations on everything from room scripts to mob scripts to items and events...
[20:59] <greiser> so it's a pretty decent simulation...
[20:59] <greiser> not the best.... but works...


How many letters does the word 'terminal' have?


[13:20] <ice9> does ubuntu supports ARMv6?
[13:22] <rbasak> ice9: no
[13:23] <ice9> so if I want to make Ubuntu image to run on my Android phone that has ARMv6, how do I build it?


[15:05] <iiious> Anyone can tell me the stage now of daily-live?
[21:57] <Jamie_1> i am having a problem with running steam
[22:03] <Jamie_1> anyone in here
[22:07] <Noskcaj> Jamie_1, What's the problem?
[22:07] <Noskcaj> Also, try #ubuntu if no one here knows the answer
[22:07] <Jamie_1> Noskcaj: i have installed steam and logged into the program and opens the dashboard but wont load any of the stuff other than the actual launcher window
[22:09] <Jamie_1> it ran fine on standard ubuntu
[22:10] <Noskcaj> Maybe try opening via terminal and seeing if any errors come up? i don't really know though
[22:24] <Jamie_1> Noskcaj: already tried that


[06:28] <alkisg> Hi, I'm PXE-booting some machines and I want to make 3 lists of filenames, one for each of {64bit, pae, 32bit} clients that ubuntu supports.
[06:28] <alkisg> E.g. LIST_KERNELS_64="generic-pae lowlatency-pae generic lowlatency"
[06:28] <alkisg> LIST_KERNELS_PAE="generic-pae lowlatency-pae generic lowlatency"
[06:28] <alkisg> LIST_KERNELS_32="generic lowlatency"
[06:28] <alkisg> I.e. for each client, I want to generate a pxemenu with the kernels that it can boot with (using syslinux ifcpu64).
[06:28] <alkisg> What I'm missing are the suffixes of /boot/vmlinuz-version-suffix, how can I find those? Or could someone fill the blanks for me? What other kernel suffixes exist, -server?
[06:31] <alkisg> Ah there's also "-virtual", ...
[06:36] <alkisg> Can linux-image-virtual be installed in 32bit (non-pae) systems?
[18:11] <dupondje> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/901410 fix commited for Precise, it means it should be in proposed no?
[18:11] <ubot2`> Launchpad bug 901410 in linux "[Dell XPS L502X] Applying soft block to bluetooth hard blocks wlan" [Undecided,Fix committed]
[19:07] <bjf> dupondje: "Fix committed" means the patch is in the git repo. "Fix Released" means it is at least in -proposed