[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: I'm looking for sponsor(s) to add my SourceForge packages to Debian



I'm editing this in Icedove - sometimes it gets the insert point wrong, so words are joined when
they shouldn't be - and not the way I see them.

Please bear with me should this happen below.

On 12/12/11 12:52, Arno Töll wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Philip

On 12.12.2011 13:03, Philip Ashmore wrote:
Where (which URL) is the source package for the version you want
sponsored into Debian? That's what needs to be examined and discussed
here.

v3c: http://sourceforge.net/projects/v3c/files/v3c-2.3.0-01.tar.gz/download
Just uploaded.
... but this is still not a final Debian package. If you really meant to
ask someone to package your software for Debian you should be filing a
RFP (request for package) bug against the wnpp pseudo-package instead.
Since RFP requests more or less never work you perhaps want to package
it yourself. When doing so, you should be filing an ITP (intend to
package) bug instead and familiarize yourself with our rules and
procedures like policy [1] and New Maintainer's Guide [2]

As people pointed out: A Debian package we are used to sponsor here
consists of a full source package which is quite different than a source
tarball.
If you run "make debian" then in the build directory you will find (among other files):
v3c_2.3.0-01-1_amd64.changes
v3c_2.3.0-01-1_amd64.deb
v3c_2.3.0-01-1.dsc
v3c_2.3.0-01-1.tar.gz
v3c-2.3.0_01.orig.tar.gz
v3c-2.3.0-01.tar.gz
v3c-dbg_2.3.0-01-1_all.deb
v3c-dev_2.3.0-01-1_amd64.deb
v3c-doc_2.3.0-01-1_all.deb

Please let me know which of these constitutes a "full source package".
As a random note: While skipping through your v3c package I noticed you
are producing a Debian package from a semi-static template like

<snip>
Maintainer: @PACKAGE_AUTHOR@<@PACKAGE_EMAIL@>
Build-Depends: debhelper (>= 7), @DEBIAN_REQUIRES@
Standards-Version: 3.7.3
Section: unknown
</snip>

That's of course not meeting our quality standard as is.
What changes do I need to make to the above so that it meets Debians quality standards?
The links below don't tell me what you mean.
[1] http://www.debian.org/doc/debian-policy/
[2] http://www.debian.org/doc/maint-guide/

- -- with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJO5fkJAAoJEMcrUe6dgPNtDkcQAKmsTigm+wrYZ8JDU2uZjaQN
mPiRN5ds2eOlOVhHCbS7TAUozWs+wmsCNl9z7OpHa3e/KqJQguCi9E/OoRmR0Rt8
JonXGaCO3UO8l2U3aW1csFl8n/ienPv3CjicOK/7l2WtOaz7M7v+c+3hTIh6P7Xt
KJLGX7FEVoQbLrzHeCKsIQPouCZcokSUMNltdqBVNLMIdrVAc4qMpKGiYEp0+w2B
AUhO1G8HwMfpky4wvUZElRH8V2bGL2KjfVYdhPXDZUixY3WHXcpG6JKsJJlamHQK
O60SZEUgQoKVCZtBXHB+g4gTEus+bP3VPLdUWmyrpxy674Bvqa0tAyz3vzjT+VTc
o9aBsWbo//4PxXp7WH+rDJmPAoOqxyTBGqJg9u9ZIo/P+RJyHxIC3MY1A8kiATDk
jMUvqdCSs0OKKtQG+ZijwgBDb8PUL6YH3CtdMrgj0F7PPv4cDQdUGn5+67q5uxxX
ES7AirQxyzK7ppKEp1hCsy3uRyLBx33gsJynJUSY2cFlW1kXf8CRS3IakhmqVlDW
WuCTTCvAXwkGFjM4bRw7bDzMwT5qCdvUfDLKkrkSarjNB9LvuZ40/1yC+O/3afkv
tTbG7NmfEGSTru9bcvGfLyBMiChi6mHCEs2Ds5NFxqLoNyvdBaMmMk3HOWZRYpti
odZYR3VW3tli5apWbJla
=D2ad
-----END PGP SIGNATURE-----




Reply to: