Hi,
On Wed, Feb 19, 2014 at 7:45 PM, Barry Warsaw wrote:
> They don't run automatically during package build for either pbuilder or
> sbuild afaik, although that would be really nice.
No. Autopkgtests are designed to test *installed* packages, which is
just not possible to do at build time (i.e.
/me continues promoting pybuild:
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
diff --git a/debian/control b/debian/control
index 8699486..c
On Feb 21, 2014, at 01:59 PM, Dmitry Shachnev wrote:
>On Wed, Feb 19, 2014 at 7:45 PM, Barry Warsaw wrote:
>> They don't run automatically during package build for either pbuilder or
>> sbuild afaik, although that would be really nice.
>
>No. Autopkgtests are designed to test *installed* packages
On Feb 21, 2014, at 12:22 AM, Matthias Klose wrote:
>In most cases this should be replaced with a python3 shebang, which can be
>done with dh_python3 --shebang=/usr/bin/python3. But why not automate this?
>dh_python3 looks at the b-d's, and if it doesn't find a b-d on
>python3-all-dev or libpytho
* Matthias Klose , 2014-02-21, 00:22:
The most common thing is a generated dependency on python3.x, because a
package contains a file/binary with a python3.x shebang. In most cases
this should be replaced with a python3 shebang, which can be done with
dh_python3 --shebang=/usr/bin/python3. But
5 matches
Mail list logo
