[00:08] mtaylor: if you think you can add it do so; if not let me know and I'll add it now [00:09] lifeless: I looked and wasn't sure where it should be added [00:14] mtaylor: there is a loop across branches right ? [00:14] mtaylor: you need to do the check for missing data on each branch [00:16] if its not stacked then it will quietly do noting [00:25] lifeless: so: [00:25] def upgrade_branch(self, branch_url): [00:25] upgrade(branch_url) [00:25] right before the upgrade(branch_url) ? [00:27] not quite [00:27] change it to do two passes over the branches [00:27] in pass one do the fixup [00:27] in pass two do the upgrades [00:34] lifeless: lp:~mordred/autolp/fix-branch [00:50] jkakar: mtaylor: spm: mtaylors branch looks correct to me. [00:52] i have a problem with a related bug, where someone did a --fixes on bzr commit. the problem is he mistyped the bug number. i mailed him, he removed that relation but now it appeared again! [00:53] spm: (I want to disappear for, oh, 4 hours.. so if you want my help on this please look at it now) [00:53] spm: (drizzle can only upgrade on mondays, because they don't want downtime-like-things during the week) [00:54] lifeless: oki [01:03] spm: I can't tell if that is 'its ok, I don't need you' [01:03] or 'ok I'm looking at it now' [01:03] lifeless: heh. sorry - am looking atit now. [01:03] just about to do a trial [01:08] lifeless: so last time we ran it "AUTOLP_DEBUG=1 ./bin/autolp upgrade-branch-format -p landscape-client" which was going to iterate over all ls-clients; in this case, I gather we don't want to run against 250 ish branches in a single hit. can we limit somehow? [01:08] spm: we don't want landscape-client [01:08] no :-) [01:08] spm: we want drizzled. [01:09] spm: why would we want to skip branches? [01:09] yes, but do we want all 250 branches of it? [01:09] that'll take ~ 5 days to run. [01:09] spm: nonsense. [01:09] spm: most should be stacked. [01:10] lifeless: select count(*) from branch where target_suffix = "drizzle" and stacked_on is NULL; ==> 249 unstacked branches [01:10] grah [01:10] thats ... insane [01:10] mtaylor: ^ [01:11] if we can limit to say to do batches of 5 or so?? [01:11] spm: we can actually skip all non stacked branches except for trunk [01:11] hang a sec [01:12] lifeless: I have no idea why they are not stacked [01:12] oh- perhaps those are the branches we pushed from before when stacking existed? [01:13] we probably don't need to upgrade any branches that haven't been pushed to in a month [01:13] in case that helps [01:14] lp:~lifeless/autolp/onlystacked [01:14] spm: ^ [01:14] mtaylor: if you want to hack that in, go right ahead. [01:14] ta [01:15] however, for now, my little patch will just hard skip the unstacked branches [01:15] so we need to do: [01:15] lifeless: ok. [01:15] autolp upgrade yada yada yada [01:15] bzr upgrade lp:drizzle [01:15] (and repeat for any other series branches you have) [01:16] spm: nice catch there. [01:16] lifeless: not really mine - thumper mentioned it earlier. That's his syntax fail query above :-) [01:16] $credit all around [01:17] spm: eh? [01:23] spm: hows it looking? [01:23] oh. sorry - I thought we were waiting on other stuff being done. I'll kick that off now. the target is 'drizzle' yes? [01:24] spm: pull my branch [01:24] spm: then yes. [01:24] yup, done that. oki. lets make some music! [01:26] lifeless: https://pastebin.canonical.com/25412/ ?? [01:32] mtaylor: branch.bzr_identity != branch :P [01:32] spm: fixing [01:32] np [01:33] k, pull. [01:33] lifeless: heh. sorry - I thought I'd fixed that... [01:33] oh well [01:33] lifeless: thanks! [01:33] spm: thanks [01:33] no worries [01:34] this is the 'throw at the admin to test' lifecycle of software development [01:34] aka spmdo (forever immortalised in my mind) [01:35] spm: Did you quotes page it ? [01:35] no, didn't thnik of that tbh [01:36] ahha http://bit.ly/SPmdo [01:38] so, did that make it happier? [01:38] gah. missed the pull comment. sorry, my bad. [01:41] bleh. perm fail; bzr lp-login, tey #2 [01:41] try! [01:42] lifeless: https://pastebin.canonical.com/25414/ hrm. still go away. [01:42] oh haha. that's on chinstrap. argh. [01:44] spm: (so, I'm doing this, then training to the city; oh 40 minutes back ;P). I will be _very prompt_ on issues. [01:44] spm: that branch is broken. [01:44] let me delete it [01:44] oki [01:45] its a lightweight checkout pointing at *my hard disk* [01:45] IzBZRBug [01:45] lifeless: wha? bzr can haz bugs? [01:45] special ones [01:46] spm: k go [01:47] going [01:47] https://code.edge.launchpad.net/~gregorytorres73/drizzle/gregory may make it hiccup too [01:47] thumper: what is bzr_identity for mirrored branches ? [01:48] lifeless: it is the location on LP [01:48] lp:~foo/bar/baz [01:48] lifeless: progress. https://pastebin.canonical.com/25415/ [01:48] hmm, we'll we'll see what error we guess I suppose ;) [01:49] I blame mtaylor for that one. [01:49] spm: fixed, pushing. [01:49] * lifeless throws it at the sysadmin again [01:49] rev9 up [01:50] heh [01:50] while broken: lifeless.fix();spmdo() :) [01:51] hmm. dunnon what your thoughts there are Rob, but that trailing ':)' would seem to be a necessary part of the syntax. [01:51] :P [01:51] or pep8 style [01:51] : { [01:51] sorry [01:51] boom. bzrlib.errors.NotBranchError: Not a branch: "bzr+ssh://bazaar.launchpad.net/~mordred/drizzle/deve/". [01:51] : P [01:52] mtaylor: ping [01:52] mtaylor: please delete that dud branch [01:52] spm: or you can - see https://code.edge.launchpad.net/~mordred/drizzle/deve [01:52] never pushed to, no content. [01:52] I have the ducky [01:53] and go again [01:53] gone [01:55] where's the kaboom, there is meant to be an earth shattering kaboom. [01:56] my favourite bugsbunny/marvin quote. ever. [01:56] goodness, it's still going! [01:56] we'll be home freeish when it starts doing upgrades [01:57] famous last words? :-) [01:57] mtaylor: @ LCA; I vant beer :P [01:57] mtaylor: and you will want to give me beer - 2a is kumtreyah [01:59] geez, what's with the 10 hour wait time on i386 ppa builds [02:00] lifeless: https://pastebin.canonical.com/25416/ [02:02] spm: run it again [02:02] kk [02:03] Huh, that's a bit surprising. [02:03] spiv: ? [02:04] spm: we don't expect lp's server to fail. [02:04] To get a smart server connection dropped like that. [02:04] spm: but it did. [02:04] really? bugger! [02:04] Especially within the data centre, where I presume the network is pretty reliable :) [02:04] well. yes! [02:05] And the smart server itself generally at least sends some sort of error before blowing up, if it does blow up. But that appears to be a straight drop of the connection. [02:05] spm: I've tossed up a slightly quieter version so if it breaks again do a pull [02:05] oki [02:05] As if the remote side segfaulted or something, which is a pretty odd thing to do in response to a BzrDir.open request. [02:06] tbh, the noise (atm) doesn't worry me. it's a clue that things are still happening. [02:06] spm: shurg. :) [02:07] spm: ok, so here is a noisier one. [02:07] rev11 [02:07] anyhow, how is it going ? [02:08] still doing it's thing [02:08] heh. noisier. :-) [02:09] bzrlib.errors.NotBranchError: Not a branch: "bzr+ssh://bazaar.launchpad.net/~mkindahl/drizzle/drizzle-refactoring/". [02:10] empty branch. should we ignore these in future? or manually delete? [02:10] delete. [02:10] they are crap in the system [02:10] if you pull again we'll get some clearer info about progress [02:11] spm: if it's empty, and has no links to bugs or anything, and they are weeks old, then I don't think anyone will miss them. This one ticks all those boxes. [02:11] oki [02:12] I really need a long white haired cat, whose fur to gently stroke when I do these deletions. Just doesn't feel right without the proper props. [02:13] still chugging ? [02:13] yup [02:17] still going... [02:17] \o/ [02:17] running my admin friendly copy? [02:20] argh. bzrlib.errors.NotBranchError: Not a branch: "bzr+ssh://bazaar.launchpad.net/~mkindahl/drizzle/plugin-fix/". [02:20] not yet; but will now. [02:22] old. empty; deleting... [02:26] Just saw launchpad.net/builders for the first time due to the build for my package being 13 hours away. After poking around the page a bit, I was wondering if the build farm is strictly Canonical machines or if there's a way to run a build machine as a virtual machine on another system? (The reason I'm asking is that I have a few high-end servers that are idle about 90% of the time and could help build...) [02:27] darkpixel: at themoment its canonical only as we don't have a trusted path to build on machines we don't control [02:27] a hostile admin could compromise packages easily :(. [02:28] wooo. much nicer noisier version. [02:29] lifeless: That's what I figured. That's a tough challenge though--how to secure a machine that's physically accessible to a malicious admin... [02:30] spm: you ask, I deliver. [02:30] lifeless: :-) [02:31] added a branch count [02:31] spm: pull again if it fails agian [02:31] kk [02:31] spm: how many seconds per branch ? [02:31] * lifeless considers that we're going to be hammering the ssh handshakes ... [02:31] ~~~~hand~~~~ 3-10 ? [02:33] fwiw, I got two syntax errors: print >self.outf, "Missing inventories: %r" % needed <== type of thing. File "./autolp/commands.py", line 101 & File "./autolp/commands.py", line 117. i s/ >/>>/ but am unsure if this is supposed to be doing something special? [02:34] mtaylor: I am lovnig the names of some of these branches. "whitespace-uncrustify" is fave so far :-) [02:36] bleh. Not a branch: "bzr+ssh://bazaar.launchpad.net/~mkindahl/drizzle/testing-overhaul/". [02:38] lifeless: oh bother. that one's ^^ linked to a bug. is old tho. ??? [02:38] mtaylor: ^ opine please [02:39] https://code.edge.launchpad.net/~mkindahl/drizzle/testing-overhaul/ <== easier clicky [02:39] > 1 year old [02:39] delete [02:39] Duhlete. [02:39] huh. I read that as '09. lala me. must be monday. [02:40] rev 13 up [02:40] with less syntax errors [02:40] off again [02:41] how many branches does it say its considering [02:41] Branches: 238 [02:42] so, 2400 seconds to check them all [02:42] once they are all checked, we should probably disable that part of the logic. [02:42] that'd be the max; yeah [02:42] --no-check? [02:43] heh. --are-you-really-sure-you-know-what-youre-doing-no-check [02:45] --no-fix pushed. [02:45] ta [02:45] though, that said, if there are 238 branches, most have to be unstacked. [02:46] as you said there were 249 unstacked branches. [02:46] >< [02:46] we haven't deleted 11 branches. [02:46] no... 3-5 at most [02:46] so, I dunno whats up there... [02:47] meh. let thumper figure it out? ;-) [02:48] ok, rev 15 when it breaks next. [02:49] heh. timing. [02:49] Not a branch: "bzr+ssh://bazaar.launchpad.net/~ro4tub/drizzle/main/" [02:50] old. deleting. [02:51] re-running, no-fix [02:51] spm: nono [02:51] ^C [02:51] spm: we want no-fix *after* we completely fix them all and we start getting into actual upgrades. [02:52] Ahhhh. righto. I misunderstood the logic. kk [02:52] because at that point the fix check is waste. I'm adding something now to make it report rather than die on NotBranchError [02:52] ta [02:54] spm: ok, stop it [02:54] stopped. [02:54] spm: pull rev 16 [02:54] start it [02:55] this should print out 'Not a branch' for things that are not-a-branch [02:55] sweet [02:55] so we don't have to do a no-op check on stuff we've checked already; N^2 time sucks. [02:55] +1 on that [03:03] no fails yet; still running [03:05] couple of 'fixed's just now [03:09] lifeless: bzrlib.errors.InvalidURL: Invalid url supplied to transport: "lp:~gregorytorres73/drizzle/gregory": The remote branch at ~gregorytorres73/drizzle/gregory has no URL specified. [03:12] spm: hmm, I think the script should probably skip remote (as opposed to hosted or mirrored) branches. [03:12] so remote is 'not mirrored at all' ? [03:13] lifeless: that's my understanding, e.g. when LP branches were hosted on devpad but had some metadata tracked on LP [03:13] lifeless: they are supposed to have a URL associated with them, though, so it sounds like maybe this remote branch is just broken anyway? [03:13] spiv: rev 17 [03:13] spm too? :-) [03:14] I suspect so :) [03:14] blarh [03:14] yes [03:15] spiv: I find it most curious that not only the similarities in our nic's, but that we're both devilishly handsome as well. Shrug. Just one of lifes co-incidences I guess. [03:17] Hah [03:26] spm: how is it looking ? [03:26] good! [03:26] two exceptions that were happily passed over [03:27] another iteration if it dies again [03:27] (I mean, I've pushed again :P) [03:28] kk [03:28] spm: how far through it is, do you think ? [03:28] 208 ish. +~ 10 now? [03:29] actually remove a few. some double lines [03:29] but ~ 3/4's I guess [03:32] awesome [03:34] wow. it just started on the upgrades! [03:35] ok [03:35] so we're committed now :) [03:35] at this point --no-fix if we have to start over [03:35] :-) [03:35] kk [03:35] and you'll want my rev 18 in that case, it handles the same cases that the check was dying on before [03:35] how fast is it chugging through? [03:36] kaboom [03:36] ok, thats not that fast :P [03:37] lifeless: https://pastebin.canonical.com/25417/ [03:37] pastify! [03:37] rev 18 pulled [03:37] oh, I see [03:37] fixing [03:37] we need nosmart+ [03:38] btw; I'll need to afk for the school run and lunch in ~ 20mins. [03:38] I think [03:38] ok [03:38] :-) [03:38] spiv: ^ your thoughts? [03:39] spiv: can you backout the upgrade of add-more-cpplint ? [03:39] spm: ^ [03:40] spm: that is, if you look inside the branch, you'll see backup.bzr, and that du -sh on .bzr shows it to be smaller than backup.bzr [03:40] that's rename the backup.bzr dir? [03:40] ok [03:40] mv .bzr .bzr.broken [03:40] mv backup.bzr .bzr [03:40] kk [03:40] then pull my rev 19 and try again [03:40] this time with --no-fix [03:41] what bzr version do you have? [03:42] Bazaar (bzr) 2.0.2 <== chinstrap [03:42] ok [03:42] so I think I know whats going to happen. [03:43] lifeless: no particular thoughts; I thought the case (upgrading when the stacked-on location is already upgraded) was supposed to work. [03:43] we don't test this particular case - its going to upgrade the repo successfully, then try to upgrade the branch and barf [03:43] spiv: its tested [03:43] /srv/bazaar.launchpad.net/push-branches/00/03/e4/a3 fwiw [03:43] spiv: but I think the test uses the same branch object [03:43] format [03:43] revno 19; trying again [03:44] spm: hang on. [03:44] hanging [03:44] spm: may have to abort and fix some bzrlibby stuff [03:44] bleh [03:44] and I'm nearly 3 hours overdue for crepe :) [03:44] I was going to say :-D [03:44] crepê ? [03:46] lifeless: :/ [03:46] bear with me just a little longer. [03:46] spiv: does that make sense? [03:46] lifeless: it sounds plausible, at least. [03:46] spiv: so, I propose we: [03:46] a) back up bzr+ssh://bazaar.launchpad.net/~drizzle-developers/drizzle/development via spmdo [03:47] b) upgrade that branch itself [03:47] c) resume upgrading [03:47] this will work, because when the branch is upgraded the stacked on branch will already be upgraded. [03:47] spiv: Ack/hate ? [03:48] spm: how long is the schrool run ? [03:48] ~ 20-25 mins. but I need lunch at some point too. [03:49] spm: for sure. [03:49] actually, my rev 21. [03:49] * lifeless rings spiv [03:49] pulling [03:49] lifeless: that sounds sane, if it workds [03:50] spiv: "working" is a fair def'n of sanity to my mind ;-) [03:53] spm: ok [03:53] see the plan above? please start on it [03:53] kk [03:53] spm: lifeless' plan sounds like it will work to me [03:54] spm: if things still fall over, I'll see what I can do to fix [03:54] I will stay until the add-more-cpplint branch has been upgraded successfully (run with --no-fix) [03:54] huh. there's already a backup.bzr dir in here [03:55] spm: recent? [03:55] 2009-03-18 [03:56] If you're paranoid I guess you can rename it to backup.bzr.2009-03-18 [03:56] wfm [03:56] (quicker than deleting, too ;) [03:56] drwxr-xr-x 5 codehost codehost 4096 2009-03-18 21:30 backup.bzr.2009-03-18 [03:56] drwxr-xr-x 5 codehost codehost 4096 2009-03-18 22:04 backup.bzr.for2a [03:56] drwxr-xr-x 5 codehost codehost 4096 2009-03-18 22:04 .bzr [03:56] for the record. [03:57] lifeless: " b) upgrade that branch itself" just "bzr upgrade" in this dir ^^ ? [03:59] * spm holds for 30secs more than really needs to go [04:01] spm: yes [04:02] where 'this dir' is the drizzle trunk dir [04:24] coolio; starting now. [04:25] spm: thankks [04:25] fyi. /srv/bazaar.launchpad.net/push-branches/00/00/3c/e5 for the record. and now, lunch. [04:27] spiv: how will you feel if I bail now? [04:32] lifeless: fine, please bail :) [04:36] * lifeless bails [05:10] that upgrade is finished! [05:10] resume step (c) [05:13] spm: cool [05:13] spm: hmm, you may need to trigger a mirror of that branch [05:14] spiv: oki, fwiw I was doing that in push-branches [05:14] spm: right [05:15] spm: yeah, I think you need to manually trigger a mirror, the webapp still thinks it's 1.9 format. [05:15] now where does mwh hide that these days.... [05:15] spm: most clients will use the mirrored version, not the hosted (push-branches) version [05:15] spm: jml probably knows, and I think he's around [05:17] bleh. wrong. https://code.edge.launchpad.net/~vcs-imports/drizzle/development [05:17] spm: (possibly we'll want to trigger mirrors for all the branches once they're upgraded...) [05:17] ~vcs-imports? [05:18] gargh. imports. wtf am I doing. [05:18] damn. I remember this stuff now. it's sql based. [05:19] spm: you don't get a button in the web UI because you're a rubber duck? :( [05:19] I wish [05:19] spm: I'm pretty sure branch owners do! [05:19] or I'm looking in the wrong place? [05:20] * spiv hmms [05:20] I'm here: https://code.edge.launchpad.net/~drizzle-developers/drizzle/development where abouts would it hide? [05:20] Hmm, maybe it only appears for mirrored, not hosted branches :/ [05:21] blurgh [05:21] mwhudson: jml: thumper: ^^ help? [05:21] There's an API, but that might not be any easier than SQL. [05:21] um. no. :-) [05:22] hat [05:22] spm: what's the problem? [05:22] spm: what are you trying to do? [05:22] mwhudson, jml: he's upgraded a hosted branch directly on disk, and now we want to trigger a mirror of that format change [05:23] we've manually upgraded drizzle https://code.edge.launchpad.net/~drizzle-developers/drizzle/development to --2a on crowberry. but the web interface is still showing the wrong format [05:23] what spiv said [05:23] ah, two sides to this [05:23] (and we may want to do this for many more branches shortly) [05:23] 1) get the puller to run to copy the branch to the mirrored area [05:23] you can do this a number of ways [05:24] mwhudson: for future, it'd be good if admins could have a 'request mirror' button in the web ui for all hosted and mirrored branches. [05:24] with spm around update branch set next_mirror_time = CURRENT_TIMESTAMP AT TIME ZONE 'UTC' where unique_name = $foo; [05:24] spiv, I've already written a *patch to bzr* to provide a convenient plugin for this [05:24] is probably easiest [05:24] spiv: ya think? [05:25] spiv, but it was rejected [05:25] however this still won't update the web ui [05:25] spiv, writing code is way too hard. [05:25] jml: dependencies suck :( [05:25] basically you need to push a new revision to make the scanner look at the branch again [05:25] mwhudson: in this case unqiue name will be 'drizzle-developers/drizzle/development' ? [05:25] which totally sucks [05:25] (rockstar is fixing this) [05:25] spm: with a ~ in front [05:25] mwhudson: For us, just making the puller run is enough, I think. [05:25] oki [05:26] spm: ^ just puller is adequate, I think. [05:26] spiv, jml: http://pastebin.ubuntu.com/336320/ [05:26] * rockstar reads backchat to see what he's committed to fixing [05:26] (oh! the suffering!) [05:26] mwhudson: whee :) [05:27] update done [05:27] rockstar: driving the scanner from a Job [05:27] mwhudson: I'd have called the command "frob", personally ;) [05:27] mwhudson, ah yes. I are doing that. [05:27] spiv: spm-not-do? [05:29] spm: ok, the mirrored branch seems to be updated, please continue with the upgrades if you haven't already [05:29] oki [05:32] is kicked off [05:33] wooo. looks to be working! [05:33] spm: woo! [05:33] spm: eta? :) [05:33] mwhudson, that won't work for mirrored branches :) [05:33] you're a funny funny man :-) [05:34] mwhudson, see, I told you writing code is too hard.. [05:34] jml: well spotted :) [05:34] :-) [05:34] Upgraded nosmart+lp:~mordred/drizzle/add-more-cpplint [05:35] so 2mins for that one. hopefully the others are just as fast. [05:35] Probably they will be, it's only doing stacked branches AIUI? [05:35] I believe so [05:36] 2 x 238. ~ 8 hours? [05:36] Upgraded nosmart+lp:~mordred/drizzle/all-plugin-dynamic-load [05:37] so yeah about 2 mins. [05:37] and some being skipping, so that may drop the time a little [06:04] spiv: lifeless: fyi; done 26 of the 240; 18 were actually upgraded. [06:06] spm: that's sounding pretty good. [06:20] lifeless, mtaylor: Thanks for the AutoLP branches. I'm about to hit the sack, but I'll check them out tomorrow. [06:46] lifeless: spiv: https://pastebin.canonical.com/25418/ boom [06:47] spm: looking [06:47] ta [06:48] spm: please put the backup.bzr for that branch back at .bzr [06:48] oki [06:50] spiv: done [07:01] spm: pull from lp:~spiv/autolp/quickfixes (should be rev 22) and try again. Argh, hang on a moment. [07:01] :-) [07:04] spm: ok, pull now :) [07:04] spm: this version will log upgrade errors and then continue [07:04] oki [07:05] spm: hopefully it'll skip past the already upgraded branches pretty quickly as it sees that they have already been upgraded. [07:05] gee this distributed development stuff is pretty cool; having 3 separate copies of the same code and I just grab from whereever. neato idea. ;-) [07:05] argh! [07:06] bzr: ERROR: KnitPackRepository('file:///home/spm/autolp/.bzr/repository/') is not compatible with RemoteRepository(bzr+ssh://bazaar.launchpad.net/~spiv/autolp/quickfixes/.bzr/) different rich-root support [07:06] lemme guess.upgrade locally to 2a? :-) [07:06] spm: oh, just a sec, sorry [07:06] spm: this was the source of my earlier argh, but I forgot to clean it up completely [07:07] heh [07:07] argh 1 and argh 2? multiple distributed arging. [07:07] spm: ok, now [07:07] "this time for *sure*!" [07:07] heh. rev 22 [07:08] and running [07:10] ahem...9 hours in the i386 queue??? [07:10] ;) [07:11] spm: hmm, that failed branch, ~mordred/drizzle/rework-functions, it got fixed by the earlier fix step? [07:11] spiv: that's giving a nice "boom" on the "UpToDateFormat: The branch format Meta directory format 1 is already at the most recent format." [07:12] not sure. looking. [07:12] spm: I can suppress those entirely if you like? [07:13] spiv: that branch isn't showing up in a not so cursory find thru backlog. so I guess it checked as ok. [07:13] spiv: nah, she's right. [07:13] although... we will likely be using this script more. So.... perhaps I will take you up on that offer? :-) [07:14] spm: ok, just a sec :) [07:14] spm: rev 23 will just print one line for that now [07:15] spm: huh, strange [07:15] ta. I'll update afther the next fail ;-) [07:15] spm: because the mirrored copy of that branch (the one I can read) is exhibiting the symptoms of the problem that fix repairs. [07:16] Oooo kaaaay [07:19] if i attach a file to a message opening a new bug is that supposed to become a bug attachment? [07:21] poolie: I have no idea but maybe BjornT_ knows? === henninge changed the topic of #launchpad to: Read https://help.launchpad.net for help | Help contact: henninge | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: see channel #launchpad-dev [07:23] spm: no news is good news, I hope? :) [07:23] yup :-) [07:23] nm it was user error [07:23] I think It's still trundling thru the ones it'd already done [07:25] spm: Hmm, I'd have hoped it would do that pretty quickly :/ [07:26] seems to be about the same speed as the 'check' step was taking. :-/ [07:28] spiv: https://pastebin.canonical.com/25420/ [07:28] it's still going, jic it's not clear [07:31] spiv: 2 more. https://pastebin.canonical.com/25421/ [07:32] spm: hmm. [07:33] damn and another. that makes 4. I'm half inclined to stop at this point. ??? [07:33] https://pastebin.canonical.com/25422/ [07:43] spm: I'm looking atm [07:43] spm: I'd rather not leave this half-done, though [07:43] spiv: oki [07:44] spm: because un-upgraded branches will give errors [07:44] spm: and some are upgrading successfully [07:44] and this would be a BadThing™; yes. [07:44] spm: and the first one at least that failed appeared to already be at least a bit broken [07:45] heh [07:45] spm: btw, if you do restart again for some reason, pull again first, I fixed the unsubstituted "%s" :) [07:45] ta [07:46] having a fast dinner. brb. [07:51] spm: I'm zeroing in on the problem I think [07:57] excellent! [08:00] hi, I get alot of timeouts on https://bugs.edge.launchpad.net/ubuntu/+filebug this morning, OOPS-1437EC227 is one example [08:00] https://lp-oops.canonical.com/oops.py/?oopsid=1437EC227 [08:01] OW! === mthaddon` is now known as mthaddon [08:03] gmb should have a fix for that soon :( [08:03] Although it has been a huge problem for more than a year now. [08:06] spm: so, the failing branches seem to exactly correspond with the branches that need that fix [08:07] spiv: ahhh [08:07] spm: when I run the fix script manually on those branches (against the mirrored copies), I see their problems. [08:08] which begs the question, how come we didn't pick this up in the check phase? [08:08] spm: well, nosmart+ is supposed to be a workaround for that bug, so something is odd here. [08:09] :-( [08:09] spm: but I wonder if manually cp'ing the fixed hosted copy over the mirrored copy would help. [08:10] spm: although presumably this script is accessing the hosted copy, given that it's writing to it... [08:10] spiv: not sure. that's something I'd want mwh to answer [08:11] spiv, spm: where is the script? [08:12] mwhudson: most recent at lp:~spiv/autolp/quickfixes [08:14] spiv, spm: if that's running as spm, then it will be accessing branches in the hosted area. yes [08:15] it is running as spm, yes. [08:17] spiv: we've just had to bounce codehost to bypass memory pain; which dropped the connections. is restarting ok? or ...? [08:20] spm: !!! :( [08:21] spm: restarting is ok, yes. [08:21] mwhudson: I've already had to kill off about 3 individual processes :-( [08:22] spm: not associated with this drizzle script I hope? [08:23] spiv: no; it's been running all day. [08:23] I wouldn't expect it to be; nosmart+ should make it pretty friendly on the smart server. [08:24] spm: how's it going? ... looks like I hijacked your entire day :) [08:25] mtaylor: getting there! [08:25] the main branch is done. the others; slowly... some issues. [08:26] mtaylor: at the moment it appears that some branches are affected by bug 354036, and although upgrade script is supposed to correct that those branches are the ones that are failing. [08:26] Launchpad bug 354036 in bzr "ErrorFromSmartServer - AbsentContentFactory (unfixable by users) error when pulling a branch from the mirrored area" [Undecided,Confirmed] https://launchpad.net/bugs/354036 [08:26] EVIL MONTY STRIKES AGAIN! [08:26] spiv: well, are we at least being helpful in fleshing out the script? :) [08:27] mtaylor: yep :) [08:28] * mtaylor pokes mneptok in the eye [08:28] the agony is delicious. [08:32] login [08:32] Error: You are not identified [08:32] spm: If you can dig out the full log of what the early runs of that script fixed, I wouldn't mind seeing that [08:32] sure. one sec [08:50] spm: I'm off to dinner for now. I guess if I come back to this tonight it'll be with a new LOSA? [08:50] spiv: hmm. well sorta. it's running as me you see.... [08:57] spm: and I guess it has hours left to run anyway... [08:58] yes [09:53] spm: Hi! [09:53] ;) [09:54] Codehosting is slooooowwww .... [09:54] Just mentioning because it already had to be restarted once today. [09:55] wow, did somebody just kick it? [10:12] spm: spiv: hi [10:12] thanks [10:13] argh, is this wide-screen bug back on LP egde? :( [10:20] against which LP project should a bug be filed affecting different web pages (bugs, persons, projects)? launchpad-foundations? [10:20] if you don't know, launchpad. [10:21] will file there, but I made the experience that a bug filed against launchpad tends to sit there uncommented for longer than being filed against the correct subproject (but my sample data is small) [10:22] geser: if you have data about that, there is a thread about process on launchpad-dev where that would be relevant. [10:28] geser: launchpad-foundations is the right place. === sale_ is now known as sale === matsubara-afk is now known as matsubara === mrevell is now known as mrevell-lunch === henninge is now known as henninge-lunch === henninge-lunch is now known as henninge === mrevell-lunch is now known as mrevell [13:44] lifeless: for some reason the branches that need fixing are failing in exactly the way you'd expect if they hadn't been fixed. If I sftp the unfixed version to my laptop I can reproduce the exact failure, but if I run the fix script on it then upgrade works fine. [13:45] lifeless: some examples at https://pastebin.canonical.com/25421/ [13:56] spm, lifeless: I suggest rerunning the script without --no-fix. I guess the .bzr dirs of the failed branches will need to be restored from their backup.bzr dirs first. [14:10] hi henninge [14:11] hi bac ! [14:51] hi [14:51] barry, you are admin on launchpad pleaze ? [14:52] McPeter: i am not [14:52] :( [14:52] McPeter: henninge is the chr this week, he can rustle up a launchpad admin to help you out [14:53] McPeter: Hi! How can I help you? [14:54] hi henninge [14:54] i write two eamil at sunday for .. bad account on launchpad [14:54] (sorry for my english .. i'm french) [14:55] McPeter: I'd talk to mthaddon if you needed admin help. [14:55] eu .. on this accoutn you can see many link : pedophile / pronographic [14:56] i count 7 account with the same profil [14:56] McPeter: Yes, thank you. I already saw those. I was about to forward them to the admins for deletion. [14:57] * henninge saw the mails not the .... ;) [14:57] if you want i can give you accoutn in private ? [14:58] all acount open at 4 december 2009 [14:59] hi [14:59] ah :) [14:59] tand Nicke are better in english :) === sraps_ is now known as sraps [14:59] s/tand/tshirtman, and [15:00] grr ... s/Nicke/niko (sorry for hl) [15:00] the ip hosting the offending content is in sweden [15:00] but the abuse mailbox is not functionnal [15:00] so not possible to get down from this side [15:00] i use feedback@launchpad.net [15:01] I was speaking of the host of the offending content, not launchpad who just link [15:01] (which) [15:04] McPeter, tshirtman: I have reveived the email and will make sure the accounts get removed as soon as possible. What else would you like us to do? [15:04] hum [15:05] Probably fix the captcha? but I'm not sure it's the issue [15:05] no :( [15:05] The main problem was the difficulty to find someone to fix that [15:06] i found the account launchpad on my pastebin site .. [15:06] and i have captcha on my pastebin :\ [15:06] spambot ☭☠@⎈⁂㌶☣⚡☠ [15:07] the bot used a lot of uncommon tags for a project, probably a common antispam filter would detect other attempts? [15:08] next time i remeber to catch ip address [15:08] i delete post before look ip :\ [15:10] henninge: anyway thanks for your reaction :) viewing things like this on launchpad is sad :( [15:11] tshirtman: yes, I am sorry about this. [15:12] maybe you have the IP of the machine which posted on launchpad? I don't want it, but reporting to his ISP would help. [15:13] tshirtman: I will check that with the admins [15:13] ok thanks :) I have no other suggestions [15:14] shouldn't the buildds automatically pickup DEPWAITS when the missing package gets available? [15:14] gah, bad timing. It picked it up at the same time as I was looking. [15:17] heh, nice [15:20] convert to question seems to keep timing out: OOPS-1437EB607 [15:20] https://lp-oops.canonical.com/oops.py/?oopsid=1437EB607 === matsubara is now known as matsubara-lunch === noodles775 is now known as noodles775-otp === noodles775-otp is now known as noodles775 === matsubara-lunch is now known as matsubara [16:38] hello, how much time it is usually need to review the manually loaded pot-file? (I understand that it is very big with 1511 huge lines). And what does the phrase "No import target selected yet" mean? === stgraber_ is now known as stgraber [17:11] any clues why https://launchpad.net/zodbbrowser claims the latest version is 0.4? [17:11] I released 0.5 two weeks ago [17:12] and launchpad was told about that [17:12] actually, 0.5.1 was also released on the same day as 0.5 [17:13] I just went over there to tell launchpad that I've just pushed 0.6 to PyPI, and noticed this [17:15] ah, I see: it picked up several versions at the same time -- https://launchpad.net/zodbbrowser/+download [17:15] then sorted them randomly instead of by filename [17:20] https://bugs.edge.launchpad.net/ubuntu/+source/linux/+filebug/Aj0lyedhvefVXavlzDy80CgaeTT#form-start says "inux (Ubuntu) guidelines: Please report a bug about the kernel using the following command in a terminal:  ubuntu-bug -p linux" [17:20] "Warning: The options -p/-P are deprecated, please do not use them. See /usr/bin/ubuntu-bug --help" [17:21] how do I file a bug against lp/linux/+filebug ? === jon is now known as Guest74571 [17:35] CarlFK: ubuntu-bug linux [17:38] could someone take a look at: https://answers.edge.launchpad.net/ubuntu/+source/gnome-panel/+question/93177 ubuntu answers [17:39] is there a way to get rid of this sort abuse... [17:40] we all are trying to help [17:44] Hi! Do the HTTP repos differ from the ssh repos? Usually notice an update lag between them so I'm assuming so. We upgraded the shared repo for lp:drizzle and the http repos seem to still be in old non-2a format. Any thoughts? http://pastebin.com/d6648d23b [17:50] maxb: are you sure? (the problem is the text on the lp page, not the linux package... but I can see it being the same person's problem) [17:50] Oh, you want to file a bug on the bug filing instructions === henninge_ is now known as henninge === henninge changed the topic of #launchpad to: Read https://help.launchpad.net for help | Help contact: - | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: see channel #launchpad-dev [18:08] maxb: right [18:09] CarlFK: I have forgotten who has the power to change those. You might ask in #ubuntu-devel [18:12] spm: you up yet? [18:48] mtaylor: it's not yet 6am local for him [18:48] only lifeless is insane enough to be up that early [18:49] mwhudson: :) === micahg1 is now known as micahg [19:48] Sorry for repeating. how much time it is usually need to review the manually loaded pot-file? (I understand that it is very big with 1511 huge lines). And what does the phrase "No import target selected yet" mean? [20:11] moradan: it usually takes a few days for the manual import [20:11] moradan: you can also set up a bzr branch that contains your pot file (like a branch of your source tree) [20:12] moradan: and tell launchpad to pull new versions of your pot file from that branch [20:12] moradan: it will then put the translations into a branch that you can merge from - to more automate the import/export process [20:13] mtaylor: thanks for info. Is setting a bzr branch worth doing that if the developement is very active and on sourceforge. And all that I want to do is to translate a help system from the stable release - 1511 lines in .pot-file? [20:13] moradan: not really [20:14] moradan: if you're doing your dev in a bzr branch, then it's just an easier mechanism for you [20:14] ASAIU after reviewing .pot file I will be able upload the corresponded .po-files for different languages without reviewing? [20:20] moradan: yeah, AKAIK [20:21] moradan: yeah, AFAIK [20:21] cgah [20:21] thanks [20:32] lamont: Hi. Apparently I need to talk to you about upgrading dpkg everywhere. === matsubara is now known as matsubara-afk [20:40] how do I create a new team in Launchpad? [20:41] The link is on the front page [20:41] maxb: thanks. I was expecting to find that in my personal page. [20:44] is it allowed to open a socket to localhost during a build (in a ppa or in a native build)? [20:46] fta: It is technically possible, and the machines are secure, so I don't see why not. [20:47] wgrant, i run some unittests and they fail a lot on network accesses, so i'm investigating [20:48] fta: Log? [20:48] net_unittests, 987 tests, 61 failed [20:48] http://launchpadlibrarian.net/36542743/buildlog_ubuntu-jaunty-amd64.chromium-browser_4.0.266.0~svn20091206r33943-0ubuntu1~ucd2~jaunty_BUILDING.txt.gz [20:48] spiv: thanks for looking at that in such detail [20:48] (this same thing was actually discussed on debian-devel a day or two ago) [20:49] mtaylor: chex is on at the moment, spm in 2 hours [20:49] lifeless: morning! [20:49] wgrant, i have failures on network accesses, dns requests, shared mem (no perm), etc.. [20:49] lifeless: well, I've worked around the issue (which actually involved doing a thing I'd been meaning to do for a while - which is getting all of the build slaves to use ssh transport) [20:50] mtaylor: oh, format not propagating? [20:50] mwhudson: ^ [20:50] lifeless: yeah - the http branches for some of the branches (like lp:drizzle/build) are sort of borked [20:50] fta: The first two are understandable. [20:51] mtaylor: hmm [20:51] They're not meant to work. [20:52] wgrant, my biggest problem is that network requests block the build, and so they are killed after 4h without output, so i had to implement various tricks to workaround that [20:52] mwhudson: http://hudson.drizzle.org/view/Drizzle-build/job/drizzle-opensolaris-64-build/275/console [20:52] mwhudson: in case that's helpful [20:53] yes, looks like the format change hasn't propagated [20:53] fta: That seems to be a bug in your build system. [20:53] Builds should poke the network just because. [20:53] s/should/shouldn't. [20:55] wgrant, not the builds, i'm talking about running unittests [20:55] mtaylor: looks like the branch hadn't been mirrored [20:55] mtaylor: i requested it by hand and it seems fine now [20:55] wgrant, i've been doing that since ~last year [20:55] mwhudson: awesome. thanks [20:56] mwhudson: any ideas about why they wouldn't mirror? [20:56] mwhudson: mtaylor is suggesting that this happened to many branches [20:57] lifeless, mwhudson: actually - I have only information on lp:drizzle/build [20:57] I haven't looked at the others - [20:57] mtaylor: ah,ok. [20:57] the one of posulliv's that wasnt' upgraded was not upgraded ssh side [20:57] so we just hitchhikered in, removed the .bzr dir and re-pushed :) [20:57] lifeless: no, not really [21:01] hey all, i tried to create a mail via email interface several hours ago, and nave not gotten any response [21:02] i tried the email interface because the web interface was timing out for me. [21:02] smoser: Did you sign the email? [21:03] the other times i've created bugs via email i at least got "bad syntax" messages if they were bad, and if good they responded fairly quickly. [21:03] i did sign [21:03] http://paste.ubuntu.com/336823/ [21:05] mwhudson: http://pastebin.flamingspork.com/2507 [21:05] mwhudson: same thing with lp:drizzle/staging [21:07] mtaylor: fixed now too [21:08] anyone know how to remove my team from another team? [21:08] mwhudson: rock. thanks [21:20] wgrant, i can't write in /dev/shm/ at build time, right? [21:22] fta: I don't know. === verterok is now known as verterok|brb [21:23] wgrant, Creating shared memory in /dev/shm/com.google.chrome.shmem.unit_tests-28518 failed: Permission denied [21:25] the build runs as fake-root, so you can't really do much === verterok|brb is now known as verterok [21:40] Joe_CoT: The other team's admin can deactivate your team's membership [21:40] maxb : so I can add my team to another team, but I can't remove it? [21:40] There does not seem to be any UI to allow a team admin to deactivate their team's membership in other teams, which is a bit silly IMO [21:41] Apparently :-/ [21:41] This seems worth a bug, if you have a moment to file one [21:44] mars, yeah, I'll file it later then. Just hoping there was something I was missing. thanks [21:44] s/mars/maxb/ :-) [21:44] yeah, that, lol [21:45] real issue here is this: https://edge.launchpad.net/~deadubuntuteam [21:45] that's apparently an old team, which a bunch of teams joined. It's now defunct. instead of the team being deleted, it was renamed to DeadBuntu [21:45] leading to a whole lot of "ZOMG why am i a member of deadbuntu?!" === salgado is now known as salgado-afk === EdwinGrubbs is now known as Edwin-afk [22:35] ls [22:35] wgrant: dpkg.. sigh [23:15] Error ID: OOPS-1437EB112 [23:15] https://lp-oops.canonical.com/oops.py/?oopsid=1437EB112 [23:15] FYI [23:22] Where are the release notes for the last release of Launchpad? [23:24] BUGabundo, its a timeout [23:24] lamont: Quadruple-sigh from me. Apparently we need it on all machines, so we can depend on it in launchpad-dependencies, even though only three or four LP machines actually need it. [23:24] cody-somerville: ok [23:26] wgrant: sounds like a new meta package to me... we really don't want it $everywhere [23:26] say launchpad-dependencies-soyuz [23:26] lamont: That's what I thought. But I suspect you'll need to argue with spm. [23:26] spm: I win. kthx. [23:27] wgrant: see. solved. :-) [23:28] spm: Do I want to create the new metapackage? [23:33] wgrant: not sure tbh. this being the lp-deps-soyuz meta package? [23:34] spm: Yes. [23:35] wgrant: if you're keen to do so, I'd personally be delighted! :-) [23:37] mtaylor: heyo! [23:39] hey spm ! [23:39] spm: thanks for upgrading everything! [23:39] no worries; has it all worked? my console seession went *really* odd towards the end there.... [23:40] hehe [23:40] mostly, yeah. [23:40] some of our local resources weren't upgraded when I thought they were [23:40] ah. that'd help. :-) [23:40] and there were a couple of branches that didn't upgrade the http mirrors [23:40] but all is up and running now [23:40] w00t! [23:40] Naming consistency suggests it should be called launchpad-soyuz-dependencies [23:40] awesome! [23:40] maxb: point! [23:59] help, all of a sudden my packages are rejected [23:59] Rejected: [23:59] Unable to find qhimdtransfer_0.0.1.orig.tar.gz in upload or distribution. [23:59] Files specified in DSC are broken or missing, skipping package unpack verification. [23:59] the day before it worked [23:59] and the logs look almost identical