Cristian Greco schrieb:
On Mon, Aug 31, 2009 at 11:59:11PM +0200, Cristian Greco wrote:
On Mon, Aug 31, 2009 at 07:51:36PM +0200, Patrick Matthäi wrote:
You should:
1) Create a dfsg tarball and remove the file from the tarball
2) Depend on geoip-database and symlink this file against:
/usr/share/GeoIP/GeoIP.dat
So I'm tagging this bug as fixed-upstream, and my intention is to actually try
to backport the upstream svn patch to the latest stable release (1.1.9) instead
of just having to wait for the new release to come.
It seems I have a small patch which enables deluge 1.1.9 to use a geoip
database from a system wide installation path.
I'm planning to upload a new package revision including this patch and deleting
the database from the deluge-core binary package. But I'd like to avoid
repackaging the source tarball as it is already repackaged (1.1.9+dfsg) and
this would mean breaking the version history with an epoch bump, I thought.
I hope this can be avoided, given the upstream awareness of the problem and the
upcoming fixed release 1.2.
Of course, I'm not going to close this bug until it would be "properly" fixed.
Would this be acceptable?
Yes sure.
Sorry I was a bit fast with it ;-)
Then the main problem is now "only" that it does not use a system wide
one and that the geoip.dat you ship is not buildable from source.
Much thanks for your answers and engagement. :)
Cheers.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
