Folks, the Debian Jessie freeze is coming up quickly. I do not think the
question of ownership of the package are productive at this point.
3.2 seems to be upstream's stable release at this point. It would seem
like a bad idea to ship Jessie with 2.x, but if that's all we can
manage, let's do it.
Hamish, you seemed to be saying that the FTP masters rejected a previous
version of the package: what was the reason? Sharing this here will save
everyone (and especially the FTP masters) a lot of time. You were also
mentionning issues about the package mentionned in the "last post in the
ITP", which I assume you mean:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538067#159
I think the major issue that Andreas mentionned there is the
"DFSG-tarball" generation: the script should be in the debian/ directory
so the source can be regenerated easily without requiring access the SVN
repo. The script I could find is this:
http://anonscm.debian.org/viewvc/pkg-grass/packages/opencpn/tarballs/get_latest_from_git.sh?view=co&revision=HEAD&content-type=text%2Fplain
.. but that script seems to generate a tarball based on the git
repository, and doesn't seem to checkout any specific tag, so I doubt it
will work unmodified.
There were also issues with the debian/rules targets for repeated
builds.
Andreas, was there other things you were thinking should be fixed with
the package?
Finally, did anyone take a look at that PPA? Why aren't we just using
that debian package??
https://launchpad.net/~opencpn/+archive/ubuntu/opencpn
Thanks for the feedback,
A.
--
That's one of the remarkable things about life: it's never so bad that
it can't get worse.
- Calvin
Attachment:
pgpho_c0UjH6v.pgp
Description: PGP signature