Comment 3 for bug 678283

Hello,
yes, the Ubuntu package exists since before the Debian one. I must've missed it
when I originally packaged pyproj in Debian. I gave a look at the Ubuntu package,
and it seems there are no fixes to backport to Debian.

1.8.6-0ubuntu1 has two patches, which are useless in the Debian package. In fact,
I'm using data from the "proj-data" binary, instead of the embedded copies (which in
Ubuntu are shipped in python-pyproj-data). I'd say this is a good thing (but I'm the
maintainer, so I'm biased :)).

I checked in Natty, and the only rdepend of python-pyproj-data is python-pyproj itself.
So here's the plan:

- I upload a 1.8.8-2 version to Debian/experimental, with the Ubuntu changelog merged
- remove "pyproj" source package from Ubuntu
- upload "python-pyproj" source package as NEW to Ubuntu.

I don't see the need for particular upgrade paths. python-pyproj-data would be removed
because not-built-from-source (at least, in Debian it would be so, I hope here it's more or
less the same), and users will have proj-data pulled in by "my" python-pyproj package.

Also, there's no conflict between proj-data and python-pyproj-data -- the first puts data in
/usr/share/proj/, while the latter in /usr/share/pyproj/data. I could just add a Conflicts to my
1.8.8-2 to force removal of python-pyproj-data.

What do you think?
David