=== doko_ is now known as doko === psivaa is now known as psivaa-lunch === chrisccoulson is now known as notchrisccoulson === psivaa-lunch is now known as psivaa === bdrung_ is now known as bdrung [14:46] Is there a reason all the current Iso directories also have old saucy images in them? http://cdimage.ubuntu.com/daily-live/current/ http://cdimage.ubuntu.com/ubuntustudio/dvd/current/ For example, but I would guess the rest are the same. [14:47] Is there a better place to ask :) [14:49] seems like a bug, possibly related to the current/pending logic [14:49] cjwatson: ^ [14:50] the 20131016.1 image should also have disappeared a while back, I suspect it's only kep there because it's referenced from current/ [14:50] it's easy enough to manually fix, but I'd rather wait for cjwatson to take a look so we can get the tool fixed instead [14:52] No problem, just making sure someone is aware. [15:04] stgraber: I've always just cleaned them out by hand TBH [15:05] Though it's probably easier to fix now following the Python rewrite [15:06] cjwatson: ok, I wasn't sure the mixed saucy/trusty symlinks under current/ was a known issue when opening a new series. If it's, then that's fine and it's indeed quite easy to fix by hand. [15:06] Actually, that's odd, it's meant to have code for this already [15:07] Oh, it's just current, OK, that's fixable [15:07] stgraber: Never mind, I'll fix the code :) [15:07] thanks :) [15:07] And you're correct about the effect on pruning, of course [16:34] zul: the new version of samba is blocking in trusty-proposed because it makes several other packages uninstallable (zentyal-samba, openchange, rds). Will you take care of figuring out what needs to happen with these? [16:34] slangasek: sure [16:35] openchange probably just needs a merge from unstable; rds and zentyal aren't in Debian so maybe they need removed [16:35] zul: thanks [16:37] slangasek, I'll ping the zentyal guys - they pretty much look after their own packaging these days [16:37] slangasek: zentyal supposedly had zentyal upstream working in ubuntu and packing it, with even maybe PPU rights as well (can't remember) [16:38] ah, alrighty [16:40] slangasek: zentyal has their own ppa now afaik [16:40] does that mean we want it removed from the archive? [16:41] i dont know they havent done anything for a while [16:42] slangasek, zul: I've ping the upstream guy to find out [16:47] slangasek, zul: they are looking at what todo now - lets give them a couple of days if thats OK [16:48] thats cool with me [17:00] slangasek, cjwatson, infinity, are we mumbling today? [17:01] I would but I seem to have mislaid my headphones ... [17:04] Oh, there they are [17:13] slangasek, zul: OK _ they have quite a bit of work todo upstream things to various other projects [17:13] so we agreed removal right now is the best course for zentyal [17:14] zentyal-samba at least [17:17] stgraber: still working on that cdimage thing, fwiw - I'm certainly convinced it's real but having a bit of trouble setting up a test for it [17:17] ok :) [17:17] jamespage: that also breaks zentyal-printers + ebox-printers, should those also be removed? (And can you file a removal request?) [17:17] oh - go on then :-) [17:23] bug 1252375 for reference [17:23] Launchpad bug 1252375 in zentyal-samba (Ubuntu) "Please remove zentyal-samba + zentyal-printers from trusty" [Medium,Confirmed] https://launchpad.net/bugs/1252375 [17:27] stgraber,OvenWerks: code fixed; the next daily build should have the effect of clearing things out [17:27] (I'll check tomorrow) === notchrisccoulson is now known as chrisccoulson [17:40] so. not sure what happened. I dput an updated crash package, but I didn't get a notification via email nor did dput complain. I also don't see it in the trusty queues. [17:46] 2013-11-18 16:09:12 INFO Failed to parse changes file '/srv/launchpad.net/ubuntu-queue/incoming/upload-ftp-20131118-160843-000434/crash_7.0.3-3ubuntu1_source.changes': GPG verification of /srv/launchpad.net/ubuntu-queue/incoming/upload-ftp-20131118-160843-000434/ [17:46] crash_7.0.3-3ubuntu1_source.changes failed: Verification failed 3 times: ["(7, 58, u'No data')", "(7, 58, u'No data')", "(7, 58, u'No data')"] [17:46] arges: Are you sure you signed it? [17:46] cjwatson: yes, double checking now [17:47] If you definitely did, then I think that must be a problem communicating with the keyserver, and it probably needs help from #webops internal. [17:47] Or #launchpad-ops. [17:47] gpg: Good signature from "Chris J Arges " [17:47] etc [17:47] cjwatson: ok. i'll ping #webops...anything I can reference to make it easier for them to track down? [17:47] launchpad was having a funny turn for me a bit ago [17:48] arges: The log messages above, which I found in carob:/srv/launchpad.net-logs/production/pepo/lp_queue/process-upload.log [17:48] cjwatson: thanks [17:49] In the past this has sometimes been related to communication problems between pepo and the keyserver, although I'm guessing [19:29] stgraber: Is there a reason you didn't release desktop-file-utils when you were going through saucy SRUs just now? [19:30] ScottK: hmm, my bash history says I did [19:30] OK. [19:30] The bug doesn't seem updated, maybe LP is just slow. [19:30] yeah, not sure what happened there, let me sru-release it again... [19:31] ah, no, was my bad, typo in the source name :) [19:31] released now [19:31] Excellent. [19:31] Thanks for getting to it 5 minutes before me and saving me the work. [19:31] :) [19:32] oh and looks like muon built fine now (was FTBFS), so I'll release that one in a few minutes too [19:32] (FTBFS on arm64 that was) [19:33] Thanks.