[00:31] <xnox> Is there an "updates-excuses" page generated for xenial?
[00:35] <jbicha> xnox: um, just take the "bionic" pages and replace "bionic" with "xenial" ;)
[00:35] <xnox> jbicha, replace what in http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html ?
[00:36] <jbicha> oh I use https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html
[00:36] <xnox> ah
[00:36] <jbicha> I didn't realize there was another version!
[00:39]  * xnox is old school; the one for "devel" series was the original, the one and only.....
[00:39] <xnox> jbicha, thanks!
[00:40] <doko> infinity: why? we still need the powerpc cross build for ppc64el, and I didn't want to have -cross and -cross-ports packages in main
[00:41] <doko> slangasek: let me copy these first to a PPA before removing them
[00:42] <doko> ahh, I see what you mean
[00:54] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.17 => 2.02~beta2-36ubuntu3.18] (core)
[01:08] <doko> slangasek: what to do about the ant upload, and excuses complaining about the missing -gcj packages?
[01:10] <slangasek> doko: fix your debian/control to stop referencing binaries you don't build?
[01:11] <doko> $ grep gcj debian/control || echo no
[01:11] <doko> no
[01:24] <doko> slangasek: ^^^
[02:24] <tsimonq2> infinity, chrisccoulson: I think it'd be great to get Firefox working on armv7l-bases systems again. Could I maybe get some eyes on bug 1711337, which claims to have a solution for that?
[02:24] <ubot5`> bug 1711337 in firefox (Ubuntu) "Firefox crashes at start on armv7L after 55.0.1 update" [Undecided,Confirmed] https://launchpad.net/bugs/1711337
[02:26] <infinity> doko: Meh.  Your package, mangle it as you see fit.  Doesn't make sense to me to have weird logic just to avoid having that source in main.
[02:32] <doko> infinity: is that about ant?
[02:32] <infinity> doko: No, the gcc-defaults versus gcc-defaults-ports thing.
[02:33] <doko> ahh, ok
[02:33] <doko> already fixed
[02:46] <infinity> tsimonq2: I see no solution in that mess of a bug log.
[02:47] <infinity> And LP also won't let me comment on it.  Grr.
[02:47] <tsimonq2> infinity: Apparently, some build flags need to be enabled.
[02:47] <tsimonq2> infinity: Don't shoot the messenger, I guess. :)
[02:47] <infinity> tsimonq2: No.  That's someone shooting wildly in the dark.
[02:48] <tsimonq2> infinity: Alright.
[02:48] <infinity> tsimonq2: Those CFLAGS are literally what defines armhf as armhf.  They're the defaults.
[02:48] <tsimonq2> infinity: TIL.
[02:51] <tsimonq2> infinity: Thanks for the comment on the bug report.
[02:51] <infinity> It only took 32 tries to post it.
[02:51] <tsimonq2> I hope you're exaggerating. :P
[02:51] <infinity> Not really.  I didn't count, so I'm extrapolating, but I don't think I'm far off.
[02:52] <tsimonq2> Hah.
[02:52] <infinity> Oh, AJAX log will tell me.  I was off by a factor of 2, apparently.  16 tries.
[02:52] <tsimonq2> Wow.
[03:02] <tsimonq2> infinity: Got your axe handy? bug 1745741
[03:02] <ubot5`> bug 1745741 in pykde4 (Ubuntu Bionic) "RM: removed in Debian, working towards Qt 4 removal goal" [Medium,New] https://launchpad.net/bugs/1745741
[03:14] <tyhicks> hello! could apparmor 2.12-4ubuntu1 be let through in bionic?
[03:15] <tyhicks> I've fixed the docker.io test errors (not failures) with this upload: https://launchpad.net/ubuntu/+source/docker.io/17.03.2-0ubuntu4
[03:16] <tyhicks> however, docker.io and golang 1.10 aren't compatible (https://github.com/moby/moby/pull/35739) so docker.io won't build now that golang 1.10 is in bionic
[03:16] <tyhicks> I've asked mwhudson for guidance when he's around
[03:17] <tyhicks> as for the snapd i386 test failure, it is failing on i386 on completely random tests that differ from test run to test run
[03:17] <tsimonq2> tyhicks: Why let it through when all arches are FTBFS? :)
[03:17] <tsimonq2> Er, I'm thinking of the wrong thing, aren't I?
[03:18] <tyhicks> tsimonq2: that's docker.io that is FTBFS, not apparmor
[03:18] <tsimonq2> Yeah.
[03:18] <tyhicks> I've locally verified that my docker.io autopkgtest changes fix the docker.io test error that we were seeing
[03:32] <tsimonq2> I updated https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure for the Alioth -> Salsa migration.
[03:32] <tsimonq2> There might be other URLs that have Alioth-ish things.
[03:43] <mwhudson> tyhicks: ugh well i have a docker upgrade to review & upload
[03:48] <slangasek> doko: oh, I see, it's a case of arch: any NBS from a package that's now arch: all only.  Yeah, the only thing to be done is to manually remove the arch-dep binaries from the release pocket; done
[03:57] -queuebot:#ubuntu-release- New binary: gnome-user-docs [amd64] (bionic-proposed/main) [3.28.0-0ubuntu2] (personal-gunnarhj, ubuntu-desktop)
[04:00] <slangasek> tsimonq2: what's the story with libkf5kface? going nowhere fast in -proposed
[04:00] <slangasek> acheronuk: ^^
[04:03] <tsimonq2> slangasek: I dunno, I was more focused on nodejs, looking now.
[04:07] <slangasek> tsimonq2: k.  also, ukwm accepted and I really hope someone didn't write that debian/copyright by hand.
[04:07] <tsimonq2> ¯\_(ツ)_/¯
[04:07] -queuebot:#ubuntu-release- New: accepted ukwm [source] (bionic-proposed) [1.1.7-0ubuntu1]
[04:08] <tsimonq2> slangasek: While you're at it, bug 1745741 could use an axe.
[04:08] <ubot5`> bug 1745741 in pykde4 (Ubuntu Bionic) "RM: removed in Debian, working towards Qt 4 removal goal" [Medium,New] https://launchpad.net/bugs/1745741
[04:08] <tsimonq2> handsome_feng: ukwm accepted ^^^^^^
[04:12] <slangasek> tsimonq2: done
[04:12] <slangasek> tsimonq2, acheronuk: do you know what should be done with gpgmepp ?  Removed from unstable, but akonadi-import-wizard still build-depends on it
[04:12] <tsimonq2> slangasek: Thanks
[04:13] <slangasek> /<<PKGBUILDDIR>>/SurgSim/Blocks/DebugDumpBehavior.cpp:97:13: error: ‘cout’ is not a member of ‘std’
[04:13] -queuebot:#ubuntu-release- New binary: ukwm [s390x] (bionic-proposed/none) [1.1.7-0ubuntu1] (no packageset)
[04:13] <tsimonq2> slangasek: I'll look too
[04:13] <slangasek> ... yes, of course it's not
[04:13] <slangasek> cout is not now, nor ever has been, a member of std
[04:14] -queuebot:#ubuntu-release- New binary: ukwm [ppc64el] (bionic-proposed/none) [1.1.7-0ubuntu1] (no packageset)
[04:16] -queuebot:#ubuntu-release- New binary: ukwm [i386] (bionic-proposed/none) [1.1.7-0ubuntu1] (no packageset)
[04:17] <tsimonq2> slangasek: I *could* be wrong so I'll confirm this, but if I recall correctly, gpgmepp is an optional build dep and can be removed.
[04:18] -queuebot:#ubuntu-release- New binary: ukwm [amd64] (bionic-proposed/none) [1.1.7-0ubuntu1] (no packageset)
[04:20] -queuebot:#ubuntu-release- New binary: ukwm [arm64] (bionic-proposed/universe) [1.1.7-0ubuntu1] (no packageset)
[04:21] -queuebot:#ubuntu-release- New binary: ukwm [armhf] (bionic-proposed/universe) [1.1.7-0ubuntu1] (no packageset)
[04:22] <tsimonq2> slangasek: It'd be cool to get this merged and uploaded, then kdesudo can be removed: https://code.launchpad.net/~tsimonq2/ubuntu-release-upgrader/port-away-from-kdesudo/+merge/341555
[04:31] <handsome_feng> slangasek, tsimonq2: Thanks! \^O^/
[04:32] <tsimonq2> slangasek: gpgmepp> https://launchpad.net/ubuntu/+source/akonadi-import-wizard/17.12.3-0ubuntu2 have fun
[04:32] <tsimonq2> handsome_feng: :D
[04:32] <nacc> tjaalton: do you know who would be responsibel for LP: #1756380 ?
[04:32] <ubot5`> Launchpad bug 1756380 in intel-vaapi-driver (Ubuntu) "vaapi VP9 hardware decoding not working anymore in bionic" [Undecided,Confirmed] https://launchpad.net/bugs/1756380
[04:36] <tsimonq2> slangasek: libkf5kface> imho it'd be better to just RM it. Debian has an open RC bug that's been there since October irt it not working with a transition that's already landed. No point in continuing to have it in -proposed imho.
[04:38] <tsimonq2> slangasek: Mind sorting bug 1757043? This is a first... https://paste.ubuntu.com/p/T2rd985QRf/
[04:39] <ubot5`> bug 1757043 in Ubuntu "Sync apper 1.0.0-1 (universe) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/1757043
[04:39] <tsimonq2> (Well, a first for *me*.)
[04:59] <tsimonq2> slangasek: Reintroduction of civicrom (as previously discussed) incoming.
[04:59] -queuebot:#ubuntu-release- New source: civicrm (bionic-proposed/primary) [4.7.30+dfsg-1ubuntu1]
[05:19] <tjaalton> nacc: me probably
[06:01] <slangasek> tsimonq2: akonadi-import-wizard - cheers.  apparently I overlooked that korganizer also build-depends on it.
[06:01] <tsimonq2> slangasek: I'll do that too.
[06:06] -queuebot:#ubuntu-release- New: accepted gnome-user-docs [amd64] (bionic-proposed) [3.28.0-0ubuntu2]
[06:06] -queuebot:#ubuntu-release- New: accepted ukwm [arm64] (bionic-proposed) [1.1.7-0ubuntu1]
[06:06] -queuebot:#ubuntu-release- New: accepted ukwm [i386] (bionic-proposed) [1.1.7-0ubuntu1]
[06:06] -queuebot:#ubuntu-release- New: accepted ukwm [s390x] (bionic-proposed) [1.1.7-0ubuntu1]
[06:06] -queuebot:#ubuntu-release- New: accepted ukwm [amd64] (bionic-proposed) [1.1.7-0ubuntu1]
[06:06] -queuebot:#ubuntu-release- New: accepted ukwm [ppc64el] (bionic-proposed) [1.1.7-0ubuntu1]
[06:06] -queuebot:#ubuntu-release- New: accepted ukwm [armhf] (bionic-proposed) [1.1.7-0ubuntu1]
[06:53] <mwhudson> tyhicks: orrr you could force docker.io to build with go 1.9 i guess (b-d on golang-1.9-go, add /usr/lib/go-1.9/bin to $PATH in d/rules)
[07:00] <slangasek> tsimonq2: apper removed from blacklist; syncing it from there is up to you
[07:00] <tsimonq2> slangasek: ack
[07:05] <slangasek> doko: https://launchpad.net/ubuntu/+source/gcc-5-cross/32ubuntu1 - is that a 'no' on dropping gcc-5?
[07:08] <slangasek> Laney: were you continuing to roll out the new-style lxd setup to the armhf runners? http://autopkgtest.ubuntu.com/packages/a/adql/bionic/armhf
[07:09] -queuebot:#ubuntu-release- New sync: apper (bionic-proposed/primary) [1.0.0-1]
[07:09] <tsimonq2> slangasek: ^^^^^
[07:15] <doko> slangasek: I'd like to get this into a consistent shape first. we can discuss if we want to remove it, or move it into a PPA
[07:16] <slangasek> doko: I'm not sure who it serves to worry about old and unused compilers <shrug>
[07:17] <slangasek> if you want it in a ppa, I don't see why you wouldn't just move it to a ppa and sort it out there
[07:17] <doko> because I don't see dak's hints and excuses
[07:18] <doko> does it personally hurt you, or is it just your eyes?
[07:18] <slangasek> doko: is the time your fellow developers spend scrolling past junk in update_excuses of no value?
[07:19] <tsimonq2> *cough* merge pages
[07:19] -queuebot:#ubuntu-release- New source: peruse (bionic-proposed/primary) [1.2+dfsg-1]
[07:21] <doko> come on ... that's lame
[07:23] <tsimonq2> slangasek: libkf5kface> I don't mean to pester, but do you want a bug for this, or can you just RM it? :)
[07:24] <slangasek> tsimonq2: ah, bug preferred for that one please
[07:25] <tsimonq2> slangasek: gpgmepp> https://launchpad.net/ubuntu/+source/korganizer/4:17.12.3-0ubuntu2
[07:25] -queuebot:#ubuntu-release- New: accepted civicrm [source] (bionic-proposed) [4.7.30+dfsg-1ubuntu1]
[07:28] <tsimonq2> slangasek: I don't think bug 1757051 needs to be an FFe. Agree/disagree?
[07:28] <ubot5`> bug 1757051 in ubuntukylin-wallpapers (Ubuntu) "[FFe] Update ubuntukylin-wallpapers from 17.10.2 to 18.04.0" [Undecided,New] https://launchpad.net/bugs/1757051
[07:29] -queuebot:#ubuntu-release- New source: virtualbox-hwe (bionic-proposed/primary) [5.2.8-dfsg-5ubuntu18.04.1]
[07:29] -queuebot:#ubuntu-release- New binary: civicrm [amd64] (bionic-proposed/none) [4.7.30+dfsg-1ubuntu1] (no packageset)
[07:30] -queuebot:#ubuntu-release- New: accepted civicrm [amd64] (bionic-proposed) [4.7.30+dfsg-1ubuntu1]
[07:30] <infinity> tsimonq2: That's UIF, not FF.
[07:31] <infinity> tsimonq2: And also limited to the flavour itself, so if they want to break it, all them.
[07:31] <tsimonq2> infinity: But it's not a FFe. :P
[07:31] <acheronuk> slangasek tsimonq2: yeah, gpgmepp deps should be cleaned out
[07:31] <tsimonq2> (Or, doesn't need to be, rather.)
[07:31] <tsimonq2> acheronuk: Kool.
[07:33] <tsimonq2> handsome_feng: ^^^^ so you're fine to proceed with bug 1757051.
[07:33] <ubot5`> bug 1757051 in ubuntukylin-wallpapers (Ubuntu) "[FFe] Update ubuntukylin-wallpapers from 17.10.2 to 18.04.0" [Undecided,New] https://launchpad.net/bugs/1757051
[07:34] <tsimonq2> infinity: Anyway, thanks.
[07:37] <handsome_feng> tsimonq2: So could you help to upload this package?
[07:37] <tsimonq2> handsome_feng: Oh, absolutely.
[07:37] <tsimonq2> handsome_feng: I thought you were a member of ~ubuntukylin-dev. :)
[07:41] <handsome_feng> tsimonq2: I will apply for it :)
[07:46] <tsimonq2> handsome_feng: Uploading now; I added the LP bug number to the changelog so you know when it migrates. :)
[07:48] <handsome_feng> tsimonq2: Thanks! and could you help upload the ukui-window-switch? since the ukwm has been accepted. LP: #1741209
[07:48] <ubot5`> Launchpad bug 1741209 in Ubuntu Kylin "[FFe] ukui-window-switch" [High,New] https://launchpad.net/bugs/1741209
[07:49] <slangasek> doko: is it you that is promoting gstreamer1.0-gl to main while libgraphene-1.0-0 is still in universe?  (please don't; it breaks the daily image builds.)
[07:52] <doko> slangasek: I think I did it yesterday, showing up in component mismatches
[07:53] <slangasek> doko: ok.  it looks like there's an MIR that could use some assistance: https://bugs.launchpad.net/ubuntu/+source/graphene/+bug/1753581
[07:53] <ubot5`> Ubuntu bug 1753581 in graphene (Ubuntu) "[MIR] graphene" [Undecided,New]
[07:54] <doko> I'll have a look after the next session
[07:55] -queuebot:#ubuntu-release- New sync: ruby-logging (bionic-proposed/primary) [2.2.2-1]
[08:00] -queuebot:#ubuntu-release- New: accepted ruby-logging [sync] (bionic-proposed) [2.2.2-1]
[08:02] -queuebot:#ubuntu-release- New binary: ruby-logging [amd64] (bionic-proposed/none) [2.2.2-1] (no packageset)
[08:03] <handsome_feng> tsimonq2: I saw your messages in ubuntu-desktop, I know you are very busy now, so just go ahead with your own business and thanks again!  :)
[08:03] <tsimonq2> handsome_feng: I'm doing a few things at once, don't worry about it. ;)
[08:03] <tsimonq2> I'll review after I catch some Zs; I'm too tired to continue.
[08:05] <tsimonq2> In the meantime, your package is still uploading. I'll leave it to upload; it's a pretty big one. :)
[08:05] <tsimonq2> o/
[08:06] <handsome_feng> tsimonq2: Thanks and take care of your body!
[08:06] <tsimonq2> :)
[09:16] -queuebot:#ubuntu-release- Unapproved: pulseaudio (xenial-proposed/main) [1:8.0-0ubuntu3.8 => 1:8.0-0ubuntu3.9] (core)
[09:22] -queuebot:#ubuntu-release- New: accepted ruby-logging [amd64] (bionic-proposed) [2.2.2-1]
[09:45] -queuebot:#ubuntu-release- New source: virtualbox-hwe (bionic-proposed/primary) [5.2.8-dfsg-5ubuntu18.04.1]
[09:52] -queuebot:#ubuntu-release- New binary: ldc [ppc64el] (bionic-proposed/universe) [1:1.8.0-1] (no packageset)
[09:58] -queuebot:#ubuntu-release- New binary: ldc [i386] (bionic-proposed/universe) [1:1.8.0-1] (no packageset)
[10:00] -queuebot:#ubuntu-release- New binary: ldc [amd64] (bionic-proposed/universe) [1:1.8.0-1] (no packageset)
[10:12] -queuebot:#ubuntu-release- New binary: ldc [armhf] (bionic-proposed/universe) [1:1.8.0-1] (no packageset)
[10:43] <sergiusens> Laney: hey there, I am having issues with upstream triggers of autopkgtests, they trigger fine, but they don't seem to report back (no idea where the issue is) e.g; https://github.com/snapcore/snapcraft/pull/2008 has a state of running, I saw them running on http://autopkgtest.ubuntu.com/running#pkg-snapcraft but then they just went away
[10:45] <Laney> sergiusens: Some slight downtime atm due to gnupg dropping off the standard install
[10:45] <sergiusens> Laney: so to line up events, is this issue from before yesterday?
[10:46] <Laney> I think it happened last night
[10:54] <Laney> sergiusens: oh ok, this is something different
[10:54] <Laney> if you go to the raw index https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-snappy-dev-snapcraft-daily/?format=plain&prefix=xenial/amd64/s/snapcraft/
[10:54] <Laney> and pick one of the most recent results, e.g<EMAIL_ADDRESS>[10:54] <Laney> it's complaining about this patchelf dependency
[10:56] <Laney> I'm not sure why that doesn't report back as a failure though
[11:01] <sergiusens> Laney: doesn't autopkgtest run with -proposed enabled?
[11:01] <sergiusens> Laney: patchelf (0.9-1~...) is in xenial-proposed. As a side comment, we have the same issue when trigerring from bionic https://github.com/snapcore/snapcraft/pull/2010
[11:08] <sergiusens> Laney: like this one<EMAIL_ADDRESS>[11:11] <Laney> sergiusens: I kicked the status reporter, they are marked as failed now
[11:12] <sergiusens> Laney: ty! Even more so, for the link with the list of runs; that solves a bunch of problems for me :-)
[11:12] <Laney> and no, no proposed unless it's asked for as part of the request
[11:12] <Laney> sergiusens: nice, you can replace plain with json too if you want to parse it for any reason
[11:12] <sergiusens> Laney: so my followup question is, how to I get patchelf from -proposed in my xenial runs?
[11:14] <Laney> it's been 10 days, so verify the SRU and get sil210_0 to release it ;-)
[11:14] <Laney> 7*
[11:15] <sergiusens> Laney: hah, I wanted to use our snapcraft autopkgtest as part of verification for that though
[11:15] <Laney> oh, well... copy it to the PPA you're using?
[11:17] <Laney> copy-package --from=ubuntu --to=\~snappy-dev/ubuntu/snapcraft-daily --from-suite=xenial-proposed --to-suite=xenial --include-binaries patchelf
[11:19] <Laney> good news for snapcraft too is once I get armhf back online it'll be using stgraber's new secret sauce to hopefully make the tests work
[11:21] <sergiusens> Laney: good deal, thanks!
[11:21] <sergiusens> Laney: so the dns timeouts have been worked out?
[11:21] <Laney> that's the hope
[11:22] <Laney> we did a manual test run and it went through without timing out
[11:23] <sergiusens> nice, I will keep an eye on it; was the fix in lxd itself?
[11:23] -queuebot:#ubuntu-release- New source: virtualbox-hwe (bionic-proposed/primary) [5.2.8-dfsg-5ubuntu18.04.1]
[11:23] <Laney> using a newer lxd and changing the networking setup a bit
[11:23] <Laney> like using the upstream DNS server directly
[11:23] <Laney> https://git.launchpad.net/autopkgtest-cloud/commit/?id=6979684bcc9a5c9425756e8910c00b251f4c2048
[11:24] <sergiusens> this is good news; I am glad this was looked into :-)
[11:30] <Laney> :>
[11:32] <Laney> all back up now
[11:35] <Laney> slangasek: all redeployed, turned out that changing the priority on gpg broke an assumption in autopkgtest so I took the chance to burn it to the ground and start again while fixing that
[12:04] <xnox> apw, at https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1749771 and I have out of bound confirmation that stakeholder sign-off was done, is that bug ready to have "block-proposed" tag removed?
[12:04] <ubot5`> Ubuntu bug 1749771 in Kernel Development Workflow "linux-azure: 4.15.0-1002.2 -proposed tracker" [Medium,In progress]
[12:04] <xnox> apw, I am confused about brad adding "regression-testing-passed" tag, yet still having "Automated-testing: confirmed"
[12:06] <tjaalton> does ubuntu care about "sourceless files", like shaders in intel-vaapi-driver? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867340
[12:06] <ubot5`> Debian bug 867340 in i965-va-driver "Contains binary files without corresponding source" [Serious,Fixed]
[12:06] <apw> xnox, regression-testing-passed is unrelated to automated-testing
[12:06] <xnox> apw, ah! so i thought =)
[12:06] <tjaalton> this split probably broke the driver, partially
[12:06]  * xnox 's hunch was correct
[12:06] <apw> xnox, it is related to regression-testing only
[12:06] <xnox> tjaalton, is that shipped in restricted/multiverse?
[12:07] <tjaalton> so I'm wondering if the split should be undone for bionic
[12:07] <tjaalton> xnox: the driver isn't
[12:07] <tjaalton> i65-va-driver-shaders is
[12:07] <tjaalton> i965-
[12:07] <apw> xnox, and you never remove the block-proposed tag, that is shanky's job
[12:07] <apw> xnox, it is pending the ADT testing passing
[12:08] <xnox> tjaalton, you may need AA review on that. E.g. we pushed linux-firmware into main. But i would hope we can keep shaders in restricted/multiverse (source-less should be fine)
[12:08] <tjaalton> xnox: alright
[12:10] <tjaalton> well, the option would be to un-split it and ship in restricted
[12:10] <tjaalton> oh, the driver is in universe, so multiverse then
[12:11] <tjaalton> weird, I thought it was seeded
[12:46] <Mirv> I think the driver has not been, although it would naturally be better if it was as otherwise most people won't get hw acceleration. that's one of the first things I install on a new install.
[13:03] -queuebot:#ubuntu-release- New: accepted apper [sync] (bionic-proposed) [1.0.0-1]
[13:03] -queuebot:#ubuntu-release- New: accepted ldc [armhf] (bionic-proposed) [1:1.8.0-1]
[13:03] -queuebot:#ubuntu-release- New: accepted ldc [ppc64el] (bionic-proposed) [1:1.8.0-1]
[13:03] -queuebot:#ubuntu-release- New: accepted ldc [amd64] (bionic-proposed) [1:1.8.0-1]
[13:03] -queuebot:#ubuntu-release- New: accepted peruse [source] (bionic-proposed) [1.2+dfsg-1]
[13:03] -queuebot:#ubuntu-release- New: accepted ldc [i386] (bionic-proposed) [1:1.8.0-1]
[13:04] <tjaalton> Mirv: iirc it's installed if the checkbox to install some codecs etc is checked
[13:05] <tjaalton> Mirv: fyi, I have a package ready to go to multiverse/video
[13:06] -queuebot:#ubuntu-release- New binary: peruse [s390x] (bionic-proposed/none) [1.2+dfsg-1] (no packageset)
[13:06] -queuebot:#ubuntu-release- New binary: apper [s390x] (bionic-proposed/none) [1.0.0-1] (no packageset)
[13:08] -queuebot:#ubuntu-release- New binary: apper [i386] (bionic-proposed/none) [1.0.0-1] (no packageset)
[13:08] -queuebot:#ubuntu-release- New binary: peruse [ppc64el] (bionic-proposed/none) [1.2+dfsg-1] (no packageset)
[13:08] -queuebot:#ubuntu-release- New binary: peruse [amd64] (bionic-proposed/none) [1.2+dfsg-1] (no packageset)
[13:09] -queuebot:#ubuntu-release- New binary: apper [ppc64el] (bionic-proposed/none) [1.0.0-1] (no packageset)
[13:09] -queuebot:#ubuntu-release- New binary: peruse [i386] (bionic-proposed/none) [1.2+dfsg-1] (no packageset)
[13:11] -queuebot:#ubuntu-release- New binary: apper [amd64] (bionic-proposed/none) [1.0.0-1] (no packageset)
[13:13] -queuebot:#ubuntu-release- New binary: peruse [arm64] (bionic-proposed/none) [1.2+dfsg-1] (no packageset)
[13:16] -queuebot:#ubuntu-release- New binary: peruse [armhf] (bionic-proposed/none) [1.2+dfsg-1] (no packageset)
[13:18] -queuebot:#ubuntu-release- New binary: apper [arm64] (bionic-proposed/none) [1.0.0-1] (no packageset)
[13:18] -queuebot:#ubuntu-release- New binary: apper [armhf] (bionic-proposed/none) [1.0.0-1] (no packageset)
[13:26] -queuebot:#ubuntu-release- New source: pyxs (artful-proposed/primary) [0.4.1+dfsg1-0ubuntu1~17.10.0]
[13:26] -queuebot:#ubuntu-release- New source: pyxs (xenial-proposed/primary) [0.4.1+dfsg1-0ubuntu1~16.04.0]
[13:29] -queuebot:#ubuntu-release- New source: rax-nova-agent (artful-proposed/primary) [2.1.12-0ubuntu2~17.10.0]
[13:29] -queuebot:#ubuntu-release- New source: rax-nova-agent (xenial-proposed/primary) [2.1.12-0ubuntu2~16.04.0]
[13:49] <Mirv> tjaalton: great for the latter! and oh, ok for the former, I usually don't check the checkbox since at some point it installed restricted-extras which included things I don't want like ms truetype fonts.
[13:57] <LocutusOfBorg> please apw sil2100 review virtualbox-hwe in bionic :(
[13:57] <LocutusOfBorg> :)
[13:58] <LocutusOfBorg> it is the same tarball of the already released one, so it should be a quick accept
[13:59] -queuebot:#ubuntu-release- Unapproved: avahi (artful-proposed/main) [0.6.32-1ubuntu1 => 0.6.32-1ubuntu1.1] (core)
[14:00] <coreycb> hello release team, bug 1757141 should unblock horizon and other openstack dashboards from proposed migration
[14:00] <ubot5`> bug 1757141 in python-django-openstack-auth (Ubuntu) "[RM] Package needs to be removed in Bionic" [Undecided,New] https://launchpad.net/bugs/1757141
[14:02] <tyhicks> mwhudson: thanks - I'll give that a shot
[14:07] -queuebot:#ubuntu-release- Unapproved: avahi (xenial-proposed/main) [0.6.32~rc+dfsg-1ubuntu2 => 0.6.32~rc+dfsg-1ubuntu2.1] (core)
[14:09] -queuebot:#ubuntu-release- Unapproved: avahi (trusty-proposed/main) [0.6.31-4ubuntu1.1 => 0.6.31-4ubuntu1.2] (core)
[14:29] <sil2100> LocutusOfBorg: I might take a look at it a bit later - what is it's purpose in bionic?
[14:30] <juliank> probably upgrades from xenial
[14:30] -queuebot:#ubuntu-release- Unapproved: grub2-signed (xenial-proposed/main) [1.66.17 => 1.66.18] (core)
[14:50] <LocutusOfBorg> sil2100, exactly, people having vbox-hwe in xenial, should move to vbox-hwe in bionic
[14:50] <LocutusOfBorg> that right now it is just a new binary identical with the virtualbox, but in the future, will start tracking real hwe packages
[14:51] <LocutusOfBorg> (right now it tracks the xserver-xorg-hwe-16.04 package)
[14:52] <sil2100> Ok, that's what I thought then, I'll need a few more minutes before looking into that though
[14:52] <slangasek> Laney: ok. was the DNS resolution failure I linked above before or after the redeploy, then?
[14:53] <Laney> slangasek: I did it today
[14:53] <slangasek> Laney: ack
[14:53] <Laney> did someone clean up priority mismatches or something?
[14:55] <apw> Laney, looks to be lots of bits on there to me
[14:56] <Laney> apw: yeah, can't see the graph though
[15:02] <slangasek> well, I hope someone didn't clean up priority-mismatches by promotions
[15:03] <slangasek> those libs all need to be dropped back out; I talked to xnox about it
[15:03] <xnox> hmmm
[15:03] <xnox> slangasek, boost?
[15:04] <slangasek> xnox: libunistring->harfgraphite->dns->freetype
[15:04] <slangasek> or something
[15:04] <xnox> ah, yes.
[15:04] <xnox> i should totally do this asap.
[15:16] <nacc> tjaalton: thanks for the updates on that bug; particularly noisy user
[15:17] <coreycb> bdmurray: we should be all set to promote to updates for bug 1755027 and bug 1747065
[15:17] <ubot5`> bug 1755027 in trove-dashboard (Ubuntu Artful) "[SRU] local_settings.py is world readable and contains passwords" [Critical,Fix committed] https://launchpad.net/bugs/1755027
[15:17] <ubot5`> bug 1747065 in nova (Ubuntu Artful) " [SRU] pike stable releases" [Undecided,Fix committed] https://launchpad.net/bugs/1747065
[15:23] <bdmurray> coreycb: and you wanted 1755027 expedited (released in less than 7 days) correct?
[15:23] <coreycb> bdmurray: yes please if possible
[15:36] -queuebot:#ubuntu-release- New sync: deepin-terminal (bionic-proposed/primary) [2.9.2-1]
[15:44] -queuebot:#ubuntu-release- New sync: deepin-screenshot (bionic-proposed/primary) [4.0.11-1]
[16:00] <tsimonq2> Can I get the apper binaries accepted please?
[16:00] -queuebot:#ubuntu-release- New binary: mongodb [s390x] (bionic-proposed/universe) [1:3.4.7-1ubuntu3] (mozilla)
[16:05] <cjwatson> tsimonq2: done
[16:05] <tsimonq2> cjwatson: Thanks.
[16:06] -queuebot:#ubuntu-release- New: accepted apper [amd64] (bionic-proposed) [1.0.0-1]
[16:06] -queuebot:#ubuntu-release- New: accepted apper [armhf] (bionic-proposed) [1.0.0-1]
[16:06] -queuebot:#ubuntu-release- New: accepted apper [ppc64el] (bionic-proposed) [1.0.0-1]
[16:06] -queuebot:#ubuntu-release- New: accepted apper [arm64] (bionic-proposed) [1.0.0-1]
[16:06] -queuebot:#ubuntu-release- New: accepted apper [s390x] (bionic-proposed) [1.0.0-1]
[16:06] -queuebot:#ubuntu-release- New: accepted apper [i386] (bionic-proposed) [1.0.0-1]
[16:17] <slangasek> tsimonq2: you're going to file a bug on libkf5kface?
[16:19] <tsimonq2> slangasek: I'll get to it as soon as I can, unless ofc you want to JFDI (the bug report won't say much).
[16:21] <slangasek> tsimonq2: because this is a new upstream version not present in Debian of a package maintained by the kubuntu team, I would prefer an audit trail before I whack it
[16:31] <tsimonq2> slangasek: bug 175720
[16:31] <ubot5`> bug 175720 in memtest86+ (Ubuntu) "ELF image not installed anywhere, would be useful" [Undecided,Fix released] https://launchpad.net/bugs/175720
[16:31] <tsimonq2> ger
[16:31] <tsimonq2> bugg 175720
[16:31] <tsimonq2> ...
[16:31] <tsimonq2> I hate this keyboard
[16:31] <tsimonq2> bug 175720
[16:31] <tsimonq2> Ok, just add a 1 at the end, ugh...
[16:31] <tsimonq2> Sorry
[16:32] <slangasek> tsimonq2: only bug open on the package, very findable ;)
[16:33] <tsimonq2> Hah.
[16:33] <tsimonq2> True.
[16:33] <tsimonq2> Thanks slangasek.
[16:43] <acheronuk> slangasek: hi. I have new libqapt and Muon package manager release for KDE, but with these changes: https://mail.kde.org/pipermail/kde-announce-apps/2018-March/005433.html
[16:44] <acheronuk> so nearly all bugfix, but one alleged 'feature' which you could argue the toss on
[16:45] <slangasek> acheronuk: I am therefore not going to argue it - please go ahead
[16:46] <acheronuk> slangasek: great. thank you
[16:52] <tsimonq2> slangasek: Mind accepting peruse binaries?
[16:52] <slangasek> tsimonq2: I was about to ping you asking why this has a -1 version number
[16:53] <tsimonq2> slangasek: uhm wat
[16:53] <slangasek> it's not a Debian sync and it has a -1?
[16:53] <tsimonq2> Yeah I messed that up... shoot.
[16:54] <slangasek> and why did an AA accept it in that state ;)
[16:54] <tsimonq2> ¯\_(ツ)_/¯
[16:54] <tsimonq2> It's the same thing that's going to go into Debian
[16:54] <slangasek> except it's not synced from Debian, and it's not guaranteed to be accepted into Debian with identical contents
[16:54] <slangasek> I: peruse: no-symbols-control-file usr/lib/x86_64-linux-gnu/libacbf.so
[16:54] <tsimonq2> True.
[16:55] <slangasek> so somebody accepted that, ah?
[16:55] <tsimonq2> ¯\_(ツ)_/¯
[16:55] <slangasek> W: peruse: appstream-metadata-in-legacy-location usr/share/appdata/org.kde.perusecreator.appdata.xml
[16:55] <tsimonq2> I thought you were going to review it so we could discuss the best path forward for libacbf.so
[16:56] <tsimonq2> i.e. if it's fine as is
[16:56] <slangasek> well, I suggested that someone should find my previous reject message so I could remember what the actual reason was that I rejected it
[16:56] <acheronuk> tsimonq2 would have got that email
[16:56] <tsimonq2> I couldn't find it
[16:57] <slangasek> k
[16:57]  * acheronuk goes back to lurking
[16:57] <slangasek> in any event, I don't know who accepted the source this time because there's no audit logs of that either
[16:58] <tsimonq2> Maybe they thought I was just fakesyncing it.
[16:58] <apw> doesn't sound like anything i was involved in
[16:58] <tsimonq2> Anyway
[16:58] <tsimonq2> slangasek: What now?
[16:59] <slangasek> tsimonq2, acheronuk: this version still has the wrong lintian overrides about libacbf.so.  Please just drop these instead of suppressing lintian's correct complaints.
[16:59] <slangasek> but I don't see anything here that should block binary NEW
[17:00] <tsimonq2> slangasek: How would I go about fixing these correct complaints?
[17:00] <tsimonq2> These are new errors to me.
[17:00] -queuebot:#ubuntu-release- New: accepted peruse [amd64] (bionic-proposed) [1.2+dfsg-1]
[17:00] -queuebot:#ubuntu-release- New: accepted peruse [armhf] (bionic-proposed) [1.2+dfsg-1]
[17:00] -queuebot:#ubuntu-release- New: accepted peruse [ppc64el] (bionic-proposed) [1.2+dfsg-1]
[17:00] -queuebot:#ubuntu-release- New: accepted peruse [arm64] (bionic-proposed) [1.2+dfsg-1]
[17:00] -queuebot:#ubuntu-release- New: accepted peruse [s390x] (bionic-proposed) [1.2+dfsg-1]
[17:00] -queuebot:#ubuntu-release- New: accepted peruse [i386] (bionic-proposed) [1.2+dfsg-1]
[17:00] <slangasek> tsimonq2: it's a private module; it shouldn't be shipped in /usr/lib/<arch>/ but in /usr/lib/<arch>/<package>
[17:01] <slangasek> and the source adjusted if necessary to find it there
[17:01] <tsimonq2> OK.
[17:01] <tsimonq2> I'll fix that.
[17:02] <tsimonq2> Thanks slangasek.
[17:08] -queuebot:#ubuntu-release- New binary: mongodb [amd64] (bionic-proposed/universe) [1:3.4.7-1ubuntu3] (mozilla)
[17:27] <slangasek> tsimonq2, acheronuk: qt-gstreamer is stuck in -proposed because of ktp-call-ui and telepathy-logger-qt5; ktp-call-ui has a newer upstream version in unstable, should this be synced to fix?
[17:27] <slangasek> (and telepathy-logger-qt5 is Ubuntu-specific with no revdeps)
[17:28] <tsimonq2> Looking.
[17:28] <slangasek> (and I've already filed a bug about telepathy-logger-qt5, LP: #1747605, so will probably axe that as soon as ktp-call-ui is sorted)
[17:28] <ubot5`> Launchpad bug 1747605 in telepathy-logger-qt5 (Ubuntu) "telepathy-logger-qt5: not compatible with qt-gstreamer5" [Critical,New] https://launchpad.net/bugs/1747605
[17:31] <tsimonq2> slangasek: uhm, ktp-call-ui is newer in Ubuntu? :)
[17:31] <tsimonq2> !info ktp-call-ui
[17:31] <ubot5`> Package ktp-call-ui does not exist in bionic
[17:32] <tsimonq2> er
[17:32] <tsimonq2> whatever
[17:32] <slangasek> tsimonq2: oh sorry, I had only queried its status from an artful machine, oops
[17:33] <tsimonq2> slangasek: The RC bug open in Debian looks relevant.
[17:33] <tsimonq2> I'm on mobile and can take a look later unless acheronuk wants to.
[17:38] <tjaalton> could someone ack/nack bug 1755717
[17:38] <ubot5`> bug 1755717 in xcb-proto (Ubuntu) "FFE: xcb-proto/libxcb 1.13" [Undecided,New] https://launchpad.net/bugs/1755717
[17:42] <acheronuk> !info kde-telepathy-call-ui
[17:42] <ubot5`> kde-telepathy-call-ui (source: ktp-call-ui): KDE Telepathy UI for audio/video calls. In component universe, is optional. Version 17.12.3-0ubuntu1 (bionic), package size 186 kB, installed size 876 kB
[17:47] <tsimonq2> Yeah.
[17:55] <acheronuk> doing now
[18:36]  * LocutusOfBorg does the ldc rebuilds
[18:37] -queuebot:#ubuntu-release- New binary: mongodb [arm64] (bionic-proposed/universe) [1:3.4.7-1ubuntu3] (mozilla)
[20:12] <mwhudson> tyhicks: that seems to have worked
[20:14] <tyhicks> mwhudson: yes, it did - thanks for the suggestion!
[20:15] <tyhicks> mwhudson: I left a big fat comment in debian/control so that you'll catch the hard-coded golang version and remember the debian/rules change when you bring bionic's docker.io back to artful and xenial
[20:16] <tyhicks> (xenial will be obvious because it'll FTBFS since golang-1.9 doesn't exist)
[20:16] <mwhudson> tyhicks: thanks
[20:18] <slangasek> tsimonq2: "the RC bug open in Debian" - which package were you referring to with that?  no open RC bugs on ktp-call-ui
[20:20] <tsimonq2> slangasek: https://bugs.debian.org/886943
[20:20] <ubot5`> Debian bug 886943 in libtelepathy-qt5-0 "libtelepathy-qt5-0: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE" [Serious,Fixed]
[20:20] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (xenial-proposed/main) [2.408.27 => 2.408.28] (desktop-core)
[20:23] <slangasek> tsimonq2: ah; relevant in the sense that it would be nice to get that fixed by migrating the package currently in -proposed...
[20:24] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.28]
[20:25] <tsimonq2> slangasek: Yeah.
[20:25] <tsimonq2> Heh.
[20:30] <nacc> slangasek: i think fusionforge in bionic-proposed needs an AA nudge; I removed those plugins becasue they depend on a no longer packaged php packages
[20:31] <slangasek> nacc: ack, NBS in -proposed requires manual attention; cleaning up now
[20:32] <nacc> slangasek: thanks
[21:13] <tsimonq2> For general recordkeeping I guess, I'll look into sbuild a bit later, but it needs a hard dep on lintian.
[21:13] <tsimonq2> nodejs is going to need some work, help would be appreciated on that.
[21:14] <tsimonq2> nodejs> Not too bad, just skimming things there's *maybe* ten packages with regressed autopkgtests.
[21:32] <nacc> slangasek: thank you for the assist on fusionforge
[21:33] <slangasek> nacc: n/p
[21:33] <slangasek> nacc: always happy to delete php packages for you, binary or otherwise ;-)
[21:38] <nacc> slangasek: heh
[22:36] -queuebot:#ubuntu-release- New binary: ubuntukylin-wallpapers [amd64] (bionic-proposed/universe) [18.04.0] (ubuntukylin)
[22:38] <tsimonq2> Can someone let that binary through? ^^^^
[22:38] <tsimonq2> That took me *three* tries to upload.
[22:38] <tsimonq2> 167 MB diff...


[19:30] <xu-contribute23w> Hi
[19:30] <xu-contribute23w> Is the finish guy still the one in charge for development work?
[19:30] <xu-contribute23w> Finnish guy


[04:00] <twb> 20:31 <lilstevie> twb, did you get that?
[04:00] <twb> lilstevie: I did now :-)
[04:00] <twb> 19:32 <twb`> What does "ld: no machine record defined" mean?
[04:00] <twb> lilstevie: any idea about that one?
[04:01] <lilstevie> none
[04:01] <twb> Dammit
[04:01] <lilstevie> never seen ld trip on that before
[04:01] <twb> I suspect it's something hf-related
[04:01] <lilstevie> maybe
[04:47] <travalas> Hello, I'm having trouble getting anything on the USB bus to show up with ubuntu on a beagle board.  I've tried two different versions of the prebuilt ubuntu and neither of them work.  It seems to be fine under angstrom.  Thoughts?
[04:48] <tmzt> it's an error from the linxu kernel source
[04:48] <tmzt> not ld
[04:48] <tmzt> it's intentional, means you haven't enabled a machine
[04:49] <tmzt> so it cant' find a certain section in the image
[05:01] <travalas> somebody mentioned that it might be a problem with USB_POWER_EN
[05:01] <travalas> anybody have any pointers?
[05:07] <twb`> tmzt: please explain, or tell me what docs I should be reading; "enable machine" is too vague for me to work out what to do
[05:08] <twb`> Googling for either that or the error isn't helping, and the .S that refers to the error just says "if you get this, your binutils is too old" -- which I doubt
[05:08] <twb`> GNU ld (GNU Binutils for Debian) <IP_ADDRESS>10910
[05:11] <lilstevie> twb`: MACH_whatever isn't enabled
[05:12] <twb`> I don't know what that means.
[05:13] <twb`> You mean like MACH_TEGRA ?
[05:13] <twb`> Would it be getting the "whatever" part from .config, or what?
[05:14] <lilstevie> yeah
[05:14] <lilstevie> like MACH_VENTANA
[05:15] <twb`> http://paste.debian.net/129908/
[05:16] <lilstevie> where is MACH_PICASSO
[05:17] <twb`> I turned it off because it didn't make sense to me :P
[05:17] <twb`> TF101 isn't an AC500
[05:17] <lilstevie> but I told you they were mutually exclusive
[05:18] <twb`> How do you mean mutually exclusive?
[05:18] <lilstevie> muromec should have put depends=CONFIG_MACH_PICASSO on MACH_TF101
[05:18] <lilstevie> board-picasso contains what is needed for the tf101
[05:18] <twb`> OK, so it's just me being stupid, I will try turning PICASSO on again
[05:19] <lilstevie> you really shouldn't turn turn off things in the config without making sure :)
[05:19] <lilstevie> arm is a lot different to x86 :p some things that don't make sense are enabled for unknown reasons :)
[05:19] <lilstevie> well appear to be unknown
[05:19] <lilstevie> until you dig
[05:20] <twb`> I was mislead by the Kconfig help string
[05:31] <twb`> OK, now it passed the spot where it stopped before.  Yay.
[05:43] <twb`> lilstevie: so what is the process to get u-boot onto the tf?  I guess step #1 is to git clone u-boot?
[05:43] <twb`> Hmm, apt-get install u-boot u-boot-tools
[05:54] <lilstevie> correct flash config, build u-boot, correct flash config
[05:54] <lilstevie> installing u-boot like that wouldn't work :p
[05:54] <lilstevie> u-boot is not generic
[05:55] <twb`> Well, obviously once I apt-get install the tools I need to use them to generate an image and nvflash it onto the device or something
[05:56] <twb`> lilstevie: does turning VFP on mean that hard-float is off?
[05:57] <twb`> Oh V is for vector not virtual
[05:59] <lilstevie> VFP is central to hardfloat :p
[06:00] <lilstevie> as for the tools, they are more for making the right images for initrd and kernel image
[06:00] <lilstevie> but the kernel image is already one
[06:00] <lilstevie> done
[06:00] <lilstevie> if you make with 'make uImage'
[06:01] <twb`> But if I do "make uImage", how does the initrd get into the image
[06:01] <twb`> Or can u-boot just find the kernel and ramdisk in /boot like an x86 bootloader
[06:01] <lilstevie> when using uboot you dont put the initrd in the image
[06:01] <lilstevie> you have a uImage and a uInitrd
[06:03] <twb`> Aha, on amd64 "apt-get install u-boot" gives you a useless empty package, but on armhf I can see it providing stuff for other arm systems (efika, omap3, etc)
[06:04] <tmzt> anybody know a fast way to byte swap values in c?
[06:04] <tmzt> use the networking functions to do it?
[06:04] <tmzt> I'm trying to dump a uimage file as it's parts (it's a multi uncompressed)
[06:23] <twb`> Poking around in the u-boot git tree, I can see "make harmony_config" and "make seaboard_config" but nothing else pointing at include/config/tegra2-common.h
[06:24] <twb`> And I see now that "make uImage" in linux will run u-boot-tools' "mkimage" internally.
[06:25] <lilstevie> make ventana CROSS_COMPILE=cross-compiler-arm DEV_SRC_TREE="tegra-tf101"
[06:25] <twb`> In the u-boot source?
[06:26] <lilstevie> yes
[06:26] <twb`> make: *** No rule to make target `ventana'.  Stop.
[06:29] <lilstevie> hmbleh
[06:29] <lilstevie> i dont remember look on the xda board
[06:29] <lilstevie> somewhere in general muromecs thread has the info
[06:29] <twb`> I never got the hang of web forums, but I'll try
[06:32] <twb`> Looks like xda-developers has a robots.txt or something that gives preferential treatment to google over duckduckgo :-/
[06:33] <twb`> http://forum.xda-developers.com/showthread.php?t=1202541 suggests ventana_config, /me tries
[06:33] <lilstevie> thats it
[06:34] <twb`> And it looks like he has a fork of u-boot so maybe I need to use that instead of mainline u-boot
[06:34] <lilstevie> I didn't do the port so I don't remember
[06:34] <lilstevie> oh yeah it isn't in mainline
[06:39] <twb`> Waah
[06:40] <twb`> /usr/src/u-boot/lib/sha1.c:228:1: internal compiler error: in maybe_add_or_update_dep_1, at sched-deps.c:845
[09:53] <ogra_> janimo, so we should check what files we actually have for mx5
[09:53] <ogra_> i suspect its just the publishing/html generating code that has a hiccup
[09:53] <ogra_> and that the image is actually fine
[09:53] <janimo> ogra_, we should only have the .gz I guess. The first test runs did not produce iso, just the sep 14 run
[09:54] <janimo> which was not manual so likely the setup needs to be changed a bit
[09:54] <ogra_> it is still an img.gz, the code generating the suffix actually uses file on the unzipped file
[09:54] <janimo> but it is 1.5G
[09:55] <janimo> is there a build of mx5 with the uboot file being found?
[09:55] <ogra_> bah, i'm blind
[09:55] <ogra_> we have both !
[09:55] <janimo> right, when I meant we have iso I meant in addition, not instead, should have worded better :)
[09:55]  * ogra_ only saw the img.gz and img.gz.zsync files
[09:55] <ogra_> well, i could have looked better :)
[09:56] <ogra_> so get a dvd reader then ...
[09:57] <ogra_> Calling uboot-mkimage on kernel and initrd
[09:57] <ogra_> mkimage: Can't open /srv/cdimage.ubuntu.com/scratch/ubuntu/daily-preinstalled/preinstalled/armel+mx5.kernel-mx5: No such file or directory
[09:57] <ogra_> make: *** [bin-preinstalled_images] Error 1
[09:57] <ogra_> so why do we have that .iso file there
[09:57] <ogra_> ARGH !!!!!!!
[09:57] <ogra_> Calling uboot-mkimage on kernel and initrd
[09:57] <ogra_> mkimage: Can't open /srv/cdimage.ubuntu.com/scratch/ubuntu/daily-preinstalled/preinstalled/armel+mx5.kernel-mx5: No such file or directory
[09:57] <ogra_> make: *** [bin-preinstalled_images] Error 1
[09:57] <ogra_> err
[09:57] <ogra_> wrong paste
[09:57] <ogra_> Publishing armel+mx5 ...
[09:57] <ogra_> WARNING: Unknown file type 'Linux rev 1.0 ext3 filesystem data, UUID=2e4ade6f-20c2-4670-9475-51fe999a8d0e'; assuming .iso
[09:57] <ogra_> Making armel+mx5 zsync metafile ...
[09:58] <ogra_> grnbl
[09:59] <ogra_> gah
[10:00] <ogra_> so the live builder produces: livecd.ubuntu-mx5.kernel-linaro-lt-mx5
[10:01] <ogra_> http://annonaceae.buildd/~buildd/LiveCD/oneiric/ubuntu-mx5/current/livecd.ubuntu-mx5.kernel-mx5:
[10:01] <ogra_> 2011-09-14 04:45:47 ERROR 404: Not Found.
[10:01] <ogra_> hmpf
[10:01] <ogra_> more hacks ahead
[10:04] <ogra_> janimo, i assume we dont want to rename mx5 to linaro-lt-mx5 all over the place ?
[10:05] <janimo> no, mx5 should be fine and much less confusing
[10:05] <janimo> lt-linaro is just the designation of the kernel origin
[10:06] <ogra_> right, live-build cant handle cases where the subarch name isnt identical to the kernel name suffix
[10:07] <ogra_> though that it assumes iso for ext3 is really weird
[10:09] <ogra_> ah, k, the iso is a fallout of the missing kernel
[10:24] <ogra_> hmm, i really fail to find the code in live-build that actually creates livecd.ubuntu-mx5.kernel-mx5
[10:41] <ogra_> janimo, i fear we need infinity ... i can stare at the code for another two hours to find out where to put a proper hack, but i guess he will be faster ...
[10:41] <janimo> indeed
[10:42] <ogra_> and i dont really feel comfortable to mangle the LB_LINUX_FLAVOURS variable during the build since all arches use it
[10:42] <ogra_> and i guess thats the wrong approach anyway
[10:43]  * ogra_ wonders if he could instead do a hack on the cdimage side
[10:56] <ogra_> janimo, i got a testbuild running with a hack in cdimage, lets see
[11:11] <twb> lilstevie: I'm going home now, but I have typed up what I've learnt up to about last sunday: http://cyber.com.au/~twb/doc/tf101.txt (source) tf101.html (rendered)
[11:11] <twb> Comments, fixes, etc. welcome.
[11:13] <lilstevie> twb: well I can tell you why the bootloader needs to be uploaded :)
[11:14] <twb> No honest, I'm going home.  Email me or something.  /me runs
[11:14] <lilstevie> heh
[11:14] <lilstevie> sure you are
[11:15] <lilstevie> there are some fixes I will write later
[11:15] <lilstevie> I kinda have a 1500 word essay due tomorrow which I only just started
[11:19] <travalas> i'm trying to get ubuntu working on my beagle board xM rev c, but nothing on the USB bus seems to be working.  Somebody mentioned looking at USB_POWER_EN.  But I haven't been able to track down much on that issue.  Does anybody have any pointers?
[11:20]  * ogra_ runs another mx5 build
[11:39] <ogra_> and another one
[11:42] <lilstevie> lol
[11:42] <ogra_> oho !
[11:43] <ogra_> that one looks good
[11:46] <ogra_> janimo, i think i have something for you in a minute
[11:46] <ogra_> it created partitions etc, now it is compressing
[11:46] <ogra_> hmm, though it again uses a 1.5G file ... where does that come from
[11:47] <janimo> ogra_, that is the standard new DVD iso size for Ubuntu right?
[11:48] <ogra_> might be
[11:49] <ogra_> hmm, but thats not a debian-cd issue
[11:49] <ogra_> the live builder actually generated an 1.5G ext3
[11:52] <lilstevie> an installer for arm that can be put on an sdcard or usb stick would be awesome
[11:52] <ogra_> lilstevie, thats how all our images work
[11:53] <lilstevie> I could make a blob for the start of the mmc that would solve the need to use nvflash :p
[11:53] <ogra_> what bothers me is that it is still convinced it builds a CD
[11:53] <ogra_> even though it isnt doing that
[11:53] <lilstevie> ah heh
[12:28]  * ogra_ will wait for infinity ... that is all odd
[13:40] <ppisati> NCommander: weren't you preparing a kernel patch for nic/usb?
[14:42] <ogra_> hmm, oss4 has a weird build failure
[14:42] <ogra_> complaining about an unused variable (which triggers Werror) but the variable is actually used
[14:43] <ogra_> hmm
[14:43]  * ogra_ doesnt get it
[14:44] <ogra_> ossmixd.c: In function 'update_values':
[14:44] <ogra_> ossmixd.c:165:7: error: variable 'prev_value' set but not used [-Werror=unused-but-set-variable]
[14:44] <ogra_> cc1: all warnings being treated as errors
[14:44] <ogra_> ...
[14:44] <ogra_> but ...
[14:44] <ogra_>   int value, prev_value;
[14:44] <ogra_> ....
[14:44] <ogra_>      prev_value = mixc_get_value (mixernum, i);
[14:44] <ogra_> ...
[14:45] <ogra_> i dont get why that would spill a warning at all
[14:48] <GrueMaster> ogra_: The netinstall for omap is no longer pulling x-loader.  We will need it as it is still a separate package from u-boot.
[14:49] <ogra_> hmm, i didnt change it
[14:49] <ogra_> i think
[14:49] <ogra_> didnt NCommander upload a d-i change for that recently ?
[14:49]  * ogra_ checks
[14:49] <GrueMaster> Didn't we take it out of the seed?  Or is this a netinstall issue only?
[14:49] <GrueMaster> He updated flash-kernel for omap.
[14:50] <ogra_> i didnt touch any omap code at all
[14:50] <ogra_> only omap4
[14:51] <GrueMaster> Ok, so it is the flash-kernel for d-i that needs fixing?
[14:51] <ogra_> and i have no idea how michael pulls x-loader, that should happen by flash-kernel-installer usually
[14:52] <GrueMaster> I'll pounce on him when he gets up.
[14:52] <GrueMaster> He may have thought that with the x-loader being pulled in for panda that it was that way for all omap.
[14:53] <ogra_> yeah, he was on vac. when it happened
[14:53] <diwic> ogra_, why do you try to compile oss4?
[14:53] <GrueMaster> He just updated it Monday.
[14:53] <ogra_> diwic, i try to make it not ftbfs :)
[14:54] <ogra_> diwic, it looks like it is right that 'prev_value' isnt used further, but it is definitely getting a value assigned once
[14:54] <ogra_> i wonder if i could just drop that var
[14:55] <diwic> ogra_, I guess you could, but is oss4 really relevant for arm? Better just mark it as "don't even try"?
[14:56] <ogra_> diwic, not an option :)
[14:56] <ogra_> (see cjwatsons mail to -devel)
[14:56] <ogra_> what makes me really wonder is why it doesnt ftbfs on all arches with that error
[14:56] <diwic> ogra_, ok will look later (will have to go to meeting now)
[14:57] <ogra_> no hurry
[14:57] <ogra_> (i didnt even mean to summon you :), but if you want to take it ... )
[15:20] <MMlosh> Hi! I am having issues with "vdr"  multimedia server..  it locks up my dvbt tuner on pandaboard.. on x86 it behaves fine (natty)
[15:20] <MMlosh> Any hints what to try?  It locks up some time after I stop recording/streaming
[15:21] <MMlosh> http://fpaste.org/4E4X/ is the dmesg.. I repluggged the tuner ~2 times and restarted vdr during the logged time
[15:31] <ogra_> looks like a driver issue ...
[15:31] <ogra_> file a bug i'd say :)
[15:35] <ogra_> GrueMaster, so looking at NCommander's f-k changes, he doesnt seem to touch x-loader stuff at all
[15:36] <GrueMaster> The x-loader package isn't installed at all.  The f-k part fails when making the system bootable due to missing MLO.
[15:36] <GrueMaster> That is why I thought it might be a seed issue.
[15:37] <ogra_> right, but i see no code changes touchcing anything x-loader related
[15:37] <ogra_> might
[15:37] <ogra_> iirc we seed it in the installer seed
[15:38] <ogra_> ogra@osiris:~/Devel/seeds/platform.oneiric$ grep x-loader *
[15:38] <ogra_> supported-hardware-common: * x-loader-omap3-beagle [armel]                  # omap3 first stage bootloader
[15:38] <ogra_> supported-hardware-common: * x-loader-omap4-panda [armel]                 # omap4 first stage bootloader
[15:38] <ogra_> yup, we do
[15:39] <ogra_> but i think thats only for main, that seed isnt used anywhere else
[15:39] <GrueMaster> Well, not sure what to look for.  The x-loader wasn't installed on this system after running netinstall.  I had to go in and manually add it.
[15:40] <ogra_> right, i'm still digging
[15:40] <ogra_> are you sure it was ever installed in these images ?
[15:41] <GrueMaster> it had to be.  We had working netinstall on Maverick (although unofficially).
[15:41] <ogra_> i'm talking about this cycle :)
[15:42] <ogra_> NCommander completely rewriote what i did in lucid/maverick
[15:42] <GrueMaster> This cycle it hasn't worked for other reasons.
[15:43] <ogra_> right, so we dont know if the new code ever worked
[15:44] <GrueMaster> I'll ping NCommanderwhen he gets up.
[15:45] <ogra_> yeah, to me it looks like that never worked
[15:46] <ogra_> at least there were no recent changes that could break it
[16:02] <utlemming> Is there a kind soul who might be able to help me with the Beagle board under QEMU emulation? I keep getting "qemu: fatal: Trying to execute code outside RAM or ROM at 0x40304350" when attempting to load the Oneiric OMAP4 kernel
[16:03] <MMlosh> ogra_, sry.. I was away..  file bug agains what?  everything is OK when I use mplayer.. everything is OK when using VDR on x86
[16:04] <ogra_> well, thses are definitely kernel messages
[16:04] <ogra_> if a userspace app triggers such things you should file a bug against the kernel
[16:04] <MMlosh> oh..  thinking that way around.. that makes sense.. ok
[16:04] <MMlosh> ogra_, on launchpad I guess?
[16:05] <ogra_> yep
[16:05] <MMlosh> (cause kernel bugzilla is down anyway)
[16:05] <ogra_> or just call ubuntu-bug on the panda
[16:05] <ogra_> it shoudl wlak you through
[16:05] <ogra_> *walk
[16:05] <MMlosh> that will need launchpad account anyway.. right?
[16:05] <ogra_> yes
[16:06] <MMlosh> it would be easier from here..  thanks for help.. I hope it's something easier to fix..
[16:06] <MMlosh> ogra_, do you think booting vanilla kernel 3.0.0. and testing with that would help?
[16:08] <ogra_> MMlosh, where would you get such a kernel ?
[16:08] <ogra_> do you have one for omap4 around ?
[16:09] <MMlosh> ogra_, yes.. I have that ready to go
[16:09] <ogra_> well, try it, then you can tell in the bug that its working in vanilla oamp4
[16:09] <MMlosh> not completely vanilla.. it has some minimal patches according to the wiki..
[16:09] <MMlosh> ah.. crap..  I think it lacks dvb support
[16:09] <ogra_> funny though, i wouldnt think that works without all the TI patches
[16:11] <GrueMaster> utlemming: The omap4 kernel is not the beagleboard kernel.  That is for the pandaboard.  You want an omap kernel.
[16:11] <MMlosh> ogra_, yes.. but I started with the omap4 defconfig from the wiki
[16:11] <MMlosh> GrueMaster, this is on panda
[16:12] <GrueMaster> MMlosh: I was referring to utlemming's post on using the omap4 kernel in quemu emulating a beagleboard (before your post).
[16:12] <ogra_> MMlosh, well, our kernel carries like 1700 patches from TI to make panda work in all aspects
[16:12] <utlemming> GrueMaster: I just double-checked, I'm install linux-image-omap
[16:13] <MMlosh> I used the 3.0.0 image to get the AP support... it worked fine
[16:15] <MMlosh> ogra_, I'll get most up to date kernel then and compile.. I hope I get the config right, so the tuner works.. but first the basic report.. and finding out my launchpad password
[16:15] <ogra_> which kernel are you currently running btw ?
[16:15] <ogra_> we have a 3.0 omap4 kernel in oneirirc
[16:18] <MMlosh> ogra_, the default one in natty
[16:18] <MMlosh> 2.6.38-1208-omap4
[16:19] <MMlosh> hmm.. that's sure worth trying..
[16:19] <utlemming> the Oneiric linux-image-omap is for OMAP3 devices
[16:19] <ogra_> utlemming, yes
[16:19] <utlemming> ogra_: that is the one that I am using that is failing in qemu
[16:20] <ogra_> utlemming, with what bootloader setup do you use it ?
[16:21] <utlemming> u-boot and MLO from the Natty Netbook images
[16:21] <ogra_> and you have a vfat you point qemu to
[16:21] <ogra_> ?
[16:21] <ogra_> carrying all these bits
[16:21] <utlemming> yeah, on a vfat
[16:22] <ogra_> weird, that should work
[16:22] <MMlosh> ogra_, he has a point - can I keep mlo and uboot from natty, or I have to upgrade for that 3.0 kernel?
[16:22] <ogra_> should work
[16:23] <MMlosh> ok
[16:24] <utlemming> Oh...wait a minute...I'm using the OMAP4 MLO and uboot
[16:24] <utlemming> I'll try the OMAP3 ones
[16:29]  * utlemming feels like an idiot for using the wrong MLO and u-boot
[17:31] <MMlosh> oh.. the bluish color of the boot messages is gone.. it's pure gray with 3.0.0..  the dvb tuner works.. let's see if it locks up when I stop using it
[17:35] <MMlosh> and the minor issue with fluxbox is gone (it used to paint default "Workspace 1" instead of my configured name at the beginning)
[17:42] <MMlosh> taking my preference for 3.0 back..  Xv does not work..  maybe I need X11 update
[17:52] <NCommander> ogra_: GrueMaster: I'm alive. I didn't touch the x-loader code in F-K, the onmly thing I did was make sure the proper packages get instlaled in f-k-i on omap3
[17:52] <GrueMaster> Well, missed one.  :P
[17:52] <NCommander> ?
[17:53] <GrueMaster> x-loader is not installed.
[17:53] <ogra_> there is no x-loader on omap
[17:53] <NCommander> great
[17:53] <ogra_> (it only moved into u-boot on panda)
[17:53] <NCommander> am I just installing the wrong package?
[17:53] <NCommander> ogra_: *facepalm*
[17:53] <ogra_> no, we arent ending up with any MLO
[17:54] <ogra_> omap3 still needs the old way
[17:54] <NCommander> lovely
[17:54] <NCommander> I'll smack it with a stick today
[17:55] <ogra_> well, up to now the omap netinst wasnt usable anyway ... and nobody complained
[17:55]  * ogra_ wouldnt cry if it wouldnt get ready to be honest
[17:56] <NCommander> ogra_: english parse fail
[17:57] <ogra_> really ?
[17:57] <NCommander> that sentence didn't make sense to me
[17:57] <ogra_> hmm, my grammar is a bit weird today, agreed
[17:58] <NCommander> ogra_: anyway, I'm going to resolve my nictine fix so I'll bbiab
[17:58] <ogra_> NCommander, we havent had any working netinst omap3 images yet and nobody complained ... so it doesnt seem like anyone misses it ... and i wouldnt miss it too if you wouldnt manage
[17:58] <ogra_> s/too/either/
[17:58]  * ogra_ hopes thats more understandable :)
[18:13] <MMlosh> ogra_, the -omap4 kernel from oneiric works so far... the tuner's "channel lock" LED sometimes gets off for a second, but always comes back on, meaning the tuner is working
[18:14] <MMlosh> too bad DPMS and Xv do not work...  maybe I need to update X11 from oneiric too
[18:17] <MMlosh> Is the issue still worth filling on launchpad?  I guess that noone will bother fixing that for a <30 days until replacement release
[20:13] <kblin> hi folks
[20:14] <kblin> I'm a bit puzzled. I was under the impression that armel was a supported platform for natty. however, it seems there's binary packages that are only available for x86 platforms
[20:14] <utlemming> I'm having a bit of trouble getting text within QEMU....I'm using as my u-boot boot.scr parameters "setenv bootargs vram=1M mem=511M console=ttyS2,115200n8 serialtty=ttyS2 root=LABEL=cloudimg-rootfs fixrtc ro". All I see is "Starting kernel ...". Does anyone have any idea what I'm doing wrong here?
[20:24] <utlemming> MMlosh: increasing it 2M seems to make things a bit happier, but not much
[21:25] <bnofreak> hi  ..  i have some problems installing the prebuilt ubuntu binaries on my Pandaboard (revision A2)  board  .. i believe that i have followed the instructions  in the "Getting Started"  guide , and im trying to install  Natty ..  but i can't boot .. the boot sequence does not get longer than "Uncompressing Linux... done, booting the kernel."  ..
[21:25] <bnofreak>  <bnofreak> After that, the two leds next to the sd slot are flashing for some minutes ..   and then nothing further happens
[21:25] <bnofreak> the image that i've copied to the sd card is  ' ubuntu-11.04-preinstalled-netbook-armel+omap4.img '
[21:26] <bnofreak> :) please help


[05:58] <warsoul> sorry
[05:59] <warsoul> can you guys -q me
[08:01] <el> warsoul: the -q happened automatically after a minute. was there anything else you needed from this channel?
[22:20] <tomreyn> someone in #ubuntu is requesting your attention
[22:21] <tomreyn> rabbitnightmare - but they just left
[22:29] <housecat> DalekSec: you just beat me to it. I note their long history.
[22:30] <housecat> oh gods, they started in -offtopic too
[22:30] <TheMaster> I set it to expire in 3 months if he doesn't end up here first, I don't mind if anyone chats with him and removes it.
[22:30] <housecat> im honestly considering just asking for a namespace ban
[22:31] <TheMaster> ...Feel free to extend if you think 3mo is too short, then.
[22:31] <housecat> what'
[22:32] <housecat> what's the ban id
[22:32] <TheMaster> 79932
[22:32] <housecat> @duration 79932
[22:33] <housecat> @duration 79932 99999d
[22:33] <housecat> that ought to do it
[22:34] <housecat> @comment 79932 repeated problematic behavior in #ubuntu and #ubuntu-offtopic since at least 2014
[22:35] <housecat> phunyguy: fyi, if they start up in -ot just nuke them ^
[22:37]  * housecat ponders flyback and rabbitnightmare in -ot scrollback, concludes we've been a bit lax on !language recently
[22:38] <TheMaster> Urgh, you guys have flyback?  I'm sorry.
[22:38] <housecat> yeah it's great im thrilled
[22:38] <housecat> i saw him in #ubuntu recently, i guess he migrated from there
[22:39] <el> i wish people would stop punting people who violate our minimum behavioural standards to offtopic where their behaviour is unsurprisingly also disallowed
[22:44] <housecat> please feel free to stick "#ubuntu-offtopic is not a dumping ground for people you think are trash" in a certain channel's topic. lord knows i've tried telling them
[22:49] <tomreyn> thanks DalekSec
[22:50] <tomreyn> if you have the time, could you also do the "fix your connection" for ferche23?
[22:50] <tomreyn> or anyone else who's around.
[22:51] <TheMaster> Hi, let me check.
[22:52] <TheMaster> Well let's see if he's still doing it, maybe his znc finally was able to catch up.
[22:56] <TheMaster> tomreyn: Looks to have settled.
[23:02] <tomreyn> looks like i need more patience. thanks, TheMaster
[23:05] <TheMaster> Hah, well I've done the same too.


[16:00] <Ursinha> hello?
[16:00] <arosales> Hello
[16:01] <smb> \o
[16:01] <utlemming> I think this is going to be lightly attended meeting today with everyone at ODS
[16:01] <Ursinha> should we do that anyway?
[16:01] <arosales> yes, lets meet
[16:02] <Ursinha> #startmeeting ubuntu-server-team
[16:02] <meetingology> Meeting started Tue Apr 17 16:02:12 2012 UTC.  The chair is Ursinha. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:02] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:02] <arosales> should be relatively short :-)
[16:02] <Ursinha> #topic Review ACTION points from previous meeting
[16:02] <Ursinha> should I trust the wiki page?
[16:03] <arosales> smoser: did you update after last weeks meeting?
[16:03] <Ursinha> the logs aren't there..
[16:04] <arosales> spamaps isn't here at the moment
[16:04] <arosales> jamespage: did you have a chance to follow up on the FTBFS?
[16:04] <arosales> jamespage: is also at ODS so may not be available.
[16:04] <arosales> Ursinha: lets move onto bugs for now
[16:05] <Ursinha> all right
[16:05] <arosales> http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:05] <Ursinha> #topic Release Bugs - http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:05]  * arosales looking for non openstack bugs
[16:05] <arosales> bug 928990
[16:06] <arosales> utlemming: any update there?
[16:06] <utlemming> arosales: yes, it is going to require substaintial plumbing to get that fixed.
[16:07] <arosales> utlemming:ok,  as we are past final freeze is this something that will need to go into an SRU?
[16:07] <utlemming> Most users should never hit it, so it not as scary as it sounds
[16:07] <utlemming> that particular bug has been changed with a request for a rescue console
[16:07] <arosales> utlemming: ok, thanks.
[16:07] <utlemming> I've done a bit of work on it, but I want to make this a UDS discussion
[16:07] <arosales> utlemming: will you be drafting up a blueprint?
[16:08] <utlemming> Yes, its part of the cloud images roundtable I've proposed
[16:08] <arosales> utlemming: cool, thanks.
[16:09]  * arosales skipping 930916 as SpamapS isn't currently available
[16:09] <arosales> quantum bugs . . .
[16:09] <arosales> bug 979159
[16:10] <arosales> looks like jamespage had confirmed that one
[16:11] <arosales> also looks like jamespage triaged bug 979190
[16:11] <arosales> as well with bug 979163
[16:12] <arosales> skipping bug 880339
[16:12] <arosales> bug 974584
[16:13] <seh> fixed for lxc for precise
[16:13] <seh> staying open to be fixed in initscripts in q+
[16:13] <arosales> seh: thanks for the update.
[16:14] <Ursinha> is the importance High as the other tasks?
[16:14] <seh> I think so
[16:14] <Ursinha> I'll set it, thanks seh
[16:14] <seh> thanks
[16:14] <arosales> Ursinha: thanks
[16:15] <arosales> have one new FTBFS
[16:15] <arosales> bug 935071
[16:15] <arosales> looks like jamespage had also taken a look at that one.
[16:16] <arosales> MIR's are progerssing
[16:16] <Ursinha> arosales, he unassigned himself from that bug
[16:17] <arosales> Ursinha: ah yes, any takers here ?
[16:17] <Ursinha> it seems the package needs to be removed from the archive, if so, there might be a process somewhere indicating how to do so
[16:17] <Ursinha> (subscribing a team to the bug or something like that)
[16:17] <arosales> ya, may need to add an archieve admin
[16:17] <arosales> I'll follow up on it
[16:18] <Ursinha> cool
[16:18] <arosales> thats it for the bugs.
[16:18] <arosales> Just a few blueprints to go over
[16:18]  * arosales looking at
[16:18] <arosales> http://status.ubuntu.com/ubuntu-precise/ubuntu-server.html
[16:18] <Ursinha> [ACTION] arosales to follow up on bug 935071
[16:18] <meetingology> ACTION: arosales to follow up on bug 935071
[16:18] <arosales> sorting by priority and completion
[16:18] <Ursinha> #topic Blueprints - http://status.ubuntu.com/ubuntu-precise/ubuntu-server.html
[16:18]  * arosales also looking at non-openstack bugs
[16:19] <arosales> skipping https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-openstack-charms
[16:19] <arosales> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-kvm-document-suggested-changes
[16:19] <arosales> I don't think hallyn is here
[16:19] <seh> I was going to start the perf runs today, but that laptop is now doing qa tests
[16:19] <seh> i blame arosales  :)
[16:19] <Ursinha> arosales, one of the ACTION items from last meeting was: SpamapS to postpone servercloud-p-cloud-power-management to Q
[16:20] <arosales> seh: for sure, I'll take that blame :-)
[16:20] <arosales> I'll follow up with hallyn
[16:20] <arosales> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-pushing-cloud
[16:20] <arosales> utlemming: are these TODOs going to make 12.04?
[16:21] <utlemming> No, I've marked the blueprint deferred already. I'll also update the todo's
[16:21] <arosales> utlemming: ok, thanks
[16:21] <arosales> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloudutils
[16:22] <arosales> also may need to look at this one I think the thought on that one was to get clou-images-sync done
[16:22] <arosales> utlemming: is that still viable for 12.04?
[16:22] <utlemming> arosales: yes, the cloud-image sync script is done
[16:23] <arosales> utlemming: cool, should "[utlemming] implement cloud-images-sync: TODO" move to done?
[16:23] <utlemming> refresh. I just updated that
[16:23] <arosales> utlemming: ah thanks :-)
[16:24] <arosales> Ursinha: thats covers the blueprints I had in mind to discuss
[16:24] <Ursinha> arosales, right
[16:24] <Ursinha> moving on then
[16:24] <Ursinha> #topic Ubuntu Server Team Events
[16:24] <Ursinha> anything to note?
[16:24] <arosales> So a lot of folks at ODS
[16:24] <seh> [1;5AI expect I'll be heading to linuxcon in august
[16:24] <Ursinha> besides ODS happening right now
[16:25] <arosales> m_3 will be attending railsconf April 23-25
[16:25] <seh> (for security summit, maybe kvm one)
[16:25] <Ursinha> cool :)
[16:25] <Ursinha> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:26]  * Ursinha looks around for hggdh
[16:26] <hggdh> I am here, just had a bit of an issue with weechat
[16:27] <Ursinha> oh
[16:27] <hggdh> Ursinha: nothing new, except please help test :-)
[16:27] <hggdh> ..
[16:27] <Ursinha> :)
[16:27] <Ursinha> great
[16:27] <Ursinha> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:27]  * smb only has to say that he has nothing to say...
[16:27] <smb> ..
[16:27] <Ursinha> hehe
[16:27] <Ursinha> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:27] <rbasak> ARM server netinstalls are currently broken due to bug 984007. This is a critical issue and should be fixed soon.
[16:27] <rbasak> Nothing else to report. Any questions for me?
[16:28] <arosales> rbasak: can that be an SRU or do we need to talk with the release team about getting this in before 12.04 release?
[16:28] <rbasak> arosales: the foundations team are looking after this - infinity in particular.
[16:29] <arosales> rbasak: ok, I'll also follow up with the release team on Friday during their meeting
[16:29] <rbasak> I presume he'll a fix in before release.
[16:29] <rbasak> he'll get a fix in
[16:29] <arosales> rbasak: thanks for the info
[16:29] <arosales> ..
[16:29] <Ursinha> it was just set to In Progress, yay
[16:29] <Ursinha> thanks rbasak
[16:30] <rbasak> np
[16:30] <Ursinha> #topic Open Discussion
[16:30] <rbasak> Our planned reference install will be a netinstall on armadaxp, so this is critical for us :)
[16:30] <arosales> rbasak: for sure
[16:30] <arosales> Ursinha: one topic
[16:30] <arosales> Call for testing on bare metal installs
[16:31] <arosales> We need help doing some installs to check off the tests at http://iso.qa.ubuntu.com/qatracker/milestones/204/builds/15473/testcases
[16:31] <arosales> so if anyone has any spare cycles please see if you check if any of the tests pass
[16:31] <arosales> ..
[16:31]  * Ursinha looks
[16:31] <seh> j'accuse
[16:32] <Ursinha> cool
[16:32] <Ursinha> please, help test!
[16:32] <Ursinha> #topicAnnounce next meeting date and time
[16:32] <Ursinha> #topic Announce next meeting date and time
[16:32] <Ursinha> according to the queue, that should be utlemming
[16:32] <Ursinha> is that correct?
[16:33] <utlemming> yup, that's my understanding
[16:33] <Ursinha> all right, I'll update the wiki page
[16:33] <arosales> Thanks for charing this meeting Ursinha :-)
[16:33] <Ursinha> #endmeeting
[16:33] <meetingology> Meeting ended Tue Apr 17 16:33:29 2012 UTC.
[16:33] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-17-16.02.moin.txt
[16:33] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-17-16.02.html
[16:33] <Ursinha> thanks arosales for leading it :)
[16:33] <Ursinha> thanks guys
[16:59] <jsalisbury> #startmeeting
[16:59] <jsalisbury> ##
[16:59] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[16:59] <jsalisbury> ##
[16:59] <meetingology> Meeting started Tue Apr 17 16:59:57 2012 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:59] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:59] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[16:59] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Precise
[17:00] <ppisati> o/
[17:00] <henrix> o/
[17:00] <herton> o/
[17:00] <kamalmostafa> \o
[17:00] <cking> o/
[17:00] <sforshee> o/
[17:00] <bjf> \o/
[17:00] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:00] <ppisati> P/omap4: the video issue was resolved (lp963512), kernel was rebased on master (3.2.0-23.36) and Ubuntu-3.2.0-1412.15 will be Precise's omap4 kernel
[17:00] <ppisati> ..
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:01] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-precise/canonical-kernel-distro-team-ubuntu-12.04.html
[17:01] <ogasawara> All work items have now been closed \o/
[17:01] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: Precise Development Kernel (ogasawara)
[17:02] <ogasawara> The Precise kernel is currently frozen and release candidate images are
[17:02] <ogasawara> set to be spun this Thurs Apr 19.  Final release is almost 1 week away
[17:02] <ogasawara> on Thurs Apr 26.  We have started queuing patches for the first kernel
[17:02] <ogasawara> SRU.  This includes patches from the most recent v3.2.15 upstream stable
[17:02] <ogasawara> release.  Should an additional upload be required before final release,
[17:02] <ogasawara> we will try to include a few bug fixes which have been queued.  Please
[17:02] <ogasawara> note that at this point in time, all patches are subject to our SRU
[17:02] <ogasawara> policy and uploads will only be granted at the discretion of the release
[17:02] <ogasawara> team.
[17:02] <ogasawara> https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat
[17:02] <ogasawara> Important upcoming dates:
[17:02] <ogasawara>  * Thurs Apr 19 - Release Candidate (~1 day)
[17:02] <ogasawara>  * Thurs Apr 26 - Final Release (~1 week)
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: CVE's (apw)
[17:03] <apw> nothing to report, backlog unchanged
[17:03] <apw> ..
[17:03] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Oneiric/Natty/Maverick/Lucid/Hardy (bjf/herton)
[17:03] <bjf>
[17:03] <bjf> Here is the status for the main kernels, until today (Apr. 17):
[17:03] <bjf>
[17:03] <bjf>  * Hardy    - 2.6.24-31.101 - Nothing this cycle
[17:03] <bjf>  * Lucid    - 2.6.32-41.88  - Regression testing
[17:03] <bjf>  * Natty    - 2.6.38-14.58  - Completed
[17:03] <bjf>  * Oneiric  - 3.0.0-19.32   - Regression testing
[17:03] <bjf>
[17:03] <bjf> Current opened tracking bugs details:
[17:03] <bjf>  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:03] <bjf>
[17:03] <bjf> For SRUs, SRU report is a good source of information:
[17:03] <bjf>  * http://people.canonical.com/~kernel/reports/sru-report.html
[17:03] <bjf>
[17:03] <bjf> Future stable cadence cycles:
[17:03] <bjf>  * https://wiki.ubuntu.com/PrecisePangolin/ReleaseInterlock
[17:03] <bjf>
[17:03] <bjf> ..
[17:03] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:04] <bjf> Quixotic Quetzacoatl
[17:04] <cking> bjf just could not resist that
[17:04] <kamalmostafa> how would I ever learn to spell that?
[17:05] <jsalisbury> Thanks everyone
[17:05] <jsalisbury> #endmeeting
[17:05] <meetingology> Meeting ended Tue Apr 17 17:05:19 2012 UTC.
[17:05] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-17-16.59.moin.txt
[17:05] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-17-16.59.html
[17:05] <kamalmostafa> thanks jsalisbury


[01:53] <EldonMcGuinness> I am so glad that KDE handles Bluetooth headphones, Gnome would crap itself all the time
[01:57] <valorie> glad to hear that it's working for ya, EldonMcGuinness
[01:57] <valorie> some people complain about it, so it is not perfect
[01:57] <valorie> yet
[01:57] <EldonMcGuinness> I used to have to login/logout/reboot and then pray for it to work with Gnome
[01:58] <EldonMcGuinness> I had to do a little playing to get it to work in KDE but it just works now when I power them on
[02:04] <valorie> excellent
[02:07] <EldonMcGuinness> I have to say I am loving KDE, had not tried it in over a decade. Needless to say it has come a longway.
[02:07] <valorie> Plasma is awesome
[02:07] <EldonMcGuinness> Been a Gnome person since WAY back
[02:07] <valorie> and I love the applications
[02:08] <valorie> the KDE community is completely awesome
[07:20] <JeroenDeDauw> Baaah. The Kubuntu installer still only has an encrypted LVM option for the entire disk. It'd be so cool if it had an option to set up an encrypted LVM for just one partition
[07:20] <JeroenDeDauw> I'm just going to buy me another disk again and use the guided option for the entire disk rather than messing around on the CLI for hours :(
[07:20] <JeroenDeDauw> Where would I post such a feature request anyway?
[07:25] <hateball> JeroenDeDauw: On Launchpad I guess
[07:26] <hateball> JeroenDeDauw: You should be able to set it up manually using partitionmanager I think, before you go to the install
[07:32] <JeroenDeDauw> hateball: oo did not know this application
[07:33] <JeroenDeDauw> hateball: so... if I install the thing on the entire disk now I will be able to make it smaller from this app later and install Faildows on another partition?
[07:42] <lordievader[m]> Good morning
[07:52] <hateball> JeroenDeDauw: sure, you can resize as you see fit
[07:53] <JeroenDeDauw> hateball: \o/
[07:53] <JeroenDeDauw> hateball: thanks for helping
[07:53] <hateball> JeroenDeDauw: installing windows after will overwrite grub tho, so if you must have that mess installed I'd do that first
[07:53] <hateball> saves you the trouble of having to !fixgrub
[07:54] <JeroenDeDauw> ugh right
[09:57] <BluesKaj> 'Morning folks
[10:02] <jubo2> G'morning BluesKaj
[10:04] <BluesKaj> hi jubo2
[11:29] <viewer|488> Hi. I have just done a clean install of kubuntu 17.04, but i have a problem with cpu usage. Anyone else experiencing this?
[11:40] <hateball> viewer|488: What's the problem?
[11:40] <hateball> viewer|488: Just press ctrl+esc to bring up the system monitor and identify what is using your resources
[11:47] <viewer|488> It's Krunner, using around 85-99% of cpu on avarage
[11:50] <viewer|488> And since I'm using a laptop, this over working cpu makes for a lot of heat. So after a few minutes running it freezes to prevend hardware damage.
[11:50] <viewer|488> prevent*
[11:51] <BluesKaj> viewer|488, do you mean krunner the "run command" ?
[11:53] <viewer|488> BluesKaj: I mean the prosses yes. When I monitor the systems cpu usage, it just says krunner      99%
[11:54] <BluesKaj> viewer|488, did you start some process/app in the run command/krunner?
[11:55] <BluesKaj> alt+F2 ?
[11:55] <viewer|488> BluesKaj: After a restart I only started system monitor from run command(alt+F2)
[11:58] <BluesKaj> to start system monitor you can use alt+esc or find it in the kmenu/system, but it shouldn't be using 099%, of the cpu. Scroll doen in the process tab  and look for a process using over 50%
[11:59] <viewer|488> Nothing else is running nealy as high, baloo_file_extractor is using constant 25%, and the rest like 1 or 2%
[12:00] <viewer|488> But i still think that 25-30% cpu usage with no presure on the system is too high
[12:00] <BluesKaj> you can turn off baloo in system settings>search if youdon't need it
[12:01] <krlov> Do you guys all removed zeitgeist, geoclue and whoopsie as well?
[12:02] <BluesKaj> it normally indexse files for a few mins after bootup, unless this is a brand new instakll then ballo will take a while to finish indexing all the serchable files
[12:02] <BluesKaj> scuse the poor spelling
[12:03] <viewer|488> Nice, after baloo is switched off, the system cpu usage is back to normal!
[12:03] <viewer|488> Is there a way to disable run command?
[12:05] <BluesKaj> run command should only run when chosen in the context menu by right clicking on the desktop or alt+F12 , otherwise it should be off
[12:06] <viewer|488> Yep, just have to remember not too use it anymore! I could just disable the shortcut though
[12:07] <viewer|488> BluesKaj: Thank you so much for your help! I was afraid I had to go back to Ubuntu again with unity.. Or add plasma to it again
[12:08] <BluesKaj> viewer|488, if you wany quick access to some fav apps use quicklai=unch widget or add them to favourites from the kmenu
[12:08] <BluesKaj> oops quicklaunch
[12:09] <viewer|488> That could work
[12:12] <BluesKaj> viewer|488, also update and upgrade your paqckages with apt or the package manager at least every few days to keep your system up to date
[12:14] <viewer|488> BluesKaj: I'm an update "anal" so, usually that's not a problem. Often I'm ending up with beta software because of it.
[12:15] <BluesKaj> only if you use ppas
[12:15] <BluesKaj> then be careful to delete the ppas once you upgrade with them
[12:17] <viewer|488> That's a good advice!
[12:20] <BluesKaj> the backports are usually quite safe because the software there is tested and more mature than alpha or beta versions
[12:21] <BluesKaj> the key word here is "usually" ...not always :-)
[12:21] <viewer|488> Hehe, yep!
[12:29] <viewer|488> BluesKaj: Well, thanks again! I have to go now. Have a good day!
[13:44] <trevize> hello I have a problem with my laptop battery, it shows: no battery available. could anyone guide me how  to troubleshoot this?
[13:45] <trevize> (Yes I am sure I have a battery and it works ;) )
[13:47] <BluesKaj> trevize, have you tried shutting down, removing the battery for 5mins or so, then reinserting it and booting up again.
[13:47] <trevize> I have not tried removing it
[13:47] <trevize> sure it works?
[13:48] <BluesKaj> it used to. haven't had that problem in a long time
[13:50] <trevize> ok I ll try and report back
[13:50] <trevize> thanks dude
[14:10] <trevize> hello its me again, I shut down the computer, I unplugged the battery,waited 5 mins and plugged it back again. kde still shows no battery
[14:10] <trevize> could anyone help?
[14:21] <lordievader[m]> What kernel parameters do you have set?
[14:21] <lordievader[m]> trevize: ^
[14:35] <trevize> I did not set any parameters
[14:36] <trevize> should be set to default parameters
[14:36] <lordievader[m]> Okay, what is the output of 'acpi -b'?
[15:39] <trevize> @lordievader: acpi shows: Battery 0: Full, 100%
[19:22] <viewer|98476> Plasma cant start due to some shit OpenGL2
[19:22] <viewer|98476> i think it has something to do with the nvidia driver update and latest kernel
[19:22] <viewer|98476> everything works when i revert to xOrg
[19:22] <viewer|98476> but how can i make it work with the nvidia again?
[19:23] <viewer|98476> "Plasma Failed To Start
[19:23] <viewer|98476> Plasma is unable to start as it could not correctly to se OpenGL2
[19:23] <viewer|98476> Please check that your graphic drivers are set up correctly
[19:23] <viewer|98476> "Plasma Failed To Start Plasma is unable to start as it could not correctly to se OpenGL2 Please check that your graphic drivers are set up correctly"
[19:23] <viewer|98476> sorry for the spam.
[19:28] <viewer|98476> ?
[19:52] <uuuuuuuuuuuu> i need help