[03:52] -queuebot:#ubuntu-release- New: accepted libwebp [amd64] (artful-proposed) [0.6.0-3]
[03:52] -queuebot:#ubuntu-release- New: accepted libwebp [armhf] (artful-proposed) [0.6.0-3]
[03:52] -queuebot:#ubuntu-release- New: accepted libwebp [ppc64el] (artful-proposed) [0.6.0-3]
[03:52] -queuebot:#ubuntu-release- New: accepted python-transitions [amd64] (artful-proposed) [0.5.3-1]
[03:52] -queuebot:#ubuntu-release- New: accepted libwebp [arm64] (artful-proposed) [0.6.0-3]
[03:52] -queuebot:#ubuntu-release- New: accepted libwebp [s390x] (artful-proposed) [0.6.0-3]
[03:52] -queuebot:#ubuntu-release- New: accepted libwebp [i386] (artful-proposed) [0.6.0-3]
[05:11] -queuebot:#ubuntu-release- New binary: golang-github-kurin-blazer [amd64] (artful-proposed/none) [0.0~git20170711.0.612082e-1] (no packageset)
[05:12] -queuebot:#ubuntu-release- New binary: python-agate-dbf [amd64] (artful-proposed/none) [0.2.0-2] (no packageset)
[05:12] -queuebot:#ubuntu-release- New binary: python-agate-sql [amd64] (artful-proposed/none) [0.5.2-2] (no packageset)
[05:12] -queuebot:#ubuntu-release- New binary: python-agate-excel [amd64] (artful-proposed/none) [0.2.1-3] (no packageset)
[05:58] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Artful Alpha 2] has been marked as ready
[05:58] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop i386 [Artful Alpha 2] has been marked as ready
[06:46] -queuebot:#ubuntu-release- New: accepted golang-github-kurin-blazer [amd64] (artful-proposed) [0.0~git20170711.0.612082e-1]
[06:46] -queuebot:#ubuntu-release- New: accepted python-agate-excel [amd64] (artful-proposed) [0.2.1-3]
[06:46] -queuebot:#ubuntu-release- New: accepted python-agate-dbf [amd64] (artful-proposed) [0.2.0-2]
[06:46] -queuebot:#ubuntu-release- New: accepted python-agate-sql [amd64] (artful-proposed) [0.5.2-2]
[06:58] <ginggs> would someone please update 'force-badtest winff/1.5.5-2/armhf' ?
[08:16] <sil2100> apw: hey! Would you have some free cycles to do some gce-compute-image-packages SRU reviews today? ;) Those are the standard ugly straight-backports from artful
[08:29] <apw> sil2100, lovely
[08:48] <apw> ginggs, done
[08:50] <ginggs> apw: thanks!
[09:11] <apw> sil2100, there is a gce-compute-image-packages | 20170622-0ubuntu1~14.04.1 sitting in trusty-proposed, what do you want doing with that
[09:12] <apw> sil2100, and is that fix included in the updates ?
[09:13] <sil2100> apw: yeah, I took the -proposed version and rebased on top of it - both changes are now in the upstream tarball actually
[09:17] <apw> sil2100, for next time, the trusty one has delta, it would be nice to enumerate the retained delta in the changelog
[09:17] <apw> python -> python3 etc
[09:17] <apw> or the opposite
[09:25] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (zesty-proposed) [20170718-0ubuntu1~17.04.0]
[09:27] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (xenial-proposed) [20170718-0ubuntu1~16.04.0]
[09:28] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (trusty-proposed) [20170718-0ubuntu1~14.04.0]
[09:28] <sil2100> apw: ok, noted! Thanks :)
[09:28] <apw> sil2100, ^ all yours ...
[09:28] <sil2100> I was always going ekhm, the easy way
[09:28] <sil2100> But the easy way isn't the best way of course
[10:05] <xnox> slangasek, next batch of u8rm https://bugs.launchpad.net/ubuntu/+bugs?field.tag=u8rm
[10:06] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Artful Alpha 2] has been marked as ready
[10:06] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Artful Alpha 2] has been marked as ready
[10:56] <jamespage> please could the nova upload waiting for review in the zesty queue be rejected - I have another fix I need to include with that
[10:58] -queuebot:#ubuntu-release- Unapproved: rejected nova [source] (zesty-proposed) [2:15.0.6-0ubuntu1]
[10:58] <apw> jamespage, ^
[10:59] <jamespage> apw: ta
[11:14] <doko> does retrying autopkg tests with -a include s390x these days?
[11:15] <xnox> doko, huh? i'm confused what you mean by "-a" using all of proposed, usually is not a good idea.
[11:15] <xnox> doko, also, there has not been a day when s390x did not have autopkgtests.
[11:16] <xnox> doko, i only click on hand crafted urls, and usually retry individual arches/builds with hand picked trigger combinations.
[11:16] <xnox> doko, note the huge backlog of autopkg tests, anything you retry will be done in only a few days time.
[11:17] <xnox> http://autopkgtest.ubuntu.com/running look at queue lengths
[11:17] <doko> xnox: at some time, autopkg tests were not triggered on s390x when not specifiying any arch
[11:17] <xnox> doko, using what?
[11:17] <doko> no arch option
[11:18] <xnox> no arch option... to what script?
[11:18] <xnox> britney triggers s390x adt tests all the time correctly, and retry urls are available and do work on s390x
[11:18] <apw> jez ... that is some backlog, 13k pending tests
[11:18]  * xnox clicks on recycle icons on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[11:18] <xnox> doko, how do you retry adt tests?
[11:19] <xnox> doko, or what/which api call?
[11:19] <xnox> maybe something needs fixing, if you tell me, what you do to cause such a question from you =)
[11:21] <doko> searching the wiki page ...
[11:21] <doko> xnox: pitti's run-something alias, sshing into some machine
[11:22] <xnox> doko, that is long gone; and has been replaced by a cgi script that people can trigger from urls on the status pages on autopkgtest.ubuntu.com or on the proposed_updates.sh
[11:22] <xnox> doko, ssh access should have been removed.
[11:22] <xnox> doko, also checkout lp:ubuntu-archive-tools retry-autopkgtest-regressions
[11:22] <doko> xnox: clicking on the recycle icon doesn't run against proposed
[11:23] <xnox> doko, it runs against a collection of packages from triggers. you can tweak the URL with &all-proposed=1 if you need all proposed.
[11:23] <xnox> and the triggered by, are pulled from -proposed.
[11:24] <xnox> doko, so it's best to add &trigger=foo/version&trigger=bar/version -> if you know that something needs to test with both foo and bar from proposed.
[11:24] <xnox> alternatively add &all-proposed=1
[11:24] <xnox> to the url.
[11:24] <doko> so I have to do that for all failing perl tests? with explicit triggers?
[11:25] <xnox> doko, look at the retry-autopkgtest-regressions script in the ubuntu-archive-tools, that automates retrying stuff.....
[11:25] <xnox> doko, you can run everything with all-proposed if you feel that is the right thing to do for perl*
[11:25] <xnox> doko, but i'd rather you _not_ retry _any_ perl yet. and let it do the first pass of 13k tests.
[11:25] <xnox> doko, and wait for the automatic cron to retry failing tests with proposed.
[11:26] <Laney> what automatic cron?
[11:26] <doko> when will that happen?
[11:26] <xnox> doko, you do know there is bot running that retries things with all-proposed apportunistically?
[11:26] <Laney> ...
[11:26] <Laney> who is running this bot?
[11:26]  * apw suspects the cron job is actually Laney
[11:26] <doko> it's fun to see who knows about that job ...
[11:26] <xnox> Laney, maybe i am imagining things, but somebody or soemthing does run retry-autopkgtest-regressions with all-proposed all the time. As e.g. systemd tests keep being retried over, and over, and over again.
[11:27] <Laney> Not me
[11:27] <Laney> I think some people learned about it and now abuse it
[11:27] <Laney> "this test fails, let's just try it with all-proposed"
[11:27] <cjwatson> Might be worth a bit of access.log analysis
[11:27] <apw> we should update that script to exit 1 at the top and see if it stops
[11:28] <xnox> logs should have the requester field recorded with the launchpad id.
[11:28] <Laney> I can see a lot of all-proposed in the queue at the minute with no requester
[11:28] <Laney> That means they got inserted into the queue without going through request.cgi
[11:28] <apw> there arn't many people who can do that are there ?
[11:29] <Laney> It's that script doko was just talking about
[11:29] <xnox> http://autopkgtest.ubuntu.com/running ctrl+f for "requester" there are a couple, but those look legit.
[11:29] <Laney> run-autopkgtest on snakefruit
[11:29] <xnox> wow....
[11:29] <apw> Laney, right, so lets change that script to add a requester of $SUDO something
[11:29] <xnox> Laney, given that we have cgi script that records launchpad id requestor, run-autopkgtest from snakefruit should be removed.
[11:30] <xnox> imho.
[11:30] <Laney> It's actually what britney uses to queue the tests
[11:30] <xnox> hm
[11:30] <xnox> well, the snakefruit club of people should sort it out then.
[11:30] <Laney> I think...
[11:30]  * Laney checks
[11:30] <apw> the equivalent of ${SUDO_USER:-$USER}
[11:31] <xnox> ideally - humans should use the cgi script, rather than ssh into snakefruit.
[11:31] <Laney> no, I lie
[11:31] <Laney> right
[11:31] <apw> xnox, that isn't very sensible for a bulk put back
[11:32] <xnox> apw, ./retry-all-proposed | xargs parallel xdg-open -- ? very bulk friendly
[11:32] <xnox> or whatever that script is that generates the retry urls, retry-autopkgtest-regressions
[11:33] <xnox> apw, i can see snakefruit used to rerun all of the release, to get the baseline results on open and some such.
[11:33] <apw> xnox, not that friendly when it opens 2000 tabs in your firefox
[11:33] <xnox> but that too whould record who requested all of that.
[11:33] <Laney> I don't really mind archive admins being able to do it
[11:33] <apw> xnox, right which is what i am suggesting
[11:33] <Laney> just....
[11:33] <Laney> ...don't abuse it
[11:33] <Laney> is there a good reason for these all-proposed requests or should I kill them off?
[11:34]  * Laney is in favour of logging the user though and hopes apw investigates doing that :-)
[11:34] <doko> well, having the perl tests not running against all-proposed will fail with uninstallabilities ...
[11:34] <xnox> Laney, i am guessing all of perl is fail, or e.g. the triggers should include perl from proposed.
[11:34] <Laney> they will do, no?
[11:34] <apw> Laney, carding self
[11:34] <Laney> dh-make-perl {"triggers": ["perl/5.26.0-4"], "all-proposed": true}
[11:35] <xnox> but e.g. not:
[11:35] <xnox> libanyevent-dbi-perl {"triggers": ["libanyevent-perl/7.130-2build1"]}
[11:35] <apw> Laney, that looks fun to cull
[11:35] <xnox> it should be and perl from proposed too..... although i hope that depends are right and things work.
[11:36] <xnox> doko, do you have failed logs with uninstallability in them?
[11:36] <doko> anyway, the uninstallability issues for perl are all resolved, so I'd appreciate a simple way of giving back all failed tests triggered by perl
[11:36] <xnox> such that we can look what triggers were used.
[11:36] <xnox> doko, but is all of perl installable in proposed?
[11:37] <doko> yes, except for one package on amd64
[11:37] <xnox> ack.
[11:37] <doko> http://people.canonical.com/~ubuntu-archive/transitions/html/perl5.26.html
[11:38] <Laney> retry-autopkgtest-regressions is the way to generate commands
[11:38] <Laney> | grep perl or similar
[11:39] <doko> xnox: example<EMAIL_ADDRESS>[12:33] -queuebot:#ubuntu-release- Unapproved: nova (zesty-proposed/main) [2:15.0.5-0ubuntu1 => 2:15.0.6-0ubuntu1] (openstack, ubuntu-server)
[13:04] <LocutusOfBorg> the failed package is now good (TM)
[13:04] <LocutusOfBorg> needs a publisher run
[13:17] -queuebot:#ubuntu-release- Unapproved: accepted intel-microcode [source] (xenial-proposed) [3.20170707.1~ubuntu16.04.0]
[13:17] -queuebot:#ubuntu-release- Unapproved: accepted intel-microcode [source] (zesty-proposed) [3.20170707.1~ubuntu17.04.0]
[13:43] <slashd> bdmurray, sil2100, morning do you have a moment to release rsyslog for LP: #1429427 in -updates ? It reaches the minimum aging of 7 days today, and it's all green. Thanks in advance.
[13:44] <sil2100> slashd: hey!
[13:44] <sil2100> slashd: let me take a look in a moment
[13:46] <slashd> sil2100, tks
[14:00] -queuebot:#ubuntu-release- Unapproved: libapache2-mod-auth-pgsql (trusty-proposed/main) [2.0.3-6 => 2.0.3-6ubuntu0.1] (no packageset)
[14:00] -queuebot:#ubuntu-release- Unapproved: libapache2-mod-auth-pgsql (zesty-proposed/main) [2.0.3-6.1 => 2.0.3-6.1ubuntu<IP_ADDRESS>] (ubuntu-server)
[14:00] -queuebot:#ubuntu-release- Unapproved: libapache2-mod-auth-pgsql (xenial-proposed/main) [2.0.3-6.1 => 2.0.3-6.1ubuntu<IP_ADDRESS>] (ubuntu-server)
[14:17] <sil2100> Ok, finally can go to my SRU duties
[14:17] <sil2100> slashd: done!
[14:19] <slashd> sil2100, thanks ;)
[16:02] -queuebot:#ubuntu-release- Unapproved: gtk+2.0 (zesty-proposed/main) [2.24.31-1ubuntu1 => 2.24.31-1ubuntu1.1] (ubuntu-desktop)
[16:04] -queuebot:#ubuntu-release- Unapproved: gtk+2.0 (xenial-proposed/main) [2.24.30-1ubuntu<IP_ADDRESS> => 2.24.30-1ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[16:12] <slangasek> xnox: and it looks like my all-proposed retests for perl have disappeared from the queue, hmm
[16:14] <ginggs> ah, slangasek was the bot!
[16:14] <xnox> slangasek, yes, because we identified that as the abuse of the queue!
[16:14] <xnox> slangasek, you should add requester "slangasek" when hogging the queue like that.
[16:14] <xnox> apw, Laney ^^^^^
[16:14] <slangasek> xnox: it was hardly hogging the queue, it was a couple of dozen requests
[16:15] <xnox> ah, we had duplicates of everything i think.
[16:15] <slangasek> if there were duplicates, then why are there zero in now?
[16:15] <xnox> not sure.
[16:15] <slangasek> I only requested one retest per package
[16:15] <slangasek> and there was no requester because it used the admin interface
[16:15] <slangasek> (snakefruit)
[16:16] <slangasek> which should be a clue who the bot is, since the REST API doesn't let you do that :)
[16:16] <xnox> i think at this point we need to wait for the queue to drain, see the follow out, and retry things via api.
[16:16] <slangasek> these are already-failed tests which I know need to be retried
[16:16] <slangasek> and they're blockers for perl, which is at the heart of the mess
[16:16] <xnox> slangasek, why not use the api generator? to request things? also can we add in the snakefruit script to demand requester and it should be "britney" or "slangasek" etc.?
[16:16] <xnox> horum sad.
[16:16] <slangasek> because the API generator is a PITA to script
[16:17] <slangasek> run-autopkgtest on the commandline is saner
[16:17] <slangasek> if there is a run-autopkgtest that will work with the API the way retry-autopkgtest-regressions does, I would be willing to transition
[16:18] <xnox> ./retry-autopkgtest-regressions | xargs parallel xdg-open -- ? very bulk friendly
[16:18] <slangasek> retry-autopkgtest-regressions does not let me specify which packages
[16:18] <slangasek> or specify trigger arguments
[16:18] <xnox> slangasek, also you can in google chrome, right click on the retry button to copy as cURL command (it includes the cookies) and even execute the lot via curl, without opening 2000 pages in firefox.
[16:19] <xnox> slangasek, it does have all-proposed option, and i guess we should add options for extra triggers and/or subset of packages, or feed a package list.
[16:19] <xnox> create a card for tooling work?
[16:20] <slangasek> xnox: the tooling work is not a priority for me; the only thing that gets you is attribution of the requests
[16:20] <slangasek> which you already have in the sense of "someone with snakefruit access"
[16:20] <xnox> slangasek, i think for us was priority to modify the snakefruit script, to e.g. include the SUDO user name into the requestor field.
[16:21] <xnox> that was disccuess, but i'm not part of the snakefruit gang.
[16:23] <slangasek> if there were a way to tag these requests to the 'huge' queue, /that/ would be a useful enhancement
[16:24] <xnox> hm, yes.
[16:24] <xnox> i forgot to eat today, going out to find food.
[16:35] <slangasek> xnox: and now I've read scrollback, and if there were duplicates it was probably because doko and I were both retrying tests (and both via snakefruit).  However, that still doesn't account for all of the test requests being removed instead of half of them ;)
[16:35] <slangasek> (would be really great if autopkgtest merged duplicate requests...)
[16:40] <slangasek> xnox, Laney, doko: as for someone regularly retrying systemd tests with --all-proposed, that is definitely *not* me; --all-proposed should almost never be used, it's appropriate for perl specifically because of it being a large transition but otherwise it is offensive.  AFAIK we don't keep a record of the requester anywhere useful after the test has completed?
[17:25] <tsimonq2> infinity, slangasek: Would one of you happen to be around?
[17:37] <slangasek> tsimonq2: hi
[17:38] <tsimonq2> slangasek: So I have figured out the root cause for bug 1633913 I believe.
[17:39] <tsimonq2> slangasek: Since the split of the Lubuntu seed into GTK and Qt parts, ship-live is empty, but we have ship-live-{gtk,qt} and ship-live-share.
[17:39] <tsimonq2> slangasek: I'll have a patch for lp:ubuntu-cdimage soon that should allow these to be picked up.
[17:40] <slangasek> tsimonq2: why would that belong to lp:ubuntu-cdimage, as opposed to changing the seed?
[17:42] <tsimonq2> slangasek: Maybe that's an option, but from what I can see, we can fix the problem by adding the appropriate seeds here: http://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/view/head:/lib/cdimage/germinate.py#L296
[17:43] <slangasek> tsimonq2: or you can fix the structure of your seeds so that ship-live depends on whatever it actually is that you want included
[17:43] <tsimonq2> i.e. if mode is ship-live, see if project is lubuntu or lubuntu-next, if it is, yield ship-live-share, if it's lubuntu yield ship-live-gtk, and if it's lubuntu-next yield ship-live-qt
[17:43] <slangasek> ah
[17:44] <slangasek> you shouldn't need to yield ship-live-share either, surely that's a dependency of ship-live-{qt,gtk} in the STRUCTURE
[17:44] <tsimonq2> Welp, let me check
[17:44] <tsimonq2> yep, you're right
[17:44] <slangasek> but ok, yes if you have two different images with disjoint requirements for ship, you're right to change ubuntu-cdimage
[17:45] <tsimonq2> Ok cool
[17:45] <slangasek> tsimonq2: assuming this is also a new change post-xenial, please be sure to include a version guard so as to not break point release builds
[17:46] <tsimonq2> slangasek: wfm
[17:55] <tsimonq2> slangasek: How does this look? https://code.launchpad.net/~tsimonq2/ubuntu-cdimage/different-ship-live-names-lubuntu/+merge/328182
[17:59] <slangasek> Laney, xnox: ftr I consider rerunning the perl-triggered autopkgtests a high priority because this is a major version bump and the likelihood of this introducing some regressions is high - in which case there is human effort required to finish this transition which can only begin once we have the signal in the results of what's actually regressed
[17:59] <slangasek> tsimonq2: looking
[18:02] -queuebot:#ubuntu-release- New source: stawk (artful-proposed/primary) [1.1-0ubuntu1]
[18:08] <tsimonq2> slangasek: ack
[18:10] <slangasek> tsimonq2: you want a respin, I assume?
[18:10] <slangasek> (branch landed)
[18:10] <tsimonq2> slangasek: I can take care of it :)
[18:11] <slangasek> tsimonq2: I'd rather do it here so if there are issues on the deploy I can notice and track
[18:11] <slangasek> (running now)
[18:11] <tsimonq2> slangasek: ack
[18:12] <tsimonq2> slangasek: In that case, please do.
[18:30] <LocutusOfBorg> and doko wants to do gcc in some days, so better find regressions quickly if possible :)
[18:32] <tsimonq2> Oh, thanks for reminding me LocutusOfBorg
[18:32] <tsimonq2> xnox: What's the status of the Ubuntu Touch removals in the archive? As soon as that's done, we can land a new Qt. :)
[18:33] <xnox> tsimonq2, i filed a bunch of removal bugs.
[18:33] <xnox> there are a lot more to do.
[18:33] <xnox> but i'm not an archive admin.
[18:34] <tsimonq2> xnox: Oh, thought you were. Do you have any sort of ETA?
[18:34] <xnox> http://bugs.launchpad.net/ubuntu/+bugs?field.tag=u8rm -> this is hardly a complete list, just the currently leaf packages to remove.
[18:34] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Artful Alpha 2] has been updated (20170727)
[18:34] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Artful Alpha 2] has been updated (20170727)
[18:34] <xnox> just the current round of pending removals.
[18:34] <tsimonq2> Oh, ok.
[18:37] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Artful Alpha 2] has been marked as ready
[18:37] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Artful Alpha 2] has been marked as ready
[18:51] <tsimonq2> slangasek: Uh oh, alternate images are failing...
[18:51] <tsimonq2> slangasek: http://people.canonical.com/~ubuntu-archive/cd-build-logs/lubuntu/artful/daily-20170727.log
[18:52] <tsimonq2> Missing debootstrap-required libpython3.5-minimal
[18:52] <tsimonq2> Missing debootstrap-required libpython3.5-stdlib
[18:52] <tsimonq2> Missing debootstrap-required python3.5
[18:52] <tsimonq2> Missing debootstrap-required python3.5-minimal
[18:52] <tsimonq2> slangasek: Erm, it's related to the Python transition, but... wat?
[18:54] <cjwatson> http://people.canonical.com/~ubuntu-archive/priority-mismatches.txt
[18:55]  * cjwatson fixes
[18:55] <tsimonq2> cjwatson: Thank you.
[19:05] -queuebot:#ubuntu-release- Builds: Lubuntu Next Desktop amd64 [Artful Alpha 2] has been updated (20170727)
[19:06] -queuebot:#ubuntu-release- Builds: Lubuntu Next Desktop i386 [Artful Alpha 2] has been updated (20170727)
[19:17] <slangasek> tsimonq2: ^^
[19:17] <tsimonq2> slangasek: ack
[19:18] <tsimonq2> slangasek: Right now the next step is to get priority mismatches sorted out (cjwatson was doing that). But for the time being, I'll see if I can get these new images tested.
[19:27] <slashd> bdmurray, Good day, do you have a moment to release "kexec-tools" in -updates for LP: #1705054 ? Thanks in advance.
[19:33] -queuebot:#ubuntu-release- New: rejected statistics [source] (artful-proposed) [1.0-0ubuntu1]
[19:33] -queuebot:#ubuntu-release- New: rejected stawk [source] (artful-proposed) [1.1-0ubuntu1]
[19:38] <tsimonq2> cjwatson: Out of curiosity, what's involved in sorting out priority matches?
[19:39] <cjwatson> change-override by an AA (with discretion)
[19:39] -queuebot:#ubuntu-release- New source: calc-stats (artful-proposed/primary) [1.2-0ubuntu1]
[19:40] <cjwatson> takes a publisher cycle, so should be done around now, though I haven't checked
[19:40] <tsimonq2> Ok.
[19:41] <tsimonq2> cjwatson: Am I safe to rebuild Lubuntu Alternate images now?
[20:13] <cjwatson> tsimonq2: looks like it
[20:14] <tsimonq2> cjwatson: Thanks!
[20:14] <cjwatson> np
[20:29] <bdmurray> slashd: done
[20:30] <slashd> bdmurray, thanks
[20:32] -queuebot:#ubuntu-release- Unapproved: accepted apt [source] (xenial-proposed) [1.2.24]
[20:34] -queuebot:#ubuntu-release- Unapproved: accepted apt [source] (zesty-proposed) [1.4.6~17.04.1]
[20:37] <flexiondotorg> tsimonq2 What is the current status?
[20:38] <tsimonq2> flexiondotorg: Testing Lubuntu images.,
[20:38] <flexiondotorg> ETA?
[20:38] <tsimonq2> 2-3 hours.
[20:39]  * flexiondotorg sighs
[20:39] <tsimonq2> flexiondotorg: Sorry. I know it's getting late for you :/
[20:39] <tsimonq2> flexiondotorg: If you want to help speed it along, help us test ;)
[20:40] <flexiondotorg> I'm packing.
[20:40] <tsimonq2> Ok.
[20:48] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate i386 [Artful Alpha 2] has been updated (20170727.1)
[21:05] <tsimonq2> :/ why would amd64 not build?
[21:06] <doko> ohh no, now I get emails for all 500 perl packages stuck in -proposed .... \o/
[21:07] <Ukikie> ...RIP inbox.
[21:13] <tsimonq2> cjwatson, slangasek: *scratches head* why wouldn't Lubuntu Alternate amd64 build? O__o
[21:14] <tsimonq2> From the log it looks like it didn't even detect that the amd64 image was supposed to build as well...
[21:29] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Artful Alpha 2] has been marked as ready
[21:30] <tsimonq2> 1 down, 5 to go
[21:34] <slangasek> tsimonq2: which log are you looking at?
[21:36] <tsimonq2> slangasek: http://people.canonical.com/~ubuntu-archive/cd-build-logs/lubuntu/artful/daily-20170727.1.log
[21:37] <tsimonq2> slangasek: Am I correct in saying that?
[21:37] <slangasek> tsimonq2: it does look like that log did not include amd64, yes. Was this a rebuild triggered via the iso tracker?
[21:38] <tsimonq2> slangasek: Yes it was, I rebuilt it for both amd64 and i386...
[21:39] <slangasek> tsimonq2: if so, and if you triggered them both at the same time, I would speculate that they were queued separately; but that wouldn't explain why a log has shown up for only one of the builds
[21:40] <slangasek> tsimonq2: try triggering amd64 again?
[21:41] <tsimonq2> slangasek: I did a little bit ago, want me to do it again?
[21:41] <slangasek> tsimonq2: so you tried to trigger them together, then you tried to trigger just amd64?
[21:42] <tsimonq2> slangasek: Correct.
[21:43] <slangasek> ok
[21:43] <slangasek> let me see what I can see
[21:50] <slangasek> tsimonq2: I could see your rebuild request but I couldn't act on it through the script, nor could I cancel it through the web ui; I've cancelled it now by hand and re-triggered, let's see what happens
[21:52] <tsimonq2> slangasek: Alright.
[21:53] <slangasek> tsimonq2: I don't see any obvious bugs, I'm not going to try to debug it further.  If the problem recurs I'll dig deeper
[21:54] <tsimonq2> slangasek: ack
[21:59] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate amd64 [Artful Alpha 2] has been updated (20170727.2)
[21:59] <tsimonq2> slangasek: ^ \o/
[22:26] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Artful Alpha 2] has been marked as ready
[22:26] -queuebot:#ubuntu-release- Builds: Lubuntu Next Desktop i386 [Artful Alpha 2] has been marked as ready
[22:26] -queuebot:#ubuntu-release- Builds: Lubuntu Next Desktop amd64 [Artful Alpha 2] has been marked as ready
[22:50] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate amd64 [Artful Alpha 2] has been marked as ready
[22:50] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate i386 [Artful Alpha 2] has been marked as ready
[22:50] -queuebot:#ubuntu-release- Unapproved: accepted gnome-applets [source] (zesty-proposed) [3.22.0-2ubuntu0.1]
[22:51] <tsimonq2> slangasek: Ship It, please.
[22:56] -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (zesty-proposed) [2.5.0-3ubuntu5.4]
[22:58] -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (xenial-proposed) [1.3.1-1ubuntu10.12]
[22:59] <slangasek> tsimonq2: looking
[23:00] <slangasek> tsimonq2: lp:ubuntu-archive-tools / publish-image-set doesn't know what to do with Lubuntu Next yet
[23:00] <slangasek> so there'll be a short delay in publishing while I address that
[23:01] <tsimonq2> slangasek: I think when stgraber did Alpha 1, he might have fixed that but not pushed it.
[23:01] <tsimonq2> I could be wrong.
[23:01] <stgraber> oh
[23:01] <stgraber> quite possible
[23:01] <stgraber> let me check
[23:01] <slangasek> tsk :)
[23:02] <slangasek> ARCHES='amd64 i386' for-project lubuntu-next publish-release daily-live 20170727 desktop no alpha-2
[23:02] <slangasek> that looks right
[23:02] <slangasek> stgraber: are you pushing?
[23:02] <stgraber> yeah
[23:03] <stgraber> trying to remember how to bzr :)
[23:03] <slangasek> tsimonq2: lubuntu-next images are oversized?
[23:03] <slangasek> (do you need to pick a different size?)
[23:04] <stgraber> slangasek: pushed
[23:04] <tsimonq2> slangasek: Didn't get an answer when I pinged about it :P
[23:04] <tsimonq2> slangasek: But yes
[23:04] <slangasek> stgraber: I don't see your push?
[23:05] <tsimonq2> slangasek: 1.5 GB sounds sane to me until we (Lubuntu) can look at reducing it
[23:05] <flexiondotorg> I just pulled
[23:05] <slangasek> stgraber: n/m, it applied without conflicts so bzr didn't bother telling me ;)
[23:05] <tsimonq2> flexiondotorg: hello!
[23:05] <flexiondotorg> o/
[23:08] <slangasek> tsimonq2: "sounds sane" == "you'd like me to commit that"?
[23:08] <tsimonq2> slangasek: Yes.
[23:08] <tsimonq2> :P
[23:09] <slangasek> k, I'm down with having zero nag emails and zero manual steps in the publishing
[23:10] <tsimonq2> slangasek: I'll be around for the next 30 mins (work needs me to come in) but since I'm signed up with bashfulrobot, he's agreed to just publish the announcement, if that's OK with you.
[23:10] <tsimonq2> Yes, zero nag emails :P
[23:10] <slangasek> tsimonq2: I'll be hitting the final 'publish' button here in about 5m
[23:10] <tsimonq2> slangasek: Alright, I just didn't know what your timing was. Works for me.
[23:11] <tsimonq2> slangasek: (i.e. please ping both me and bashfulrobot when it's ready for announcement publishing, if you could)
[23:12] -queuebot:#ubuntu-release- New binary: node-tty-browserify [amd64] (artful-proposed/none) [0.0.0-2] (no packageset)
[23:18] <slangasek> tsimonq2: http://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/revision/1672
[23:18] <tsimonq2> slangasek: ack, thanks
[23:20] <slangasek> hmph, 12 CPU threads and we block on a single-threaded checksumming operation
[23:21] -queuebot:#ubuntu-release- Unapproved: accepted aodh [source] (zesty-proposed) [4.0.1-0ubuntu<IP_ADDRESS>]
[23:23] -queuebot:#ubuntu-release- Unapproved: accepted ceilometer [source] (zesty-proposed) [1:8.0.2-0ubuntu<IP_ADDRESS>]
[23:23] <cjwatson> valid point on lack of multiprocessing, but it's supposed to copy the checksums from the dailies it's publishing, and if it doesn't do that then it's a bug worth looking into
[23:25] <slangasek> cjwatson: I noticed the delay on the src images
[23:26] -queuebot:#ubuntu-release- Unapproved: accepted cinder [source] (zesty-proposed) [2:10.0.4-0ubuntu1]
[23:27] -queuebot:#ubuntu-release- Unapproved: accepted heat [source] (zesty-proposed) [1:8.0.2-0ubuntu1]
[23:28] <slangasek> ...which also don't appear to have been regenerated since alpha-1
[23:30] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (zesty-proposed) [3:11.0.3-0ubuntu1]
[23:30] <slangasek> tsimonq2 bashfulrobot: alpha-2 mirroring in progress
[23:30] <tsimonq2> slangasek: ack
[23:31] <slangasek> infinity, cjwatson, stgraber: how are the src images meant to be built, since they don't appear to be happening automatically by cron and aren't listed on https://wiki.ubuntu.com/MilestoneProcess ?
[23:31] <stgraber> slangasek: I usually call cron.source manually (takes quite a long time), make sure to set the right env so it only generates for the participating flavors (bash history should help)
[23:31] <cjwatson> I fear it is manual but I have long forgotten the details
[23:32] <slangasek> artful milestone marked as released; crontab reset
[23:32] <stgraber> slangasek: you will also have to move them around a bit so that the publish process works, otherwise it's going to be looking for them at the wrong place
[23:32]  * stgraber -> out for a bit
[23:32] <cjwatson> it's probably the buggiest bit of cdimage
[23:34] <slangasek> k, regenerating, and added to https://wiki.ubuntu.com/MilestoneProcess
[23:34]  * tsimonq2 -> AFK for the next two hours, bashfulrobot should be around any minute (spoke with him on Telegram) to publish the announcement. o/
[23:35] <tsimonq2> s/two/three/ - that's more realistic
[23:35] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (zesty-proposed) [2:10.0.2-0ubuntu1.1]
[23:37] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (xenial-proposed) [2:8.4.0-0ubuntu4]
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted neutron-fwaas [source] (zesty-proposed) [1:10.0.1-0ubuntu1]
[23:41] -queuebot:#ubuntu-release- Unapproved: accepted neutron-lbaas [source] (zesty-proposed) [2:10.0.1-0ubuntu1]
[23:48] <infinity> stgraber: The "wrong place" thing is fixable with a symlink.  I do it every release. :/
[23:48] <slangasek> which symlink is this?
[23:49] <infinity> Well, I say that, but now I can't find weird symlinks.  It is possible I fixed the source instead?
[23:49] <infinity> That sounds less likely.
[23:50] -queuebot:#ubuntu-release- Unapproved: accepted google-cloud-sdk [source] (zesty-proposed) [163.0.0-0ubuntu1~17.04.0]
[23:50] <infinity> slangasek: Anyhow, not sure if I fixed something, or someone unfixed filesystem hacks, but if it spits out source in someplace other than where the current/pending/20170630 live, just shuffle it around.
[23:51] <slangasek> groovy
[23:51] -queuebot:#ubuntu-release- Unapproved: accepted google-cloud-sdk [source] (xenial-proposed) [163.0.0-0ubuntu1~16.04.0]
[23:52] -queuebot:#ubuntu-release- Unapproved: accepted google-cloud-sdk [source] (trusty-proposed) [163.0.0-0ubuntu1~14.04.0]


[22:49] <amarillion> Why are they in a debian/contrib subdirectory? I haven't seen that before
[22:49] <wallyweek> I thought it was a good idea to keep them separate from upstream
[22:49] <amarillion> Well everything in debian is already separate isn't it?
[22:50] <amarillion> Not that I think it should be different, I'm just asking.
[22:50] <mok0> amarillion: I've seen it a few times
[22:51] <mok0> amarillion: it's ok not to clutter debian/
[22:51] <wallyweek> it's just for tidiness IMHO... i know that everything but packaging stuff I have written is in debian/contrib/
[22:51] <amarillion> ok, I see
[22:52] <amarillion> I think your package is at the point of quality where I can't comment on it
[22:53] <wallyweek> amarillion: I should take this good, should I? ;)
[22:53] <amarillion> I won't pretend I'm an experienced reviewer
[22:53] <amarillion> so it's not saying much...
[22:54] <wallyweek> I don't think so... you probably know more than I do :$
[22:54] <amarillion> Ok, I'll look a bit more :)
[22:55] <wallyweek> nice!
[22:55] <amarillion> Feel free to look at mine too: http://revu.tauware.de/details.py?package=alex4
[23:02] <amarillion> wallyweek, after reviewing your package...
[23:02] <amarillion> I've got comments for my own package
[23:03] <amarillion> I should put my man page in section 6 too as it is a game as well
[23:03] <amarillion> hehe
[23:03] <wallyweek> amarillion: the only thing I see, manpage needs to make distinction from hyphens and minus signs (only 2 occurrences btw)
[23:03] <amarillion> wallyweek, yeah, persia told me that before
[23:04] <amarillion> but what does that mean exactly?
[23:05] <mok0> amarillion: (not a motu) ... get rid of boilerplate comments at top of rules
[23:05] <wallyweek> amarillion: hyphens separates words between lines and may cause some mess
[23:06] <wallyweek> you need mostly minus sign (e.g. for options), and when you need a minus sign you should escape it with a backslash
[23:06] <mok0> amarillion: in rules, make sensible comments instead of boilerplate, and get rid of commented dh_* lines
[23:07] <amarillion> ok
[23:09] <wallyweek> amarillion: just asking: alex4.ini shouldn't go in /etc/ ? It's config file, I presume
[23:10] <amarillion> wallyweek, yeah I was unsure about that one
[23:10] <amarillion> Should it then be in /etc/alex4.ini or /etc/alex4/alex4.ini?
[23:11] <mok0> amarillion: in copyright, you need to include the full preample
[23:11] <wallyweek> amarillion: /etc/alex4.ini IMHO, you need a subdir only when you have two or more config files
[23:12] <mok0> wallyweek: agree
[23:12] <amarillion> mok0, you mean the preamble of the GPL?
[23:12] <mok0> amarillion: yes
[23:12] <amarillion> I'll look at some other packages for examples
[23:13] <mok0> look at the templates in /usr/share/debhelper/dh_make
[23:14] <amarillion> Ok, thanks guys
[23:14] <amarillion> looks like I have some work to do
[23:14] <amarillion> but first: dlrrp
[23:15] <amarillion> good night!
[23:15] <mok0> amarillion: ... and when the MOTUs come back to work they will make you change everything again ;-)
[23:16] <wallyweek> :)
[23:17] <mok0> amarillions left hand was shifted 1 position: sleep -> dlrrp :-)
[23:17] <mok0> known as qwerty encryption
[23:21] <wallyweek> ...and I was looking for a new interner acronym... :)
[23:22] <jdong> it even sounds like how I say "sleep" when it's really time to do that.
[23:23] <wallyweek> jdong: and that's what I need indeed... ;)
[23:23] <wallyweek> g'night everyone!
[23:29] <persia> Frimost: Just in case you didn't notice already, the keyring sync is complete
[23:29]  * persia goes away again


[03:42] <smartboyhw> len-dt: What are you working on now?
[03:43] <len-dt> I have been doing some recording.
[03:44] <smartboyhw> I have been building an ISO
[03:44] <len-dt> Sounds fun.
[03:45] <smartboyhw> Yeah the Ubuntu GNOME remix
[03:46] <len-dt> I'm thinking to leave that one alone till at least first release... maybe first LTS to look at it.
[03:46] <smartboyhw> HAHAHA
[03:47] <len-dt> I only have so much time to spend playing with distro building and priorities are studio then xubuntu.
[03:47] <smartboyhw> len-dt: My priority is studio then ubuntu then xubuntu
[03:49] <len-dt> My first thought was to give holstein's line "ubuntustudio _is_ ubuntu" :) But I know what you mean.
[03:49] <smartboyhw> len-dt: Yes.:)
[03:50] <smartboyhw> Yes "ubuntustudio _is_  Ubuntu with multimedia creation apps:)
[03:50] <smartboyhw> And xfce
[03:51] <smartboyhw> And xubuntu base
[03:51] <len-dt> Vanilla is Ubuntu with unity on top
[03:51] <smartboyhw> len-dt: LOL
[03:52] <len-dt> The DE is actually a very small part of what Ubuntu is.
[03:52] <smartboyhw> Yes.
[03:52] <len-dt> But very visible.
[03:52] <smartboyhw> LOL
[04:03] <micahg> smartboyhw: the DE is part of the Ubuntu desktop product
[04:05] <len-dt> micahg, I have sent an email to Colin about our metas
[04:05] <micahg> len-dt: ok, I'll take a look at the diff when he uploads it so I can do stuff like this in thefuture
[04:05] <micahg> I just seem to be missing something
[04:07] <len-dt> It does seem odd that it doesn't just work. The graphics meta changed just fine.
[04:08] <smartboyhw> Am I wrong but then isn't there something known as Ubuntu Core which has no DE micahg?
[04:08] <micahg> smartboyhw: I didn't say anything about Ubuntu core, there are many difference projects under the umbrella of the Ubuntu project
[04:09] <micahg> err...products under the umbrella
[04:09] <len-dt> I don't think core is meant to be used on it's own though smartboyhw
[04:09] <len-dt> :)
[04:09] <smartboyhw> i don't know!!??!?
[04:10] <smartboyhw> Anyway what I know is that Ubuntu is the Ubuntu kernel with Unity that's all
[04:11] <len-dt> Without the repos with all the extra software, Ubuntu would not be where it is.
[04:11] <len-dt> It is all a part of it
[04:11] <micahg> no, that's the Ubuntu desktop product which a lot of people think of as Ubuntu
[04:14] <smartboyhw> Now I'm confused
[04:14] <micahg> Ubuntu is a project, this project has archives, lots of products are hosted in this archive
[04:14] <len-dt> smartboyhw, you might think of it like Lego. Someone could build a Lego truck. Is that truck Lego? or is it the parts the truck is made of?
[04:15] <smartboyhw> Lego??? I don't play lego, len-dt:(
[04:15]  * len-dt sometimes plays with Lego.
[04:15] <len-dt> But you do know what it is. ?
[04:16] <smartboyhw> Yes
[04:16] <smartboyhw> len-dt: How old are you to play Lego???
[04:16] <len-dt> I have a 6 year old. I get to play with his.
[04:16] <smartboyhw> Ah alright
[04:20] <len-dt> No worries, I was not trying to make you any younger than you are.
[04:21] <smartboyhw> LOL
[08:38] <ailo> Anyone experienced quantal pulseaudio crashing now and then?
[08:39] <ailo> I need to test on other HW, cause it might HW related for me. PA crashes every now and then, and reinitializes volumes. My apps get stuck and need tp get
[08:39] <ailo> ..be restarted
[08:41] <ailo> Well, actually. Jack is fine all the time, only PA is having problems
[08:49] <ailo> smartboyhw: Ubuntu without the desktop is in the package ubuntu-minimal
[09:03] <falktx> hey
[09:04] <falktx> I'm wondering again - why is debian multimedia packages built with debug mode on?
[09:07] <ailo> falktx: I would ask Debian Multimedia Team, if the packages aren't built differently on Ubuntu
[09:07] <falktx> afaik they are not
[09:07] <falktx> I just saw some recent syncs
[09:08] <ailo> Interesting note. Wonder why they do that
[09:11] <falktx> is anyone here on their mailing list?
[09:14] <ailo> falktx: I am. I could ask them
[09:14] <ailo> falktx: I'm actually going to join that team later on. You ever thought about doing that?
[09:15] <falktx> I did once, but then I saw the limitations
[09:15] <ailo> falktx: limititations?
[09:15] <falktx> and all the hard work just for simple tasks
[09:16] <falktx> ailo: yes, if a piece of code doens't have a very clear license, they refuse to package it
[09:16] <falktx> I remember the audacious case
[09:16] <falktx> a plugin code was removed from the source tarball because it didn't have any header-comments
[09:17] <falktx> I though that was just crazy
[09:17] <ailo> To me that just sounds like making sure packages adhere to the Debian policy
[09:17] <falktx> yeah, that is the thing - I don't agree with that policy
[09:18] <falktx> linuxsampler exception rule still kills me
[09:18] <falktx> Ubuntu used to have java in the repos, it displayed the license when installing
[09:18] <falktx> why can't that be done too?
[09:19] <falktx> there are a lot of things that I don't agree with Debian, I guess that's the main reason why I haven't joined the team
[09:19] <ailo> You can either join Debian, and help improve it, or start your own Debian
[09:20] <ailo> You can't change something, if you are looking in from the outside
[09:20] <falktx> well, I started my separate project, as you know
[09:21] <ailo> falktx: Are you sure linux-sampler could not be packaged for Debian? There is a non-free repo after all
[09:21] <ailo> falktx: You mean, your PPA's
[09:21] <ailo> Yea, they are filling a purpose in deed
[09:22] <falktx> ailo: considering there is worst licenses then LS, I'm sure it could
[09:22] <falktx> *than
[09:22] <ailo> I've seen a bug report about packaging it, and no one was claiming it couldn't be done
[09:23] <ailo> On the report, that is
[09:23] <falktx> I think debian is just losing people's attention, not sure...
[09:24] <falktx> I know alession works in d-multimedia, but is there anyone else?
[09:24] <ailo> falktx: Anyone else from where? there are people there. And I don't think anyone is loosing attention to the foundation for anything Debian based
[09:25] <ailo> falktx: there's no reason why you can't do things on many levels you know
[09:25] <falktx> well, it's just my impression
[09:25] <ailo> There are reasons for the restrictions that Debian has. If they would change them, many would leave Debian
[09:26] <ailo> And you can build upon it, just like Ubuntu does, and Mint does off on Ubuntu
[09:26] <ailo> Like you do with your PPA's. Similar to Mint
[09:26] <ailo> So, I don't really see the problem
[09:27] <falktx> I see your point
[09:27] <ailo> You can't have a library of software representing free and open source software, if it's not being free and open source.
[09:27] <ailo> And surely, there are lot's of grey zones
[09:27] <ailo> Debian vanilla is 100% free. Even the kernel.
[09:28] <ailo> But they have a non-free repo
[09:28] <falktx> well, I think there's some firmware things that are not truly free
[09:28] <falktx> but that's being picky... :)
[09:28] <falktx> still, back to my main though - why do they have to build things in debug mode
[09:28] <ailo> falktx: Even in Debian vanilla? They took out all the firmware that wasn't and put them in different packages
[09:29] <falktx> ailo: could you ask on their ML ?
[09:29] <ailo> falktx: I'll do that
[09:29] <falktx> ailo: I mean the kernel, I read that at phoronix once. whatever that is a trust-worthy source... heh...
[09:30] <ailo> falktx: I don't know the specifics, but to my knowledge, all the non-free parts of the kernel were repackaged, and put into the non-free repo, so you can add them after installation
[09:30] <ailo> wifi drivers, etc
[09:30] <ailo> It's a pain, cause the installation freezes if you have a non-free wifi
[09:31] <falktx> ok
[09:31] <ailo> Ubuntu being less restrictive, just keeps it all in the kernel as is
[09:31] <falktx> I see, I'm just too used to Ubuntu I guess
[09:31] <falktx> it makes things too easy :)
[09:32] <ailo> Debian is in some way not a distro. More of a library
[09:34] <ailo> falktx: Oh, let me ask you where you saw about the debug being built in. I want to know what I'm asking for
[09:36] <ailo> bbs
[09:37] <ailo> Actually, let me check some packages sources :)
[09:37] <falktx> ailo: it's all in the new lv2 libs
[09:37] <falktx> lv2-dev, serd, sord, sratom, lilv, suil
[09:37] <falktx> also qtractor, patchage
[09:38] <falktx> I noticed it in the recent packages
[09:39] <falktx> also muse I think
[09:39] <falktx> better to give an example
[09:40] <falktx> here we go
[09:40] <falktx> ailo: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/qtractor.git;a=summary
[09:40] <falktx> ^that is the qtractor debian-git page
[09:41] <falktx> look at debian/rules file:
[09:41] <falktx> http://anonscm.debian.org/gitweb/?p=pkg-multimedia/qtractor.git;a=blob;f=debian/rules;hb=HEAD
[09:41] <falktx> dh_auto_configure -- --enable-debug ...
[09:41] <falktx> that is just awful for qtractor
[09:42] <falktx> it gets into an unusable state (prints a lot of debug stuff even when processing, as it's being built for debug purposes)
[09:42] <falktx> splitting the debug symbols into a separate package won't do anything, as debug is already activated
[09:43] <falktx> and this is just 1 small example
[09:43] <falktx> if all qtractor's libs are built in debug (lv2 libs, libsamplerate, libsndfile, etc), then it gets even worse
[09:44] <falktx> ailo: do you think this information is enough for a post?
[09:44] <falktx> you can post the direct irc chat if you want
[10:00] <ailo> falktx: Thanks. More than enough. I'll start with that, and see what they say
[10:01] <smartboyhw> Oops what did I miss
[10:06] <ailo> smartboyhw: You can always check the irc logs
[10:06] <ailo> at http://irclogs.ubuntu.com/
[10:07] <smartboyhw> Bye no
[10:08] <smartboyhw> *now
[10:12] <ailo> falktx: I was just googling at first, just to see if there was already something discussed about this. So, this might answer half the question: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684035
[10:12] <falktx> wtf??
[10:12] <falktx> jack itself with debug
[10:12] <falktx> .... what???
[10:13] <falktx> ailo: do they not think about how sluggish apps are by default in debug?
[10:14] <falktx> ailo: anyway, please let me know when you post something. and thanks in advance
[10:15] <ailo> falktx: I guess it would be best if debug was always in a separate package, right?
[10:15] <falktx> I'll try to speak with Rui from qtractor when I see them (about this)
[10:15] <falktx> ailo: separate package - yes. using debug mode in all packages and split symbols - no
[10:16] <falktx> splitting debug symbols do nothing
[10:16] <falktx> the app was not optiized for runtime, it will be slow
[10:16] <falktx> *optimized
[10:17] <falktx> audio denormals will most likely happen with this scenario, increasing cpu even more
[10:17] <falktx> I see the point on using debug mode for testing releases, but not for final ones
[10:22] <ailo> yea. Would seem like the best procedure would still be keeping separate debug packages, no matter which release, so you only need to maintain one version of something
[10:22] <ailo> I've never done a package like that, so I don't know what extra work goes into it
[10:23] <falktx> I guess it comes down to what is most important - app optimization and less cpu usage, or better debug/crash info
[10:23] <falktx> considering that most users never report any kind of bugs, well...
[11:31] <ailo> falktx: Message sent. I'll let you know when and if i get an answer
[11:32] <falktx> ailo: ok, thanks!
[12:17] <smartboyhw> Oh yo I saw the mail ailo:)
[12:29] <holstein> wonder what that was about
[12:29] <smartboyhw> holstein: Look at the channel backlog:)
[12:29] <holstein> "im trying to boot into a new operating system without rebootin"
[12:29] <holstein> smartboyhw: oh, im aware of what was said.. i just dont understand.. i assume im missing something else
[12:30] <smartboyhw> OK
[13:15] <len-dt> ailo, does ubuntu-minimal come as a ISO? Is that the new pulse version? (PA-2.1)
[13:17] <len-dt> holstein, I'm not really sure either. Maybe he wants to boot into a virtual box of some sort.
[13:18] <smartboyhw> Hmm
[13:18] <smartboyhw> len-dt: But he's trying to install it on a SSD
[13:19] <len-dt> I don't think that makes that much difference as to where it is. Just the same as running wine, The directories that make the fake win part could be anywhere
[13:31] <len-dt> smartboyhw, is there a page that describes the various ISOs?
[13:32] <smartboyhw> len-dt: What do you mean?
[13:33] <len-dt> smartboyhw, I go to http://cdimage.ubuntu.com/ and there is a list of flavours. Is there a page that has a description for all these flavours? or do I have to find each one separately
[13:34] <len-dt> There are a lot of them that are not even ISOs
[13:34] <smartboyhw> len-dt: I don't know. Tell me what do ya want
[13:35] <len-dt> I want a ubuntu ISO that has no GUI
[13:35] <smartboyhw> len-dt: Try Ubuntu Core
[13:36] <len-dt> It is not an ISO
[13:36] <smartboyhw> Why do you need one without gui?
[13:36] <len-dt> I want to try something on a minimal machine
[13:36] <smartboyhw> Hmm
[13:37] <smartboyhw> IDK then.
[13:38] <len-dt> No problem. I was going to use server and not install any services :-) but I would really like something not server oriented.
[13:38] <smartboyhw> :)
[13:39] <falktx> len-dt: you want the net-boot I assume?
[13:40] <falktx> http://cdimage.ubuntu.com/netboot/quantal/ ?
[13:40] <len-dt> falktx, I'll look
[13:43] <len-dt> https://help.ubuntu.com/community/Installation/MinimalCD looks like what I want.
[13:43] <falktx> len-dt: yep, that's the same
[13:44] <falktx> minimal = netboot
[13:44] <len-dt> Ya, that was what I thought I got there from the netboot wiki.
[13:44] <len-dt> But the minimal page provides info the way I want to do things.
[13:46] <len-dt> falktx, I want to make an CLI audio machine and also try netjack on an older machine.
[14:52] <ailo> len-dt: If you do an expert install, you can choose to not install any of the metas (or tasks). What you get then is ubuntu-minimal.
[14:53] <ailo> That which is below all the derivatives
[14:54] <ailo> len-dt: You can do that with different installers. Alternate, net-install
[14:54] <len-dt> ailo, I have a mini.iso (40M) that has an alt installer
[14:54] <len-dt> ya from net-install
[14:58] <ailo> Or maybe just a normal install does that too, with those
[14:58] <ailo> I don't remember. I always do expert install
[14:59] <len-dt> No matter, I have something to play with. I'll start with that.
[15:00] <len-dt> ailo, what version of PA did you have problems with?
[15:01] <ailo> len-dt: hmm, actually not 2.1. 2.0-6
[15:01] <len-dt> Might be an idea to try 2.1
[15:02] <ailo> I'm on Debian Sid at the moment. It's not updating much right now, which I think has to do with Wheezy being released soon
[15:02] <ailo> I should do some tests on Quantal
[15:03] <len-dt> When next I boot quantal I will exercise PA as hard as I can.
[15:03] <ailo> len-dt: Just put something playing for a long period. Like Totem
[15:04] <ailo> It can take hours
[15:04] <len-dt> Ya. 2.1 is available from https://launchpad.net/~ubuntu-audio-dev/+archive
[15:04] <ailo> If it happens on Quantal, I will try to see what happens
[15:30] <holstein> len-dt: yeah... still, that would be "easy" to just point the virtualization software to the downloaded iso
[15:31] <smartboyhw> holstein: +1
[15:31] <holstein> i wouldnt think someone wanting to do that would need to ask how
[15:31]  * holstein shrugs
[15:31] <len-dt> holstein, that would be my guess too.
[15:31] <smartboyhw> How on earth can you install without reboot? That is a step after installation using the live dvd
[15:32] <len-dt> smartboyhw, on a virtual run the reboot is only in the virtual box not the surrounding OS
[15:32] <smartboyhw> len-dt: I know
[15:33] <len-dt> I think part of the problem is that the user was not explaining what they wanted to do very well.
[15:33] <smartboyhw> But then it IS a step, and I don't think Ubuntu Studio is really not suitable in a VM
[15:33] <len-dt> I tend to be the same... My brain thinks everyone already knows what I  am talking about.
[15:34] <holstein> len-dt: yeah, maybe a language barrier
[15:34] <smartboyhw> I think he just wants to install it without having a reboot after installation
[15:36] <len-dt> Some of that may be possible... no new kernel for example. But it leads to odd bugs. I have found that even when a SW update does not ask for reboot, it often helps.
[15:36] <smartboyhw> :)
[15:37] <ailo> You can build a new OS on a different partition, but I don't know about installing from ISO, without using the installer.
[15:38] <ailo> Maybe it's possible to switch OS's without rebooting somehow, but I've never heard of it
[15:39] <ailo> I'd assume you need to be running the same kernel, and somehow switch the filesystem on the fly
[15:40] <ailo> Restart pretty much everything
[15:40] <ailo> Which is basically rebooting
[15:40] <len-dt> Ya, but someone doing that should not be having to ask how...
[15:40] <smartboyhw> ailo: +1
[15:42] <ailo> len-dt: At least not on our channel. But, as you said, I'm not sure we understood the question


[08:32] <enchi> Hi, would I be able to be unbanned from #ubuntu-offtopic?
[10:01] <chu> Hey enchi. I'll unban you, but this is the last time. OK?
[10:03] <enchi> All right. Thank you, and sorry.
[10:08] <chu> Try now please
[11:02] <popey> @btlogin
[12:27] <Paddy_NI> There is a problem in #ubuntu-mate with "Guest_84848"
[12:29] <k1l> popey or flexiondotorg not available?
[12:30] <Myrtti> is it the allah spam?
[12:32] <k1l> its a known troll iprange, btw
[12:32] <k1l> bantracker is full of it
[12:33] <k1l> Myrtti: yes it is: http://irclogs.ubuntu.com/2016/05/26/%23ubuntu-mate.html#t12:05
[22:08] <bazhang> no ubottu
[22:08] <dax> she timed out half an hour ago
[22:08] <dax> Pici: ur bots broek
[22:09] <bazhang> cheers
[22:38] <hggdh> dax: broek? Something like Afrikans?
[22:39] <hggdh> not that I speak it, BTW


[09:28] <inetpro> .
[10:08] <pavlushka> ..
[10:17] <psydroid> ...
[11:34] <Kilos> \o
[19:09] <Kilos> too cold to think


[02:57] <roasted> hello friends
[02:57] <roasted> question for a project manager - is it a requirement that ubuntu gnome be released at the same time as other *buntu's?
[13:16] <`wolfie> hi, does the beta come with gnome3.10?
[13:17] <`wolfie> ubuntu gnome 13.10 i mean
[13:21] <smartboyhw> `wolfie, no
[13:21] <smartboyhw> You can, of course, have GNOME 3.10 by adding a PPA.
[13:24] <`wolfie> how bout gnome wayland tech preview like in fedora20
[13:24] <`wolfie> does the ppa have that??
[13:28]  * smartboyhw doesn't know, sorry;P
[13:40] <`wolfie> what version of wayland is packaged in ubuntugnome13.10 beta?
[13:44] <Guest93121> Hello guys, i have problem installing weather extension on ubuntu gnome 64bit 13.04, this is the error : Error: Requiring GWeather, version none: Typelib file for namespace 'GWeather' (any version) not found
[13:54] <Guest93121> anyone
[14:00] <bjsnider> Guest93121, install the typelib file
[14:01] <bjsnider> gir1.0-gweather-3.0
[14:01] <bjsnider> or whatever it is
[16:09] <ricotz> darkxst, hi, thanks for the hint, i am going to push a mozjs24 package
[16:50] <ricotz> darkxst, https://launchpad.net/~ricotz/+archive/unstable/+sourcepub/3533420/+listing-archive-extra
[18:34] <valahead> what's up people :D
[18:44] <Amon-san> hi. i was wondering if ubuntu gnome will support wayland when development is at the right stage?
[18:57] <bjsnider> of course. that's gnome
[19:11] <Amon-san> bjsnider was that directed to me?
[19:12] <bjsnider> yes
[19:14] <Amon-san> ok thanks. so will there be parallel support of both systems mir and wayland or will it be exclusively wayland?
[19:18] <`wolfie> Amon-san, I dont think gnome will support mir anytime soon
[19:22] <Amon-san> good :-D
[19:23] <Amon-san> Have a nice evening you all :-D
[19:23]  * Amon-san signing off
[19:58] <manuelcua> I realized that the Daily ISO and the Beta2 ISO of Ubuntu Gnome in QA Testing Pare are the same. Is that correct?
[19:58] <manuelcua> *Page
[22:44] <manuelcua> Is anyone in the room??? By that I mean that can talk?
[22:44] <manuelcua> or write lol
[22:53] <darkxst> manuelcua, just ask!
[22:58] <manuelcua> I did, like three hours ago lol
[22:59] <manuelcua> I realized that the Daily ISO and the Beta2 ISO of Ubuntu Gnome in QA Testing Page are the same. Is that correct?
[23:02] <manuelcua> I've send my other question on a Testing matter to the mailing-list
[23:03] <darkxst> probably the cron jobs havent been turned back on yet.
[23:03] <manuelcua> Ok, got it
[23:08] <darkxst> manuelcua, there should be a "try ubuntu" option in syslinux screen
[23:09] <darkxst> but you have to press any key, when the first grey screen loads


[13:47] <BluesKaj> Hi all
[15:12] <dscassel> Morning.
[15:14] <BluesKaj> 'Morning dscassel
[23:53] <dscassel> Meeting in 5 minutes. (ish)
[23:58] <hakimsheriff> Is there a meeting now?
[23:59] <dscassel> Yeah.


[01:58] <asac> @time
[01:58] <ubotu> Current time in Etc/UTC: January 30 2008, 01:58:52 - Next meeting: Edubuntu meeting in 10 hours 1 minute
[02:56] <shirish> Ubulette_: you up m8?
[02:58] <shirish> Kazehakase just released 0.5.2
[02:58] <shirish> bug 187210
[02:58] <ubotu> Launchpad bug 187210 in kazehakase "upgrade version available kazehakase 0.5.2" [Undecided,New] https://launchpad.net/bugs/187210
[02:59] <shirish> Ubulette_: I know you packaged it some releases ago. It would be nice to have it again :)
[11:38] <asac> Ubulette_: if you tell me that your kaze branch is good and will work on debian i would be willing to push it to debian and then to ubuntu as well
[11:41] <asac> Ubulette_: http://afp.google.com/article/ALeqM5iU4Lq7tOR_WVOJLZ3IeRaIH03x6w
[14:05] <armin76> [reed]: can you tell me if the trasversal stuff in http://blog.mozilla.com/security is just for win32?
[14:11] <asac> armin76: no its not win only ... sec release will be out on mon
[14:12] <asac> armin76: the fix is in mozilla bug 413250
[14:12] <ubotu> Mozilla bug 413250 in General "chrome directory traversal (local disk access via "flat" addons)" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=413250
[14:13] <armin76> okay, thanks
[14:16]  * asac off to the doctor
[16:08] <shirish> hey guys, anybody up?
[16:13] <shirish> Ubulette_: just ping when you're up? I'll be today on for quite some time.
[16:45] <shirish> asac: did you see the mail I sent u?
[16:46] <asac> kaze?
[16:48] <shirish> yup
[16:48] <shirish> I'm having the same issue/crashing with FF2. I decided to file this one rather than FF2, although both have the same characteristics.
[16:49] <shirish> Mind u this is on hardy though.
[16:56] <asac> he crashing?
[16:56] <asac> shirish: hmm ... can you install -dbgsym packages and run firefox in gdb?
[16:56] <asac> like firefox -g
[16:56] <asac> (gdb) run
[16:56] <asac> then reproduce and type
[16:56] <asac> bt
[16:56] <asac> then
[16:56] <asac> bt full
[16:56] <asac> and attach that to the bug (as the bug apperas to not have a vlid backtrace)
[16:57] <shirish> aha, ok will do
[16:58] <shirish> asac: that was with kazahekase, but will do of kazahekase as well.
[16:58] <asac> thanks
[16:58] <asac> let me know if you have something :)
[16:58] <shirish> sure, will do :)
[17:21] <shirish> out for now. :)
[18:48] <Ubulette> hi
[19:12] <Ubulette> asac, http://cairographics.org//news/cairo-1.5.8/
[19:25] <armin76> yay
[20:03] <Ubulette> http://developer.mozilla.org/devnews/index.php/2008/01/29/firefox-3-beta-3-code-freeze-tonight/
[21:51] <armin76> nsinstall: cannot access ../../dist/branding/default.xpm: No such file or directory
[21:51] <armin76> gmake[4]: *** [libs] Error 1
[21:51] <armin76> gmake[4]: Leaving directory `/var/tmp/portage/www-client/mozilla-firefox-3.0_pre20080130/work/mozilla/browser/app'
[21:51] <armin76> trun broken?
[21:51] <armin76> trunk
[21:54] <armin76> probably my patch...
[22:00] <Ubulette> i'll rebuild trunk now that i've solved my cairo issue
[22:02] <Ubulette> and I need to drop my system png as ubuntu guys don't want the apng patch :(
[22:05] <armin76> hahaha
[22:05] <armin76> i told you :P
[22:05] <Ubulette> you did ?
[22:06] <armin76> yeah, something like that
[22:14] <armin76> wtf
[22:14] <armin76> Ubulette: did they add the icons for the bookmarks again?
[22:14] <Ubulette> I don't think so.
[22:15] <Ubulette> mozilla bug 404825
[22:15] <ubotu> Mozilla bug 404825 in Widget: Gtk "Bookmark folders in Personal Toolbar" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=404825
[22:16] <armin76> http://dev.gentoo.org/~armin76/ff3icons3.png
[22:19] <Ubulette> ehhhh
[22:22] <armin76> i'm i right?
[22:23] <Ubulette> no idea, i'm rebuilding everything
[22:23] <Ubulette> nss-trunk is broken too: http://paste.ubuntu.com/4014/
[22:24] <armin76> i only use cvs tags
[22:25] <armin76> http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&file=browser.css&branch=&root=/cvsroot&subdir=/mozilla/browser/themes/gnomestripe/browser&command=DIFF_FRAMESET&rev1=1.157&rev2=1.158
[22:25] <armin76> could be that change?
[22:25] <armin76> haha
[22:25] <armin76> or this one?
[22:25] <armin76> http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&file=browser.css&branch=&root=/cvsroot&subdir=/mozilla/browser/themes/gnomestripe/browser&command=DIFF_FRAMESET&rev1=1.160&rev2=1.161
[22:27] <armin76> oh
[22:27] <armin76> mozilla bug 413294
[22:27] <ubotu> Mozilla bug 413294 in OS Integration "[gnomestripe] folders on bookmarks toolbar are missing icons" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=413294
[22:27] <armin76> Ubulette: ^^^you should be happy now :P
[22:27] <Ubulette> strange the guy in the bug did not comment about that
[23:34] <asac> Ubulette: good ... lets hope that 1.5.8 is good enough for beta3
[23:52] <asac> [reed]: do you know anyhting about a serious X bug in ff3?
[23:52] <[reed]> what bug?
[23:54] <asac> no idea; thats why i asked ... just heard that you are tracking it and that it must be serios :)
[23:54] <Ubulette> i've seen it at work on an ati box
[23:54]  * asac running the bug muncher
[23:55] <Ubulette> ff3 renders part of the page using the desktop background
[23:55] <asac> [reed]: how can i get all blockers for beta3? do i need to use the advanced search feature or is there a shorthand element somewhere that i am missing?
[23:55] <Ubulette> kinda weird
[23:56] <asac> Ubulette: yes ... maybe thats really the bug ... the one we are looking for causes wrong rendering and Xcrashes
[23:56] <[reed]> I was tracking it?
[23:57] <[reed]> who told you that?
[23:57] <[reed]> lol
[23:57] <armin76> asac did
[23:57] <asac> yeah ... i spoke to myself ;)
[23:57] <asac> [reed]: whats the bug id?
[23:58] <Ubulette> mozilla bug 406810
[23:58] <Ubulette> hm, no
[23:58] <ubotu> Mozilla bug 406810 in General "Analyze startup time of Firefox3 (TRUNK)" [Enhancement,Assigned] http://bugzilla.mozilla.org/show_bug.cgi?id=406810
[23:58] <[reed]> asac: I still don't know what you're talking about
[23:58] <[reed]> http://tinyurl.com/yr74y3 is the list of all blockers left for b3
[23:58] <Ubulette> bug 186385 seems popular, but i'm not seeing it
[23:58] <ubotu> Launchpad bug 186385 in firefox-3.0 "Firefox 3.0 renders pages slowly at 100% CPU and is unresponsive as it does so" [Undecided,New] https://launchpad.net/bugs/186385