Bug#790104: RFS: lightdm-gtk-greeter-settings/1.2.0-1 [ITP]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "lightdm-gtk-greeter-settings".
* Package name : lightdm-gtk-greeter-settings
Version : 1.2.0-1
Upstream Author : Andrew P. <pan.pav.7c5@gmail.com>
* URL : http://launchpad.net/lightdm-gtk-greeter-settings
* License : GPLv3
Section : utils
It builds those binary packages:
lightdm-gtk-greeter-settings - Settings editor for LightDM Gtk+ Greeter
To access further information about this package, please visit the following URL:
http://mentors.debian.net/package/lightdm-gtk-greeter-settings
Alternatively, one can download the package with dget using this command:
dget -x http://mentors.debian.net/debian/pool/main/l/lightdm-gtk-greeter-settings/lightdm-gtk-greeter-settings_1.2.0-1.dsc
More information about lightdm-gtk-greeter-settings can be obtained from http://launchpad.net/lightdm-gtk-greeter-settings.
Changes since the last upload:
lightdm-gtk-greeter-settings (1.2.0-1) unstable; urgency=medium
* Initial Debian release, imported from Ubuntu. (Closes: #788614)
* debian/ folder changes:
- Add a watch file pointing to Launchpad.
- Write a manpage (lightdm-gtk-greeter-settings.1), dropping
the binary-without-manpage lintian override
for /usr/bin/lightdm-gtk-greeter-settings.
- Add a get-orig-source target for debian/rules.
- Set myself as maintainer.
- Set package source/format to 3.0 quilt.
- debian/links: symlink the root NEWS file as an upstream changelog.
This fixes the no-upstream-changelog Lintian pedantic warning.
- debian/rules: override dh_auto_clean to remove
po/lightdm-gtk-greeter-settings.pot, so that successive builds work.
Regards,
James Lu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJVji2rAAoJEC7D9g3nHAudJNQP/0JxcBJ2ZB2rnGNE/O5RYf/J
VhLVyu2V1RjOrCaMdNntha5dYR/gLM7zocD6w4227GpKQmZzPrrZtPEWvPZgj5Bp
kSLztlsBoSds0t9NE/T2S5ol/3IcTowVSkacWWL0ohV0fFc/YjaSan83tbLwX9My
E4o+6Qp57S1qCsA5NJ5Knaem3NWM3iZHeIvFFTTsnv//uAo4Mc27FgXtv+ePuj4u
cKTEqJi4neikKoyvHGFuYAZYQaQFeMqAdOhm1mxO8dhr6jwf9Be7n9BIvx2q4261
vSfbaUyg+CJDyPRluMakUHOekMik1d2JGTMMzcOdEmtBLa0uWxx2kgbDso498UZ3
DcKYIQ3JohYj92A7XicrNTkRt+agnjDYJMW/7UdbfrBXWRFVqUVZfUXPhri+wn6u
61MPwfXjBFBUDKm14I66+nJKa2wTPqMRT03y+TVTe4V3cV/FGGNMMLFARykyapbT
AmUIn9gTGNfOvYFu+PzWndoj3ljbxeCZlFT6IhXvYEwEEy2uaYnCcorR9Wh6i8e+
VIn0rO4ZVcyX9++Rex6BqIIPOdvYhNSRKsGwY14pziTz6HLBQwzb7EZs0KbWKYRS
PUmKUtuDMadGIui2CFMvTTXRv2INKP+9YMMwJqfPPaecmW5Iv/LCzUmO1lBTz07M
L+d+6DpQffdxA9KUY+cI
=V+aq
-----END PGP SIGNATURE-----
Reply to: