Fwd: libturpial: FTBFS: Trying to write outside builddir

[Miguel Landaeta]

tags 750348 + confirmed help upstream
forwarded 750348 turpi...@googlegroups.com
thanks

On Mon, Jun 02, 2014 at 08:59:10PM +0200, David Suárez wrote:
> Source: libturpial
> Version: 1.7.0-2
> Severity: serious
> Tags: jessie sid
> User: debi...@lists.debian.org
> Usertags: qa-ftbfs-20140601 qa-ftbfs
> Justification: FTBFS on amd64
>

Hi folks,

I'm looking for help with this bug. For full context, please take a
look at:

* https://bugs.debian.org/750348
* http://aws-logs.debian.net/ftbfs-logs/2014/06/01/libturpial_1.7.0-2_unstable.log

What is happening here is: a Debian autobuilder is unable to build
libturpial from source. This is a serious bug and has caused to get
turpial dropped from testing.

The autobuilder is failing because libturpial unit tests are trying to
write in the homedir of the user who is running the build and this
violates Debian guidelines (a package should not try to write outside
its builddir).

I was hacking the unit tests but I'm unable to get a reasonable fix
for this issue. The files with problematic unit tests are:

* tests/test_column_manager.py
* tests/test_account_manager.py
* tests/test_core.py

I stumbled upon these two situations:

* I tried to pass an explicit basedir to libturpial.config.AppConfig
constructor to override the default basedir pointing to the homedir of
the user running libturpial. I did this on tests/test_column_manager.py
and tests/test_account_manager.py.

* On tests/test_core.py I noticed that I can't specify an explicit
basedir when you create an instance of libturpial.api.core.Core, so this
is going to try to create ~user/.config/turpial.


I'm looking for help to get a fix or workaround for this issue.

Thanks,

--
Miguel Landaeta, nomadium at gmail.com
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche

[Miguel Landaeta]

On Thu, Jul 31, 2014 at 06:16:58PM -0300, Miguel Landaeta wrote:

> [...]

>

> I'm looking for help to get a fix or workaround for this issue.

>

I decided to disable the unit tests during build time and prepared a

new upload (1.7.0-3) with this change.

I'm downgrading the severity of this bug since libturpial is not going

to FTBFS but I keep the bug open because this is not a proper fix.

This is a workaround, so libturpial can migrate to testing and can be

included in "jessie".

The units tests must not write outside the builddir and they must pass

to be able to close this bug report.

--

Miguel Landaeta, nomadium at gmail.com
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key

[Wil Alvarez]

Hey Miguel,

Thanks for reporting this behavior. I'm really busy right now but I've created the ticket in github to fix it soon when I've a couple of free hours.

Regards

--
Has recibido este mensaje porque estás suscrito al grupo "Turpial-Dev" de Grupos de Google.
Para anular la suscripción a este grupo y dejar de recibir sus mensajes, envía un correo electrónico a turpial-dev...@googlegroups.com.
Para acceder a más opciones, visita https://groups.google.com/d/optout.

--

Wil A. Alvarez
Linux Counter #415026

Debian Counter #259

http://turpial.org.ve
http://damncorner.blogspot.com/