poolie | hi all | 00:00 |
---|---|---|
GRiD | hello | 00:05 |
poolie | hi grid | 00:05 |
Noldorin | hi jelmer | 00:20 |
michaelh1 | HI. http://doc.bazaar.canonical.com/plugins/en/ is a bit broken at the moment - shows a directory index. | 01:29 |
michaelh1 | I ended up there by Googling bzr colo which lead me to the missing http://doc.bazaar.canonical.com/plugins/en/colo-plugin.html | 01:30 |
poolie | hi michaelh1 | 02:24 |
poolie | huh | 02:24 |
michaelh1 | Hey | 02:24 |
poolie | i'll have a look at it | 02:25 |
poolie | actually, i have to go out right now, but i'll have a look at it soon, thanks for pointing it out | 02:27 |
=== robbyoconnor is now known as hamsterdance | ||
=== hamsterdance is now known as robbyoconnor | ||
=== michaelh1 is now known as michaelh1|away | ||
=== elmo_ is now known as Guest35863 | ||
mgz | morning all | 08:03 |
poolie | hi all | 08:28 |
mgz | hey poolie. | 08:28 |
poolie | just the man | 08:29 |
poolie | can you remind me - would python's default stream encoding change when it's run from cron? | 08:29 |
poolie | it seems like it fails there but not when run from a terminal | 08:29 |
poolie | even with LANG set | 08:29 |
mgz | I'll check, but eg sys.stdout.encoding possibly depends on having a terminal, it can sometimes be None certainly | 08:31 |
mgz | yup, in pythonrun.c | 08:38 |
mgz | for some reason, the setting of the encoding attribute depends on isatty | 08:39 |
mgz | if PYTHONIOENCODING is set to something (probably Python 2.7 only), that is used. | 08:39 |
poolie | i thought so | 08:40 |
poolie | and i'm lazy | 08:40 |
poolie | gar | 08:40 |
mgz | it's not terribly clear why this logic is used. | 08:41 |
poolie | ok | 08:42 |
poolie | kanbans have been failing from cron (and spamming me) because there is a unicode character somewhere in the output | 08:42 |
vila | hey guys | 08:44 |
poolie | i think i will just manually create an encoder | 08:45 |
mgz | shortest fix is probably replace sys.stdout with a codecs module wrapper that encodes to locale.getpreferredencoding | 08:45 |
poolie | hi vila | 08:45 |
vila | just recorded a new signature for lp being down, the package importer made tea happily and should do so for the next rollouts | 08:45 |
mgz | as long as you're consistent with trying to output unicode, and not mixing in non-ascii bytestrings | 08:45 |
poolie | it's actually writing to a file not stdout | 08:45 |
poolie | but yes | 08:46 |
vila | I'm still looking at the 6 failures which may also be recorded as identifying lp being down | 08:46 |
vila | s/6/4/ | 08:46 |
poolie | oh? | 08:46 |
poolie | until we deploy a new restfulclient it will continue to mishandle 503 in reading a collection, perahps | 08:46 |
poolie | ... or actually i think i put in a new workaround? | 08:47 |
vila | hehe, one involves preload_root_objects :) | 08:47 |
vila | poolie: right | 08:47 |
vila | in the mean time 'requeue --auto <pkg>' is good enough | 08:47 |
vila | done, so 5 new signatures added, | 08:52 |
vila | the first one was *during* the downtime and as such represents the first access to lp which is the most important one | 08:53 |
poolie | ok running now, hopefully better, off to squash | 08:54 |
vila | the others were easy to analyze which is good as it means we can progressively update them to cover all cases as they appear | 08:54 |
vila | poolie: enjoy :) | 08:54 |
poolie | happy udd hacking | 08:54 |
mgz | happy squashing | 08:57 |
vila | excellent, imports aborted during lp down time have already been re-processed with success (with some 'requeue --priority' help ;) | 09:00 |
jnl | hi i've ran into a problem where im now missing a couple of commits: i had a colo-workspace with two branches "trunk" and "foo". i wanted to switch betweem them but forgot (or actually thought i didnt need it) to add the "colo:"-prefix and ran "bzr switch trunk" while on the foo branch, and then switched back with "bzr switch foo" | 09:56 |
jnl | but.. the foo-branch im on now is not the colo-branch "foo" | 09:56 |
jnl | in fact: | 09:56 |
jnl | bzr colo-branches | 09:56 |
jnl | bzr: ERROR: No colocated workspace in . | 09:56 |
jnl | is there any way to get my colo-workspace/branches back? | 09:56 |
jnl | i had a couple of commits in colo:foo that are gone now... | 09:58 |
jam | jnl: find . -path '*/.bzr/branch' ? | 10:09 |
jnl | jam: ah! ./.bzr/branches/foo/.bzr/branch | 10:27 |
jam | jnl: right, that is how colocated stores the real branches | 10:28 |
jam | I'm not sure how to get your working space colo-ified again | 10:28 |
jam | but the history is still available | 10:28 |
jnl | jam: bzr log in that dir looks like my missing branch! | 10:28 |
jnl | sweet, thanks! | 10:28 |
redwyrex | jelmer: I managed to get everything into svn, though I had to limit it to 100 changes at a time because the propery hook would fail for some reason after doing many | 11:46 |
jelmer | redwyrex: oh, that's odd | 11:49 |
jelmer | redwyrex: what's the error? | 11:49 |
redwyrex | umm something about the tip revision or something | 11:50 |
redwyrex | I assume it's on the svn side | 11:50 |
redwyrex | anyway, thanks for your help | 11:55 |
lamont | jelmer: still around? | 12:21 |
jelmer | lamont: yes, hi\ | 12:21 |
lamont | see chinstrap:~lamont/bzr-logs/* | 12:22 |
lamont | the .1 on the version is me messing up the upload and repackaging the source with the right dsc format version :( | 12:23 |
jelmer | Hmm, I thought ~9 already had the source format changed back to "1.0" ? | 12:25 |
jelmer | lamont: The problem does appear to be that the patches aren't applied | 12:29 |
jelmer | lamont: is this ~9 from the cat-proposed archive, or yours? | 12:30 |
lamont | bah | 12:31 |
lamont | jelmer: it had source/format=1, but the .dsc was still new or such | 12:32 |
lamont | Architecture: any all | 12:32 |
lamont | so I rebuilt it. | 12:32 |
lamont | let me see how a .2 fares | 12:33 |
=== tchan1 is now known as tchan | ||
jam | mgz: I poked at https://answers.launchpad.net/bzr/+question/175127 | 13:32 |
jam | if you could follow up, that would be great, as I spent a bit too much time on it already | 13:32 |
mgz | jam: I've just been reading that as I ate my lunch and was wondering how to send you a teddy bear | 13:33 |
mgz | will follow up as needed. | 13:34 |
jam | mgz: so we could do something like fix up leo-editor, which may require a losa to run a script we write (branch into a clean repo, copy that back over the original). | 13:36 |
jam | I've seen complaints about leo-editor in bug reports before | 13:37 |
jam | I'm pretty sure he didn't intend to include a file with 800MB of '\' characters | 13:37 |
mgz | yeah, and the good news is bzr does now have a check for that kind of accident | 13:40 |
lamont | jelmer: I suspect that I know what happened here, verifying that | 13:40 |
mgz | getting rid of that revision from the leo-editor repo sounds like a good plan | 13:41 |
lamont | jelmer: how much longer will you be aorund? | 13:41 |
jam | mgz: sort of. If you add a file in revision 1, and then in rev2 you bloat it to 800MB, bzr won't warn you | 13:41 |
jam | I don't think | 13:41 |
jam | (the check was put in 'add') | 13:41 |
jam | which is actually what happened here. | 13:42 |
jam | the file has a parent revision. | 13:42 |
jam | which is a wee bit smaller :) | 13:42 |
mgz | jam: I noticed when subscribing to things last night I'm down as the approver for foundatons-p-bzr-workflows | 13:50 |
jam | mgz: I think that was mostly that I wanted you to be present at the meeting, and by making you an 'Important Person' it will try to schedule around that. | 13:51 |
mgz | I'm now an essential subscriber, so I think the schedual should now know that I need to be there? | 13:52 |
jam | I think it is actually supposed to be in the linaro-training track, which was added after I was setting up the blueprint | 13:52 |
jam | I'll see if I can do something about it | 13:52 |
mgz | if there's anything else you need or would like me to do for UDS, poke | 13:53 |
jelmer | lamont: I'll be around for another 3 hours | 13:53 |
jam | mgz: it looks like the actually session is going to be: https://blueprints.launchpad.net/linaro/+spec/linaro-training-bzr | 13:53 |
jam | Andy set up a different session, so we'll just switch to that one | 13:54 |
jam | wow, I wanted to try and mark it superseded by the other session. | 13:55 |
jam | But if you try to go there | 13:55 |
jam | it requires that you select the superseding blueprint from a drop-down list | 13:55 |
jam | of *all* ubuntu sessions | 13:55 |
jam | it is about 1900 pixels wide | 13:55 |
jam | and probably 10,000 entries in it? | 13:56 |
jam | on the plus side, I can view source to actually get a reasonable view of it, and linaro-training-bzr isn't in there ... | 13:57 |
mgz | yep, that was pretty funny | 14:01 |
mgz | did you delete it then, or did my hack go horribly wrong? | 14:01 |
jam | mgz: I retargetted it to linaro, and then superseded it with the above spec | 14:02 |
mgz | ah, good good. | 14:02 |
=== zyga is now known as zyga-afk | ||
=== Guest35863 is now known as elmo | ||
jelmer | jam: wasn't a name change reason for updating a file's last modified data? | 15:37 |
jelmer | nevermind, there's something else going wrong | 15:50 |
=== deryck is now known as deryck[lunch] | ||
=== zyga-afk is now known as zyga | ||
=== beuno is now known as beuno-lunch | ||
=== deryck[lunch] is now known as deryck | ||
=== beuno-lunch is now known as beuno | ||
jam | jelmer: yes, rename to another directory, and changing a filename are in the per-file graph. Note that renaming a directory isn't in the file's graph | 17:50 |
jelmer | jam: Thanks | 17:55 |
jelmer | jam: I just fixed the last failing bzr-svn test, which was related to that. | 17:56 |
* jelmer prepares a victory email for the mailing list | 17:56 | |
jam | jelmer: congrats | 18:05 |
lamont | jelmer: your test suite runs forever on some architectures. just sayin | 19:27 |
=== yofel_ is now known as yofel | ||
jelmer | lamont: what's your definition of forever ? :-) More than an hour? | 20:25 |
lamont | 8.3 hrs | 20:26 |
lamont | you know, forever | 20:26 |
jelmer | lamont: ah, worse than Launchpad's testsuite in its dark days. That is forever. | 20:30 |
lamont | it's also a bbg3 | 20:55 |
Guest3968 | exit | 21:42 |
Noldorin | hi jelmer | 22:51 |
jelmer | hi Noldorin \ | 23:00 |
lamont | jelmer: ticket updated, still waiting on some of the bzr builds to finish | 23:06 |
jelmer | lamont: thanks | 23:06 |
jelmer | lamont: That's indeed very long. These were the arm/sparc builders? | 23:07 |
lamont | and I'll be updating a wiki page somewhere with lessons learned from the packaging fun | 23:07 |
lamont | yeah | 23:07 |
lamont | arm | 23:07 |
jelmer | lamont: thanks, that'd be useful | 23:10 |
lamont | jelmer: don't delete your final versions from your ppa - I'll want to go poke at them a little in doing that update | 23:11 |
jelmer | lamont: sure, I'll leave them around | 23:12 |
Noldorin | jelmer, how's things going? | 23:14 |
jelmer | lamont: do you know when hardy is going to disappear from the builders? after 12.04? | 23:17 |
jelmer | Noldorin: alright, how are you? | 23:22 |
jelmer | managed to get the full bzr testsuite to pass against bzr-svn earlier today, which I'm quite pleased with | 23:22 |
spiv | jelmer: \o/ | 23:23 |
jelmer | g'morning spiv :) | 23:23 |
jelmer | how are things at the big G? | 23:23 |
thumper | jelmer: congratulations | 23:23 |
jelmer | thumper: thanks | 23:25 |
jelmer | I'll be really pleased when we manage to do this for git and hg, but that's some time away | 23:25 |
Noldorin | jelmer, pretty decent, just as busy as ever heh. | 23:30 |
Noldorin | jelmer, same with you? bzr 2.5 keeping you occupied? | 23:30 |
=== r0bby_ is now known as robbyoconnor |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!