[01:04] RAOF: sphinx is an interesting SRU, it's reached its 7 days now, I'd like it released to -updates so that webkit2gtk updates will pass their autopkgtests without manual intervention [01:05] but, there are rdepends that now fail their autopkgtests but it doesn't look like it's because sphinx changed in this SRU [01:11] Ok, I'll check it out. [01:12] Once I work out why no internet! [01:34] -queuebot:#ubuntu-release- Unapproved: gnome-software (yakkety-proposed/main) [3.20.1+git20170509.0.8292905-0ubuntu1 => 3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.10.1] (ubuntu-desktop) === maclin1 is now known as maclin [01:35] So many Xenial SRUs that could be released if only Yakkety failures were resolved... :( [01:36] Woot! [01:36] Now with a working Cat5 cable! [01:44] -queuebot:#ubuntu-release- Unapproved: gnome-software (xenial-proposed/main) [3.20.1+git20170509.0.8292905-0ubuntu1~xenial1 => 3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1] (ubuntu-desktop) [03:24] whenever possible, it'd be much appreciated to get a sponsor for bug 1683076 [03:24] bug 1683076 in swift (Ubuntu Xenial) "Swift-storage dies if rsyslog is stopped" [Critical,New] https://launchpad.net/bugs/1683076 [06:19] -queuebot:#ubuntu-release- Unapproved: swift (xenial-proposed/main) [2.7.1-0ubuntu1 => 2.7.1-0ubuntu1.1] (openstack, ubuntu-server) [06:21] -queuebot:#ubuntu-release- Unapproved: swift (trusty-proposed/main) [1.13.1-0ubuntu1.2 => 1.13.1-0ubuntu1.3] (ubuntu-server) [07:12] -queuebot:#ubuntu-release- Unapproved: telegram-desktop (zesty-proposed/universe) [1.0.29-1 => 1.0.29-1ubuntu1.17.04.1] (no packageset) [10:41] -queuebot:#ubuntu-release- Unapproved: accepted netcfg [source] (xenial-proposed) [1.135ubuntu4.3] [12:17] -queuebot:#ubuntu-release- New binary: debian-med [amd64] (artful-proposed/universe) [3.0.1ubuntu1] (no packageset) [12:41] is britney on vac today? [12:42] hmmm [12:43] ginggs, possible it is less britney and more the publisher ... hmmm [12:56] publisher doesn't seem to be working, I've been waiting over an hour and a half now [12:58] publisher you had one job [13:02] yeah the publisher is sad, people are looking [13:04] Yeah, override generation got stuck for some reason. I killed the stuck job and am keeping an eye on it. [13:07] thanks [13:10] * sil2100 was waiting for a signed kernel to publish since the morning [13:13] * mdeslaur bribes publisher with plate of fancy cakes [13:13] Do feel free to mention unusual-looking delays :) [13:14] yeah it had gotten to 5 hours since i'd seen anything change, 3 hours i can imagine kde making :) [13:17] ah! the cakes worked :) [13:17] thanks cjwatson [13:19] with a bit of luck, soon the only things blocking the r-base migration will be r-cran-spatstat on armhf and s390x, tests segfault with 'memory not mapped'. could we run these tests on large instances, please? [13:20] there are no instances for either of those arches. [13:20] the tests are run inside lxd/lxc containers on those architectures [13:21] xnox: but can those containers run on large instances? i seem to recall this working previously [13:40] ginggs, these are containers running on physical hardware.... [13:40] baremetal... they are not "instances" that one can "resize" =) [13:40] * xnox wishes we could just "resize" physical servers =) [13:41] it is possible those tests get blocked by security policies of the container. [13:42] xnox: so would adding r-cran-spatstat to big_packages not have any effect on armhf and s390x? [13:44] i don't have access to do that, or check what the effect would be. [13:44] Laney, ^ ? [13:46] that's not a thing [13:47] xnox, Laney: thanks, i must be confused [13:47] it's a thing for cloud but not for those arches [13:49] -queuebot:#ubuntu-release- Unapproved: isc-dhcp (trusty-proposed/main) [4.2.4-7ubuntu12.9 => 4.2.4-7ubuntu12.10] (core) [13:53] -queuebot:#ubuntu-release- Unapproved: isc-dhcp (xenial-proposed/main) [4.3.3-5ubuntu12.6 => 4.3.3-5ubuntu12.7] (core) [14:03] rbasak, good day, I just uploaded isc-dhcp for Trusty and Xenial in their respective upload queues, could you please have a look and make them start building in -proposed (if all the criteria are meet) ? [14:04] arges, ^^ [14:06] slashd: I can take a look at those if others are busy [14:07] rbasak: taking those if you're ok with that ^ [14:09] hm, ok, I see rbasak was handling this before, so maybe I should leave it to him after all, since he has all the context === acheronuk is now known as acheronUK [14:14] sil2100, ack, yeah let's see if rbasak will take it or not since he know all the context of it [14:14] sil2100, tks for offering [14:15] slashd, sil2100: I'll take a look. If it's identical to what I reviewed, then I only need a cursory check. [14:42] slashd: I appreciate the fixing up of the descriptions and changelog wrapping etc. [14:42] slashd: it'd be nice if you could control your editor to avoid extra trailing whitespace everywhere though. It's ugly and my syntax highlighter is showing red everywhere. [14:47] rbasak, will pay attention to that [14:47] slashd: also the Trusty debian/changelog is going >80 characters [14:48] and you have tabs in there [14:48] set list lcs=tab:»·,trail:· :-) [14:48] rbasak, weird let me check [14:51] rbasak, want me to fix the >80 character ? and tabs ? [14:52] slashd: yes please. That's for Trusty. Xenial's wrapping is OK, and the trailing whitespace I can cope with. [14:53] rbasak, so you'll reject Trusty ? and I'll re-upload it ? or I can overwrite the actual one ? [14:53] You can re-upload over the top. I'll reject the old one, but that doesn't block the upload of your replacement. [14:53] rbasak, so no problem keeping the same pkg version ? just to make sure [14:54] slashd: correct. Same version. Just edit the changelog entry in-place and reupload. [14:54] rbasak, ok I'll do the modification and re-upload in the next hour tks [14:54] dput will reject unless you delete the .upload file first. [14:54] rbasak, right [14:55] -queuebot:#ubuntu-release- Unapproved: rejected isc-dhcp [source] (trusty-proposed) [4.2.4-7ubuntu12.10] [15:30] -queuebot:#ubuntu-release- Unapproved: systemd (zesty-proposed/main) [232-21ubuntu3 => 232-21ubuntu4] (core) [15:53] rbasak: could you reject grub2 2.02~beta3-4ubuntu2.1 from the zesty queue? [15:53] (please) [15:53] leave grub2-signed; it's still good, but grub2 is missing a bit. [15:54] -queuebot:#ubuntu-release- Unapproved: rejected grub2 [source] (zesty-proposed) [2.02~beta3-4ubuntu2.1] [16:05] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [amd64] (xenial-proposed/main) [4.10.0-22.24~16.04.1] (kernel) [16:06] apw, could the SRUs for the #1618463 be deleted? the proposed fix is not actually needed, as the software works correctly. The bug itself is invalid, as the bug is between chair and keyboard as was pointed out to us by the vendor. [16:07] i will be SRUing revert into zesty, and already uploaded revert into artful. [16:07] or shall i just trump current SRU with a revert, + the new bugfixes we do need to fix? [16:07] xnox, which package is that ... [16:07] s390-tools in xenial-proposed and yakkety-proposed [16:10] xnox, gone [16:10] whoop whoop. [16:16] -queuebot:#ubuntu-release- Unapproved: accepted postgresql-9.3 [sync] (trusty-proposed) [9.3.17-0ubuntu0.14.04] [16:33] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [amd64] (xenial-proposed) [4.10.0-22.24~16.04.1] [16:44] rbasak, re-upload for Trusty [16:45] -queuebot:#ubuntu-release- Unapproved: isc-dhcp (trusty-proposed/main) [4.2.4-7ubuntu12.9 => 4.2.4-7ubuntu12.10] (core) [18:22] -queuebot:#ubuntu-release- Unapproved: accepted network-manager [source] (zesty-proposed) [1.4.4-1ubuntu3.1] [18:32] would someone please review r-bioc-genomeinfodbdata in artful NEW? it only contains data files that were shipped in r-bioc-genomeinfodb previously [18:36] ginggs: no, but I will wave it through as a Debian sync :) [18:37] slangasek: handwaving accepted, thanks [18:37] -queuebot:#ubuntu-release- New: accepted r-bioc-genomeinfodbdata [amd64] (artful-proposed) [0.99.0-1] [19:41] -queuebot:#ubuntu-release- Unapproved: lxd (xenial-proposed/main) [2.13-0ubuntu3~ubuntu16.04.1 => 2.0.10-0ubuntu1~16.04.1] (edubuntu, ubuntu-server) [20:31] -queuebot:#ubuntu-release- Unapproved: grub2 (zesty-proposed/main) [2.02~beta3-4ubuntu2 => 2.02~beta3-4ubuntu2.1] (core) === sergiusens_ is now known as sergiusens [20:46] slangasek, infinity: Sooooo lubuntu-next livefs building was FINALLY successful, but it's failing because of the following... I assume there's a place that I specified the location for this (and it's incorrect), orrr is it built-in tooling that's being fun? [20:46] * Fetching branch of http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/lubuntu-next.artful/ [20:46] bzr: ERROR: Not a branch: "http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/lubuntu-next.artful/". [20:46] ! Could not open STRUCTURE from checkout of (any of): [20:46] tsimonq2: I am only a bot, please don't think I'm intelligent :) [20:46] ! http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/lubuntu-next.artful [20:46] tsimonq2: I am only a bot, please don't think I'm intelligent :) [20:46] * tsimonq2 kicks ubot5 "{ [20:46] *:P [20:47] tsimonq2: where does that error happen? AFAIK the correct branch is lp:~lubuntu-dev/ubuntu-seeds/lubuntu.artful/ [20:47] slangasek: http://people.canonical.com/~ubuntu-archive/cd-build-logs/lubuntu-next/artful/daily-live-20170524.log [20:48] Actual file: [20:48] CalledProcessError: Command '['/srv/cdimage.ubuntu.com/germinate/bin/germinate', '--seed-source', 'http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/', '--mirror', 'file:///srv/cdimage.ubuntu.com/scratch/lubuntu-next/artful/daily-live/germinate/', '--seed-dist', 'lubuntu-next.artful', '--dist', 'artful,artful-security,artful-updates', '--arch', 'amd64', '--components', 'main', [20:48] '--no-rdepends', '--bzr']' returned non-zero exit status 1 [20:48] afaict that's called from: [20:48] File "/srv/cdimage.ubuntu.com/bin/../lib/cdimage/build.py", line 758, in build_image_set_locked [20:48] germination.run() [20:49] slangasek: And yes, the branch you said is the correct one. [20:50] tsimonq2: I believe you need to patch lib/cdimage/germinate.py:seed_sources() in lp:ubuntu-cdimage [20:50] slangasek: ack [20:51] tsimonq2: and also seed_dist() [20:51] slangasek: Ok. And also, do I have access to rebuild lubuntu-next images, or is that something you guys have to do on the ~core-dev/Archive Admin side? [20:53] tsimonq2: rebuilds are triggered through iso.qa.ubuntu.com; per-flavor product owners should have access to rebuild [20:54] I don't know if you currently have access or not, I would have to dig in to see and I'm currently in a meeting [20:57] slangasek: It doesn't look like it's even on iso.qa.ubuntu.com... Any chance you could dig in when you have a min? :) [20:58] That being said, we don't even have artful images on there yet... [21:01] http://iso.qa.ubuntu.com/qatracker/milestones/376/builds is there [21:01] Oh... [21:01] Weird [21:01] Didn't see it on my end... [21:01] slangasek: But yeah, no Lubuntu Next :) [21:02] slangasek: fwiw it isn't really something I need RIGHT NOW, but as soon as we have working Lubuntu Next images, I'd certainly like access. [21:02] s/access/access to rebuild/ [21:10] slangasek: Would you be OK with me explicitly specifying pattern in seed_sources, or do you need me to actually put in the functionality allowing for multiple seeds at one bzr branch? [21:10] :P [21:11] tsimonq2: there should be existing examples there that you can crib from [21:14] slangasek: That isn't the case here. [21:14] slangasek: This is what's modified in the if/else code: pattern = "http://bazaar.launchpad.net/~%s/ubuntu-seeds/" [21:14] slangasek: It looks like it just takes the project name and appends it on the end. [21:15] slangasek: Am I mistaken here? [21:15] tsimonq2: the appended part is why you need to also change seed_dist() [21:16] slangasek: Ahhhh ok, yeah, that makes sense. [21:20] slangasek: https://code.launchpad.net/~tsimonq2/ubuntu-cdimage/lubuntu-next-germinate/+merge/324571 [21:23] tsimonq2: I've done all the setup of lubuntu-next as a project on the ISO tracker, but I don't see anything in the web ui to let me add people to groups and I don't recall where else that might live. I think we'll need to get stgraber's help [21:24] slangasek: Well afair flocculant did Ubuntu Budgie's, so he might know? [21:24] slangasek: it's rather well hidden [21:24] ohai stgraber :D [21:24] nvm flocculant [21:24] tsimonq2: 'elif project == "lubuntu" or "lubuntu-next"' is written 'elif project in ("lubuntu", "lubuntu-next")' (cf the kubuntu-plasma handling above) [21:25] slangasek: so looks like you tied Lubuntu Next to the "lubuntu release" role, so that should actually be all good already [21:25] stgraber: we don't think tsimonq2 is in that role [21:25] or we don't know [21:25] I am. [21:25] oh [21:25] I can rebuild lubuntu images [21:25] you didn't say ;) [21:25] That happened as of... February something? [21:26] "lubuntu release" maps to ~lubuntu-product-managers on launchpad [21:26] that's transparent [21:26] slangasek: http://iso.qa.ubuntu.com/admin/config/services/openid_teams if you're admin enough to access :) [21:26] Well then consider this my indication... I'm Lubuntu Release Manager as of https://lists.ubuntu.com/archives/lubuntu-devel/2017-February/000968.html and should have all the relevant permissions if wxl didn't screw anything up ;) XD [21:27] tsimonq2: branch merged with the above adjustment, and deployed; you should be able to try a respin now [21:27] slangasek: QA products are tied to Drupal roles which are then tied to OpenID roles coming from SSO that are themselves LP teams [21:27] slangasek: ack [21:27] so yeah, not the easiest thing to track down :) [21:27] stgraber: yeah, I can't see that link. who all are the admins and why is it not a 1:1 for the nusakan admins? [21:28] Hmm, why wouldn't http://iso.qa.ubuntu.com/qatracker have Artful yet? [21:28] hmm, ubuntu release is linked to the "ubuntu iso admin" role, that should have been enough... [21:28] tsimonq2: it does, look at the bottom :) [21:28] stgraber: Oh... why... :P [21:29] tsimonq2: sorting is hard [21:29] stgraber: heh [21:29] stgraber: I got that :P [21:30] * tsimonq2 sips more coffee [21:30] slangasek: try logging out and back in, being in ~ubuntu-release should now get you full admin [21:31] stgraber: looks good, thanks! [21:32] well I mean, the UI makes me sad [21:32] but I definitely have more privs now ;) [21:32] :) [21:34] stgraber: what url should actually show me the 'lubuntu release' -> ~lubuntu-product-managers mapping? [21:39] slangasek: http://iso.qa.ubuntu.com/admin/config/services/openid_teams [21:39] stgraber: ta [21:49] slangasek: Any success so far? :) [22:03] tsimonq2: success with what? I'm done and turned it over to you to trigger rebuilds :) [22:04] slangasek: Uhm... but where is it? [22:04] slangasek: I don't see it on http://iso.qa.ubuntu.com/qatracker/milestones/376/builds [22:04] slangasek: Maybe I just don't know all the ways to trigger a rebuild? :P [22:06] It won't be on the tracker until it's had at least one successful run. [22:06] tsimonq2: ok; ISTR having this before, where you can't 'rebuild' unless there's first been a successful build right [22:06] so I'll retrigger from my end [22:07] Ack [22:07] infinity, slangasek, stgraber: Gracias por la ayuda. :) [22:08] tsimonq2: no hay de que (y cuidado con la lengua en este canal si no pretendes practicar de veras) [22:09] :) [22:09] * infinity wonders if he accidentally joined #ubuntu-release-es [22:12] slangasek: Heyyy, yo aprendiendo Español en mi escuela. :P [22:12] infinity: #ubuntu-rel-es por favor [22:13] infinity: Necesitamos #ubuntu-release-es porque Español es divertido. :P [22:14] * tsimonq2 stops speaking Spanish for now :P [22:14] tsimonq2: ¿cuánto tiempo suele tardar el construyo en fallar? [22:14] slangasek: #ubuntu-rel-es-es? [22:15] Also, I love that there's an inverted interrobang called gnaborretni. [22:15] Though, I don't know how to compose it. [22:16] ⸘‽ [22:16] Ah-ha. [22:16] Just the inverse sequence. [22:19] slangasek: No sé... generalmente una hora y treinta minutos pero varía. [22:21] hmm eso es mucho [22:21] pero vale, esperemos [22:22] slangasek: infinity: I'm curious about sponsor logos appearing in slideshow source; could you give your 2 pesos on https://code.launchpad.net/~aaronhoneycutt/ubiquity-slideshow-ubuntu/artful/+merge/324285 ? [22:23] cyphermox: "2 pesos" lol [22:24] oh, I had failed to see it was even in a big file all together... yuck [22:24] ahoneybun: ^ [22:24] slangasek: No sé exactamente... soooo :P [22:25] (as in, usually people would complain that you muck with their trademark logos by putting them together, so I'd ask the sponsors directly...) [22:25] cyphermox: It's on kubuntu.org. I saw the discussion on the KC side about it and generally people were OK with it because it's already on the site... [22:26] being on the site is not the same as being in public source, and/or being in one large image. [22:26] But having Steve's and Adam's 2 pesos is probably a good thing, I agree. [22:26] cyphermox: Good point. [22:28] admittedly, IANAL, but trademark/copyright law is complex and fraught with peril [22:29] for this kind of thing, I rather be extra extra cautious [22:30] slangasek: Ohhhh... el construyo por livefs o todos? [22:32] slangasek: Porque mi estimacion es por todos los procesos... [22:33] slangasek: Your turn to fix the failure :P http://people.canonical.com/~ubuntu-archive/cd-build-logs/lubuntu-next/artful/daily-live-20170524.1.log [22:36] slangasek: (because it's on the ISO QA tracker side) [22:37] and needs the name adjusted, ack [22:38] tsimonq2: it does seem like the image built, at least [22:38] tsimonq2: and is oversized ;P [22:40] * infinity is trying really hard not to respond with "So's your mom". [22:40] tsimonq2: habiendo cambiado el nombre, lanzo de nuevo el construyo [22:41] cyphermox: which logos specifically are you concerned about / in what file? [22:42] I think he's referring to slideshows/kubuntu/slides/11_Sponsors.html [22:42] slangasek: Gracias [22:44] infinity: the .png that references appears to not be a file added as part of this diff? [22:44] slangasek: Dunno. I just pulled the merge and ran the slideshow test. [22:46] slangasek: http://lucifer.0c3.net/~adconrad/logos.png [22:46] slangasek: Because the best thing to do when one suspect a copyright violation is to make more copies. [22:46] lol [22:51] infinity: slangasek it's in the screenshot dir [22:51] sponsors-slide [22:51] it's all one image [22:52] ahoneybun: Are they free use logos? And are you violating anyone's weird trademark requirements (must have X amount of whitespace, can't be shown near a mark of someone who sell boneless chicken burgers, because boneless chickens are just plain wrong, etc)? [22:52] it's very common for logo policies to specify that logos need plenty of padding (they shouldn't be placed so closely to other logos) [22:52] tbh I did not look that up [22:52] like it almost looks like Launchpad is part of Linode in that screenshot [22:53] like I said tho it's all one image to take down [22:53] if it can't be included [22:55] I appreciate the sentiment (and I expect your sponsors would too), and we already give trademarks a pass on not needing to meet DFSG requirements for modification, but you should probably make sure you're respecting whatever licenses and requirements they have, so they see it as a Good Thing rather than an abuse of their mark. [22:55] I love -O3 on ppc64el :-/ [22:56] infinity: prehaps take it out for now and add it later in? [22:56] cyphermox: ^ [22:56] I'd like to get the new slides design in asap before a freeze or something [22:56] also test how they look on a live iso [22:58] that slide does look untidy :/ [22:59] like someone took a load of logo fridge magnets and threw them at a fridge door. and accepted where they stuck === Elleo_ is now known as Elleo [23:00] acheronUK: At least they're all right side up? That's some solid magnet-tossing skill right there. [23:01] infinity: lol. true [23:02] * acheronUK would have been obsessive enough to straighten then in place after throwing though [23:07] * Ukikie gives acheronUK a magnet, magnet:?xt=urn:btih:aee3499cb4276c6f15bed91705717cb2c02100b2&tr=http://torrent.ubuntu.com:6969/announce [23:16] cyphermox: pushed some text changes and removed the sponsors slide for now [23:22] ahoneybun: ack [23:22] (sorry, I went to cook and eat dinner) [23:32] * ahoneybun messes with his Nextcloud [23:37] Oh, wonderful. [23:37] The Lubuntu Next image boots... but has an "unsupported arguments" error, right after launching an unthemed Openbox session... [23:37] That'll be fun to fix ^.^ [23:39] Yeah, throw some theming on that Openbox session, it'll look pretty fantastic. [23:42] Ukikie: No, but right now it's literally Openbox with an error message... :P [23:54] thanks <3 cyphermox [23:54] it's uploading too, just a big tarball [23:55] tsimonq2: are you doing autologin? [23:55] I seem to recall some display manager had issues with a setup we used for autologin (though it was for oem) [23:57] also if you changed things, like the live session username, and the dm doesn't know about it, it would fail... so two things to look at for starters :) [23:59] I would expect things to work though, as casper just reads casper.conf, and livecd-rootfs knows how to write that.