From ncoleman at internode.on.net Sun Jun 12 14:24:02 2011 From: ncoleman at internode.on.net (ncoleman at internode.on.net) Date: Sun, 12 Jun 2011 22:24:02 +0800 Subject: [sbopkg-users] Upgraded to 13.37, now rsync fails Message-ID: <74437ff231e1e6675697def1aea7494dbbce3b20@webmail.internode.on.net> I've been using Sbopkg for a year or two on Slackware 13.0 without problems. Today I decided to update Slackware to 13.37, which I did by upgrading to 13.1 and immediately upgrading from that to 13.37. ?For each, I did a clean-system, then an install-new, then an upgrade-all, as well as following the UPGRADE and CHANGES_AND_HINTS. The system works fine with the limited amount of testing I've given it so far. However, I reinstalled sbopkg, but now cannot sync to the repository. ?I get a "rsync connection unexpectedly closed, error in rsync data protocol stream" error message. I notice that 13.37 looks as though it is using a different form of ssh; is this causing problems from left-over config files I have laying around? Thanks for any help,Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik at slackbuilds.org Sun Jun 12 18:51:21 2011 From: erik at slackbuilds.org (Erik Hanson) Date: Sun, 12 Jun 2011 13:51:21 -0500 Subject: [sbopkg-users] Upgraded to 13.37, now rsync fails In-Reply-To: <74437ff231e1e6675697def1aea7494dbbce3b20@webmail.internode.on.net> References: <74437ff231e1e6675697def1aea7494dbbce3b20@webmail.internode.on.net> Message-ID: <20110612135121.2c4b1d99@shaggy.doo> On Sun, 12 Jun 2011 22:24:02 +0800 ncoleman at internode.on.net wrote: > However, I reinstalled sbopkg, but now cannot sync to the repository. > ?I get a "rsync connection unexpectedly closed, error in rsync data > protocol stream" error message. I did some upgrading on the server yesterday and forgot to kick rsync, try again it should be fine now. -- Erik Hanson (erik at slackbuilds.org) From Bradley at NorthTech.US Mon Jun 13 02:32:30 2011 From: Bradley at NorthTech.US (Bradley D. Thornton) Date: Sun, 12 Jun 2011 19:32:30 -0700 Subject: [sbopkg-users] Upgraded to 13.37, now rsync fails In-Reply-To: <20110612135121.2c4b1d99@shaggy.doo> References: <74437ff231e1e6675697def1aea7494dbbce3b20@webmail.internode.on.net> <20110612135121.2c4b1d99@shaggy.doo> Message-ID: <4DF576BE.6050702@NorthTech.US> -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 On 06/12/2011 11:51 AM, Erik Hanson wrote: > On Sun, 12 Jun 2011 22:24:02 +0800 > ncoleman at internode.on.net wrote: > >> However, I reinstalled sbopkg, but now cannot sync to the repository. >> I get a "rsync connection unexpectedly closed, error in rsync data >> protocol stream" error message. > > I did some upgrading on the server yesterday and forgot to kick rsync, > try again it should be fine now. I figured that was a temporary error ;) Had the same issue myself earlier today :) All better now I see. > > - -- Bradley D. Thornton Manager Network Services NorthTech Computer TEL: +1.760.666.2703 (US) TEL: +44.203.318.2755 (UK) http://NorthTech.US -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Find this cert at x-hkp://pool.sks-keyservers.net iQEcBAEBAwAGBQJN9Xa+AAoJEE1wgkIhr9j3ihIH/RQ+JzeYfSeGclACFafJaK9t sj+VReSrOxGL222Rd6GXpw5xsncPrUudbFiNWBgJyNCB2Htmb6CWnz60PbBUOIJU wHUs+2k6IyQh70I35CIyfXCL9CyOf8J/GAgFI0CY1K2FqRWWp5Qb8M4cg1cDnSrC rZxeH50413IHv6A2dfe+T9nVbvrvieUkasVKgjQPkpmrmXu1AaQQ3dO692NEheLF hZ7XE4O9wrJPNEdNrwqbjLDkD0F3J+cXkWnvU/F0OWD7D3fZ6Hv5lSMrA6YHq+v8 TEwlrfvUvfFHz76pcgsMS6V7FD2IIm5vL0Pjj+lMJmdPqa1PqGhweexw0sYOz6E= =R7on -----END PGP SIGNATURE----- From ncoleman at internode.on.net Mon Jun 13 03:29:32 2011 From: ncoleman at internode.on.net (ncoleman at internode.on.net) Date: Mon, 13 Jun 2011 11:29:32 +0800 Subject: [sbopkg-users] sbopkg-users@sbopkg.org Message-ID: > However, I reinstalled sbopkg, but now cannot sync to the repository. > I get a "rsync connection unexpectedly closed, error in rsync data > protocol stream" error message. Never mind, all is well today.? It appears I was unlucky enough to coincidentally? encounter a slackbuild.org problem at the same time that I did the Slackware upgrades. -------------- next part -------------- An HTML attachment was scrubbed... URL: