=== morphis__ is now known as morphis [13:34] cjwatson: Hi, could you check if you are grabbing appstream from us correctly please? [13:34] I added a timestamp on my end to check on this and yours doesn't have it [13:45] Laney: nothing worrisome in logs. how long ago did you add it and on what host? [13:46] Laney: I don't see anything obviously timestamp-like when I try "rsync -av appstream.ubuntu.com::appstream/" [13:47] cjwatson: "Time" in the header document [13:47] I think it should have started appearing yesterday [13:47] which header document is that? [13:47] at least xenial/main/amd64 has it [13:48] is this somewhere inside xenial/main/Components-amd64.yml.gz ? [13:48] ubuntu@temp-rsync-host:~/appstream/xenial/main$ zgrep "Time:" Components-amd64.yml.gz [13:48] /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_GB.UTF-8) [13:48] Time: '2016-03-08T13:05:43.158291+00:00' [13:56] Laney: for some reason the mtime of that file is older than the version we already have, so LP doesn't install it [13:56] cjwatson@pepo:/srv/launchpad.net/ubuntu-archive$ ls -l ubuntu/dists/xenial/main/dep11/Components-amd64.yml.gz [13:56] -rw-rw-r-- 1 lp_publish lp_publish 433553 Mar 8 13:44 ubuntu/dists/xenial/main/dep11/Components-amd64.yml.gz [13:56] cjwatson@pepo:/srv/launchpad.net/ubuntu-archive$ ls -l ubuntu-staging/xenial/main/dep11/Components-amd64.yml.gz [13:56] -rw-rw-r-- 1 lp_publish lp_publish 429569 Mar 8 13:07 ubuntu-staging/xenial/main/dep11/Components-amd64.yml.gz [13:57] hm, that's today though [13:57] Is it possible that something is making that always be the case? [13:57] I thought I was fairly careful there [13:58] I think that I made emacs24 appear some time last week [13:58] and it's not in the archive's version [13:58] that mtime is super weird though [13:58] The first thing that made me suspicious enough to add this timestamp was not seeing apt downloading it very often [13:59] it's in the middle of release file generation [13:59] which is a bit WTF [13:59] oh [13:59] _syncTimestamps [14:00] there's a thing that makes sure that all the mtimes of Release and anything it contains match up, to make it easier to insert caching headers on mirrors [14:00] that clashes rather badly with this [14:00] probably with Contents files too [14:00] hm hm hm [14:01] Laney: please file a bug, this is definitely screwed but I need to think about the best way to fix it [14:01] OK [14:02] we may need to use something other than mtime for the sync-from-staging [14:02] * Laney gets this filed quickly so that he can go away before hearing too much of the archers [14:03] paging @SoVeryBritish [14:05] https://bugs.launchpad.net/launchpad/+bug/1554535 [14:05] Launchpad bug 1554535 in Launchpad itself "DEP-11 metadata is not updated correctly" [Undecided,New] [14:06] * Laney goes to lunch [14:06] ta [15:25] hi cjwatson, last week you mentioned an LP change that needed to land to fix snap builder issues. Has that landed and if not, is there a bug I can track? [15:39] dpm: it was a launchpad-buildd change, and it's landed [15:39] well, except on arm64 for reasons, I should go and chase that up [15:51] cjwatson, great, thanks. I saw the build of my snap failing again this morning, so I wasn't sure if it was the same issue. But it might also be the latest changes to the branch, which don't seem to be supported by snapcraft. I'll check later [15:55] dpm: link? [15:55] dpm: snapcraft compatibility is fairly, yes, well [15:56] dpm: afaics you've performed no snap builds on LP since last week [17:11] do clone links look broken here https://code.launchpad.net/~james-page/charms/+source/openstack-on-lxd-bundle/+git/openstack-on-lxd-bundle [17:17] they're OK aside from the annoying wrapping === pavlushka_ is now known as pavlushka [19:02] cjwatson, indeed, no snap builds. Sorry, misread the subject of the e-mail notification, as I'm building both snaps and .debs for the same upstream project [19:07] cjwatson, imho they shall never wrap, like they don't on https://git.launchpad.net/~james-page/charms/+source/openstack-on-lxd-bundle [19:07] cjwatson, and e.g. i have enough screen space to have them non-wrapped. [21:09] xnox: (ITYM "should".) I agree, file a bug? [21:09] hello, how are spamming accounts suppose to be handled? https://answers.launchpad.net/synapse-project/+question/288140 [21:09] wgrant: ^- [21:09] * wgrant applies fire. [21:09] ;-)