Your message dated Sat, 18 Jun 2022 09:05:58 +0200
with message-id <[email protected]>
and subject line Re: Bug#1012200: RFS: rush/2.2+dfsg-1 [ITA] -- restricted user
shell
has caused the Debian Bug report #1012200,
regarding RFS: rush/2.2-1 [ITA] -- restricted user shell
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1012200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012200
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 <[email protected]>
* 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
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Thanks for adopting the package.
Please delete your fork and local copy of the repo and continue work in
https://salsa.debian.org/debian/rush.
Please use `gbp import-orig --uscan` to import new upstream versions so that they appear as commits on the
upstream/latest branch. You did not do that in your fork.
--- End Message ---
