What has happened to the main gui-ufw bzr branch?

Asked by Jeff Fortin Tam

It seems as if the project's version control history has been destroyed:

$ bzr log -r -1
revno: 84
timestamp: Wed 2008-08-20 22:45:46 +0200
  Move to System/Administration menu

$ bzr pull
Using saved parent location: bzr+ssh://<email address hidden>/~gufw-developers/gui-ufw/gufw/
bzr: ERROR: Not a branch: "bzr+ssh://<email address hidden>/~gufw-developers/gui-ufw/gufw/".

$ bzr pull --remember lp:gui-ufw
Doing on-the-fly conversion from RemoteRepositoryFormat(_network_name='Bazaar repository format 2a (needs bzr 1.16 or later)\n') to RepositoryFormatKnitPack1().
This may take some time. Upgrade the repositories to the same format for better performance.
bzr: ERROR: KnitPackRepository('file:///home/jeff/dev/gui-ufw/.bzr/repository/')
is not compatible with
different rich-root support

$ bzr upgrade
starting upgrade of file:///home/jeff/dev/gui-ufw/
making backup of file:///home/jeff/dev/gui-ufw/.bzr
  to file:///home/jeff/dev/gui-ufw/backup.bzr.~1~
starting repository conversion
repository converted

$ bzr pull --remember lp:gui-ufw
bzr: ERROR: These branches have diverged. Use the missing command to see how.
Use the merge command to reconcile them.

Looking at lp:gui-ufw, there are only 14 revisions... back in 2008, there were at least 84. What happened?

Question information

English Edit question
Gufw Edit question
No assignee Edit question
Last query:
Last reply:
Revision history for this message
costales (costales) said :

Hi! I prefer a very clear information, if you click in "Code" tab you'll see only the actual branch for the actual Gufw ;) then, no confusions.
There aren't problems about the licence, because you have all debian installers with the code, it's python, then all is open :)
Best regards :)

Revision history for this message
Jeremy Bicha (jbicha) said :

I agree with the original question. You're doing it wrong to create a brand new branch for each revision. The normal way is to have a trunk which then branches out for each release; creating those branches are useful in case you need to do bugfixes for old releases.

And you can also create an experimental branch if changes are too disruptive even for trunk, but this branch should be merged in once it works better.

Keeping all of the history in your trunk branch is very useful to easily see who made what changes and when they were made. With your style, it takes a lot of work digging up old branches to try to figure it out. Also, there is a jump between branches where changes were made in between and that's very disruptive.

Finally, you've advised a few people in these Answers to check out your trunk branch. As this individual found out, whenever you change trunk like you do, bzr doesn't have any clue what's going on and it's very disruptive to anyone trying to use trunk.

Revision history for this message
costales (costales) said :

@jbicha: Good reasons! I didn't think in all of them :$ I'll not do again :)
Thanks very much!

Can you help with this problem?

Provide an answer of your own, or ask Jeff Fortin Tam for more information if necessary.

To post a message you must log in.