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

Bug#902836: RFS: slick-greeter/1.2.2-1



Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "slick-greeter"

 * Package name    : slick-greeter
   Version         : 1.2.2-1
  Upstream Author :  Clement Lefebvre <root@linuxmint.com>
 * URL             : https://github.com/linuxmint/slick-greeter/
 * License         : GPL-3+
  Section         : x11

  It builds those binary packages:

    slick-greeter - Slick-looking LightDM greeter

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/slick-greeter


  Alternatively, one can download the package with dget using this command:

    dget -x https://mentors.debian.net/debian/pool/main/s/slick-greeter/slick-greeter_1.2.2-1.dsc

Notes:
Tested by building on an up-to-date buster and installing the built .deb

check-all-the-things has been run on the source
lintian -i -I --pedantic run on the built changes files. It is lintian free
with the exception of the
following information/pedantic issues;

testsuite-autopkgtest-missing - I don't believe a autopkgtest is
required for a greeter

no-upstream-changelog - upstream does not supply a changelog so I have
summarised the changes in the debian/changelog

debian-watch-does-not-check-gpg-signature - upstream do not sign their
release tarballs

pbuilder-dist unstable build has been run successfully

May I request that this package be added to my debian maintainers
list of packages I'm allowed to look after (dak
fossfreedom@ubuntu.com) ?

  Changes since the last upload:

   * New upstream release
    - Latest translations
    - Fix HiDPI detection
    - Add option to display to specific monitor (only-on-monitor)
  * Packaging Changes:
    - Drop patch mint-master-unstable-19.patch since it is now
      included in the new release
    - debian/control bump StandardsVersion - no changes required


  Regards,
   David Mohammed


Reply to: