Re: OpenPKG Registry launched
On Tue, Nov 29, 2005, Bill Campbell wrote: On Tue, Nov 29, 2005, Ralf S. Engelschall wrote: On Mon, Nov 28, 2005, OpenPKG wrote: OpenPKG Registry finally launched! [...] The first questions pop up around the OpenPKG Registry. We will try hard to answer all of them to you. Let me just share a few personal points with you: What has happened to rsync access? My nightly mirror run succeeded in deleting everything from our mirrors here. Sorry for the delay. RSYNC access is resurrected. The difference is just that plain anonymous-RSYNC is not possible because rsync(1) doesn't support both anonymous and non-anonymous in parallel. If you have registered with [EMAIL PROTECTED] you can now RSYNC again with: $ RSYNC_PASSWORD= rsync -r -v \ rsync://[EMAIL PROTECTED]@rsync.openpkg.org/openpkg-ftp/[...] [...] Instead of the old: $ rsync://rsync.openpkg.org/openpkg-ftp/[...] [...] Please recognize that no password is required as the applied restrictions are for tracking and not for security reasons. Same applies to the FTP server: for security reasons never login with your real registered password, just use an empty one, please. You are required to just identify yourself, not to authenticate. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ The OpenPKG Projectwww.openpkg.org User Communication List openpkg-users@openpkg.org
Re: OpenPKG Registry launched
On Tue, Nov 29, 2005, David M. Fetter wrote: While I try to keep up on all the news and such here, I still miss a few things here and there. However, I think that perhaps a few things may not have been discussed like the specifics of what things and when exactly they would be going offline for anonymous access. The problem with rsync, of course, is that I was using the --delete option which means everything was wiped out. However, I anticipate such problems in my coding so I had a rather simple recover and I just stopped the rsync mirror script for now. If/When you find time to get the rsync bit back up, I would be more than happy to help you test it. [...] RSYNC is resurrected. You can just use it again: $ RSYNC_PASSWORD= rsync -r -v rsync://email@rsync.openpkg.org/openpkg-ftp/[...] Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ The OpenPKG Projectwww.openpkg.org User Communication List openpkg-users@openpkg.org
Re: OpenPKG Registry launched
Ralf S. Engelschall wrote: And please do not hesitate to give us YOUR important opinions, complains, suggestions, wishes, etc. Either state them in public on openpkg-users@openpkg.org or in private to [EMAIL PROTECTED] We will try to answer all of them. Hi Ralf! What I am missing are instructions to get hold of the openpkg-registry package since I think it is non obvious to use a package from /current if i run /release/x.y. It would be helpful to have the openpkg-registry also in the release tree from the releases, especialy since the 'openpkg build openpkg-registry' would find it there. cheeiro Steve __ The OpenPKG Projectwww.openpkg.org User Communication List openpkg-users@openpkg.org
Re: OpenPKG Registry launched
On Wed, Nov 30, 2005, Steffen Weinreich wrote: And please do not hesitate to give us YOUR important opinions, complains, suggestions, wishes, etc. Either state them in public on openpkg-users@openpkg.org or in private to [EMAIL PROTECTED] We will try to answer all of them. What I am missing are instructions to get hold of the openpkg-registry package since I think it is non obvious to use a package from /current if i run /release/x.y. It would be helpful to have the openpkg-registry also in the release tree from the releases, especialy since the 'openpkg build openpkg-registry' would find it there. Yes, of course. We just wanted to let it be tested a little bit more in depth until we place it also into at least the OpenPKG 2.5 RELEASE tree. But expect this to happen in the next days, too. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ The OpenPKG Projectwww.openpkg.org User Communication List openpkg-users@openpkg.org
Re: OpenPKG Registry launched
Ralf S. Engelschall wrote: Sorry for the delay. RSYNC access is resurrected. The difference is just that plain anonymous-RSYNC is not possible because rsync(1) doesn't support both anonymous and non-anonymous in parallel. If you have registered with [EMAIL PROTECTED] you can now RSYNC again with: $ RSYNC_PASSWORD= rsync -r -v \ rsync://[EMAIL PROTECTED]@rsync.openpkg.org/openpkg-ftp/[...] [...] Instead of the old: $ rsync://rsync.openpkg.org/openpkg-ftp/[...] [...] Please recognize that no password is required as the applied restrictions are for tracking and not for security reasons. Same applies to the FTP server: for security reasons never login with your real registered password, just use an empty one, please. You are required to just identify yourself, not to authenticate. Well there seems to be something still broke. I get: RSYNC_PASSWORD= rsync -avuz --exclude BIN/ --exclude ISO/ \ rsync://[EMAIL PROTECTED]@rsync.openpkg.org/openpkg-ftp/release/2.2/ /data/software/openpkg/release/2.2/ @ERROR: auth failed on module openpkg-ftp rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(420) cheerio Steve __ The OpenPKG Projectwww.openpkg.org User Communication List openpkg-users@openpkg.org
Re: OpenPKG Registry launched
On Wed, Nov 30, 2005, Steffen Weinreich wrote: Ralf S. Engelschall wrote: Sorry for the delay. RSYNC access is resurrected. The difference is just that plain anonymous-RSYNC is not possible because rsync(1) doesn't support both anonymous and non-anonymous in parallel. If you have registered with [EMAIL PROTECTED] you can now RSYNC again with: $ RSYNC_PASSWORD= rsync -r -v \ rsync://[EMAIL PROTECTED]@rsync.openpkg.org/openpkg-ftp/[...] [...] Instead of the old: $ rsync://rsync.openpkg.org/openpkg-ftp/[...] [...] Please recognize that no password is required as the applied restrictions are for tracking and not for security reasons. Same applies to the FTP server: for security reasons never login with your real registered password, just use an empty one, please. You are required to just identify yourself, not to authenticate. Well there seems to be something still broke. I get: RSYNC_PASSWORD= rsync -avuz --exclude BIN/ --exclude ISO/ \ rsync://[EMAIL PROTECTED]@rsync.openpkg.org/openpkg-ftp/release/2.2/ /data/software/openpkg/release/2.2/ @ERROR: auth failed on module openpkg-ftp rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(420) H... works fine for me: | $ RSYNC_PASSWORD= rsync -avuz --exclude BIN/ --exclude ISO/ \ | rsync://[EMAIL PROTECTED]@rsync.openpkg.org/openpkg-ftp/release/ \ | 2.2/ /tmp/2.2/ | receiving file list ... done | created directory /tmp/2.2 | ./ | 00INDEX.rdf | SRC/ | SRC/00INDEX.rdf.bz2 | SRC/00README | [...] Maybe you were just two fast. While the ProFTPD directly authenticates against the underlying SQL database (and this way your account is active immediately), the RSYNC still has to read the information from a plain text file. And this plain text file is updated every 15 minutes only. Perhaps you were two fast in trying RSYNC after registration? Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ The OpenPKG Projectwww.openpkg.org User Communication List openpkg-users@openpkg.org
obmtool (Was: Re: OpenPKG Registry launched)
There is a new obmtool [1] available from ZfOS [2] for use in the new OpenPKG Registry world order. New features are mirror support, choice of download tool with fallbacks and user/pass support. The latter especially understands and obeys the URL rewriting of those instances who utilize that feature after registration. Find ChangeLog and sample obmtool.conf alongside. Requires openpkg-registry-0.2.5, it won't rewrite URLs with previous versions. [1] ftp://ftp.zfos.org/comp/obmtool/ [2] http://www.zfos.org/ __ The OpenPKG Projectwww.openpkg.org User Communication List openpkg-users@openpkg.org
