[02:24] if someone's around; I'd need somebody to check in on autopilot which seems to be stuck believing its autopkgtests are still running... well because technically the job is still running but should have returned with success a few hours ago it seems [02:29] slangasek: re qtcreator and remotelinux - Do we really want to fork from upstream going into an LTS on something upstream hasn't agreed they will ever do? [02:30] As far as I know, this hasn't been coordinated with the Kubuntu team and I find it quite disappointing after having gotten the Ubuntu SDK module out of hte qtcreator source package to have the package run off on another tangent from upstream. [02:30] ScottK: Bug? [02:31] bugs/1302620 [02:31] Seems to me that no agreement with upstream on a long term release is a pretty good reason to wait a cycle. [02:33] BBIAB [02:34] ScottK: I'm not sure splitting a package out is quite the same level of awful as adding random bits TO the package. [02:35] Even if upstream never wants to split the tarball, that's no reason for Ubuntu to not have split tarballs (or, at the very least, split binaries, which is a very Debian thing to do anyway). [02:36] (The timing is a bit crap, but it doesn't seem to have wide impact currently) [02:37] infinity, can you take a look at ubuntu-gnome-wallpapers in NEW? [02:40] darkxst: Did you guys not have a wallpapers package before? [02:40] Where did your wallpaper come from? :P [02:40] we use the stock gnome wallpapers previously [02:40] Ahh, kay. [02:40] darkxst: So, will this invalidate all your docs and screenshots, or do you not particularly care? [02:40] this was the first cycle we had a community wallpaper contest [02:41] (And I assume this will need to be seeded, etc) [02:41] darkxst: Will your default wallpaper also come from this package, or will it not change? [02:41] infinity, it will be seeded, but not set as default wallpapers [02:41] Kay, cool. [02:41] Will review based on that knowledge, then. [02:41] thanks [02:48] infinity: I don't see it as any different since our package if forked, possibly permanently. [03:44] ScottK: bzoltan made a strong case to me that the sensible way forward for these plugins is to have them out of tree so that they can be developed without wrangling all of qcreator; I was pushing back hard so long as I thought this was being regarded as a temporary workaround, but given that this is their long-term goal it seems sensible to me. Would you prefer they do something differently wrt getting this into the archive (aside fro [03:44] ScottK: the other point was that AIUI they've already done this for the cmake module [03:45] slangasek: you cut at "(aside fro" [03:46] really? odd [03:46] (aside from the timing)? [04:02] slangasek: I think he should be making the case to upstream and it shouldn't be done as a distro thing. [04:02] Didn't know about the cmake thing. See my earlier points about coordination. [04:03] slangasek: I'd say let them sort it out with upstream, get it into "U" and backport as necessary. [04:07] I don't particularly buy their whining about it being hard to upstream stuff with Digia either. If it's hard for them, it's only because they aren't working with them (which it a problem). To the extent they are having trouble it's a symptom of a problem that is exactly why I don't want stuff in our packages upstream hasn't agreed to. [04:08] Bed time for me. [05:44] infinity, will ubuntu-gnome-wallpapers project get created automatically or do I need to add it manually ? [05:44] (to be able to push the vcs-bzr branch) === maclin_ is now known as maclin [07:07] hi, I'd like to coordinate/review syncs of checkbox releated packages [07:07] the full list of packages is https://lists.launchpad.net/checkbox-dev/msg00111.html [07:08] this is also heavily related to https://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/1302615 [07:08] Launchpad bug 1302615 in checkbox (Ubuntu) "[FFe] [UIFe] Checkbox GUI needs to be able to send test results to Launchpad" [Undecided,New] [07:37] infinity, hey - i added those debdiff's to the bugs. i also put a clarification for you on the bug about ui customization [08:14] plainbox debdiff: http://paste.ubuntu.com/7225244/ [08:15] checkbox-support debdiff: http://paste.ubuntu.com/7225250/ [08:16] checkbox-ng debdiff: http://paste.ubuntu.com/7225251/ [08:17] plainbox-provider-resource-generic debdiff: http://paste.ubuntu.com/7225256/ [08:21] plainbox-provider-checkbox debdiff: http://paste.ubuntu.com/7225270/ [08:54] is anyone able to look at https://code.launchpad.net/bugs/1302615 [08:54] and [08:54] https://code.launchpad.net/bugs/1303849 [08:55] i'm ready and willing to follow up on any questions and comments [09:54] Daviey, ceph 0.79 was out yesterday; I've tested quite a bit - details in bug 1278466 [09:54] Launchpad bug 1278466 in ceph (Ubuntu Trusty) "[FFe] ceph firefly stable release" [High,In progress] https://launchpad.net/bugs/1278466 [09:54] (last comment) [09:54] Daviey, can I get an ack for upload please [10:13] jamespage: Oh, that is great news. Please upload. [10:13] Daviey, ack [10:14] jamespage: To clarify, we have the release goals for 14.04 here... or is there something else we wanted from 0.80? [10:14] Daviey, other than to lineup with the release that upstream will actually push point releases against - no [10:15] all the features are now in [10:15] Great! [10:16] Daviey, uploading now [10:23] superm1: Hmm, mythbuntu-live-autostart includes .bzr with the upload and inconsistent historic d/changelog.. I assume this is an accident.. [10:24] superm1: Going to reject it, if this is intent - please let me know, and we can retrieve it from the rejected queue for review. [10:53] hi [10:53] please hold webbrowser-app in the unapproved queue when it arrives, we have another fix coming down silos right after [11:06] hey, can we do something to move plainbox|checkbox packages forward? [11:06] * zyga is unsure how this process works [11:58] Hi release team! I would need some help on investigating something - there has been a account-plugins version (0.11+14.04.20140401-0ubuntu1) that has been put into the rejected queue - we have another release for this component and because of that I would like to know the reasons for why it was rejected the last time [11:58] https://launchpad.net/ubuntu/trusty/+queue?queue_state=4&queue_text=account-plugins [11:58] Does anyone remember by any chance what were the reasons for rejecting this one? [12:00] Whoever uploaded it should have gotten a mail with the reason. [12:01] It's all part of CI Train, so hm, not sure where to look [12:02] No clear sign of it in IRC logs [12:03] The archive robot requested it, so I might have it [12:03] * cjwatson looks in that gigantic mailbox [12:03] o/ [12:03] hmm, nothing [12:03] cjwatson: thanks for looking into that - mardy (one of the upstream developers) says that it might have been infinity rejecting the upload [12:04] maybe it's the account that did the original copy that gets the sync? [12:04] s/sync/mail/ [12:04] That'd be ~ps-jenkins I suppose [12:05] Maybe find somebody who can read the archives of https://lists.canonical.com/mailman/listinfo/ps-jenkins ? [12:06] Yet another pitfall of a process without a human uploader. [12:07] To be fair it's not clear why the archive robot shouldn't have got mail here [12:07] It probably also ought to use the facility for sponsoring syncs on behalf of other people [12:07] ci-train should I mean [12:08] It knows who's logged into Jenkins to request it, hopefully it can map that back to an LP username ... [12:10] didrocks: ^- can citrain get at the requesting user's LP username? if so it could add sponsored= to its copyPackage calls [12:12] cjwatson: it will need some testing. I'm unsure what the jenkins plugin is sending and if we can map back to a user name [12:12] I'm not totally sure that that would let LP rejection messages go to the requesting user, but it would at least make it *possible* to do that [12:12] which would have helped this [12:14] yeah [12:16] cjwatson: I'm not really sure with the amount of churn we are having right now I can look at it, but definitively adding to the backlog of things to investigate [12:19] yep, thanks [12:48] hello, sorry for naging, but any thoughts on https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1302947 ? or should I use my own judgement (given that I'm the debian maintainer of ansible as well?) [12:48] Launchpad bug 1302947 in ansible (Ubuntu) "[FFe] ansible 1.5.4" [Undecided,New] [13:07] hi guys, we need to land a new package sync-monitor as part of the Touch FFE - will only be seeded on touch. didrocks has done the archive admin review already [13:44] Can someone poke my ima-* tools in the NEW queue? [14:02] Daviey: i'll double check [14:07] Daviey: yeah it was a mistake that tgm committed something to bzr with the wrong changelog entry, and me using a different computer that configured in bashrc to not include .bzr, i'll upload again momentarily [14:09] how can I get some cooperation on checkbox|plainbox packages? what do we need to get them approved? [14:26] zyga: we currently have 261 uploads in the queue [14:28] * cjwatson accepts a load of langpacks then [14:29] * doko greats from PyCon [14:35] cjwatson: What are you looking for with a langpack review? [14:37] superm1: accepted, thanks [14:38] Daviey: not a lot [14:39] Daviey: I generally wave through the bulk ones because I know langpacks get some testing in advance and I'm not liable to add much with a manual review compared to the effort it would take [14:42] * cjwatson approves the two checkbox ffes, rolls up sleeves, and prepares to plough through diffs [14:42] cjwatson: thanks!!! [14:42] I may be some time ... [14:47] cjwatson: I can do the checkbox upload, maybe that'll save you some time? [14:48] I'm not clear how that would save me time, given that I wasn't planning to upload checkbox :) [14:49] cjwatson: heheh :) I'm not the time-saver I thought I was :P [15:00] ok, let's see how this goes [15:00] In the queue is an upload called folks, well - a sync from a PPA. It looks like it was uploaded to the PPA by a developer, without upload access. The requester in the queue just shows the Archive Robot. How do i tell who 'sponsored' this? [15:01] you have to go look at the PPA, that's the CI Train stuff [15:01] ci-train.ubuntu.com will have the requesting user [15:01] cjwatson: The PPA shows the user that doesn't have upload access [15:02] Oh [15:02] see above discussion of why it'd be good for the ci-train system to use sponsored= [15:02] https://ci-train.ubuntu.com/job/landing-009-2-publish/5/console says Mirv published it [15:04] cjwatson: Amazin' I don't have ACL to view that url. [15:04] really. you're meant to [15:04] didrocks: ^- I thought those were meant to be community-visible [15:05] hum [15:05] it should [15:05] yeah it's SSOing me too [15:05] maybe the move to prodstack prevented that? It seems to forcingly forces me to log in [15:05] I guess I'll have to file an IS RT for investigating [15:06] is it just "you have to log in with SSO but then anyone can see it"? [15:06] No, i did the logout+login dance [15:06] Still apache SSO blocked [15:07] I'll have a look, cant' right now, but I'll follow up with #webops [15:07] the canonistack instance wasn't forcing you to log in [15:07] didrocks: thanks [15:08] Doing source packages through CI is quite new, and I'm not sure what the governance there is meant to look like [15:08] Interesting [15:10] Well, I was looking for a responsible name of someone that virtually sponsored it, ie - requested but not signed. [15:10] yeah, in this case the answer is Mirv [15:12] But that set of people is not the same as the set of uploaders of the package, and now any package can be uploaded through this process [15:12] The people who can upload to the PPAs in the first place is a different team too (~ci-train-ppa-service) [15:18] cjwatson: Sorry to labour this... but unless I am mistaken, Mirv doesn't have upload access to this package - how can he sponsor it? [15:19] the landing procedures require a core-dev ack for anything that's a substantive packaging change [15:20] otherwise I suggest you look through the diff and decide whether you're happy with it [15:20] cjwatson: How is substantive defined, and is there an audit history of which core-dev ack'd it? [15:20] don't ask me [15:20] I just do my best with this stuff, I didn't set any of it up :) [15:21] the diff is 104 lines here so seems pretty straightforward to review [15:21] cjwatson: Oh, Sorry I wasn't waving a finger.. I appreciate that. :) [15:21] how> The CI train generates a request which is executed by a script with Ubuntu Archive Robot's credentials [15:22] cjwatson: Right.. No problem with the diff... But I feel uncomfortable reviewing stuff without the backstory, i suppose. The audit history. [15:22] So what you need are the right permissions to generate those requests [15:23] right, it's delegated; anything that goes through the ci-train stuff has been built everywhere, run through autopilot tests, and manually tested on a device, aiui [15:25] I certainly agree that it's pretty cumbersome to dig up the audit trail right now ... [15:25] stgraber: thanks, I see, where can I monitor th4e queue? [15:26] zyga: https://launchpad.net/ubuntu/trusty/+queue [15:27] look for the Unapproved queue [15:28] * zyga sees versiontools and is quite surprised [15:42] I could use reviews of attr and grub-installer since those both have other changes I need to land behind them [15:43] seb128: I'm having trouble seeing how this language-selector upload relates to bug 1008344. Was that a typo? [15:43] Launchpad bug 1008344 in language-selector (Ubuntu) "checks "admin" group membership instead of querying polkit" [Medium,Triaged] https://launchpad.net/bugs/1008344 [15:43] cjwatson, yes, sorry, I had both bugs in tabs :/ [15:44] it's bug #1165626 [15:44] Launchpad bug 1165626 in language-selector (Ubuntu) "Details pane is dysfunctionally small in package installation prompt." [Low,Triaged] https://launchpad.net/bugs/1165626 [15:44] cjwatson, I can reupload if you want [15:44] yes please, I'll reject this one [15:45] smoser: This will not affect curtin http://launchpadlibrarian.net/172345441/grub-installer_1.78ubuntu19_1.78ubuntu20.diff.gz ? [15:47] Daviey, i dont think so . [15:47] curtin would probably be broken if it did - if you don't have an EFI System Partition then grub-efi won't work [15:47] unless some arcane detail has leaked out the back of my head :) [15:48] cjwatson, when does that code run ? [15:50] smoser: in the installer phase that installs the boot loader (i.e. well after partitioning) [15:50] should be fine then. [15:51] excellent a quick php upload just before release =) [15:54] hey, so we have an oxide upload in https://launchpad.net/~ubuntu-security-proposed/+archive/ppa/+packages that is need to fix issues on touch, add file picking support (required for touch and webapp-container parity on desktop), along with bug fixes [15:54] oxide is in main now and technically this is adding features, but this is all part of the FFe imo (ie, it is for feature parity) [15:56] can someone from the release team review/ack. at that point I will coordinate with citrain [15:59] * jdstrand -> reboots real quick [16:03] * jdstrand back [16:06] slangasek: +MANIFEST-NETBOOT_DIR = "PXE boot directory for tftp server" [16:06] slangasek: Didn't you just break your own rule there? :) [16:08] =)))) [16:10] jdstrand: If it's well-tested in any context that applies to desktop, go for it. [16:11] infinity: it is undergoing said testing and won't be pushed until it is completed. thanks! === bfiller is now known as bfiller_afk [16:21] cjwatson, ^ with right bug ref this time, thanks for spotting it ;-) [16:28] infinity: sighhhh. Cut'n'paste error :( [16:29] slangasek: Well, given the lack of pxelinux.cfg, I'd call that a complete lie. Want to reject and fix the manifest? [16:39] infinity: yeah, reuploaded [16:55] infinity: ^^ new debian-installer in the queue [17:08] Who's the release POC for Ubuntu Studio these days? [17:09] zequence: ^ [17:10] Thanks. [17:11] zequence: I'd like your opinion on bug 1291675 (please comment in the bug too). [17:11] Launchpad bug 1291675 in lmms (Ubuntu) "[FFe] LMMS 1.0.0" [Wishlist,New] https://launchpad.net/bugs/1291675 === roadmr is now known as roadmr_afk === roadmr_afk is now known as roadmr [17:50] stgraber: hey, could you accept sssd 1.11.5 from the queue, it has MRE and all :) [17:51] yeah, I'll take a look in a tiny bit [17:51] thx [17:51] modified the upstart job too [17:52] oh, yay for the upstart job! [17:52] the failure was easy to test, like when my local ipa server is down the ipa backend on the client fails to start [17:52] I've been hitting that problem quite a few times this week with boxes that are provisioned through a configuration manager (sssd starts before the machine is joined) [17:52] so sssd is running, but not doing much [17:52] stopping it will fail [17:52] yeah this should finally fix that.. [17:53] I should probably reply to the folks who complained about this on sssd-users@.. [17:53] long ago [17:54] ok, upstream changelog seems fine and packaging changes too, accepted [17:55] great === bfiller_afk is now known as bfiller [18:11] ScottK: Yep. I'll give it a testrun shortly. [18:11] Thanks. [18:13] can someone please push pollinate through? this upload is required to enable pollinate to handle the new ssl certs, per the heartbleed ssl fixes [18:15] kirkland: unseeded packages are auto-accepted [19:40] Hi folks. I was wondering if someone can look at nvidia-grpahics-drivers-331-updates in the precise queue (in new). this update is required for compat with 3.13 and it's blocking for people wanting to test the trusty backport kernel early. thanks! [20:18] Good day for all!, i am searching for ubuntu studio 10.4, but i cant find it, can any body give me an advice. [20:19] were can i download it? [20:31] tjaalton: around? [20:31] tjaalton: I have a few systems where sssd now crashes since the upgrade... [20:31] stgraber: gah.. [20:32] tjaalton: oh, one obvious mistakes at least, s/-f/-i/ [20:32] I should have caught that one in my review... [20:32] where was that? [20:32] the upstart job? [20:33] yeah [20:33] well, the default file [20:33] but even with that one fixed, authentication is broken [20:33] it worked for me without -i [20:34] err [20:34] (Wed Apr 9 20:34:06 2014) [sssd] [mt_svc_exit_handler] (0x0040): Child [SAMBA] terminated with signal [11] [20:34] (Wed Apr 9 20:34:06 2014) [sssd] [mt_svc_exit_handler] (0x0010): Process [SAMBA], definitely stopped! [20:34] so I have -f, it just means send debug to logfiles [20:35] right, it won't guarantee sssd will stay in the foreground [20:36] just did a quick check and sssd died post-upgrade on all of my 50 or so trusty systems [20:37] so I effectively can't login to any of them without some hacks [20:37] ouch.. [20:38] so much for upstream qa.. this was supposed to be all bugfixes in the ad backend [20:38] I'm trying to get one of my machines to give me a .crash file [20:40] got one from an arm box, trying to get it sent to LP [20:40] oh and LP isn't IPv6 yet so I can't submit the report... [20:43] :/ [20:43] pinged upstream as you probably noticed [20:46] tjaalton: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1305303 [20:46] stgraber: Error: launchpad bug 1305303 not found [20:46] thanks [20:47] let's hope the retracers will get us a stacktrace soon [20:50] should the link work already? [20:51] yeah, but it's private [20:51] added you to it now [20:52] ah [20:54] I'm trying to find a machine I can still log into to do a manual retrace [20:55] Riddell: ^^^ please review/approve. [20:56] (penance for forgetting to update bzr after your last upload, if nothing else) [20:57] tjaalton: http://paste.ubuntu.com/7228102/ [20:58] hmm did you use the ldap backend or ad? [20:58] and mind posting that on #sssd too.. [20:58] tjaalton: http://paste.ubuntu.com/7228110/ [20:59] ok, sort of a hybrid then as i remembered :) [21:12] seems to work fine on my ipa client :/ [21:12] which is a simple setup, admitted [21:13] tjaalton: I'll upload the old sssd to my PPA for now with an higher version number, so that my systems start working again. If we don't get a resolution for this by final freeze time tomorrow, I'll push it to the archive too. [21:13] stgraber: that's fine [21:14] I'm out of cycles for today, so you're probably better off working directly with sgallagh on this.. I'll check the scrollback in the morning [21:18] tjaalton: ok. I just uploaded my revert to my PPA, will keep one container broken on purpose for testing [21:38] stgraber: i just realized that they don't test against samba4, since fedora/rhel doesn't have dc functionality for it [21:38] since they're mit-krb only [21:39] fyi, oxide-qt should be coming in here soon. it was discussed earlier and is tested, passed citrain, etc [21:39] I will be afk for a while [21:39] tjaalton: yeah, that's why things always blow up for me ;) [21:40] :) [21:40] i'll remember to ask you test stuff _before_ the fan gets smelly [21:42] btw, oxide-qt has two NEW packages. oxideqt-codecs for main and oxide-codecs-extra for universe [21:42] I can handle that later if needed [21:42] * jdstrand is really gone now [21:43] * cjwatson tries to sneak a >300000-line diff in before final freeze [21:43] debconf-updatepo... also known as "I'm feeling unproductive today. [21:43] Please give me a huge diff to check in" [21:51] tjaalton: ok, so that patch seems to do the trick, now I'm just trying to figure out the upstart problem. [21:51] tjaalton: so on your system. If you do "status sssd" it reports it as running with the right pid? [21:52] hum no :) [21:54] right, so we have a problem there :) [21:54] and -i doesn't improve things for some weird reason... [21:54] right [21:56] oh, I think I see why [21:56] try: sssd -i < /dev/null [21:57] it'll fail immediately [21:57] yep [21:59] I've got a fix [21:59] tjaalton: I'll upload the patch and the upstart fix to the archive now [22:00] sure, thanks [22:00] push to git too :) [22:01] yep, will do [22:01] stgraber: hey, could you please review mtp? [22:01] nevermind, I fail at reading [22:02] tjaalton: http://paste.ubuntu.com/7228326/ [22:03] stgraber: 'stding', a typo? [22:04] typo indeed, let me fix that quickly [22:06] yep, works fine now [22:06] a peculiar looking fix though :) [22:07] slangasek, infinity, ScottK: if one of you is around, could you review sssd in the queue? anyone who like me is using samba4 currently can't authenticate because of that bug... [22:08] tjaalton: one could certainly argue that the bug is upstream and that sssd should deal with stdin being /dev/null, but whatever, easy enough to make it happy :) [22:09] didn't know daemons get passed input like that [22:12] stgraber: Done [22:13] slangasek: Could we release the SRU fixing bug 1286161 early? [22:13] Launchpad bug 1286161 in ubuntu-release-upgrader (Ubuntu Trusty) "13.10 -> 14.04 upgrade failed: initramfs failed to ugprade, udev is not configured yet" [High,In progress] https://launchpad.net/bugs/1286161 [22:14] speaking of, we should get that gdk-pixbuf sru verified [22:14] that could possibly cause upgrade failures [22:14] * Laney notes down for tomorrow [22:18] ScottK: thanks [22:18] Laney, btw your bamf fix is in the unapproved queue [22:19] excellent [22:19] I'm sure one of these kind fellows will look at it in due course [22:20] slangasek: ^ qtbase-opensource-src [22:26] tjaalton: ok, I think I pushed things to alioth properly. I pushed everything in debian-unstable first, added an UNRELEASED changelog entry there, then merged that into the ubuntu branch, did a proper merge of the changelog and committed the result. [22:27] stgraber: yup, sounds good [23:01] Would someone pretty, pretty please review the FFe for python-seamicroclient - https://bugs.launchpad.net/ubuntu/+source/python-seamicroclient/+bug/1305220 [23:01] Launchpad bug 1305220 in python-seamicroclient (Ubuntu) "FFE: python-seamicroclient new upstream release" [Critical,New] [23:03] and can please some review MAAS upload? it is just important bugfixes [23:50] hello, just wondering if somebody can take a look at account-plugins in UNAPPROVED. it has an important facebook app token update, all facebook-connected apps are broken without it