On Sat, Mar 8, 2014 at 4:57 AM, Andreas Noteng andr...@noteng.no wrote:
On 07. mars 2014 02:52, Vincent Cheng wrote:
If there aren't any non-DFSG-compliant files in upstream's tarball
(and I see nothing that would suggest that this file in particular is
non-DFSG-compliant), please do not
i,
(I realise this list is primarily on packaging Python modules, but since I got
no response from the Python maintainer, I'm trying it here)
I prepared a security update for python2.7 in stable-security fixing
CVE-2013-4238
and CVE-2014-1912. But rebuilding the package caused changes in the
* Moritz Muehlenhoff j...@debian.org, 2014-03-11, 18:30:
I prepared a security update for python2.7 in stable-security fixing
CVE-2013-4238 and CVE-2014-1912. But rebuilding the package caused
changes in the file list which are not obvious to me:
In python2.7-minimal:
On Tue, Mar 11, 2014 at 07:26:55PM +0100, Jakub Wilk wrote:
* Moritz Muehlenhoff j...@debian.org, 2014-03-11, 18:30:
I prepared a security update for python2.7 in stable-security fixing
CVE-2013-4238 and CVE-2014-1912. But rebuilding the package caused changes
in the file list which are not
[This is a copy of what I sent to #702005 (after unarchiving it), which
didn't show up on bugs.d.o yet.]
According to python2.7-minimal's README.Debian, the _ssl and _hashlib
are supposed to be included in the -minimal package.
python2.7-minimal_2.7.3-6_amd64.deb indeed includes them both,
Hello,
Le 05/03/2014 10:31, Andreas Tille a écrit :
I have noted another problem: I worked a bit
on the tests and noticed that those tests that are including compiled C
code are failing. Is there anything in addition I need to do to make
the C object code visible to the Python modules?
Can
Hello,
I'm working on a package that uses pytest. Conventiently, pybuild seems
to have a --test-pytest option -- but I'm completely at a loss where to
put it.
Currently my rules file looks like this:
,
| #!/usr/bin/make -f
| # -*- makefile -*-
|
| #export DH_VERBOSE=1
| export
7 matches
Mail list logo
