Bug#1001643: Bug#1060913: Re: Bug#1060913: RFS: sdaps/1.9.11-0.1 [NMU] [RC] -- scripts for data acquisition with paper-based surveys

[Bo YU]

Hi!

On Tue, Jan 16, 2024 at 10:39 PM Dominik George <natureshadow at debian.org> wrote:
>
> Hi,
>
> > Here I am not a member of DebianEdu team and told if am not a member
> > of one team there is no reason to do team upload.
> > Ideally, I should contact the team to join in or tell team I am going
> > to fix ftbfs issue.
>
> Whether the maintainer is a team doesn't matter here (it just means I am
> not responsible alone for the lack of updates on the package, haha ;)).
Ah, I just realized you are the maintainer of the package(as
uploader), many thanks for your work.
>
> In general, you always contact the maintainer for every upload before
> doing an NMU, through the address from the package meta-data or by
> sending your changes to the BTS into the bug you are fixing.

Thanks for reminding me about this.
Before submitting an NMU I basically will give it at a glance from
debian tracker to look at the care/upload frequency of this package is
used to determine if the NMU. Because for some packages that lack
care, there are bugs filed in time, but they may not be resolved for a
long time. But this is only from my experience. I should obey Debian
NMU guidance here.


>
> > But I got no response from there(not DebianEdu
> > team) in the past.
>
> Can you point me to message IDs where you requested changes to be
> uploaded?
Sorry, here I mean I asked for some help on IRC.  The package is here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060388

I will ping the maintainer of the package again and will fix some
issue like `UNRELEASE` here.
>
> Ideally, you should just send the changes to the BTS bug you are fixing,
> and tag it "patch".
OKay, no problem. Sometimes the debdiff for new upstream release is
very huge and BTS will drop this.:(

Many Thanks again, TIL.

BR,
Bo
>
> -nik