Hi Well the package still provides a binary without the source which breaks the DFSG. I prepared a patch which is a NMU (I attached the URL below). I repacked the existing fruit_2.1.orig.tar.gz to fruit_2.1.0.1dfsg.orig.tar.gz . I saw that upstream only uses the first two digits for the version number so there should never be a problem with a newer upstream release, but just to make sure i chose to append a 0.1 if upstream changes his mind :) I used the same packaging.
My changelog entry looks like:
fruit (2.1.0.1dfsg-0.1) unstable; urgency=low
* Non-maintainer upload
* The package provided a binary without source, which broke the DFSG
I had to repack the old orig.tar.gz and bumped the version number to
2.1.0.1dfsg. Upstream only uses the first two digits so there
should never be a versioning problem. (Closes: #350033)
-- Steffen Joeris <[EMAIL PROTECTED]> Sat, 29 Apr 2006 16:12:42
+0200
Greetings
Steffen
You can find the NMU under
http://developer.skolelinux.org/~white/debs/nmu/fruit/
pgp2jg3HVkOCs.pgp
Description: PGP signature
