[opensuse] How to mirror rpms with rsync from OSB?
Listmates, When I have a number of machines to update, I usually just create a temporary directory and download the needed rpms and then install from there. I generally use wget, but then I have to delete a bunch of stuff I didn't need link index.html, the ymp files, etc. I was going to try a simple rsync of the rpms, but I can't figure out how to form the command line. I was trying to download the compiz i586 rpms with the following (and several variations). I'm normally very good with rsync, what's the trick here? rsync -avn download.opensuse.org:/repositories/X11\:/XGL/openSUSE_10.3/i586 . Is it just not possible? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Den 08.02.2009 klokka 10:12, David C. Rankin skrev:
rsync -avn download.opensuse.org:/repositories/X11\:/XGL/openSUSE_10.3/i586 .
rsync -avz --stats --progress --delete download.opensuse.org:/repositories/X11\:/XGL/openSUSE_10.3/i586/ /local/directory/ If you want to exclude some architectures you simply don't need, add "--exclude" and "--delete-excluded". -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Heinz Diehl wrote:
Den 08.02.2009 klokka 10:12, David C. Rankin skrev:
rsync -avn download.opensuse.org:/repositories/X11\:/XGL/openSUSE_10.3/i586 .
rsync -avz --stats --progress --delete download.opensuse.org:/repositories/X11\:/XGL/openSUSE_10.3/i586/ /local/directory/
If you want to exclude some architectures you simply don't need, add "--exclude" and "--delete-excluded".
Thanks Heinz, But I'm still running into problems: 03:58 alchemy:~> rsync -avnz --stats --progress --delete download.opensuse.org:/repositories/X11\:/XGL/openSUSE_10.3/i586/ . ssh: connect to host download.opensuse.org port 22: Connection refused rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: unexplained error (code 255) at io.c(635) [receiver=3.0.2] Any other thoughts? Do I need to specify port information with --port= ? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
----- Original Message ----- From: "David C. Rankin" <drankinatty@suddenlinkmail.com> To: "suse" <opensuse@opensuse.org> Sent: Sunday, February 08, 2009 5:05 AM Subject: Re: [opensuse] Re: How to mirror rpms with rsync from OSB?
Heinz Diehl wrote:
Den 08.02.2009 klokka 10:12, David C. Rankin skrev:
rsync -avn download.opensuse.org:/repositories/X11\:/XGL/openSUSE_10.3/i586 .
rsync -avz --stats --progress --delete download.opensuse.org:/repositories/X11\:/XGL/openSUSE_10.3/i586/ /local/directory/
If you want to exclude some architectures you simply don't need, add "--exclude" and "--delete-excluded".
Thanks Heinz,
But I'm still running into problems:
03:58 alchemy:~> rsync -avnz --stats --progress --delete download.opensuse.org:/repositories/X11\:/XGL/openSUSE_10.3/i586/ . ssh: connect to host download.opensuse.org port 22: Connection refused rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: unexplained error (code 255) at io.c(635) [receiver=3.0.2]
Any other thoughts? Do I need to specify port information with --port= ?
By having only one colon in the remote address (whether it's the source as in this case, or the target if you were uploading) you are telling rsync to log in to the remote machine via ssh. Do you have an ssh login account on download.opensuse.org? Two colons means an entirely different thing, not merely to use native rsync instead of ssh, but also it means the remote path is a module name followed by a path relative to that module. Think of a module as just rsync's terminology for what nfs and samba and windows call a share. Next, only certain machines even allow anonymous rsync, and download.opensuse.org is not one of them. However, it does let you in enough to find out what to do next: Also, as long as we're talking about anonymous rsync shares like http, rsync supports a url syntax thats pretty convnient. as an anternative way to say: rsync -vl host::module/path/to/file you can also say rsync rsync://host/module/path/to/file without any options it lists the contents, or rather, any contents that the site admin has allowed to be visible in listings. When the full command you tried above didn't work, a reasonable starting point is to just try to list what's available on the host at all, and go from there if there even is anything. Maybe there are no public shares, or maybe the path you think you want is really relative to some share: algol:/tmp/obs # rsync rsync://download.opensuse.org Wed Nov 12 13:56:14 CET 2008 - poeml This is stage.opensuse.org. ********************************************************* ONLY REGISTERED MIRRORS DO HAVE ACCESS TO THIS SERVER ********************************************************* But a public rsync server is also available: rsync.opensuse.org. [...] Well that was obvious enough... so lets try the suggested public host: algol:/tmp/obs # rsync rsync://rsync.opensuse.org This is rsync.opensuse.org, public rsync server of openSUSE.org, limited to 50 connections. If you run a public mirror, please get in contact so we can give you access to the stage rsync server. You'll find conditions for access and further information at http://www.opensuse.org/Mirror_Infrastructure Thanks! admin@opensuse.org opensuse-hotstuff-160gb The most requested stuff that fits into 160 gigabytes opensuse-hotstuff-80gb The most requested stuff that fits into 80 gigabytes opensuse-updates Official updates for released openSUSE distributions opensuse-full The download.opensuse.org tree starting at /pub without daily devel snapshots opensuse-full-with-factory The download.opensuse.org tree starting at /pub including daily devel snapshots opensuse-full-with-factory-dvd5 The download.opensuse.org tree starting at /pub including daily devel snapshots and large, short-lived Beta DVDs opensuse-full-with-factory-drpmsync The download.opensuse.org tree starting at /pub including daily devel snapshots, and drpmsync tree buildservice-repos The repositories from the openSUSE build service buildservice-repos-main The repositories from the openSUSE build service without the home: directories opensuse-tube Videos hosted on tube.opensuse.org nc5:/tmp/obs # AHA! look at all those module names, and look theres a likely suspect: "buildservice-repos-main The repositories from the openSUSE build service without the home:" Lets see what's in there: algol:/tmp/obs # rsync rsync://rsync.opensuse.org/buildservice-repos-main [...] drwxr-xr-x 2800 2009/01/30 13:50:59 . drwxr-xr-x 392 2009/02/03 12:09:13 Apache drwxr-xr-x 128 2008/12/17 05:49:38 Apache: drwxr-xr-x 96 2008/08/26 17:22:19 Application: [...] drwxr-xr-x 480 2008/10/06 06:32:56 X11: [...] So there is your "X11:" directory frm your original attempted path. Let's try skipping ahead and tacking on your probable path from above to this starting point here: algol:/tmp/obs # rsync rsync://rsync.opensuse.org/buildservice-repos-main/X11\:/X GL/openSUSE_10.3/i586/ [...] drwxr-xr-x 1344 2008/09/26 10:17:15 . -rw-r--r-- 445362 2008/09/23 08:04:00 compiz-0.7.6-25.2.i586.rpm -rw-r--r-- 9472 2008/09/23 06:35:41 compiz-bcop-0.7.6-1.1.i586.rpm -rw-r--r-- 57357 2008/09/23 08:04:00 compiz-devel-0.7.6-25.2.i586.rpm [...] OK that looks like what you want, so now just up-arrow and insert -avz to the command and add the " ." after to actually download it. algol:/tmp/obs # rsync -avz rsync://rsync.opensuse.org/buildservice-repos-main/X1 1\:/XGL/openSUSE_10.3/i586 . [...] i586/python-compizconfig-0.7.6-2.2.i586.rpm i586/simple-ccsm-0.7.6-5.2.i586.rpm i586/xgl-git_071026-67.1.i586.rpm i586/xwinwrap-061227-9.1.i586.rpm sent 467 bytes received 6836997 bytes 506478.81 bytes/sec total size is 6832390 speedup is 1.00 algol:/tmp/obs # And it worked, I now have a i586 directory full of rpms algol:/tmp/obs # ls -lR .: total 1 drwxr-xr-x 2 demo 1000 1288 2008-09-26 10:17 i586 ./i586: total 6721 -rw-r--r-- 1 demo 1000 445362 2008-09-23 08:04 compiz-0.7.6-25.2.i586.rpm -rw-r--r-- 1 demo 1000 9472 2008-09-23 06:35 compiz-bcop-0.7.6-1.1.i586.rpm -rw-r--r-- 1 demo 1000 535602 2008-09-23 08:21 compizconfig-settings-manager-0.7.6.2.2.i586.rpm [...] -- Brian K. White brian@aljex.com http://profile.to/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-02-08 at 06:06 -0500, Brian K. White wrote: ...
Next, only certain machines even allow anonymous rsync, and download.opensuse.org is not one of them.
Use "rsync.opensuse.org" instead ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmO3o0ACgkQtTMYHG2NR9WTqACgiwDRD68n7S4rjfSiZDLAV/q8 Qd8An1Ub87NZ7AExpzjRhkRRKbzcKJ3L =K07M -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
----- Original Message ----- From: "Carlos E. R." <robin.listas@telefonica.net> To: "OS-en" <opensuse@opensuse.org> Sent: Sunday, February 08, 2009 8:30 AM Subject: Re: [opensuse] Re: How to mirror rpms with rsync from OSB?
Next, only certain machines even allow anonymous rsync, and download.opensuse.org is not one of them.
Use "rsync.opensuse.org" instead ;-)
You reply to things you didn't even read? -- Brian K. White brian@aljex.com http://profile.to/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-02-08 at 09:03 -0500, Brian K. White wrote:
Use "rsync.opensuse.org" instead ;-)
You reply to things you didn't even read?
What did I not read? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmO6RgACgkQtTMYHG2NR9X63gCgk5lg4CHlM4Hk8gCy0h/GOEGh JFEAn27ma3yTY0aRGaz8bZGkdq0Y0ABa =+ASI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
----- Original Message ----- From: "Carlos E. R." <robin.listas@telefonica.net> To: "OS-en" <opensuse@opensuse.org> Sent: Sunday, February 08, 2009 9:15 AM Subject: Re: [opensuse] Re: How to mirror rpms with rsync from OSB?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sunday, 2009-02-08 at 09:03 -0500, Brian K. White wrote:
Use "rsync.opensuse.org" instead ;-)
You reply to things you didn't even read?
What did I not read?
That whole post was spent doing exactly that, using rsync.opensuse.org. -- Brian K. White brian@aljex.com http://profile.to/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-02-08 at 09:22 -0500, Brian K. White wrote:
Use "rsync.opensuse.org" instead ;-)
You reply to things you didn't even read?
What did I not read?
That whole post was spent doing exactly that, using rsync.opensuse.org.
Well, certainly I did not read the entire post. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmO+VcACgkQtTMYHG2NR9VxmACfRBc3g0rTH7GX0WBOWDUz28cX 0NsAoJPk2lhJx47idKxo7SXAajmtM+cM =uNhF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
----- Original Message ----- From: "Carlos E. R." <robin.listas@telefonica.net> To: "OS-en" <opensuse@opensuse.org> Sent: Sunday, February 08, 2009 10:25 AM Subject: Re: [opensuse] Re: How to mirror rpms with rsync from OSB?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sunday, 2009-02-08 at 09:22 -0500, Brian K. White wrote:
Use "rsync.opensuse.org" instead ;-)
You reply to things you didn't even read?
What did I not read?
That whole post was spent doing exactly that, using rsync.opensuse.org.
Well, certainly I did not read the entire post.
The point of it all was to show how I got the answer and how it was there for anyone else to find the same way. I didn't magically know about the other hostname, or the correct module & path on that host which holds the obs repos. I started from exactly the same starting point of knowing nothing but non-working guess at a possible url, apparently based on the http path to the repo. I did already know about the basics of rsync command syntax and ssh vs native modes from "man rsync", but everything else came just from reading the screen and doing what it suggested next. Also, my longer answer actually got to the correct and working answer, whereas "use rsync.opensuse.org" still left 2 things missing. The OP was trying to use ssh, which still wouldn't have worked, more wasted time while they try that and then mail the list again when no matter what they try it doesn't work. And the OP was trying to use the path they use to the repo via http, which doesn't work because there is a different path to the same place via rsync. I covered all that, the _first_ time, which is much faster than more mail list back & forth. Sure I could have just spat out the answer like a free answer vending machine, after figuring it out myself for no other reason since I don't even happen to need that info or that repo, and sure lazy people just want answers handed to them, and they have no interest in how the answer was arrived at because they're just going to ask someone else to give them the answer again next time, and next time,... but who cares about them? -- Brian K. White brian@aljex.com http://profile.to/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Brian K. White wrote:
----- Original Message ----- From: "David C. Rankin" <drankinatty@suddenlinkmail.com> To: "suse" <opensuse@opensuse.org> Sent: Sunday, February 08, 2009 5:05 AM Subject: Re: [opensuse] Re: How to mirror rpms with rsync from OSB?
Heinz Diehl wrote:
Den 08.02.2009 klokka 10:12, David C. Rankin skrev:
rsync -avn download.opensuse.org:/repositories/X11\:/XGL/openSUSE_10.3/i586 . rsync -avz --stats --progress --delete download.opensuse.org:/repositories/X11\:/XGL/openSUSE_10.3/i586/ /local/directory/
If you want to exclude some architectures you simply don't need, add "--exclude" and "--delete-excluded".
Thanks Heinz,
But I'm still running into problems:
03:58 alchemy:~> rsync -avnz --stats --progress --delete download.opensuse.org:/repositories/X11\:/XGL/openSUSE_10.3/i586/ . ssh: connect to host download.opensuse.org port 22: Connection refused rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: unexplained error (code 255) at io.c(635) [receiver=3.0.2]
Any other thoughts? Do I need to specify port information with --port= ?
By having only one colon in the remote address (whether it's the source as in this case, or the target if you were uploading) you are telling rsync to log in to the remote machine via ssh. Do you have an ssh login account on download.opensuse.org?
Two colons means an entirely different thing, not merely to use native rsync instead of ssh, but also it means the remote path is a module name followed by a path relative to that module. Think of a module as just rsync's terminology for what nfs and samba and windows call a share.
Next, only certain machines even allow anonymous rsync, and download.opensuse.org is not one of them.
However, it does let you in enough to find out what to do next:
Also, as long as we're talking about anonymous rsync shares like http, rsync supports a url syntax thats pretty convnient. as an anternative way to say: rsync -vl host::module/path/to/file you can also say rsync rsync://host/module/path/to/file
Brian, That was the best damn explanation of the other 1/2 of rsync I could have ever hoped for! Thank you. I was frustrated at first being quite adept at fairly sophisticated single colon ssh rsync operations. The nfs/samba share analogy and walk-through threw the switch and the lightbulb came on. I have probably read through the rsync man page 50 times, and I had noticed the double colon explanation and always digested the information as some sort of 'abstraction' in rsync. The example was the key. Thank you! Now after I re-download the rpms, maybe I can get my damn window decorations to reappear. Thanks .... and don't be surprised if you see a bulk of your wisdom appear on my rsync page when it gets done. I've dropped the message in my /srv/www/tmp/todo folder. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Feb 09, 2009 at 11:02:29PM -0600, David C. Rankin wrote:
That was the best damn explanation of the other 1/2 of rsync I could have ever hoped for! Thank you. I was frustrated at first being quite adept at fairly [...]
Brian is obviously someone who has read http://www.catb.org/~esr/faqs/smart-questions.html to the very end. Or he's a natural. Anyway, it's a picture-book example ;-) Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
On Tue February 10 2009 12:02:29 am David C. Rankin wrote:
Brian K. White wrote:
<very much valuable SNIP> via ssh. Do you have an ssh login account on download.opensuse.org?
Two colons means an entirely different thing, not merely to use native rsync instead of ssh, but also it means the remote path is a module name followed by a path relative to that module. Think of a module as just rsync's terminology for what nfs and samba and windows call a share.
Next, only certain machines even allow anonymous rsync, and download.opensuse.org is not one of them.
However, it does let you in enough to find out what to do next:
Also, as long as we're talking about anonymous rsync shares like http, rsync supports a url syntax thats pretty convnient. as an anternative way to say: rsync -vl host::module/path/to/file you can also say rsync rsync://host/module/path/to/file
Brian,
That was the best damn explanation of the other 1/2 of rsync I could have ever hoped for! Thank you. I was frustrated at first being quite adept at fairly sophisticated single colon ssh rsync operations. The nfs/samba share analogy and walk-through threw the switch and the lightbulb came on. I have probably read through the rsync man page 50 times, and I had noticed the double colon explanation and always digested the information as some sort of 'abstraction' in rsync. The example was the key. Thank you!
Now after I re-download the rpms, maybe I can get my damn window decorations to reappear. Thanks .... and don't be surprised if you see a bulk of your wisdom appear on my rsync page when it gets done. I've dropped the message in my /srv/www/tmp/todo folder.
-- David C. Rankin, J.D.,P.E.
</very much valuable SNIP> David, I was just about to write the same thing to both you and Brian. Both you and he should go into the PRACTICAL-HOW-TO writing business specializing in clear and concise PRACTICAL information as to how to do things. Current HOW-TOs all too often are written with system-design-theoretical-physics-required degrees assumed and while I taught OS & Networking Theory in College, I often am frustrated by the assumptions that I know all of the slang, buzz words and abbreviations used by the authors, who obviously know what they are talking about but lack the ability to say it in a human readable language, unlike you and Brian. David, you will need a larger, faster server for your website if you and Brian collaborate as I am suggesting <grin>. Even Randall was useful by finding Brian's hot-button regarding "."s in PATH which elicited a very useful dissertation on the subject and which made it to my personal save file (along with many dozens of yours) as a great example of logic and reasoning without stooping to pettiness and personal attack. I :CC'd it to one of my best friends who also doesn't see the need for firewalls :{ (Brian, a nice dissertation on that would be forwarded just as quickly <grin>). Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Richard wrote:
David, I was just about to write the same thing to both you and Brian. Both you and he should go into the PRACTICAL-HOW-TO writing business specializing in clear and concise PRACTICAL information as to how to do things. Current HOW-TOs all too often are written with system-design-theoretical-physics-required degrees assumed and while I taught OS & Networking Theory in College, I often am frustrated by the assumptions that I know all of the slang, buzz words and abbreviations used by the authors, who obviously know what they are talking about but lack the ability to say it in a human readable language, unlike you and Brian. David, you will need a larger, faster server for your website if you and Brian collaborate as I am suggesting <grin>.
Even Randall was useful by finding Brian's hot-button regarding "."s in PATH which elicited a very useful dissertation on the subject and which made it to my personal save file (along with many dozens of yours) as a great example of logic and reasoning without stooping to pettiness and personal attack. I :CC'd it to one of my best friends who also doesn't see the need for firewalls :{ (Brian, a nice dissertation on that would be forwarded just as quickly <grin>).
Richard
Richard, Thanks for the kind words for all. I agree about the documentation. Some man pages are actually written in a way you can understand them perfectly. Others just leave you scratching your head thinking "What the hell are they trying to say here? -- That makes no sense at all." In my experience documentation suffers from two primary problems: (1) Let's face it, writing documentation isn't the funnest thing to do, even though it is by far as important as the actual code, so often it gets short-changed on effort and QA; (2) As you say, the documentation is written on a cognitive level that zooms over the a majority of the readers heads. (mine particularly) To some extent, I think that many of the core documents (man & info pages) were written primarily for developers when linux was in its infancy. I don't think it was ever envisioned that Linux would get to the point that John Q. Public would be typing (or more often referred to) man anything. [that in itself is a great testament to how far Linux has come in the past decade] I can only imaging where I would be if the only answer I ever got to all my screwy bash questions was: "See man bash" -- all 3,846 lines of it. (I'll add 3) Format and navigation. When most of the documentation was put together in the man and info format, it was put together in a format that was more like a maze than any navigable book. I went though fits before I made friends with :help in vi, or the info pages. The kde team was brilliant with konqueror's integrated ability to display man and info pages. That provided a quantum leap forward in usability of the documentation, but it still didn't get around items 1 & 2 above. It just makes that old adage ring true: You can build a better mousetrap, but if you can't explain how to use it, the world will never beat a path to your door. Hope you got your ftp issue resolved, sorry I couldn't help there, but I have never gotten beyond a simple setup with an ftp server. Thanks again. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Brian K. White wrote: <big beneficial snip>
OK that looks like what you want, so now just up-arrow and insert -avz to the command and add the " ." after to actually download it.
algol:/tmp/obs # rsync -avz rsync://rsync.opensuse.org/buildservice-repos-main/X1 1\:/XGL/openSUSE_10.3/i586 . [...] i586/python-compizconfig-0.7.6-2.2.i586.rpm <snip>
An interesting note. There appears to be a difference in the way rsync passes information between the version on 10.3 and the later versions. On 10.3 when you try and use the rsync:// protocol with a filename after the module, the server responds with the following error no matter how you quote or escape the ':' after X11: 11:24 ripper~/linux/ati/compiz> rsync -avz rsync://rsync.opensuse.org/buildservice-repos-main/X11\:/XGL/openSUSE_10.3/i586 . rsync: getaddrinfo: rsync.opensuse.org/buildservice-repos-main/X11 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(105) [receiver=2.6.9] Now, on 10.3, you can use the rsync:// protocol to query the host/module, but no matter what you do, you can't get around the : in the path. Not with single-quotes; single-quotes with the colon escaped; double-quotes or double-quotes with the colon escaped. However, if you use the :: format on 10.3 the server does what it is supposed to do no matter how you escape or quote the colon: 11:25 ripper~/linux/ati/compiz> rsync -avz rsync.opensuse.org::buildservice-repos-main/X11\:/XGL/openSUSE_10.3/i586 . This is rsync.opensuse.org, public rsync server of openSUSE.org, limited to 50 connections. If you run a public mirror, please get in contact so we can give you access to the stage rsync server. You'll find conditions for access and further information at http://www.opensuse.org/Mirror_Infrastructure Thanks! admin@opensuse.org receiving file list ... done This gave me no end of grief last night, but I finally figured out what was going on. I still don't know 'why' it worked that way, but at least I understand 'what' was going on.... I tried and confirmed this behavior on two separate 10.3 boxes, one x86 and one x86_64. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
----- Original Message ----- From: "David C. Rankin" <drankinatty@suddenlinkmail.com> To: "Brian K. White" <brian@aljex.com>; "suse" <opensuse@opensuse.org>
An interesting note. There appears to be a difference in the way rsync passes information between the version on 10.3 and the later versions. On 10.3 when you try and use the rsync:// protocol with a filename after the module, the server responds with the following error no matter how you quote or escape the ':' after X11:
11:24 ripper~/linux/ati/compiz> rsync -avz rsync://rsync.opensuse.org/buildservice-repos-main/X11\:/XGL/openSUSE_10.3/i586 . rsync: getaddrinfo: rsync.opensuse.org/buildservice-repos-main/X11 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(105) [receiver=2.6.9]
Now, on 10.3, you can use the rsync:// protocol to query the host/module, but no matter what you do, you can't get around the : in the path. Not with
I don't know. Works for me on 10.3 and everywhere else, but I maintain and use my own rsync builds that don't have the fistfull of suse patches. http://download.opensuse.org/repositories/home:/aljex/ So it's _possible_ this really is some bug in the stock rsync build on 10.3, or possibly in 2.6.9 -- Brian K. White brian@aljex.com http://profile.to/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Feb 11, 2009 at 11:27:51AM -0600, David C. Rankin wrote:
An interesting note. There appears to be a difference in the way rsync passes information between the version on 10.3 and the later versions. On 10.3 when you try and use the rsync:// protocol with a filename after the module, the server responds with the following error no matter how you quote or escape the ':' after X11:
11:24 ripper~/linux/ati/compiz> rsync -avz rsync://rsync.opensuse.org/buildservice-repos-main/X11\:/XGL/openSUSE_10.3/i586 . rsync: getaddrinfo: rsync.opensuse.org/buildservice-repos-main/X11 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(105) [receiver=2.6.9]
This is a known limitation in some rsync version, in combination with some other rsync version. I don't remember the actual detail (when the change came and until which point rsync was affected) but you can get away with a simple rule of thumb; try rsync rsync://hostname/path/ and if it doesn't work, try rsync hostname::path/ The good thing is, that (I claim so) one of them *always* works, regardless of combination of client rsync version and server rsync version. And trying to quote anything will just make you loose hair. Btw, openSUSE servers run rsync 3.x. Another problem that you might run into when the server runs an extremely old rsync version is that module/file listing doesn't work with 3.x client: rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(632) [receiver=3.0.4] The server will log rsync: on remote machine: -de.: unknown option Syncing still works. And the --old-d in 3.x is there to work around, see the man page. Peter -- Contact: admin@opensuse.org (a.k.a. ftpadmin@suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development
Peter Poeml wrote:
On Wed, Feb 11, 2009 at 11:27:51AM -0600, David C. Rankin wrote:
An interesting note. There appears to be a difference in the way rsync passes information between the version on 10.3 and the later versions. On 10.3 when you try and use the rsync:// protocol with a filename after the module, the server responds with the following error no matter how you quote or escape the ':' after X11:
11:24 ripper~/linux/ati/compiz> rsync -avz rsync://rsync.opensuse.org/buildservice-repos-main/X11\:/XGL/openSUSE_10.3/i586 . rsync: getaddrinfo: rsync.opensuse.org/buildservice-repos-main/X11 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(105) [receiver=2.6.9]
This is a known limitation in some rsync version, in combination with some other rsync version. I don't remember the actual detail (when the change came and until which point rsync was affected) but you can get away with a simple rule of thumb; try rsync rsync://hostname/path/ and if it doesn't work, try rsync hostname::path/
The good thing is, that (I claim so) one of them *always* works, regardless of combination of client rsync version and server rsync version. And trying to quote anything will just make you loose hair.
Btw, openSUSE servers run rsync 3.x.
Another problem that you might run into when the server runs an extremely old rsync version is that module/file listing doesn't work with 3.x client: rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(632) [receiver=3.0.4] The server will log rsync: on remote machine: -de.: unknown option Syncing still works. And the --old-d in 3.x is there to work around, see the man page.
Peter
Excellent Peter, That just proves I'm not crazy -- maybe.. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Brian K. White
-
Carlos E. R.
-
David C. Rankin
-
Heinz Diehl
-
Peter Poeml
-
Richard