Hi Ivan,
you were right on target. I've added the build path to the PYTHONPATH
and the tests are now running.
Andreas, I'll push my changes to the repo right away. Could you please
check if everything seems to be fine also on your side?
Cheers!
Tomás
On 28/12/13 00:32, Ivan Kalev wrote:
> Hi An
Hi Andreas,
Nothing has really changed on our end. Is /your/path/to/CSB in $PYTHONPATH?
This error typically means that the package "csb" is not importable, i.e.
the python interpreter does not know where to find it. Here is an example:
$ hg clone https://hg.codeplex.com/csb ~/build
$ export PYTH
Hi Ivan,
On Fri, Dec 27, 2013 at 11:07:57PM +0100, Ivan Kalev wrote:
> Hi Andreas,
>
> Here is an alternative solution: in version 1.2.2 you can override the
> default cache directory with -g:
>
> $ python csb/test/app.py --generated-resources /tmp
>
> What do you think? Version 1.2.2 can be
Hi Andreas,
Here is an alternative solution: in version 1.2.2 you can override the
default cache directory with -g:
$ python csb/test/app.py --generated-resources /tmp
What do you think? Version 1.2.2 can be downloaded from PyPI or CodePlex
Best regards,
Ivan
On Dec 25, 2013 10:02 AM, "Andrea
Hi Ivan,
On Wed, Dec 25, 2013 at 08:56:02AM +, Ivan Kalev wrote:
> The problem with /var/lib or cache is that it won't work on windows. The
> advantage of ~ is that python resolves it to user's home directory on any
> platform. Transparent portability is somehow essential in csb.
OK, sorry fo
Hi Andreas,
The problem with /var/lib or cache is that it won't work on windows. The
advantage of ~ is that python resolves it to user's home directory on any
platform. Transparent portability is somehow essential in csb.
But there are other options as well:
1) Use a temp directory and setup/tea
Hi Ivan,
On Tue, Dec 24, 2013 at 08:41:38AM +, Ivan Kalev wrote:
> Just to make sure that I understood everything correctly:
>
> - you run the build as root
Well, it is actually fakeroot (so faking to be root but without
permission to write to /usr).
> - then you run the test suite again as
Hi Andreas,
Just to make sure that I understood everything correctly:
- you run the build as root
- then you run the test suite again as root and it passes, right?
- this bug appears only when you install the built package and then run the
test suite as normal user?
Is this all correct?
Here is
Hi Ivan,
many thanks for your quick reply.
On Mon, Dec 23, 2013 at 12:39:46PM +, Ivan Kalev wrote:
> Michael's address has changed indeed --- the correct one is mhab...@gwdg.de.
Thanks - updated the address in our packaging metadata.
> The problem here is that these are not intermediate re
9 matches
Mail list logo
