Re: [Duplicity-talk] Duplicity 1.0.1 Released

[Scott Hannahs]

Ken,

I will leave fink out, but it should be doing exactly the same thing!  :-)

the following doesn’t even build duplicity correctly, so I don’t get to the tox command.

% tar xf duplicity-1.0.1.tar 

% cd duplicity-1.0.1 

% % C_INCLUDE_PATH=/opt/sw/include LIBRARY_PATH=/opt/sw/lib python3 ./setup.py build_ext > build.out.txt 2>&1

This gives the following output.

Unable to get SCM version: defaulting to 1.0.1

running build_ext

Building extension for librsync...

building 'duplicity._librsync' extension

clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -I/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/include/python3.9 -c duplicity/_librsyncmodule.c -o build/temp.macosx-10.9-universal2-3.9/duplicity/_librsyncmodule.o

clang -bundle -undefined dynamic_lookup -arch arm64 -arch x86_64 -Wl,-headerpad,0x1000 build/temp.macosx-10.9-universal2-3.9/duplicity/_librsyncmodule.o -lrsync -o build/lib.macosx-10.9-universal2-3.9/duplicity/_librsync.cpython-39-darwin.so

ld: warning: ignoring file /opt/sw/lib/librsync.dylib, building for macOS-arm64 but attempting to link with file built for macOS-x86_64

ld: warning: dylib (/opt/sw/lib/librsync.dylib) was built for newer macOS version (12.4) than being linked (10.9)

copying build/lib.macosx-10.9-universal2-3.9/duplicity/_librsync.cpython-39-darwin.so -> duplicity

I am building on an X86 machine and my libraries are x86 and I am not trying to build a universal arm 64 system.   But with warnings it tries to build.

tox does not like the py3x value

% tox -epy3 

py3 create: /Users/sth/Downloads/duplicity-1.0.1/.tox/py3

py3 installdeps: -rrequirements.txt

and I ran out of time this AM waiting for more output.

-Scott

On Oct 5, 2022, at 11:54 AM, Kenneth Loafman <kenneth@loafman.com> wrote:

Could you try just building and running the tests in a 'normal' user environment?  Leave Fink out of the picture.

do this:

1. $ tar xf duplicity-1.01.tar.gz
2. $ ./setup.py build_ext
3. $ tox -e py3x

...Thanks,

...Ken