User1: were we supposed to stop using bundle-buggy already?
User1: nevermind, I need to sleep now. will ask again another time..
User2: LUSERS
User2: been a long time since I last used irc..  anyone here that might be able to answer a bazaar question?
User3: ...
User2: I am trying to set up repository with multiple projects and traditional trunk, branches, tags, etc..  Documewntation has left me guessing twixt no-trees and conmtainers
User4: hello igc?
User5: Is it possible to change an author name on old bzr revisions?
User5: Like say one of my team members got married, and she wants her married name on her old bzr revisions.
User5: How would I go about doing that?
User6: Was she married when she made those commits?
User5: Is that a no?
User6: It's not.
User6: There are ways, but if anyone has done anything based on those revs (incl. merges etc) then it'll be a total and complete arse
User6: And basically involves replaying history
User6: IIRC
User5: They haven't.
User5: It's just commits in trunk
User6: And noone else has committed after her commits which need changing?
User5: Uhhhhhhhhh
User5: She committed r77
User5: We're pushing 700 >_<
User6: Then there's stuff "based" on the commits
User6: Social problem.
User6: She needs to understand that the past is the past.
User5: Well uhhh
User6: Same as I cope with the fact that some of the early commits in one project I never thought I'd publish have change comments like "feh, moosed."
User5: She doesn't like her old last name for reasons I can't disclose on channel ._.
User5: There's no way to change it?
User6: Not without replaying history entirely IIRC
User6: and that'll break any in-flight branches you might have, or any of your users might have
User5: So I can just set my clock back to 2006 and redo it all? >_>
User5: If we have users that would be news to me
User6: Is she wanting you to fix all the backups to not contain her old name too?
User5: Backups?
User5: Those get erased after they're old
User5: Because bzr is incremental and includes all of history
User6: It truly sounds like she should just stop worrying, names are hardly a critical thing.
User5: Maybe there's two backups?
User6: User5 Now, if only it were possible to *guarantee* that nothing else will corrupt historical data
User7: Hello, can I use bzr to maintain a package that I've merge from Ubuntu ?
User8: Yes?
User7: it's gnome-games,
User7: I did bzr branch lp:~ubuntu-desktop/gnome-games/ubuntu
User7: then changed in the packaging
User7: so, if I do bzr push <some other repository>
User7: how can I maintain the diff for following versions ?
User7: just do bzr pull lp:~ubuntu-desktop/gnome-games/ubuntu for every new version or what ?
User8: User7 If you've committed new revisions, you'd have to use "bzr merge", but sure.
User8: User7 I don't know the best practices for packaging branches, though,
User9: How can I run the bazaar unit test suite?
User10: bzr selftest
User10: (and then go make lunch or something :))
User9: User10 How long does a test suite run normally take? I see that bzr has more than 19000 tests.
User10: I don't remember
User10: I used to be more than 30 minutes, but that was over a year ago
User9: is there a possibility to run only some tests? bzr selftest <filename> or something like that?
User10: bzr selftest test_name_pattern
User10: there is also an option to run only a specific module
User10: see bzr help selftest
User9: User10 Thanks :-) (running the self-test after every generation of a new RPM packages seems to be a good way to ensure everything is still working)
User10: not sure if the maintainers of the build machines will be happy about it :)
User9: User10 Probably I have to ask - given the current rate the full run will take ~ 1 1/2 hours...
User11: hello
User11: what is the intended purpose of bzr nick?
User12: hi
User9: What is the expected key id for the signature of the bzr release tarballs? They seem to be signed by Robert Tanner but this is not mentioned in the installation FAQ..
User13: User9 signed by the RM, which differs per release.
User9: User13 But the InstallationFAQ does not mention the release manager for 1.14/1.15
User9: so who is the release manager for 1.14/1.15?
User12: User11 it's a nick name for a particular branch, e.g. "trunk", "fix-bug-42342", "jelmer", etc
User13: User9 1.14 was Bob Tanner, 1.15 I haven't paid attention to
User13: User9 note that http://bazaar-vcs.org/InstallationFaq hasn't been updated since 0.13
 * LarstiQ doesn't know if they're mentioned somewhere else
User11: User12 I knew that. I just found the real use: nick are preserved no matter what arguments you use to clone a branch. A renamed dir keeps the original nick (unless set again after the clone)
User13: User11 right. It's more that in absence of an explicit nick it defaults to the basename of the branch root.
User9: User13 looks like. However I found a ml post (https://lists.ubuntu.com/archives/bazaar/2009q1/055151.html) for his nomination. And obviously he signed the 1.14 which ubuntu ships so I guess key id 0x0DDBE378 should be okay.
User11: OK, I've added another term to CategoryTerm: http://bazaar-vcs.org/Nick
User13: User9 if, given a released version, you want to know who the RM was, it's easier to check the -announce list: https://lists.ubuntu.com/archives/bazaar-announce/
User13: User9 the release announcement will be made by the RM
User13: now Bob includes his gpg fingerprint in his mails *checks to see if other RMs mention the signature*
User13: seems not
User13: User9 bzr/doc/developers/release.txt mentions to upload and link the sig from http://bazaar-vcs.org/Download , would also stating it to be explicitly mentioned in the announcement help your use case?
User9: User13 I needed to ensure that the signature is legitimate. Mentioning key id and/or checksums would definitely help (from a distro perspective you can't be paranoid enough ;-)
User13: User9 well, they're mentioned next to the release itself on http://bazaar-vcs.org/Download
User13: someone could potentially change that, but they could also send mail
User13: User9 so I'm wondering which source you're willing to trust :)
User9: On that page I only fig the sig. But how can I verify that the key used for the sig is legitimate? (e.g. someone hacked the server and put his own binaries/sigs there)
 * LarstiQ nods
User13: User9 yes, how do you?
User9: User13 A release announcement on a mailing list which is mirrored by many web sites mentioning the key should be okay.
User13: User9 ok, then lets include that in the release policy.
User9: User13 Thanks :-)
User14: does it ever make sense to update an unbound branch, or to pull a bound branch?
User15: User12 hi!
User15: User12 just saw you the script didn't reproduce the bug for you
User13: User14 yes.
User13: User14 firstly, update makes sense in a working tree context. Now consider from remote `bzr push host/unbound`. The working tree will now be out of date wrt its branch.
User13: User14 hence the push-and-update plugin
User13: User14 pulling in a bound branch will pull to it's master.
User13: User14 so they do both make sense, but for different usage then what you had in mind I think.
User14: ok, that's fine
User14: I just want to make sure I shouldn't be hiding "Update" when the branch is unbound, and vice-versa
User13: User14 afaik those are the only usages, if you can provide that in a different way you might get away with it.
User13: User14 it's a balancing act between not confusing users and giving them the power to accomplish things.
User13: User14 in bzr too, it could be debated if this behaviour is what we want.
User13: since I agree it isn't entirely obvious
User13: User14 so if you have a better workflow model, please share! :)
User14: heh
User16: hi. has anyone experience with clue-bzrserver? I cannot manage to get it running, and there is almost no documentation. Or can anyone recommend me the simplest way to have authentication on commit/push without having to expose the full path on the server? (the way bzr+ssh works).
User17: What would be the best way to search for commits by a particular user? I can't see anything in bzr log about it, and bzr search doesn't appear to either.
User12: User16 I think rocky or pygi are the people to talk to
User12: User15 hi
User15: User12 hi!
User16: User12 as usual, thanks for the help/info... I will ping them later then
User12: User15 Yeah, I couldn't reproduce it but then realized I was testing with an older version of bzr-svn
User12: so I'll give it another try in a few minutes
User15: User12 ok, let me know
 * pickscrape resorts to bzr log -n0 | less
User18: hello
User18: i screwed up my repo on launchpad, i don't know why
User18: how can i get it working again?
User18: (link coming..)
User18: https://code.launchpad.net/~c10ud/emesene/emesene-crazy
User18: it shows two faulty revisions, it should show 1341
User14: is 1341 the revision at which you branched from somewhere else?
User18: yes, i screwed up while trying to create another branch of this one
User14: so is it that you don't want those two revisions in the branch?
User18: yep
User18: i don't even know why they got 1 and two..
User14: if you click "all revisions" it shows them as 1342 and 1343
User18: oh, right, but i tried reverting and didn't work...i'll try again
User18: $   bzr branch lp:~c10ud/emesene/emesene-crazy
User18: Branched 2 revision(s).
User18: see?
User18: $ bzr revert -r1341
User18: bzr: ERROR: Requested revision: u'1341' does not exist in branch: BzrBranch6('file:///home/riky/msn/emesene-crazy/'
User14: from the branch's perspective, you want to revert to r0 (bzr log)
User14: hmm, no, that's notn right
User18: :s
User18: anyway fortunately there's another repo in there that contains exactly what i need.. if it can help
User18: it's stopped exactly at rev 1341
User14: `bzr uncommit -r0` seems to do what you want
User14: or you could rebranch from the other
User18: if i uncommit, then i must push directly or commit?
User18: ok, i tried.. if i commit i get a newer revision: 1
User18: pushing make no difference
User18: maybe found
User18: let's try
User18: i was using revid's but seems i can't get to previous numeration, when i commit i still get 1 or two...mmm
 * maxb wonders if "bzr push --overwrite" is what C10uD wants?
User18: after uncommit?
User18: anyway, yes now i killed the latest two changes
User18: but still, i get 1 as the latest commit id
User14: User18 is there some reason you're so concerned about the revision numbers?
User18: just win the machine, i guess
 * LarstiQ looks at the branch
User18: $ cat .bzr/branch/last-revision
User18: 0 robinsonemily@example.net
User18: what if i edit this?
User18: i'll do it
User14: that seems like A Bad Idea
User18: but, seems it worked (!)
User12: User18 you can change it, but you generalyl shouldn't have to
User18: let's see web interface
User18: it worked ._.
User18: so simple, wtf
User18: brb food, thanks for your support guys
User18: :)
User19: Ok, I can pretty much guess what the answer is ; but... when editing branch metadata (like `.bzr/branch/location`) in vim, they become broken (because of vim's obstinate insistence of tacking a line ending to the end of every line). Workaround ; don't use an editor that follows this convention, or use the binary mode of vim (by passing -b). But would people be open to making Bazaar tolerant of this condition?
User12: User19 I think so
User19: Ooh, goody
User12: User19 what is .bzr/branch/location used for though? I don't have that file
User19: It's used in lightweight checkouts to point to the location of the branch
User19: Mine appeared to have been orphaned so I was editing it to point to a new spot
User20: so i haven't quite pinpointed the exact way to reproduce the bug, but using bzr+ssh to a remote host that i have ControlMaster configured for in my .ssh/config file seems to break that ssh connection semi-regularly
User20: it seems bzr keeps the connection open
User20: so if i started a shell session first, it freezes
User20: if i used bzr first and try to connect via ssh, ssh never seems to connect (like the control pipe isn't responding)
User20: i'd like to let bzr use ssh connection multiplexing, but as a workaround is there a way to tell bzr what options to pass to its ssh subprocess?
User21: When running bzr checkout --lightweight, the control directory is not supposed to come along, correct?
User12: User21 it is supposed to come along, but contain almost no data
User21: Ah
User12: User21 for no control directory at all, use "bzr export"
User21: Excellent; it's for pulling onto a live web server, so that would be best
User12: User21 if you need to keep a checkout without control directory on a web server up to date, use bzr upload
User21: What is the difference between that and export?
User12: User21 export doesn't work incrementally
User21: For small projects, would there be any noticeable advantage?
User12: I think export will complain if you use it incrementally
User21: OK.
User22: User12 is there some way to just disable the whole "discovering tags" step in bzr-svn?
User22: it's always by far the longest part of push or pull to the repo, and I don't really care that much if bzr-svn knows about the svn tags dir.
User20: hm, the wiki seems to advocate ssh multiplexing yet it seems awfully buggy to me: http://bazaar-vcs.org/Bzr_and_SSH
User12: User22 it should be very quick in newer versions
User12: User20 I haven't ahd any trouble with it
User20: User12 really?  damn, wonder whats going on for me.  ubuntu 9.04 locally and debian lenny remotely fwiw
User20: hm, think bzr-avahi or dbus could be to blame?  i'll try disabling them
User23: Does Bazaar have anything similar to externals in Subversion?
User12: User23 not yet, but work is underway
User20: how do i display the current rev # like "hg id"?
User20: ah revno
User19: Offtopic : does `top` have a problem reporting process memory allocation beyond 2GB (on a 64-bit kernel) ?
User24: Is there any way to take my uncommitted changes and apply them to another branch?
User24: Since the branch I have the changes in is bound...
User25: User24 you can use bzr merge --uncommitted
User24: User25 Perfect.
User26: how do i make a patch?
User12: User26 bzr diff > file.diff
User26: thanks
bzr
Ubuntu IRC