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

Bug#883662: RFS: agenda.app/0.44-1



Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "agenda.app".

 * Package name    : agenda.app
   Version         : 0.44-1
   Upstream Author : Philippe Roussel <p.o.roussel@free.fr>
 * URL             : https://github.com/poroussel/simpleagenda
 * License         : GPL-2+
   Section         : gnustep

It builds this binary package:

  agenda.app - Calendar manager for GNUstep

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

  https://mentors.debian.net/package/agenda.app

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

  dget -x https://mentors.debian.net/debian/pool/main/a/agenda.app/agenda.app_0.44-1.dsc

Or clone the Git repository:

  git clone https://anonscm.debian.org/git/pkg-gnustep/agenda.app.git

Changes since the last upload:

  * New upstream release.
  * debian/compat: Set to 10.
  * debian/control (Build-Depends): Require debhelper >= 10 and
    gnustep-make >= 2.7.0-3 for recent config.mk.  Add libdbuskit-dev for
    desktop notifications; drop dpkg-dev (obsolete) and imagemagick (not
    needed anymore as support for Debian menu is removed).
    (Depends): Remove ${gnustep:Depends}; obsolete.
    (Homepage): Replace with the new one at GitHub.
    (Vcs-Git, Vcs-Browser): Use canonical/secure URIs.
    (Standards-Version): Compliant with 4.1.2 as of this release.
  * debian/rules: Update for modern dh.
  * debian/install:
  * debian/docs:
  * debian/manpages: New files.
  * debian/menu: Delete.
  * debian/watch: Upgrade to version 4; use new upstream location.
  * debian/SimpleAgenda.desktop: Add Keywords field.
  * debian/patches/spelling-fix.patch: New, fix trivial spelling error.
  * debian/patches/series: New file.
  * debian/copyright: Switch to format 1.0; update Source field and
    copyright years.

P.S. The package doesn't pass the piuparts test due to #832349.


Reply to: