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

Bug#1065221: Packaging multivolumefile?



Hi Yokota,

Am Tue, Apr 02, 2024 at 08:39:36PM +0200 schrieb Andreas Tille:
> > Nevermind, YOKOTA Hiroshi already has done this and more and is looking
> > for sponsors.
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065221#17
> 
> Thanks a lot for your packaging work.  My very personal sponsoring
> policy is that I sponsor only team maintained packages.  If you move
> your packages to DPT I'll happily sponsor your work. 

Thanks a lot for all your work on the said pre-requisites and moving
them to DPT.  For the moment I've picked python-multivolumefile and
python-bcj and uploaded them to New queue.  My sponsoring style is to do
additional commits trying to be as verbose as possible to tell the
sponsee what to change and why.  I hope you like this.  When looking
at these two packages I've noticed a pattern of changes that were needed
to fix lintian info messages.  Please make sure to run

   lintian -I PACKAGE_VERSION_amd64.changes

to learn about what changes might be sensible to silence lintian.
Some of them where cosmetic but I try to fix these to make sure the
lintian output is not too noisy and I might miss something that
might really need fixing.  I'd also recommend:

$ grep -v ^# ~/.lintianrc 
color=always
display-info=yes

I hope my commits are sensible to you - if not please ask back.

As a general remark:  In those teams I'm more involved we have the
tradition that sponsees leave the distribution in d/changelog to
UNRELEASED while the sponsor changes this to unstable before the final
upload.  This helps team members to immediately know about the status.
I'd be happy if you would follow this as well.

Please verify that your other packages are fixing the things I
commited to the two example packages.  If time permits I'd happily
sponsor you other packages (if nobody else in the team will beat
me in doing so).

Thanks again for all your work
   Andreas.

-- 
https://fam-tille.de


Reply to: