[02:14] <tsimonq2> so do we have a progress update since I was last on? or is it pretty obvious?
[04:30] <pitti> infinity: ddebs should set themselves up, retracers and autopkgtests coming now
[04:30] <pitti> http://ddebs.ubuntu.com/dists/xenial/ -- yup
[04:33] <pitti> infinity: there's no britney for xenial yet either
[06:31] <pitti> infinity: xenial autopkgtest queues ready for business; but I stopped the ppc64el workers, see #u-devel
[06:34] <pitti> infinity: are you going to switch $DEFAULT_SERIES in britney1-ubuntu and set up britney, or want me to walk through it?
[08:24] <flocculant> slangasek: hi - could you look at the xubuntu core MP again, there are changes following your disapprove, we really want to get this in as soon as possible so we get as much cycle as poss to test it https://code.launchpad.net/~unit193/ubuntu-cdimage/xubuntu-core/+merge/268167
[08:24] <flocculant> thanks :)
[08:56] <Riddell> adios chicos, it's been a pleasure working with you, I don't expect I'll be going too far https://kubuntu.org/news/jonathan-riddell-stands-down-as-release-manager-of-kubuntu/
[08:59] <pitti> infinity, Laney: do you have a magic script to move over wily's proposed packages (except the new ones which got accepted today) over to xenial?
[08:59]  * pitti bbl
[08:59] <infinity> pitti: I don't have a magic script, I do it by hand, ish.
[09:49] <cjwatson> Riddell: Good luck
[09:51] <doko> just filed the ticket (#38) to create new chroots on the developer boxes
[09:53] <Riddell> thanks cjwatson :)
[10:14] <pitti> grep: /home/ubuntu-archive/public_html/proposed-migration/xenial/update_excuses.html: No
[10:14] <pitti> +such file or directory
[10:14] <pitti> cjwatson, infinity: ^ should I just go ahead and create that dir, or is there something more to it?
[10:14] <pitti> (cron mail on snakefruit)
[10:15]  * pitti mkdirs, what could possibly go wrong :)
[10:16] <Laney> will need to update the symlinks too
[10:16] <pitti> ah, is that manual? ok
[10:16] <Laney> AFAIK
[10:16] <pitti> but I'll wait with that until we actually have a report
[10:17] <pitti> Laney: I had assumed DEFAULT_SERIES=wily → DEFAULT_SERIES=xenial would do that
[10:17]  * pitti commits that
[10:18] <pitti> hah, infinity just beat me to it
[10:19] <infinity> pitti: Did your pkg-create-dbgsym upload break me? :P
[10:19] <infinity> https://launchpadlibrarian.net/222260532/buildlog_ubuntu-xenial-armhf.vim_2%3A7.4.826-1ubuntu1_BUILDING.txt.gz
[10:19] <pitti> infinity: wut?
[10:19] <infinity> ^-- That seems weird.
[10:20] <cjwatson> mkdir was unnecessary, p-m would've done that once it started running for the right series.
[10:20] <pitti> cjwatson: ah, ok
[10:20] <pitti> infinity: apparently so, meh; let me upload a revert, then I'll investigate
[10:22] <infinity> pitti: I removed 0.70 as well to hurry the process along.
[10:22] <pitti> infinity: ah, even better; then I don't even need to upload a revert, right?
[10:22] <pitti> ood, there's no python* package involved at all, which was the only case that this changed
[10:22] <infinity> pitti: That vim build concerns me, given that it succeeded on most arches, but not all, seems likely there's some sensitivity to parallelism or other raciness going on.
[10:23] <pitti> it smells more like this bug has been there for quite some time, and we've just been lucky (or retried the builds without much investigation)
[10:23] <infinity> pitti: Possibly.
[10:23] <infinity> pitti: Are we almost ready to move to the debhelper-based implementation and scrap ours?
[10:24] <pitti> infinity: I didn't look at that yet
[10:24] <pitti> infinity: but the debhelper one spits out *.debs, not *.ddebs, so I figure before we do that we need some rework in LP and ddeb-retriever
[10:24] <pitti> (which won't be a "ddeb"-retriever any more then)
[10:24] <infinity> pitti: Err, really?  I thought there was some back and forth on that and then it ended up being ddebs?
[10:25] <pitti> infinity: hm, then I didn't get that; I saw the discussion and had the impression they sticked to *.deb
[10:25] <infinity> pitti: I'm somewhat opposed to a non-policy-compliant deb-like thing being .deb
[10:25] <pitti> me too, but I think the argument was something like "similar to -dbg.deb" or so
[10:28] <infinity> pitti: Anyhow, if you're sure this bug can't possibly relate to 0.70, I can just copy it back in place.
[10:28] <infinity> I'm retrying that build with 0.70 right now.
[10:28] <pitti> infinity: it's very unlikely; the effective diff was
[10:28] <pitti> if [ "$pkgname" != "${pkgname#python}" ]; then
[10:28] <pitti>    <ignore>
[10:28] <pitti> but there is no python* binary in that vim build
[10:30] <pitti> infinity: indeed it looks like dh_strip and dh_gencontrol run in parallel for the same packages
[10:30] <infinity> pitti: Well, it should succeed/fail in ~7m.
[10:31] <pitti> indeed pkg-c-d is currently assuming that dh_strip runs before dh_gencontrol
[10:31] <infinity> pitti: Could be a parallelisation error in dh or vim, but I've never seen this before, so weird.
[10:32] <pitti> hm, debian/rules looks okay
[10:32] <infinity> Yeah, it looks pretty serial.
[10:32] <infinity> It exports MAKEFLAGS=-j, but that shouldn't suddenly mangle recipes within a target. :P
[10:35] <pitti> infinity: submitted bug 1509299 and attached the build log to it, as they tend to disappear on retries
[10:35] <ubot2> bug 1509299 in pkg-create-dbgsym "parallel build race condition between dh_gencontrol and dh_strip" [Undecided,New] https://launchpad.net/bugs/1509299
[10:36] <infinity> pitti: Ta.  The weird thing is that this wasn't isolated, that build failed on armhf *and* powerpc (succeeded on ppc on retry, armhf is still building).
[10:36] <infinity> pitti: Which seems weirdly frequent for a rare race we've never noticed before.
[10:36] <infinity> pitti: But maybe I'm just having an unlucky Friday.
[10:39] <pitti> ok, treating that as medium for now; /me looks at broken ddebs.u.c. indexes then
[10:45] <doko> infinity, pitti: it's a rules error
[10:45] <doko> the indep and arch targets are run in parallel
[10:46] <doko> I don't know if it's a make issue, or a rules issue, the export of the different DH_OPTIONS goes wrong. yeah for -j as the default in dpkg :-/
[10:47] <pitti> ah, that's why all the lines appear twice
[10:48] <infinity> Probably not dpkg's fault, he's setting MAKEFLAGS.
[10:48] <infinity> I can turn that into a PARALLELFLAGS and pass it explicitly just to the build target makes.
[10:48] <doko> yep, "because it should work", done without testing
[10:49] <pitti> ah, it never sets DH_OPTIONS=-a or -s
[10:49] <pitti> just -i
[10:51] <doko> anybody working on a dpkg merge?
[10:51] <infinity> I will, yes.
[10:51] <infinity> s/will/am/
[10:51] <doko> ta
[10:53] <infinity> pitti: Copying your package back in.
[10:54] <pitti> infinity: cheers
[10:54] <pitti> infinity: OOI, where do you copy it from?
[10:54] <infinity> copy-package -s xenial-proposed --to-suite=xenial-proposed --force-same-destination --silent --auto-approve -e 0.70 -b pkg-create-dbgsym
[10:54] <pitti> wow
[10:54] <pitti> you can copy deleted packages?
[10:55] <infinity> Yup.
[10:55] <cjwatson> sure can
[10:55] <pitti> neat
[10:55] <pitti> hm, britney still doesn't run, wth
[10:56] <pitti> I got another mail about the missing /home/ubuntu-archive/public_html/proposed-migration/xenial/update_excuses.html, so archive-reports clearly ran
[10:56] <pitti> but proposed-migration/code/b1/ wasn't pulled yet
[11:05]  * pitti pulls it manually and sees if that helps somehow
[11:06] <Laney> run-proposed-migration is supposed to do that
[11:06] <pitti> yeah, that's what I thought too
[11:06]  * Laney can see it right there
[11:07]  * pitti tries DISTRIBUTION=ubuntu SERIES=xenial run-proposed-migration
[11:07] <pitti> and sure enough that immediately exits
[11:08] <Laney> the STOP file
[11:08] <pitti> ah! proposed-migration/STOP  exists
[11:08] <Laney> :)
[11:08] <pitti> I guess leftover from yesterday?
[11:08] <infinity> Yep.
[11:09] <pitti> tail -f proposed-migration/log/xenial/2015-10-23/11\:08\:46.log
[11:09] <pitti> muuuc better
[11:09]  * pitti tosses in a 'h'
[11:09] <Laney> betterh
[11:09] <pitti> Laney: no; "better, haha!"
[11:14] <cjwatson> Right, I touched STOP yesterday to stop it doing stuff with wily
[11:14] <pitti> yay, 238 xenial test requests on all three arches
[11:15] <pitti> that'll keep stuff busy over the weekend :)
[11:15] <cjwatson> Hopefully it'll migrate base-files soon so that people stop complaining about launchpad-buildd recipes producing wrong versions
[11:15] <pitti> Not touching package due to block request by freeze (contact #ubuntu-release if update is needed)
[11:16] <pitti> (also, outstanding tests, but this needs unblocking too I figure)
[11:16] <infinity> Yeah, we might want to keep the block there for now, but unblocking base-files is sane.
[11:16]  * infinity does that.
[11:16] <cjwatson> Removing block-all source is on NRCP
[11:16]  * infinity does that after checking the diff.
[11:17] <cjwatson> infinity: looks like you did branch-livefses?
[11:17] <pitti> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html and *.yaml etc. is still wily, I'll adjust the symlinks
[11:17] <infinity> I did yesterday, yes.
[11:18] <infinity> doko: Your base-files merge dropped os-release from conffiles.
[11:19] <doko> infinity, intended
[11:19] <infinity> doko: ?
[11:19] <doko> moved to /usr/lib
[11:19] <doko> or is there a mistake?
[11:19] <pitti> oh, and /etc/os-release becomes a symlink?
[11:20] <cjwatson> http://bugs.debian.org/753658
[11:20] <ubot2> Debian bug 753658 in base-files "/etc/os-release has moved" [Normal,Fixed]
[11:20] <pitti> shoudln't it move to /lib then, as long as we still have separate /usr ?
[11:20] <infinity> Probably.
[11:20] <cjwatson> Eh, whatever; we have separate /usr but it's always mounted
[11:20] <cjwatson> AIUI
[11:21] <doko>   * Moved /etc/os-release to /usr/lib/os-release. Put a symlink pointing to
[11:21] <doko>     the new place. Thanks to Marco d'Itri for the report. Closes: #753658.
[11:21] <pitti> I got debian bug reports from people with separate /usr who didn't have an initramfs; not that I think that this is even remotely sane/supported, but just saying
[11:21] <pitti> yay for not being a conffile any more, though
[11:22] <infinity> doko: Also dropped a newline from /etc/issue accidentally.
[11:22] <doko> ouch
[11:24] <doko> pitti, so should that be move to /lib/os-release? is there a spec / documentation referencing /usr/lib/os-release?
[11:24] <pitti> doko: I read the debian bug now, should be fine
[11:24] <pitti> doko: indeed we mount /usr in the initramfs, so that's fine
[11:25] <pitti> doko: man os-release
[11:30] <infinity> Hrm.  Not convinced that symlink should be shipped in the package.
[11:30] <infinity> Seems like it should be written once in postinst.
[11:30] <infinity> So users can replace it with a file.
[11:31] <doko> why do you want it to be replacable?
[11:31] <infinity> Because /etc/os-release is for user overrides of /usr/lib/os-release
[11:31] <infinity> There's no point in having both locations if they're always identical.
[11:32] <infinity>        The file /etc/os-release takes precedence over /usr/lib/os-release. Applications should
[11:32] <infinity>        check for the former, and exclusively use its data if it exists, and only fall back to
[11:32] <infinity>        /usr/lib/os-release if it is missing.
[11:32] <doko> "/etc/os-release should be a relative symlink to /usr/lib/os-release, to provide
[11:32] <doko>        compatibility with applications only looking at /etc."
[11:32] <infinity> Yeah, I read that as "it should default to being a symlink", but I agree the doc is ambiguous between my paste and yours. :P
[11:33] <infinity> There's not much point in defining precedence, if they're always the same.
[11:34] <rbasak> They don't seem to have provided any rationale for having it available in the tree in both places.
[11:35] <infinity> rbasak: Except for the usual systemd/coreos rationale of
[11:35] <infinity> "/usr is immutable default configs, /etc is overrides"
[11:35] <infinity> Likely the only reason for os-release to also ship the symlink is because it used to live in /etc, so it needs backward compat with software that only looks there.
[11:36] <infinity> Unlike systemd units, etc, which we've expected in /lib from day one.
[11:36] <rbasak> It was supposed to be yet-another-standard-to-rule-them-all, and now we have two of them?
[11:37]  * rbasak is feeling grumpy
[11:37] <cjwatson> Never believe such claims.
[11:37] <cjwatson> Then you can be grumpy all the time rather than having your hopes inevitably dashed.
[11:38] <rbasak> Well, I never particularly believed it in the first place. But it would have been nice if they had thought of this before changing it and making everyone leave cruft everywhere.
[11:39] <rbasak> Given that moving it to /usr/lib won't benefit Debian, why move it at all?
[11:39] <rbasak> Might as well just keep it in /etc.
[11:39] <rbasak> (not that it matters as it's moved now)
[11:39] <rbasak> Then we could just skip straight to their fifth iteration when they decide on it.
[11:40]  * rbasak will stop ranting now.
[12:12] <xnox> rbasak: in clearlinux, we don't have /etc/os-release and have been fixing everything to start checking both locations. E.g. last discovery was docker, and the merge proposal to fix it is not yet upstream nor released.
[12:12] <xnox> infinity: systemd accepts units from /usr/lib, even on /lib enabled systems.... it's kind of freaky.
[12:13] <xnox> rbasak: i don't think os-release was for debian benefit...
[12:37] <rbasak> xnox: it's to have one standard everywhere. But now we have two standards everywhere. If /etc/os-release is the one required and more universally available, then I don't see any need to do anything different now.
[12:37] <xnox> rbasak: the os-release spec says: use /etc/os-release if present, otherwise check /usr/lib/os-release as well.
[12:37] <xnox> (well the updated spec, original only had /etc)
[12:38] <rbasak> xnox: deciding it should be somewhere else now doesn't necessarily mean that the spec has to be changed like it has been done.
[12:39] <xnox> rbasak: the change enables "thin" derivatives. With mostly identicaly /usr (read-only / atomic), yet enough custom stuff in /etc & e.g. /opt to warrant a change in os-release.
[12:39] <rbasak> xnox: the change goes beyond that. It only needed to be changed to say that /etc/os-release may be a symlink.
[12:40] <xnox> there is no requirement for it to be a symlink.... and in practice it shouldn't be a symlink. it should either be a different thing, or not exist at all.
[12:40] <xnox> and not everything supports symlinks....
[12:40] <rbasak> xnox: I didn't say that there was a requirement for it to be a symlink. Read what I said.
[12:41] <xnox> rbasak: sorry, then i don't understand. both old and new standard say nothing about whether or not it's a real file, or symlink somewhere else.
[12:41] <xnox> rbasak: and the change was not about symlinks, or moving locations. but splitting immutable & configurable parts. Previously it wasn't like that and rpm doesn't have sensible config file handling ;-)
[12:42] <rbasak> xnox: "both old and new standard say nothing". No, that's wrong. It says "/etc/os-release should be a relative symlink to /usr/lib/os-release..."
[12:43] <rbasak> xnox: I'm saying that this "should" is unnecessary. The spec only needed to be amended to say that /etc/os-release may be a symlink, and no changes in "shoulds" for OS implementors or changes in "shoulds" in how apps should read the file would have been necessary.
[12:44] <xnox> rbasak: the goal is to drop file from /etc. and make it muitable. what you are proposing whould not achieve that, especially on rpm systems which have broken config handling.
[12:44] <xnox> rbasak: as in on upgrade /etc/os-release.rpmNEW was written out without updating /etc/os-release -> not good =)
[12:44] <xnox> rbasak: at the moment we are in a transition period.
[12:45] <xnox> rbasak: this is /etc -> /lib mistake, as have been seen e.g. with udev.d rules. one would think, that history would be learned.
[12:46] <tsimonq2> xnox: how so?
[12:48] <xnox> tsimonq2: how so, what? udev past mistake? initially udev rules were only loaded from /etc cause it needs to be customizable and at early boot. Later, people did modify these, upstreams/upgrades rename things resulting in an utter mess. Hence udev rules got moved to [/usr]/lib location and /etc became just an overlay, for admin customizations. Segregating system defaults from admin customizations. If one doesn't segregate system & admin defaults,
[12:48] <xnox> there is no easy upgrade path.
[12:48] <xnox> tsimonq2: http://blog.surgut.co.uk/2015/03/boiling-frog-or-when-did-we-loose-it.html
[12:54] <tsimonq2> xnox: no, 07:44:47 AM < xnox> rbasak: at the moment we are in a transition period.
[12:55] <tsimonq2> xnox: first time seeing this end of things, so I am curious.
[12:56] <xnox> tsimonq2: once one no longer wants to support old tooling parsing /etc/os-release, one can and will drop such symlink.
[12:56] <xnox> tsimonq2: read the os-release man page. it does state said symlink is for backwards compat only.
[12:57] <tsimonq2> xnox: I didn't want to know about that issue at all :)
[12:57] <xnox> =)
[12:57] <tsimonq2> xnox: I just wanted to know where we are at
[12:58] <tsimonq2> xnox: what step are you guys on? https://wiki.ubuntu.com/NewReleaseCycleProcess
[13:01] <xnox> tsimonq2: i'm not doing it. wait for "open for development" email to ubuntu-devel-announce.
[13:01] <xnox> like last one, https://lists.ubuntu.com/archives/ubuntu-devel-announce/2015-May/001134.html
[13:02] <tsimonq2> oh
[13:03] <tsimonq2> xnox: so is that step 28? Inform #ubuntu-devel and ubuntu-devel-announce that the new release is now open for uploads, pointing to merge-o-matic output.
[13:03] <xnox> tsimonq2: no.
[13:04] <xnox> tsimonq2: i said, i do not know. hence assuming it is not open. it will be open for development, once the email is out. so wait for that.
[13:05] <tsimonq2> ok :)
[13:13] <cjwatson> tsimonq2: Waiting to make sure that autopkgtests have their lives sorted out sufficiently to be able to let stuff migrate to xenial, I think.
[13:13] <cjwatson> infinity: I guess once we see base-files migrate successfully, we can unblock the world and open?
[13:14] <tsimonq2> cjwatson: I know I am (maybe) gonna irk you, but what step is that?
[13:14] <cjwatson> tsimonq2: I don't remember.
[13:14] <cjwatson> It's not completely linear.
[13:15] <cjwatson> A lot of it is "make sure not to forget this stuff", not "must be done in exactly this order".
[13:15] <tsimonq2> ok :)
[13:16] <tsimonq2> cjwatson: so after xenial is unblocked, is that when it is marked as Development in Launchpad?
[13:16] <cjwatson> Yes
[13:16] <tsimonq2> cjwatson: and when the announcement is sent out?
[13:17] <cjwatson> I would assume so.
[13:17]  * tsimonq2 whispers to himself, "step 28"
[13:18] <tsimonq2> ◔ ⌣ ◔
[13:41] <pitti> infinity: AFAICS everything on http://people.canonical.com/~ubuntu-archive/proposed-migration/wily/update_excuses.yaml should be moved to xenial; want me to do that?
[13:41] <pitti> (I thought I saw some "real" wily SRUs being accepted, but openjdk-9 is the most recent one and not an SRU)
[14:11]  * pitti moves wily-proposed cruft to xenial-proposed, to clear up the way for SRUs
[14:19] <infinity> pitti: I'm doing it now.
[14:19] <cjwatson> ^- log4cxx should help base-files migrate
[14:20] <infinity> cjwatson: Also, I'm reminded every 6 months that I really want a copy-package --with-or-without-binaries-yknow-whatever option. :P
[14:21] <pitti> infinity: already copied to xenial
[14:21] <infinity> pitti: Oh.
[14:21] <pitti> infinity: I'm removing them from wily-proposed now
[14:21] <pitti> infinity: xenial-proposed of course, sorry
[14:21] <infinity> pitti: Did you watch carefully to make sure they all succeeded?
[14:21] <infinity> pitti: In that ones with binaries need -b and ones without will fail with -b.
[14:22] <pitti> I ran with -b, and got "1 package successfully copied." on the FTBFS ones
[14:22]  * infinity raises brow.
[14:22] <pitti> but Laney says there are some rejections, checking
[14:22] <infinity> Did someone fix that since wily opening?
[14:22] <pitti> Copy candidates:
[14:23] <pitti>  node-srs 0.4.8+dfsg-2 in wily
[14:23] <infinity> pitti: Oh.  copy-package told you that.
[14:23] <pitti> Candidate copy target: https://api.launchpad.net/devel/ubuntu/+archive/primary
[14:23] <pitti> 1 package successfully copied.
[14:23] <pitti> e. g. that
[14:23] <infinity> pitti: copy-package lied.
[14:23] <pitti> yeah, it might be lying
[14:23] <infinity> pitti: You probably have a ton of mail.
[14:23] <infinity> pitti: Also, you might want to use --silent, no need to spam the world with this. :P
[14:24] <infinity> pitti: But I'll let you sort the mess now that you started.
[14:25] <infinity> (Welcome to "things that look simple when someone else does them")
[14:25] <pitti> yep
[14:25] <pitti> heh :)
[14:25] <pitti> yeah, will use --silent next time, sorry
[14:27] <cjwatson> I've made copy-package's output a little less misleading.
[14:27] <cjwatson> (It'll say "1 copy requested." now)
[14:27] <pitti> thanks
[14:28] <pitti> so I'll re-copy the rejected ones with --silent and without -b
[14:28] <cjwatson> And yeah, I should fix the copier at some point ...
[14:29] <cjwatson> pitti: I'm sure http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#base-files should be showing log4cxx/amd64 has "Always failed" by now - it's been at least a few cycles
[14:29] <cjwatson> Oh, though I guess it could have been requested again
[14:30] <cjwatson> pitti: Do you have any way to push dict-foldoc and log4cxx up the queue?  I believe we're only waiting for those to get base-files migrated.
[14:30] <cjwatson> And then hopefully we can unblock and open.
[14:32] <pitti> cjwatson: no, didn't run yet (click on the individual packages, you won't see a result from yesterday or today), e. g. http://autopkgtest.ubuntu.com/packages/d/dict-foldoc/xenial/amd64/
[14:32] <pitti> the older ones are the latest successful ones I copied from wily
[14:32] <pitti> to be able to continue to track "regression" vs. "always failed"
[14:32] <pitti> queues are 181 on amd64, 194 on i386
[14:33] <pitti> and lcy01 is still only running with max 5 instances, as with anything more it keeps falling over :(
[14:33] <pitti> ok, copied the FTBFS ones
[14:34] <pitti> e. g. https://launchpad.net/ubuntu/+source/mpdris2/+publishinghistory
[14:36] <infinity> pitti: Kay.  I have a script here to check both match.  So, after a publisher run, I can verify that, then we can go on a deleting spree.
[14:36] <infinity> pitti: Unless you trust yourself enough that you've started deleting already. :P
[14:36] <pitti> infinity: err, sorry, I already did
[14:36] <infinity> Heh.
[14:36] <pitti> I spot-checked some 5 packages, and they looked ok
[14:37] <pitti> we'll get almost all of them back during autosyncs too, but there are a few -ubuntuN ones, so I mostly checked those
[14:37] <pitti> but also e. g. https://launchpad.net/ubuntu/+source/bup/+publishinghistory
[14:38] <infinity> pitti: I'll double-check for paranoia in a bit.
[14:38] <pitti> infinity: http://paste.ubuntu.com/12903087/ is the package list of everything that was in wily-proposed
[14:38] <cjwatson> pitti: log4cxx ran today, but a bit earlier perhaps.
[14:38] <cjwatson> So maybe your copies.
[14:38] <infinity> pitti: Yup, I have the same list.
[14:39] <pitti> cjwatson: no, I only copied the latest successful result, no failed ones (as they don't serve any purpose)
[14:39] <pitti> cjwatson: the point is just that if we get a failure as the first "real" xenial run we need to tell apart regression vs "always failed", so I "seeded" xenial with the latest "pass"
[14:40] <pitti> infinity: let's see for how much longer we'll drag cairo-5c along :)
[14:40] <cjwatson> I'm failing to wrap my head around that today, but I guess I don't in fact need to know :)
[14:41] <pitti> cjwatson: ok, sorry; indeed http://autopkgtest.ubuntu.com/packages/l/log4cxx/xenial/i386/ is a valid run and britney should consider it
[14:41] <infinity> pitti: I feel like it's the real champion here.
[14:41]  * pitti checks
[14:41] <infinity> Oh.  Did someone bring forward the britney history?
[14:41] <pitti> infinity: how do you mean?
[14:41] <infinity> Erk.
[14:42] <pitti> infinity: we didn't copy the wily autopkgtest results if you mean that, which is probably the reason for a good chunk of the ~ 300 test requests that we got after opening
[14:42] <pitti> infinity: but at least python3-defaults, debhelper etc. are genuine new requests
[14:42] <cjwatson> Oh, Dates ...
[14:43] <infinity> cjwatson: Fixed.
[14:43] <cjwatson> infinity: you fixed Dates, or something else?
[14:43] <infinity> Dates.
[14:43] <cjwatson> That was quick.
[14:43] <infinity> I have a way with shells?
[14:43] <pitti> oh, for keeping the 523 days or whatnot of cairo-5c? :-)
[14:43] <pitti> can't lose that record!
[14:44] <cjwatson> Well, I assumed it couldn't just be a copy, because we've had uploads since opening.
[14:44] <infinity> Hopefully, the run in progress doesn't undo my handiwork.
[14:44] <infinity> cjwatson: I concatenated and sorted wily and xenial into a new xenial.
[14:45] <cjwatson> Cool.
[14:45] <pitti> oh, wth
[14:46] <infinity> Oh, hrm.  That has some dupes, though.  Might need to be more clever.
[14:46] <pitti> cjwatson: ah, that's it -- teh result is for base-files/9.4ubuntu1 (and that's already in britney's cache)
[14:46] <pitti> cjwatson: but there was another upload ubuntu2 to fix the missing newline
[14:46] <infinity> If britney doesn't rewrite it to fix it.
[14:46] <pitti> and that's still in the queue
[14:47] <pitti> cjwatson: so, I have a really awful way of expediting this, if desired
[14:47] <pitti> I could flush the entire queue, stuff these 4 tests back in, and then let britney re-create the other test results
[14:47] <pitti> can't directly reorder an AMQP queue, sorry
[14:48] <pitti> while I'm at screwing up things, let's do that :)
[14:50] <cjwatson> infinity: britney should fix it, I think
[14:50] <infinity> cjwatson: S'ok, I just learned a new shell trick.
[14:50] <cjwatson> (haven't checked, I'm knee-deep in twisted code)
[14:50] <infinity> sort -u -k1,1 Dates > Dates.new
[14:50] <infinity> (To sort on only the first field)
[14:50] <pitti> ok, base-files tests are now at the front of the queue
[14:52] <pitti> all four running on http://autopkgtest.ubuntu.com/running.html now
[15:00] <pitti> infinity: turns out I didn't actually remove yet as it stumbled over openjdk-9 which you already removed
[15:00] <pitti> infinity: I have the Remove [y|N] prompt now; do you still want to run your script first?
[15:01] <pitti> (it takes ages to even get to that point)
[15:02] <infinity> pitti: I'll check right now, yeah.
[15:02] <infinity> Looks like my Dates hacking worked.
[15:04] <infinity> pitti: I see some still missing, so either snakefruit's mirror is behind, or you missed a few.
[15:04] <infinity> pitti: Waiting and trying again/
[15:04] <pitti> infinity: ah, you're checking on archive.u.c., not LP publishing
[15:05] <infinity> pitti: Well, snakefruit, but yes.
[15:05] <infinity> (ie: rmadison)
[15:05] <pitti> ok; /me cancels this and stashes the remove-package command for later
[15:06] <cyphermox> slangasek: ^ fwupdate.
[15:07] <infinity> pitti: No, you really did miss some.  Spot-checking my list against publishing records, there are some xenial records missing.
[15:07] <infinity> pitti: http://paste.ubuntu.com/12903342/
[15:08] <cjwatson> pitti: thanks
[15:12] <pitti> infinity: fun; thanks for the pastebin, copying those again then
[15:13] <infinity> pitti: Most of those have binaries, I think, so need -b, but I didn't check them all.  It might be a mix.
[15:17] <pitti> infinity: hm, so maybe it stops at the first error or so
[15:18]  * pitti might need to re-do the loop to call copy-package individually on each one, instead of a big batch
[15:21] <pitti> ok, plastimatch, ruby-gsl, and statsmodels worked now
[15:21] <infinity> pitti: When you think you've cleaned it all up, lemme know and I'll double-check again. :P
[15:23] <pitti> meh, --silent also disables rjection mails
[15:23]  * pitti throws hands in the air, mumble ridiculously complicated mumble
[15:25] <infinity> pitti: Sometimes, it's best not to look behind the curtain.
[15:25] <infinity> But, y'know, welcome back here.  We have tea and cakes.
[15:30] <Laney> And snakes
[15:30] <pitti> infinity, cjwatson: https://launchpad.net/ubuntu/+source/base-files/9.4ubuntu2 promoted
[15:31] <cjwatson> pitti: I think --silent disabling rejection mails could be argued to be a bug - the main purpose was to have a way to not spam with success mails in some cases
[15:31] <cjwatson> pitti: base-files> excellent, thanks
[15:31] <cjwatson> infinity: anything more before we open?
[15:32] <pitti> infinity: I did the next round of copies (both with binaries and without -b for the FTBFS ones)
[15:32] <pitti> but due to the complete lack of error messages I guess that again some packages might just silently have failed; so I guess it's waiting for pulisher now and rmadison again
[15:33] <infinity> pitti: Yeah, we'll see shortly, yes.  You could check pending publishing records for all of them, but I'd rather see the archive consistent anyway.
[15:33] <pitti> infinity: yeah, doing that would need a script; too much effort/error prone in firefox
[15:33]  * pitti -> dinner, will check again after that
[15:34] <infinity> cjwatson: Whoever's writing the email, and maybe confirming pitti's copies are sane.
[15:35] <infinity> cjwatson: But we're pretty much thereish.
[16:06] <pitti> infinity: can you re-run your script? I checked with rmadison again, and it seems to be ok now
[16:07] <pitti> rmadison -s xenial-proposed $(cat remove-from-wily-proposed) > /tmp/out
[16:07] <pitti> for p in $(cat remove-from-wily-proposed); do grep -q $p /tmp/out || echo $p; done
[16:07] <pitti> where remove-from-wily-proposed is the above pastebin (i. e. packages from http://people.canonical.com/~ubuntu-archive/proposed-migration/wily/update_excuses.html)
[16:08] <pitti> wow, e. g. https://launchpad.net/ubuntu/+source/jruby/1.7.22-1ubuntu1 actually built in xenial, but not in wily
[16:10] <infinity> pitti: Confirmed, LGTM.
[16:10] <doko> indeed a surprise
[16:10] <infinity> pitti: Delete away.
[16:10]  * pitti pushes the delete button and calls it a day/week
[16:11] <pitti> infinity: safe travels back home!
[16:11] <pitti> infinity: and congrats for the release
[16:13] <infinity> pitti: Not going home for another two weeks, but I'll see you in Austin.
[16:13] <pitti> infinity: oh, ok; you stay in London?
[16:14] <infinity> pitti: Detour on the way home for a week, plus VAC.
[16:14] <infinity> s/home/to Austin/
[16:15] <Laney> bye pitti!
[16:15] <pitti> Laney: bye, enjoy the weekend!
[16:15]  * Laney is coming to .de ;-)
[16:15] <pitti> ^ BTW, none of these syncs are urgent in any way, just stashing them after reviewing my merges
[16:15] <Laney> ah yes, they made polkit support the old syntax
[16:15] <Laney> or backported new stuff, or something
[16:16] <pitti> Laney: no, new polkit is just a lot of backported bug fixes, and getting back in sync
[16:16] <pitti> same for our ppolkit-qt-1 vs. polkit-qt5-1 split
[16:17] <pitti> they are both in Debian's ppolkit-qt-1 package now, and we can remove polkit-qt5-1 source once built
[16:17] <Laney> pitti: indeed, I remember that we (and debian) were blocked because of the JS stuff
[16:17] <pitti> Laney: yeah, and I don't see that change anytime soon
[16:17] <Laney> but smcv or someone backported a load of good stuff
[16:17] <Laney> which is nice
[16:17] <Laney> nanyway
[16:17] <Laney> get going :)
[16:18] <pitti> these poor test machines now won't have any free time on the weekend :)
[16:18] <pitti> debci-xenial-amd64  465
[16:18] <pitti> debci-xenial-armhf  321
[16:18] <pitti> debci-xenial-i386   458
[16:19] <Laney> did you get some more capacity?
[16:19] <Laney> or still on 5?
[16:19] <pitti> Laney: no, lcy01 is still brittle, only 5 on that; 8 on lgw01
[16:19] <pitti> and of course 16 armhf LXC ones as usual
[16:20] <Laney> mmm
[16:20] <pitti> Laney: I had to disable ppc64el, as that's power7, and xenial is power8 now
[16:20] <Laney> yeah I heard
[16:20] <pitti> hope we can get scalingstack bos soon
[16:20] <tsimonq2> I have a spare machine and I was wondering if I could use that to help somehow, maybe automated build machine, or somethibg of that nature...any ideas?
[16:20]  * pitti waves, have a nice weekend everyone!
[16:22] <tsimonq2> bai
[16:23] <tsimonq2> spam much? XD
[16:37] <sil2100> infinity, seb128, slangasek: hey! If anyone of you guys has a minute, we have a silo that introduces a new binary package to the qtmir source - qtmir-tests
[16:37] <sil2100> https://ci-train.ubuntu.com/job/ubuntu-landing-022-2-publish/46/
[16:50] <cjwatson> infinity: I imagine I could copy and paste an email if you like.
[16:50] <infinity> cjwatson: I expected doko might want to do one, but if he's not...
[16:50] <infinity> doko: Did you have a "welcome to Xenial" mail drafted?
[16:51] <cjwatson> I think we could unfreeze, since all this stuff going through the queue isn't exactly toolchain.
[16:51] <infinity> Yep.
[16:51] <infinity> We can thaw both the queue and britney, I think.
[16:51] <infinity> Lemme do the former.
[16:54] <doko> infinity, cjwatson: yep, wanted to wait until the queues cleared up, and send it tomorrow. afk now
[16:54] <cjwatson> All right, how about I turn on auto-sync?
[16:55] <doko> then the queues will be busy with main, but anyway, they can do something over the weekend
[16:56] <infinity> cjwatson: auto-sync on sounds fine by me.
[16:56] <infinity> And I think I'll clear the britney block, if no one has any objections?
[16:56] <cjwatson> doko: They may as well, no point in them being idle
[16:57] <infinity> britney block clearing in 3...
[16:57] <infinity> 2...
[16:57] <cjwatson> auto-sync enabled
[16:57] <infinity> 1...
[16:57] <doko> infinity, yes please
[16:57] <Laney> boom
[16:57] <cjwatson> Conveniently, will run in three minutes
[16:57] <infinity> Let's see how my PPC VMs hold up with 3.19 kernels instead of 3.13
[16:58] <infinity> Hoping for a miracle, since I'll probably only check in daily while on VAC.
[16:58] <cjwatson> Everything except arm64 should be pretty quick to clear now.
[16:59] <infinity> Those poor Mustangs.
[16:59] <infinity> If only they had I/O.
[16:59] <infinity> And friends.
[16:59] <cjwatson> And weren't trying to finish a test rebuild as well
[16:59] <cyphermox> careful, soon they'll form a union.
[17:31] <olli_> happy day after release day!
[17:31] <olli_> does anyone know if slangasek is around today?
[17:31] <infinity> slangasek might know if he's around.
[17:35] <olli_> infinity, hanging out in the channel and replying are two slightly different but important things ;)
[17:35] <infinity> olli_: Indeed.
[18:23] <davmor2> olli_: assume he isn't till he says he is :)
[18:32] <slangasek> olli_, infinity: I am around, but don't tell anyone
[18:33] <slangasek> infinity, cjwatson: have either of you been filled in on the lxd breakage on the cloud images?
[18:33] <slangasek> or are you all safely at the pub now? :)
[18:42] <cyphermox> slangasek: no pub tonight on account of travelling tomorrow, it seems
[18:42] <cyphermox> (at least, for me it's a good enough reason)
[18:42] <slangasek> heh ok
[18:44] <cyphermox> tacos ended the week quite well though.
[19:36] <cjwatson> slangasek: didn't hear anything about it
[19:36] <slangasek> cjwatson: ok.  is being addressed in a way that doesn't involve nasty archive surgery, so carry on ;)
[19:37] <cjwatson> ok :)
[19:38] <cjwatson> good grief auto-sync is still going
[22:43] <bdmurray> slangasek: still about? I'm not certain how to proceed with bug 1509305.
[22:43] <ubot2> bug 1509305 in ubuntu-release-upgrader "Kernel not upgraded during upgrade from Vivid to Wily" [High,Triaged] https://launchpad.net/bugs/1509305
[22:44] <slangasek> hmm
[22:44] <bdmurray> its a result of bug 1506169
[22:44] <ubot2> bug 1506169 in software-properties "if linux metapackage is installed software properties will uninstall it" [High,In progress] https://launchpad.net/bugs/1506169
[22:45] <slangasek> ah, ick
[22:46] <slangasek> bdmurray: probably wants an upgrader quirk in u-r-u/u-m to unconditionally install linux-generic if there's no linux metapackage installed
[23:02]  * doko looses hopes to quickly get a python3-defaults into the release pocket :-/