Re: [s3ql] S3QL 2.13 upgrade broken (runtests.py fails on HostnameNotResolvable)

2015-02-11 Thread Strobi
> > That should have been "dugang 3.4", sorry. But it's correct in the > user's guide :-P. > > I must have misread it like 3.2 yesterday :-) Runtests gives me this: == 255 passed, 24 skipped, 1 warnings in 105.41 seconds =

Re: [s3ql] S3QL 2.13 upgrade broken (runtests.py fails on HostnameNotResolvable)

2015-02-11 Thread Nikolaus Rath
Strobi writes: >> S3QL needs at least dugong 3. Are you sure that you've got that >> installed? Try to run That should have been "dugang 3.4", sorry. But it's correct in the user's guide :-P. >> # python3 -c 'import dugong; print(dugong.__version__)' > > > > # python3 -c 'i

Re: [s3ql] S3QL 2.13 upgrade broken (runtests.py fails on HostnameNotResolvable)

2015-02-11 Thread Strobi
> S3QL needs at least dugong 3. Are you sure that you've got that >> installed? Try to run >> >> # python3 -c 'import dugong; print(dugong.__version__) >> >> > # python3 -c 'import dugong; print(dugong.__version__)' > 3.2 > > In addition to some google queries I made: DNS does work on this server (

Re: [s3ql] S3QL 2.13 upgrade broken (runtests.py fails on HostnameNotResolvable)

2015-02-10 Thread Strobi
> S3QL needs at least dugong 3. Are you sure that you've got that > installed? Try to run > > # python3 -c 'import dugong; print(dugong.__version__)' > > # python3 -c 'import dugong; print(dugong.__version__)' 3.2 -- You received this message because you are subscribed to the Google Groups "s3ql

Re: [s3ql] S3QL 2.13 upgrade broken (runtests.py fails on HostnameNotResolvable)

2015-02-10 Thread Nikolaus Rath
Super Strobi writes: > Hello Niko, > > I think I bumped in the same issue as issue #110 again whilst > upgrading to S3QL 2.13. > > Ran test unsuccessfully: [...] > from dugong import HostnameNotResolvable > E ImportError: cannot import name HostnameNotResolvable S3QL needs at least dugong 3. Are

[s3ql] S3QL 2.13 upgrade broken (runtests.py fails on HostnameNotResolvable)

2015-02-10 Thread Super Strobi
Hello Niko, I think I bumped in the same issue as issue #110 again whilst upgrading to S3QL 2.13. Current situation: fedora with S3QL 2.11.1 Ran built successfully: **python3 setup.py build_ext --inplace** running build_ext building 's3ql.deltadump' extension creating build creating build/temp.