On May 13, 2016, at 08:51 AM, Rolf Leggewie wrote:
>Ubuntu is still unchanged both in Xenial and Yakkety.
I'm currently in the process of resyncing the libpeas stack in Debian back to
Yakkety. It's slow going because the python2/3 loader issue isn't the only
delta from Debian in these packages.
Rolf,
I'm currently not aware of any python plugins available for Roger
Router. The
change to python3 has already been done in the new development version,
which will be released soon.
Am Fr, 13. Mai, 2016 um 6:34 schrieb Rolf Leggewie
:
On 13.05.2016 12:26, Rolf
On 13.05.2016 12:26, Rolf Leggewie wrote:
> there's been some talk in http://bugs.debian.org/620391 about Roger
> Router and PEAS Python2 plugins.
Make that http://bugs.debian.org/817936
Jan-Michael,
there's been some talk in http://bugs.debian.org/620391 about Roger
Router and PEAS Python2 plugins.
As upstream, are you actually aware of any Plugins for Roger that are
Python 2? I'd rather see them ported to Python 3 or become deprecated
than add a complicated web of additional
On 13.05.2016 08:51, Rolf Leggewie wrote:
> Hello Barry,
>
> so, libpeas-1.0-0-python2loader has officially made it into Debian. I'm
> now thinking how to deal with that for roger.
>
> On 03.04.2016 05:35, Barry Warsaw wrote:
>> On Apr 02, 2016, at 10:33 PM, Rolf Leggewie wrote:
>>
>> Hi Rolf,
>>
On 13.05.2016 11:22, Rolf Leggewie wrote:
> I think that depending on
> "libpeas-1.0-python2loader | libpeas-1.0-0 (<< 1.16.0-1ubuntu1),
> libpeas-1.0-0 (>= 1.18.0-2) | libpeas-1.0-python3loader" would be needed
> to support all of trusty, xenial and unstable from the same roger code
> base.
Hello Barry,
so, libpeas-1.0-0-python2loader has officially made it into Debian. I'm
now thinking how to deal with that for roger.
On 03.04.2016 05:35, Barry Warsaw wrote:
> On Apr 02, 2016, at 10:33 PM, Rolf Leggewie wrote:
>
> Hi Rolf,
>
>> I'm still at a loss what it is you are asking of me.
On 02.04.2016 23:35, Barry Warsaw wrote:
> I look at this as a tracking bug - something that needs to happen if another
> bug gets resolved, but nothing to do right now.
Thank you for the clarification.
I'll keep this ticket open in the spirit your explained above.
On Apr 02, 2016, at 10:33 PM, Rolf Leggewie wrote:
Hi Rolf,
>I'm still at a loss what it is you are asking of me. The title of this
>bug requests me to add a run-time dependency that doesn't even exist in
>Debian yet. In Ubuntu the change you advocate has been made, but
>apparently there were
On 02.04.2016 21:34, Barry Warsaw wrote:
> to reduce the overall dependence on Python 2 in Debian. We've already
> made this split in Ubuntu and haven't seen any reports of problems
Barry,
thank you for the quick response.
I'm still at a loss what it is you are asking of me. The title of this
On Apr 02, 2016, at 12:27 PM, Rolf Leggewie wrote:
>On 11.03.2016 19:45, Barry Warsaw wrote:
>> In bug #806824 I propose to split the Python loaders for libpeas into
>> separate binary packages.
>
>That split hasn't happened yet and it isn't even clear if
>libpeas-1.0-0-python2loader will ever
Barry,
On 11.03.2016 19:45, Barry Warsaw wrote:
> In bug #806824 I propose to split the Python loaders for libpeas into
> separate binary packages.
That split hasn't happened yet and it isn't even clear if
libpeas-1.0-0-python2loader will ever hit the archive. To file this bug
looks a bit
Source: roger-router
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
In bug #806824 I propose to split the Python loaders for libpeas into
separate binary packages. This allows us to segregate the Python 2
and Python 3 versions, and eases the transition to a
13 matches
Mail list logo