/srv/irclogs.ubuntu.com/2013/10/28/#ubuntu-release.txt

stgraberogra_: fixed the issue with the diff generator (failing on relative hardlinks path in the tarball when the path is relative to the tarball root and not the fs root) and re-enabled the cronjob, so your image should publish in the next few minutes00:53
slangasekhmm, https://merges.ubuntu.com/main.html appears to be updating, but the content doesn't seem to have04:34
cjwatsonslangasek: note that its data source is trusty, not trusty+trusty-proposed04:52
cjwatson(which is arguably a bug ...)04:52
slangasekcjwatson: ah, right, I had assumed rsyslog had already migrated and it hasn't04:53
slangasekoh right, it hasn't migrated because it hasn't built because I'm still waiting for an MIR ack - ho hum04:54
xnoxI've had to retry lucene++ twice on amd64 & i386. It's now built on amd64, but still not on i386. https://launchpad.net/ubuntu/+source/lucene++/3.0.4-0ubuntu309:23
xnoxare there any tricks as to getting it built?  disable parallel? keep retrying?09:23
=== peterm-ubuntu is now known as Peter-wfh
=== yofel_ is now known as yofel
jamespageplease could someone reject openvswitch from saucy-proposed13:21
jamespageapparently I don't have my brain correctly wired today13:21
sil2100Hello, is anyone from the SRU team around?13:23
stgraberjamespage: done13:54
jamespagestgraber, ta13:55
zulcan you reject msgpack-python and python-cliff for me? thanks14:04
stgraberzul: done14:20
zulstgraber:  thanks14:21
lamontwhat release-teamish folks around?15:05
stgraberlamont: what's up?15:06
lamontI'm about to possibly introduce a small disturbance into the syncproxy world.  figured I should make sure it's a rational time and all that15:06
lamontsyncproxy is moving to a new home is all15:07
lamontit _should_ be seamless15:07
lamontstgraber: any thoughts?15:08
stgraberlamont: syncproxy is just for the ISO images right?15:09
lamontand archive15:09
lamontreleases + archive15:09
lamontthose IP addresses are dedicated, and moving to a new host15:09
stgraberok, how long do you expect it to be down?15:09
lamontwhich is a clone of the old host15:09
lamontmoments only, though if I broke sync because of firewalls and such, there could be lagginess15:09
lamontsteps:15:10
lamont1) disable triggering of old15:10
lamont2) one last sync15:10
lamont1.5) quiesce old :D15:10
lamont3) enable triggering on the new15:10
lamont4) manually trigger an archive pulse15:10
lamont5)watch15:10
lamont6) profit15:11
stgraberok, well, go ahead whenever you want, just make sure to let us know here. releases I'm not concerned about since we won't be publishing anything new there for quite a while. archive is a bit more problematic but there aren't really any good time to get it out of sync with ftpmaster15:11
lamontright15:11
lamontit should remain synced.  It may miss one sync pulse though15:11
lamonts/synced/consistent/15:12
stgraberlamont: looks like we use *.syncproxy.ubuntu.com for the trigger, so nothing to change on our side apparently15:14
stgraberlamont: though I just noticed releases.syncproxy.ubuntu.com is currently unhappy. Is that because you started the switch?15:15
lamontstgraber: I disabled the triggering of syncproxy15:15
stgraberok, good, makes sense15:15
lamont(commented out the ssh keys for archvsync15:15
* lamont is on step 1.515:15
lamontlast sync is running15:17
lamontstgraber: feel like doing a manual trigger for me?15:40
stgraberlamont: trying from nusakan now15:42
stgraberlamont: seems to be hanging15:42
=== brainwash_ is now known as brainwash
stgraberlamont: is 91.189.92.173 the correct IP for releases.syncproxy.ubuntu.com?15:43
stgraberlamont: if so, port 22 times out, possibly due to a firewall somewhere15:43
lamontfirewall.  let me go smacking15:43
lamontinteresting15:44
* infinity wakes up and sees people talking about syncproxy...15:47
infinitylamont: Fill me in, is this a new ssh key and IP, or a cloned cutover?15:47
infinityMon, 28 Oct 2013 15:44:39 +0000: Triggering archive.syncproxy.ubuntu.com:15:47
infinityssh: connect to host archive.syncproxy.ubuntu.com port 22: Connection timed out15:48
infinity(From ftpmaster)15:48
lamontsame ip same key, etc.15:48
lamontotoh, I'm figuring out why that IP isn't as live as it thinks it is15:48
infinityAhh, check.15:48
xnoxplease de-new vowpal-wabbit for boost1.54 transition. https://launchpad.net/ubuntu/trusty/+queue?queue_state=0&queue_text=15:49
infinityxnox: Looking.15:51
lamontinfinity: it should be happy now.15:58
lamontstupid sticky arp caches15:58
stgraberlamont: still unhappy from nusakan15:59
lamonthrmpf15:59
lamontmore arp caches cleared16:01
lamontnusakan should be happy16:02
stgraberyep, looks happy now16:02
ogra_high hopes16:02
infinitylamont: ftpmaster's about done a publisher run, I'll let you know if it explodes.16:02
* lamont is tailing logfiles16:02
stgraberof course there's nothing to sync so I can't really check, but ssh to syncproxy definitely worked16:02
lamontstgraber: true that16:03
infinitylamont: Log looked good, at least.  Assuming the trigger did something on the other side. ;)16:06
infinityI don't see that host attached to pepo:873, but maybe it was that quick?16:07
lamontMon, 28 Oct 2013 16:07:29 +0000: Unifying file list with stay-of-execution list16:08
lamontit's chunking along on the archive bit16:08
lamontboth a releases and an archive push are now in progress16:11
lamontinfinity: I'm going to declare step 6 complete (profit)16:18
lamont /dev/sda1       1.7T  754G  807G  49% /16:18
infinitylamont: Good deal.16:18
ogra_lamont, so on to step 716:18
ogra_(beer)16:18
infinityogra_: lamont doesn't drink. :P16:18
* infinity sends root beer.16:18
lamontogra_: 7) close ticket.16:18
lamontFIN16:19
ogra_heh16:19
bdmurrayinfinity: could you merge https://code.launchpad.net/~brian-murray/ubuntu-archive-tools/phased-updates-disregard-package/+merge/192741?16:20
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
seb128infinity, bdmurray: hey, any chances you guys could review some saucy SRUs? (hud, libgpod, file-roller, indicator-* would be nice, would fix some of the top reported issues in saucy)17:55
infinityseb128: I'm suffering on seriously awful WiFi here, but I can have a look.17:56
bdmurrayinfinity: I can do it17:57
infinityEven better.17:57
seb128infinity, thanks, those are mostly small packages so should be easier to download17:57
seb128bdmurray, thanks17:57
bdmurrayinfinity: could you have a look at those procps uploads though since I sponsored them?18:01
infinitybdmurray: Sure.  P/Q/R/S?18:23
bdmurrayinfinity: yes all four18:24
infinitybdmurray: Is this fixed in T?18:26
infinityAhh, bug log says yes.18:26
seb128bdmurray, infinity: libindicator's saucy's SRU is green and 9 days old, can we move it to updates?18:36
infinityYep.18:37
infinityseb128: Done.18:38
seb128infinity, thanks18:38
seb128infinity, do you guys pocket copy to t or should we do uploads there?18:39
infinityseb128: I can do the copy in this case, if there's no T upload planned.18:40
seb128infinity, that would be great ;-)18:40
infinityDone.18:41
bdmurrayseb128: I'm confused about the indicator-datetime upload and bug 123317618:49
ubot2Launchpad bug 1233176 in Ubuntu Clock App "Alarm notifications do not appear when an alarm is triggered" [Critical,Triaged] https://launchpad.net/bugs/123317618:49
seb128bdmurray, https://code.launchpad.net/~indicator-applet-developers/indicator-datetime/trunk.13.1018:50
seb128bdmurray, the change was reverted from the stable branch since it was not suitable for it, but the daily landing doesn't know how to delete changelog entries when that happens I guess18:50
bdmurraySo then the janitor will close the saucy task although it hasn't been fixed.18:52
seb128bdmurray, we can re-open, or do you prefer another upload?18:53
seb128cyphermox, ^18:53
bdmurrayseb128: I think another upload would be the cleanest solution18:54
cyphermoxbdmurray: agree18:56
cyphermoxI'll do a manual upload that fixes this18:56
seb128bdmurray, what cyphermox said ;-)18:56
cyphermoxthat's going to be fun :)18:56
bdmurraycyphermox: thanks, let me know and I'll review it straight away18:56
cyphermoxbdmurray: same version number, right?18:58
cyphermoxit wasn't accepted into proposed yet?18:58
bdmurraycyphermox: no, it wasn't accepted18:58
cyphermoxalright18:59
cyphermoxbdmurray: ^19:04
=== iulian is now known as Guest86495
=== sergiusens_ is now known as sergiusens
=== Guest86495 is now known as iulian
=== vila is now known as lt-columbo
=== lt-columbo is now known as vila
lamontoh hai20:40
lamontinfinity: (et al): how horrific are the windows if I just want to manually run the script that the publisher run triggers for the archive?20:40
cjwatsonJFDI, it locks20:41
lamont\o/20:41
cjwatsonIt tries to run every five minutes, 3 and 820:41
lamontta20:41
cjwatsonYou can stop it for a bit in lp_publish's crontab if you like20:41
lamontatm, it's vweeping at me because awk runs for apparently forever20:41
cjwatsonawk?!20:41
lamont1001     21411 99.2  1.2  81244 74508 ?        R    20:39   2:32  \_ awk { x[$1]=1} END { for (v in x) { print v }} filelists/2013-10-26-20-37-...20:42
lamonttrust me.... after you shook your head and pondered, you'd say "yeah, that makes sense"20:42
lamontmost of that whole thing is like that20:42
cjwatsonOh, this is your stuff not in the publisher20:43
lamontyep20:43
cjwatsonk20:43
lamontI see what I did there20:59
lamontcjwatson: infinity I'm wondering just when we switched over to the publisher running every 5 instead of every 3021:41
cjwatsonlamont: It was this summer, around the time of the releng sprint, IIRC21:43
cjwatsonMaybe a bit earlier?21:43
stgraberI'd have said a couple weeks before the sprint21:43
stgraberso early July ish21:43
cjwatsontimestamp: Wed 2013-07-03 07:03:00 +000021:44
cjwatsonmessage:21:44
cjwatson  [adconrad,r=gnuoy] Attempt to run the publisher every five minutes instead of every thirty (lp:~adconrad/lp-production-crontabs/faster-publisher into lp:lp-production-crontabs)21:44
cjwatsonlp-production-crontabs r79221:44
lamontright.  I'll work though the rest of what that means to the mirrormagic...21:47
lamont6 times the files, and 1/6th the time to do it in ... amusing is one word for it21:48
lamontbut anyway, it'll help make the evening more interesting21:49
cjwatsonIt won't actually run every five minutes21:49
cjwatsonIt just tries21:49
cjwatsonI mean, it sometimes has a runtime under 5min, but only if it doesn't have any release pockets to publish21:50
lamontyeah, the stay of execution code is a touch more resilient21:50
lamont71 cpu minutes, and we're almost 10% of the way through21:51
lamontlets just say there's room for improvement21:51

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!