On Tue, Mar 04, 2008 at 06:20:21PM +0100, Paul Slootman wrote:
> The other issue in the bug report is something else, but as that happens
> when using 3.0.0 going to the 2.6.8 version running at rsync.net
It sounds like they're running something like the support/rrsync
validation script, which rem
On Mon 03 Mar 2008, Wayne Davison wrote:
> On Mon, Mar 03, 2008 at 01:50:28PM -0800, Wayne Davison wrote:
> > I'll fix the NULL and look to get a test for this added.
>
> The git repository has both the fix and the extended test.
>
> Attached is just the NULL-pointer fix.
Confirmed that it now w
On Mon, Mar 03, 2008 at 01:50:28PM -0800, Wayne Davison wrote:
> I'll fix the NULL and look to get a test for this added.
The git repository has both the fix and the extended test.
Attached is just the NULL-pointer fix.
Thanks for your help!
..wayne..
--- a/clientserver.c
+++ b/clientserver.c
@
On Mon, Mar 03, 2008 at 09:16:46PM +0100, Paul Slootman wrote:
> The short story: it looks like client_info is NULL at compat.c:90, if I
> look at the strace and ltrace output supplied in the above URL.
No, looks like the problem is a NULL config_file var. If rsync had been
called with --rsync-pa
The long story: http://bugs.debian.org/469172
The short story: it looks like client_info is NULL at compat.c:90, if I
look at the strace and ltrace output supplied in the above URL.
Perhaps someone can investigate further, I don't have much time this
evening. Tomorrow I can look again
Paul
