[08:57] <bullgard4> How is the 'machine hardware name' defined that the command '~$ uname -m' outputs? '~$ info coreutils 'uname invocation' returns the additional information: "sometimes called the hardware class or hardware type" and does not give a definition either.


[09:14] <alkisg> Using mate 18.04 daily, right after finishing with the installation from the live cd, it says [remove cd and press enter], and I do, but shutdown doesn't work
[09:14] <alkisg> I assume systemd unmounts the squashfs live image and it blocks there waiting to read from the unmounted root device? Has anyone else seen this, should I report it?
[09:15] <alkisg> (pressing Esc at plymouth does reveal "squashfs error: unable to read metadata..." at that point)
[09:16] <alkisg> Also, isn't alt+ctrl+del 7 times supposed to reboot anyway? It doesn't...
[18:24] <flocculant> tsimonq2 acheronuk - just tried uefi oem install kubuntu - fails to get to desktop following user setup
[18:24] <flocculant> re discussion in -release
[18:24] <flocculant> just doing uefi xubuntu - I know normal xubuntu worked for both arch's over weekend
[18:33] <flocculant> that works
[18:34] <flocculant> doing bios kubuntu
[18:45]  * flocculant notes acheronuk's comment in -release
[18:46] <flocculant> I reported 2 fails on your tracker
[18:47] <acheronuk> flocculant: that's ok. I reported 2 fails for artful final
[18:48] <flocculant> don't tend to test uefi here - worked fine for us *shrug*
[18:49] <acheronuk> you don't have sddm leaving it's oem temp config file behind to mess up the user login
[18:49] <flocculant> nope :)
[18:50] <flocculant> anyway - thought I would check them - didn't know when you'd appear :)
[18:50] <acheronuk> thanks
[18:51] <flocculant> np
[19:10] <acheronuk> flocculant: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1447144
[19:14] <acheronuk> quite distressing how old that is! recent duplicates aside
[19:16] <flocculant> acheronuk: yea not so good
[19:17]  * acheronuk gently pokes cyphermox


[01:36] <tsimonq2> cjwatson: Would you happen to know where this is forked from? https://git.launchpad.net/~kubuntu-ci-admins/kubuntu-ci/+git/pangea-tooling/tree/kci/imager/ubuntu-defaults-image
[01:38] <wxl> tsimonq2: why don't you git blame it?
[01:41] <tsimonq2> wxl: Because Harald Sitter stole it, not leaving Git history :P
[01:41] <wxl> bahhhhh
[01:42] <wxl> just download every repo on lp and grep it :)
[01:43] <tsimonq2> Bahhhhhhhhh
[01:44] <wxl> i'm sure that's trivial with the lp api XD
[01:44] <tsimonq2> wxl: Better to ask the person who originally freaking wrote it ;)
[01:44] <tsimonq2> Bahhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
[02:43] <tsimonq2> infinity: Could you please give the ISO QA tracker a kick? It still doesn't show the new Lubuntu Alternate daily images
[03:00] <tsimonq2> infinity: Also, if you could, please just disable the Lubuntu Next jobs. We THOUGHT it would be used this cycle, but we had too many blockers, so these images are just wasting space at the moment.
[04:29] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate amd64 [Zesty Beta 1] (20170221.2) has been added
[04:29] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate i386 [Zesty Beta 1] (20170221.2) has been added
[04:30] <infinity> tsimonq2: ^-- Fixed.
[06:50] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (zesty-proposed/main) [4.10.0-9.11] (core, kernel)
[07:18] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (zesty-proposed) [4.10.0-9.11]
[07:21] <handsome_feng> Good morning! everyone! I'm a member of UbuntuKylin, Could someone help to deal with this bug? Bug #1663477 ,I had send an e-mail,but no reply, Thank you!
[07:29] <apw> handsome_feng, the status of that bug is really quite unclear by the end, could you add a comment at the bottom detailing the remaining packages you are trying to upload etc
[07:30] <handsome_feng> apw: I will do that soon, Thank you! :)
[07:50] <handsome_feng> hi, apw, I have added a comment, can you have a look?
[08:19] <cjwatson> tsimonq2: sounds like the ubuntu-defaults-builder package
[10:27] <xnox> apw, can you please split publish binaries generated by src:zfs-linux? bin:zfs-dracut should go into universe, instead of main.
[10:49] <apw> xnox, perhaps :)
[10:54] <apw> xnox, ahh new support, yes that seems reasonable to me
[10:55] <xnox> zfs-dracut/amd64 unsatisfiable Depends: dracut in execuses; and dracut is in universe and i think we want to keep it in universe, hence zfs-dracut should go to universe too.
[10:55] <xnox> interestingly enough zfs-initramfs is also in universe
[10:56] <apw> i think you only need that if you do root on zfs
[10:57] <apw> xnox, done
[12:52] <tsimonq2> infinity: Awesome thanks
[12:52] <tsimonq2> cjwatson: Huh? O__o
[12:52] <tsimonq2> !info ubuntu-defaults-builder zesty
[12:53] <tsimonq2> Weeeeeeeiiiiiiirrrrrrrrrdddddd.
[12:53] <tsimonq2> cjwatson: Ok, thank you.
[14:45] -queuebot:#ubuntu-release- Unapproved: mdadm (xenial-proposed/main) [3.3-2ubuntu7.1 => 3.3-2ubuntu7.2] (core) (sync)
[17:15] -queuebot:#ubuntu-release- Unapproved: fglrx-installer (trusty-proposed/restricted) [2:15.201-0ubuntu<IP_ADDRESS> => 2:15.201-0ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[17:16] -queuebot:#ubuntu-release- Unapproved: fglrx-installer-updates (trusty-proposed/restricted) [2:15.201-0ubuntu<IP_ADDRESS> => 2:15.201-0ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[19:18] -queuebot:#ubuntu-release- New source: networking-bagpipe (zesty-proposed/primary) [6.0.0-0ubuntu1]
[19:22] <barry> let's talk about gpgme1.0.  i just uploaded -3ubuntu2 but excuses indicates it blocked by freeze, which is reasonable.  it's been a long slog to get 1.8.0 to build on all archs (LP: #1647204) but -3u2 should work (i can't test s390 or powerpc in my ppa).  i also rebuilt claws-mail (a revdep) against it in my ppa and tested encryption/signing in a vm, both of which worked.  so, should we unblock gpgme1.0-3ubuntu2 and let the normal
[19:22] <barry> -proposed gate do its thing?  what other testing should be done before that (there are a bunch of other revdeps)?  or should we punt it all to zesty+1?
[19:37] <sergiusens> RAOF (or slangasek) can we let snapcraft 2.27.1 into xenial-updates and yakkety-updates? the yakkety armhf adt failure is a network timeout, the previous run timed out in a different test; can we take that into consideration?
[20:14] <slangasek> sergiusens: network timeout> why is it needing to hit a network?
[20:26] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (yakkety-proposed/main) [4.8.0-39.42] (core, kernel)
[20:30] <cyphermox> cjwatson: any idea why http://people.canonical.com/~ubuntu-archive/apt-mirror.cgi/1480648440/dists/xenial/Release would work, but not the zesty one? this timestamp should bring me to Dec 01, which should have had zesty.
[20:30] -queuebot:#ubuntu-release- New source: networking-bgpvpn (zesty-proposed/primary) [5.0.0-0ubuntu1]
[20:33] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (vivid-proposed/main) [3.19.0-82.90] (core, kernel)
[20:34] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (trusty-proposed/main) [3.13.0-110.157] (core, kernel)
[20:36] <wxl> um
[20:36] <wxl> is there a reason why the dates for Beta 1 images are all over the map?
[20:37] <wxl> some are as early as the 19th and yet i wouldn't even expect them to be made available until today
[20:37] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-64.85] (core, kernel)
[20:38] -queuebot:#ubuntu-release- New binary: linux-signed-lts-trusty [amd64] (precise-proposed/main) [3.13.0-110.157~precise1] (kernel)
[20:38] -queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-64.85~14.04.1] (kernel)
[20:38] <wxl> ^^ i guess i should direct that question at you Laney
[20:45] <sergiusens> slangasek: all of our adt tests mostly test against many upstreams
[20:46] <sergiusens> but other times, they just fail when hitting the ftp.internal deb archive
[20:46] <sergiusens> these network timeouts we seldom see on x86 fwiw
[20:55] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.8.0-39.42~16.04.1] (no packageset)
[20:58] <wxl> Laney: if there's hope that the images are not final, that would be great, because plasma 5.9.2 (bugfix release) is in release
[21:01] <wxl> acheronuk: nice! good job kubuntu team! :)
[21:06] <wxl> ugh that's the wrongc hannel
[21:11] <acheronuk> I guessed :P
[21:30] <slangasek> sergiusens: could the autopkgtest be set up to bypass the CDN using the environment variable that's now honored by snapd?
[21:30] <slangasek> sergiusens: https://bugs.launchpad.net/snappy/+bug/1653851
[21:32] <slangasek> sergiusens: at least, that looks like it would address the most recent failure... but hmm there seem to be a lot of dns resolution failures on armhf that aren't explained by a CDN issue.  So yeah, let's ignore that failure for now (though I'm also poking to see if we can get a good run)
[21:33] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (yakkety-proposed) [4.8.0-39.42]
[21:33] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (vivid-proposed) [3.19.0-82.90]
[21:33] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-64.85]
[21:33] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.8.0-39.42~16.04.1]
[21:34] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-64.85~14.04.1]
[21:34] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-110.157]
[21:34] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-trusty [amd64] (precise-proposed) [3.13.0-110.157~precise1]
[22:23] -queuebot:#ubuntu-release- Unapproved: linux-hwe (xenial-updates/main) [4.8.0-39.42~16.04.1 => 4.8.0-39.42~16.04.1] (no packageset) (sync)
[22:25] -queuebot:#ubuntu-release- Unapproved: linux-armadaxp (precise-updates/main) [3.2.0-1684.111 => 3.2.0-1684.111] (kernel) (sync)
[22:27] -queuebot:#ubuntu-release- Unapproved: accepted linux-hwe [sync] (xenial-updates) [4.8.0-39.42~16.04.1]
[22:42] -queuebot:#ubuntu-release- Unapproved: accepted linux-armadaxp [sync] (precise-updates) [3.2.0-1684.111]
[23:22] <cjwatson> cyphermox: not off the top of my head; somebody would need to poke around on snakefruit ...
[23:43] -queuebot:#ubuntu-release- Unapproved: vlc (xenial-proposed/universe) [2.2.2-5 => 2.2.2-5ubuntu<IP_ADDRESS>] (mozilla, mythbuntu)
[23:47] <Laney> wxl: Don't ask me, if you want to have a respin then that's up to you
[23:52] <tsimonq2> Laney: When I pressed the respin button (got wxl's permission to do for Kubuntu), nothing happened.
[23:52] <tsimonq2> Laney: What's the deal?


[05:27] <janimo> infinity, do you think the drivers should be purged even from git history or a regular removal commit should be ok? Is having them in .git considered redistribution?
[15:55] <ogra_> root@ubuntu:~# du -hcs /
[15:55] <ogra_> 7.0M	/
[15:55] <ogra_> yay
[15:56]  * ogra_ fiddles with his embedded rootfs builder
[15:59] <highvoltage> what's that on, ogra_?
[15:59] <ogra_> vm
[16:00] <ogra_> the target is that the tool will build you a tarball with an embedded fs
[16:00] <ogra_> no matterr what you run it on, it should work
[16:01] <ogra_> and the core rootfs shouldnt be larger than 10M (with upstart. udev etc)
[16:03] <ogra_> the system will be truely embedded thoguh, no package manager or anything
[16:06] <Guest9216> I am using ubuntu-desktop on beagleboard-xm, is there any SDK that works on it?
[16:22] <Guest9216> what package do I need to install  to my ubuntu (laptop) for the toolchain of beagleboard-xm (ubuntu-arm)? is it gcc-arm-linux-gnueabi ?
[16:23] <ogra_> well, rather gnueabihf
[16:23] <ogra_> (unless you actually want to produce armel stuff which is rather dead)
[16:24] <Guest9216> I want to compile my C code on beagleboard-xm by using eclipse or Qt-creator
[16:25] <Guest9216> I am looking for the tool chain for it, do you suggest me to install gcc-arm-linux-gnueabihf ?
[16:26] <Guest9216> uname -a outputs "Linux beagleubuntu 3.2.0-26-omap #41-Ubuntu Thu Jun 14 18:19:55 UTC 2012 armv7l armv7l armv7l GNU/Linux" on the beagleboard
[16:28] <ogra_> well, for compiling a kernel or so the gcc package should be enough ...
[16:29] <ogra_> as soon as you start doing things that need dependencies a chroot is way better
[16:31] <Guest9216> are gcc on my laptop (ubuntu-12.04) and gcc on beagleboard-xm(ubuntu-desktop) the same?
[16:31] <ogra_> if your release is the same on both
[16:32] <ogra_> the gcc for all arches in ubuntu is built from the same source package so your x86 one as well as the cross one as well as the native one on the beagle itself are identical within one release
[16:33] <Guest9216> now I see. thank you ogra_
[16:35] <ogra_> 90% of the software you write you can just develop on x86 ... unless its highly HW specific probably ... and then just rebuild it for your target arch if you are done
[16:36] <ogra_> the same as for gcc above is usually also true for libs etc so you have the same APIs on both arches
[16:37] <Guest9216> thanks a lot
[17:10] <infinity> janimo: If there's a sane way to rebase them out of existence in the git history, that would be better.
[17:10] <infinity> janimo: One of the drivers isn't even something that Marvell *can* give you permission to redistribute, since the copyright belongs to one of their partners, not them.
[22:25] <mogh> Hi, i want to get ubuntu running on my Gooseberry board
[22:25] <mogh> but all i can find is that i should extract an image onto my microSD card, but i can't seem to find any images anywhere..
[22:26] <mogh> Are there any tutorials or other resources on how to go about this?