On 2020-08-13 David da Silva Polverari <david.polver...@gmail.com> wrote: > On Wed, Aug 12, 2020 at 07:11:35PM +0200, Andreas Metzler wrote: >> this bug tracks the fact that the changes in the NMU have NOT been >> integrated into a maintainer upload. So it should stay open until that >> has happened, afaik.
> Hi Andreas, > I'm not sure if I follow, but from what I see, you are worried that new > maintainers will not take these NMU changes into account on the next > revisions, right? Hello David, Yes, indeed.[1] > I have an ITA opened and I'm working on a Debian revision of the package > atm, and I have created a git repository (using gbp import-dscs > --debsnap), which contains your NMU. > Even if I weren't doing this revision, I think any other potential > Debian contributor would be basing their work on the latest Debian > revision found on the archives, which happen to be your NMU at this > point, as can be seen by fetching the package sources on sid with apt > source. > Thus I'm not sure what the benefits are of keeping this bug open. Of > course, I may be completely wrong :). So, do you think I should reopen > it until I (or anyone else, for that matter) release a new Debian > revision? Reopening seems to be make-work if you are in the process of adopting anyway. ;-) cu Andreas [1] Worried is too strong. But the rationale for closing made no sense. I submitted a bugreport with a diff for the NMU to make it available to the maintainer and track its integration. Closing it with "a package that contains the diff already entered the Debian archive" did not make sense, since the only package in the archive with the diff is still the NMU, so the status of the package had not changed at all since I had submitted the tracking bug report.
