On 12/11/2011 03:38 PM, Christian wrote:

Hi Nikolaus,

Am 11.12.2011 02:33, schrieb Nikolaus Rath:

...

Hello,

I noticed that the S3QL OpenSUSE package at https://build.opensuse.org/package/show?package=s3ql&project=filesystems lags far behind the upstream version and has also failed to build for quite some time.

Is there anything I can do (as the upstream developer) to help getting this fixed? I'm not familiar with either OpenSUSE or RPM packaging (long-time Debian user), but I'd be happy to assist in any way I can. I tried to update to current version, but still having some problems. Perhaps you can help fixing the failed builds.

look here: https://build.opensuse.org/project/show?project=home%3Acomputersalat%3Abranc...

I clicked on "build errors" and then on "failed" under "openSUSE_11.4 x86_64". If I'm looking at the right output, then this just says that some module could not be loaded. The stupid Python unittest2 module hides the real error message behind a generic "can't load test". My guess is that there is no llfuse Python module installed in the build environment. Could that be it? Could you temporarily insert a call to bin/mount.s3ql --help before the call to setup.py test? This should fail with a more helpful error message.

P.S.: Is there really need to have python >= 2.6.6 ? This would work only for openSUSE >= 11.4

Can you incorporate a patch in the RPM? If so, you could reuse the patch that's used in the Ubuntu Lucid package, which makes S3QL compatible with any Python 2.6. You can download it at https://launchpad.net/~nikratio/+archive/s3ql/+files/s3ql_1.8.1-1%7Elucid1.d..., the patch is in debian/patches. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

chris@computersalat.de writes:

...

Could you temporarily insert a call to bin/mount.s3ql --help before the call to setup.py test? This should fail with a more helpful error message. done

Sorry, my bad. Now the build error is + python bin/mount.s3ql --help Traceback (most recent call last): File "bin/mount.s3ql", line 22, in <module> import s3ql.mount File "/home/abuild/rpmbuild/BUILD/s3ql-1.8.1/src/s3ql/mount.py", line 10, in <module> from . import fs, CURRENT_FS_REV File "/home/abuild/rpmbuild/BUILD/s3ql-1.8.1/src/s3ql/fs.py", line 14, in <module> from . import deltadump File "/home/abuild/rpmbuild/BUILD/s3ql-1.8.1/src/s3ql/deltadump.py", line 17, in <module> from . import _deltadump ImportError: cannot import name _deltadump but that's because _deltadump.so was compiled into build/, where bin/mount.s3ql can't find it. If you could add 'setup.py build_ext --inplace' before 'bin/mount.s3ql --help', that would be great. Sorry...

P.S.: Please do not "CC" me on "list mails", just "reply to list". Thank you.

Just did so because you did it first :-P. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Pascal Bleser <pascal.bleser@opensuse.org> writes:

I've just changed our python-apsw package to link dynamically against the sqlite3-devel package version of each openSUSE/SLE version, instead of building against the latest amalgamation.

Once that is through, I'll test the build again.

(I'm hacking on filesystems/s3ql, and not home:...)

I just looked at s3ql.spec, some comments: - Dependency on gccxml can be dropped - With the Debian patch, you can depend on Python >= 2.6 instead of Python >= 2.6.5 - Hardcoding the URL of the .debian.tar.bz2 is going to break once the Ubuntu package gets updated, and I'm not sure if you always want to run all the debian patches. My recommendation would be to copy the 2.6 compatibility patch into the opensuse package and not refer to Ubuntu at all. - Dependency on python-paramiko can be dropped - Dependency on llfuse needs to be bumped up to 0.37 - Dependency on FUSE should probably be versioned to >= 2.8.0 - You don't need to remove tests/t4_* and t5_*, they should be skipped automatically if no fuse module has been loaded Thanks for your work, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Pascal Bleser <pascal.bleser@opensuse.org> writes:

You'll note that I chose to rename all /usr/bin/* stuff to prefix it with "s3ql-", in order to avoid clashes with other binaries, as their names are.. well.. not necessarily s3ql specific :)

Hope that's fine with you.

Hmmm. Everything that S3QL install by default in /usr/bin already has 's3ql' in its name (mount.s3ql, s3qlcp, s3qlrm etc). Are you talking about the stuff in contrib/ that doesn't get installed by setup.py automatically? I think the only scripts in there that deserve a place in /usr/bin are expire-backups and pcp. I guess that name clashes need to be avoided, but prefixing them with -s3ql would IMO be misleading, because they don't need an S3QL file system, and S3QL doesn't need them... Best, -Nikolaus PS: I'm (positively) surprised to get such a quick response from you here on the list. I sent you two or three personal emails about S3QL packaging over the last year and never got any reply -- or did they get caught in some filter? -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On 12/12/2011 08:50 AM, Pascal Bleser wrote:

On 2011-12-11 17:59:07 (-0500), Nikolaus Rath <Nikolaus@rath.org> wrote:

...

On 12/11/2011 03:38 PM, Christian wrote: [...] My guess is that there is no llfuse Python module installed in the build environment. Could that be it?

No, llfuse is installed in the build chroot.

But some tests will fail anyway because we cannot load the fuse module in the build chroot (runs in a chroot + building and testing does not run as root). We shall disable those tests.

This should already be done automatically.

...

Could you temporarily insert a call to bin/mount.s3ql --help before the call to setup.py test? This should fail with a more helpful error message.

from . import _deltadump ImportError: cannot import name _deltadump

Even when explicitly adding the directory that contains _deltadump.so to PYTHONPATH, it still fails.

Hmm. But that's not the complete error message, or is it? Can I download a CD or virtual host image somewhere to reproduce this? Thanks, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org