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

Bug#915354: Bug#921482: RFS: note/1.3.26-3 +help



control: tags -1 +help

I add @bugs.d.o with the tag.



El sáb., 9 de feb. de 2019 a la(s) 13:36, Dmitry Bogatov (KAction@debian.org) escribió:

control: tags -1 +help

[2019-02-07 14:39] eamanu15 <emmanuelarias30@gmail.com>
> > >
> > > * Add me to Maintainer Field on d/control:
> > >   - For some reason that I ignore the Maintainer field
> > >   on d/control was not updated.
> >
> > Sorry, I do not understand this sentense. Mind to simplify explaination
> > what changed?
> >
> In the middle of my ITA, I have the "little" problem that
> the unstable version was different with the salsa. I contacted
> with the maintainer to push the last version on salsa, but I did not
> have response. So, I download the orig.tar.gz and debian.tz file.
> Then, and replace the files and
> I forgot change the Maintainer field d/control.
>
> Because of that I write: "For some reason that I ignore the Maintainer field
> on d/control was not updated."

Still do not understand. You either updated Maintainer field, in which
case you should write something like "Set myself as maintainer", maybe
with "(Closes: #O-Bug-Number)", or you did not. It is changelog.


you will see that I set myself as maintainer. The Version of note on salsa was: 1.3.22
But on unstable was 1.3.26

For this reason, I download the files from package.debian

I forgot set myself as maintainer. Was my foul.

For this reason In this new package version 1.3.26-3 I add me
on Maintainer field.

 

Added tag +help. Fellow developers, I need help reviewing this entry.

> > > * Delete NOTEDB folder and NOTEDB.pm because they are
> > >   not on upstream from ad6cb95 commit (Github).
> >
> > What is ad6cb95 commit? For person who do not follow upstream
> > development, this changelog entry brings more questions, then
> > explainations.
> >
>
> Ok I will write
> * Delete NOTEDB folder and NOTEDB.pm because they
>   are not necessary.
>
> What about it?

In this case I understand "what" is done, but still do not understand
"why". You package some specific release. What is the purpose of
backporting changes from upstream HEAD?

> No, but I want to have the package as close as possible to the upstream.

In general, we at Debian package releases, we do not follow upstream
development commit-after-commit.  Usually, we backport patches only to
fix some bug.

Ok I will delete that patch.

Thanks for the review.
Regards

 
--
        Note, that I send and fetch email in batch, once every 24 hours.
                 If matter is urgent, try https://t.me/kaction
                                                                             --


--
Arias Emmanuel
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Reply to: