[12:47] <GridCube> so in theory this saturday its release date correct?
[12:48] <GridCube> its there any schedule for us to follow, and by us i mean xubuntu, so i might bother some people to do iso testings etc
[13:44] <maddernick> GridCube: thursday, no?
[13:47] <GridCube> april 25th, its thursday correct, i read 27 and got confused, https://wiki.ubuntu.com/RaringRingtail/ReleaseSchedule
[14:39] <luke_> hello everyone
[14:40] <GridCube> :) hi luke_
[14:41] <GridCube> as i said you earlier, if you want to help, at this moment what we need the most its iso testings http://xubuntu.org/news/want-to-help-out-xubuntu-test-raring/
[14:42] <luke_> alright thanks GridCude!
[14:42] <luke_> appreciate your help
[14:43] <GridCube> :)
[14:44] <GridCube> after this week everyone will have lots of free time and there will be more time for helping newcommers :)
[14:44] <luke_> ok great
[14:44] <luke_> what team are you from?
[14:44] <GridCube> luckly we got some people interested in the last few weeks, we hope they stick around
[14:45] <GridCube> im xubuntu, user support mostly, and some testings, but not lately :( sadly
[14:45] <luke_> how come?
[14:46] <GridCube> my internets are not very helpful, very low rates adn my work its worse, so i cant get the isos
[14:46] <GridCube> luke_, :) https://launchpad.net/~gridcube you can see my badges here
[14:47] <luke_> awesome
[19:56] <micom> do you think that c++ programmer with a little experience can be helpful in the xubuntu?
[19:56] <knome> welcome here as well :)
[19:57] <elfy> all channels lead to the same place :p
[19:57] <Noskcaj> anyone willing to hel pis helpful
[19:57] <knome> they do, they do
[19:57] <Noskcaj> *help is
[19:59] <knome> micom, definitely! and there are other contributors here as well :)
[20:00] <micom> ok lets say that i have a IDE, g++ and etc, what's in your opinion best way to get into xubuntu's development?
[20:01] <ochosi> usually the best way is to start with a bug
[20:01] <knome> micom, fixing bugs that scratch your own itch is a very good way to start
[20:09] <Noskcaj> micom, get a basic knowledge of python first. i did it in about a day, and learn as you go
[20:10] <knome> micom, xfce is written in C... :)
[20:11] <micom> :(
[20:12] <Noskcaj> knome, one other thing to add to our list for next cycle: make the release notes link point to xubuntu.org rather than ubuntu.com
[20:13] <Noskcaj> micom, have a look on bugs.launchpad.net, see what you can fix. C and python are the main languages. also, testing or translations could be a way to help
[20:14] <knome> Noskcaj, does other flavors do that either? we still share most of the release notes with ubuntu, so i'm not even sure if that's ideal
[20:14] <Noskcaj> knome, have a look at bug 1065789, it happened for all of this cycle and most of q cycle
[20:15] <Noskcaj> kubuntu goes to kubuntu.org/news, xubuntu an ubuntu go ubuntu.com, i forget what lubuntu does
[20:15] <knome> Noskcaj, as long as they point to the general release notes, i don't consider that a huge bug
[20:16] <Noskcaj> understandable
[20:17] <knome> if we wanted it to point to xubuntu.org, we'd have to create our own release notes page
[20:17] <knome> from that, we probably want to link to the main ubuntu notes as well, so i don't know if that's a shortcut or a detour (xubuntu-specific notes *are
[20:17] <knome> * in the general page as well)
[20:17] <knome> brb
[20:43] <Unit193> Not that it matters much, but as it stands now (or maybe a couple days ago?) http://unit193.ninth.su/xubuntu/quantal-to-raring.txt  this is from unbooted live CDs.
[21:32] <Noskcaj> is everyone running iso tests? if not, please start.
[21:32] <Noskcaj> or fixing bugs, that works too
[21:33] <knome> Unit193, umph. we'll need to fix that for S
[21:33] <Unit193> Well hey, may actually be more useful than I thought.
[21:33] <knome> the 3.8.0 series kernels do not like my desktop :/
[21:34] <knome> whenever they upload a new one, my system refuses to boot the first time, then proceeds without problems on the second time
[21:34] <Unit193> .2 was very good, later hasn't worked yet.
[21:34] <knome> (after a hard boot, that is)
[21:35] <knome> staying with 12.10 on the laptop for some more
[21:37] <Unit193> I may only be able to upgrade one or two.
[21:38] <knome> i was about to upgrade my wife's
[21:38] <knome> then i realized it's a precise system
[21:39] <knome> so going to do the wacko LTS jump
[21:41] <knome> need to upgrade mum's when we get there the next time
[21:41] <knome> i'm pretty sure she's running Q
[21:42] <ochosi> live on the edge and upgrade her remotely ;)
[21:42] <knome> hmm...
[21:42] <knome> ;)
[21:42] <knome> that's not completely out of question
[21:43] <Unit193> I've done several over SSH, worked pretty well.
[21:43] <knome> i've done some less wanted commands over SSH too :)
[21:44] <knome> resulting in questions like "where IS that server even (physically)?"
[21:44] <ochosi> as long as it comes back on after reboot, it's probably fine/fixable :)
[21:44] <knome> hehe
[21:44] <Unit193> Or sometimes you have to wait half a week or longer to fix your goof... Been there.
[21:45] <knome> yeah. probably better do the upgrade when i'm around and also AFTER RELEASE ;)
[21:45] <knome> (moral right to point fingers at others!)
[21:45] <mac_> cant wait for 13.04 stable
[21:46] <knome> only a few days
[21:46] <Unit193> He said stable, not relese.
[21:46] <knome> lol
[21:46] <knome> yeah.
[21:46] <knome> only a few months
[21:47] <mac_> knome are you a team leader?
[21:47] <knome> mac_, yeah, the xubuntu team/project leader
[21:48] <mac_> how would i get involved with QA?
[21:48] <knome> mac_, the best way to get started is doing the ISO tests
[21:49] <knome> mac_, this article: http://xubuntu.org/news/want-to-help-out-xubuntu-test-raring/ describes testing pretty well generally
[21:49] <mac_> what about code testing like writing units test etc. ?
[21:49] <Noskcaj> mac_, you want to get involved in QA?
[21:50] <knome> mac_, the first thing with that would be to do some planning/investigating work where xubuntu can benefit from it
[21:50] <mac_> ok fair enough
[21:50] <knome> mac_, some of that is probably best cooperated with the xfce team, but some of it is naturally xubuntu-specific too (and it doesn't hurt to run more tests in xubuntu as well, naturally)
[21:51] <knome> mac_, you might want to talk to our developers (micahg, mr_pouit, bluesabre) who could possibly point you to specific things on unit testing
[21:51] <Noskcaj> mac_, Main things for QA team: ISO tests (easy), Autopilot (nothing fox xubuntu, but a version for post-install would be good) and just running a devel version of something and looking for bugs
[21:52] <mac_> who is incharge of the QA team?
[21:53] <knome> Noskcaj is running the calling errands at the moment
[21:53] <Noskcaj> mac_, for Xubuntu, i'm trialling
[21:53] <Noskcaj> mac_, come onto #ubuntu-quality. that's were the team is
[21:54] <knome> well, both here and there; #ubuntu-quality is for the ubuntu wide QA cooperation
[21:54] <knome> xubuntu-specific issues are best discussed here where the xubuntu people hang out
[21:54] <knome> i'd imagine -quality have more pointers on automated testing
[22:19] <ochosi> pleia2: have fun!
[22:19] <pleia2> :)
[22:19] <Noskcaj> pleia2, enjoy.
[22:19] <pleia2> thanks everyone
[22:49] <knome> micahg, can you look at http://unit193.ninth.su/xubuntu/quantal-to-raring.txt someday before release if possible and see if there's some obviously unwanted packages, and get rid of them in our seed? :)
[22:52] <Unit193> (Added a couple more comments, some of those are clearly needed changes.)
[22:53] <knome> what's the story of zeitgeist?
[22:53] <knome> is xubuntu really benefitting from it?
[22:56] <mac_> looks like spyware to me
[22:56] <Unit193> I don't know the database well, but what's in mine was from UbuntuOne before I purged it.
[22:57] <knome> i'll add investigating that to the todo-list for S
[22:57] <Unit193> Since we don't ship U1, I don't *personally* see anything using it, but I don't have all the shipped applications any more.
[22:58] <knome> (unless micahg deems it unnecessary before R release and drops it)
[22:58] <knome> is it not taking any resources then?
[22:58] <knome> i doubt that
[22:58] <knome> we should look in our seed anyway, not because of space or resources, just not to ship something utterly useless :)
[22:59] <knome> (but for space and resources too)
[23:01] <Unit193> I don't have it running it would appear, and now I've purged the last of it.
[23:01] <knome> i seem to have it running
[23:05] <knome> bluesabre, how badly catfish needs zeitgeist? what's their connection?
[23:39] <skellat> I had almost forgotten this merge request: https://code.launchpad.net/~skellat/ubuntu-seeds/xubuntu.raring/+merge/155753
[23:40] <knome> uuugh.
[23:40] <knome> me too.
[23:40] <skellat> Probably needs killing this late in the game
[23:40] <knome> tbe, i had forgotten
[23:41] <knome> i'd say let's do that and other small things in S
[23:41] <knome> though meh, we changed the docs
[23:41] <knome> micahg, when you look at Unit193's link, see the merge request 155753 too
[23:42] <knome> i'd consider that low-mediumish
[23:42] <knome> even more so because R only has 9 months of support, and we're more rolling now
[23:43] <knome> we can probably let ourselves a bit easier with things like this on the interim releases in the future
[23:43] <skellat> How about disapprove it now and we'll consider it in the S cycle then?
[23:43] <knome> if we can get it in, it's fine
[23:43] <skellat> Okay
[23:43] <knome> if not, then it'll automatically be postponed
[23:44] <skellat> There were supposed to be re-spins tonight.  I don't know if the crew in -release started yet, though.
[23:44] <knome> this doesn't affect any image really
[23:44] <knome> it's just a matter if micahg has time before the release and if it's considered something that can pass through
[23:46] <knome> if not.. then let it be
[23:46] <skellat> Alrighty
[23:46] <knome> a bit different from "oops, we forgot to upload the new wallpaper" :P
[23:47] <skellat> :-)  Been there, done that, got the IRC logs for it
[23:48] <knome> that still wasn't as crazy as the "we know it's after UIF... but can we change our logo?" in 12.04 :D
[23:55] <Unit193> knome: /eval.txt too now.


[02:31] <slangasek> infinity: ah, is that why c-m screamed at me? :)
[05:29] <krytarik> infinity: Hi. Could you please accompany  http://bazaar.launchpad.net/~ubuntustudio-dev/ubuntu-seeds/ubuntustudio.artful/revision/1508  by adding the "ship-live" seed to Studio here similar to the Edubuntu one?: http://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/view/head:/lib/cdimage/germinate.py#L371  Thanks!
[05:57] <estan> i know it's a desktop package, so probably takes some extra checking, but qtbase-opensource-src 5.5.1+dfsg-16ubuntu7.4 has been in the upload queue for almost a month now, does it usually take this long for someone to have a look at it?
[05:58] <estan> (it fixes this bug i reported: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173 )
[05:59] <estan> (note that there's already a 5.5.1+dfsg-16ubuntu7.3 upload there as well, but 5.5.1+dfsg-16ubuntu7.4 includes both those fixes, see dmitri's comment on the bug)
[06:02] <apw> estan, in large part it is because it is a sync and syncs are a pig to review
[06:03] -queuebot:#ubuntu-release- Unapproved: rejected qtbase-opensource-src [sync] (xenial-proposed) [5.5.1+dfsg-16ubuntu7.3]
[06:15] -queuebot:#ubuntu-release- Unapproved: qtbase-opensource-src (xenial-proposed/main) [5.5.1+dfsg-16ubuntu7.2 => 5.5.1+dfsg-16ubuntu7.4] (kubuntu, qt5, ubuntu-desktop)
[06:17] -queuebot:#ubuntu-release- Unapproved: rejected qtbase-opensource-src [sync] (xenial-proposed) [5.5.1+dfsg-16ubuntu7.4]
[06:24] -queuebot:#ubuntu-release- Unapproved: accepted qtbase-opensource-src [source] (xenial-proposed) [5.5.1+dfsg-16ubuntu7.4]
[06:58] <estan> apw: aha, i see. thanks a lot for taking care of it!
[07:20] <LocutusOfBorg> hello, any AA around for a question=
[07:21] <flocculant> that's going to be fun for 6 months ... any AA around to talk about AA :p
[07:21] <LocutusOfBorg> I restricted the architectures where llvm 3.7 is built (because just needed for ghc on arm*, so not really needed to build on other architectures)
[07:22] <LocutusOfBorg> unfortunately I'm not sure I gave the commands correctly, it seems "decruftable" but I need double checking before asking or filing a removal bug
[07:25] <infinity> Looks removable to me.
[07:26] <LocutusOfBorg> thanks!
[07:27] <infinity> LocutusOfBorg: And removed.
[07:27] <LocutusOfBorg> my biggest concern was on the -all packages, because debian has them built, while ubuntu has not
[07:28] <LocutusOfBorg> oh... thanks <3 I was filing a bug lol :)
[07:28] <LocutusOfBorg> now, I have to understand why llvm 4.0 is not migrating
[07:28] <LocutusOfBorg> and fix a build failure on 3.8 :)
[07:29] <infinity> * amd64: libllvm-ocaml-dev
[07:29] <LocutusOfBorg> yep I saw that
[07:29] <LocutusOfBorg> but I have to rmadison a little bit
[07:30] <LocutusOfBorg> indeed
[07:30] <LocutusOfBorg> so the decruft happening in Debian has to happen here too, let me see
[07:31] <infinity> LocutusOfBorg: Looks like llvm-4.0 stopped producing libllvm-4.0-ocaml-dev
[07:31] <LocutusOfBorg> libllvm-4.0-ocaml-dev it probably needs to be removed too?
[07:31] <LocutusOfBorg> exactly
[07:31] <infinity> LocutusOfBorg: Which libllvm-ocaml-dev depends on.
[07:31] <infinity> LocutusOfBorg: Nothing about things needing to be removed.
[07:31] <infinity> LocutusOfBorg: But rather llvm-defaults needing fixing.
[07:32] <LocutusOfBorg> interesting, I got the same conclusion, but meh, not sure why this is happening :)
[07:32] <LocutusOfBorg> let me double check
[07:34] <infinity> LocutusOfBorg: Not sure why it's happening?  libllvm-ocaml-dev depends on libllvm-4.0-ocaml-dev, and llvm-toolchain-4.0 doesn't produce libllvm-4.0-ocaml-dev anymore, thus libllvm-ocaml-dev is broken. :P
[07:34] <LocutusOfBorg> the question is "why is not happening in Debian" :)
[07:34] <infinity> LocutusOfBorg: Either llvm-toolchain-4.0 needs to start producing that binary again, or llvm-defaults need to stop producing the unversioned one.
[07:34] <LocutusOfBorg> https://packages.debian.org/unstable/libllvm-ocaml-dev
[07:34] <infinity> LocutusOfBorg: It's not happening in Debian because their llvm-defaults isn't 4.0?
[07:35] <LocutusOfBorg> 3.8 satisfies it
[07:35] <infinity> ...
[07:35] <infinity> Our llvm-defaults points to 4.0.
[07:35] <LocutusOfBorg> indeed, on that page there was a "not alpha, hurd-*" I missed the "not"
[07:35] <infinity> Debian's does not.
[07:36] <LocutusOfBorg> yep, but I didn't parse correctly that page lol
[07:36] <LocutusOfBorg> ENOCOFFEE
[07:36] <LocutusOfBorg> thanks!
[07:47] <infinity> LocutusOfBorg: As for the 3.8/arm64 thing, I have a hunch that related to a gcc regression.  At least, it's moderately suspicious that the current gcc's testsuite has a ton of timeouts in asan tests, and llvm-3.8 also times out in sanitizer tests.
[07:48] <infinity> Oh, but that built before gcc-6 did.
[07:48] <infinity> So, weird coincidence, but perhaps unrelated.
[07:49] <infinity> Or the same patches landed in both toolchains. :P
[07:49] <LocutusOfBorg> well, it fails on Debian experimental but not Debian unstable
[07:49] <LocutusOfBorg> so, somewhere we picked up that stuff from experimental I wild guess
[07:51] <infinity> That's not really how I read the Debian build history.
[07:51] <infinity> I read it as "this timeout is just borderline, and sometimes it succeeds, and sometimes it doesn't".
[07:51] <infinity> It's just sbuild killing it for N minutes without stdout, afterall, it's not the package itself throwing a failure.
[07:51] <LocutusOfBorg> well, it failed 3/4 experimental builds, and 0/2 unstable builds
[07:52] <LocutusOfBorg> (there are three kinds of lies, lies, damn lies, and statistics)
[07:52] <infinity> Right, 3/4.  Not 4/4.  Hence your assertion that "experimental breaks it" is clearly false.
[07:52] <infinity> And 2/2 is hardly a large enough sample size to assert that "unstable fixes" it.
[07:53] <infinity> So I suspect it's just right on the edge of the timeout window.  Sometimes a few minutes over, sometimes a few minutes under.
[07:53] <LocutusOfBorg> yep, I fully agree, I was just trying to see if something in the toolchain was different
[07:53] <LocutusOfBorg> and 3/4, VS 0/2 at least is worth a look :)
[07:54] <LocutusOfBorg> anyway, lets see if now it builds
[08:01] -queuebot:#ubuntu-release- Unapproved: accepted walinuxagent [source] (zesty-proposed) [2.2.9-0ubuntu1]
[08:03] -queuebot:#ubuntu-release- Unapproved: accepted walinuxagent [source] (xenial-proposed) [2.2.9-0ubuntu1~16.04.1]
[08:03] -queuebot:#ubuntu-release- Unapproved: accepted walinuxagent [source] (yakkety-proposed) [2.2.9-0ubuntu1~16.10.1]
[08:04] -queuebot:#ubuntu-release- Unapproved: accepted walinuxagent [source] (trusty-proposed) [2.2.9-0ubuntu1~14.04.1]
[08:25] -queuebot:#ubuntu-release- New sync: vine (artful-proposed/primary) [1.1.3+dfsg-2]
[08:27] -queuebot:#ubuntu-release- New binary: healpix-cxx [s390x] (artful-proposed/universe) [3.30.0-6ubuntu1] (no packageset)
[08:28] -queuebot:#ubuntu-release- New binary: healpix-cxx [amd64] (artful-proposed/universe) [3.30.0-6ubuntu1] (no packageset)
[08:28] -queuebot:#ubuntu-release- New binary: case [amd64] (artful-proposed/universe) [1.5.3+dfsg-1] (no packageset)
[08:29] -queuebot:#ubuntu-release- New binary: healpix-cxx [ppc64el] (artful-proposed/universe) [3.30.0-6ubuntu1] (no packageset)
[08:33] -queuebot:#ubuntu-release- New binary: healpix-cxx [i386] (artful-proposed/universe) [3.30.0-6ubuntu1] (no packageset)
[08:41] -queuebot:#ubuntu-release- New binary: healpix-cxx [arm64] (artful-proposed/universe) [3.30.0-6ubuntu1] (no packageset)
[08:50] <xnox> Laney, infinity - have archive reports been adjusted for artful? because i get emails from pitti, that are not visible in http://people.canonical.com/~ubuntu-archive/component-mismatches.txt unless something has moved as well now.
[08:53] <Laney> They should have been
[08:53] <xnox> Laney, ok, in that case i'm emiling ubuntu-release with a question =)
[08:54] <Laney> Someone demoted the unity8 stuff?
[08:54] <Laney> Is that what you're asking about?
[08:54] -queuebot:#ubuntu-release- New binary: healpix-cxx [armhf] (artful-proposed/universe) [3.30.0-6ubuntu1] (no packageset)
[08:55] <xnox> Laney, yes | no | maybe. https://launchpad.net/ubuntu/+source/ubuntu-meta/1.380
[08:55] <Laney> I saw that
[08:55] <xnox> then there was pitti's email stating that everything is a mess now
[08:55] <Laney> I don't see that one
[08:55] <xnox> then i couldn't find the mess
[08:55] <Laney> It looks like someone put it all in universe
[08:55] <xnox> ah, let's check publishing record.
[08:55] <Laney> https://launchpad.net/ubuntu/+source/unity8/+publishinghistory
[08:56] <xnox> but that was bileto landing
[08:56] <xnox> has bileto gone crazy?!
[08:56] <Laney> what was?
[08:56] <xnox> unity8 publishing
[08:57] <Laney> I don't see what that has to do with it
[08:57] <xnox> it does have AA rights, .... or do we not get a publishing entry when things move between components?
[08:57] <Laney> There is an entry there
[08:57] <jamespage> just checking that the archive is open for artful uploads before I bombard it with half a hundred uploads?
[08:57] <LocutusOfBorg> jamespage, open :)
[08:57] <jamespage> \o/
[08:57] <xnox> jamespage, enjoy!
[08:58] <Laney> jamespage: you can see the status on https://launchpad.net/ubuntu/artful BTW
[08:58] <Laney> It'll say "Frozen" or something if it's frozen
[08:59] <jamespage> Laney: yeah - just making sure
[08:59] <Laney> but Active Development -> go wild
[08:59] <jamespage> Laney: it does say something like pre-release freeze until its open (looked last week)
[08:59] <Laney> yep
[09:01] <jamespage> I love the fact that I can wildcard with dput :-)
[09:02]  * jamespage launches a salvo of uploads
[09:07] <jamespage> if there is an AA around - most of that's going to depwait until the new sync of vine from Debian gets acked - pretty please :-)
[09:11] <apw> xnox, i think infinity had "sorted" component missmatches to 0 and is intending to keep it so
[09:12] <xnox> right. now i'm thinking the emails i got was because there was delay between branch updates; and my meta upload. such that once meta cleared things were fine. but someone still demoted things.
[09:16] <Laney> I would assume that someone used the output of component-mismatches to know what to demote
[09:16] <apw> i am sure that is true
[09:17] <apw> but presumably if meta now needed things they would be in there as new component-missmatches with MIRs already acked
[09:17] <apw> c-m-proposed looks believeably and non-empty
[09:22] <LocutusOfBorg> infinity, do you think I have to reupload llvm-3.7 without the examples package? I still see some sadness there, even after your hammer
[09:28] -queuebot:#ubuntu-release- Unapproved: linux-firmware (zesty-proposed/main) [1.164 => 1.164.1] (core, kernel)
[09:28] -queuebot:#ubuntu-release- Unapproved: rejected linux-firmware [source] (zesty-proposed) [1.164.1]
[11:15] -queuebot:#ubuntu-release- Unapproved: ceph (xenial-proposed/main) [10.2.6-0ubuntu<IP_ADDRESS> => 10.2.7-0ubuntu<IP_ADDRESS>] (kubuntu, ubuntu-desktop, ubuntu-server) (sync)
[11:15] -queuebot:#ubuntu-release- Unapproved: ceph (zesty-proposed/main) [10.2.6-0ubuntu1 => 10.2.7-0ubuntu<IP_ADDRESS>] (kubuntu, ubuntu-desktop, ubuntu-server) (sync)
[11:15] -queuebot:#ubuntu-release- Unapproved: ceph (yakkety-proposed/main) [10.2.6-0ubuntu<IP_ADDRESS> => 10.2.7-0ubuntu<IP_ADDRESS>] (kubuntu, ubuntu-desktop, ubuntu-server) (sync)
[12:12] -queuebot:#ubuntu-release- Unapproved: accepted mtx [source] (yakkety-proposed) [1.3.12-9ubuntu<IP_ADDRESS>]
[12:14] -queuebot:#ubuntu-release- Unapproved: accepted mtx [source] (xenial-proposed) [1.3.12-9ubuntu<IP_ADDRESS>]
[12:17] -queuebot:#ubuntu-release- Unapproved: linux-firmware (zesty-proposed/main) [1.164 => 1.164.1] (core, kernel)
[12:20] <xnox> hehe autopkgtests will take forever to run
[12:27] <xnox> apw, could you please demote these to universe? http://people.canonical.com/~ubuntu-archive/component-mismatches.txt
[12:53] <LocutusOfBorg> remove upstart instead of demote? :)
[13:01] <xnox> LocutusOfBorg, not ready to be removed, demotion is a good start.
[13:01] <xnox> because then we know it's dropping out of tasks.
[13:01] <xnox> and if any remain.
[13:04] <LocutusOfBorg> it was an half joke btw :)
[13:04] <LocutusOfBorg> unity demoted it is also nice
[13:07] <LocutusOfBorg> The requested URL /~ubuntu-archive/proposed-migration was not found on this server.
[13:07] <LocutusOfBorg> is it just me or...
[13:08] <mapreri> not just you
[13:08] <mapreri> some minutes ago it was giving 403 errors, so I guess sysadm are doing something
[13:09]  * LocutusOfBorg fights daily against proxies and bad connections
[13:09] <mapreri> ... and you work on an IT company!
[13:09] <LocutusOfBorg> this is why I have to fight against it folks blocking everything
[13:10] <LocutusOfBorg> security for some customers means block even irc/ssh/git protocols
[13:10] <acheronUK> aha. at least it's not just me
[13:21] <LocutusOfBorg> I have to fetch git repos over https and proxy
[13:21] <Laney> it would be quite something if a 404 error were just experienced by one person :)
[13:21] <LocutusOfBorg> and canonical in the last months is disabling https fetch for git repos
[13:22] <LocutusOfBorg> Laney, when your proxy changes what you see... this happens
[13:22] -queuebot:#ubuntu-release- Unapproved: sssd (xenial-proposed/main) [1.13.4-1ubuntu1.4 => 1.13.4-1ubuntu1.5] (kubuntu, ubuntu-desktop, ubuntu-server)
[13:22] -queuebot:#ubuntu-release- Unapproved: sssd (yakkety-proposed/main) [1.13.4-3ubuntu0.3 => 1.13.4-3ubuntu0.4] (kubuntu, ubuntu-desktop, ubuntu-server)
[13:22] <LocutusOfBorg> not probably at this level, but before downloading it downloads the file for you, and redirect you to a download link if the antivirus is happy
[13:23] <Laney> Anyway
[13:23] <Laney> I believe the machine is down atm due to being upgraded to xenial
[13:23] <LocutusOfBorg> nice :)
[13:23] <sergiusens> ah, that might explain my 503s
[13:23] <LocutusOfBorg> was it on trusty?
[13:24] <Laney> dapper
[13:25] -queuebot:#ubuntu-release- Unapproved: rejected vlc [source] (yakkety-proposed) [2.2.4-4ubuntu<IP_ADDRESS>]
[13:25] <Laney> (that was a joke)
[13:26] <Laney> (a hilarious one)
[13:26] <LocutusOfBorg> I got it :)
[13:26] <Laney> (please laugh)
[13:26] <LocutusOfBorg> seriously, it was on breezy I gues
[13:26] <LocutusOfBorg> *guess
[13:27]  * acheronUK wondered at the symbolism of people.ubuntu.com vanishing
[13:27] <LocutusOfBorg> we had dapper machines on buildd for quite some time IIRC, so it might even not be a joke :)
[13:27] <acheronUK> *canonical
[13:28] <cjwatson> disabling https fetch for git repos> what do you mean?  https fetch from git.launchpad.net works fine ...
[13:28] <LocutusOfBorg> ehm, some repositories I don't remember where
[13:29] <LocutusOfBorg> not git.l.net
[13:29] <LocutusOfBorg> will try to remember
[13:29] <cjwatson> I think it's more likely that something would be broken that that Canonical would be intentionally disabling it, though perhaps there's some weirdness I'm unaware of
[13:30] <LocutusOfBorg> ok, so I will maybe write here in case I find that link
[13:36] <xnox> LocutusOfBorg, bzr http, git https
[13:42] <mapreri> that reminds me that ubuntu-it still has his machine on precise... we should probably complete the preparations for the upgrade...
[13:45] <xnox> mapreri, it can wait, another 4 days
[13:45] <LocutusOfBorg> plenty of time!!!
[13:45] <mapreri> ahem :|
[13:46] <mapreri> if only software would port itself over new libs :(
[13:48] <jamespage> please could an AA accept the sync I did of vine into artful earlier today - that will unblock a number of dep-waits I have in the openstack dependencies for pike-1
[14:08] -queuebot:#ubuntu-release- New binary: libepoxy [ppc64el] (artful-proposed/main) [1.3.1-2ubuntu1] (desktop-core)
[14:09] -queuebot:#ubuntu-release- New binary: libepoxy [amd64] (artful-proposed/main) [1.3.1-2ubuntu1] (desktop-core)
[14:09] -queuebot:#ubuntu-release- New binary: libepoxy [s390x] (artful-proposed/main) [1.3.1-2ubuntu1] (desktop-core)
[14:09] -queuebot:#ubuntu-release- New binary: libepoxy [i386] (artful-proposed/main) [1.3.1-2ubuntu1] (desktop-core)
[14:14] -queuebot:#ubuntu-release- New binary: libepoxy [armhf] (artful-proposed/main) [1.3.1-2ubuntu1] (desktop-core)
[14:14] <zx2c4> infinity: what's the next step with https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1685522 ?
[14:15] -queuebot:#ubuntu-release- New binary: libepoxy [arm64] (artful-proposed/main) [1.3.1-2ubuntu1] (desktop-core)
[14:16] <jbicha> zx2c4: according to https://wiki.ubuntu.com/SponsorshipProcess you should subscribe ~ubuntu-sponsors to the bug
[14:18] <zx2c4> jbicha: thanks just did that
[14:20] <zx2c4> jbicha: so now what?
[14:20] <zx2c4> somebody just needs to "sponsor" me?
[14:20] <zx2c4> seems like most folks are too busy
[14:22] <LocutusOfBorg> let me see
[14:22] <zx2c4> LocutusOfBorg: thanks!
[14:23] <zx2c4> LocutusOfBorg: infinity, cjwatson, and i discussed this strategy of using an empty package pretty extensively last night in this channel
[14:23] <LocutusOfBorg> README.Debian file was nice too
[14:24] <zx2c4> LocutusOfBorg: you want me to add a README.Debian file to it?
[14:28] -queuebot:#ubuntu-release- Unapproved: wireguard (zesty-proposed/universe) [0.0.20170214-1 => 0.0.20170214-1ubuntu0.17.04] (no packageset)
[14:28] <LocutusOfBorg> zx2c4, ^^ I had to tweak it a little bit
[14:28] <zx2c4> LocutusOfBorg: im writing a README.debian and then im going to reupload to the bug, doe sthat sound good?
[14:28] <LocutusOfBorg> nah
[14:28] <LocutusOfBorg> it is fine
[14:28] <zx2c4> oh, cool, okay
[14:28] <zx2c4> so when this says "Unapproved: wireguard ..." what does that mean?
[14:28] <zx2c4> (where can i see your tweaks?)
[14:30] <LocutusOfBorg> https://launchpad.net/ubuntu/zesty/+queue?queue_state=1&queue_text=
[14:30] <LocutusOfBorg> http://launchpadlibrarian.net/316831052/wireguard_0.0.20170214-1_0.0.20170214-1ubuntu0.17.04.diff.gz
[14:30] <LocutusOfBorg> here, just look at my debdiff and compare it to your
[14:30] <LocutusOfBorg> (hint: I removed the .pc directory, changed back to quilt)
[14:33] <zx2c4> LocutusOfBorg: you added back in all those random other files?
[14:33] <zx2c4> i guess thats fine
[14:33] <zx2c4> interesting in any case
[14:34] <zx2c4> debian/ubuntu processes remain mysterious to me
[14:34] <LocutusOfBorg> zx2c4, you changed from quilt to native, so it means the orig tarball is not preserved
[14:34] <LocutusOfBorg> so, patches are not unapplied and a lot of other stuff
[14:34] <zx2c4> i didnt realize we wanted to keep the original tarball?
[14:34] <LocutusOfBorg> and that .pc was a result for that
[14:34] <LocutusOfBorg> yes zx2c4
[14:34] <zx2c4> ahh
[14:34] <LocutusOfBorg> why not?
[14:34] <LocutusOfBorg> security, avoid new tarballs just for fun
[14:35] <LocutusOfBorg> native package is not easy to follow, upstream one is
[14:35] <zx2c4> because it's code that should _not_ persist
[14:35] <zx2c4> but in anycaes, its not a big deal
[14:35] <zx2c4> im just happy that this is in the queue
[14:35] <LocutusOfBorg> we are talking about the upstream package, not the debian changes that prevents it from working
[14:35] <LocutusOfBorg> that version needs to be complete and coherent with what upstream released on that snapshot
[14:35] <zx2c4> even the upstream package. its not a package. or a release. its just some random code dump from one particular day. which is why it shouldnt have been in ubuntu
[14:35] <zx2c4> okay i understand
[14:36] <zx2c4> so what happens next with this queue?
[14:36] <LocutusOfBorg> and your debian/* foo should explain/change that, with patches approach
[14:36] <zx2c4> somebody else presses the "approve" button, and then we're all set?
[14:36] <LocutusOfBorg> zx2c4, now, somebody on release team should approve yes
[14:36] <zx2c4> oh cool, so that's where infinity comes in
[14:36] <LocutusOfBorg> somebody will add verification-needed and you will test/change back to verification-done, explaining the testing you did
[14:36] <LocutusOfBorg> https://wiki.ubuntu.com/StableReleaseUpdates
[14:37] <zx2c4> cool okay
[14:38] <zx2c4> and all that explanation will happen on the original bug report?
[14:42] <LocutusOfBorg> I hope so :)
[14:43] <xnox> Laney, britney runs off snakefruit right? thus i should not expect anything to migrate, until snakefruit is back up?
[14:44] <xnox> and infinity / slangasek fix it up?
[14:44] <cjwatson> xnox: correct
[14:44] <apw> correct
[14:44] <xnox> tah
[16:03] -queuebot:#ubuntu-release- New binary: systemd [s390x] (artful-proposed/main) [233-5ubuntu1] (core)
[16:07] -queuebot:#ubuntu-release- New binary: systemd [ppc64el] (artful-proposed/main) [233-5ubuntu1] (core)
[16:07] -queuebot:#ubuntu-release- New: accepted systemd [s390x] (artful-proposed) [233-5ubuntu1]
[16:10] -queuebot:#ubuntu-release- New binary: systemd [i386] (artful-proposed/main) [233-5ubuntu1] (core)
[17:32] <santa_> dear release wizards,
[17:32] <santa_> I have a question regarding SRU's to zesty
[17:33] <nacc> santa_: what is the question?
[17:33] <santa_> we are considering in kubuntu an SRU for plasma (we have 5.9.4 in zesty and we would like to provide 5.9.5 via an SRU)
[17:33] <santa_> we maintainain in kubuntu ~300 packages, so we have some automation tools
[17:34] <santa_> the easier thing for us would be preparing a _complete_ plasma update
[17:34] <santa_> that means we might have some packages providing a 0-diff update
[17:34] <santa_> would be allowed to do that?
[17:35] <infinity> krytarik: You completely broke the ubuntustudio seeds.
[17:35] <xnox> santa_, as long as it will be tolerable to reject all the 0-diff updates?! e.g. things do not depend on the updated version numbers.
[17:35] <xnox> i think SRU team may be ok with rejecting a bunch of things.
[17:36] <infinity> xnox: You might want to not speak for the SRU team. ;)
[17:36]  * xnox is not ~ubuntu-sru team member
[17:36] <santa_> xnox: we can make it tolerable, yes
[17:36] <infinity> santa_: I have no issues with it conceptually.  It certainly has precedent.
[17:36] <santa_> we just need to not bump the buld depends, that's easy to do, we just disable that in the tooling and that's it
[17:37] <infinity> santa_: The bigger issue is findind someone with the time to process it all, since that used to be ScottK.
[17:37] <santa_> plasma are 42 source packages in case you are wondering
[17:37] <apw> how many of these packages would ... 42 ok
[17:38] <infinity> 42 is a much less scary number than 300.
[17:39] <infinity> santa_: So, yeah.  From our POV, even the 0-change uploads are not a huge burden on *us*.  But you need to think hard about yourself as well, as you do need to verify all those binary builds.
[17:39] <infinity> santa_: Cause part of the SRU process is not trusting something is okay just because it rebuilt with "no changes".  It needs to be installed, run, tested.
[17:39] <infinity> santa_: So, for the 0-change ones, it's probably in your best interest to skip them.
[17:40] <infinity> (For me, I don't much care, it's easy to review sometihng without a change :P)
[17:42] <santa_> infinity: yeah, I get what you mean. a 0-diff is after all a rebuild, so that 'invalidates' somehow the testing we do. I guess we could improve a bit the tooling and the workflow to deal with these kind of things
[17:42] <infinity> santa_: But if you're willing to verify them all and you want the versions to be pretty and match, I'm not going to tell you not to do it.
[17:44] <santa_> regarding the status of artful. I guess we are free to upload now? we already have several things to update
[17:44] <nacc> santa_: archive is open
[17:44] <santa_> plasma 5.9.5 in the first place
[17:44] <santa_> frameworks
[17:44] <santa_> and we also have the kdepim which we couldn't include in zesty, that needs several NEW reviews
[17:46] <santa_> regarding the kdepim this is what we had in zesty: http://gpul.grupos.udc.es/ka-iron-hand_reports/applications_archive/16.12.3_zesty_proposed_migration.pdf
[17:48] <santa_> the kdepim is the bunch of the top, those in dark red are already in the archive, those in grey are not
[17:50] <santa_> so what do you suggest us to do? upload those who are not in the archive first, and then the rest, or just upload them all? we could do any of both with our automation tooling
[17:55] <mapreri> oh, people.c.c is back.
[17:56] <mapreri> was britney also stopped, by any chance?
[17:56] <bdmurray> infinity: Is the Artful release schedule good?
[17:58] <apw> mapreri, yes same machine
[17:58] <infinity> bdmurray: I like it well enough.
[17:58] <infinity> mapreri: people was never gone, but people/~ubuntu-archive is actually a proxy through to another machine (the one that runs britney)
[17:59] <mapreri> ic
[18:06] <bdmurray> infinity: Okay, I was thinking about doing the meta-release file
[18:06] <infinity> bdmurray: Might want to upload u-r-u to artful before you do.
[18:11] <bdmurray> infinity: well, alright
[18:26] <krytarik> infinity: Hurr durr, I was hoping I wouldn't have to duplicate the general 'live' seed file to 'dvd-live' - will do so then.. :/
[18:27] <infinity> krytarik: Well, I'm not entirely sure what your intent is here.
[18:27] <infinity> krytarik: There's nothing wrong with having a dvd-live, but you deleted it.
[18:28] <infinity> krytarik: Deleting it and still having it listed in STRUCTURE makes germinate very unhappy.
[18:29] <infinity> krytarik: Your STRUCTURE references a lot of seeds that don't exist. :P
[18:29] <slangasek> xnox: upstart, cgmanager demoted
[18:29] <infinity> krytarik: live-common and ship-live also aren't a thing in your seeds.
[18:31] <krytarik> infinity: Trust me! :P
[18:31] <infinity> krytarik: No? :)
[18:33] <infinity> krytarik: Oh, scratch the live-common bit, that's in platform, so everyone shares it.
[18:34] <infinity> krytarik: So, that's correct.  But deleting dvd-live was less correct. :P
[18:34] <krytarik> Yes, I see that now. :P
[18:34] <infinity> krytarik: And the bug you were trying to fix, I think, was the lack of ship-live.
[18:35] <infinity> If you even need one.
[18:35] <krytarik> Well, that plus referencing a 'dvd' seed that doesn't exist.
[18:39] <infinity> krytarik: Anyhow, I think reverting that entire last commit and then deleting "live" (moving anything from there that you need into dvd-live), and then sorting out a ship-live seed to fix your other bug would get the job(s) done.
[18:40] <infinity> Although... You don't have a LIVE_TASK in livecd-rootfs.  How does ANY of this work for you?
[18:45] <infinity> bdmurray: Wow, phased-updater takes an amazingly long time to run.
[18:46] <infinity> bdmurray: Are you doing something very slow there like iterating through all SRUs via LP?
[18:57] <krytarik> infinity: Oh meh, I just see Edubuntu, which I've been following for this, has 'include ubuntu.*' rather than just 'platform.*' as we do, so that's why they get away with not having a 'ship-live' seed themselves.  So I guess I'll either copy the Ubuntu or the Xubuntu one, which our seed is otherwise based on.  Also, I was thinking earlier regarding the 'dvd-live' seed, could I just have it ...
[18:57] <krytarik> ... an empty file except the header, and otherwise pull in 'live' as it does now?
[18:58] <infinity> krytarik: An empty file pulling in live would work fine, but we really don't need both "ubuntustudio-live" *and* "ubuntustudio-dvd-live" tasks in the archive.
[18:58] <infinity> krytarik: Just settling on dvd-live and making it behave like edubuntu makes more sense to me.
[18:59] <infinity> krytarik: The only reason to have a split would be if you were producing both size/type images, which you're not.
[19:00] <infinity> I'll note that edubuntu has that same bug. :P
[19:00] <infinity> Not that it's producing images anymore at all.
[19:02] <krytarik> And yes, adding a LIVE_TASK for it would be nice then indeed, I see. :P
[19:04] <infinity> I'm not actually sure where dvd-live comes into play for edubuntu, now that I look...
[19:06] <infinity> krytarik: Anyhow, unwinding all of that and sorting out what you actually need/want to do could be some back and forth.
[19:06] <infinity> krytarik: Could you please just revert your last commit (or I will), so it stops breaking infrastructure? :P
[19:07] <krytarik> infinity: Sure, asap.  Would you be fine with an --overwrite there? :P
[19:07] <infinity> No.
[19:07] <infinity> That'll break anyone who updates with a pull.
[19:07] <infinity> Which icludes the aforementioned infrastructure.
[19:08] <infinity> Never ever go back in time in a shared repository unless you control all the checkouts.
[19:13] <krytarik> Alright, if there are copies of it someplace indeed..  And well, it should be easy enough to fix properly now that I know more about it.
[19:18] -queuebot:#ubuntu-release- Unapproved: distro-info-data (precise-proposed/main) [0.8ubuntu0.11 => 0.8ubuntu0.12] (ubuntu-server)
[19:24] <cjwatson> Copying Edubuntu is probably a bad idea.
[19:24] <cjwatson> It was complicated and weird to set up that way.
[19:25] <cjwatson> There was some special reason for it that I now forget.
[19:33] <krytarik> infinity: Look good to you?: http://paste.openstack.org/show/MpSB7IDbQ03QyYeOgvPD/
[19:35] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (precise-proposed) [0.8ubuntu0.12]
[19:35] <infinity> krytarik: I dunno.  The surefire way to not mess up a revert is to do a revert. :P
[19:36] <infinity> krytarik: ie: bzr revert -r1507
[19:36] <krytarik> Well, I don't want to go back to where it doesn't have any 'pool/'.. :P
[19:38] <infinity> krytarik: Fair enough, though the actual bug that was meant to be fixed by giving you a pool won't be fixed.
[19:38] <infinity> In that you don't ship grub-efi-whatever anywhere.
[19:39] <krytarik> Pretty sure it will..?
[19:41] <infinity> krytarik: How?  Your seeds don't reference grub-efi-amd64-signed anywhere.
[19:43] <krytarik> Err, look again at the paste?
[19:44] <infinity> krytarik: Oh, in the uncommitted revision, sure.
[19:44] <infinity> krytarik: I was looking at the current and saying that reverting from current to current-1 wouldn't regress anything.
[19:45] <infinity> krytarik: Yes, there's a fair chance that paste will fix things.
[19:55] <krytarik> infinity: Done.
[20:12] <bdmurray> slangasek: https://code.launchpad.net/~brian-murray/apport/lp-retracer-config-artful/+merge/323074
[20:13] <slangasek> bdmurray: is this on the release-opening checklist, or if not could you add it?
[20:14] <slangasek> (merged)
[20:14] <bdmurray> slangasek: it is just slightly wrong
[20:16] <slangasek> bdmurray: and I've dropped powerpc for 17.*
[20:18] <bdmurray> slangasek: noted
[20:34] -queuebot:#ubuntu-release- Unapproved: accepted network-manager [source] (yakkety-proposed) [1.2.6-0ubuntu1.1]
[20:54] <krytarik> infinity: Oh no, now it's moaning at a missing 'dvd' seed file still - not sure what should be in there though..
[20:55] <infinity> krytarik: The edubuntu dvd file looks useful, minute the ltsp bit.
[20:55] <infinity> krytarik: (ie: all the langpacks)
[20:56] <infinity> krytarik: The edubuntu dvd-langsupport also looks handy.
[20:56] <infinity> I mean, if you care about translations.
[21:00] <krytarik> I think the image is bloated enough already as it is.. :P
[21:03] <infinity> krytarik: An empty (well, comment-only) dvd file might do the trick too.  Along with the cdimage change you proposed.
[21:04] <krytarik> Yeah, just thought the same.
[21:10] <krytarik> infinity: ..I'm stuck at the comment part now. :P
[21:11] <infinity> "This seed exists only to gather together all the other dvd seeds."
[21:11] <infinity> See platform/support-common for prior art. :P
[21:12] <krytarik> Yes! \o/
[21:14] <infinity> krytarik: Bonus points for comitting and pushing the fix?
[21:16] <krytarik> Sure, am on it.
[21:21] <krytarik> infinity: Done.
[21:25] <rcj> slangasek: can we bump distro-info-data out of precise-proposed?
[21:26] <slangasek> rcj: do you mean release it or supersede it?
[21:26] <rcj> slangasek: release it, sorry for being imprecise
[21:27] <rcj> That's being super aggressive on the timing but it's blocking image builds and the nature of the change is low-risk.
[21:27] <slangasek> rcj: at the moment I'm wondering why it's not showing up on http://people.canonical.com/~ubuntu-archive/pending-sru.html; <-- infinity, snakefruit fallout?
[21:28] <rcj> possibly, last update ~90m ago?
[21:28] <rcj> Also hasn't automatically approved the nominated track in bug #1685055
[21:29] <slangasek> rcj: it ignores the nomination and creates the bug task outright, so the nomination is still there
[21:29] <rcj> oh, there is a precise series entry.  It's just also showing my nomination message.
[21:30] <slangasek> rcj: released
[21:30] <rcj> slangasek: Thank you
[21:32] <slangasek> infinity: so what is taking update-germinate so long?
[21:36] <infinity> slangasek: I suspect it might always take this long, I just normally never have something I want to do. :P
[21:37] <infinity> slangasek: But I have a manual archive-reports running too now, since halting the world on update-germinate was apparently not a solid plan.
[21:37] <slangasek> infinity: really? why shouldn't this be a no-op for stable releases?
[21:37] <slangasek> infinity: you do? does that mean you killed mine, or did it die on its own?
[21:37] <infinity> You had one running?
[21:38] <slangasek> infinity: from a minute after I asked you about update-germinate ;)
[21:38] <infinity> slangasek: Mine's been running longer.  So, the more interesting question is if you killed mine, or if yours is spinning on a lock, or if you didn't notice it exited. :P
[21:39] <infinity> slangasek: Oh, or mine exited already.
[21:40] <slangasek> infinity: ps really thinks mine was the only one running when I checked :)
[21:40] <infinity> Possibly due to the chdist bug I fixed.
[21:40] <slangasek> but mine exited non-zero
[21:40] <infinity> slangasek: Yours is running currently?
[21:40] <slangasek> no
[21:40] <slangasek> wait
[21:40] <slangasek> yes
[21:40] <infinity> 30020 pts/5    S      0:00 /bin/sh /home/ubuntu-archive/bin/archive-reports
[21:40] <infinity> 30022 pts/5    S      0:00  \_ /bin/sh /home/ubuntu-archive/bin/run-proposed-migration
[21:40] <infinity> pts/5 is you, so...
[21:40] <infinity> UNIX is hard.
[21:41] <slangasek> but it detached from the tty...
[21:41] <slangasek> wat
[21:41] <infinity> The background_and_wait stuff probably behaves weirdly with a controlling terminal.
[21:41] <slangasek> and $HOME/.archive-reports.lock is absent
[21:43] <infinity> Oh, yay, not whining about SSL certs anymore.
[21:52] -queuebot:#ubuntu-release- New: accepted systemd [i386] (artful-proposed) [233-5ubuntu1]
[21:53] -queuebot:#ubuntu-release- New: accepted systemd [ppc64el] (artful-proposed) [233-5ubuntu1]
[22:01] <infinity> slangasek: So, have you found anything broken yet?  I've only had to fix chdist so far, it seems.
[22:02] <infinity> Hrm, archive-reports is clearly exiting early, cause no component-mismatches.
[22:03] <slangasek> infinity: haven't pinpointed the breakage, but yeah, pending-sru is not updated either
[22:03] <infinity> Right, time to -x it.
[22:03] <infinity> And see where it bombs.
[22:03] <infinity> Ideally only one of us. :P
[22:03] <slangasek> infinity: go ahead :)
[22:04] <infinity> Watch it succeed this time, since I think I fixed chdist after you started your last run.
[22:05] <infinity> Anyhow, running with much spew.
[22:25] <infinity> slangasek: We have component-mismatches this go around. \o/
[22:26] <infinity> slangasek: Note that pending_sru doesn't come from archive-reports, it's out of band (and not running because I disabled the whole crontab)
[22:26] <infinity> But it did have one successful run since reboot, I think.
[22:31] <slangasek> ok
[22:41] <infinity> slangasek: Oh.  When you ran archive-reports, did you run it straight, or with the PYTHONPATH bits from crontab?
[22:41] <infinity> (I ran mine straight and it succeeded)
[22:41]  * infinity is running every other bit of contrab by hand to see how they fare.
[22:41] <infinity> contrab!
[22:41] -queuebot:#ubuntu-release- Unapproved: gnome-calendar (zesty-proposed/main) [3.24.0-0ubuntu1 => 3.24.1-0ubuntu0.1] (desktop-extra, ubuntu-desktop)
[22:42] <slangasek> infinity: ah I had grabbed PATH but missed PYTHONPATH
[22:42] <infinity> slangasek: Okay, so we both ran it without the altered PYTHONPATH.  Curious.
[22:43] <infinity> (I suspect that's obsoleted by xenial having new enough whatever)
[22:45] <slangasek> infinity: there's not much /in/ pythonpath; it's probably lazr that's been updated
[22:45] <infinity> And germinate from git, which we want to keep doing, IIRC.
[22:45] <slangasek> yeah
[22:45] <infinity> As Colin's given up on SRUing it.
[22:46] <slangasek> lazr in xenial is now newer than the one we have in ~/python
[22:46] <slangasek> six should probably go
[22:46] <slangasek> the other bits probably still belong
[22:47] <slangasek> six is 1.8.0 (~/python) vs. 1.10.0 (xenial)
[22:47] <infinity> Kay, go ahead and whack that, IMO.
[22:47] <infinity> archive-reports clearly ran fine without the downgrade.
[22:47] <slangasek> removed the links; keeping the trees until we're sure everything that uses PYTHONPATH is happy
[22:48] <infinity> Almost through crontab.
[22:48] <infinity> Won't restore it until after one more reboot to make systemd stop whining.
[22:49] <infinity> krytarik: I fixed your fix, FWIW.  germinate doesn't hate your seed anymore.
[22:49] <infinity> krytarik: (No guarantees it'll do the things you want it to do, but at least it's not exploding)
[22:53] <infinity> slangasek: And have a fresh pending_sru.
[22:53] <slangasek> tada
[22:54] <infinity> Two of stgraber's reports running, and if those complete, I'm calling snakefruit done, ish.
[22:54] <infinity> Which turned out to be a lot less painful than I'd thought.
[22:56] <infinity> Oh, hrm.  No.  old britney (used for /testing/ and /testing-ports/) might be broken.  But I can sort that out without holding up everything else.
[23:01] <infinity> slangasek: Ahh, slight stay of execution on some bits that cheat and schroot into the trusty-transitions chroot.  Likely because precise was too old. :P
[23:02] <infinity> slangasek: So, we'll probably want to upgrade that schroot $later, do some testing, and then decide if we even need it anymore.
[23:02] <infinity> Well, upgrade, or create a parallel one to test in.
[23:08] <krytarik> infinity: Given there was a seemingly successful run of Germinate before that addition, it wasn't entirely necessary though, right?
[23:09] <infinity> krytarik: It was necessary.  I hacked it in production to test before committing. :P
[23:11] <krytarik> Ah. :P
[23:21] <cjwatson> slangasek: update-germinate routinely takes forever because it's emitting the full rdepends tree.
[23:21] <slangasek> cjwatson: and it's intentional that this isn't short-circuited for e.g. trusty?
[23:21] <cjwatson> slangasek: it certainly was intentional at one point, because I wanted to keep seeing updates
[23:21] <slangasek> ok
[23:22] <cjwatson> (I think it looks at -updates; haven't checked recently)
[23:22] <cjwatson> feel free to override this if you don't think it's useful enough to merit it of ocurse
[23:22] <cjwatson> *course
[23:22] <infinity> Yeah, the taking forever thing isn't really an issue when it's not blocking me rebooting. ;)
[23:22] <cjwatson> if so you should just do it by removing things from the update-germinate script
[23:22] <infinity> It could also be mitigated by parallelizing it, but I think running single-threaded is better to keep it out of the way.
[23:23] <infinity> I just whacked a bunch of vivid for flavours that clearly won't care (ie: almost everyone), which will help some.  And precise will go away in 4 days.
[23:30] <cjwatson> It could also be mitigated by doing some of what I did to speed things up in Launchpad.
[23:30] <cjwatson> Or rather on the publisher machine.
[23:30] <cjwatson> We can't share the processing that depends on the seed data, but we can share the processing that depends on the input Packages files.
[23:31] <cjwatson> See lp:ubuntu-archive-publishing lib/scripts/generate_extra_overrides.py
[23:31] <infinity> cjwatson: Yeah, but wasn't the major win there parallelisation?
[23:32] <infinity> Which I think we don't want on snakefruit, as we'll get massive spikes instead of the smooth munching of one core.
[23:32] <cjwatson> That helped, but sharing the output of duplicated processing steps helped too.
[23:32] <infinity> Ahh.
[23:32] <infinity> So we could maybe reuse that bit.
[23:32] <cjwatson> Emitting rdepends is still going to be terrible though, and that's one of the most useful bits of that output.
[23:33] <cjwatson> I think the correct fix there is to output a DB of some kind and have a little webapp to render bits of it as needed.
[23:33] <cjwatson> Rather than the gigantic tree of a zillion little files.
[23:33] <infinity> On the other hand, the nice lasy at A&W thought I looked grumpy and gave me a root beer lollipop.
[23:33] <infinity> Which, it turns out, is awesome.
[23:34] <infinity> s/lasy/lady/
[23:34] <cjwatson> Score one for looking grumpy.
[23:34] <cjwatson> Oh.  I thought that was a Canadian spelling of lassie.
[23:34] <infinity> I knew it would pay off eventually.
[23:34] <infinity> Just didn't think I'd wait 39 years.
[23:35] <infinity> I don't really want to know what science goes into making a hard candy taste like a carbonated beverage, do I?


[15:01] <CIA-4> apt-setup: cjwatson * r185 ubuntu/ (44 files in 5 dirs): merge from Debian 1:0.45
[15:06] <CIA-4> apt-setup: cjwatson * r186 ubuntu/ (16 files in 8 dirs): Add Release files for maverick.
[15:07] <CIA-4> apt-setup: cjwatson * r187 ubuntu/debian/control: bump build-dep for debhelper overrides
[15:10] <CIA-4> apt-setup: cjwatson * r188 ubuntu/debian/changelog: releasing version 1:0.45ubuntu1
[16:36] <kirkland> cjwatson: hi
[16:36] <kirkland> cjwatson: could you have another look at https://bugs.launchpad.net/bugs/569900
[16:36] <ubot2> Launchpad bug 569900 in mdadm (Ubuntu Lucid) (and 3 other projects) "mount: mounting /dev/md0 on /root/ failed: Invalid argument (affects: 9) (heat: 66)" [High,Confirmed]
[16:37] <kirkland> cjwatson: the dupes and confirms are piling up now
[16:37] <kirkland> cjwatson: looks like 500GB drives are almost always the affected
[16:40] <cjwatson> kirkland: only if there's some way for me to reproduce it.  Does anyone have a reproduction recipe in KVM?
[16:40] <cjwatson> and did you get anywhere with my hint in comment 17?
[16:58] <CIA-4> debian-installer-utils: cjwatson * r695 ubuntu/ (30 files in 3 dirs): merge from Debian 1.75
[17:01] <CIA-4> debian-installer-utils: cjwatson * r696 ubuntu/debian/changelog: releasing version 1.75ubuntu1
[17:32] <robbiew> cjwatson: ping
[17:38] <cjwatson> robbiew: hi
[17:38] <robbiew> cjwatson: quick question
[17:38] <robbiew> is there a known issue with the installer minimizing itself during install...on a netbook
[17:39] <cjwatson> not one I've heard of - ev?
[17:39] <ev> not that I'm aware of
[17:39] <robbiew> so I spent an hour with sister on the phone trying to figure out why she couldn't install
[17:39] <ev> robbiew: can you elaborate?
[17:39] <cjwatson> there's the bug that it *can* be minimised
[17:39] <robbiew> she would go through the 7 steps
[17:39] <cjwatson> bug 249045
[17:40] <ubot2> Launchpad bug 249045 in ubiquity (Ubuntu) (and 1 other project) "installer can be minimized (dups: 1) (heat: 10)" [Medium,Confirmed] https://launchpad.net/bugs/249045
[17:40] <robbiew> and then the installer minimizes to the background
[17:40] <cjwatson> which I suppose might have been triggered by an accidental keystroke or something
[17:40] <robbiew> so she thought it was done
[17:40] <robbiew> when it hadn't started
[17:40] <robbiew> so when she would reboot...she was rebooting in the middle of the partioning
[17:41] <robbiew> it wasn't until I did the install myself that I noticed it
[17:41] <ev> we should really inhibit rebooting
[17:41] <robbiew> all she had to do was click on the minimized icon in the upper left
[17:41] <ev> when ubiquity is running
[17:41] <robbiew> and the slideshow popped up with all its goodness
[17:41] <ev> robbiew: so you personally witnessed the installer minimizing itself?
[17:42] <robbiew> yep
[17:42]  * ev blinks
[17:42] <robbiew> after I said "Install"
[17:42] <robbiew> I went back to the UNE screen
[17:43] <ev> ohhh, this must be netbook-launcher specialness
[17:44] <ev> robbiew: can you file a bug, please?
[17:44] <robbiew> sure thing
[17:44] <ev> much appreciated
[17:45] <robbiew> ev: against the installer?
[17:45] <ev> robbiew: http://launchpad.net/ubuntu/+source/ubiquity/+filebug - probably the best place for it until we can find out what's causing this
[17:46] <robbiew> ack


[02:03] <cwayne_> thomi, hiya, is there a way to specify which dir autopilot run looks in for tests? or is it always just cwd?
[02:04] <veebers> cwayne_: you can pass autopilot either a python module (that's local or exists in PYTHONPATH) or give it a path itself
[02:05] <veebers> As long as the path is importable
[02:05] <cwayne_> veebers, so just 'autopilot3 run /path/to/my/tests' as long as tests/ has an __init___.py?
[02:06] <veebers> cwayne_: should work, just double checking now as I now recall there was a catch of some sort :-)
[02:07] <cwayne_> hm, didn't seem to work :/
[02:07] <veebers> cwayne_: hmm, I may have lied to you
[02:08] <cwayne_> :(
[02:08] <veebers> cwayne_: yeah sorry doesn't work for me, I have miss-remembered how that works :-\
[02:09] <cwayne_> yeah, it tries to load it from 1 dir below for some reason
[02:09] <cwayne_> so i guess i'd have to hack together a script to cd to the right dir first..
[02:10] <cwayne_> seems like a good feature request though :)
[02:14] <veebers> cwayne_: sorry connection issues. Can I ask what you're attempting there should be a way to do it
[02:16] <cwayne_> veebers, calling autopilot run from checkbox-touch
[02:19] <veebers> cwayne_: this works for me (uses the trunk copy not dist): PYTHONPATH=~/code/touch-apps/camera-app/trunk/tests/autopilot python3 -m autopilot.run list camera_app
[02:20] <veebers> where tests/autopilot/ contains a dir 'camera_app' that is importable (with __init__.py)
[02:21] <cwayne_> veebers, problem is i kinda have to do some hackery already with pythonpath, since checkbox-touch is a click package
[02:22] <veebers> cwayne_: ah right. Man, I could have sworn that we had made it so you could just give autopilot a path to use.
[02:23] <cwayne_> it seems like it should be that way i'd think
[02:43] <veebers> cwayne_: yeah totally a bug. Well I can see where it goes wrong, not sure of a fix yet but I'll file a but anyway
[02:43] <cwayne_> veebers, thanks!
[02:44] <veebers> cwayne_: can you give us an idea of priority so that we can put that card on our backlog?
[02:47] <cwayne_> veebers, probably lowish, I think I can just cd to a different dir in a bash script for now
[02:48] <veebers> cwayne_: ack thanks. Bug filed will put it on our backlog as I imagine you're not the only one that would like to run from a path (https://bugs.launchpad.net/autopilot/+bug/1470307)
[02:55] <cwayne_> veebers, thanks man


[00:00] <maco> yofel: http://mackenzie.morgan.name/tmp/kwin_crash_handler.png
[00:00] <maco> jbicha:  my graphics card is irrelevant. its a vm. and there is no kdm involved in booting the live cd
[00:01] <BUGabundo> maco: what GPU?
[00:01] <maco> intel, as always
[00:01] <maco> but thats not whats inside the vm
[00:01] <BUGabundo> right
[00:02] <jbicha> maco: perhaps you'll need to install natty & then upgrade unless you want to report iso bugs
[00:02] <maco> jbicha: im working on ubiquity
[00:04] <jbicha> well you can do some ubiquity work on an already installed system
[00:04] <yofel> does kwin work at all after that? Or is that a fatal crash?
[00:05] <yofel> IIRC I did get a kwin crash once too when opengl didn't work right here, which would be the case too in KVM.
[00:05] <jbicha> it sometimes take the vm devs a while to support the latest kernel & graphics stacks
[00:06] <jo-erlend> uhm. I'm curious to have a look at what 11.10 looks like. Should I use the latest alpha, or the daily?
[00:06] <yofel> if you want to look at it use the daily. (if it boots)
[00:09] <jo-erlend> if I add persistence to the usb stick, then I can install software including drivers, yes?
[00:10] <yofel> yes
[00:12] <jo-erlend> guess it'll only be a quick peek now, but if it works well, I guess I'll test it more thoroughly on my boxes. I've usually waited a little longer before testing, so I'm not entirely sure what to expect :)
[00:16] <jo-erlend> will firefox get overlay scrollbars during this cycle, you think?
[00:21] <jo-erlend> one thing I don't understand, if why they always call the isos for ubuntu, xubuntu, kubuntu, etc by the exact same name. That's kinda annoying when you want to download any test several images.
[00:22] <yofel> I think they're just created in the same way by the same way.
[00:23] <jbicha> jo-erlend: you could use testdrive or dl-ubuntu-test-iso to automatically put the isos in separate folders
[00:23] <jo-erlend> oh. I didn't know that.
[00:23] <yofel> having the same names makes things easier to script too
[00:24] <jo-erlend> how is that?
[00:25] <yofel> simply switching subfolder is usally easier than parsing iso names, but don't ask me
[00:25] <maco> yofel: fatal
[00:26] <yofel> :(
[00:26] <maco> yofel: if i exit the crash thingy it just stays a black screen and X cursor. there's nothing else
[00:26] <jo-erlend> oneiric-*-desktop-arc.iso? :)
[00:26] <maco> no menus...no krunner
[00:27] <yofel> no idea, talk to mgraesslin. Perhaps its fixed in rc2
[00:49] <jo-erlend> I sure hope we'll be able to replace those sounds by 12.04....
[00:51]  * yofel passionately hates system sounds, no matter if it's gnome or kde
[00:55] <maco> yofel: hmm ya know, kwin must still be running because the crash handler has decorations
[00:55] <maco> or must have restarted at least
[00:55] <maco> but there's still no plasma
[00:56] <yofel> when I got the kwin crash the desktop didn't start either, had to restart X. After the crash kwin disabled the GL checks and the desktop came up fine
[00:57] <maco> how do you restart X? theres no kdm
[00:58] <jbicha> maco: can you get to a virtual terminal
[00:58] <maco> yes
[00:58] <yofel> well, kdm should be running, just with auto-login, so restarting kdm should work
[00:58] <maco> nope
[00:58] <maco> sudo service restart kdm      told me that kdm wasnt running
[00:58] <yofel> :S
[00:59] <maco> and its not ubiquity-dm either, which is the only result on    ps -ef | grep dm
[01:02] <BUGabundo> startx ?
[01:03] <maco> x is already running though, i think?
[01:03] <BUGabundo> ps it ?
[01:03] <rww> Alt-SysRq-K would kill X, wouldn't it?
[01:03] <maco> hmm maybe not
[01:03] <BUGabundo> not in a VM
[01:03] <rww> oh, true.
[01:03] <maco> libkexec was running drkonqi
[01:03] <maco> which i think is like using xinit
[01:04] <maco> startx didnt like that...probably because kexec's already got :0
[01:05] <maco> i cant figure out how to kill the currently running X session
[01:05] <maco> which is interesting since there are no X processes
[01:05] <maco> oh wait got it
[01:06] <maco> there was one, but sudo...
[01:06] <maco> now i have a black background again but this time with a folderview widget. slight improvement at least
[01:12] <maco> ...and then the whole thing crashed and went all i/o error on me. lovely.
[01:18] <BUGabundo> I had that 3 weeks ago
[01:18] <BUGabundo> then switched to lubuntu
[01:19] <BUGabundo> will reboot tonight for the 1st time in many days
[01:19] <BUGabundo> and retry Gnome again
[01:33] <jo-erlend> I have to say it's looking good. Unity2d is really impressive.
[01:33] <jo-erlend> is it intentional that you can no longer get a context menu on the desktop?
[01:34] <jo-erlend> ohh. It was just a nautilus crash :)
[01:35] <BUGabundo> ntie
[01:35] <jo-erlend> ntie?
[01:37] <jo-erlend> oh. Good night. :)
[01:38] <jo-erlend> I'm off myself. Very late.
[05:59] <jakubo> hi again... something is being weird with sound for me in  ubuntu... on my intel sound based laptop the login jingle from empathy and pidgin have become a mere click with yesterdays updates...
[08:10] <daniel__> hello i have been trying everything i can to get my wireless working and keep seem to get to no matter what i do i use a Broadcom Corporation BCM4311 802.11b/g WLAN [14e4:4311] (rev 01)
[08:10] <daniel__> would anyone have any suggestions?
[08:10] <daniel__> it worked before i updated to 11.04
[10:29] <om26er> after using arrow keys cursor does not move for a second or two whats the problem?
[10:30] <om26er> seems like happens with every key press :/
[10:44] <antihero> Hmm, just grabbed the latest kernel
[10:45] <antihero> nvidia drivers don't work, so I tried the ones downloaded and it claims I don't have the source
[10:45] <antihero> Which is untrue
[10:45] <antihero> as linux-source was also upgraded
[10:48] <antihero> Could nouveau be a an alternative?
[10:59] <antihero> any idea why Nouveau not working
[11:12] <gunni_> Hi. Is the number behind the kernel version in ubuntu consistent with the RC kernel? I.e. Is linux-image-3.0.0-6 = kernel 3.0 RC6 ?
[11:14] <dr_willis> hmm.  never noticed
[11:14] <dr_willis> ! info linux-image
[11:15] <gunni_> I ask because a fix i depend on seems to be in RC7 and the actual kernel in oneiric is 3.0.0-6 ... ok, i may try and see, but knowing would be nicer :)
[11:17] <dr_willis> the apt package info may state the actual source version
[11:18] <geser> gunni_: I'm not sure if this doesn't code the kernel-module ABI (but better ask in #ubuntu-kernel if you want to know for sure)
[11:18] <albert23> gunni_: there is no direct match. 3.0.0-5.6 was already based on rc7
[11:18] <albert23> changelog will tell
[11:18] <gunni_> albert23: Thanks, i will try it now, and hope the fix is in.
[11:19] <gunni_> albert23: How to find the changelog?
[11:19] <albert23> aptitude changelog linux-image-3.0.0-6-generic
[11:20] <albert23> or which kernel version you use
[11:20] <geser> or /usr/share/doc/$pkg/changelog.Debian.gz (if you have the package already installed)
[11:20] <gunni_> thx
[13:36] <seif> hey guys
[13:36] <seif> since today i cant login into my desktop anymore
[13:40] <nyuszika7h> seif: can you log in to a tty (Ctrl-Alt-F1, Ctrl-Alt-F2 etc.)?
[13:40] <seif> nyuszika7h, yeah i can
[13:40] <seif> :)
[13:41] <nyuszika7h> Try this:
[13:41] <nyuszika7h> $ sudo /etc/init.d/?dm restart
[13:42] <nyuszika7h> Replace '?' with your desktop manager's first letter (e.g. 'g' for Gnome, 'k' for KDE, and so on.)
[13:42] <seif> i did that with gdm and lightdm
[13:42] <seif> but both then don allow me to insert a password
[13:42] <seif> they restart
[13:42] <seif> however the kdm works
[16:24] <h00k> I'm waiting for my boot-time to go back down in Oneric ;) It was 7.8 something seconds in Natty, and it's back up to 22 in Oneric.
[16:26] <yofel> use bootchart and find out what's causing it
[16:27] <h00k> I have bootchart, that's why I know the differences, but I haven't gone through it yet to figure it out.
[16:27] <KM0201> h00k: ouch
[16:55] <BluesKaj> hiyas
[17:22] <antihero> Does nvidia-current work with the latest kernel yet
[17:27] <trism> antihero: I haven't tested it with 3.0.0-6 yet but it works with 3.0.0-5 (I imagine it will probably work with the latest as well though)
[17:32] <antihero> trism: Worked ine with -5
[17:32] <antihero> but has a problem with -6 it seems :(
[17:32] <antihero> "Module build for the currently running kernel was skipped since the
[17:32] <antihero> kernel source for this kernel does not seem to be installed.
[17:32] <antihero> "
[17:32] <antihero> Even though linux-source is installed
[17:32] <trism> antihero: ahh, alright, I'm gonna go test as soon as I finish upgrading
[17:33] <trism> antihero: you don't need the linux-source package for nvidia-current, you need the linux-headers package
[17:33] <antihero> trism:  ah, okay. I'll make sure i've got that
[17:35] <antihero> I can't wait 'till nouvaeu supports my 460
[17:35] <antihero> high res console is yummy
[17:39] <antihero> trism: linux-headers also installed
[17:39] <antihero> :C
[17:41] <antihero> http://paste.pocoo.org/show/444398/ <<<
[17:48] <trism> antihero: gonna reboot and see what happens with my system
[17:52] <antihero> don't expect a display
[17:52] <antihero> but you might be cool
[17:55] <trism> antihero: strangely, it didn't build here initially either, I forced a rebuild with: sudo apt-get install --reinstall linux-headers-$(uname -r); (after booting into 3.0.0-6) then I could: sudo modprobe nvidia-current; and start lightdm
[17:55] <yofel> hm, true, 3.0.0-6 is installed here, but dkms status shows that none of the dkms modules were built with it
[17:55]  * yofel is still running 3.0.0-5
[17:57] <yofel> trism: 'sudo dkms autoinstall -k 3.0.0-6-generic' would've been shorter ^^
[17:57] <micahg> anyone else get a conffile prompt on the 3.0.0-6 upgrade?
[17:58] <micahg> *kernel
[17:58] <yofel> didn't get one here
[17:58] <trism> here either
[17:58] <charlie-tca> none here
[17:58] <micahg> k, will chalk it up to system weirdness
[17:58] <charlie-tca> micahg: locally modified, maybe?
[17:58] <micahg> not that I know of
[17:58] <trism> yofel: I will have to remember the for later
[18:06] <robin0800> any one else noticed this when wireless not connected from sys log every minuet NetworkManager[503]: nm_supplicant_config_get_pkcs11_engine_path: assertion `NM_IS_SUPPLICANT_CONFIG (self)' failed
[18:40] <jakubo> hi, i got a problem recovering from chroot, it says bin/bash has a false format....
[18:40] <jakubo> when chrooting
[18:42] <yofel> that happens if you run a 32bit kernel and try to chroot to a 64bit system
[18:43] <jakubo> you mean... ah fuck... so i need a different live cd version
[18:43] <jakubo> thx a lot ;)
[18:46] <BUGabundo> good afternoon folks! dead dead DEAD tired  but karting was great
[19:18] <antihero> trism: So nvidia-current works for you now?
[19:19] <trism> antihero: yes
[19:19] <antihero> Excellent
[19:19] <antihero> I'll give that a shot
[19:19] <antihero> And switch to lightdm for the hell of it
[19:23] <BUGabundo> I need to recall what's the safe procedure to go back to nouveua
[19:23] <BUGabundo> bjsnider: ^^^^^
[19:23] <BUGabundo> where's sarvat when I need him?
[19:23] <yofel> remove the package and xorg.conf?
[19:23] <Ian_Corne> just removing xorg.conf is enough methinks
[19:24] <Ian_Corne> It's what I always do at least
[19:24] <BUGabundo> yofel: I'm afraid even to try
[19:25] <BUGabundo> already spent 8 days without X this cycle
[19:25] <BUGabundo> must be a record
[19:25] <Ian_Corne> just remove you xorg
[19:25] <yofel> Ian_Corne: that works without problems? Because the nvidia package blacklists the module
[19:25] <Ian_Corne> oh
[19:25] <Ian_Corne> maybe vesa takes over then :)
[19:25] <BUGabundo> going on 3 weeks without gnome LOL
[19:25] <Ian_Corne> I don't know, but removing the conf allows me to log in graphically
[19:25] <BUGabundo> lubuntu user :\ and its not pretty
[19:26] <Ian_Corne> i'll check next time yofel :)
[19:26] <yofel> k
[19:26] <Ian_Corne> of to the bars now!
[19:26] <Ian_Corne> wooot
[19:26] <Ian_Corne> jockey fails to activate nvidia-current atm for me
[19:26] <BUGabundo> bars?
[19:29] <BUGabundo> dinner, bbl
[19:32] <antihero> Hmm, can't get lightdm working at all
[19:32] <antihero> It just is a blanscreen
[19:32] <antihero> damn lag
[19:35] <trism> antihero: did you install a greeter with lightdm? it only recommends one, so you might not have one (probably lightdm-greeter-example-gtk unless you want to edit /etc/lightdm/lightdm.conf to choose another)
[19:35] <antihero> trism ah ok
[19:35] <antihero> what's the advantage of it over gdm
[19:40] <antihero> WHAT THE HELL UNITY?!
[19:40] <antihero> Why is it overriding Ctrl+Tab ?!?!
[19:41] <antihero> Who's insane idea was this
[20:05] <jo-erlend> wow... They're blowing up my home town. Oslo looks like a war zone and I walk past that exact area almost every day. I'm talking a few meters away and at that time. I'm really happy I've been programming at home today....
[20:20] <charlie-tca> jo-erlend: glad to hear you are safe today,then.
[20:20] <charlie-tca> That is a frightening experience all the same
[20:20] <jo-erlend> thank you, yes, so am I.
[20:25] <BUGabundo> glad you are all right jo-erlend
[20:25] <BUGabundo> hope no friends, family or acquaintance have been hurt
[20:26] <BUGabundo> anyone tracking http://opendedup.org/ ?
[20:27] <charlie-tca> That website is a mess
[20:27] <charlie-tca> apparently, 14pt fonts are too big for them
[20:27] <charlie-tca> most of the sentences are  cut off
[20:28] <BUGabundo> yeah, stuff goes over tables
[20:29] <BUGabundo> can't even read it in android browser
[20:45] <BUGabundo> I seem to have lost sound controls :\
[20:45] <BUGabundo> and no libnotify in lubuntu
[20:48] <charlie-tca> in lubuntu?
[20:48] <charlie-tca> you give gnome up now?
[20:56] <BUGabundo> charlie-tca: its not working for me
[20:56] <BUGabundo> unity or gnome3 is missing the applet bars or what ever
[20:56] <BUGabundo> gnome classic says its not installed and logs me out
[21:12] <BUGabundo> charlie-tca: any ideas what packages I would need to get Classic to work?
[21:12] <BUGabundo> I already made sure I had Ubuntu-desktop :\
[21:13] <BUGabundo> I'll try gnome-applets :D
[21:14] <charlie-tca> They removed classic from oneiric
[21:14] <charlie-tca> now got unity2d and unity3d
[21:15] <yofel> gnome 3 fallback should work though?
[21:15] <charlie-tca> 2d is the fallback
[21:15] <charlie-tca> it works for me here
[21:15] <BUGabundo> charlie-tca: I can't use either
[21:15] <BUGabundo> where are MY options?
[21:15] <charlie-tca> xubuntu?
[21:15] <yofel> not unity2d, I meant the gnome 3 panel
[21:15] <BUGabundo> LOL
[21:15] <BUGabundo> :D
[21:15] <charlie-tca> :)
[21:15] <BUGabundo> I don't like unity, really
[21:16] <yofel> kubuntu?
[21:16] <BUGabundo> I need my app applet
[21:16] <charlie-tca> kubuntu?
[21:16] <BUGabundo> yofel: :D
[21:16] <yofel> charlie-tca: let's start a match who gets BUGabundo as user :P
[21:16] <BUGabundo> been there, done that for a cicle
[21:16] <charlie-tca> heh
[21:16] <BUGabundo> xubuntu to light and cof ugly cof
[21:16] <charlie-tca> Kubuntu is really nice, if you can figure out to make it do anything
[21:17] <BUGabundo> Lubuntu is nice, but the UI is very outdated compared to Gnome
[21:17] <charlie-tca> ugly?
[21:17] <yofel> lubuntu is too simple for me, my fallback if KDE's broken is xubuntu currently
[21:17] <BUGabundo> charlie-tca: last time I picked it up we were in the mist of 9.04 :(
[21:17] <BUGabundo> :)
[21:17] <BUGabundo> yofel: simple but its working
[21:17] <BUGabundo> and I need a working WM
[21:18] <BUGabundo> if at least I could start a Guest Session *from* inside lubuntu I would see if I could login to Gnome
[21:18] <BUGabundo> but all priors attempts forced me to reisub it :\
[21:18] <BUGabundo> its *that* bad
[21:19] <BUGabundo> how does one log out of Unity ???
[21:19] <BUGabundo> can you believe I couldn't find the button?
[21:19] <BUGabundo> at least CAD worked
[21:19] <charlie-tca> don't you just click your name?
[21:19] <BUGabundo> didn't see it
[21:20]  * yofel needs a new oneiric VM to look at unity these days
[21:21] <BUGabundo> I need a new distro :)
[21:21] <yofel> :(
[21:21] <BUGabundo> if I could get ChromiumOS 14 to boot
[21:22] <BUGabundo> and install pidgin there, I would leave Ubuntu behind faster then a light bolt
[21:22] <charlie-tca> hm, I guess kubuntu, lubuntu, xubuntu are all waiting for you?
[21:22] <BUGabundo> I need some vacations from all this testing and mess
[21:22] <BUGabundo> I won't go to k or x
[21:22] <BUGabundo> trying L now
[21:22] <BUGabundo> but its not of my taste
[21:22] <BUGabundo> I just want classic
[21:22] <BUGabundo> at least until gnome3 supports gnome-do properly and have a better notification bar
[21:23] <charlie-tca> yup, sounds like it is time for a break, it has been a long run already
[21:24] <BUGabundo> "Graceful exit if physical disk capacity is reached. ETA : Will be implemented shortly" LOL
[21:24] <BUGabundo> been a full time K/Ubuntu user since 2006
[21:25] <charlie-tca> heh
[21:25] <charlie-tca> yeah, you been testing for a long time, now
[21:25] <BUGabundo> sure, I could just run _stable_
[21:25] <yofel> that doesn't sound like you :P
[21:25] <BUGabundo> but my other laptop with 10.10 and 11.04 seem as imperfect as this
[21:25] <BUGabundo> and don't have the cutting edge goodness
[21:26] <BUGabundo> you know what I miss most now?
[21:26] <charlie-tca> Maybe this hardware is not so good?
[21:26] <BUGabundo> I bet NONE of you will guess
[21:26] <charlie-tca> stability?
[21:26] <BUGabundo> nope
[21:26] <BUGabundo> not even close
[21:26] <BUGabundo> hint: gnome feature related
[21:27] <charlie-tca> I give up
[21:29] <BUGabundo> eheh
[21:29] <BUGabundo> alt-tab grab and drop
[21:29] <yofel> what did that do again?
[21:29] <BUGabundo> you drag something and press alt+tab to change windows
[21:30] <yofel> aaah
[21:30] <BUGabundo> FINALLY it was implemented in Gnome this cycle
[21:30] <BUGabundo> like....   Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server."
[21:37] <BUGabundo> LOL
[21:37] <bjsnider> what does xorg.conf say?
[21:37] <BUGabundo> looking at it as we speak
[21:37] <BUGabundo> $ cat /etc/X11/xorg.conf | pastebinit
[21:37] <BUGabundo> http://paste.ubuntu.com/650256/
[21:38] <BUGabundo> no nvidia ther
[21:38] <BUGabundo> meh... total system borked
[21:38] <bjsnider> just uninstall nvidia-current, remove that xorg.conf fragment and reboot
[21:38] <bjsnider> but you really seem to be using nouveau now
[21:38] <BUGabundo> weird
[21:38] <bjsnider> so maybe if you're having graphics issues it is to blame and not the blob
[21:38] <BUGabundo> since I never went back to it , after installing nvidia
[21:39] <yofel> maybe jockey screwed up creating xorg.conf
[21:41] <bjsnider> if nvidia-current is installed you really should be uing nvidia's glx, which means it would be paired with nouveau's ddx driver
[21:41] <bjsnider> that's a mess
[21:51] <BUGabundo> tell me about it bjsnider
[22:02] <bjsnider> BUGabundo, you really shouldn't be submitting any bug reports until you sort this out because everything could be caused by this misconfiguration
[22:03] <BUGabundo> ok
[22:03] <BUGabundo> I haven't done any this month
[22:03] <BUGabundo> :)
[22:08] <aroman> hi, what's the Mac version about? http://cdimage.ubuntu.com/releases/oneiric/alpha-2/
[22:11] <charlie-tca> specific to mac 64bit with the intel chip
[22:11] <aroman> how is that different than for PC?
[22:12] <charlie-tca> something with the EFI in mac
[22:12] <aroman> ah probably 64bit EFI
[22:12] <charlie-tca> it is optimized to take advantage of it
[22:12] <aroman> that's what I suspected
[23:59] <h00k> WOAH
[23:59] <h00k> I just found something
[23:59] <h00k> you know how alt-tab is...well, alt-tab


[16:55] <pleia2> bkerensa: can we get a status update on where you are with updating the getting involved docs?
[16:55] <pleia2> (last I knew you had sent it off to a couple reviewers, wondering if it's time to open it up to more reviewers?)
[20:38] <bkerensa> pleia2: surely... e-mail sent
[20:39] <pleia2> thank you :)


[12:26] <Jak08> hello
[12:26] <kwwii_> hi
[12:27] <Jak08> question, I am not able to use ubuntu right now, because well it doesn't work with my harddrive in my imac, it doesn't recognize the free space, but in what ways can I contribute?
[12:30] <Jak08> I am hoping that the new version of ubuntu will have complete support for the new intel macs, I can use it on another computer, but it only has dialup, which I am not fond of
[12:31] <kwwii_> Jak08: well, in a virtual desktop, it certainlyl works
[12:31] <kwwii_> not sure how well on the actual machine
[12:32] <Jak08> ok, but is there anyway I can contribute then? and is there a by chance a better sollution to a virtual desktop besides vmware?
[12:33] <kwwii_> well, we need work everywhere
[12:33] <kwwii_> pick what you can do best and do it
[12:34] <kwwii_> well, on macbooks there is a program (paralells, or such)
[12:34] <Jak08> can I have an example of such work? I'm sorry but I am rather new to OS graphics and am not sure what there is all to do
[12:35] <Jak08> yeah, I should look into paralells
[12:37] <Jak08> hmm not bad only 80 bucks
[12:39] <kwwii_> well, it is all in the source code
[12:39] <kwwii_> installing it is kinda important
[12:39] <kwwii_> you can check the wiki
[12:40] <Jak08> but can I have some example of work that can be done without the actual OS? for the meantime
[12:40] <kwwii_> wiki.ubuntu.com/Artwork
[12:40] <kwwii_> we are currently in the process of making the artwork for 6.10
[12:40] <kwwii_> the wiki might be the best place for you
[12:41] <Jak08> k
[12:41] <kwwii_> at the bottom of each page is a list of sub-pages
[12:41] <kwwii_> that is important
[12:41] <Jak08> do you know, about how much experiance wise do you lose by using a virtual desktop?
[12:41] <kwwii_> none
[12:41] <kwwii_> little
[12:41] <kwwii_> depends on the computer
[12:42] <kwwii_> on a macbook, little
[12:43] <Jak08> also besides photoshop what are some other usful tools that you can name for me to get?
[12:43] <kwwii_> well, a vector program is very important...
[12:44] <kwwii_> on linux I would suggest inkscape
[12:44] <Jak08> ok, what exactly is a vector program?
[12:44] <kwwii_> it runs on win and mac too I think
[12:44] <kwwii_> it makes vector pics, which can be scaled
[12:44] <kwwii_> the important thing to know is SVG
[12:44] <kwwii_> Scalable Vector Graphiccs
[12:44] <kwwii_> check wikipedia or such if you don't know it
[12:45] <Jak08> ok
[12:45] <Jak08> and besides inkscape what other usful tools should i get?
[12:45] <kwwii_> in addition to the pixmap programs like photoshop or GIMP those apps will be the most important
[12:45] <kwwii_> I use imagemagick a lot
[12:46] <kwwii_> a whole lot
[12:46] <Jak08> what is imagemagick per say?
[12:46] <kwwii_> it is best used in the bash shell (so the terminal)
[12:46] <kwwii_> it is a program for graphics
[12:46] <kwwii_> but it is best used in scripting
[12:47] <kwwii_> anyway, as a normal user...inkscape on linux, Adobe Illustrator on a prop. system like win or mac
[12:47] <Jak08> so imagemagick is like an alternative to photoshop and gimp?
[12:47] <Jak08> ok, I have illustrator for mac
[12:48] <kwwii_> hehe, no..it is just as powerfull, but in a different way...you can do things with scripts on pics with it very effeciently
[12:48] <kwwii_> illustrator is good
[12:48] <kwwii_> save things as svg
[12:48] <kwwii_> do not use too many filters
[12:48] <kwwii_> like negative multiply, etc.
[12:49] <Jak08> so is it completely fesable to do the graphics in os x and then port them to linux?
[12:49] <Jak08> ok
[12:51] <kwwii_> yes, definitely
[12:51] <kwwii_> I do quite a lot of work in osx
[12:51] <kwwii_> I do have to earn a living :-)
[12:51] <Jak08> haha, yeah
[12:53] <kwwii_> although atm I do earn most of my money working for canonical doing graphics and it is 100% linux and inkscape
[12:54] <kwwii_> for a good artist, the tool is not the problem
[12:55] <kwwii_> funny to say, but good art can be done with any tool
[12:55] <kwwii_> it is more a matter of intent and will
[12:56] <Jak08> yeah
[12:57] <Jak08> ok, well i will definitly get the tools you suggested, and do a bit of research and try my damndest to get ubuntu installed, but for now I have to go, hopefully I will get to speak with you again soon, with better news on my end
[12:57] <kwwii_> cool :-) have fun!
[12:58] <kwwii_> hope to see you here again
[01:01] <Jak08> oh i'll be back, don't worry
[01:01] <Jak08> hey a bit off topic but have you been able to use vista?
[01:03] <kwwii_> I only have ppc at home, so I haven't checked it out at all, actually
[01:04] <kwwii_> funny, but as a mac user, who does linux vista is some screenshot festival that I do not even get into
[01:04] <Jak08> ahh, it is a lot better than xp but in a lot of ways it falls short
[01:04] <Jak08> haha
[01:05] <kwwii_> I think that linux can surpass all that
[01:05] <Jak08> oh definitly especially with the rapid growth and developement it has seen recently
[01:06] <kwwii_> it comes down to leadership
[01:06] <kwwii_> in some aspects
[01:07] <kwwii_> and kubuntu and ubuntu have it...a goal
[01:07] <Jak08> yes
[01:07] <Jak08> I have never used kubuntu how does it compare with normal ubuntu?
[01:08] <kwwii_> I think it is even better oriented for the "normal Windows" user
[01:08] <kwwii_> it is powerfull, yet simple to use
[01:09] <Jak08> yeah, well anything else you say to me i'll just have to read in the logs couse i really need to go now
[01:09] <kwwii_> hehe
[01:09] <kwwii_> me too
[01:09] <kwwii_> see you
[11:52] <giga> any1 here?
[11:58] <kwwii_> hi
[11:58] <kwwii_> just me it seems
[12:01] <giga> is this channel ever active? Does it serve a purpose?
[12:01] <kwwii_> lol
[12:01] <kwwii_> of course it does
[12:01] <kwwii_> and yes, it is often actice
[12:01] <kwwii_> active
[12:02] <kwwii_> at certain times
[12:02] <kwwii_> it is more a channel for direct contact
[12:05] <giga> What do you do though?