Re: ITS: triggerhappy
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 2011-05-11 00:08, Stefan Tomanek wrote:
> Dies schrieb Niels Thykier (niels@thykier.net):
>
>> To say "GPLv3" or "GPLv3 or any later"? (I did not check the tarball for
>> the reasons listed below)
>
> "or any later version", so every licence statement should be the same.
>
>> I tried to re-fetch your package, but dpkg-source refuses to unpack it
>> because the tarball has a different size than what is expected(/written
>> in the .dsc). Not sure what happened, but according to the directory
>> listing on mentors.debian.net[1], the orig.tar.gz is from March and the
>> dsc is from today.
>> Perhaps, you have to remove the package from mentors and re-upload it
>> again?
>
> I just did that, it should be working now.
>
>
Uploaded; thanks for your contribution to Debian. Since the package is
new, it will end up in the NEW queue. Here it will wait for the
FTP-masters to give it a second review.
You may want to consider making a separate upstream changelog for the
next version. There some of the entries in the current debian changelog
that I am somewhat conflicted about.
An example would be 0.1.4-1: "Minor modifications for better code
safety". I do not see how that (directly) affects the user of the
package; but that particular line could be added to an upstream changelog.
You might also want to "attach" relevant upstream changes to "New
upstream release" bullet, like:
triggerhappy (0.1.4-1) unstable; urgency=low
* New upstream release
- Support for new --clear command line
- etc.
* fix "Provides" in init script
* etc.
-- Stefan Tomanek [...]
There is a "Best Practices for (Debian) changelogs" in the Developer's
Reference[1] that might be a good read.
~Niels
[1]
http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-debian-changelog
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCAAGBQJNykeTAAoJEAVLu599gGRCjHIP/j4P7cgAgyMiuP1nmt2ocUa3
kzS44F/6zg825txUb4T9ZL2dMTYT7MAaCZCDCRxuDyJyFs++m4K5jXpu21Zrl7v9
TRsPjQ46HI5/cGYSEdG/IAUvqA6Wu0SVh4tkxa4GKO/8WthTFpGoq94MsnRph72n
PQElziVcfk0aPX7r+iJbT1WMmACYO6YDthpZkOCJCxeFuH+TtKlrdTsqIk6/oK3O
5zl59/qypOvYbnnHpREmaXMD8gx9yZ93K7TOcNiClk3dCnme4qM1uBpn8fLhNoMG
zmQAdxWjfwjYEh5KSSWLkxnEsoMxBAGEsw2wayNCzooU4jZPHmVMMtUjy5RRYPfL
fGuyCSBHJFh9kLOZHXdHml3S+xAB+3J+JeWsNMTiu3Twm2rrlRiBcBlhF+cd/zXi
eqQoD1VAfXFuGxhuvpyjA79nQ0MWCPIFva35kDonkeYfVVBV5coiEe9a7/GbVXQ8
ABXgeRKVmKBW9yQoD/6sBzWtCEvV+qyeY9GmFAyKU9MBQ4rOTYDY5xp9WTgu7Rqn
mQ9Gc2kCCV3Z1j99PylmzTApPZaFBHnkNKxHpXqBFSrUxctnrsFuNw4zWwaHO5iT
Ys+e/Gv9dcyOQuBn5I//iY/Abqhec9QN1H/ej62cvdQluZrRJCq1ajqpXBazd4BY
UJMcoCh9X7utLwCefBp2
=mogI
-----END PGP SIGNATURE-----
Reply to: