Bug#790391: RFS: bomberclone/0.11.9-5 ITA
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "bomberclone"
* Package name : bomberclone
Version : 0.11.9-5
Upstream Author : Steffen Pohle <steffen@bomberclone.de>
* URL : http://bomberclone.de/
* License : GPL-2
Section : games
It builds those binary packages:
bomberclone - free Bomberman clone
bomberclone-data - Data files for bomberclone game
To access further information about this package, please visit the
following URL:
http://mentors.debian.net/package/bomberclone
Alternatively, one can download the package with dget using this
command:
dget -x
http://mentors.debian.net/debian/pool/main/b/bomberclone/bomberclone_0.1
1.9-5.dsc
Changes since the last upload:
bomberclone (0.11.9-5) unstable; urgency=medium
* New maintainer, mutually agreement (Closes: #790143)
* Switch to dpkg-source 3.0 (quilt) format
* d/patches/*: added description for existing patches
* d/control: migrated from cdbs to dh9
* d/control: extended bomberclone-data description
* d/control: Standards-Version 3.9.6: no changes required
* d/control: Added Vcs-* references
* d/copyright: updated to DEP-5 machine readable copyright format
* Added patch for gcc5 support (Closes: #777803)
* d/bomberclone.desktop: added categories (Closes: #737833)
-- Peter Spiess-Knafl <dev@spiessknafl.at> Sun, 28 Jun 2015 21:29:44
+0200
The package still has some lintian warnings which I would like to fix,
but don't know how:
- - deprecated-configure-filename
- - hardening-no-fortify-functions
Can someone help me with that? I thought that dh9 automatically takes
care of the hardening?
Additionally I would like to mention, that I got approved for DM, so
after the first few successful uploads a potential sponsor could grant
me upload rights for bomberclone.
Thank you in advance and Regards,
Peter Spiess-Knafl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJVkE+SAAoJED/ImGelQYVWC3sQAK7lIcjyuUnVIGCtAtGJMMKb
ldw1Z0h5Qr3WSdbRdyRSzzd+SjYcRgTaz/h8z0mRpR3+cKlGemmeOej4CbtPs121
rpJMqhLgCNNBcDhS1HW6/aiM9R17VF5NmTmHETQzYqXUJ1ACkLrEaBJQGPX2jPaA
PkV7CXENHtjUwhnSxzq2vlOpMQCHWlKmXqonT/xfq833X5eJkirHg9YH2dx0czfp
7Ds7GNbdx991iYLBx9hznGkILvAGwE2uGzX86obK2EctCtHwl9zBKzITI82+X/AI
2U9h8zXzajJJLLqotqQglFSItHawXYCzBropV4GlyHai27Oc1XRCBZ6VFjwd76gk
YiDf9yitOHRBuuwsaBGjnLRCkNWg/H2KL1AsaqQl0Z7MX+BCI6ZINdG6lvqr740H
Ko1Cs8JnuhNJCZ9VssNA9oOHNVPc7ocEji7IYZoMV05wrQ5V/Ob6noDFv5XoG78a
p4ur68ys5Q/1GZUx8uSx6RVUwhP3xyTiaQBFoFeUHhBypsKlSiwGWZ70px4PJvi1
YObYF0z7v42UPKm3pUQcTvzToW3NmKTDyQ6SbBMpZeJFh52cqRfMJFevd1/oM6A+
UNhVkDKHA3+DtKgpx/mbQHauY+0PYRMIbt5HvED5SrQsCkY6XjAtJx4juUqCg/yb
/ky77hJBD7Tm5gu/u5wY
=MzCF
-----END PGP SIGNATURE-----
Reply to: