[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

On Fri, Jun 03, 2022 at 03:49:48PM +0200, Bastian Germann wrote:

On Wed, 1 Jun 2022 12:20:33 +0800 Bo YU <tsu.yubo@gmail.com> wrote:

   * Non-maintainer upload.
   * New upstream release (Closes: #1001091)


There is no need to repack the doc directory anymore since 1.9 changed the license.
I have removed the repacking stuff in
https://salsa.debian.org/debian/rush/-/commit/ef5fa020502263c594b83827ed3302200e95650d

I have left the d/copyright addition of GFDL for you.


   * fix rush FTCBFS (Closes: #929160)
   * Update Standards-Version to 4.6.1
   * drop debian/patches/intprops.patch
   * drop debian/patches/manpages.diff


What happened to format_security.diff?
Why did you remove it? It should still be valid but maybe needs a rebase.


Ok. I got huzz hint when applying the patch and i forget to record it
here.




   * Add vcs-* in d/control
   * introducing the git gbp packaging


You are not using gbp as intended. The upstream and debian/* files are commited together in one commit.
I have created https://salsa.debian.org/debian/rush. Please fork it and apply your upstream and
debian changes separately. After cloning you should begin with the command
gbp import-orig --uscan --debian-branch=debian/main --upstream-branch=upstream/latest


Thank you. This is very help for me to do such. I am trying to find my
sold packaging way. yeah, although I call it as gbp here, but some
process do not follow the gbp way.

This is where I like Debian :)
Then add your debian/* changes in debian/main but make sure to have the Vcs-* fields pointing to https://salsa.debian.org/debian/rush (not your fork). It would be nice to split the logical steps 
in single commits but it is not required.

I would discourage the gbp.conf file and also the pristine-tar but I will leave that to your decision.
If you want to use pristine-tar make sure you add all the old commits before importing v2.2.
IIRC, There is no pristine-tar branch in go team packaing also. Ok, It is become more complex if keep pristine-tar branch maybe. 


    * Add myself as maintainer (Closes: 1012205)


Thanks for this decision. Please add the missing hash #.


Oh, sorry, will do;)

Thank you again for help me to maintain rush package.

Bo

--
Best Regards,

Attachment: signature.asc
Description: PGP signature

Reply to: