[01:16] Good morning. [01:17] oh hai === CcxCZ_ is now known as CcxCZ [03:05] Hm. Can you suggest a reason why installing the bzr-builddeb package wants to bring in the entire libqt stack? [03:14] its in love! [03:15] is qbzr being dragged in somehow? [03:16] mwhudson: as far as I could tell, no [03:16] This was a nearly naked server system; [03:16] (ie, no Desktop) [03:16] I subsequently removed the *qt* and apt didn't try to remove bzr-builddeb [03:17] so I was really at a loss as to wtf [03:17] recommends vs depends [03:17] I install with -o Install-Recommends=false [03:17] (and it still came in; I look closely for that sort of thing) [03:18] what does apt-cache bzr-builddeb show for you [03:18] under depends, recommends & suggests [03:18] (ie, there was something in the Recommends: column that was nothing to do with libqt* [03:18] lifeless: I looked through that too. Its innocent, as far as I can tell === CcxCZ_ is now known as CcxCZ [03:19] [which is why I raise this casually here; it was _weird_] [03:19] so, to diagnose it [03:19] apt-cache rdepends [03:19] the package that was being brought in [03:19] yeah, I didn't think to try that at the time [03:19] and/or remove bzr-builddeb and install it again [03:25] lifeless: I tried that too [03:25] oh [03:25] and /var/log/apt/ has some debug stuff [03:25] (I'll keep an eye out for this; at the moment that machine is churning away building things, so...) [03:25] true, [03:25] looking [03:27] ah ha [03:27] it was arora, depending on libqt4-webkit [03:27] * AfC wonders what arora is [03:27] some kind of web browser, obviously... but what pulled it? Weird. [03:28] Well, embedding mail reading in everything was SO 1980's. So now all apps grow until they can render HTML. [03:28] lifeless: nice call on /var/log/apt/history.log [03:29] if don't have a browser [03:29] then the first explicit one listed (if one is) is pulled in [03:29] someone has a clause like [03:29] some kind of virtual package requirement, presumbably [03:29] arora | web-browser [03:30] yeah [03:30] eek [03:53] hi all, i'm back [03:55] wb [03:59] poolie: wb [04:00] thanks === timchen1` is now known as nasloc__ [05:09] Hi. Is there any gotchas in makine /etc a bzr working tree. [05:09] andrewblack: bzr doesn't track permissions very closely [05:09] andrewblack: permissions on funky files within the /etc tree within the .bzr directory. [05:09] so i think you might want to use a wrapper like etckeeper [05:10] or lock down /etc/.bzr [05:10] http://joey.kitenet.net/code/etckeeper/ [05:10] ok - will look at etckeeper [05:10] mwhudson: nice tag teaming there. high-five :-) [05:11] spm: aren't we supposed to do that in a privmsg? [05:11] :) [05:11] um.... [05:13] It says it tracks changes during package updates. What about manual changes to /etc/xxxx files [05:19] you can manually check those in [05:19] it'll also auto check those in next package update [05:19] if you want; you can always setup some sort of cron script that alerts/or auto-commits changes [05:20] at $job-1, we had a process rule; any /etc or other config changes were always done thru a wrapper script that would check the edited file in/out/diff of an RCS store. [05:24] ho hum. said article has gone the way of the dodo. was on the samag.com website; now defunct. [05:25] Thanks spm [05:26] so basically it sets up the repos in a way that is permission friendly [05:32] ok - I wanted to edit a cron job (and get it under bzr first) [05:32] turns out the that thing I needed to change was in a file it calls that was already in a bzr tree. [05:36] hrm. not so much permission friendly; more permission *unfriendly*. /etc/.bzr ==> 0700 type of thing. [05:57] http://bazaar.canonical.com/en/ seems to be a little old on the released bzr status [06:06] thanks thumper, i'll check why later [06:06] poolie: we should have a chat some time [06:06] soonish [06:06] we should [06:06] now is good with me, if you like [06:06] (or in about 2m) [06:10] poolie: I'm sprinting this week, but would still like to organise something... [06:10] induction for wallyworld_ [06:17] yay wallyworld_ ! [06:17] thumper: how about now [06:18] hi poolie [06:18] * thumper fetches headset === r0bby is now known as robbyoconnor [07:45] hi all ! [07:45] wv poolie ! [07:45] meh [07:45] wb [07:45] hello vila, how are you? [07:45] first typo in second msg, looks like a good way to start the week :) [07:46] poolie: great, about to half the active review queue by landing those long awaited fixes :) [07:49] only 660 messages to go .. [07:50] Hi all. [07:51] hey GaryvdM ! [07:52] spiv, vila, did either of you do anything about unlocking on interrupts, or coping when we were interrupted? [07:52] poolie: nope, I thought you were working on it and then... went to other things [07:53] poolie: ping [07:55] * bialix waves at ddaa [07:55] Hi bialix [07:56] Heya Gary! I happy to see you [07:59] I'm trying to write some tests for qlog. I need to create branches with interesting graphs. I looked at BranchBuilder to see if it would make things easier, it helps some what, but one thing that is crufty is having to branch my branch on disk so that I can create a diverging graph. Is there a helper to make this easier? [08:01] np, i might look at it this week [08:02] GaryvdM: invoke `bzr branch` command via self.run_bzr? [08:05] poolie: no, I didn't either. [08:14] what did you two get up to? [08:17] poolie: resuming working on transform targeting allowing deleting dirs containing .pyc files [08:17] s/resuming/resumed/ [08:18] nice [08:24] GaryvdM: can you look at https://code.launchpad.net/~s-dumbie/qbzr/ench_qdiff/+merge/33986 [08:25] one russian guy contacted me with patch couple of months ago. then yesterday friend of him decided to finish that patch [08:25] GaryvdM: as I understand some of their changes should be reworked with new toolbar in qdiff. but we don't have one yet. [08:26] bialix: Ok [08:26] we (I) may ask him to split the patch into smaller pieces [08:26] if it helps [08:27] * vila banhs head on desktop, from pqm: "Exception processing merge: Unknown branch format: 'Bazaar-NG Loom branch format 7\\n'" [08:27] bialix: Hopefully the search stuff can be made common with annotate too. [08:27] yeah, banhs, brohe a teeth doing that [08:28] vila: we're with you! [08:28] * fullermd broke a tooth on the bottom of a pool once. [08:29] tooth yeah, the only remaining one in fact [08:29] fullermd: forgot to check for water ? [08:30] Oh, no. There was water. It was pretty bizarre; I probably couldn't do it again if I tried. [08:30] Not that I plan on trying, though. Unpleasant experience. [08:30] fullermd: and *that* was the last time you left your basement right ? [08:31] Well, it shoulda been :p [08:31] :-D [08:31] But I was young and foolish, and therefor sociable, back then. [08:31] fullermd: such a loss of time... [08:32] I know! All those afternoons I could have spent plotting the downfall of humanit... er, studying and improving myself. [08:45] spiv, what's new with you? [08:50] errr, what did I miss ? pqm got a faster machine ? I wasn't able to see my requests on http://pqm.bazaar-vcs.org/, yet they have landed... [08:51] today speed of light is much faster I suppose [08:51] hi bialix [08:51] vila, oops [08:51] i suggest you send one you know will fail [08:52] hi poolie [08:52] and make sure that it does [08:52] spiv does my guess on bug 626649 sound plausible? [08:52] Launchpad bug 626649 in Bazaar "pull from one ssh branch into another fails with TooManyConcurrentRequests (affected: 1, heat: 6)" [Undecided,New] https://launchpad.net/bugs/626649 [08:54] poolie: you're kidding ? Time to send all those controversial patches instead :) [08:55] poolie: yes, very plausible, I waited far too long to report it wanting to write a test for it :-} [08:57] poolie: I work around it with: 'bzr unbind ; bzr pull -v ; bzr push ; bzr bind' [09:00] yup, it's a dupe of bug 483661 [09:00] Launchpad bug 483661 in Bazaar "bzr pull bzr+ssh into a bound branch fails with TooManyConcurrentRequests (affected: 3, heat: 4)" [High,Confirmed] https://launchpad.net/bugs/483661 [09:00] poolie: yep, that sounds plausible. Not 100% sure, but definitely plausible. [09:03] poolie: I did some measurement of where we're at with gcc-linaro, and found a 15% win for one of the cases. [09:03] oh, nice, what was that [09:04] Although for some reason I'm having trouble with getting useful results with --lsprof-file and kcachegrind, I'm not sure why yet. It might be something about trunk, or something about maverick... [09:04] It turns out that InterTree.iter_changes was doing "if file_id in self.target.all_file_ids()" in a loop. [09:05] so recalculating all the ids every time? [09:05] Right, which means set(tree.inventory) [09:07] maybe that should be deprecated [09:07] hm [09:07] Anyway, Tree already has a __contains__ method that does that check without iterating over an entire inventory, so "if file_id in self.target" is the trivial and faster replacement. [09:07] ok [09:07] no, i guess profiling is probably a better way to find expensive things called repeatedly [09:07] i'd like to delete __contains__ etc [09:08] vila does this mean all those recently merged things of yours perhaps should not have merged? [09:08] or did you integrate them and then send the whole thing? [09:08] poolie: investigating [09:09] poolie: I went with pqm-submit instead of feed-pqm because looms were involved (and not supported by pqm) but that still use the "regular" pqm way [09:10] hmm, looks like I used syntax accepted by python-2.6 but not 2.5, so probably not 2.4 either [09:11] that in turn would mean that pqm accepted the merge when selftest failed with a syntax error... bad bad [09:13] vila: ! [09:14] rhaaaa, on no more py25 on lucid... shudder [09:22] spiv: Isn't it a nice way to land a patch ? [09:25] poolie, spiv: here is the fix: http://paste.ubuntu.com/485753/ [09:27] poolie, spiv: I will send this to pqm *now* and check for fallouts (unless you yell loud) [09:28] * poolie looks [09:28] vila, is this because py25 won't let you use *args and also regular kwargs? [09:29] poolie: seems so, 2.4 and 2.5 fail without and succeed with this patch [09:29] but doesn't pqm use 2.4? [09:30] I don't remember if it stills uses 2.4 or 2.5, but I've filled bug #626667 [09:30] Launchpad bug 626667 in PQM "syntax error doesn't prevent merge (affected: 1, heat: 6)" [Critical,Confirmed] https://launchpad.net/bugs/626667 [09:31] losa: can you help diagnose bug #626667 by checking the recent logs on the bzr pqm instance ? [09:31] poolie: ok to land the above fix ? [09:31] vila, i guess so [09:31] i really want to work out why it wasn't rejected though [09:32] sent [09:32] as i'm sure you do too :) [09:32] poolie: yup, hence the bug [09:32] losa: first data point: which python version is used there ? 2.4 or 2.5 ? [09:33] hey [09:33] http://paste.ubuntu.com/485756/ hmpf [09:33] I accidentally uploaded some stuff to lp without fixing bzr whoami first [09:34] is there a way to fix my commits? [09:34] vila: not loud yells from me [09:34] s/not/no/ [09:35] bug 626667 updated... just lovely [09:35] Launchpad bug 626667 in PQM "syntax error doesn't prevent merge (affected: 1, heat: 6)" [Critical,Confirmed] https://launchpad.net/bugs/626667 [09:36] lvh: uncommit, or push --overwrite [09:37] bialix: so if I fix whoami, and then push --overwrite, it'll be fixed? Cool, thanks [09:38] lvh: no [09:38] bialix: huh? what do I do then [09:38] lvh: you have to redo your commits locally and then push --overwrite [09:38] how many of them do you have? [09:38] so 10:36 lvh: uncommit, or push --overwrite => uncommit *and* push locally [09:38] twenty or so [09:39] I didn't have a working internet connection to push to lp [09:39] so it took me about a day to notice [09:39] what's wrong with your old whoami? [09:40] lp doesn't link it to my user profile correctly [09:40] it doesn't have my email address [09:40] lvh: and you don't get karma ? [09:40] it's not too bad [09:40] vila: maybe, I don't know [09:40] yes, it's not a major issue [09:41] I was just hoping there's a way of letting lp know "oh hey that guy, that's me" [09:41] lvh: that's the only consequence I can think of [09:41] lvh it has no address at all? [09:41] poolie: worse, it has a useless one [09:41] 20 commits... you can redo them one by one, or maybe use bzr-rewrite plugin [09:41] It says Laurens Van Houtven [09:42] lvh: try adding this email to your lp profile [09:42] you can add it to your profile as alternate mail [09:42] vila: aha, okay [09:42] bialix: Is that possible without mail confirmation? [09:42] lvh: not sure lp willl accept an invalid email but worth a try [09:43] A confirmation message has been sent to 'lvh@bruichladdich'. Follow the instructions in that message to confirm that the address is yours. (If the message doesn't arrive in a few minutes, your mail provider might use 'greylisting', which could delay the message for up to an hour or two.) [09:43] That'll backfire :) [09:43] lp is too smart [09:43] lvh: all you have to do now is register this TLD :-D [09:44] lvh: You could as in #launchpad if there is a way around that, or fix up the commits and push again.. [09:44] maybe you can file a bug report against lp itself and ask for such deature [09:44] Okay, thanks :) [09:44] s/feature [09:47] https://launchpad.net/bzr-rewrite is that the rewrite plugin I want? [09:47] lvh: yes [09:49] vila is it just me or is --parallel still a bit flaky? [09:49] i get "failed to connect to ssh server" [09:49] oh, heh, and the strace tests are broken by maverick's policy change there [09:50] poolie: ENOTENOUGHCONTEXT [09:50] poolie: is that with the leaking tests fix landed ? [09:50] ERROR: bzrlib.tests.test_transport.TestSSHConnections.test_bzr_connect_to_bzr_ssh: Unable to connect to SSH host localhost:51613; [Errno 111] Connection refused [09:50] that's just in trunk as of a few minutes ago [09:51] Okay, so lets say I want to fix all my commits and then push --overwrite, how does rewrite make my life easier [09:51] poolie: on maverick? That's a paramiko bug relating to IPv6 [09:51] poolie: sounds like either a transient one or something related to a spiv fix for paramiko [09:51] oh ok, thanks [09:51] how about bug 626679 [09:52] Launchpad bug 626679 in Bazaar "test_strace_result_has_raw_log fails on maverick (affected: 1, heat: 6)" [Medium,Confirmed] https://launchpad.net/bugs/626679 [09:52] I should nag upstream and/or the Ubuntu packager to include my patch, I guess. [09:53] poolie: I'd like to draw your attention to bazaar.canonical.com/en/index.html page [09:54] * poolie looks [09:54] i need to go soon [09:54] hi bialix [09:54] that page has section "Developer's Blog" [09:54] what about it ? [09:54] hi poolie [09:54] but it links to "None", i see [09:54] the section is empty for me. [09:55] but when I'm regenerating the index on my machine it's not empty [09:55] does this index regenerated on the production server? [09:55] it seems production server has no access to wordpress feed, or something like that [09:56] I have no idea how that page deployed, but there is definitely some problem [09:57] i'll check it out on the production server [09:57] ping LOSA [09:57] and btw local index has link to http://bazaarvcs.wordpress.com/ and not to None [09:57] something weird [09:58] vila: hi [09:58] mthaddon: hey ! [09:59] mthaddon: really bad bug on pqm bzr instance: bug #626667 [09:59] Launchpad bug 626667 in PQM "syntax error doesn't prevent merge (affected: 1, heat: 6)" [Critical,Confirmed] https://launchpad.net/bugs/626667 [09:59] losa: can you help diagnose bug #626667 by checking the recent logs on the bzr pqm instance ? [09:59] losa: first data point: which python version is used there ? 2.4 or 2.5 ? [10:00] Okay, I installed bzr-rewrite. I don't think rebase is what I want if it's anything like git's [10:00] mthaddon: a fix for *bzr* is currently landing, but pqm needs to be fixed, we prefer to rely on pqm to *detect* such problems :) [10:00] vila: it's a hardy chroot, so python 2.5 is the default [10:01] mthaddon: ok, that's one thing [10:01] vila: in what way does PQM need to be fixed? [10:02] see the bug report, despite an *error* it happily merged the submission [10:05] hi [10:05] bialix: it's a problem with the proxy setting being not seen [10:05] when doing bzr export i get the following error: bzr: ERROR: zlib.error: Error -3 while decompressing data: incorrect data check [10:05] fixed now, thanks for letting me know! [10:05] poolie: :-) [10:05] after googling i found that this means an data error [10:06] is there some way to fix this [10:06] bzr status / bzr commit and so on still work [10:07] nomatter001: try to branch it to new location [10:08] nomatter001: try 'md5sum .bzr/repository/packs/*' and check that the md5sums match the filenames [10:10] vila: pqm just works by submitting if the command you give it returns a "0" exit code - if for some reason the conditions you're describing still return a 0 exit code, then PQM is still doing the right thing [10:11] mthaddon: right, so what is this command for the bzr instance ? [10:11] spiv: not for all files [10:11] Hi. I don't understand how to use the rewrite plugin to change the author of a bunch of commits. [10:12] vila: for which branch? [10:12] bzr rebase appears to be for rebasing branches like git's rebase, which isn't quite what I want (I think). [10:12] mthaddon: bzr.dev [10:12] mthaddon: but I hope it's the same for all bzr branches :-} [10:12] spiv: for 1 file it is different [10:12] spiv: what can i do? [10:12] vila: "make check PYTHON=python2.4" :( [10:13] mthaddon: LOL, good so it's 2.4 finally, I'll look into 'make check' now [10:13] spiv: rename the file? [10:15] i'm off, see you later [10:15] mthaddon: wow, reproduced, indeed, there are two commands for the make target and the second one is eating the first error :( [10:16] good to have reproduced... [10:16] mthaddon: thanks a lot [10:16] mthaddon: I've enough info to propose a fix [10:16] ok, cool [10:17] nomatter001: if they don't match, the data in the repository doesn't match what bzr thought it was writing to disk, which probably indicates filesystem corruption has occurred :( [10:17] * vila re-re-re-re-reading the make doc to find the right prefix [10:17] spiv: so what can i do? [10:18] spiv: can i get a diff between real data and what bzr thinks it should be? [10:18] nomatter001: ideally, rebuild the repository from backups or other (good) copies that don't exhibit that error [10:18] First, you reverse MD5... [10:19] spiv: i have an online repository which i branched right now where no error happend when i exported [10:19] but i made a push into it (i think after error happend) [10:20] can this still be valid? [10:20] nomatter001: is the file that doesn't match an empty one ? [10:20] villa: no [10:20] nomatter001: ok, so I'd make a new repository from that one, and then if you have new data in the damaged one branch/pull the new branches/revisions into it and hope they aren't affected. [10:21] spiv: ok thx [10:21] 'bzr check' when you're done should tell you if it the result is ok [10:22] (Although just checking the md5sums would be a good and quick sanity check too) [10:22] nomatter001: out of interest, which filesystem and OS, and has your system crashed at all? [10:23] ha, yeah, 'cmd1 | cmd2' in a Makefile... nice way to ignore errors in cmd1... [10:24] spiv: archlinux, ext3 and no [10:24] no crash at all [10:25] nomatter001: then it could be your HD slowly dying :-/ [10:25] vila: hd is 2 months old [10:25] nomatter001: the pack files are named with their md5sum and are *never* modified after that [10:26] nomatter001: wow, that's really surprising then! [10:26] vila: would be quickly dying [10:26] :-/ [10:26] nomatter001: what the english expression for that: infant mortality ? [10:26] vila: exactly [10:26] nomatter001: some electronic devices die young or never, something like that [10:27] I've also heard "bathtub curve of reliability" [10:27] vila: yes i think its called mtbf [10:27] nomatter001: *I* would closely monitor this HD [10:27] mean time between failure [10:27] These are hard drives. It's not a bathtub, so much as an endless abyss. [10:28] It's a question of the shape of the curve, not just where the mean is :) [10:28] nomatter001: all reports I've seen about such corruptions were massively empty files after crashes, the few others were hardware problems [10:28] vila: ok great ... [10:29] nomatter001: I wish you the best but... if you really had no crashes nor rude reboots... [10:29] nomatter@nomatter-laptop ~ % uptime [10:29] 11:30:52 up 11 days, 14:47, 1 user, load average: 0.00, 0.02, 0.05 [10:29] scary, and you're sure the pack file has been created since then ? [10:30] vila: hmm thats another question [10:30] i have no idea when this files are created? [10:30] nomatter001: oh, the modification time should be good for that :) [10:30] nomatter001: they are *never* modified ;) [10:30] 'stat that_file' should show you the mtime (and the ctime) [10:31] vila: -rw-r--r-- 1 nomatter nomatter 55804179 Aug 10 07:40 925afb86da175268da810b3337d50eea.pack [10:31] Except by the hard drive ;) [10:31] ok no before [10:31] nomatter001: right, so that's before your uptime [10:31] fullermd: ;) [10:31] vila: i have no idea what happend in that timeframe [10:32] but what i know is that i could make exports since then [10:32] nomatter001: so hope for a crash, cross your fingers, kill a chicken, and monitor this HD for any suspicious activities ;) [10:33] nomatter001: follow spiv directions, if 'bzr check' is ok, then you're fine [10:36] ok seems that the online repo is finde [10:36] *fine [10:36] i'm lucky [10:36] so i have only to hope that another of my local branches is ok then i'm rescued [10:37] thx for the help so far [10:38] nomatter001: if you use a shared repo, you only need to fix the repo [10:38] nomatter001: you're welcome, and good luck with the mysterious corruption :/ [10:38] vila: how can i fix the repo? [10:40] nomatter001: ECONTEXT, I thought you just did that ? [10:41] vila: i created a new repository [10:41] and branched the trunk branch from the online repo [10:42] nomatter001: a shared repo ? [10:43] vila: no normal repo [10:43] or no shared-repo [10:43] damn [10:43] nomatter001: let step back [10:44] how many branches did you have on your laptop, are they sharing a repo or are they standalone branches ? [10:44] i have no idea i just followed the tutorial [10:44] i made a repo with bzr init-repo [10:44] wo i think a shared one [10:44] yup [10:44] and in that i had several branches [10:44] err, init-repo creates a repo, if your create branches below that, they'll use this shared repo [10:45] ok [10:45] run 'bzr info' in such a branch and you can confirm that [10:45] yes [10:45] and this shared repo doesn't work [10:45] ok [10:45] cause one pack doesn't match the md5 [10:45] i also have a online-repo [10:46] so a shared repo contains all revisions ever created by any branch there [10:46] and now i just created a new shared repo [10:46] and branched the one branch in the online-repo into the new shared repo [10:46] and that seems to work [10:46] good [10:47] how many branches do you still need to get back ? [10:47] vila: only one is important [10:47] nomatter001: is it in the online repo ? [10:47] vila: the other ones have no changes i still need (all important ones are in trunk and online) [10:47] no that one is not online [10:48] but if it doesn't work i have the code (outside of the repo online) [10:48] ok, but all the changes are still in the working tree, right ? [10:48] vila: yes [10:48] nomatter001: try running 'bzr revno' in this branch [10:49] ok [10:49] its 50 [10:49] nomatter001: try branching this branch under the new repo, this will transfer all needed revisions from the broken repo to the new one OR fail [10:50] vila: ok i'll try right after fixing the testserver (last scriptrun destoyed code there after incorrect export) [10:51] nomatter001: meh, this is unrelated right ? [10:51] nomatter001: then ping me when you're back [10:52] vila: 1 minute [10:53] vila: so now i'll try branching [10:54] ok seems to work [10:55]