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

Bug#1012200: RFS: rush/2.2+dfsg-1.0 [NMU] -- restricted user shell



Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "rush":

 * Package name    : rush
   Version         : 2.2+dfsg-1.0
   Upstream Author : Sergey Poznyakoff <gray@gnu.org.ua>
 * URL             : http://puszcza.gnu.org.ua/software/rush/
 * License         : custom-gettext, custom-X, GPL-3+, GPL-2+
 * Vcs             : https://salsa.debian.org/vimerbf-guest/rush
   Section         : shells

The source builds the following binary packages:

  rush - restricted user shell

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

  https://mentors.debian.net/package/rush/

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

  dget -x https://mentors.debian.net/debian/pool/main/r/rush/rush_2.2+dfsg-1.0.dsc

Changes since the last upload:

 rush (2.2+dfsg-1.0) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release (Closes: #1001091)
   * fix rush FTCBFS (Closes: #929160)
   * Update Standards-Version to 4.6.1
   * drop debian/patches/intprops.patch
   * drop debian/patches/manpages.diff
   * Add vcs-* in d/control
   * introducing the git gbp packaging

----------------------
I have to explains more here[0]:
TL;DR. The rush package need to be updated that is reported by user. But
the maintainer of the package does not want to contineue maintain it .
But there is some procedural process to unclear. I think the NMU-upload is simple
to deal with it. this is my the first to NMU upload.

PS: Personlly I like to upload it as NMU. But if there is some tortuous
to do that, maintaining it by myself is ok also.


[0] https://lists.debian.org/debian-mentors/2022/03/msg00050.html
Regards,
--
  Bo YU

Attachment: signature.asc
Description: PGP signature


Reply to: