| === beuno_ is now known as beuno | ||
| === Guest88485 is now known as jelmer | ||
| milleja46 | hi | 02:18 |
|---|---|---|
| milleja46 | ok...so i've created a project on launchpad and i need to know how to post my code on there using bzr...is there a guide to do it anywhere? | 02:19 |
| lifeless | milleja46: bzr push lp:~youruserid/yourprojectname/branchname | 03:41 |
| milleja46 | lifeless: will that work since it's just the initial code for the project? | 03:42 |
| milleja46 | apparently not..... i did "bzr push lp:~milleja46/m46sgoffice/trunk" and it reported "bzr: ERROR: Not a branch: "C:/Python27/projects/M46 Office Suite/"." | 03:44 |
| milleja46 | is there a reason for that? i sholdn't have gotten that error if this is the first code for the project... | 03:46 |
| milleja46 | well...i'll be back in the morning...gotta go to bed before i fall asleep at the computer... | 03:46 |
| alkisg | Um, if I did `bzr revert file`, is there any way to undo that action? | 08:19 |
| alkisg | (I typed the wrong filename there :-/) | 08:19 |
| alkisg | The man page mentions that revert backs up the file, is there a command to restore the backup, or I do it manually? | 08:21 |
| Peng | alkisg: Just do it manually. ls -ltr file* | 08:23 |
| * alkisg did it manually - thank you | 08:23 | |
| === med_out is now known as medberry | ||
| vila | poolie: I'm happy to make you a happy child ;-p http://www.happychild.org.uk/islands/O.htm | 12:22 |
| jelmer | haha | 12:23 |
| vila | jelmer: of course he missed the joke which is waiting for his laptop to be opened again ;) | 12:28 |
| jml | mgz: I'm giving up on those issues for now. Have tagged them all with 'unicode' in case it makes sense to fix them in a cluster. https://bugs.launchpad.net/testtools/+bugs?field.tag=unicode | 12:37 |
| milleja46 | ok...i created a project last night on launchpad...but my question is...how do i upload my current code i have on my computer to at least have that basis there? | 13:59 |
| maxb | You probably want to read some of the introductory Bazaar documentation | 14:01 |
| milleja46 | maxb: well i thought i would just do lp~milleja46/m46sgoffice/trunk but doesn't seem to work... | 14:03 |
| maxb | You're missing a colon | 14:03 |
| maxb | lp:...... | 14:03 |
| milleja46 | i forgot it on that when posting on here...i actually put it when i did the push command | 14:04 |
| maxb | Then you need to explain "doesn't work" | 14:04 |
| milleja46 | it reports "bzr: ERROR: Not a branch: "C:/Python27/projects/M46 Office Suite/"." | 14:05 |
| milleja46 | ^that's what i mean by doesn't work | 14:08 |
| jamdahl | Hey, is there a way I can configure bazaar to automatically add files in a directory rather than doing so manually? | 14:37 |
| jelmer | jamdahl: you can run "bzr add" (without arguments) to add all unknown files | 14:38 |
| jamdahl | Thanks jelmer, is there a set of arguments for add to add all files in subfolders but not in main directory? | 14:40 |
| jelmer | jamdahl: "bzr add" works recursively, so it should work if you specify the subfolders | 14:40 |
| jamdahl | Is there a way to do that without specifying? | 14:41 |
| jamdahl | In my particular case, I know there is going to be some junk in the main folder I don't want versioned but stuff added to folders that I always want versioned | 14:42 |
| milleja46 | can anyone answer my question? i have a new project on launchpad but i need to know how to seend my code i have so far to it...how do i do that? the command it tells me on the page doesn't work...reports it's not a branch | 14:50 |
| jelmer | jamdahl: you should be able to add the junk to .bzrignore and then run "bzr add" - it should ignore things that are in .bzrignore | 14:53 |
| jelmer | milleja46: can you be more specific, what command does it tell you to run? | 14:54 |
| milleja46 | bzr push lp:~milleja46/m46sgoffice/trunk <-but it reports that where i'm pushing from isn't a branch...i don't think it should because i need to put my latest code on there right now... | 14:55 |
| jelmer | milleja46, what's the exact error that command gives you? | 14:55 |
| milleja46 | "bzr: ERROR: Not a branch: "C:/Python27/projects/M46 Office Suite/". | 14:56 |
| jelmer | milleja46, you don't have a branch locally, so it has nothing to push | 14:56 |
| jelmer | milleja46, you should be able to create one with "bzr init" and then add your files with "bzr add" and "bzr commit" | 14:57 |
| milleja46 | i know...but i need to put the inital code on the project... | 14:57 |
| jelmer | or see http://doc.bazaar.canonical.com/latest/en/mini-tutorial/ for the tutorial | 14:57 |
| jelmer | milleja46, you have to create a branch locally before you can push that branch to Launchpad | 14:58 |
| milleja46 | jelmer: ok...now that i've run through that...how do i convert it to a branch so that i can use it with launchpad? | 15:16 |
| jelmer | milleja46, run the push command you tried earlier | 15:16 |
| milleja46 | i did that and now it reported "bzr: ERROR: Not a branch: "C:/Python27/projects/M46 Office Suite/m46sgofficesuite/.bzr/branch/": location is a repository." | 15:17 |
| jelmer | milleja46: It seems like you just created a repository, not a branch; what commands did you run | 15:19 |
| jelmer | ? | 15:19 |
| milleja46 | the ones to make it a repository but ti doesn't say ones for making my code the original code for the project | 15:19 |
| jelmer | milleja46, you have to create a branch as well | 15:20 |
| jelmer | (not just "bzr init-repo", but "bzr init" too) | 15:20 |
| milleja46 | how do i do that? i've forgotten how to do it... | 15:21 |
| jelmer | milleja46: "bzr init" to create an empty branch (see http://doc.bazaar.canonical.com/latest/en/mini-tutorial/ for background) | 15:23 |
| jam | spiv: if you're around, poolie is looking for you | 15:27 |
| spiv | jam: ok, I'll head to the lp room | 15:34 |
| dchilton | I've noticed that the size of my local repo was getting huge; tracked it down to having ~ 50 packs in '.bzr/repository/packs'. running 'bzr pack --delete-obsolete-packs' fixed the issue -- back down to reasonable size, with just one pack. but as i continue to pull/add/etc, the packs are accumulating again. | 15:35 |
| dchilton | is this normal behavior? shouldn't packs be getting auto-managed? or do i need to keep manual exec of 'bzr pack' as part of my regular maint | 15:35 |
| spiv | dchilton: they are auto-managed, and the obsolete pbacks will be gradually removed over time | 15:36 |
| dchilton | spiv the oldest of those ~50 packs was around 4 months old ... i had NO packs in /repository/obsolete-packs. | 15:37 |
| dchilton | something not configured right on my end? | 15:37 |
| dchilton | the total repository had swelled, because of those unmanaged packs, to around 35x the size of the actual managed files/dirs | 15:38 |
| magmatt | When I install bzr on my mac, it installs bzrlib in the site-packages of an old install, not my current install | 16:03 |
| magmatt | How can I tell the installer which python to use (because it's not using the one given by "which python")? | 16:04 |
| dchilton | magmatt do you need/use anything in the 'site-packages of an old install'? if not, what happens if you temporarily move that dir out of the way? | 16:05 |
| magmatt | lemme try | 16:06 |
| magmatt | dchilton: I moved it then installed from the dmg. The installer recreated the directory :) http://paste.pocoo.org/show/425906/ | 16:10 |
| magmatt | And filled site-packages with bizarre things | 16:10 |
| magmatt | *bazaar | 16:10 |
| magmatt | is there a way to install from source? | 16:13 |
| poolie | magmatt: to install bzr from source? or ptyhon? | 16:15 |
| dchilton | magmatt: fwiw, i pull the bzr repo, then 'make', 'python setup.py install'. | 16:15 |
| poolie | that should work | 16:15 |
| dchilton | magmatt: ah, are you using a Mac package installer? | 16:15 |
| magmatt | poolie: bzr | 16:15 |
| magmatt | dchilton: yes | 16:15 |
| poolie | dchilton: bzr should normally repack them | 16:16 |
| dchilton | $5 sez it's presuming a target dir. try the source install. | 16:16 |
| poolie | unless you're running a very early 2.0 version maybe | 16:16 |
| magmatt | dchilton: yes, I'm trying from source right now | 16:16 |
| magmatt | poolie: 2.6.6 | 16:16 |
| poolie | Riddell: can you tag your gpg bugs so we can link them together to see the overall state of it? | 16:16 |
| magmatt | actually, I'm trying easy_install first | 16:17 |
| Riddell | I think I did | 16:17 |
| magmatt | easy_install wins | 16:17 |
| Riddell | poolie: they all have the tag "gpg" | 16:17 |
| dchilton | poolie: that's what i figured. apparently, in my case, it isn't. i'm running '2.3.4dev' | 16:17 |
| dchilton | magmatt: er, 2.6? | 16:21 |
| magmatt | dchilton: python 2.6.6, bzr 2.4b4 | 16:21 |
| dchilton | ah | 16:21 |
| magmatt | dchilton: thanks | 16:26 |
| dchilton | worked? | 16:26 |
| dchilton | poolie: fwiw, atm, every new commit seems to create an additional pack file. | 16:30 |
| dchilton | what's being created seems small ... likely proportional to the size of the commit? | 16:31 |
| maxb | dchilton: IIRC, it'll go 1 commit per pack, then when you hit 10 commits, those will be repacked into a single one. And then repeat that pattern. | 16:34 |
| maxb | When you get to 10 * 10 commit packs, they get repacked into 1 100 commit pack | 16:34 |
| maxb | etc..... | 16:34 |
| === JasonOO is now known as JasonO | ||
| dchilton | maxb: that sounds like a reasonable approach. at least for a default. again, apparently not happening here. | 16:35 |
| === JasonO is now known as Guest30760 | ||
| maxb | dchilton: So, I just ran a quick shell for loop to commit 1001 revisions to a repository, tracking the pack count - it's as I suggested | 16:41 |
| maxb | You get up to 27 packs at r999 before you drop back to 1 at r1000 | 16:41 |
| maxb | ooh, that's pretty | 16:42 |
| maxb | The expected number of packs if bzr is left to autopack automatically is the sum of the value of all the digits in the number of revisions :-) | 16:43 |
| dchilton | maxb: unclear to me whether my case falls within those 'tortured' constraints. so can i override this? basically, i'd like NOT to have a 35GB repo for 1GB of files being tracked ... solely due to unmanaged packs. of course, i *can* add 'bzr pack' to my mgmt repertoire ... just useful to know if that's the only/best/recommended way to handle this. | 16:53 |
| maxb | I don't understand why your repository is so big | 16:55 |
| maxb | Repeated manual 'bzr pack' should never be necessary - in particular because it has to do I/O over the entire history of the repository each time. | 16:55 |
| maxb | How much of your tree is changing in every commit? | 16:56 |
| dchilton | maxb: well, it's cuz there are, well *were*, lots of really big packs ... each about the size of the files/dirs under mgmt | 16:56 |
| dchilton | maxb a few files at a time. not a whole bunch. | 16:56 |
| poolie | dchilton: oh they're accumulating in obsolete packs? | 16:57 |
| poolie | or they're in plain packs/ | 16:57 |
| poolie | hi maxb | 16:57 |
| dchilton | poolie: nope. there is *nothing* in ../obsolete-packs. ever. | 16:57 |
| dchilton | all just in ../packs | 16:57 |
| poolie | hm | 16:57 |
| poolie | that's strange | 16:57 |
| poolie | is there anything unusual about your environment? | 16:57 |
| dchilton | poolie: unusual --> probly that *I* am involved ... | 16:58 |
| dchilton | other than that, not really | 16:58 |
| maxb | I suppose if you commit a large amount of changed files in several successive commits, you might end up with a bloated repository until the next autopack kicks in | 16:59 |
| dchilton | maxb: sure. but, i don't think i've ever committed more than about 20 edits to text files at a time ... | 17:00 |
| maxb | Quite mysterious | 17:01 |
| dchilton | hm. would '.bzrignore' interpret/parse these two entries differently?: "./test/*" and "./test/" | 17:02 |
| dchilton | maxb poolie so, until if/when i find a gremlin, is there any *harm* to occassionally/regularly running 'bzr pack --delete-obsolete-packs' ? | 17:04 |
| maxb | You mean --clean-obsolete-packs? | 17:04 |
| maxb | You've seen the warning in bzr pack --help, right? | 17:05 |
| maxb | Other than that, the only harm is wasted time | 17:05 |
| dchilton | maxb: yes, --clean... yes, saw the warning. re: wasted time ... a tradeoff: less than backing up bloated repos. | 17:06 |
| dchilton | thx. | 17:06 |
| dchilton | off for moar coffee ... ta! | 17:12 |
| [1]reggie | bzr gurus -- how do I undo a push? | 17:47 |
| spiv | [1]reggie: 'bzr push --overwrite -r OLDREV' | 17:54 |
| [1]reggie | spiv, thx | 17:54 |
| mgz | man I hate doctestmatches | 18:30 |
| === medberry is now known as med_out | ||
| MarkAtwood | is there a "better way" to make a reverse patch than to do: | 20:05 |
| MarkAtwood | bzr diff -r-1..-2 >..reverse.patch | 20:05 |
| MarkAtwood | patch -p0 <../reverse.patch | 20:05 |
| MarkAtwood | bzr commit -m "reverse previous commit" | 20:05 |
| MarkAtwood | ? | 20:05 |
| === yofel_ is now known as yofel | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!