As a side thought, since 0.48 will be maintained for a bit while 0.49 is under development. What do people think about our use of LP and how we use Fix Released rather than Fix Committed... are people game to perhaps try using Fix Committed (and target them for 0.48 when doing so) for this cycle?

De : Krzysztof Kosiński <tweenk.pl@...400...> Launchpad will automatically mark a bug "Fix Available" (rather than "Fix Committed") once somebody commits using the flag --fixes, e.g. bzr commit --fixes lp:123456 --fixes lp:123457 (if you fix those two bugs in one commit). Then, bugs can be changed automatically from "Fix Available" to "Fix Released"

Probably a stupid question, but can I do updates and commits without creating a "branch"?

I'm not against branches in principle, but with SVN I was doing compulsive updates many times a day. Now, whenever everything changes, I must commit someone's updates into my branch, and think up a commit message for that, even if I have no idea what those changes were. That's a bit much for me, frankly.

Also, if I do a commit of merge changes into my branch, then do some changes of my own, and then push it all to the trunk - will my merge commits be pushed as well? If not why?

2009/11/30 Ted Gould <ted@...11...>: > Probably want you want is to bind your branch to trunk. What that means > is that you'll commit to trunk and then update, it makes things work > very much like SVN. You always have to be connected, and you can't > commit if someone else has changed trunk. This sounds like what I need, but: > $ bzr branch lp:inkscape > $ cd inkscape > $ bzr bind lp:inkscape > <do work> > $ bzr commit I get this: $ bzr commit -m "..." Format <RepositoryFormatKnit4> for file:///home/d/ink/inkscape-bzr/inkscape/.bzr/ is deprecated - please use 'bzr upgrade' to get better performance bzr: ERROR: Cannot lock LockDir(http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/.bzr/rep...: Transport operation not possible: http does not support mkdir()

On Tue, 2009-12-01 at 08:46 -0600, Ted Gould wrote: > On Tue, 2009-12-01 at 01:18 -0400, bulia byak wrote: > > 2009/11/30 Ted Gould <ted@...11...>: > > > Probably want you want is to bind your branch to trunk. What that means > > > is that you'll commit to trunk and then update, it makes things work > > > very much like SVN. You always have to be connected, and you can't > > > commit if someone else has changed trunk. > > > > This sounds like what I need, but: > > > > > $ bzr branch lp:inkscape > > > $ cd inkscape > > > $ bzr bind lp:inkscape > > > <do work> > > > $ bzr commit > > > > I get this: > > > > $ bzr commit -m "..." > > Format <RepositoryFormatKnit4> for > > file:///home/d/ink/inkscape-bzr/inkscape/.bzr/ is deprecated - please > > use 'bzr upgrade' to get better performance > > bzr: ERROR: Cannot lock > > LockDir(http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/.bzr/rep...: > > Transport operation not possible: http does not support mkdir() > > This is because you haven't told bazaar your launchpad ID so you don't > have permission to upload :) > > You probably want to run two commands actually: > > $ bzr whoami > > Which sets your name and e-mail address, otherwise it defaults to > username@...2282... which isn't that useful. Then you should also set > your LP ID with: > > $ bzr launchpad-login > > Sorry, should have included these earlier -- I just set them long ago :) I got that far with bulia via chatting last night... he got his ssh key uploaded, logged in via command line, bzr whoami says what it should, bzr missing shows that it's liked to the server repo and it's up-to-date, but it's still throwing the same error on him when he tries to commit.

On Tue, Dec 1, 2009 at 1:39 PM, Ted Gould <ted@...11...> wrote: > My guess would be that when he did the "bzr bind" it resolved to use the > 'http' address (non-login) so if he did "bzr unbind" and then "bzr bind > lp:inkscape" again it would change the ssh+bzr: URL. Yes, that worked. Thanks everyone! Will it ask for the passphrase every time I commit, as it just did?

> Hmm, it even asks for it when I do bzr up... > Make sure you create a SSH key WITHOUT a passphrase if you want a no password experience.

I made the first commit on LP after our trunk branch was established and it went smoothly. So, everyone, feel free to go to town!

As a side thought, since 0.48 will be maintained for a bit while 0.49 is under development. What do people think about our use of LP and how we use Fix Released rather than Fix Committed... are people game to perhaps try using Fix Committed (and target them for 0.48 when doing so) for this cycle? If we properly use committed and mark where it will be available, we can then just script it to change to released when it really is (I think it will be nicer for users). Just a thought.

On Sat, Nov 28, 2009 at 11:08:08PM -0600, Ted Gould wrote: > On Sat, 2009-11-28 at 16:05 -0800, Joshua A. Andler wrote: > > I made the first commit on LP after our trunk branch was established and > > it went smoothly. So, everyone, feel free to go to town! > > Yeah! I'll see if I can clean up the GSoC branches a little once I have > upload bandwidth again. I think merging trunk into them would make > things much simpler. > > > As a side thought, since 0.48 will be maintained for a bit while 0.49 is > > under development. What do people think about our use of LP and how we > > use Fix Released rather than Fix Committed... are people game to perhaps > > try using Fix Committed (and target them for 0.48 when doing so) for > > this cycle? If we properly use committed and mark where it will be > > available, we can then just script it to change to released when it > > really is (I think it will be nicer for users). Just a thought. > > I like "Fix Committed" meaning that it landed on trunk. And "Fix > Released" meaning that it's in a tarball. I keep pushing for the script > you're talking about there being a button in LP... hopefully it will be > soon-ish. Until then, I'm pretty sure such a script already exists. Hi Josh, Did anyone end up finding a script to do this? If not, I've coded one up for you for next time (attached).