Debian Bug report logs - #806824
libpeas: Split Python 2 and 3 support

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: libpeas: Split Python 2 and 3 support

Date: Tue, 01 Dec 2015 16:46:44 -0500

Source: libpeas
Severity: wishlist

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear Maintainer,

As we move to a world dominated by Python 3, we are trying to reduce
the dependencies on Python 2 in Debian and derivatives.  libpeas is a
problem because the package links against both Python 2 and Python 3.

I don't know whether it makes sense to support both at the same time,
but it definitely makes sense to have a version that only supports
Python 3.  For example, in Ubuntu we want to remove Python 2 from the
default images, but we can't do that with a libpeas that links against
both Python 2 and 3.

At the least, we need a libpeas built without --enable-python2.
Questions:

* Does it also make sense to have a libpeas built without
  --enable-python3?
  
* Does it still make sense to have a libpeas built with both
  --enable-python2 and --enable-python3 as is currently the case?

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJWXhVBAAoJEBJutWOnSwa/UG0P/3kPG+wfjtxlM2Ht0zkCJQKa
lB6jiBNOHjm+AJbhYaQMdfvuCLy8z7fXn8NVgyJtlEEBlD8mwjl7e5LrYSgXFmoN
wdYAbJohckVVjhOEek6vsvX5YU9JGSR/np0aA1B1gkxKZBIUfIzdPiTX446kTOyg
X/EdXLpz5EwWPJLZavxSBe4BC09VNmCB+zUXllIjgIBb/xqSsstkVODAjjO3hAcc
JQF0lfUqRAYwCFhvb99qiSvx/NDluzAHOt2NVaYOCMVEealpIKFAK8sncltXrRX2
ocHlqhooCKIbv0+p75LVdN1MrCJcXPp/umriL88jxYsnC3Wb8Opw873FdglaeapV
bkhBfODmx0rQTBwmGJSR2u05/506sLTmGfLg5xyBF81nE7WzBmeXnOkDrn+NIihl
0mrvChgYUfpMzQiWOBN2qnZ1KtsrekPYeQyLi6znKjhUQXDqmghQM5uSpn4o0Aqw
YCLN5Z5slsOZIJ1wFg2x8jWS5/lSG4duuXhVN8TdWb8Kp3FAKVxO30fEREKSxC7c
Bpk0PJWpgwCW+lLPL2ggHUymGWlS5kX/NUkR+vQ5JZ4RyVGeyvBY+X9/iL+yxEfU
EdCAQOTM/0sSJFSIwC0m8LFTSrmPJ4fWjk4fM+yEWkJezwLpSHaDlsUPIMWSvpMM
FmRIQriklAzmUc5sprdY
=Sa0W
-----END PGP SIGNATURE-----

Message #10 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: 806824@bugs.debian.org

Date: Thu, 14 Jan 2016 09:53:15 -0500

[Message part 1 (text/plain, inline)]

This is actually easier than I first thought.  All we need to do is move the
Python loaders to separate binary packages and update dependents which ship
Python support to Depends on the appropriate loader package.

This is an important fix so that we can provide images which only have Python
3 support.  See the attached patch.  For a list of packages which will need
updated Depends, see

https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1440504/comments/6

and

https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1440504/comments/9

[lp1440504.diff (text/x-patch, attachment)]

Message #15 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: 806824@bugs.debian.org

Date: Fri, 15 Jan 2016 12:30:27 -0500

[Message part 1 (text/plain, inline)]

This one has the Breaks/Replaces and a Recommends.  Please feel free to adjust
the changelog entry.

[bug806824.diff (text/x-patch, attachment)]

Message #20 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: 806824@bugs.debian.org

Date: Thu, 18 Feb 2016 09:54:25 -0500

We've gone ahead and made this transition in Ubuntu 16.04, just as described
here.  See LP: #1440504 for the changes we made to dependents.  I am not a
Gnome developer so I don't want to make the changes in Debian despite being a
DD, but I'm happy to help if patches are needed.

Message #25 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Iain Lane <laney@debian.org>

To: Barry Warsaw <barry@debian.org>, 806824@bugs.debian.org

Subject: Re: Bug#806824: (no subject)

Date: Fri, 19 Feb 2016 11:52:23 +0000

[Message part 1 (text/plain, inline)]

On Thu, Feb 18, 2016 at 09:54:25AM -0500, Barry Warsaw wrote:
> We've gone ahead and made this transition in Ubuntu 16.04, just as described
> here.  See LP: #1440504 for the changes we made to dependents.  I am not a
> Gnome developer so I don't want to make the changes in Debian despite being a
> DD, but I'm happy to help if patches are needed.

It would be good IMO if you would provide patches for this. I don't see a
problem with us doing this transition in Debian (but others should shout if
they disagree).

(sid-amd64)root@xenial:/# apt rdepends libpeas-1.0-0 
libpeas-1.0-0
Reverse Depends:
  Depends: libpeas-dev (= 1.16.0-1+b1)
  Depends: libtotem0 (>= 1.0.0)
  Depends: roger-router-cli (>= 1.0.0)
  Depends: roger-router (>= 1.0.0)
  Depends: libroutermanager0 (>= 1.1.0)
  Depends: rhythmbox-plugins (>= 1.0.0)
  Depends: rhythmbox-plugin-cdrecorder (>= 1.0.0)
  Depends: rhythmbox (>= 1.0.0)
  Depends: librhythmbox-core9 (>= 1.0.0)
  Depends: liferea (>= 1.1.0)
  Depends: libpeas-doc (>= 1.1.0)
  Depends: gnome-builder (>= 1.6.2)
  Depends: gir1.2-peas-1.0 (>= 1.14.0)
  Depends: gtranslator (>= 1.1.0)
  Depends: libdiodon0 (>= 1.1.0)
  Depends: gedit-plugins (>= 1.0.0)
  Depends: gedit (>= 1.1.0)
  Depends: eog-plugins (>= 1.0.0)
  Depends: eog (>= 1.0.0)
  Depends: entangle (>= 1.1.0)
  Depends: deja-dup (>= 1.0.0)
  Depends: diodon (>= 1.0.0)
(sid-amd64)root@xenial:/# apt rdepends gir1.2-peas-1.0
gir1.2-peas-1.0
Reverse Depends:
  Depends: libpeas-dev (= 1.16.0-1+b1)
  Depends: totem-plugins
  Depends: rhythmbox-plugins
  Depends: liferea
  Depends: gir1.2-entangle-0.1
  Depends: gtranslator
  Depends: gnome-builder
  Depends: gedit-plugins
  Depends: gedit
  Depends: eog

Assuming that the analysis is the same as Ubuntu, that leaves

  deja-dup entangle eog gedit gnome-builder gtranslator liferea totem rhythmbox

to be updated.

You could provide us with an svn diff for the pkg-gnome maintained
packages, and file bugs for the other ones - I could then upload our
ones.

Given that we have to interact with other maintainers, this transition
could be made into a smooth one by uploading libpeas itself (why do I
always type libpease?) with a dependency on both loaders from
libpeas-1.0-0 (did it again there) until everything has been adjusted.
WDYT?

-- 
Iain Lane                                  [ iain@orangesquash.org.uk ]
Debian Developer                                   [ laney@debian.org ]
Ubuntu Developer                                   [ laney@ubuntu.com ]

[signature.asc (application/pgp-signature, inline)]

Message #30 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

Cc: 806824@bugs.debian.org

Subject: Re: Bug#806824: (no subject)

Date: Fri, 19 Feb 2016 10:08:09 -0500

[Message part 1 (text/plain, inline)]

On Feb 19, 2016, at 11:52 AM, Iain Lane wrote:

>Assuming that the analysis is the same as Ubuntu, that leaves
>
>  deja-dup entangle eog gedit gnome-builder gtranslator liferea totem rhythmbox
>
>to be updated.

That's a few more than what I changed in Ubuntu, which makes me think maybe I
missed them.

In Ubuntu deja-dup doesn't have a direct dependency on python2.7 since the
bits that do are installed on demand.   I don't see a direct depends in
entangle, eog (though yes for eog-plugins), or totem.

>You could provide us with an svn diff for the pkg-gnome maintained
>packages, and file bugs for the other ones - I could then upload our
>ones.
>
>Given that we have to interact with other maintainers, this transition
>could be made into a smooth one by uploading libpeas itself (why do I
>always type libpease?) with a dependency on both loaders from
>libpeas-1.0-0 (did it again there) until everything has been adjusted.
>WDYT?

I think that's a great idea.  I'll work on the diffs and bugs.  Thanks!

[Message part 2 (application/pgp-signature, inline)]

Message #35 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: Iain Lane <laney@debian.org>

Cc: 806824@bugs.debian.org

Subject: Re: Bug#806824: (no subject)

Date: Thu, 10 Mar 2016 17:58:13 -0500

[Message part 1 (text/plain, inline)]

I finally managed to report bugs on deja-dup, eog-plugins, gedit,
gnome-builder, gtranslator, liferea, rhythmbox, and totem.

[Message part 2 (application/pgp-signature, inline)]

Message #40 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Iain Lane <laney@debian.org>, 806824@bugs.debian.org, Barry Warsaw <barry@debian.org>

Subject: Re: Bug#806824: (no subject)

Date: Fri, 11 Mar 2016 00:20:11 +0100

[Message part 1 (text/plain, inline)]

Am 19.02.2016 um 12:52 schrieb Iain Lane:
> On Thu, Feb 18, 2016 at 09:54:25AM -0500, Barry Warsaw wrote:
>> We've gone ahead and made this transition in Ubuntu 16.04, just as described
>> here.  See LP: #1440504 for the changes we made to dependents.  I am not a
>> Gnome developer so I don't want to make the changes in Debian despite being a
>> DD, but I'm happy to help if patches are needed.
> 
> It would be good IMO if you would provide patches for this. I don't see a
> problem with us doing this transition in Debian (but others should shout if
> they disagree).


Tbh, I'm not too thrilled by hard-coding dependencies on
libpeas-1.0-0-python3loader in several packages.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #45 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: Michael Biebl <biebl@debian.org>

Cc: Iain Lane <laney@debian.org>, 806824@bugs.debian.org

Subject: Re: Bug#806824: (no subject)

Date: Thu, 10 Mar 2016 18:27:58 -0500

[Message part 1 (text/plain, inline)]

On Mar 11, 2016, at 12:20 AM, Michael Biebl wrote:

>Tbh, I'm not too thrilled by hard-coding dependencies on
>libpeas-1.0-0-python3loader in several packages.

Can you explain why?

[Message part 2 (application/pgp-signature, inline)]

Message #50 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Barry Warsaw <barry@debian.org>

Cc: Iain Lane <laney@debian.org>, 806824@bugs.debian.org

Subject: Re: Bug#806824: (no subject)

Date: Fri, 11 Mar 2016 07:22:11 +0100

[Message part 1 (text/plain, inline)]

Am 11.03.2016 um 00:27 schrieb Barry Warsaw:
> On Mar 11, 2016, at 12:20 AM, Michael Biebl wrote:
> 
>> Tbh, I'm not too thrilled by hard-coding dependencies on
>> libpeas-1.0-0-python3loader in several packages.
> 
> Can you explain why?

It creates unnecessary churn and potential stale dependencies in the future.
Most importantly, this split looks like an implementation detail to me.
I don't see, why packages should add a dependency on
libpeas-1.0-0-python3loader but not libpeas-1.0-0-python2loader

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #55 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: Michael Biebl <biebl@debian.org>

Cc: Iain Lane <laney@debian.org>, 806824@bugs.debian.org

Subject: Re: Bug#806824: (no subject)

Date: Fri, 11 Mar 2016 09:34:55 -0500

[Message part 1 (text/plain, inline)]

On Mar 11, 2016, at 07:22 AM, Michael Biebl wrote:

>It creates unnecessary churn and potential stale dependencies in the future.
>Most importantly, this split looks like an implementation detail to me.
>I don't see, why packages should add a dependency on
>libpeas-1.0-0-python3loader but not libpeas-1.0-0-python2loader

I'm not sure about your first point, but as to your last point: it would make
no sense for an application to depend on both loaders.  You cannot load both a
Python 2 and Python 3 runtime into the same address space.

The problem this is trying to solve is two-fold.  First, some libpeas plugins
don't use Python at all, and yet with the old arrangement they would still be
pulling in both Python stacks.  With this change, non-Python plugins wouldn't
depend on either loader package and it would be a clear win.

Python plugins are either going to be ported to Python 3 or not, in which case
they now make explicit which runtime stack they require, via the loader they
depend on, and in fact load at runtime (again, they cannot load them both).
So this is another win because it allows such applications to only depend on
the Python stack they use, and we can better identify which ones need porting
to Python 3.

[Message part 2 (application/pgp-signature, inline)]

Message #60 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Barry Warsaw <barry@debian.org>

Cc: Iain Lane <laney@debian.org>, 806824@bugs.debian.org

Subject: Re: Bug#806824: (no subject)

Date: Fri, 11 Mar 2016 16:16:05 +0100

[Message part 1 (text/plain, inline)]

Hi Barry,

first of all, would be great if you can block all bugs you filed by this
one, so we can keep track of them more easily and the maintainers of
those packages know that they should hold off until this particular bug
report has been dealt with.

Looking at [1] I see a few packages missing on your list.

Am 11.03.2016 um 15:34 schrieb Barry Warsaw:
> On Mar 11, 2016, at 07:22 AM, Michael Biebl wrote:
> 
>> It creates unnecessary churn and potential stale dependencies in the future.
>> Most importantly, this split looks like an implementation detail to me.
>> I don't see, why packages should add a dependency on
>> libpeas-1.0-0-python3loader but not libpeas-1.0-0-python2loader
> 
> I'm not sure about your first point, but as to your last point: it would make
> no sense for an application to depend on both loaders.  You cannot load both a
> Python 2 and Python 3 runtime into the same address space.

Ok, this was misleading. I'll try to explain what I meant in more
detail. Let's take liferea as an example, which currently uses python2.
You asked the maintainer to add an explicit dependency on
libpeas-1.0-0-python2loader, but didn't really explain why.
The maintainer would need to know that he needs to scan all .plugin
files for Loader=python[3] lines, and do that for every new upstream
release.
It's highly likely, that liferea is ported to python3 at some point but
this dependency is forgotten to be updated to libpeas-1.0-0-python3loader.

> The problem this is trying to solve is two-fold.  First, some libpeas plugins
> don't use Python at all, and yet with the old arrangement they would still be
> pulling in both Python stacks.  With this change, non-Python plugins wouldn't
> depend on either loader package and it would be a clear win.
> 
> Python plugins are either going to be ported to Python 3 or not, in which case
> they now make explicit which runtime stack they require, via the loader they
> depend on, and in fact load at runtime (again, they cannot load them both).
> So this is another win because it allows such applications to only depend on
> the Python stack they use, and we can better identify which ones need porting
> to Python 3.

So, I'm not generally against splitting out the loaders, but if we do
so, I think we should automate the dependency generation via a dh_peas
debhelper addon, which scans .plugin files and adds the correct
dependency depending on what it finds.

The alternative I see, is to not split out the loaders, but get the
remaining python2-using packages ported and then disable the python2 loader.

Splitting off the loaders and adding the dependencies manually is a
quick and dirty solution which creates a maintenance burden down the
line. I prefer solutions that potentially require more initial work but
create less work later on.

Regards,
Michael


[1]
https://codesearch.debian.net/perpackage-results/Loader%3Dpython/2/page_0
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #79 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: Michael Biebl <biebl@debian.org>

Cc: Iain Lane <laney@debian.org>, 806824@bugs.debian.org

Subject: Re: Bug#806824: (no subject)

Date: Fri, 11 Mar 2016 13:47:13 -0500

[Message part 1 (text/plain, inline)]

On Mar 11, 2016, at 04:16 PM, Michael Biebl wrote:

>first of all, would be great if you can block all bugs you filed by this
>one, so we can keep track of them more easily and the maintainers of
>those packages know that they should hold off until this particular bug
>report has been dealt with.

Good point; done.

>Looking at [1] I see a few packages missing on your list.

Isn't this a better search?

https://codesearch.debian.net/results/peas_engine_enable_loader/page_0

That returns the packages that actually call the function that potentially
loads one of the Python runtimes.   It does show the initial bug list missed
eog (python3), roger-router (python2), and entangle (python3).  I'll file bugs
for those too.

>Ok, this was misleading. I'll try to explain what I meant in more
>detail. Let's take liferea as an example, which currently uses python2.  You
>asked the maintainer to add an explicit dependency on
>libpeas-1.0-0-python2loader, but didn't really explain why.  The maintainer
>would need to know that he needs to scan all .plugin files for
>Loader=python[3] lines, and do that for every new upstream release.

I might be wrong, but I don't think that's the appropriate criteria.  As
described above, wouldn't the dependency have to be added to the package that
loads the python2 or python3 loader, not the individual plugins?
E.g. rhythmbox-plugin-alternative-toolbar doesn't load the loader, but it
depends on rhythmbox, so if the latter has the proper loader dependency, that
should be enough.

>It's highly likely, that liferea is ported to python3 at some point but this
>dependency is forgotten to be updated to libpeas-1.0-0-python3loader.

I think it's much less likely if the above analysis is correct.  Once liferea
is ported to Python 3, it will be obvious that liferea's libpeas loader
dependency will also need to be updated when all its other dependencies are
updated.

>So, I'm not generally against splitting out the loaders, but if we do
>so, I think we should automate the dependency generation via a dh_peas
>debhelper addon, which scans .plugin files and adds the correct
>dependency depending on what it finds.

Given the above analysis, I think that's probably overkill.

>The alternative I see, is to not split out the loaders, but get the
>remaining python2-using packages ported and then disable the python2 loader.

Sure, that would be great, but outside the scope of this bug ;).

[Message part 2 (application/pgp-signature, inline)]

Message #90 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Barry Warsaw <barry@debian.org>

Cc: Iain Lane <laney@debian.org>, 806824@bugs.debian.org

Subject: Re: Bug#806824: (no subject)

Date: Sun, 13 Mar 2016 00:29:17 +0100

[Message part 1 (text/plain, inline)]

Am 11.03.2016 um 19:47 schrieb Barry Warsaw:
> On Mar 11, 2016, at 04:16 PM, Michael Biebl wrote:
> 
>> first of all, would be great if you can block all bugs you filed by this
>> one, so we can keep track of them more easily and the maintainers of
>> those packages know that they should hold off until this particular bug
>> report has been dealt with.
> 
> Good point; done.

Thanks


>> The alternative I see, is to not split out the loaders, but get the
>> remaining python2-using packages ported and then disable the python2 loader.
> 
> Sure, that would be great, but outside the scope of this bug ;).

So, if I'm counting correctly, there are only 3 packages remaining that
use the python2 loader. Somehow I think the best course of action would
be to get those updated to python3.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #95 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: Michael Biebl <biebl@debian.org>

Cc: Iain Lane <laney@debian.org>, 806824@bugs.debian.org

Subject: Re: Bug#806824: (no subject)

Date: Mon, 14 Mar 2016 19:42:37 -0400

[Message part 1 (text/plain, inline)]

On Mar 13, 2016, at 12:29 AM, Michael Biebl wrote:

>So, if I'm counting correctly, there are only 3 packages remaining that
>use the python2 loader. Somehow I think the best course of action would
>be to get those updated to python3.

Perhaps, but isn't that an upstream decision?  Also, isn't it possible that
third parties might still have Python 2 plugins for applications outside of
the Debian archive?

-Barry

[Message part 2 (application/pgp-signature, inline)]

Message #100 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Emilio Pozuelo Monfort <pochu@debian.org>

To: Barry Warsaw <barry@debian.org>, 806824@bugs.debian.org, Michael Biebl <biebl@debian.org>

Cc: Iain Lane <laney@debian.org>

Subject: Re: Bug#806824: (no subject)

Date: Tue, 15 Mar 2016 11:17:39 +0100

On 15/03/16 00:42, Barry Warsaw wrote:
> On Mar 13, 2016, at 12:29 AM, Michael Biebl wrote:
>
>> So, if I'm counting correctly, there are only 3 packages remaining that
>> use the python2 loader. Somehow I think the best course of action would
>> be to get those updated to python3.
>
> Perhaps, but isn't that an upstream decision?

We can put some pressure on upstreams to switch to python3. Or disable plugins 
on those rdeps. Or get them out of Debian...

> Also, isn't it possible that
> third parties might still have Python 2 plugins for applications outside of
> the Debian archive?

Well, sure. But there may also be stuff out there that uses stuff that we have 
removed from the archive. That has never stopped us from making changes and 
moving forward, as long as our changes have been reasonable.

I also don't like the split, fwiw, and given the few py2 rdeps I think we should 
just fix those and drop the py2 loader.

Cheers,
Emilio

Message #105 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 806824@bugs.debian.org, Barry Warsaw <barry@debian.org>

Subject: Re: Bug#806824: libpeas python split

Date: Mon, 4 Apr 2016 01:52:14 +0200

[Message part 1 (text/plain, inline)]

Hi Barry,

On Mon, 14 Mar 2016 19:42:37 -0400 Barry Warsaw <barry@debian.org> wrote:
> On Mar 13, 2016, at 12:29 AM, Michael Biebl wrote:
> 
> >So, if I'm counting correctly, there are only 3 packages remaining that
> >use the python2 loader. Somehow I think the best course of action would
> >be to get those updated to python3.
> 
> Perhaps, but isn't that an upstream decision?  Also, isn't it possible that
> third parties might still have Python 2 plugins for applications outside of
> the Debian archive?

Andreas was suggesting a compromise.
Split out the python2 loader but keep the python3 loader within the main
libpeas-1.0-0 package. This will reduce the churn quite a but.

Both Emilio and myself are ok with that proposal, so we intend to
proceed with that plan.

This means we can close most of the bugs and and only need to keep the 3
python2 bugs open. We should follow up there and make it clear that they
should update to python3. They then can drop the explicit dependency on
the python2 loader package again.

I intend to work on the libpeas package the next couple of days.
One of the modfications I'd like to do, is move the python2 loader
package to oldlibs/extra and drop the soname specific part from the package.

I hope you can agree with this plan, if not, please shout.



Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #110 received at 806824@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

Cc: 806824@bugs.debian.org

Subject: Re: Bug#806824: libpeas python split

Date: Mon, 4 Apr 2016 09:59:16 -0400

[Message part 1 (text/plain, inline)]

Hi Michael,

On Apr 04, 2016, at 01:52 AM, Michael Biebl wrote:

>Andreas was suggesting a compromise.  Split out the python2 loader but keep
>the python3 loader within the main libpeas-1.0-0 package. This will reduce
>the churn quite a but.

I think I missed that, thanks for the clarification.

This solution works for me.  I'll note the one difference is that it will keep
a Python dependency even for libpeas clients that don't extend through Python
(crazy talk, I know! :).  But since it will be a Python *3* dependency and
Python 2 can be split off and demoted, that's okay by me.

>This means we can close most of the bugs and and only need to keep the 3
>python2 bugs open. We should follow up there and make it clear that they
>should update to python3. They then can drop the explicit dependency on
>the python2 loader package again.

+1

>I intend to work on the libpeas package the next couple of days.
>One of the modfications I'd like to do, is move the python2 loader
>package to oldlibs/extra and drop the soname specific part from the package.
>
>I hope you can agree with this plan, if not, please shout.

<sotto voce> I agree with the plan.  :)

Thanks!

[Message part 2 (application/pgp-signature, inline)]

Message #115 received at 806824-close@bugs.debian.org (full text, mbox, reply):

From: Andreas Henriksson <andreas@fatal.se>

To: 806824-close@bugs.debian.org

Subject: Bug#806824: fixed in libpeas 1.18.0-2

Date: Tue, 10 May 2016 14:00:54 +0000

Source: libpeas
Source-Version: 1.18.0-2

We believe that the bug you reported is fixed in the latest version of
libpeas, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 806824@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Henriksson <andreas@fatal.se> (supplier of updated libpeas package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 15 Apr 2016 10:17:52 +0200
Source: libpeas
Binary: libpeas-1.0-0 libpeas-1.0-python2loader libpeas-dev libpeas-doc libpeas-common gir1.2-peas-1.0
Architecture: source amd64 all
Version: 1.18.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Changed-By: Andreas Henriksson <andreas@fatal.se>
Description:
 gir1.2-peas-1.0 - Application plugin library (introspection files)
 libpeas-1.0-0 - Application plugin library
 libpeas-1.0-python2loader - Application plugin library (Python 2 support)
 libpeas-common - Application plugin library (common files)
 libpeas-dev - Application plugin library (development files)
 libpeas-doc - Application plugin library (documentation)
Closes: 806824
Changes:
 libpeas (1.18.0-2) unstable; urgency=medium
 .
   * Add Build-Depends-Package meta-tags to symbols file.
   * Split out python2 loader in a separate package (Closes: #806824)
   * Use --fail-missing when installing package files.
   * Bump Standards-Version to 3.9.8
Checksums-Sha1:
 3ddd7b906d183d3a34d304bd32df3c1c1fadbe21 2674 libpeas_1.18.0-2.dsc
 83c8ab85f661a84ca0ff37368219fb414843c622 8328 libpeas_1.18.0-2.debian.tar.xz
 7bd0b771e0bf37e19dc9831b29c6566de8bf207c 152366 gir1.2-peas-1.0_1.18.0-2_amd64.deb
 8961f18b2372f38ba251efcf3ae2e9dc4d124b4f 173850 libpeas-1.0-0-dbgsym_1.18.0-2_amd64.deb
 4e44352fa032c1e1882b6da8ab8c88021075f092 197686 libpeas-1.0-0_1.18.0-2_amd64.deb
 4eff244cf924e97fe18e71854008be74fbc1f167 24282 libpeas-1.0-python2loader-dbgsym_1.18.0-2_amd64.deb
 0e42a7c72a7193be1187bb5912d9479316919e20 158026 libpeas-1.0-python2loader_1.18.0-2_amd64.deb
 fbb6442c82b35b03d6bee4227a1410ebb549086a 193450 libpeas-common_1.18.0-2_all.deb
 6a06621f96fe1a3aad685c41eae59c2e42ab01ab 165410 libpeas-dev_1.18.0-2_amd64.deb
 4338aef976c8ad8d7772ec2f6e33fc29369e3f27 40952 libpeas-doc-dbgsym_1.18.0-2_amd64.deb
 a42087118bba6f5eb0ca4fb7d3af0e7e825b05f8 213092 libpeas-doc_1.18.0-2_amd64.deb
Checksums-Sha256:
 7ae67625e7220ad3705cfbad361ec20770922e2343064f4204b272b929156d53 2674 libpeas_1.18.0-2.dsc
 34abf209a96ce8083e6aa89e112383cb56ce4dcd1102b3d650a315e821b7c56e 8328 libpeas_1.18.0-2.debian.tar.xz
 ba55f3f674a69a6acf463f8e058c3198fe3dba8cd3b32f041bce472a492186ba 152366 gir1.2-peas-1.0_1.18.0-2_amd64.deb
 65143885e1ed2d8ad3964b3ccf1ccc52261390386a626003c5f62e4422cfbf8b 173850 libpeas-1.0-0-dbgsym_1.18.0-2_amd64.deb
 6e34024e2a8f960c4e00b31e2298a8e0387ecd459b068e95389add9cfeb4c088 197686 libpeas-1.0-0_1.18.0-2_amd64.deb
 4d5dc663abe95dfb44ec8137f0cf883f45700713667524b79ec6a497f00a9eff 24282 libpeas-1.0-python2loader-dbgsym_1.18.0-2_amd64.deb
 59da592fab6d2c2cf68981467c06981b9f6b793b5e7db717c4716ba8f6c5db8c 158026 libpeas-1.0-python2loader_1.18.0-2_amd64.deb
 ed503339ffb1123615096b7de873a51d5a73ead356736606ee04195276b849a3 193450 libpeas-common_1.18.0-2_all.deb
 027ac51a1cac569b8e3c8b2877f50ae2408eb26bede2ad4d2de13e5bebab0b7d 165410 libpeas-dev_1.18.0-2_amd64.deb
 de9e44e08cb71c95fdae736aa74a19d42c497618f2713385ad574faaabc03ddf 40952 libpeas-doc-dbgsym_1.18.0-2_amd64.deb
 6758deed36b807921054762d49e41926b33b58e68ed475824fd3482218ee759c 213092 libpeas-doc_1.18.0-2_amd64.deb
Files:
 f5a4f24cbe8a1fbd068ddd02680d7bf5 2674 libs extra libpeas_1.18.0-2.dsc
 fbe1ab516c7a654639ca7145b2afdb1b 8328 libs extra libpeas_1.18.0-2.debian.tar.xz
 4ab46bd72c81360c969a3be4b67c14d9 152366 introspection extra gir1.2-peas-1.0_1.18.0-2_amd64.deb
 65f266ba30129952a70869c0d18d2508 173850 debug extra libpeas-1.0-0-dbgsym_1.18.0-2_amd64.deb
 9201ade812e6a2979860bb4e620a9404 197686 libs extra libpeas-1.0-0_1.18.0-2_amd64.deb
 11fd5dcae6f4b9e7423452558724b484 24282 debug extra libpeas-1.0-python2loader-dbgsym_1.18.0-2_amd64.deb
 83aff9edebcb4b97bce627dace059112 158026 oldlibs extra libpeas-1.0-python2loader_1.18.0-2_amd64.deb
 2a4e4fc575f276776807f89c13783ea8 193450 libs extra libpeas-common_1.18.0-2_all.deb
 bbd22061a4ade7fa4dbcaa8b01385d7f 165410 libdevel extra libpeas-dev_1.18.0-2_amd64.deb
 bbf724ee57a55e9dabc947ea9b0e3609 40952 debug extra libpeas-doc-dbgsym_1.18.0-2_amd64.deb
 45aa8104d10bf5f57c14a6f36ef369c5 213092 doc extra libpeas-doc_1.18.0-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJXENZeAAoJEAvEfcZNE1MGU5oP/iWWwTBc+iJr0hJ4yHPC8j1V
FjXLNyI0U1XUuBRU594U0ktCmUtBlYIFC3XdOXOOjt6ONBYWm9OWYxPMDWYZLxKu
NzqmLhLGSNLviLSD32YAV5ticImEqsMWpovRqI15ciCFygtNobn0GShxjxRFrdhH
PD58KOp2IN+8RkKi/nfJ0PiW+GkbWUywrWCXDpRyFroi5SVb4zMXAdXBpJ+bLqI/
IZ32VJtG91sKB+B9xhWyU0+BzrPyFaBedCY9546k00KsTmItDP8W2ddTSphaJlYm
ap1hWtiksPf/bmpOq+Uktb+BIBntLSZXgUtFSi+keWcGpb+UaO0cYXqc+qXcbaCz
aL3oUqhGgun5PJG7SKL58Pnu4/SE3axo7Sp//KWhALk9tRCBYCXIJVBvC0EWh4Rx
W8PXdMTSiXTKmLfkkXRQPqMkoLtEKBSTkevB6MV7za8x/sIjVfJV9DoeJQuxIvL8
teLlvYx7/GB4+rrGTjiEDKp2EFPW5msHZxjdT1TGWbLRiOukSi48+fh6DQyaAsww
U4DjUskhBopTFBmGgnowXIHsMe+cm6AXwulRz2WFlgu/d9+cN/pmor+GXPftgUSB
ZMOnAOs/FX2d00JaRjc+Kzxgy1BR/sj0nqfb6iYuTc+ZJWEVJXDYgkMpzpSvEi7m
7M8Gsc4J2XtI/zKEAfqA
=60Xa
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.