python-support has been deprecated and should be replaced with dh_python2

Bug #979694 reported by Philip Peitsch on 2012-04-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gpoweroff
Undecided
Unassigned

Bug Description

As per comments at https://bugs.launchpad.net/gpoweroff/+bug/973577/comments/3

Hey, it seems python-support is deprecated since Ubuntu 11.10 (but still supported even in Ubuntu 12.04), see

http://www.rowinggolfer.org/tutorials/packaging/dh_python2_tutorial.html
http://wiki.debian.org/Python/TransitionToDHPython2

I think we could still use python-support for packaging for few months, maybe until Ubuntu 12.10, but in future we should use dh_python2, as recommends Ubuntu and Debian developers.

Related branches

Changed in gpoweroff:
status: New → In Progress
Changed in gpoweroff:
status: In Progress → Fix Committed
Mantas Kriaučiūnas (mantas) wrote :

I think it would be better to use python-support for packaging for few months, maybe until Ubuntu 12.10, because dh_python2 doesn't work in Ubuntu 10.04 LTS and older. In future we should use dh_python2, as recommends Ubuntu and Debian developers, but not now, because it is simpler to use the same code for all supported Ubuntu releases.

If you like to use separate packaging code (debian folder) for Ubuntu 10.04 and older releases then please don't create separate branch of whole gpoweroff code, it's better to have just separate "packaging" branch only for debian folder and use "merge packaging" or "nest packaging" instructions in lucid recipe.

Philip Peitsch (philip-peitsch) wrote :

The changeover has to happen sooner or later and no matter when the switch-over happens, some releases are going to be left out in the cold.

The recipe suggestion sounds like a decent alternative though, I'll look into that. Thanks again for all the pointers... I haven't had a lot of time for a while to keep on top of all the changes in Ubuntu's corner of the world.

Philip Peitsch (philip-peitsch) wrote :

Hmm... this is taking longer than I'd hoped.

It appears the merging & nesting only functions if the base source does not contain a debian folder, in spite of what the docs appear to say. As soon as both the base branch and the merged/nesting branch have the debian folder, the build recipes throw their hands up and claim it's all a conflict, irrespective of whether the history is shared or not.

I'll leave this for tonight and come back and wrestle with it tomorrow. If you know how to create a proper packaging branch, feel free to get one setup and I'll check it out. Otherwise I will ponder more seriously reverting the move to dh_python2 until some magical time in the future when I can be bothered again :)

Hi Philip,

It seems you simply forgot to request new build after you uploaded revision 85
to lp:~gpoweroff/gpoweroff/lucid

I've just builded new lucid build without any problems with your recipe:

https://code.launchpad.net/~gpoweroff/+recipe/gpoweroff-lucid

As you see, merging works fine now :) Conflict was before, because in both
branches the same line in debian/control file was changed after branch split,
but now you changed this line only in one branch - lp:~gpoweroff/gpoweroff/lucid

Btw, could you set automatic translation export to main lp:gpoweroff branch?

Simply type gpoweroff here:
https://translations.launchpad.net/gpoweroff/trunk/+link-translations-branch

I can't set this because you are the owner of main lp:gpoweroff branch

On Thu, Apr 12, 2012 at 02:50:23PM -0000, Philip Peitsch wrote:
> It appears the merging & nesting only functions if the base source does
> not contain a debian folder, in spite of what the docs appear to say.
> As soon as both the base branch and the merged/nesting branch have the
> debian folder, the build recipes throw their hands up and claim it's all
> a conflict, irrespective of whether the history is shared or not.
>
> I'll leave this for tonight and come back and wrestle with it tomorrow.
> If you know how to create a proper packaging branch, feel free to get
> one setup and I'll check it out. Otherwise I will ponder more seriously
> reverting the move to dh_python2 until some magical time in the future
> when I can be bothered again :)
>
> --
> https://bugs.launchpad.net/bugs/979694
> python-support has been deprecated and should be replaced with
> dh_python2

--
Labanaktis/Good luck,
Mantas Kriaučiūnas Jabber ID: <email address hidden> GPG ID: 43535BD5
Public organization "Open Source for Lithuania" - www.akl.lt
Geriausios biuro programos verslui ir namams - http://openoffice.lt
Prekyba naujais ir atnaujintais kompiuteriais su Linux OS - http://tinklas.eu
Naudok Baltix GNU/Linux sistemą savo kompiuteryje - http://baltix.lt

Philip Peitsch (philip-peitsch) wrote :

Hi Mantas,

Indeed they appear to be green again. Not sure what was going on locally on my machine :(

I've turned on automatic translation snapshots as suggested. I also changed the main lp:gpoweroff trunk to be under control of gpoweroff developers just in cease you do want/require more direct involvement :)

Changed in gpoweroff:
milestone: none → 12.04
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers