Yes,
but how can I tell to dh_ to use py3versions instead of pyversions ?
I only found discussion for bug #597105 from 2010. One solution is
define own rules to use py3versions. So, is there another clearer and
simple solution, like variable in deian control, or set some
environment variable in
Use py3versions for Python3.
Scott K
On October 26, 2017 4:46:56 PM EDT, Ondrej Tuma wrote:
>Hi there,
>
>i try to create my first official debian package of my Formiko
>application. So Formiko is gui application, and i want to create
>package with python3. But when i try build package with sbui
Hi there,
i try to create my first official debian package of my Formiko
application. So Formiko is gui application, and i want to create
package with python3. But when i try build package with sbuild, I got
error:
Can't exec "pyversions": No such file or directory ...
What i see, pyversions is
On 10/26/2017 03:02 PM, Thomas Goirand wrote:
> To avoid breakage, I'll wait for antlr support for Python 3 passes the
> NEW queue, and then upload. I've already merged to master.
I've found out that antlr.py is embedded, and still in use in this
upstream release. So I added a patch to remove it f
On 10/26/2017 12:27 PM, Jan Dittberner wrote:
> On Wed, Oct 25, 2017 at 08:02:57PM +0200, Thomas Goirand wrote:
>> Hi Jan,
>>
>> I've pushed to the git a new branch called new-upstream-1.3.0, which
>> adds Python 3 support, and some improvements to the package. Here's the
>> debian/changelog:
>>
>>
On Wed, Oct 25, 2017 at 08:02:57PM +0200, Thomas Goirand wrote:
> Hi Jan,
>
> I've pushed to the git a new branch called new-upstream-1.3.0, which
> adds Python 3 support, and some improvements to the package. Here's the
> debian/changelog:
>
> * New upstream release.
> * Ran wrap-and-sort -b
Hi Angel and team,
would you mind, if I update wokkel and close #735304 (teams git
repo) and #879712 (Python 3 support)? I would add myself to
uploaders, too.
TIA & Cheers
signature.asc
Description: PGP signature
7 matches
Mail list logo