[00:36] <phillw> ScottK: kubuntu-ppc is still not on http://iso.qa.ubuntu.com/qatracker/milestones/269/builds is it worth asking our ppc testers to look out for it?
[00:36] <ScottK> Let me have a look.
[00:37] <phillw> I'm going to send them one last nagging email :)
[00:46] <ScottK> phillw: It's there now.
[00:46] <phillw> okies, I'll amend my email :D
[00:49] <ScottK> See. There you go.
[00:49] <phillw> ScottK: are you ubuntu@kitterman.com ?
[00:49] <ScottK> I am.
[00:49] <phillw> okies, just so you get a cc
[00:50] <ScottK> I'm also kitterman@ubuntu.com.  So you can actually do it either way.
[00:50] <ScottK> ;-)
[00:54] <phillw> ScottK: you have mail, either way. I'm not too PC with the lubuntu-qa team, we work hard, but chat easy :)
[00:54] <ScottK> OK.
[01:12] <ScottK> highvoltage: I'm a bit unsure what to to about calibre - http://launchpadlibrarian.net/138120901/calibre_0.9.18%2Bdfsg-1bzr_source.changes - It's on your image, so I'm relucant to accept, but if it's not in pre-release, we're stuck with the non-free stuff in the archive.
[01:30] <TheDrums> https://launchpad.net/ubuntu/+source/adobe-flashplugin/  Not in raring?
[01:35] <micahg> TheDrums: partner uploads happen at the last minute
[01:35] <sarnold> also this exists https://launchpad.net/ubuntu/+source/flashplugin-nonfree
[01:35] <TheDrums> micahg: Thank you.
[01:36]  * micahg wonders if there's a doc reminding people they need to happen
[01:37] <TheDrums> (There was plenty of packages in the partner repo, wasn't sure if it was removed or had something else done with it.)
[06:54] <stgraber> good morning
[07:22] <infinity> phillw: Any issues with me respinning lubuntu alternates for you today?  The current ones contain one stale package.
[07:52] <stgraber> xnox, cjwatson: do you know if anyone looked at bug 1172002?
[07:52] <ubot2> Launchpad bug 1172002 in ubiquity (Ubuntu) "Install doesn't mount encrypted swap for reinstall" [Undecided,Confirmed] https://launchpad.net/bugs/1172002
[08:38] <infinity> phillw: Sine you didn't seem to be awake yet, I just went ahead and respun lubuntu/alternates.  They should spit out soon.
[08:38] <xnox> stgraber: I commented on it. It is a bit strange. Partman doesn't seem to show any logical partition, which i'd expect to be dm-crypt activated with random password to become swap.
[08:38] <infinity> phillw: s/Sine/Since/
[08:39] <stgraber> xnox: right, I saw your discussion with infinity in #ubuntu-installer
[08:39] <xnox> ack.
[08:51] <ogra_> stgraber, i have a wishlist request for the iso tracker ... can we please use sane dates ?
[08:51] <ogra_> like iso ones :)
[08:52] <ogra_> 04/24/2013 is as wrong as a date can be :P
[08:55] <knome> is there a wikipage or a blog post that explains the new release model? i'm looking for something that i can link to from the xubuntu release notes, don't really want to use https://wiki.ubuntu.com/ReleaseCadence/RollingRelease
[08:55] <infinity> knome: There is no new release model.  Does that help?
[08:55] <knome> well... no.
[08:56] <knome> is raring supported for 18 months?
[08:56] <cjwatson> 9 months
[08:56] <infinity> knome: raring is supported for 9 months.  But the release model hasn't changed, just the support window.
[08:56] <knome> okay, is there an announcement for that?
[08:56] <cjwatson> it was in TB minutes I think ...
[08:56] <stgraber> ogra_: well, Drupal thinks it's in the US and so formats the date that way ;)
[08:57] <knome> ok, i'll dig up the archives
[08:57] <cjwatson> https://lists.ubuntu.com/archives/ubuntu-devel-announce/2013-March/001027.html
[08:57] <Laney> stgraber did a summary and it got posted on some blog
[08:57] <infinity> I'll be sure to mention it in the release announcement.
[08:57] <ogra_> stgraber, tell it that it isnt :)
[08:57] <cjwatson> But it certainly ought to be written up in some less "for those who care about Ubuntu process minutiae" way
[08:58] <stgraber> ogra_: oh actually, looks like we can now reconfigure that in the web UI! let me see if I can easily change that without breaking things
[08:58] <ogra_> :)
[08:59] <infinity> stgraber: If I accepted callibre and rebuilt edubuntu-dvd, would you or highvoltage have a sad?
[08:59] <infinity> calibre, even.
[09:00] <highvoltage> infinity: ah I meant to respond to the calibre issue earlier but had a ton of interruptions (I should spend less time at the office)
[09:00] <stgraber> infinity: considering I'm half-way through testing, probably :)
[09:00] <highvoltage> infinity: syncing now and will then test. cdimage is pretty slow though.
[09:00] <knome> infinity, if you're including it in the general release notes, then i don't need to. ta :)
[09:00] <stgraber> highvoltage: it's your country that has slow internet, I'm getting my iso images at a nice 8MB/s here ;)
[09:00]  * cjwatson is getting 38MB/s from cdimage, anything else is your problem :P
[09:01]  * cjwatson <- slight advantage this week
[09:01] <infinity> Well, looks who's all smug about his borrowed internet.
[09:01] <ogra_> cjwatson, using LTE over your mobile ?
[09:01] <ogra_> :)
[09:01] <highvoltage> I got 10mbps for everything else yesterday but just around 100-200KB/s for cdimage.
[09:01] <highvoltage> maybe it was just bad timing or something from my part :)
[09:01] <cjwatson> I will admit that my mobile internet is in fact faster than my ADSL, but not that ...
[09:01] <ogra_> heh
[09:02] <cjwatson> (anyway, my actual point was that cdimage itself seems fine, even if it's only because I'm sort of effectively next to it)
[09:02] <ogra_> yeah
[09:03] <highvoltage> I still only get around 200KB/s from it, but my image was last synced yesterday so I guess it won't take long anyway
[09:04] <infinity> highvoltage / stgraber : Want to join in on the conversation in #-devel?
[09:05] <stgraber> infinity: yeah, was looking over the diff to actually know what we're talking about ;)
[09:07] <Laney> We can still sneak unseeded universe fixes in, yes?
[09:09] <infinity> Laney: Absolutely.
[09:09] <Laney> Solid.
[09:15] <stgraber> ok, so I finished pushing my test results for Edubuntu (everything looking good) and marked the images for rebuild so nobody wastes their time on them
[09:15] <stgraber> I really need to figure out why queuebot does that ^...
[09:16] <infinity> I assume because it's Swiss.
[09:18] <highvoltage> stgraber: ack
[09:18] <knome> fixed the broken link to stéphanes detailed summary at https://wiki.ubuntu.com/TechnicalBoard/TeamReports/13/March
[09:36] <knome> will https://wiki.ubuntu.com/RaringRingtail/ReleaseNotes be created sometime soon?
[09:36] <infinity> knome: It will exist later today.
[09:37] <knome> cheers
[09:37] <infinity> knome: But if you need to edit or add to it, edit TechnicalOverview please.
[09:37] <infinity> knome: It'll just be a copy/paste (or even just a rename) of that.
[09:37] <knome> sure
[09:37] <knome> i'm just working on the xubuntu release announcement and prefer to have the links ready
[09:43] <smartboyhw> infinity: Which link.format are we supposed to use for flavour release notes? https://wiki.ubuntu.com/RaringRingtail/ReleaseNotes/<distro> or https://wiki.ubuntu.com/RaringRingtail/<distro> ?
[09:44] <infinity> smartboyhw: Wherever you want to put them, as long as you link them correctly from the master one, I don't much care, to be honest.
[09:45] <smartboyhw> infinity: OK then, the Ubuntu Studio one is at https://wiki.ubuntu.com/RaringRingtail/UbuntuStudio
[09:46] <smartboyhw> I saw the Lubuntu one having /ReleaseNotes after /RaringRingtail and I was afraid I got it wrong:P
[09:46] <infinity> smartboyhw: Is it linked from TechnicalOverview?
[09:47] <infinity> smartboyhw: I don't want to do all the wiki gardening required to make sure everyone's stuff is right, so if you link it to the right location, I don't care where that is. :)
[11:30] <Laney> please review kaya in the queue
[11:33] <cjwatson> ooh, you fixed it?
[11:33] <cjwatson> +-import Contol.Exception
[11:33] <cjwatson> ++import Control.Exception
[11:33] <cjwatson> stylish
[11:34] <Laney> erm, wait, that's probably my mistake
[11:34] <Laney> I made that typo while fixing it
[11:34] <cjwatson> you appear to have fixed that typo
[11:34] <Laney> does the diff introduce it and then fix it?
[11:35] <cjwatson> er, can't see, have accepted :)
[11:35]  * cjwatson goes and looks again
[11:35] <Laney> yes
[11:35] <cjwatson> Yeah, it does
[11:35] <cjwatson> Oh well
[11:35] <stgraber> introducing a bug and fixing it in the same diff, yay! :)
[11:35] <Laney> I was evidently on new-gc-api when I did it
[11:35] <Laney> ho hum
[11:35] <cjwatson> Can tidy up for s
[11:42] <smartboyhw_> Question: Still no codename for S cycle right?
[12:09] <rustx> hi
[12:10] <rustx> could i ask you information about the bug fix i would like to provide you on this page ? https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1170325
[12:10] <ubot2> Launchpad bug 1170325 in facter (Ubuntu) "Facter 1.6.X not considering Qemu/KVM virtual type" [Undecided,New]
[12:11] <rustx> i m not sure how to propose this fix in the LTS development release
[12:11] <rustx> can somebody help me to make it clear ?
[12:12] <ScottK> rustx: We're releasing Ubuntu 13.04 tomorrow, so anything not directly related to that is extremely unlikely to get attention until next week.
[12:13] <rustx> ScottK: I clearly understand
[12:13] <rustx> ScottK: that's ok to me, i will fix my productio on my side, and will come back to you next week
[12:14] <rustx> ScottK: the only thing i am sure with is that puppet devs fixed that bug in later version of facter. I just wanted to be sure that the 120.4 LTS won't be broken, as this is the distro I use on production
[12:14] <rustx> ScottK: all the best for Ubuntu 13.04 release, big up !
[12:15] <ScottK> rustx: Sure.  If you can find the exact commit that fixed the bug, then there's a good chance of getting it fixed, but not this week.
[12:19] <seb128> rustx, ScottK: seems like http://projects.puppetlabs.com/issues/20265 ?
[12:19] <rustx> yes, this is my issue
[12:19] <rustx> on puppet side, they told me it was fixed on further facter version (1.7), and asked me to see with Ubuntu teams
[12:20] <rustx> i wil find the exact commit that fixes this
[12:24] <seb128> rustx, seems like it's https://github.com/puppetlabs/facter/commit/5c653e98e97ba8e83a46b8e0c1fd72dfe672964b
[12:25] <seb128> rustx, https://github.com/puppetlabs/facter/commit/4b44b797785ad48d64116e9e13f063dfe89910d2 rather
[12:25] <rustx> seb128: yes, you got it
[12:25] <Daviey> Wow, that is remarkably unsafe detection
[12:25] <rustx> my patch was proposing using a pipe '|' to add KVM Common Processor
[12:25] <rustx> but it is exactly the same
[12:26] <rustx> won't break anything, but will fix all VMs running with latest version of qemu-server (with proxmox 2.3)
[12:26] <seb128> rustx, if you want that SRUed you need to add SRU infos to the bug, especially a testcase to confirm the bug and the fix
[12:26] <rustx> yes, ok, i will do it
[12:26] <seb128> thanks
[12:26] <Daviey> I don't think that fix is enough..
[12:26] <rustx> this if my first bug fix contribution, so i want to do it well (and not bother you too much)
[12:27] <seb128> subscribe ubuntu-sponsors to the bug once you are done
[12:27] <rustx> ok
[12:27] <seb128> Daviey, I've no clue about the topic, just tried to go back from the launchpad bug infos to the upstream commit...
[12:27] <rustx> seb128: and you did it really well
[12:27] <rustx> ty
[12:27] <seb128> yw
[12:28] <rustx> Daviey: what is your concern about hat fix which could not be enough ?
[12:28] <Riddell> update-manager caches the meta-release file (in /var/lib/update-manager/meta-release or $HOME/.cache/update-manager-core/ depending on who runs it) won't that stop notification happening when the new release happens?
[12:28] <Riddell> I just spent an hour wondering why I wasn't getting notification on my test
[12:28] <cjwatson> It catches up eventually, and it's good to spread out the load a bit
[12:29] <Riddell> fair enough I suppose, makes testing a bit more hassle is all
[12:30] <cjwatson> there's a force option somewhere
[12:30] <cjwatson> actually, it also uses If-Modified-Since
[12:32] <Daviey> rustx: I would suggest that, checking if, dmidecode -s system-manufacturer  == Bochs is cleaner
[12:33] <Daviey> rustx: the cpu field is largely free-form
[12:33] <rustx> Daviey: yep, but the is_virtual method in facter depends on the output of the /proc/cpuinfo
[12:34] <rustx> Daviey: i just proposed a patch in accordance with the explanation about this method, on puppet side
[12:34] <Daviey> rustx: Well, your change makes it no worse than it currently is then :)... but if you really want to be a good citzen, you could speak to upstream about making their detection suck less. :)
[12:35] <rustx> Daviey: I clearly agree with you, but didn't really want to lead the facter dev. I just saw on my production that all my VMs were considered as 'physical' after qemu-server update, and went to apply a bug fix on my side
[12:35] <rustx> Daviey: all my monitoring was wrong because of that simple output in /proc/cpuinfo
[12:36] <rustx> so, I decided to see if i can help on any way :)
[12:36] <seb128> rustx, was qemu-server a distro upgrade/SRU?
[12:36] <Daviey> rustx: Yes, sorry - I didn't mean to suggest you shouldn't follow upstreams path
[12:37] <rustx> seb128: yep. This bug was caused just after qemu-server update
[12:37] <rustx> i could realize this using proxmoxVE
[12:37] <rustx> with proxmox 2.2, no trouble, the output is ok
[12:37] <rustx> with proxmox 2.3, the bug appears, as the output for /proc/cpuinfo changed on the VMs ...
[12:37] <seb128> rustx, do you know what upgrade exactly?
[12:38] <rustx> i am updating the SRU, to be sure it's clear to you
[12:38] <rustx> i will tell you
[12:38] <seb128> rustx, I don't see any major change in precise
[12:39] <seb128> thanks
[12:39] <rustx> in precise, there is no change
[12:39] <rustx> seb128: but in qemu-server, (debian side), there were some (or on proxmoxVE side)
[12:39] <rustx> which causes the bug when using facter1.6
[12:39] <seb128> I see
[12:39] <rustx> at the end, including facter1.7 in ubuntu 12.04 would fix everything
[12:40] <seb128> well anyway that upstream patch might not be perfect, as Daviey pointed, but if it fixes real world issues it seems ok for a SRU
[12:40] <rustx> or, the patch I proposed you should help to fix the facter1.6 version
[12:40] <Daviey> (This is why I consider it unsafe, as the host/user can put whatever they like) - but this is a good short term fix.
[12:40] <rustx> i repeat this is my first bug fix : i hope i am not bothering you too much with this
[12:41] <Daviey> rustx: not at all.. your effort is greatly appreciated :)
[12:43] <rustx> seb128: http://pastebin.com/DZXmmXCC . This first paste is containing information about my node, with qemu-server not updated (no bug on the VM)
[12:43] <rustx> seb128: http://pastebin.com/HsHyij3j this second one is containing information on the node that was updated, and that reveals wrong output for /proc/cpuinfo on all the running ubuntu 12.04 Vms ...
[12:44] <rustx> the only difference is the qemu-server version at the end ..
[12:45] <Daviey> rustx: Ah, https://github.com/puppetlabs/facter/commit/4b44b797785ad48d64116e9e13f063dfe89910d2#L1R140 <--- does add checking of dmideocode.. seb128 found the right patch for you to pull :)
[12:46] <rustx> seb128: this is the output of a VM running on the first node (not updated) http://pastebin.com/FuRp7D4M
[12:47] <rustx> seb128: and this is the output of a VM running on the second node (updated) -> http://pastebin.com/ifhNk77J
[12:47] <rustx> great then
[12:47] <rustx> Daviey: you should be a better sysadmin than I am, congrats, and thank you for making me learn good practices
[12:48] <rustx> i like it
[12:49] <Daviey> rustx: Thanks for driving this. :) (adding .patch to the url gives you a nice patch you can pull in btw)
[12:51] <rustx> Daviey: thanks for information
[12:52] <rustx> i will update my launchpad bug issue, so that it contains all information we discussed here
[12:52] <rustx> i really want to do it clean :)
[12:55] <rustx> waouhou, you already updated my launchpad issue ..
[12:56] <rustx> you're too strong guys !
[13:00] <stgraber> highvoltage: ^
[13:07] <highvoltage> stgraber: awesome, thanks
[13:15] <cjwatson> ScottK: bug 910903 - the source package is still around.  Is it ever likely to be fixed, or should we remove it?
[13:15] <ubot2> Launchpad bug 908462 in plasma-widget-daisy (Ubuntu Precise) "duplicate for #910903 FTBFS: error: 'TaskManager::TaskPtr' has not been declared " [High,Fix released] https://launchpad.net/bugs/908462
[13:16] <ScottK> cjwatson: IIRC it's dead upstream so removal is fine.
[13:19] <cjwatson> Oh, removed from Debian too.  That makes the decision easier.
[13:20] <rustx> seb128: I've updated the SRU with all informations i could
[13:20] <cjwatson> ... I was looking at the wrong package.  Never in Debian.
[13:21] <seb128> rustx, thanks, the testcase should be something others can follow to confirm the issue and verify the fix
[13:21] <seb128> rustx, like "install kvm; configure it this way; connect to a server running that version; it gives that result"
[13:21] <cjwatson> ScottK: Hmm.  FWIW plasma-widget-fancytasks has a newer version upstream than was ever in Ubuntu.
[13:21] <cjwatson> http://kde-look.org/content/show.php/Fancy+Tasks?content=99737
[13:21] <rustx> ok, i will udpate the test case
[13:22] <rustx> seb128: perfect, thanks for your explanation
[13:22] <ScottK> cjwatson: I guess we should look into updating that for "S".
[13:23] <ScottK> Maybe it's time to tell Mark, "It's slimy slug unless you give us a different name."
[13:24] <cjwatson> my family suggested Sad Salamander and Steadfast Sloth
[13:25] <cjwatson> Slippery Snail
[13:25] <Daviey> Poor Mark has been on the road for a while now, he's not had a chance to consult his oxford dictionary.
[13:25] <ScottK> Right.  My premise was to suggest something so horrible it would have to be changed.  Of course the recent budget sequester here in the US suggests that can be a risky strategy.
[13:25] <ogra_> yeah, he's travelling
[13:25] <cjwatson> ktouchpadenabler source is superseded by kde-workspace, right?
[13:26] <ScottK> cjwatson: yes.
[13:26] <cjwatson> ScottK: we have a specific precedent for trolling Mark about release names being risky
[13:27] <ScottK> Interesting.
[13:27] <cjwatson> ScottK: we almost ended up with Bendy Badger because of Keybuk trolling him
[13:27] <cjwatson> (Not that Breezy Badger was much better, but eh)
[13:27] <ScottK> We've had worse since.  I'm sure it seemed like a troll at the time.
[13:27] <cjwatson> hah
[13:28] <ScottK> Salacious Salamander
[13:29] <Daviey> Sloppy Sloth, is my preference
[13:29]  * ogra_ is sure mark will again come up with something completely different and unexpected 
[13:31] <rustx> seb128: test case was updated now
[13:33] <rustx> i just hope it fits your expectation
[13:33] <seb128> rustx, that looks great, thanks for the work! please subscribe ubuntu-sponsors to the bug and we are all set ;-)
[13:33] <doko> huh, avian did just build?
[13:35] <rustx> seb128: done -> Your subscription request has been received, and will soon be acted upon
[13:37] <cjwatson> doko: Yeah, apparently magically built when Adam did a mass give-back
[13:37] <cjwatson> Which was surprising, but I'll take it
[13:39] <seb128> rustx, excellent
[13:42] <ScottK> So what's the latest the announcement of the next name has ever come?
[13:42] <ScottK> It's hard to image it being much later than this.
[13:42] <dobey> didrocks: ping
[13:43] <stgraber> ScottK: I think last was the latest we had so far but I don't think it wasn't nearly as late as this one :)
[13:44] <ScottK> Last time was not nearly as late as this one.
[13:44] <seb128> ScottK, http://www.markshuttleworth.com/archives/1195 was on oct 17th where release was on the 18th
[13:44] <rustx> thanks a lot for your time seb128 and Daviey
[13:44] <ScottK> OK, so it's gone to Wednesday before.
[13:45] <ScottK> seb128: Thanks.
[13:45] <seb128> yw ;-)
[13:45]  * popey still wants Schrödinger's Siamese
[13:47] <smartboyhw> ScottK: I rather think it is Snappy Shuttleworth
[13:51] <cjwatson> That's down to ten orphaned source packages, which is I think as good as I can get it for raring.
[13:52]  * Laney wonders how bad ftphs is
[14:00] <cjwatson> Daviey: bug 1017609 - could somebody on your team answer jbicha's question about python-melangeclient?
[14:00] <ubot2> Launchpad bug 1017609 in python-melangeclient (Ubuntu) "Please remove melange from ubuntu archive" [Undecided,New] https://launchpad.net/bugs/1017609
[14:00] <cjwatson> Laney: I don't quite remember, it might be tractable
[14:02] <Laney> cjwatson: yeah, it is
[14:03] <Laney> most of the breakage has been down to this one Control.Exception API change ...
[14:03]  * Laney yah boos at GHC upstream
[14:05] <cjwatson> src/Network/FTP/Server.hs:169:18: Not in scope: `try'
[14:05] <cjwatson> src/Network/FTP/Server.hs:217:33: Not in scope: `catch'
[14:05] <cjwatson> indeed, looks tractable
[14:05] <cjwatson> You sorting?
[14:06] <Laney> done
[14:06] <ScottK> stgraber: Should the "Raring Daily" milestone in the tracker be marked released?  We won't be using that again.
[14:06] <Laney> just donig the packaging bits and bobs
[14:06] <xnox> cjwatson: infinity: stgraber: ^
[14:06] <xnox> ubiquity for kubuntu only.
[14:06] <xnox> Riddell: ScottK ^
[14:07] <ScottK> Standing by to retest.
[14:07] <stgraber> ScottK: nope, not until raring is released as nusakan actually pushes all our builds to the Daily milestone and then those get auto-copied to Raring Final if they're on the manifest
[14:07] <ScottK> stgraber: OK.  Understood.
[14:08] <smartboyhw> xnox: Will ubiquity fix respin the entire world
[14:08] <ScottK> smartboyhw: It will
[14:08] <ScottK> It should only go in if we're going to do that anyway.
[14:08] <smartboyhw> Uh oh:P
[14:09] <xnox> ScottK: smartboyhw: no.
[14:09] <ScottK> xnox: Yes.
[14:09] <xnox> ScottK: smartboyhw: the current plan is to put ubiquity into -updates and respin kubuntu against updates only.
[14:09] <xnox> as ter infinity, cjwatson earlier on.
[14:09] <ScottK> xnox: Oh.  Missed that.  Thanks.
[14:10] <highvoltage> stgraber: do we need a link for the website team to fix https://bugs.launchpad.net/ubuntu-website-content/+bug/1065789 ?
[14:10] <ubot2> Launchpad bug 1065789 in ubuntu-website-content "the release notes link in installer points to www.ubuntu.com" [Undecided,Fix released]
[14:11] <xnox> highvoltage: that happens with website rollout.
[14:11] <xnox> highvoltage: the "link" points to the correct redirector with args. By _default_ at pre-release it redirects to default website(s), but once the website is flipped to the "release" edition, the redirects start working correctly.
[14:12] <xnox> i guess there is no _harm_ in activating redirects early, but the website is frozen already and the next website rollout is the release rollout.
[14:14] <cjwatson> And *not* unblocking ubiquity, since indeed we'll put it in -updates.
[14:14] <cjwatson> Relatively tried-and-tested trick by this point :)
[14:18] <Riddell> ubiquity diff on bug 1172059 looks good
[14:18] <ubot2> Launchpad bug 1172059 in ubiquity (Ubuntu Raring) "kubuntu ubiquity encryption doesn't check password" [High,In progress] https://launchpad.net/bugs/1172059
[14:18] <Riddell> can I let it into -proposed or is someone else taking care of that?
[14:18] <Riddell> oh it's in already
[14:18] <Riddell> groovy
[14:21] <highvoltage> xnox: ok
[14:32] <didrocks> dobey: pong
[14:35] <dobey> didrocks: hey. i've been pinged about getting bug #1163504 fixed in 13.04, but i don't see anything i can do. can you get the fix into -proposed and see about getting new images spinned with the fix?
[14:35] <ubot2> Launchpad bug 1163504 in kopete (Ubuntu Raring) "Trademarked assets" [Undecided,New] https://launchpad.net/bugs/1163504
[14:35] <dobey> didrocks: or a 0-day SRU for worst case?
[14:37] <cjwatson> uhhh
[14:37] <cjwatson> it's kinda late dude :(
[14:37] <dobey> yeah i know that. but tell that to MS legal i guess? :)
[14:37] <cjwatson> (also shouldn't that kopete task be kdenetwork?)
[14:38] <cjwatson> well, um, I thought you guys had this handled
[14:38] <dobey> i knew nothing about it until today
[14:38] <xnox> dobey: but it's fixed in all found packages but kopete which is not on any of the images.
[14:38] <dobey> i just had it dumped on me, and saw it's all unity and there's basically nothing here that i have any privileges in ubuntu to upload :)
[14:39] <xnox> dobey: the next upload can "fix" it, but previous versions of the package will still be in the archive.
[14:39] <dobey> xnox: it's not fixed in unity-asset-pool
[14:39] <cjwatson> we know that older versions will still be in the archive
[14:39] <xnox> dobey: oh....
[14:39] <dobey> xnox: it's committed in the upstream, but it's still in the ubuntu package
[14:40] <xnox> dobey: why was is set to committed then (!) i did check all of them.....
[14:40] <slangasek> ftpshs> fails to puild hrom source?
[14:40] <cjwatson> unity-asset-pool (from unity-asset-pool) is seeded in:
[14:40] <cjwatson>   edubuntu: dvd
[14:40] <cjwatson>   ubuntu-gnome: daily-live
[14:40] <cjwatson>   ubuntu: daily-live, daily-preinstalled
[14:40] <cjwatson>   ubuntukylin: daily-live
[14:40] <cjwatson>   ubuntustudio: dvd
[14:40] <dobey> xnox: i have no idea. that's why i'm pinging didrocks (and presumably why it somehow managed to get dumped on me this lovely morning)
[14:41] <cjwatson> and can we get kdenetwork fixed while we're here, please?
[14:41] <smartboyhw> Why does ubuntustudio contain unity-assets-pool?
[14:41] <smartboyhw> :O
[14:41] <cjwatson> no idea
[14:41] <smartboyhw> ......
[14:41] <dobey> smartboyhw: or ubuntu-gnome or edubuntu?
[14:41] <cjwatson> not the time for such questions
[14:41] <dobey> yeah
[14:42] <smartboyhw> dobey: Edubuntu does make sense. US doesn't.
[14:42] <cjwatson> Whatever
[14:42] <cjwatson> Now is not the time
[14:42] <dobey> cjwatson: who would be best to fix kdenetwork? ScottK?
[14:42] <xnox> well kdenetwork i can even upload.
[14:42]  * xnox looks.
[14:42] <ScottK> What's the issue?
[14:42] <dobey> xnox: thanks
[14:43] <cjwatson> ScottK: Presence of a skype icon which has attack lawyers after it
[14:43] <cjwatson> bug 1163504
[14:43] <ScottK> Ah.
[14:43] <ubot2> Launchpad bug 1163504 in kdenetwork (Ubuntu Raring) "Trademarked assets" [Undecided,New] https://launchpad.net/bugs/1163504
[14:43] <ScottK> Yeah, should probably fix that.
[14:43] <Daviey> cjwatson: sure
[14:44] <cjwatson> kopete isn't on any images
[14:44] <cjwatson> So we could get away with a day-0 SRU for that
[14:44] <xnox> dobey: didrocks: why kdenetwork needs fixing? it has code to link/use skype or something for kopete. But it's just kopete which has the icon.
[14:44] <ScottK> cjwatson: Except then the file is in the release pool for the life of the release.
[14:45] <ScottK> We plan a Kubuntu respin anyway.
[14:45] <cjwatson> True.
[14:45] <didrocks> dobey: xnox: sorry, in another discussion. I'm only looking at unity-asset-pool shortly
[14:45] <cjwatson> didrocks: This is critical - I hope the other discussion can be suspended for a bit
[14:45] <dobey> xnox: i don't know. cjwatson asked if it should be kdenetwork instead of kopete. if it's kopete then it's kopete :)
[14:45] <cjwatson> kopete is from the kdenetwork source package
[14:46] <dobey> ah ok. xnox ^^
[14:47] <jokerdino> hey guys, is the archive frozen yet? i would like some advice on how to get a couple of fixes in. separate SRU requests or a new bug-fix only version sync request?
[14:47] <cjwatson> SRU unless it's critical for images
[14:48] <jokerdino> (with re: to unity-tweak-tool)
[14:48] <jokerdino> that was a darn lag. sorry.
[14:48] <stgraber> unity-tweak-tool isn't seeded, so just upload
[14:49] <jokerdino> so, i can get a upload later today?
[14:49] <didrocks> cjwatson: argh, it seems the fix wasn't released :/
[14:50] <stgraber> cjwatson,infinity: do we have a deadline for unseeded stuff?
[14:50] <xnox> ScottK: Riddell: so kopete has protocol to connect to skype and the trademarked & copyright assets for everything: logo, status, etc.
[14:50] <Riddell> nothing in kdenetwork, it's in oxygen-icons
[14:50] <jokerdino> i think i'll bug you later when i pick the fixes. thanks!
[14:50] <xnox> ScottK: Riddell: remove all of those icons and see what happens?
[14:50] <cjwatson> stgraber: probably tomorrow sometime - everything's settled, we shouldn't need to stress about it
[14:50] <xnox> Riddell: there clerly images in kdenetwork package.
[14:50] <infinity> stgraber: Tomorrow morningish.
[14:50] <xnox> Riddell: kdenetwork-4.10.2/kopete/protocols/skype/icons
[14:50] <infinity> stgraber: If it doesn't build in time and make it, we can just dump it to s-series.
[14:50] <Riddell> xnox: where? I see only ones in oxygen-icon-theme
[14:51] <slangasek> jokerdino: this isn't the place to ask for upload sponsorship, if that's what you mean.  Uploads to unseeded packages are still allowed at this point, but not guaranteed to make it into the release - you can still upload but it may wind up having to go through the SRU process
[14:51] <xnox> Riddell: kdenetwork-4.10.2/kopete/protocols/skype/icons .....
[14:51] <didrocks> cjwatson: is there a respin needed?
[14:51] <cjwatson> didrocks: Yes
[14:51] <stgraber> jokerdino: so based on the above, you should be fine if you upload today
[14:51] <didrocks> cjwatson: if so, I can fix that quickly
[14:51] <Riddell> xnox: ooh sneaky
[14:52] <xnox> Riddell: unless they are not installed...... let me check.
[14:52] <cjwatson> didrocks: We can't say to the lawyer's "sorry, we can't fix 12.10 images now, but we'll fix it in 13.04" and then not fix it in 13.04
[14:52] <cjwatson> *lawyers    # argh what's wrong with my typing
[14:52] <didrocks> cjwatson: let me do a quick upload
[14:52] <cjwatson> didrocks: Thanks
[14:52] <cjwatson> Looks like just that one rev since the last autolanding
[14:52] <didrocks> cjwatson: sorry, I'm not anymore the one looking that stuff getting merged are released, but well :)
[14:52] <didrocks> cjwatson: yep
[14:53] <Riddell> xnox: they are indeed
[14:53] <cjwatson> didrocks: Yep, not looking to allocate blame, but it needs to get fixed
[14:53] <jokerdino> slangasek, heh no. i wasnt sure about last day procedures with the archive. i was thinking SRU requests go through archive admins. thanks regardless!
[14:53] <xnox> Riddell: I'm looking at packaging. Does oxygen-icon-theme provide fallbacks? are those trademarked assets as well?
[14:54] <xnox> Riddell: I'd like to rebuild kdenetwork without skype plugin activated such that we don't ship something that tries to load skype plugin and crashes due to missing icons.
[14:54] <Riddell> xnox: /usr/share/icons/oxygen/*/actions/im-skype.png and /usr/share/icons/hicolor/*/actions/im-skype.png could well be considered to be the trademark
[14:54]  * xnox looks at oxygen.
[14:55] <didrocks> cjwatson: doing a quickly daily, sync in ~20 minutes I guess
[14:55] <xnox> Riddell: those are shipped from the kopete bin package, by kdenetwork package?!
[14:55] <pgraner> cjohnston, infinity: just got this report on server cd's https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1107686
[14:55] <ubot2> Launchpad bug 1107686 in isc-dhcp (Ubuntu) "dhcpd: Open a socket for LPF: Permission denied" [Undecided,Fix released]
[14:55] <Riddell> xnox: those are from oxygen-icon-theme
[14:55] <cjohnston> I'm guessing cjwatson ^
[14:56] <cjwatson> stgraber: ^-
[14:56] <stgraber> pgraner: how did that get linked to raring server? that bug report is about a regression in a quantal SRU
[14:56] <stgraber> (which I fixed yesterday and is now in quantal-updates)
[14:57] <pgraner> stgraber, matsubara pinged me since he is doing the maas testing
[14:57] <pgraner> stgraber, he says its in raring as well
[14:57] <dobey> Riddell: /usr/share/kde4/apps/kopete/icons/oxygen/128x128/apps/skype_protocol.png is in kopete - http://packages.ubuntu.com/raring/all/kopete/filelist
[14:57] <stgraber> pgraner: hmm, ok, that's pretty surprising considering I copied the fix from raring... so must be something else
[14:57] <Riddell> dobey: yep
[14:58] <stgraber> pgraner: anyway, is that on some lab machines? (can I see it?)
[14:58] <pgraner> stgraber, ok I asked him to join here so you can talk to him, and yes it should be on a lab boxen
[14:59] <matsubara> stgraber, hi there. pgraner told me you have some questions about https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1107686
[14:59] <ubot2> Launchpad bug 1107686 in isc-dhcp (Ubuntu) "dhcpd: Open a socket for LPF: Permission denied" [Undecided,Fix released]
[14:59] <stgraber> matsubara: right. That specific bug was a regression in quantal, we've had the fix for that in raring for months, so it's very unlikely you're seeing the same issue.
[14:59] <stgraber> matsubara: any chance I can have access to your test machine to see exactly what's going on?
[15:00] <matsubara> stgraber, I see the same error in the log and when I put the workaround suggested in place, the dhcpd server starts normally
[15:00] <stgraber> matsubara: what workaround?
[15:00] <matsubara> stgraber, yes, sure. do you have access to the QA VPN?
[15:00] <cjwatson> Daviey: ah, excellent, you went ahead and removed it, thanks
[15:00] <stgraber> matsubara: yep, I've got VPN access to the QA lab
[15:00] <matsubara> network packet packet,\n network packet raw
[15:01] <matsubara> stgraber, ok. I'll pm you the details
[15:02] <cjwatson> didrocks: Great, thanks
[15:02] <Daviey> cjwatson: thanks for noticing it, sad we didn't notice it in quantal
[15:02] <didrocks> cjwatson: yw, sorry I didn't notice it beforehand :)
[15:03] <cjwatson> Daviey: Yeah, was trying to make sure the ubuntu-archive request queue was clean for release
[15:03] <Daviey> perfect, thanks!
[15:03] <cjwatson> (We now have just three long-term issues that aren't release-specific)
[15:04] <xnox> Riddell: proposing http://paste.ubuntu.com/5598572/ will test build and test the package in the moment. Looking at the oxygen icons now.
[15:04] <Riddell> xnox: I'd recommend setting WITH_skype=false too
[15:05] <xnox> Riddell: for CMake config. Ok. let me try.
[15:06] <xnox> Riddell: the cdbs combinded dh style packaging is ugly.
[15:07] <xnox> http://paste.ubuntu.com/5598576/
[15:07] <Riddell> xnox: looking good
[15:09] <stgraber> cjwatson, pgraner: turns out the test was on quantal so they hit the SRU regression which I fixed yesterday and landed in -updates this morning. A re-run confirmed that the issue is no longer present.
[15:09] <cjwatson> Oh good
[15:10] <pgraner> stgraber, ack great
[15:10] <pgraner> stgraber, thanks
[15:10] <Riddell> is it really ok to have the skype icon in the source package?
[15:14] <cjwatson> Good question
[15:14] <cjwatson> It might be safer to redo the orig
[15:17] <cjwatson> At least to remove the icon (I don't think it's necessary to purge all traces of the word "skype", since AFAIK we haven't been asked to)
[15:17] <xnox> Riddell: i'll repack to remove trademarked assets from kdenetwork and oxygen.
[15:17] <Riddell> "assets" you sound like a lawyer :)
[15:17] <bdmurray> what is the release process wiki page?
[15:19] <Laney> do you need to disable the skype plugin completely?
[15:19] <cjwatson> AFAIK only the icon needs to go away
[15:19] <xnox> Riddell: hang out to much with designers. Apperantly "photoshop" produces "assets".
[15:19] <Laney> that's how I see it too
[15:19] <cjwatson> if there's a suitable replacement icon then it would be preferable to use that
[15:20] <xnox> Laney: sure. but i don't want to ship kopete which will try to load skype plugin and fail due to missing icons.
[15:20] <cjwatson> (we can probably check that if you want)
[15:20] <cjwatson> bdmurray: https://wiki.ubuntu.com/ReleaseProcess
[15:20] <Laney> right ...
[15:20] <xnox> it uses the xdg lookup.... but.
[15:21] <xnox> Laney: we can always sru kopete with enabled skype plugin and debranded or whatever.
[15:22] <cjwatson> ubuntukylin-default-settings needs a slideshow fix too (skype icon)
[15:22]  * cjwatson looks at that
[15:23] <dobey> xnox: have you verified it will fail without those icons?
[15:23] <xnox> dobey: no, somebody can do that in the mean time?!
[15:24] <cjwatson> Kylin doesn't actually *use* those icons, but it ships them
[15:24] <xnox> Riddell: ^ ?
[15:24] <dobey> xnox: i doubt it will fail
[15:24] <dobey> but it would be good if someone could test it real quick
[15:24]  * xnox doesn't think that offering skype plugin with missing icons is good. One of the "Skype" plugin features is mozilla plugin call to button.
[15:24] <dobey> hopefully they don't get compiled into the binary so just rm the icons will work to remove them
[15:24] <xnox> I'd like someone test that as well, if you are going with "remove icons only"
[15:25] <xnox> dobey: there are alot of compiled moc/ui objects....
[15:25] <xnox> (not sure if those embdeb icons or not)
[15:25] <cjwatson> Shouldn't
[15:25] <xnox> ack.
[15:25] <dobey> depends on what the rc files do
[15:26] <dobey> if rc files include reference to the png files, they'll get pulled into the binary as well
[15:26] <xnox> broken kopete -> breaking firefox sounds like a risky possibility. Hence disable full plugin + maybe sru it back in later after testing and/or replaced artwork.
[15:29] <Riddell> xnox: how could it break firefox?
[15:30] <xnox> Riddell: by crashing a page with a phone number that is rendered into a skype callto button.
[15:30] <xnox> Riddell: kopete builds that as well....
[15:30] <dobey> i doubt it will crash
[15:31] <Laney> you could check ...
[15:31] <Riddell> I've never heard of things crashing ust from missing artwork
[15:31] <Laney> disabling it seems like a sledgehammer approach
[15:31] <Riddell> I'll try it out
[15:31]  * xnox finished the kdenetwork build with skype disabled. testing now.
[15:37]  * xnox kdenetwork works & kopete works.
[15:38] <cjwatson> Should we pull in the new casper to -updates for this respin?
[15:38] <cjwatson> How well is it tested?
[15:44] <stgraber> cjwatson: the virtio swap bit I've used to debug another issue so I know it works. The shutdown I only did a quick test yesterday in a UEFI VM, doing the same in a BIOS VM now to confirm
[15:44] <cjwatson> Yeah, I couldn't even get plymouth to show on shutdown in kvm so I'm no help
[15:47] <stgraber> ah right, just figured out why everything's slow on the machine, I'm building a kernel in the background with -j5, that explains it!
[15:48] <Riddell> xnox: kopete works ok with skype with no icons
[15:50] <xnox> Riddell: and firefox as well? callto button?!
[15:50] <Riddell> xnox: that I've no idea what it is or how it work
[15:51] <xnox> Riddell: login into skype, enable account in kopete, start firefox, check that mozilla callto plugin is loaded, navigate any pages which have phone numbers
[15:52] <xnox> and if detected they should turn into call icon with the skype green phone thing, upon clicking which a call should initiate
[15:52] <xnox> a call in kopete.
[15:52] <Riddell> xnox: do I need to install this callto plugin?
[15:52] <xnox> Riddell: it seems to come inside kopete package....
[15:52] <xnox> doesn't it?
[15:53] <Riddell> oh nifty
[15:54] <stgraber> cjwatson: VM with broken text boot/shutdown doesn't look worse with the new casper than it did with the old one. I've got another VM using vmvga which does give me a working plymouth, let's see what that one does.
[15:55] <xnox> Riddell: hence my concerns.....
[15:56] <stgraber> cjwatson: I see the message and pressing enter works (kvm with vmvga driver)
[15:56] <cjwatson> Promising
[15:56] <stgraber> yeah, I can't confirm whether we fixed the bug or not but at least it doesn't look like it's any worse than it was
[15:58] <Riddell> xnox: doesn't seem to work with the current kopete package
[15:59] <Riddell> xnox: I install kopete package, check it's listed in about:plugins  go to http://davidwalsh.name/demo/phone-link-protocol.php to test and link doesn't work "the protocol (tel) isn't associated with any program."
[16:00] <xnox> Riddell: with and without icons?! =)
[16:00] <xnox> Riddell: skype should be running....
[16:00] <xnox> (logged in etc.)
[16:00] <Laney> since xnox has it working, it sounds like it would be easier for him to check this ...
[16:01] <jbicha> xnox: what are we going to do for bug 1164592?
[16:01] <ubot2> Launchpad bug 1164592 in ubiquity (Ubuntu) "Ubiquity freezes in Install Alongside screen" [Medium,Confirmed] https://launchpad.net/bugs/1164592
[16:01] <Riddell> xnox: yep
[16:01] <xnox> Laney: what do you mean "working" ?
[16:01] <Laney> the call thing?
[16:02] <Laney> at least you're giving instructions like you have it working fo ryou
[16:02] <xnox> Laney: I know how it's suppose to work, but I haven't used it myself in raring yet. And my machine I'm on at the moment cannot do skype.
[16:04] <xnox> I have package that is repackaged to remove skype icons, and disable skype plugins and not install them.
[16:04] <xnox> It works as expected.
[16:04] <xnox> the final debdiff is: http://paste.ubuntu.com/5598697/
[16:04] <xnox> I am tempted to upload that.
[16:04] <xnox> The alternative is to still ship all plugins and just have the icons removed. But that needs another build on my end.
[16:05] <xnox> Let me dput this version, and I can do another one for icons only and then it's up to release team to decide what to take.
[16:05] <Riddell> xnox: I'm not fussed but have a slight preference for only removing the icons and not the kopete plugin
[16:05]  * Laney too
[16:05] <xnox> ScottK: ^?
[16:05] <cjwatson> I share that preference
[16:05]  * ScottK too
[16:06] <stgraber> yeah, I don't think we want a last minute feature change, dropping/replacing the icons should be enough to fix the bug
[16:07] <xnox> purging all skype icons? (e.g. even the like skype human contact & status icons)
[16:08] <Laney> what was asked for?
[16:09] <Riddell> xnox: they look a lot like straight copies from skype so best to yes
[16:09] <cjwatson> Apparently the one they really care about is the one that was overriding their icon in their new skype package
[16:09] <cjwatson> So an actual functional breakage - that was unity-asset-pool
[16:09] <cjwatson> For the others, we should still be avoiding shipping trademarked things where we don't have permission
[16:09] <cjwatson> AFAIK it is just the logo
[16:10] <cjwatson> Or images that incorporate the logo
[16:10] <xnox> do we know if the trademarked the tripple circle status icon? (which is same outline like the (S) logo)
[16:10] <xnox> s/the/they/
[16:11] <xnox> the above kdenetwork is with disabling plugin.
[16:11] <cjwatson> I do not know and the guidelines do not appear to say
[16:11] <xnox> cjwatson: ^ reject, I guess for now.
[16:11] <xnox> well my trademark knoweledge slightly reminds that anything that reasonably can associate / make one believe it's trademark....
[16:12] <xnox> none the less, I belive those icons are violating copyright and are not suitable for main.
[16:13] <cjwatson> I would probably err on the side of removing any icons you're unsure about
[16:18] <Riddell> xnox: kopete mozilla plugin seems broken generally, not much to break more
[16:19] <cjwatson> rejecting the earlier kdenetwork at least for now
[16:24]  * cjwatson copies casper to raring-updates
[16:26] <xnox> Riddell: oxygen-icons shouldn't be an xz, since most of icons are compressed with svgz, thus exploading the archive to be bigger than it should have been.
[16:26] <xnox> Riddell: for future =)
[16:28] <cjwatson> OK, so I'm fine with that kdenetwork upload.  Anyone else want to chime in before I accept it?
[16:28] <Riddell> xnox: I'll pass on your wisdom to upstream but he does work for the same company as you so he might pay more attention to you directly :)
[16:28] <Riddell> cjwatson: good with me
[16:28] <Chipaca> xnox: if the plugin needs skype to be installed in order to work, can't it use the real skype icon?
[16:28]  * Chipaca carries on reading
[16:28] <xnox> I dunno
[16:28] <xnox> Chipaca: but good point.
[16:29] <Riddell> ktp-common-internals also has a skype icon
[16:29] <cjwatson> It's not clear, but we can always put things back in an SRU if we get clearance
[16:29] <cjwatson> From what David Pitkin told me, I'm not stressed at this point about grepping the archive for everything
[16:29] <cjwatson> Since the most pressing concern is how it breaks Skype 4.2
[16:30] <Laney> LGTM apart from the changelog being wrong
[16:30] <xnox> Laney: which changelog? mine?
[16:30] <cjwatson> I don't mind if people want to clean up universe further but it's not immediately critical
[16:30] <xnox> Laney: yeah.
[16:30] <cjwatson> xnox: Oh yeah, s/plugin/icons/
[16:31] <infinity> Riddell: If you want to clean up kt-common-internals, be my guest, kdenetwork will be building for 4h anyway. :/
[16:31] <cjwatson> changelog ... too late :)
[16:31] <Laney> unacceptable!
[16:32] <shibata> Hi release team. I encountered a crash of usb-creator-gtk on 13.04, bug 1068473.
[16:32] <ubot2> Launchpad bug 1068473 in usb-creator (Ubuntu) "Crash when trying to create USB startup disk." [Undecided,Confirmed] https://launchpad.net/bugs/1068473
[16:33] <cjwatson> I think our position on usb-creator is mainly "Er, yeah, sorry, it kind of sucks and we haven't had time to sort it out, but for most purposes you can just use dd"
[16:35] <shibata> cjwatson: I see. Thank you.
[16:40] <cjwatson> Just waiting for casper to publish to -updates before starting respins
[16:40] <cjwatson> Anything else, better shout now :-P
[16:41] <slangasek> can I have libpony on the CD
[16:41] <infinity> slangasek: No.
[16:41] <cjwatson> No, because the images don't fit on CDs any more :-)
[16:41] <infinity> slangasek: Nor can you get a lollipop.
[16:43] <Laney> what's going to be respinned?
[16:43] <infinity> gnome, ubuntu, kubuntu, edubuntu...
[16:43] <cjwatson> weidergespunnen
[16:43] <cjwatson> er, wieder
[16:44] <Laney> like a record baby
[16:44] <stgraber> Laney: edubuntu, ubuntu-gnome, ubuntu, ubuntukylin, ubuntustudio and kubuntu
[16:44] <cjwatson> Yeah, WHS
[16:44] <Laney> ah, who cares about that stuff
[16:44]  * Laney should have checked seeded-in-ubuntu casper
[16:44] <cjwatson> I dunno why all of those have unity-asset-pool, but they do, and we have to respin either way (either to remove the files or remove the package)
[16:45] <cjwatson> Laney: I put casper into -updates specifically to avoid everything it touches
[16:45] <Laney> er, uap
[16:45] <cjwatson> Yeah
[16:45] <Laney> I don't see kubuntu there?
[16:46] <cjwatson> In the case of ubuntu-gnome, it's shotwell -> account-plugin-facebook -> u-a-p
[16:46] <cjwatson> Kubuntu is there for a different reason
[16:46] <cjwatson> It wanted a couple of ubiquity changes anyway
[16:46] <infinity> Laney: kdenetwork for kubuntu (and one or two others)
[16:46] <Laney> but that's later for kdenetwork, yes?
[16:46]  * Laney nods
[16:46] <jbicha> yeah I think we wish we didn't have unity-asset-pool included ;)
[16:46] <cjwatson> Indeed
[16:47] <Laney> jbicha: It's an asset to you
[16:47] <JackYu> cjwatson, when will the new iso of ubuntukylin ready?
[16:47] <cjwatson> Need to wait for this publisher run to finish (a few more minutes) and then kick everything off; probably a couple of hours
[16:48]  * skellat is downloading the latest branch of xubuntu-artwork really fast just to do a fast double-check for The Forbidden Trademarked Asset
[16:48] <cjwatson> Changes are very minor so if you've already done full testing I think a revised smoke test should be fine
[16:48] <JackYu> cjwatson, ok, so we will test it tomorrow (beijing time:) ).
[16:48] <cjwatson> What's that in UTC?
[16:49] <JackYu> +8
[16:49] <cjwatson> I mean, depending on what you mean by tomorrow that might be after release
[16:49] <cjwatson> But you're after midnight right now so you mean in about eight hours or so?
[16:50] <JackYu> oh, yes:)
[16:50] <cjwatson> OK, that'll be fine, thanks
[16:51] <Laney> huge oxygen-icons orig is huge
[16:51] <Riddell> size is everything
[16:51] <stgraber> should we mark the world as rebuilding on the tracker or do we want to still let people report results on the current ones?
[16:51] <xnox> Laney: hence my complained. It's an xz tarball of gz compressed icons. Thus it explodes in size for no gain.
[16:52] <Laney> file a bug :-)
[16:52] <xnox> Laney: to me that orig src is not actually orig, as icons are "pre-processed".
[16:52] <xnox> Laney: I will in debian as a serious one.
[16:52] <xnox> Laney: after may the 7th.
[16:53] <cjwatson> stgraber: Hmm.  Probably the latter, it'll still be a little while
[16:53] <Laney> o-i lgtm
[16:54] <cjwatson> jamespage: your juju-core version number is b i z a r r e
[16:55] <jamespage> cjwatson, tell me about it
[16:56] <ScottK> cjwatson: I think it'd be better to just put it in S next week and backport anway.
[16:56] <infinity> jamespage: We just did.
[16:56] <infinity> jamespage: Why does the upstream version have a -1 at the end of it?
[16:56] <cjwatson> ScottK: Yeah, I'm trying to avoid having an opinion on that since I haven't looked :)
[16:56] <ScottK> (said so in the FFe bug too)
[16:56] <infinity> Don't technically need an FFe for new unseeded stuff...
[16:57] <Laney> really?
[16:57] <Laney> or does F = Final?
[16:57] <Daviey> infinity: erm, that isn't how it used to be
[16:57] <ScottK> infinity: New does.
[16:57] <infinity> It's no more a new feature than any other unseeded things we've synced from Debian in the last week.
[16:57] <jamespage> it has a -1 because the juju team had to recut the release tarball as it had cruft in it
[16:57] <infinity> Did those all have bugs?
[16:57] <infinity> jamespage: That's what dots are for...
[16:57] <Daviey> The primary reason for an FFe on unseeded stuff was to be a vanguard to Archive Admins.
[16:58] <ScottK> infinity: Except you need an archive admin to New it and we're all allegedly busy with other stuff now.
[16:58] <infinity> ScottK: Sure, but added process doesn't help that, we can all just say "no, not enough time".
[16:58] <ScottK> My usual answer (at least when it's not release week) is to say go ahead if you can find an AA with time.
[16:58] <Daviey> I don't think it's an unreasonable process TBH.
[16:58] <infinity> *shrug*
[16:59] <infinity> I think it's pointless process.
[16:59] <ScottK> It is a bit different now that we have more AAs and most of the release team are also AA's but meh.
[16:59] <infinity> FFEs are about reviewing the new features and changes.  "New package" isn't a feature changed in a package, it's just, well, a new package, which we already know how to deal with.
[16:59] <infinity> And we know how to not deal with it too.
[17:00] <ScottK> Maybe, but that's not the way we've done it for as long as I can remember.
[17:00] <infinity> Just seems to be overloading it a bit, and adding process to an already annoying process (new review).
[17:00] <Daviey> infinity: this one does potentially introduce risk with a non-seeded, but important feature package
[17:00] <infinity> Daviey: The real risk was in the juju upload we reviewed and accepted earlier.
[17:00] <ScottK> Daviey: All the more reason to backport it next week.
[17:00] <infinity> Daviey: (ie: the one that switched it to using alternatives).
[17:01] <cjwatson> Starting Ubuntu desktop respins
[17:01] <infinity> There's no "danger" in accepting an alternative implementation.
[17:01] <infinity> That's like saying every MTA is a "danger" to postfix.
[17:01] <Daviey> true
[17:02] <skellat> Alrighty, it looks like xubuntu-artwork is clean of The Forbidden Trademarked Asset
[17:02]  * ScottK protectively cuddles postfix and summons lamont.
[17:02] <infinity> But, I'm down with saying it's silly to jam it in late when we'll end up later with people claiming it needs to be heavily SRUed when all the bugs are found.
[17:02] <infinity> *cough* maas in precise *cough*
[17:02] <cjwatson> skellat: thanks
[17:02] <ScottK> infinity: Yep.
[17:03] <Daviey> To be clear, i couldn't give a hoot if this gets in or not.  I just know that a few people have worked pretty hard to try and get it in.  I don't mind spendig some time trying to help make that happen.
[17:03] <Daviey> I think they have learned to get it in sooner next cycle.
[17:03] <infinity> Daviey: Sure, they worked hard, they just worked hard to get it in at the wrong time.
[17:03] <ScottK> If we don't accept it until next week, it will be in sooner next cycle.
[17:03] <infinity> Daviey: Such is life sometimes, not everyone makes every milestone.
[17:03] <infinity> Daviey: Getting it in first thing next week means they have six months to make it not crap. ;)
[17:04] <Laney> Backports is super easy for new packages too.
[17:04] <Daviey> infinity: your confidence is high.
[17:04] <ScottK> I sense consensus emerging on the release team.
[17:08] <lamont> ScottK: maybe  we should throw postfix at infinity and see if it sticks :D
[17:08] <lamont> (hi infinity)
[17:08] <cjwatson> Yeah, no matter how hard you work, landing an entirely new package a day before release is something you should expect to be questioned pretty heavily and possibly denied.
[17:09] <Daviey> Oh, there has been significant questioning for the last few weeks.
[17:09]  * ScottK just marked it wontfix based on the discussion here.
[17:10] <infinity> lamont: I don't want your filthy postfix.
[17:10] <apw> jamespage, can we assume that the python juju version will never rev into the same version space as the go juju version
[17:10]  * infinity cuddles exim.
[17:10] <cjwatson> The questioning I was referring to is the questioning happening now, not anything that happened before upload :-)
[17:10] <Daviey> ScottK: I disagree that backporting it next week makes any difference.
[17:10] <Daviey> apw: I checked that.. and it is safe to assume.
[17:10] <ScottK> Daviey: Sure it does.  If the backport goes badly you can easily update it or even remove it.
[17:10] <cjwatson> And I'm afraid I agree.  It's too late for a new project.  A backport has more time to deal with stupid build problems and the like.
[17:11] <infinity> Daviey: It's a huge difference, since the backport can be revved with zero effort.
[17:11] <ScottK> If it goes into the release pocket, you're stuck with it for the duration.
[17:13] <Daviey> infinity: 'zero effort' ?
[17:13] <infinity> Yes.
[17:13] <cjwatson> In fact, if it goes well in -backports, there's no real reason we couldn't put it in -updates to give it wider visibility.
[17:13] <infinity> You're familiar with the backports pocket, right?
[17:14] <Daviey> naturally
[17:14] <cjwatson> But the first exposure of something like this to the archive shouldn't be in the release pocket a day before release.
[17:14] <Daviey> But zero effort implies throwing any crap in there.
[17:14] <infinity> ...
[17:14] <infinity> You'd rather throw any crap into the release pocket? :)
[17:15] <lamont> infinity: ....
[17:16] <Daviey> infinity: No, which is why i declaimed my point with the package being of sound quality :P
[17:16] <ScottK> Since it's been tested on raring, the additional effort to backport it once it's in "S" is negligible.
[17:17] <Riddell> today's kubuntu images still have the "this is a pre-release" warning on ubiquity
[17:17] <xnox> Riddell: you should have used a plus in ktp upload, as in "0.6.1+dfsg1-0ubuntu1" but it's just ok.... passes a point.point.point.point release test.
[17:18] <cjwatson> Fortunately we have an opportunity to fix that :-)
[17:18] <cjwatson> What's the exact string so I can grep?
[17:18] <Riddell> "This is a pre-release of the Kubuntu live CD installer."
[17:19] <cjwatson> Ah yes
[17:19] <Riddell> isn't that turned off by something on the CD?
[17:19] <cjwatson> It's in ubiquity
[17:19] <cjwatson> Looks like only the KDE frontend is affected
[17:20] <cjwatson> So I'll upload a fix in a moment
[17:20] <cjwatson> Is there a bug number/
[17:20] <cjwatson> ?
[17:21] <cjwatson> Looks like no
[17:23] <Riddell> cjwatson: I'll report one
[17:23] <Riddell> bug 1172059 verified as good
[17:23] <ubot2> Launchpad bug 1172059 in ubiquity (Ubuntu Raring) "kubuntu ubiquity encryption doesn't check password" [High,In progress] https://launchpad.net/bugs/1172059
[17:24] <cjwatson> Riddell: don't bother, already building a package
[17:24] <Riddell> ok
[17:31] <apw> jamespage, shouldn't this jujud have a manpage ...
[17:32]  * Riddell uploads muon so raring->s version upgrades will work
[17:38] <Riddell> cjwatson: ubiquity upload looks good, shall I accept?
[17:39] <ScottK> Riddell: I already did
[17:39] <Riddell> lovely
[17:40] <ScottK> So how come that variable only affects the Qt front end?  How is it done for Ubuntu?
[17:40] <ScottK> Seems like a deeper disconnect we ought to fix while it's fresh.
[17:40] <Riddell> it used to be the same thing I'm sure
[17:41] <cjwatson> The GTK frontend lost the alpha warning in some redesign or other
[17:44] <ScottK> Riddell: Should we just lose it too then?
[17:44] <ScottK> One less thing to go wrong.
[17:44] <Riddell> ScottK: there's a good argument for that yes
[17:44] <ScottK> So all we need to do is not turn it back on ....
[17:45] <cjwatson> We can delete that code for S if that's what you'd prefer, sure
[17:45] <ScottK> May as well.
[17:46] <cjwatson> I think the need for it is rather less than when it was first introduced anyway
[17:52] <ScottK> Riddell: What happened to muon?
[17:57] <balloons> forgive me if this has been asked, i dn't see it in the backscroll. Do we plan on having a "Ubuntu Project Contributors"section in the release notes again?
[18:03] <balloons> sounds like bkrenesa is going to do this?
[18:07] <bkerensa> balloons: :)
[18:11] <pgraner> balloons, yep, I have bkerensa the link so he knows where to put them
[18:11] <bkerensa> ;)
[18:12] <Riddell> ScottK: it's compiling away
[18:13]  * Riddell out for a couple of hours
[18:32] <jamespage> apw, undoubtedly so
[18:32] <jamespage> apw, guess I get time to fixup lint now :-)
[18:34] <cjwatson> I'm preemptively prepublishing the desktop images above so that we can get them onto cloudfront/mirrors/etc.
[18:34] <cjwatson> dinner
[18:37] <Daviey> ^ I wanted a bug on the iptables decency introduction
[18:39] <ScottK> Nothing outside Kubuntu, so I'm unblocking it for release.
[18:48] <ScottK> Daviey: Is that for release or SRU?
[18:50] <Daviey> nova and cinder should be release.  maas should be sru
[18:52] <ScottK> So you're going to respin server?
[18:52] <Daviey> ScottK: no
[18:52] <ScottK> Ah, I confused pacackage set with seed there
[19:17] <dobey> infinity: hey, i got bumrushed to poke at a critical issue with skype icons this morning, and forgot to ping you re: rhythmbox-ubuntuone. can you still look at those SRU uploads today? thanks.
[19:52] <ScottK> infinity/cjwatson: Any reason not to go ahead and copy ubiquity to updates?
[19:53] <stgraber> I think they're all out for dinner
[19:54] <stgraber> but besides that (as being the reason why nobody did it already), I can't see any reason not to copy it
[19:55] <ScottK> We're still waiting for kdenetwork on armhf anyway.
[19:55] <ScottK> Let me see how long that's likely to be ...
[19:56] <ScottK> Ah.  Finished.
[19:57] <stgraber> I'd just go ahead with copying to updates or pushing straight to the release pocket for the various bits you need (depending on whether you're the only one to ship those or not) and once everything is published let me know and I'll kick a rebuild for you (assuming the others aren't back by then)
[19:59] <ScottK> We don't want ubiquity in the release pocket because it's there for Kubuntu only.
[19:59] <ScottK> Just copied to updates.
[19:59] <stgraber> right, that one goes to updates, the other bits can probably go to release
[19:59] <ScottK> I suspect that's the first use of the 'sru-release' script for raring.
[19:59] <ScottK> Yes.
[19:59] <ScottK> There's already and unblock for kdenetwrok.
[20:00] <ScottK> Should be good after the next publisher run finishes.
[20:01] <ScottK> Riddell: Do you know of anything else we're waiting for?
[20:13] <ScottK> stgraber: I don't know if you fixed something or something magical happened, but I can mark for rebuild now.
[20:16] <stgraber> ScottK: didn't change anything, so I guess you just didn't hit the same weird bug you hit last time
[20:19] <xnox> stgraber: ScottK: yeah, they are still out for dinner. I'm heading home now. copy to -updates and respin kubuntu with -updates if all the bits landed seems to me like the only next step.
[20:24] <xnox> calling it a night =) see you tomorrow.
[20:48] <Daviey> ScottK: Are you pushing hard against this being NEW reviewed now, overriding my initial assessment - or was your Wont Fix your preference ?
[20:52] <slangasek> FWIW, I've talked with Daviey about juju-core (both today, and in the lead-up to this FFe); if we think we would just be adding this in via backports+updates later, I don't think there's a strong justification, release-wise, for not letting it into the release pocket today
[20:53] <ScottK> slangasek: Everyone (except Daviey) that was here earlier on the release team saw it differently.
[20:53] <Daviey> Proving it's of suitable quality.
[20:53] <Daviey> providing*
[20:54] <ScottK> There is zero difference to the user either way.
[20:54] <slangasek> ScottK: yep, I saw
[20:54] <Daviey> ScottK: to be fair, infinity seemed quite moderate about it initially
[20:54] <ScottK> Daviey: True, but after discussion seemed to view it reasonably strongly.
[20:54] <Daviey> ScottK: if there is zero difference, do you object to it going in now then?
[20:55] <slangasek> ScottK: the fact that there's zero difference to the user is exactly why I don't see that it's warranted to *not* allow it in the release
[20:56] <ScottK> slangasek: The complexity of supporting it post release for us is the difference.
[20:56] <ScottK> See the fun we're having over MaaS in precise now (it was also slammed into the archive on release week).
[20:57] <ScottK> In a nutshell, I guess the difference is that we don't have to promise zero regressions next week.
[20:57] <slangasek> is that really because of the late landing in precise, as opposed to being a matter of the code having evolved since then?
[20:58] <ScottK> It was trouble on contact.
[20:58] <ScottK> I'm sure it's some of both though.
[20:58] <Daviey> ScottK: Erm, i disagree with you stating it was introduced in release week
[20:58] <Daviey> ScottK: https://launchpad.net/ubuntu/+source/maas/0.1~bzr146+dfsg-0ubuntu1
[20:58] <slangasek> ah, but I would much rather hold the juju team to the "zero regressions" rule
[20:59] <Daviey> And to be clear, this is on a whole different scale of less complexity
[20:59] <ScottK> You're correct.
[21:00] <ScottK> There were however significant changes release week (which must be what I remember) https://launchpad.net/ubuntu/precise/+source/maas/0.1+bzr462+dfsg-0ubuntu1
[21:00] <stgraber> I really don't see why the JuJu folks want their package in the 13.04 release pocket. If it was my package, I'd actually be very happy to have it just in raring-backports as it'd let me do full version updates post-release without having to go through the SRU process with the exact same installation/discoverability for my users
[21:00] <ScottK> slangasek: It's still a management burden for the SRU team.
[21:00] <Daviey> Yes, i remember your commentary.
[21:01] <Daviey> ScottK: I don't agree it to be any more of a burden than anything else.
[21:01] <ScottK> MaaS certainly is.
[21:02] <Daviey> And this is a different topic.
[21:02] <stgraber> I mean the package will be in the software-center, will be visible in apt, will be mirrored as part of the Ubuntu archive and you get the ability to do major version updates for free if you need to. Why do you want to restrict yourself to the strict SRU policies you'd have to follow if you were to get it in the archive now?
[21:02] <slangasek> as for juju-core being pushed the week of release... well, the juju team was asking for this a couple of weeks ago, and it didn't go in right away because AIUI Daviey + jamespage were iterating over the packaging and providing feedback; I'm not sure we want a perverse incentive of less diligent review
[21:02] <Daviey> That bares no resemblance. Different team working on it, different target.
[21:02] <slangasek> ScottK: from the earlier discussion, I thought it was proposed that the package would be in -backports + -updates?  so AFAICS that would be the same SRU version
[21:03] <slangasek> er, SRU burden
[21:03] <ScottK> slangasek: updates maybe someday if things go well.
[21:03] <slangasek> except that in this case there would be no SRU team overhead for the initial version
[21:03] <ScottK> I didn't really understand why that would be better either.
[21:03] <ScottK> The only reason to copy it to updates is if you had something stable and you wanted to offer something newer in backports.
[21:04] <ScottK> Additionally, I don't think Ubuntu should give this special treatment because it's a Canonical project.  If this were any other upstream, we wouldn't even be discussing it.
[21:04] <Daviey> ScottK: To be clear, are you keen to actively block this?
[21:04] <Daviey> ScottK: I don't think that is true.
[21:05] <ScottK> Yes.  I think it's fundamentally a poor choice.
[21:05] <slangasek> ScottK: well, I don't see accepting a new package into universe the week of release as special treatment
[21:05] <slangasek> not qualitatively
[21:06] <ScottK> The amount of arguing over it certainly is.
[21:06] <ScottK> If it weren't a Canonical project, the release team would have said no and that would have been it.
[21:06] <Daviey> ScottK: Well, this would likely be in now.... if you hadn't of decided to re-review my decision
[21:06] <Daviey> Which TBH, is kinda unheard of anyway
[21:07] <slangasek> if it weren't a Canonical project, would members of the release team be saying 'no' when other AAs / RT members are saying they're willing to process it?
[21:07] <ScottK> Of which I was not aware.
[21:07] <ScottK> If it were an upstream with a history of late delivery of buggy code, absolutely.
[21:08] <Daviey> This upstream doesn't have that history
[21:08] <ScottK> It's a matter of opinion.
[21:09] <slangasek> it's a question of how broad a brush you're using
[21:09] <Daviey> ScottK: I think that pov requires justification, otherwise it's nothing but rude against the juju team
[21:09] <ScottK> BTW, I'm not sure how much before my comment yours was (they both say 4 hours ago now), but I hadn't seen it when I wrote my initial objection.  I wasn't intending to re-review what you'd done.
[21:09] <ScottK> Daviey: I wasn't being that specific.
[21:10] <Daviey> ScottK: noted, yours was 9 mins after my assessment. Apologies for assuming it was a re-review
[21:11] <ScottK> If I had seen it and disagreed, I would have directly discussed it with you.  Not sure why didn't see the bug mail come in later.
[21:12]  * ScottK starts to wonder if we should just do away with feature freeze and let anyone do whatever, whenever?
[21:13] <Daviey> ScottK: Maybe raise it as a vUDS session?
[21:14] <ScottK> Ooops.
[21:14] <ScottK> Forgot the sarcasm tag.
[21:14] <Laney> Now look what you've done, Kitterman.
[21:14] <roaksoax> stgraber: so I have one more bug I'd like to get fixed for MAAS as a 0-day sru. Should I upload a new revision of the package that will superseed the one in the still unapproved queue?
[21:14] <slangasek> ScottK: I don't see the current request being at odds with feature freeze; I thought our policy has always been "new packages that don't touch anything else are fine post-FF if you can find the manpower to review it"
[21:14] <ScottK> slangasek: Yes, up to a point.
[21:15] <ScottK> And particularly since this is a re-implementation of an existing package and it's not yet at feature parity, I don't see why it's a big deal to wait a week.
[21:16] <Daviey> So full feature parity should be achieved this week?
[21:16] <ScottK> Then if it turns out there are problems, we aren't stuck with some unsupportable mess.
[21:16] <ScottK> No.
[21:16] <Daviey> Otherwise, i fail to see how it makes any difference
[21:17] <ScottK> Why would a user switch to a less mature/less featureful implementation?  Because someday it'll be better?
[21:17] <ScottK> Other than PR, I don't see any reason to push it in now.
[21:17] <stgraber> roaksoax: I can reject your previous MAAS upload and you can just upload the same version with the fix
[21:17] <Daviey> ScottK: Would you be willing to review this next week?
[21:18] <Daviey> ScottK: This version has assurance of being maintained.
[21:18] <roaksoax> stgraber: that would work :)
[21:19] <stgraber> roaksoax: ok, rejected
[21:19] <ScottK> Daviey: I'll be glad to process the backport request next week.
[21:20] <Daviey> ScottK: No, i am asking if you can do a NEW review?
[21:20] <Riddell> evening
[21:20] <ScottK> Not sure what next week looks like.  Probably.
[21:20] <roaksoax> stgraber: Thanks, will prepare new package with fix and upload!
[21:22] <cjwatson> ScottK: Sorry, I beat you to using sru-release, for casper :)
[21:22] <ScottK> Heh
[21:23] <ScottK> So where did kdenetwork go?
[21:23] <cjwatson> I'm afraid I still feel pretty strongly about juju-core.  I actually think that putting it in post-release pockets will make things *better* for the juju team.
[21:24] <Daviey> cjwatson: how so?
[21:24] <stgraber> ScottK: so it looks like ubiquity 2.14.8 has now been published in raring-updates. Need anything else?
[21:24] <Laney> You know we technically have backports open now.
[21:24] <ScottK> stgraber: kdenetwork.
[21:24] <ScottK> Laney: Good point.
[21:24] <cjwatson> Because you won't have the initial "huge pile of stuff via updates, have to get the TB to pass it" thing.
[21:24] <ScottK> Daviey: How about we put it in backports now?
[21:25] <cjwatson> Also, I very strongly believe that the "but it's in universe" thing is a case of trying to have your cake and eat it too.
[21:25] <cjwatson> It's entirely obvious that this is something that Canonical wants to recommend to relevant audiences
[21:25] <cjwatson> We can't say that on the one hand, and on the other use the excuse of being in universe to be more lenient about it
[21:25] <Daviey> Oh i agree. I don't subscribe to the idea that universe means 'throw any crap in'
[21:26] <slangasek> well, from my POV having it in universe is an important benefit for the user because right now users of the package are getting it only from a ppa
[21:26] <cjwatson> They can get it just as well from -updates a bit later, and with only a slight extra step from -backports nowish (if uploaded there)
[21:26] <stgraber> ScottK: what version of kdenetwork do you need? The current one is 52min old
[21:26] <slangasek> ... which means the system provides no guarantees that the maintainers won't introduce regressions
[21:27] <stgraber> kdenetwork | 4:4.10.2+dfsg-0ubuntu1 | raring/universe | source, all
[21:27] <ScottK> stgraber: that's the one.
[21:27] <stgraber> ScottK: ok, so all set then?
[21:27] <ScottK> I was looking for an ubuntu2.  Forgot about the DFSG.
[21:27] <ScottK> Yes.
[21:27] <cjwatson> stgraber: I'm just making sure cdimage can see it
[21:27] <ScottK> It's been a long day.
[21:27] <Daviey> Does it need a separate upload to go to backports, before s opens?  Or can i just be included there as part of acceptance ?
[21:27] <stgraber> cjwatson: ok, feel free to kick the respin if you're already playing on nusakan
[21:28] <cjwatson> It'd need a separate upload, or separate copy from a PPA or whatever
[21:29] <cjwatson> slangasek: For my part, I don't see this as the normal case of a new package (I was fine with the libgit2 sync that somebody else accepted) because it's far from without interactions with existing packages; and of course it has the static linking business too which I'm separately unhappy about
[21:29] <ScottK> Daviey: ^^^^ easiest just to re-upload with raring-backports.
[21:30] <Daviey> cjwatson: Yes, that frustration has been shared.
[21:30] <Daviey> jamespage: are you around?
[21:30] <cjwatson> But not resolved.
[21:30] <jamespage> Daviey, yes
[21:30]  * jamespage reads backscroll
[21:31] <cjwatson> Do we need to respin kubuntu-active as well?
[21:31] <cjwatson> There's bits of kdenetwork in it, so I guess yes
[21:31] <cjwatson> Oh, and ubiquity.  So yes.
[21:31] <stgraber> right and ScottK marked it for respin on the tracker
[21:32] <Daviey> jamespage: Can you re-upload targeting backports please?
[21:32] <cjwatson> Respinning.
[21:32] <cjwatson> So want the "respin everything marked for rebuilding" thing :)
[21:33] <stgraber> well, I'm going to spend around 15h on various airplanes over the weekend so you may have that next week ;)
[21:33] <jamespage> Daviey, ack - I'll sort out the ugly version number at the same time.
[21:33] <stgraber> adding DB fields and testing migration scripts is the kind of thing that long flights are good for
[21:34] <Daviey> jamespage: thanks
[21:44] <jamespage> Daviey, ScottK: OK - uploaded to raring-backports
[21:44] <Daviey> jamespage: thanks.
[21:45] <Daviey> Hmm, I can't review backports.. can i?
[21:45] <cjwatson> Technically yes but by policy no (same for me - it's ~ubuntu-backporters)
[21:46] <cjwatson> But several relevant folks here
[21:46] <ScottK> Daviey: I've approved the backport, so I think any archive admin can do New.  Please feel free.
[21:48] <ScottK> I just clearly said it was approved in the bug.
[21:49] <Daviey> ScottK: I didn't think i was allowed to process backports, even if approved.  Now i do.
[21:49] <ScottK> IMO, ubuntu-backporters has to approve any backport.
[21:50] <ScottK> Since this is a new package, there's none of the usual things to worry about that are unique to backports, so there's no reason I can't do the approval and leave the New to another archive admin.
[21:52] <ScottK> It's a bit of an odd case to have come up.
[21:56] <roaksoax> stgraber: done! thanks
[22:08] <balloons> ogra_, have you tried the arm builds for panda or the nexus7?
[22:13] <xnox> balloons: i can blast through nexus7 tomorrow morning. should be all fine.
[22:13] <xnox> balloons: and panda as well.
[22:16] <pgraner> balloons, we don't care about desktop even tho is built, server is the focus on arm
[22:21]  * cjwatson fixes corner-case checksumming bug in publish-release
[22:21] <cjwatson> (Confused verify-cloudfront)
[22:39] <cjwatson> Daviey,jamespage: FWIW, things missed in the NEW review of juju-core: missing ${shlibs:Depends} (yes, it's at least a partially dynamically linked binary); fairly arbitrary Architecture: amd64 i386 that really should be any so that if nothing else we can have visibility of why it fails elsewhere
[22:40] <Daviey> cjwatson: It was expressly set to amd64 i386
[22:40] <infinity> Daviey: Yes, it shouldn't be.
[22:40] <infinity> Daviey: It should be arch:any.
[22:40] <cjwatson> expressly> that was in fact my complaint
[22:40] <Daviey> cjwatson: If you are doing a post-review review, why didn't you just volunteer to do it in the first place?
[22:41] <cjwatson> Er, because I was doing a load of other critical-path things at the time?
[22:41] <Daviey> And now?
[22:41] <cjwatson> Now I'm not
[22:41] <Daviey> Super.
[22:41] <cjwatson> And I don't see how this is any of your business
[22:42] <cjwatson> Apparently I should never report problems in packages you care about.  Fine.
[22:42] <Daviey> Well, you can surely see that it is frustrating to see someone do a review moments after it has just been accepted.
[22:42] <infinity> You do realise that people can find issues with packages at any point, right?  "It was reviewed" doesn't imply it's perfect.
[22:42] <cjwatson> I don't really care.  Sorry.
[22:42] <cjwatson> Since I would far rather be in bed but I need to supervise a load of stuff.
[22:43] <cjwatson> So, you know, sorry if finding problems has hurt your feeling
[22:43] <cjwatson> s
[22:43] <Daviey> No, it has not hurt feelings.  But I appreciate the apologetic sentiment.
[22:44] <cjwatson> Happy to file bugs if you'd prefer.
[22:46]  * cjwatson does so
[22:49] <xnox> cjwatson: time to implement debian ftpmaster style auto-rejects based on lintian tags?! /me recently got auto-rejected in debian =)
[22:50] <xnox> that should do it.
[22:53] <Riddell> new Kubuntu builds on their way?
[22:54] <cjwatson> Yeah
[22:54] <infinity> Riddell: Yeah, waiting on ARM.
[22:54] <cjwatson> 22763 pts/9    S+     0:00      \_ ssh -n -o StrictHostKeyChecking=no -o BatchMode=yes buildd@cadejo.buildd /home/buildd/bin/BuildLiveCD -l -A armhf -s omap4 -d raring kubuntu
[22:54] <cjwatson> At some point ...
[22:54]  * cjwatson feeds cadejo more hamsters
[23:00] <cjwatson> It's building the squashfs
[23:19] <cjwatson> Ah, good, there we go
[23:38] <balloons> xnox, pgraner ok.. just wanted to see if you noticed some of the bugs creeping in.. the desktop images as usual have some little things
[23:39] <pgraner> balloons, yep I'll round them up in the am for the release notes
[23:39] <balloons> pgraner, excellent. Let me know if you need bug numbers :-0
[23:40] <pgraner> balloons, ha!
[23:41] <stgraber> apparently my brain really needs sleep now, so I'll disappear for a few hours and be back early tomorrow morning to finish some Edubuntu tests and look at techoverview/release notes. Good night everyone!
[23:44] <infinity> stgraber: 'Night.