On Wednesday, January 06, 2016 03:39:15 PM you wrote:
...
> 1. pygpgme is FTBFS due to test failures (#797776). There has been no
> response from the maintainers and I have been unable to determine the
> source of the failures. I do not believe it is python3 version related (the
> package builds
Control: tags -1 confirmed
On 06/01/16 21:39, Scott Kitterman wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
>
> This is the tracking bug for the transition to make python3.5 the default
> python3. The transition trac
On Wednesday, January 06, 2016 03:39:15 PM you wrote:
...
> 2. Elektra is FTBFS due to unrelated test failures (#810069). The impact
> of this is that python3-elektra will become uninstallable. It has no
> rdepends. Presumably elektra could be temporarily removed from testing.
...
This issue tu
On Jan 06, 2016, at 01:34 PM, Nikolaus Rath wrote:
>If necessary, s3ql can also be build with cython instead of cython3.
I strongly suspect this is a regression due to
http://bugs.python.org/issue22995 which I've now reopened. We're probably
just starting to see the unintended consequences of th
On Jan 06 2016, Scott Kitterman wrote:
> 5. Cython3 not currently working [3]. This appears to be due to a change in
> python3.5. It affects borgbackup and s3ql only. As these are rather late in
> the transition, we could probably go ahead while this is getting sorted.
> These
> are both lea
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
This is the tracking bug for the transition to make python3.5 the default
python3. The transition tracker is already in place [1].
The archive is generally ready for this transition, bu
6 matches
Mail list logo