[00:29] <daugustine_lap> hello, i want to set up a bazaar server with public checking out but then authenticated committing... is this possible? and if so, how do you set up the users, can they be the users already on the os?
[00:31] <Peng> daugustine_lap: Usually you would use http for anonymous checkouts, then bzr+ssh for. committing.
[00:32] <daugustine_lap> alright... and that uses the current system users cause it goes through ssh?
[00:32] <Peng> Yep.
[00:32] <daugustine_lap> alright, thanks
[00:41] <alex-weej> is there something like giggle/gitk for bazaar?
[00:47] <dato> alex-weej: `bzr viz` from bzr-gtk
[00:48] <alex-weej> oo
[00:48]  * alex-weej checks it out
[01:03] <awilkins> Right, I'm off on my holidays, back in 2 weeks
[01:54] <ozzloy> i want to push to a windows 2k3 server.  what's the minimum stuff i need to install to do that?
[01:54] <ozzloy> on the win 2k3 server that is
[01:54] <ozzloy> it doesn't even have ftp installed right now
[01:55] <ozzloy> and if i can, i'd like to avoid.  is there a way to use bazaar itself to listen for connections?
[01:57] <bob2> you can use ssh/sftp/webdav(experimental), too
[01:59] <bob2> not sure if bzr:// itself has any auth yet
[01:59] <ozzloy> bob2: what if i'm ok that it doesn't have auth?
[02:00] <ozzloy> how do i make it so i can go bzr push bzr://192.168.1.100
[02:00] <bob2> then you can just run 'bzr serve' to allow read-only access
[02:00] <ozzloy> oh, so bzr:// without auth won't write
[02:01] <ozzloy> ok then.  i'll see aboutsome other method
[02:01] <bob2> no, bzr help serve
[02:01] <bob2> I just don't really want to suggest something so insecure :)
[02:02] <ozzloy> it's insecure, yes.  but i'm only doing it because my boss doesn't understand that every copy of the repo is completely functional
[02:02] <ozzloy> and so having it on 5 or so computers isn't enough backup
[02:02] <ozzloy> it has to be on the server that gets "backed up"
[02:03] <ozzloy> aha, bzr serve will probably do
[02:03] <ozzloy> thanks
[02:04] <daugustine_lap> how do you get svn+ssh to work..., if anyone could help me out or point me to the right place, i'd appreciate it bunches, i'm having the damnedest time
[02:09] <antoranz> Hi, Guys!
[02:09] <antoranz> Have you heard that bzr has problems running on 64-bit boxes?
[02:09] <bob2> no
[02:10] <bob2> are you having a problem?
[02:10] <antoranz> Today I saw the same kind of problem on two different boxes... one running SLES10 (unpathced, I think) and the other an OpenSuSE 10.2 (pathed... I think)
[02:10] <antoranz> patched, i mean
[02:10] <antoranz> I'll get the logs on monday and submit a bug then
[02:11] <antoranz> There were no problems besides those two on the two boxes.... they were both Turion Boxes.
[02:12] <bob2> I've not had any issues in 10 months running it on amd64, and I'm pretty sure the whole test suite has to pass on amd64 for every commit to trunk
[02:13] <antoranz> could it be a distribution problem then?
[02:13] <antoranz> what ditro do you use?
[02:13] <bob2> debian and ubuntu
[02:14] <antoranz> me two.. and I haven't seen the kind of problem I saw today
[02:14] <antoranz> (ubuntu, mostly, by the way)
[02:14] <antoranz> anyway.. I'll get the logs on monday and tell you how it was
[02:15] <antoranz> (post a bug report, anyway)
[02:30] <cody-somerville> bzr check shows:      1 inconsistent parents
[02:30] <cody-somerville> should I do a bzr reconcile?
[02:31] <Peng_> cody-somerville: That will fix it, but it's not like it's a big deal.
[02:32] <spiv> cody-somerville: yeah.  Although it's not a very serious problem.
[02:32] <Peng_> If you've gone to the effort to run check, you might as well reconcile.
[02:34] <cody-somerville> Peng, well, I've noticed a performance loss lately and my branch is 46mb while if I export it, the actual stuff only takes up 1.4mb
[02:35] <cody-somerville> Well, 2.4mb to be correct.
[02:37] <antoranz> but export will only export a revision
[02:37] <antoranz> that's not the repository per se
[02:38] <Peng_> cody-somerville: One inconsistent parent is not going to give you bad performance.
[02:38] <Peng_> cody-somerville: You're using packs, right?
[02:39] <cody-somerville> I just upgraded tonight from knit
[02:39] <cody-somerville> my branch only has 100 some commits but it has quite a bit of branch merging
[02:41] <spiv> After an upgrade you might have a bit of junk in .bzr/repository/obsolete_packs.  You can save some space by emptying (not deleting!) that directory.  That won't make any difference to performance though.
[02:42] <Peng_> cody-somerville: You might as well run reconcile, then. I don't think it will take long.
[02:43] <cody-somerville> spiv, that'll improve initial branch times, no?
[02:43] <pickscrape> Weird. My bash prompts is suddenly slower and shows bzr branch details if I'm in a branch directory.
[02:43] <cody-somerville> pickscrape, mine too :(
[02:44] <pickscrape> Something new in 1.6?
[02:45] <cody-somerville> wow!
[02:45] <cody-somerville> I
[02:45] <cody-somerville> After doing the reconcile, bzr branch flew! :)
[02:45] <Peng_> pickscrape: Yeah. It was an accident that it got installed.
[02:46] <Peng_> pickscrape: Delete /etc/bash_completion.d/bzrbashprompt.sh to get rid of it if you want to.
[02:46] <pickscrape> It's would actually be a pretty cool feature if it didn't cause such a drag on general bash performance
[02:47] <Peng_> Agreed.
[02:48] <pickscrape> Anyone know if 1.5 for hardy will make it back into the PPA before Monday? We're about to migrate to bzr so that's a complication I wasn't planning on having to deal with :)
[02:49] <pickscrape> I suppose they could just try specifying feisty in sources.list
[02:49] <Peng_> pickscrape: Well, using 1.6b3 shouldn't cause any problems (except with plugin compatibility.)
[02:50] <pickscrape> And constantly complaining about getting the server upgraded :)
[02:50] <Peng_> Heh, that too.
[02:52] <spiv> cody-somerville: no, it won't affect initial branch times, the obsolete_packs are basically ignored by everything.
[02:54] <cody-somerville> Peng_, spiv: Well, regardless, now that I've done the reconcile the branch took 43 seconds (and that included me entering my password) in comparison to 941.563 seconds
[02:55] <Peng_> What took 941 seconds?
[02:57] <cody-somerville> Peng_, initial branch
[02:57] <cody-somerville> from launchpad
[02:58] <Peng_> Ooh.
[02:59] <docgnome> I'm have a bzr repo on my desktop that I keep all my emacs settings in. mostly I'm using it like a glorified rsync. I want to whack that machine though. If I unbind one of my checkouts on another box, rebuild my desktop machine and do a checkout on it, can I tell my other checkouts to rebind to the new place?
[03:02] <bob2> as long as you remember to commit and update
[03:05] <docgnome> on the checkout?
[03:06] <bob2> commit on the desktop
[03:06] <bob2> and udpate on the other machine
[03:07] <docgnome> ah yeah.
[03:16] <cody-somerville> How do I revision control bzr hooks if they exist under .bzr?
[03:30] <Odd_Bloke> cody-somerville: You want the hooks to be part of the branch's history?
[03:30] <cody-somerville> Odd_Bloke, well, I want the hooks to be downloaded with the branch so that they're always run
[03:31] <Odd_Bloke> Well, off the top of my head, I'm not sure of a good way to do that.
[03:31] <Odd_Bloke> I'd suggest posting something to the ML or asking a question on LP.
[03:32] <pickscrape> I think there are security implication with that
[03:32] <Odd_Bloke> As it's 3:30am here, I'm going to bed. :)
[03:33] <Peng_> You can set up something so "make hooks" or whatever installs them.
[03:33] <Peng_> And tell people to run it.
[03:33] <Odd_Bloke> That seems reasonable.
[03:33] <Odd_Bloke> *GONE*
[03:34] <Peng_> Odd_Bloke: Good night.
[03:39] <docgnome> /part/part
[03:39] <docgnome> ...
[03:39] <docgnome> fail
[03:45] <Peng_> I love when people fail to exit. It gives you a chance to get a last word in.
[05:53] <alfonsodg> Hello
[05:54] <alfonsodg> i have a problem....
[05:55] <alfonsodg> when i try to push a content in a new branch with: bzr push bzr+ssh://alfonsodg-pe@bazaar.launchpad.net/~alfonsodg-pe/edukt/main
[05:55] <alfonsodg> i receive a message: bzr: ERROR: Transport operation not possible: readonly transport
[05:55] <alfonsodg> any ideas?
[05:59] <Yurim> Hi, I just shot myself in the foot with bzr. Is there anybode awake willing to help me reanimate my branch?  After some hours of work, i moved files from a subdirectory into the parent directory, removed the subdir and got now "ERROR: exceptions.AssertionError: Could not find target parent in wt: w3mimg/fb"
[06:01] <Yurim> now i can't branch from this dead branch and "bzr st" raises an exception. how do i get the last revision?
[06:06]  * Yurim sighs.
[06:13] <Peng_> Yurim: This isn't great, but if you rename .bzr/checkout/, bzr should forget that you have a working tree.
[06:13] <Peng_> Yurim: (Don't delete it though.)
[06:13] <Peng_> Yurim: Are you using bzr 1.5 or 1.6b3?
[06:14] <Yurim> @peng: ah, somebody listening. bazaar 1.3.1 from ubuntu
[06:14] <Yurim> i can reproduce the bug
[06:14] <Yurim> mkdir -p test_repo/subdir1; touch test_repo/subdir1/file1; cd test_repo; bzr init .; bzr add .; bzr commit -m "initial commit. 1 subdir, 1 file"; rm subdir1/file1; bzr rm subdir1; bzr st
[06:16] <Peng_> Yurim: I can confirm that with bzr.dev. You should file a bug, if there isn't one already.
[06:16] <Yurim> ok, i'll do that immediately
[06:18] <Peng_> I think I remember hearing about something like that a few months ago.
[06:19] <Yurim> @Peng_ Thank you very much. Removing .bzr/checkout was the thing i needed.
[06:20] <alfonsodg> sorry .... any ideas about my problem?
[06:20] <Peng_> "bzr branch" stopped working too? I wonder why it cares about the working tree?
[06:20] <Peng_> alfonsodg: Err.
[06:22] <Peng_> alfonsodg: Sorry, I hadn't noticed your question. If you're sure you're using bzr+ssh, I dunno.
[06:22] <Peng_> alfonsodg: Are you using a modern version of bzr?
[06:22] <alfonsodg> bzr 1.3.1
[06:23] <alfonsodg> Peng_: included with ubuntu hardy
[06:23] <alfonsodg> Peng_: i must to upgrade, right?
[06:23] <Yurim> right, "bzr branch" stopped working too. that was the first thing i tried and after i saw the exception i began to panik
[06:24] <Peng_> alfonsodg: It would be a good idea to upgrade, but I don't know if it will help here.
[06:24] <bob2> have you tarred up the whole thing now so fddling won't break it further?
[06:25] <Peng_> alfonsodg: (You can use the apt repo -- https://launchpad.net/~bzr/+archive )
[06:26] <Peng_> Does the PPA seriously not have a version of bzr for Hardy right now? Oops.
[06:29] <alfonsodg> Peng_: updating.....
[06:30] <alfonsodg> Peng_: sure... i will install from sources.....
[06:46] <Yurim> @bob2 sorry, i didn't see your question. no i haven't but after copying the whole directory and removing .bzr/checkout i could branch from this new directory and copy my changes from the old one. everything's back to normal again
[06:50] <alfonsodg> Peng_: nothing... still the problem.......
[06:51] <Peng_> alfonsodg: Can you push anywhere else? Are you sure you aren't accidentally using http? What's the exact command you're running?
[06:52] <alfonsodg> bzr push bzr+ssh://alfonsodg@bazaar.launchpad.net/~alfonsodg/edukt/main/
[06:52] <alfonsodg> bzr: ERROR: Transport operation not possible: readonly transport
[06:53] <alfonsodg> Peng_: with this works: bzr push sftp://alfonsodg@localhost/~/example_dok
[06:54] <alfonsodg>  bzr push sftp://alfonsodg@bazaar.launchpad.net/~alfonsodg/edukt/main/
[06:54] <alfonsodg> bzr: ERROR: Permission denied: "/~alfonsodg/edukt/main": [Errno 13] mkdir failed
[06:54] <Peng_> alfonsodg: Can you push to any other branches on Launchpad?
[06:54] <Peng_> Ah-ha!
[06:55] <Peng_> alfonsodg: That's a mirrored branch. Push to your server, not Launchpad.
[06:55] <Peng_> alfonsodg: https://code.launchpad.net/~alfonsodg/edukt/main says it's a mirror of http://cosperu.com/EduKT , which doesn't exist. If you didn't intend to make it mirrored, it's easy to change.
[07:02] <alfonsodg> Peng_: thanks.... in fact, the problem was in the launchpad side.....
[07:39] <lifeless> moin
[07:39] <Peng_> Good morning.
[07:41] <Jc2k> moin
[07:46]  * Peng_ wonders why a pull of bzr.dev has been running for a couple minutes.
[07:56] <Peng_> Still going . . .
[07:56] <Peng_> If I'm DoSing bazaar-vcs.org, well, it's your fault. :P
[08:25] <Peng> Oh, good, it exited with "No revisions to pull" after 1030.762 seconds.
[08:25] <Peng> Man, Mercurial's really got you guys beat. :P
[08:26] <RAOF> That seems to be unusually poor performance for a noop.
[08:26] <Peng> Yes, yes it does.
[08:27] <RAOF> Oh, I'm pulling from launchpad, which may make a difference, but mine is 17s
[08:27] <Peng> I know it's weird. It's usually only a few seconds.
[08:27] <bob2> is your local branch the same format as /bzr/bzr.dev?
[08:27] <lifeless> Peng: wtf
[08:28] <lifeless> Peng: can you grab your ~/.bzr.log for the session and file a bug?
[08:28] <fullermd> Pshaw.  hg isn't THAT much faster.  Why, it took me almost 10 seconds to pull 3.5 months worth of mutt changes.
[08:28] <Peng_> Haha, "wtf" is a good reaction.
[08:29] <Peng_> I just tried again. It took 3.081 seconds.
[08:29] <Peng_> lifeless: I was kinda pulling 4 things at once, so my .bzr.log is messy.
[08:30] <fullermd> I did have a bzr.dev pull go off into the weeds once a month or two back.  It spent several minutes using no CPU and doing no network transfer.  Killed it, restarted, and it ran normally.
[08:30] <fullermd> I marked it up to "bizarre network crap".
[08:30] <Peng_> Heck, I can't even tell which is which. .bzr.log should include the CWD.
[08:31] <Peng_> fullermd: Yeah. It was probably something like a connection died and it took forever to time out.
[08:53] <bob2> could pull trigger a local repack even if nothing is pulled?
[08:55] <fullermd> I don't think so...
[08:55] <Peng_> I doubt it.
[08:57] <Peng_> If it would, it would've repacked last time it added revisions.
[08:57] <Peng_> Also, it didn't trigger one.
[09:13] <lifeless> uws: rebase bug fixed in a branch for you
[09:32] <lifeless> jelmer: bug is fixed
[09:48] <Peng_> Ooh, what bug?
[10:04] <jelmer> lifeless: which bug ? :-)
[10:17] <lifeless> jelmer: rebase slow
[10:18] <jelmer> EMISSINGBUNDLE
[10:18] <Peng_> Nice.
[10:18] <jelmer> :-P
[10:18] <lifeless> jelmer: EATTACHEDTOBUG
[10:18] <lifeless> :P
[10:19] <jelmer> at least lp didn't mail me about anything being attached to that bug...
[10:19] <lifeless> https://bugs.edge.launchpad.net/bzr-rebase/+bug/249823
[10:20] <jelmer> ah, it's a branch
[10:20] <jelmer> malone doesn't appear to email if a  branch is attached
[10:20]  * jelmer files bug
[10:28] <lifeless> -> conf
[11:30] <lifeless> jelmer: where is commit-notify?!
[12:52] <LarstiQ> lifeless: bzr-gtk?
[13:08] <kiorky> jelmer: any chance, you around?
[14:29] <ChristopheT> Hi.  One can use "bzr ci --fixes x:id".  And then what?  It is visible with "bzr cat-revision" but can it be searched upon (to answer the question "in which revision was bug x fixed?")?
[15:04] <bob2> ChristopheT: not sure if it is exposed by the bzr ui, but launchpad can use it (and maybe trac etc)
[15:22] <Peng_> Launchpad uses it. Trac certainly *could*, but who knows if it does.
[15:28] <kiorky> jelmer: it seems the progress function is bugged somehow
[15:29] <kiorky> jelmer: i putted a "return;" at first statement in ra.c:py_progress_function as the first statement and then i was able to check out something
[15:31] <uws> lifeless: rock on
[16:55] <alfonsodg> Peng_: ping
[16:59] <Peng_> alfonsodg: Pong.
[17:01] <Peng_> peng ping pong
[17:01] <alfonsodg> Peng_: in reference to https://bugs.launchpad.net/bzr/+bug/250022.... what's the procedure for fix a bug?... i found the problem but is my first bug with bzr /launchpad
[17:03] <Peng_> alfonsodg: Branch bzr.dev, start hacking?
[17:03] <Peng_> But that might be a big one for someone new...
[17:04] <alfonsodg> Peng_: nope...... the code is really easy.... great work... by the way... joining to bzr.dev
[17:05] <Peng_> :)
[17:05] <Peng_> You shouldn't direct that at me; I'm hardly a developer.
[17:05] <Peng_> I fix the occasional typo in the documentation but that's it.
[17:06] <alfonsodg> Peng_: ok.... but at least...... need some guides...
[17:07] <Peng_> Well, there's http://bazaar-vcs.org/Documentation and the ./doc directory in the source tree.
[17:07] <alfonsodg> Peng_: looking.... right... thanks
[17:08] <alfonsodg> Peng_: i think that the bug was for bzr-gtk which doesn't have enough information.....
[17:08] <alfonsodg> Peng_: my mistake
[19:23] <colbrac> In bzrlib: I have a workingtree object and want to merge from a bundle. For a branch you use wt.merge_from_branch(branchobject). Where is the merge_from_bundle? :)
[19:38] <beuno> Verterok, mornin'.   If you don't have anything fun to do today, you may want to try upgrading knits -> packs on xmloutput: https://code.launchpad.net/~guillo.gonzo/bzr-xmloutput/trunk
[19:39] <Verterok> beuno: mornin'
[19:39] <Verterok> beuno: ups, I already upgraded it, but only xmlrpc branch :P
[19:40]  * Verterok upgrading trunk
[19:40] <beuno> Verterok, :)
[19:42]  * beuno is on a crusade to upgrade knits -> packs everywhere
[19:44] <Verterok> beuno: bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is already at the most recent format.
[19:59] <beuno> Verterok, are you upgrading using sftp?
[19:59] <beuno> (you can only upgrade through sftp)
[19:59] <Verterok> beuno: bzr upgrade --pack-0.92 lp:bzr-xmloutput/0.4
[20:00] <beuno> Verterok, bzr upgrade sftp://guillo.gonzo@bazaar.launchpad.net/~guillo.gonzo/bzr-xmloutput/trunk
[20:00] <Verterok> ok, thanks
[20:01] <beuno> we should really warn people when trying to upgrade via bzr+ssh...
[20:01] <Verterok> indeed :)
[20:13] <Verterok> beuno: done, the upgrade just finished. thanks for the tip.
[20:13] <beuno> Verterok, cool, one down, 12 to go
[20:13] <Verterok> :D
[20:14] <Verterok> good luck
[20:40] <bialix> luks: ping
[21:22] <pygi> I see you're pushing KDE to bzr :)
[22:55] <lifeless> hola
[23:05] <Jc2k> lo
[23:17] <Mecha25> Anybody here have time to help with debugging a BZR upload?  my client says it's uploaded properly, and launchpad says it has the structure, but that the directories are empty
[23:17] <Mecha25> I tried reuploading, but it said all files were up to date, even though they're not there
[23:18] <Mecha25>  anybody out there?
[23:20] <Mecha25> 115 people in the room and everybody's afk
[23:20] <Mecha25> jeez
[23:20] <cody-somerville> I
[23:20] <cody-somerville> I'm not afk.
[23:21] <Mecha25> do you have time to help me debug an upload?  I've spent 2 weeks working on a plug-in for Gnome-do, and it'll be for nothing if I can't upload it
[23:22] <lifeless> Mecha25: sure
[23:23] <lifeless> Mecha25: run 'bzr info URL -v" where URL is the place you uploaded to
[23:24] <Mecha25> URL including the LP: at the front?
[23:24] <lifeless> yes
[23:25] <Mecha25> standalone branch, format unnamed
[23:25] <Mecha25> and gives me a location
[23:25] <Mecha25> I uploaded the code before, it says it worked, but launchpad lists the branch as empty
[23:25] <lifeless> Mecha25: whats the branch ?
[23:26] <Mecha25> there's 2, I'll give you the simple one, I'll do the complicated one later
[23:26] <Mecha25> lp:~mechaphoenix25/do-plugins/Grep-Plugin
[23:28] <lifeless> Mecha25: have you done 'bzr commit' ?
[23:28] <Mecha25> no
[23:29] <Mecha25> bzr commit ﻿lp:~mechaphoenix25/do-plugins/Grep-Plugin ?
[23:29] <lifeless> Mecha25: if you haven't committed there is nothing to upload :)
[23:29] <lifeless> Mecha25: three key commands:
[23:29] <lifeless> Mecha25: bzr st
[23:29] <lifeless> bzr diff
[23:29] <lifeless> bzr commit
[23:29] <Mecha25> ok
[23:29] <lifeless> st shows you what will be added/deleted/renamed/altered etc
[23:29] <lifeless> diff shows you the content changes of each file
[23:30] <Mecha25> I've never used a version control system before, I know how to use diff though.  Thanks, it's been really confusing so far
[23:30] <Mecha25> so I need to   ﻿bzr commit ﻿lp:~mechaphoenix25/do-plugins/Grep-Plugin ?
[23:30] <Mecha25> from the directory containing the code?
[23:31] <lifeless> just 'bzr commit'
[23:31] <lifeless> after you use 'bzr st' and 'bzr diff' to be sure its going to commit what you want committed
[23:31] <lifeless> after teh commit, you can do 'bzr push'
[23:31] <Mecha25> ok... did the commit, and it threw me into vim
[23:31] <lifeless> right
[23:31] <Mecha25> exit it?
[23:32] <lifeless> write a message describing your commit
[23:32] <Mecha25> alright, then bzr st
[23:32] <Mecha25> and bzr push lp:... etc
[23:32] <Mecha25> ?
[23:32] <lifeless> yes
[23:33] <Mecha25> alright, one sec
[23:34] <Mecha25> it says it pushed the revision
[23:34] <Mecha25> ok, now what does a commit actually mean?
[23:34] <lifeless> a commit records a directory structure and the content fo the files within it
[23:34] <lifeless> a bit like a tar file
[23:34] <Mecha25> ok, then what does bzr add do?
[23:34] <Mecha25> I had to do that first I think
[23:35] <lifeless> bzr add selects files to have them be recorded
[23:35] <lifeless> files that have not been added are 'unknown' to thbzr
[23:35] <lifeless> *bzr8
[23:35] <Mecha25> ok
[23:35] <Mecha25> so I create the branch, add the files, commit the tree, then push it?
[23:35] <lifeless> yes
[23:35] <lifeless> and then you can make further changes
[23:35] <Mecha25> um... I did the push, it's still showing up as empty
[23:35] <lifeless> commit the tree again and push again
[23:36] <lifeless> Mecha25: run bzr log URL
[23:36] <lifeless> Mecha25: where URL is the lp url
[23:36] <lifeless> and look http://bazaar.launchpad.net/~mechaphoenix25/do-plugins/Grep-Plugin/
[23:36] <Mecha25> says it uploaded, has my message
[23:36] <lifeless> its all operating as normal
[23:37] <Mecha25> um.... it still says empty on my end
[23:37] <lifeless> Mecha25: what do you mean
[23:37] <lifeless> uws: please let me know if the performance issue in rebase is better
[23:37] <Mecha25> refreshing the page says it's still empty, but the link you sent me worked
[23:38] <Mecha25> weird
[23:38] <Mecha25> your link is what I'm viewing, and it says it's empty when I view it normally, and working when I view it from your link
[23:38] <Mecha25> odd
[23:38] <lifeless> what do yo umean 'view it normal'
[23:39] <Mecha25> no, wait, you're on bazaar.launchpad, I'm on code.launchpad
[23:39] <Mecha25> I mean go in from my launchpad profile
[23:39] <lifeless> code.launchpad.net takes a few minutes to update its history listing normally
[23:39] <Mecha25> d'oh
[23:39] <Mecha25> alright then, I can wait
[23:39] <lifeless> there is a issue right now I think, something backlogged
[23:39] <lifeless> but it has worked
[23:40] <Mecha25> wahoo!  I'll upload the other one, and chuck it on the mailing list
[23:40] <Mecha25> thanks a ton, this open source development thing is finally paying off
[23:40] <Mecha25> peace