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, >> >>> 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 no changes necessary for roger-router alongside. >>> In fact, roger-router in Ubuntu still depends on libpeas-1.0.0 and not >>> libpeas-1.0-0-python2loader even though the package does exist there. >> We should certainly fix roger-router in Ubuntu; I'm not sure how I missed >> that >> one over there. I'll file a bug and fix that early next week. > Ubuntu is still unchanged both in Xenial and Yakkety. > > The title of this ticket suggests I should add an explicit dependency on > libpeas-1.0-0-python2loader to Depends. I'm a bit reluctant to do that > since it would mean I need to maintain a fork since my main computer is > trusty. In any case, roger does not ship any python code at all. My > understanding is that it uses peas to allow third party plugins and > those could be written in python or other programming languages. I'm > actually not aware of any plugins and they could be written in either > python 2 or python 3. Adding a strong dependency to the python 2 loader > seems wrong to me. I feel like adding a Suggests for > "libpeas-1.0-0-python2loader|libpeas-1.0-0-python3loader" would be more > appropriate. Or should I be mistaken? If it really needs to be a > Depends wouldn't it be better to have debhelper and dh_shlibs take care > of doing the right thing?
After further inspection of the peas packages in testing and unstable I have now learned that the new libpeas-1.0-0 includes what I thought was going to be carved out into libpeas-1.0-0-python3loader. Barry, I think that adding "libpeas-1.0-python2loader | libpeas-1.0-0 (<< 1.16.0-1ubuntu1)" to Depends for libroutermanager0 (all other roger binary packages depend on this one directly or indirectly) would fix this ticket as well as allow me to build from the same code base for trusty. Seeing that libpeas-1.0-0-python3loader was indeed added to Xenial (and Yakkety, so far, for that matter), 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. This assumes that Ubuntu will later during the Yakkety cycle go back to syncing libpeas from unstable and thus drop libpeas-1.0-python3loader. It would be appreciated if you confirmed this change for roger.
