Question #264557 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/264557
Domoradov Alex posted a new comment:
> $ tar tzvf duplicity-full.20150322T220729Z.vol16.difftar.gz
completed successfully without any errors
> do you get the value in the manifest or the value calculated in the error
> message?
I got the value calculated in the error message
> first update to latest stable 0.6.25 to make sure you have the latest
> greatest most bugfixed version.
there is some problems with librsync-1.0+. I can't build it
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.6 -c
duplicity/_librsyncmodule.c -o
build/temp.linux-x86_64-2.6/duplicity/_librsyncmodule.o
duplicity/_librsyncmodule.c: In function '_librsync_new_sigmaker':
duplicity/_librsyncmodule.c:71: error: 'RS_DEFAULT_STRONG_LEN' undeclared
(first use in this function)
duplicity/_librsyncmodule.c:71: error: (Each undeclared identifier is reported
only once
duplicity/_librsyncmodule.c:71: error: for each function it appears in.)
duplicity/_librsyncmodule.c:71: error: too few arguments to function
'rs_sig_begin'
error: command 'gcc' failed with exit status 1
error: Bad exit status from /var/tmp/rpm-tmp.V3BaQQ (%build)
RPM build errors:
line 14: buildprereq is deprecated: BuildPrereq: python-devel >= 2.4,
librsync-devel >= 0.9.6
Bad exit status from /var/tmp/rpm-tmp.V3BaQQ (%build)
--
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.
_______________________________________________
Mailing list: https://launchpad.net/~duplicity-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~duplicity-team
More help : https://help.launchpad.net/ListHelp
