Quoting Łukasz Walewski (2018-02-05 21:19:27)
> On 03.02.2018 14:23, Helmut Grohne wrote:
> > All Build-Depends are treated as host architecture by default. In this
> > case, it seems very likely that python is a build tool so you
> > (implicitly) requested python for the wrong architecture. Switch
Łukasz Walewski writes:
> BTW what is this python-all good for?
This expresses “whatever versions of Python 2 are currently supported in
the distribution”.
Similarly, ‘python3-all’ says the equivalent about Python 3 versions.
It is only contingent that, today, ‘python-all’ installs only Python
On 03.02.2018 14:23, Helmut Grohne wrote:
Recently the upstream development introduced a compile step that requires
some source files to be pre-processed with a Python script (shipped with the
sources). I thus added python-all to my Build-Depends field and the native
Why do you use python-all? I
Hi,
thanks to pabs for making me aware of the question. I'm cross posting it
to d-cross@l.d.o as that is the proper place for these questions.
On Fri, Feb 02, 2018 at 02:01:30PM +0100, Lukasz Walewski wrote:
> I maintain a binary package that is not part of Debian (yet). The upstream
> content is
Hi,
I maintain a binary package that is not part of Debian (yet). The
upstream content is developed for amd64 and armhf architectures and
distributed using git. I build the package using git-buildpackage and
pbuilder/pdebuild on an amd64 build machine with native (i.e. amd64)
pbuilder. Obviou
5 matches
Mail list logo
