[00:29] iulian: you uploaded ghc without -v :( [00:38] MiS-SAT, --override-config flag is needed for changes to pbuilderrc to persist [00:38] MiS-SAT, i.e. pbuilder update --override-config [00:38] (the pbuilder image has priority over pbuilderrc, by default) [01:29] micahg: you don't mind if I sync moodle for a bunch of security fixes? wasn't sure if you'd spotted that one yet :) [02:16] ajmitch: go for it [02:17] micahg: great, was more of a heads up that it was being synced, in case it gets held up for a few hours in the queue [02:35] http://people.canonical.com/~ubuntu-archive/transitions/ghc.html (and the fun is already showing up) [02:38] * ajmitch should get in on the fun [02:39] ajmitch: you have to wait for ghc to build on all archs first :) [02:39] micahg: in other words, probably not before I go to bed tonight? :) [02:39] right [02:40] well, ~7-8 hours [02:40] that's what I thought [02:40] assuming that the builds succeed [02:41] amd64 & armhf look to have failed already === almaisan-away is now known as al-maisan [07:04] broder: I see you made it into the LWN quotes this week https://lwn.net/Articles/484521/ [07:04] haha, somebody pointed that out to me [07:05] if i had known they'd be looking i would have tried to write a better soundbyte [07:05] heh [07:08] ah, good, vorlon's "To be fair, it also omits one of SystemD's greatest strengths: Roman numeral-compliant project naming. System D is obviously way better than System V." made it too [07:10] i guess it's just a banner week for ubuntu [07:11] where are all of these === al-maisan is now known as almaisan-away [07:11] slangasek is the "development" quote of the week: https://lwn.net/Articles/484166/ [07:11] they're part of the lwn weekly edition [07:12] ah [07:12] well, that one came from a Debian flamewar^Wthread that had lots of amusing bits [08:14] good morning === almaisan-away is now known as al-maisan === Zic_ is now known as Zic [09:43] heya [09:55] hi Laney [09:58] myunity fan? [10:13] Laney: just excited to see things backported ;) [10:48] yar === al-maisan is now known as almaisan-away [12:33] Heya - I have two related packages built from separate source packages, the upstream version numbers will always match up but the package version may not. I was hoping for something like "python-carbon (= ${binary:Version})" where I can just check the upstream version number? any suggestions? [12:34] Kiall: {source:Version} [12:35] Actually, that's not right. [12:35] ah.. nice! Is there a list of that kind of thing anywhere? [12:37] Actually, that does seem correct. Googling for that turned out the deb-substvars man page, with that listed [12:38] source:Upstream-Version [12:39] Yes. That's the place to look. [12:39] It seems both are listed there.. the Upstream-Version seems to included the "Debian version epoch if any." [12:39] source:Version still includes the package revision. You need Upstream-Version [12:40] Oh. Fair enough :) Thanks [12:40] Will give that a go now... [12:58] ScottK: That worked a charm, thanks again... [13:12] You're welcome. === almaisan-away is now known as al-maisan === tubadaz_ is now known as tubadaz === Quintasan_ is now known as Quintasan === yofel_ is now known as yofel === tubadaz_ is now known as tubadaz === al-maisan is now known as almaisan-away === YokoZar1 is now known as YokoZar === plustwo is now known as plustwo_1 [18:38] Hi [18:38] Need some instant advice [18:39] with? [18:39] UBJ [18:40] For test 12.04 and Bug reporting [18:40] I need to know what we have to do [18:40] how to start [18:40] etc [19:00] ubuntu-bug package [19:17] Hi all! === plustwo_1 is now known as plustwo [19:39] :( my unison upload was rejected, no the search for the reason begins again ... [19:39] why does the mail not just tell you [19:41] https://code.launchpad.net/~jtaylor/ubuntu/precise/unison2.32.52/lp-937596 here is the branch in case someone want to help me in the search ._. [19:42] does the mail tell you who rejected it? [19:42] no [19:42] a little trickier then, I guess you have to ask around :) [19:42] The archive admin that rejected it is supposed to mail you seperately. [19:42] (It wasn't me) [19:47] jtaylor: There were some accidental rejects that are being restored. [19:49] k, because I can't find an issue with the package === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === RoAkSoAx_ is now known as roaksoax === RoAkSoAx is now known as roaksoax [23:24] For backports, how strict are the criteria? Can new-in-precise packages be added? [23:25] arand: yes. what part of the criteria makes you think you couldn't? [23:27] Hmm, re-reading it againk, I guess none... [23:30] Also, new versions of multiplayer-centric games (which needs to match server-client versions), are those strictly backport-material, and not SRU-able? === nixmaniack is now known as n1x [23:50] arand: That depends case to case. [23:51] ok, I guess I'll have to dig deeper once that time comes :) [23:52] Hmm, by default only the main repo is available right? [23:52] But software centre shows universe as well? Or does it only hint about enabling it? [23:55] And if something is in universe and depends on a -data package in mutliverse, it asks for confirmation but auto-enables multiverse then, right? [23:56] packages in universe can't depend on packages in multivers [23:57] Hmm, I wonder if my package is voilating policy then :/ [23:58] Ah, no they're both in multiverse, good :) [23:59] But on that note, does Ubuntu hold the same rules as Debian as to what is considered "free" with respect to artwork, music, 3D models, etc.?