[Pkg-corba-devel] [omniORB] Preparing an upload for 4.1.5

[Floris Bruynooghe]

On 21 March 2011 15:51, Thomas Girard <thomas.g.girard at free.fr> wrote:
> Hello Floris,
>
> I made some trivial changes to omniORB today. Do you feel like it's
> ready for upload?

On Friday I was trying to get use dh_python2 instead of dh_pycentral
but that appeared non-trivial due to the "current" keyword
disappearing for X-Python-Version.  I had some discussions on the
#debian-python IRC channel and it's not entirely clear what the right
thing to do is.

But I have a hack which appears to work fine superficially and
strangely did not result in cries of horror: use "dh_python2 -V
$(pyversions -dv) -pomniidl".  Although I am not sure how good this is
as someone will have to notice when a python version changes and
schedule a bin-NMU (just like before, but at least there was the
"current" keyword which was used in the control file to detect these
cases).  Furthermore this either leaves X-P-V unset, i.e. wrongly
declares all supported, or fixes it to the current default which is
2.6 - but then it needs an entire new upload for a python upgrade.
Hence I don't like this hack very much.

I was told that we should be really shipping the omniidl modules in
/usr/share/omniidl/ and patch /usr/bin/omniidl so that this ends up on
python's sys.path.  In principle I agree that this is better style,
however I've never seen much harm in following the way upstream works.
 Somehow Piotr Ożarowski seemed to think this alone would be
sufficient to make dh_python2 happy, and presumably fix the python
upgrade issue, but I don't know how so am dubious before having tried
this out in detail.

Lastly if we start using /usr/share/omnidl then we need to coordinate
this with the omniidl-python package.  This either means patching
omniidl to look in both dist-packages and /usr/share/omniidl for the
python backend or forcing the upgrade together with a conflicts with
earlier omniidl-python packages.  The latter complicating upgrades.


So to summarise: I'd like to experiment some more with using
/usr/share/omniidl and dh_python2 to see if this would solve or ease
the upgrading-python problems.  If so this will have to be coordinated
with a new upload of python-omnorb.

However if you are in a hurry there are a few thing we could try which
are simpler:
* Just keep using dh_pycentral for now
* Keep using the "XS-Python-Version: current" header, dh_python2 still
accepts this but deprecates it (haven't tried this).
* Use no X-V-P header (or XS-P-V) and use the "-V `pyversions -dv`" hack


Regards
Floris


-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org