[00:16] Logan: No, but it seems someone else just did. [00:17] ah, but I wanted the infinity stamp on it :( [00:17] Logan: Trusty's done; would you kindly add the bug reference to vivid? [00:18] oh, did I not nominate it for Vivid? awks [00:18] No, you didn't include the bug in the changelog. [00:18] OH [00:18] do I need to bump the version? [00:18] No. [00:18] No. [00:18] Rejected versions aren't "used up". [00:18] I figured [00:22] RAOF: ^ thanks! [06:02] RAOF: Probably poor form to accept mesa-lts-vivid/trusty, but not the matching mesa/vivid. [06:04] infinity: Hm. Didn't notice that one. [06:04] RAOF: For HWE backports, I tend to verify that the origin exists in the archive before accepting the backport. [06:04] RAOF: Since it's a bit backwards the other way. :) [06:04] :) [06:05] RAOF: (pls fix, since you have context from the first review) [06:05] Doing so now. [06:19] if there is a sru team member around the horizon in trusty proposed addresses a regression introduced with the last update [06:19] https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1476417 [06:19] Launchpad bug 1476417 in horizon (Ubuntu Trusty) "[SRU] FloatingIpManager in neutron.py missing is_supported method" [Critical,Triaged] [06:20] I'd like to get that out asap as horizon is quite broken in trusty right now [06:20] jamespage: Looking. [06:20] infinity, thankyou [06:22] jamespage: Accepted. If it's critical, feel free to turn around a quick verification with some indication of reasonable regression testing, and we can fasttrack the promotion to updates. [06:23] infinity, on that now [06:23] jamespage: Well, ideally wait for the binaries to spit out. ;) [06:23] indeed [08:10] infinity, (or any other sru team member): I've worked through the horizon webui as both an end-user and a admin user - fix for bug 1476417 tests out OK and causes no regressions that I can see [08:10] bug 1476417 in horizon (Ubuntu Trusty) "[SRU] FloatingIpManager in neutron.py missing is_supported method" [Critical,Fix committed] https://launchpad.net/bugs/1476417 [08:10] if we can get that released today much appreciated [08:23] flexiondotorg: You dropped ubuntu-mate-wallpapers-common but stuff depends on it [08:23] didn't notice that, partially my bad [08:34] can an admin approve nvidia-graphics-drivers-352 and nvidia-graphics-drivers-352-updates in wily NEW, please? [08:34] they belong in "restricted" [08:41] tseliot: I'll be looking at those later, but first you need to fix your nvidia-* trusty SRUs for me. [08:42] tseliot: Note the comment on the bug, you got your conflicts/replaces wrong (the old packages provide a different virtual package than the one you replace in the new ones) [08:42] infinity: ok, let me check that [08:44] infinity: what bug report did you use for that comment? [08:48] tseliot: The one mentioned in the SRUs? [08:49] tseliot: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-346/+bug/1465706 [08:49] Launchpad bug 1465706 in nvidia-settings (Ubuntu Trusty) "SRU: New upstream releases of nvidia for 14.04.3" [High,In progress] [08:49] tseliot: Comment #7 [08:49] tseliot: Easily visually verifiable that nvidia-opencl-icd-331 doesn't provide the package that the newer ones are replacing. [08:56] infinity: ok, thanks [09:05] tseliot: If you can fix that up ASAP, we can re-verify and get it all sorted today. [09:10] infinity: sure [09:25] infinity: is it ok if I add opencl-icd to conflicts/replaces and keep the new virtual package? [09:26] tseliot: Yeahp. [09:26] infinity: ok [09:30] flexiondotorg: fixing the LO icon deps in your metapackage, since that's also uninstallable on arm64 and ppc64el [09:32] infinity: actually, I've just remembered that I removed that conflicts/replaces in 331 to fix LP: #1247736 . My guess is that the user who reported the problem was using an nvidia-opencl-icd-331 (331.38-0ubuntu7 ?) that is older than what is available in trusty updates (331.113-0ubuntu0.0.4). You can see the difference here: http://paste.ubuntu.com/11958577/ [09:32] Launchpad bug 1247736 in nvidia-graphics-drivers-304-updates (Ubuntu Trusty) "[SRU] nvidia-opencl-icd-* should not conflicts/replaces on opencl-icd" [Undecided,Confirmed] https://launchpad.net/bugs/1247736 [09:38] tseliot: Hrm? [09:39] tseliot: It either need to conflict/replace that virtual package, *or* needs versioned conflict/replaces on the older nvidia-opencl-icd-331{,-updates} packages. [09:39] tseliot: If the opencl-icd conflict is a bug, then do the latter. [09:40] tseliot: If you're overwriting files, you need to express that. [09:40] infinity: yes, the latter seems like the only option [09:41] tseliot: I assume nvidia-opencl-icd-331{,-updates} >> 340 are actually empty packages? [09:41] So you can just conflict/replace against those (<< 340) [09:42] infinity: yes, those are empty transitional packages [09:42] good point [09:42] I introduced that change in 331.38-0ubuntu7.1 [09:43] (<< 340) is easier to type. :P [09:43] right [09:43] :) [09:44] And also more obviously correct to a human reviewing, like me. :P [09:44] I assumed admins were superhuman beings ;) [09:48] infinity: something like this should work, right? http://paste.ubuntu.com/11958630/ [09:49] tseliot: That looks reasonable, yeahp. [09:49] tseliot: x however many packages need that fix. [09:50] 2, 4, I dunno, the nvidia stuff seems to multiply. [09:51] infinity: right, it's not my fault though ;) [10:03] infinity: I should debuild with -v to include the diff from the previous release in -proposed too, right? [10:04] tseliot: Ideally, yes. [10:04] infinity: ok, good [10:11] infinity: I'm going to add unversioned conflict/replaces for 304 and 304 updates, since, apparently, I've never fixed 1247736 in trusty for these packages [10:15] infinity, Are you on duty? [10:16] flexiondotorg: I'm barely awake, so I guess it depends on what you're asking. [10:16] infinity, Sleep well :-) [10:18] Laney, So ubuntu-mate-wallpapers-common should not have been dropped. I'll check my sources and see what happened there. [10:18] Laney, Thanks for steering me in the right direction. [10:19] np [10:34] Laney, I've found the issue. ubuntu-mate-common was erroneously removed in a commit. [10:34] Laney, I'll can raise a new debdiff bug for ubuntu-mate-artwork. Should I rev the version in the resubmission? [10:35] infinity: ok, uploaded [10:37] flexiondotorg: yes, it's already uploaded so we need a new version [10:37] OK, understood. Sorry I messed this up. Any chance you'd be able to sponsor the new upload when I submit it? [10:38] sure [10:38] Laney, because I'd really need this in Alpha 2. I appreciate I'll need to issue a rebuild at some point. [10:38] Laney, Thanks very much. I'll go and make the debdiff. [11:33] tseliot: Were 346* the only ones with the bug? [11:39] tseliot: Both accepted. Please re-verify, including testing the broken upgrade path you just fixed, so we can get these in. [12:03] stgraber: You around? [12:04] lordievader: sorta [12:04] Did you see my message of yesterday? [12:54] infinity: thanks, I will re-verify that. As for the other packages, 340 has transitional packages for 331, so it should be ok. Installing 340-updates over (non -updates) 331 will probably fail though. [13:24] Laney, sorry for the delay. Here is the ubuntu-mate-artwork debdiff. Thanks for helping. [13:24] https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1479352 [13:24] Launchpad bug 1479352 in ubuntu-mate-artwork (Ubuntu) " ubuntu-mate-artwork 0.4.12 new nelease [debdiff attached] " [Undecided,New] [14:30] didrocks, If you're not too busy could you sponsor this upload please? [14:31] https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1479352 [14:31] Launchpad bug 1479352 in ubuntu-mate-artwork (Ubuntu) " ubuntu-mate-artwork 0.4.12 new nelease [debdiff attached] " [Undecided,New] [14:31] didrocks, I really need this so I can rebuild the Ubuntu MATE 15.10 Alpha images. [14:31] didrocks, Laney is aware of this but I'm guessing he got busy. [14:34] flexiondotorg: hey, I didn't download the package yet, but there is no .install? You copy them in the right dir yourself in debian/rules? [14:35] didrocks, The .install for ubuntu-mate-artwork-common was present in 0.4.11 [14:36] ah, you just forgot the declaration in debian/control [14:36] didrocks, But the entry in debian/control got nuked by an erroneous commit. [14:36] So, 0.4.12 just reinstates the control entry that should have been there all long. [14:36] didrocks, Thanks for looking :-) [14:37] flexiondotorg: yw! doing a quick build before uploading :) [14:37] didrocks, Cool. [14:37] go didrocks [14:37] flexiondotorg: I was having lunch. [14:37] Laney, well I know you're busy. [14:37] Laney, I done some smoke test for Ubuntu MATE. [14:38] Laney, But I want to rebuild and make sure this artwork and meta package stuff is all good too. [14:38] 'k [14:38] Laney, I assume that ubuntu-mate-meta will automatically promote from proposed when ubuntu-mate-artwork 0.4.12 is in the relese pocket? [14:39] laney@nightingale> rmadison -swily,wily-proposed ubuntu-mate-meta ~ ubuntu-mate-meta | 1.127 | wily/universe | source [14:39] laney@nightingale> ~ [14:39] it already did [14:40] Laney, Ah, great. [14:40] Laney, Thanks. [14:44] flexiondotorg: sponsored, and kudos for the trailing comma after the last depends :) [14:44] didrocks, I found wrap-and-sort :-) [14:44] didrocks, Thanks for helping out. [14:44] oh, wrap-and-sort is adding the trailing comma? NICE! :) [14:44] yw [14:44] wrap-and-sort -t -a [14:46] haha [14:46] I swear I didn't add the -t option to it. But that would have been the case if I thought about it |o| [15:49] infinity, any chance you can release the horizon fixup (bug 1476417) to updates? it LGTM [15:49] bug 1476417 in horizon (Ubuntu Trusty) "[SRU] FloatingIpManager in neutron.py missing is_supported method" [Critical,Fix committed] https://launchpad.net/bugs/1476417 [15:49] pretty please :-) [16:24] Laney, ubuntu-mate-artwork 0.4.12 is now in the released pocket :-) [16:25] Laney, If I rebuild the iso images will the build pick up that new version? Or is there something else I need to wait for? [16:25] flexiondotorg: If rmadison shows you the new version in wily then it'll get that [16:26] * flexiondotorg goes to learn what rmadison is and how to use it. [16:26] I gave you an example line just there ^^^ [16:27] * flexiondotorg knows rmadison. Whoa. [16:27] It queries a remote machine to tell you about package versions [16:27] Laney, Thanks. rmadison still shows 0.4.10. So I'll wait. [16:28] nod [19:25] jamespage: Done. [19:32] Riddell, wxl How is your 15.10 Alpha 2 testing going? [19:35] flexiondotorg: Speaking for Riddell, good :) tested lots yesterday, no crucial problems found. [19:36] lordievader, Excellent. I've found myself in the same happy situation with Ubuntu MATE. One note worthy issue but noth critical :-) [19:37] * flexiondotorg makes mental note to contact lordievader tomorrow. [19:38] I do have one problem though, since the Kubuntu team is away at Akademy I volunteerd to do the lead on this one. But as of yet I do not have the rights to make the image ready... :( [19:39] lordievader: You can just tell Laney your images are ready and he can mark them. [19:40] Oke, I will remember that. Going to test some more tommorow. Thanks :) [20:27] lordievader, Looks like I could also make you image as ready when you get to that point :-) [20:34] Ah, cool. Then I'll bug one of you two tommorow about it ;) [20:34] flexiondotorg: ^ [20:34] lordievader, Sure, no problem :-) [20:35] lordievader, I owe Riddell a favour or three [20:37] :) [21:18] infinity: seems something is a bit off in the *lts-vivid X bits still https://bugs.launchpad.net/system76/+bug/1479524 [21:18] Launchpad bug 1479524 in totem (Ubuntu) "Totem Crashes at launch from missing libwayland-egl" [Undecided,Confirmed] [21:19] that's with todays 14.04.3 daily ISO, sha1sum 61afb95256980077b41415f2986ee75d2b3222cd [21:19] jderose: So something has an undeclared dep? Lovely. [21:19] tjaalton: Around? [21:22] jderose: So, (minus version bumps, obviously), this is the delta from .2 to .3: http://paste.ubuntu.com/11962290/ [21:23] jderose: Pretty clearly missing that one library, but I assumed this was intentional on the part of the X maintainers, so we'll have to sort out why. :P [21:26] infinity: gotcha. while i have you, do you know why there is no "libegl1-mesa-drivers-lts-vivid" package to replace "libegl1-mesa-drivers-lts-utopic"? is this deliberate or a goof? [21:27] So, looks like libopenvg1-mesa and libegl1-mesa-drivers legitimately no longer exist in the new mesa. [21:27] But libwayland-egl1-mesa-lts-vivid definitely exists, it's just that nothing pulls it in. [21:28] jderose: newer mesa Provides mesa-drivers. [21:29] jderose: So, I guess whatever was in that package was pulled in. [21:29] infinity: so something that truly does depend on libwayland-egl1-mesa-lts-vivid hasen't properly declared it as such... and after that's fixed, it will fix the ISO manifest automatically? [21:29] gotcha, thanks [21:30] And it was drivers that depended on wayland, so I guess that dependency needs to move around a bit. [21:30] (i don't know much about the ISO building process BTW, so sorry if that's a dumb/obvious question) [21:30] ah, gotcha [21:30] jderose: Yeah, this isn't something we should hack around in the ISO mastering process, if a package is legit missing a dep, we should fix it. :) [21:30] agreed :) [21:31] A bit curious that this wasn't an issue with vivid, though... [21:31] Unless the backport broke the deps a bit. [21:31] * infinity goes to look at the vivid manifest. [21:33] Hrm, *something* pulled it in in vivid. [21:34] Wait. I've confused myself. [21:38] Ahh, it's pulled in incidentally in vivid by gtk depending on it. [21:38] Which clearly won't be true in trusty. [21:42] jderose: Can you reproduce that bug and verify that installing libwayland-egl1-mesa-lts-vivid fixes it? [21:47] infinity: sure, just a sec... [21:50] infinity: yup, `apt-get install libwayland-egl1-mesa-lts-vivid` fixes it [21:54] jderose: Alright. We'll either get it fixed in mesa, or I'll pull some tricks, but we'll figure it out. [21:55] infinity: awesome, thanks! :) [22:00] tjaalton: When you pop your head in, please have a look at https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1479524 [22:00] Launchpad bug 1479524 in mesa-lts-vivid (Ubuntu Trusty) "Totem Crashes at launch from missing libwayland-egl" [Undecided,Confirmed] [22:02] RAOF: Or you ---^ [22:03] Oh, hrm. I used to install libegl1-mesa-drivers manually for lts-utopic. Maybe you'll both tell me I should just install this manually now instead. [22:05] * infinity grumps and admits that's probably the answer he'll be given. [22:05] But we'll see. [22:12] There are a lot of packages related to KDE, which have been _not_ yet migrated from -proposed. e.g. kf5unitconversion, is there any blacklist for such packages? [22:13] That seems to fail Occam's Razor [22:13] Also, I don't see kf5unitconversion in proposed... [22:13] So you might need to be a bit more specific. [22:13] kunitconversion? [22:13] Much easier to actually look at http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html [22:13] infinity: yes, kunitconversion, sorry [22:14] Regression in the kdelibs4support autopkgtest [22:15] Dunno if that actually has anything to do with kunitconversion, I haven't unpicked that; but it would probably be easier to make the tests pass than to invent conspiracy theories about blacklists :-) [22:15] cjwatson: Conspiracies are more fun. [22:16] infinity: when you say "I used to install libegl1-mesa-drivers manually for lts-utopic", do you mean as per the instructions here - https://wiki.ubuntu.com/Kernel/LTSEnablementStack [22:16] There is the facility to block packages, but if that were in use then you would see it logged on the above page [22:17] https://wiki.ubuntu.com/ProposedMigration has overall documentation [22:17] infinity: or do you mean in terms of the ISO mastering [22:17] Oh, and there are a bunch of other problems, because kunitconversion needs ki18n and that has a couple of other autopkgtest regressions [22:19] jderose: I mean for the livefs mastering. [22:19] cjwatson: I thought you were sleeping. [22:20] I sure am, I type by telepathy. [22:23] infinity: okay, gotcha. just to make sure i'm understanding things correctly, totem should in fact depend on libwayland-egl1-mesa[-lts-*], either directly or indirectly, right? like if you installed from the server ISO, the expectation is that `apt-get install totem` would do something sane, in theory yield a workable totem install? [22:24] jderose: I doubt it's totem itself that's trying to load that library. [22:24] jderose: Odds are it's mesa's fault. [22:25] jderose: Oh, you did say "or indirectly". So, yeah, I'd imagine that mesa has an undeclared dependency there because someone was trying to be overly clever with a package split and didn't notice the consequence. :P [22:26] jderose: Alternate fix would be to make whatever's dl()opening that library be more conditional and less violently faily. [22:26] Anyhow, the band-aid solution might just be for me to pre-install it, as I did for mesa-plugins in .2 [22:26] We'll see. [22:27] jderose: I'll have a healthy argument with the X folks and have it fixed -- one way or another -- by tomorrow. [22:27] infinity: okay, gotcha. for me the ISO/livefs build process is still much mystery sauce, so i'm just trying to understand things a bit better. thanks for graciously humoring my questions! :D [22:29] jderose: In an ideal world where all packages behave, the livefs build process should just be "apt-get install ubuntu-minimal ubuntu-standard ubuntu-desktop" && take package list && "apt-get install ubuntu-live" && take new package list, so we have install/live diff, compress and ship. [22:29] jderose: The world isn't always entirely ideal. But we aim for it. :P [22:31] infinity: thanks for the pseudo-code there... that hugely, hugely helped me understand the process. [22:31] and it's good to have ideals to strive for, even if you don't always reach them :) [22:51] * jderose catches the bus [23:03] Could somebody have a look at my apport SRU in the vivid queue? [23:14] bdmurray: What's the magic word? [23:16] bdmurray: Pretty sure your bug ref is bogus. [23:28] infinity: hmmph, thanks [23:30] infinity: could you please do me a favor and take a look at the nginx sru in the trusty queue? That's a fairly-easy-to-reproduce bug, and init failing because it can't parse pidfile is *bad*... no rush, though, i'm fine waiting for a few days longer, since I use the nginx PPAs on my trusty systems. others, unfortunately, are still hit by this. [23:30] if you're busy i'll wait :0 [23:37] teward: Can you fix your changelog to remove the trailing " *\n"? [23:38] teward: Not that that's a problem, but it's icky and shows a lack of attention to detail. :P [23:39] teward: Also, the reference to "debian/control:" seems wrong, that's not the file you changed... [23:39] infinity: I've reuploaded apport. [23:41] infinity: reject, i'll reupload [23:41] infinity: i'll make those fixes :) [23:50] ehhh, i don't need to increment the version again do I, given that it was rejected...? [23:50] * teward may have made a failure if it needs another version number bump >.< [23:50] teward: No, you don't need to the bump the version since it was never published. [23:50] teward: You d... What he said. [23:52] bdmurray: that's what i thought, but i've failed in the past :) [23:52] the headache of staring at ESXi's command line, coupled by manually rebuilding two VMs is draining my brain :) [23:54] that one should look better