Bug#315390: cannot register archive with name specified explicitly
also sprach Rob Weir [EMAIL PROTECTED] [2005.08.05.0328 +0200]: Both are listed as master, and one is 'readonly'. Nice so far! So how does baz know which one to use? Both are listed as master? That sounds wrong... Yes, it does. But that is the case: url=http://arch.madduck.net/~madduck/pub/debianbook/ master readonly url=sftp://[EMAIL PROTECTED]/srv/arch/madduck/pub/debianbook master Interesting. Welcome SVN! So what happens when I change that URL? Will I need to update/switch all checkouts rather than being able to change the location in one single location as before? No, the checkout stores the name, not the URL. Ah, ok. That cleares it up, I think. -- .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! it is only the modern that ever becomes old-fashioned. -- oscar wilde signature.asc Description: Digital signature
Bug#315390: cannot register archive with name specified explicitly
On Mon, Jul 25, 2005 at 12:15:42AM +0200, martin f krafft said Both are listed as master, and one is 'readonly'. Nice so far! So how does baz know which one to use? Both are listed as master? That sounds wrong... The aim of the move is to let you use urls instead of archive names, Mh, and archive names was one of the strongest features of arch, I thought... It's also a little annoying, since you have two keys pointing at each archive (name, url). What do they do that you can't do with the new system's combination of names and urls? Interesting. Welcome SVN! So what happens when I change that URL? Will I need to update/switch all checkouts rather than being able to change the location in one single location as before? No, the checkout stores the name, not the URL. -- Words of the day:threat Sarin nerve gas Ermes underground kilderkin Comirex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315390: cannot register archive with name specified explicitly
also sprach Rob Weir [EMAIL PROTECTED] [2005.07.23.1530 +0200]: Why are you trying to specify a name for it? Bazaar doesn't really do this anymore; instead, you have multiple locations for the one name, and bazaar figures out which to use based on context. I am not sure I follow, but it sounds cool. So let's take the classic case: I have an archive accessible via read-only WebDAV as well as sftp. Previously, I would register the first with an -anon suffix, and the second normally. This would allow me to commit to an archive from the same machine where I could also use cron to sync automatically (using password-less WebDAV). Since I cannot specify a suffix anymore and am thus bound to using the official name of the archive, I try to register both successively, but I find that they overwrite each other: cirrus:~ baz --version baz Bazaar version 1.4.1 ([EMAIL PROTECTED]/dists--bazaar--1.4[bazaar--devo.cfg] [...] cirrus:~ baz register-archive -d [EMAIL PROTECTED] [364] cirrus:~ baz register-archive http://arch.madduck.net/~madduck/pub/debianbook/ [365] Registering Archive: [EMAIL PROTECTED] cirrus:~ baz register-archive sftp://[EMAIL PROTECTED]/srv/arch/madduck/pub/debianbook Registering Archive: [EMAIL PROTECTED] cirrus:~ baz archives | grep -A2 [EMAIL PROTECTED] [367] [EMAIL PROTECTED] http://arch.madduck.net/~madduck/pub/debianbook/ [EMAIL PROTECTED] This is a real shame, because it effectively loses the extra layer of abstraction of the archive name. I really enjoyed being able to register an archive as zope-upstream-archive-anon and just use that name instead of the [EMAIL PROTECTED] crap. Why do you require the archive name I use on my work machine to be bound to the upstream name? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver! the remote desktop feature of windows xp is really nice (and *novel*!). a micro$oft consultant can *remotely* disable the personal firewall and control the system. we'll ignore the fact that this tampering with the firewall is not logged, and more importantly, that the firewall isn't restored when the clowns from redmond are done with their job. signature.asc Description: Digital signature
Bug#315390: cannot register archive with name specified explicitly
Hm, this reply is kinda out of order... On Sun, Jul 24, 2005 at 01:14:11PM +0200, martin f krafft said also sprach Rob Weir [EMAIL PROTECTED] [2005.07.23.1530 +0200]: Why are you trying to specify a name for it? Bazaar doesn't really do this anymore; instead, you have multiple locations for the one name, and bazaar figures out which to use based on context. I am not sure I follow, but it sounds cool. So let's take the classic case: I have an archive accessible via read-only WebDAV as well as sftp. Previously, I would register the first with an -anon suffix, and the second normally. This would allow me to commit to an archive from the same machine where I could also use cron to sync automatically (using password-less WebDAV). baz archive-mirror http://arch.madduck.net/~madduck/pub/debianbook/; should mirror *to* the http server, but I think I'm misunderstanding your use-case. Since I cannot specify a suffix anymore and am thus bound to using the official name of the archive, I try to register both successively, but I find that they overwrite each other: cirrus:~ baz --version baz Bazaar version 1.4.1 ([EMAIL PROTECTED]/dists--bazaar--1.4[bazaar--devo.cfg] [...] cirrus:~ baz register-archive -d [EMAIL PROTECTED] [364] cirrus:~ baz register-archive http://arch.madduck.net/~madduck/pub/debianbook/ [365] Registering Archive: [EMAIL PROTECTED] cirrus:~ baz register-archive sftp://[EMAIL PROTECTED]/srv/arch/madduck/pub/debianbook Registering Archive: [EMAIL PROTECTED] cirrus:~ baz archives | grep -A2 [EMAIL PROTECTED] [367] [EMAIL PROTECTED] http://arch.madduck.net/~madduck/pub/debianbook/ [EMAIL PROTECTED] What does baz whereis-archive --all-locations [EMAIL PROTECTED] print? baz archives now only prints one of the registrations of an archive, apparently the primary (aka master). If you look in ~/.arch-params/archives/, you can see the data that's stored directly. This is a real shame, because it effectively loses the extra layer of abstraction of the archive name. I really enjoyed being able to register an archive as zope-upstream-archive-anon and just use that name instead of the [EMAIL PROTECTED] crap. The aim of the move is to let you use urls instead of archive names, preparing for the day that names are optional (or at least way less obvious). Have you run baz upgrade yet? It will convert your existing archive to the new registration system, then you can do things like baz get http://arch.madduck.net/~madduck/pub/debianbook/; to check out from the webserver copy of it... Why do you require the archive name I use on my work machine to be bound to the upstream name? Because they're nominally the same archive, just different (possibly incomplete) copies of it. You can mostly not use archive names at all now, and just refer to things by URL. -rob -- Words of the day: strategic Skipjack Elvis industrial intelligence credit card -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315390: cannot register archive with name specified explicitly
also sprach Rob Weir [EMAIL PROTECTED] [2005.07.24.1444 +0200]: What does baz whereis-archive --all-locations [EMAIL PROTECTED] print? baz archives now only prints one of the registrations of an archive, apparently the primary (aka master). If you look in ~/.arch-params/archives/, you can see the data that's stored directly. Both are listed as master, and one is 'readonly'. Nice so far! So how does baz know which one to use? The aim of the move is to let you use urls instead of archive names, Mh, and archive names was one of the strongest features of arch, I thought... obvious). Have you run baz upgrade yet? It will convert your existing archive to the new registration system, then you can do things like baz get http://arch.madduck.net/~madduck/pub/debianbook/; to check out from the webserver copy of it... Interesting. Welcome SVN! So what happens when I change that URL? Will I need to update/switch all checkouts rather than being able to change the location in one single location as before? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver! my experience is that as soon as people are old enough to know better, they don't know anything at all. -- oscar wilde signature.asc Description: Digital signature
Bug#315390: cannot register archive with name specified explicitly
On Wed, Jun 22, 2005 at 12:24:55PM +0200, martin f krafft said Package: bazaar Version: 1.4.2 Severity: normal piper:~/.arch-params/archives baz register-archive [EMAIL PROTECTED] /srv/arch/madduck/priv/2005/debianbook usage: baz register-archive [options] [-d name] location try register-archive --help No matter what I try, if I specify the name under which to register an archive, baz reports an error. Why are you trying to specify a name for it? Bazaar doesn't really do this anymore; instead, you have multiple locations for the one name, and bazaar figures out which to use based on context. -rob -- Words of the day: Perl-RSA AUTODIN STARLAN Ruby Ridge enigma Etacs cracking -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315390: cannot register archive with name specified explicitly
Package: bazaar Version: 1.4.2 Severity: normal piper:~/.arch-params/archives baz register-archive [EMAIL PROTECTED] /srv/arch/madduck/priv/2005/debianbook usage: baz register-archive [options] [-d name] location try register-archive --help No matter what I try, if I specify the name under which to register an archive, baz reports an error. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (600, 'testing'), (98, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.11-cirrus Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages bazaar depends on: ii diff 2.8.1-11 File comparison utilities ii gawk 1:3.1.4-2 GNU awk, a pattern scanning and pr ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libgpgme11 1.0.2-1 GPGME - GnuPG Made Easy ii libneon24 0.24.7.dfsg-2 An HTTP and WebDAV client library ii libssl0.9.70.9.7e-3 SSL shared libraries ii patch 2.5.9-2 Apply a diff file to an original -- no debconf information -- .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! drink canada dry! you might not succeed, but it *is* fun trying. signature.asc Description: Digital signature
