Pe 11 iul. 2016 11:17, "Andreas Tille" <andreas@an3as.eu> a scris:
>
> On Mon, Jul 11, 2016 at 10:02:11AM -0500, Michael Crusoe wrote:
> > Yeah, -dev is inappropriate; we aren't compiling a custom module. Something
> > broke with the Python packages in unstable.
> >
> > Using python*-dev leads to
> >
> > I: mypy source: build-depends-on-python-dev-with-no-arch-any
> > N:
> > N: The given package appears to have a Python development package
> > N: (python-dev, python-all-dev or pythonX.Y-dev) listed in its
> > N: Build-Depends or Build-Depends-Indep fields, but only "Architecture:
> > N: all" packages are built by this source package. Python applications
> > and
> > N: modules do not usually require those dev packages, so you should
> > N: consider removing them in favour of python, python-all or pythonX.Y.
> > N:
> > N: If you are building a Python extension instead, you should have
> > N: development packages listed in Build-Depends, but normally there
> > should
> > N: be at least one Architecture: any package.
> > N:
> > N: Severity: minor, Certainty: possible
> > N:
> > N: Check: fields, Type: binary, udeb, source
> > N:
>
> I noticed this lintian issue but trading a lintian information for a
> FTBFS error is fair, isn't it?
Lintian is correct, so no issue there :-)
> > I had previously uploaded a 0.4.2-2 but the build failed due to this
> > transient error elsewhere:
> > https://buildd.debian.org/status/package.php?p=mypy
> >
> > How do I request a new build?
>
> Hmmm, is there any need for a new build? If the package builds now fine
> as is (which I did not tested) I would write this insied the bug report
> (not reproducible any more).
Yes a new build is needed, there are no binary packages; I did a source only upload.
It builds for me in an updated pbuilder chroot but I don't know how to trigger the build daemons to try again.
> Kind regards
>
> Andreas.
>
> --
> http://fam-tille.de
>