Hi Dmitry,
On Sun, Jan 08, 2017 at 09:45:23PM +0300, Dmitry Shachnev wrote:
> >
> > The build does fail in the tests phase, but I does not look related to
> > what you are experiencing. Instead it seems to need running setup.py
> > makeuis in the build process.
>
> I get the same result as Albert
Hi Andreas,
On Sun, Dec 18, 2016 at 05:03:10PM +0100, Alberto Caso wrote:
> I could not reproduce the behavior you describe. Maybe your environment
> is messed?
>
> Here is what I get after removing your overrides (for full log see the
> attached file):
>
> [...]
> dh_auto_build -O--buildsystem=py
On Sun, Dec 18, 2016 at 05:03:10PM +0100, Alberto Caso wrote:
> On Sat, 2016-12-17 at 21:14 +0100, Andreas Tille wrote:
> > Unfortunately I have severe trouble to stop the build system from
> > always trying pyversions instead of py3versions. For instance I
> > injected
> >
> > override_dh_auto_b
On Sat, 2016-12-17 at 21:14 +0100, Andreas Tille wrote:
> Unfortunately I have severe trouble to stop the build system from
> always trying pyversions instead of py3versions. For instance I
> injected
>
> override_dh_auto_build:
> # No idea why this would call
> # python set
Hi,
I noticed that openmolar has a new upstream version which I injected
into packaging Git[1]. Upstream moved to Python 3 and so tried I for
the packaging.
Unfortunately I have severe trouble to stop the build system from always
trying pyversions instead of py3versions. For instance I injected
5 matches
Mail list logo
