Hi. Is this issue being worked on or not? The BTS report was a bit
unclear to me there. What exactly should be done to fix it? Why did it
surface in the first place?
This issue is threatening to cause my package creepy to be removed
from testing 2016-02-07, and I hope this can be avoided.
--
On Mon, Jan 4, 2016 at 6:43 AM, Carl Chenet wrote:
> Hi Miguel,
>
> First of all, happy new year 2016!
Hi Carl, happy new year to you as well! :)
> [...]
>
> Tell me if I'm wrong but unittests executions are not mandatory by
> Debian policy while building a Debian package.
Hi Miguel,
First of all, happy new year 2016!
We have a RC bug for Tweepy in Debian because the unittest2 and/or vcr
Python modules are not packaged for Debian, so the package build fails
while trying to execute the unit tests of Tweepy and my packages
depending on python3-tweepy can not go to
On Jan 04, 2016, at 10:43 AM, Carl Chenet wrote:
>We have a RC bug for Tweepy in Debian because the unittest2 and/or vcr
>Python modules are not packaged for Debian
Not correct. Both packages are in Debian for both Python 2 and 3.
We have unittest2 1.1.0-6 and vcr 1.7.3-1
There must be some
Source: tweepy
Version: 3.4.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
tweepy fails to build from source in unstable/amd64:
[..]
5 matches
Mail list logo