[MERGE] Cleanups for fallback repos and stacking

John Arbash Meinel john at arbash-meinel.com
Wed May 27 10:37:25 BST 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

As part of trying to get GC to work with stacking, Andrew and I ran into
some bugs with RemoteRepository and fallback repos.


This patch is mostly about clarifying the contracts of locking and
fallback repositories.

The final statement we came up with for fallback repositories was:
1) When transitioning from unlocked => locked, a repo will lock its
   fallback repos
2) When transitioning from locked => unlocked, a repo will unlock its
   fallback repos
3) If self.is_locked(), add_fallback_repository() will lock the fallback
   repo, which will match (2) when self is finally unlocked.
Callers of add_fallback_repository() maintain their responsibility to
match every lock that they perform with a corresponding unlock.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkodCdUACgkQJdeBCYSNAAMxLwCePlITviQqEwPjJFdYCI9uEMq5
UfwAnirdXD7q0rpVy+zIykP+0vMtAOWZ
=7XHO
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 1.16-bug375496.patch
Url: https://lists.ubuntu.com/archives/bazaar/attachments/20090527/720f860a/attachment-0001.diff 


More information about the bazaar mailing list