Bug#969291: RFS: sane-backends/1.0.31-1~experimental1 [RC] -- API library for scanners [transitional package]
Hi,
On Sat, 05 Sep 2020, Jörg Frings-Fürst wrote:
> > First of all, why is this packaging git repository not hosted on
> > salsa.debian.org? I can create you a repository in the "debian"
> > namespace and grant you commit rights on this repository. It
> > would make it easier for random DD to help you out.
>
> Why is simply explained. For the packages in the salsa section debian DDs have
> the right to make changes even against the intention of the maintainers and then
> upload them without following the NMU rules. This is not my idea of teamwork.
This is seldom a problem. And you should trust your peers, not fear their
help.
Having it hosted outside of salsa.debian.org creates needless barriers, in
particular when you are not a DD. When I sponsor, I prefer to sponsor out
of salsa so that I can fix the issues that I find and so that I can tag,
etc.
> The change from libsane to libsane1 requires IMHO a transition. Therefore only
> in experimental.
It no longer requires a transition since we have a transitional package.
That said you should still ask for a binnmu of the reverse dependencies to
get updated dependencies. But they don't have to migrate together with
sane-backends.
> Normally I forward almost all patches. After lintian complained about the
> missing entry forwarded as a warning, I added not-needed for old patches. After
> moving sane to GitLab I don't have direct access to the old bug reports
> anymore.
I don't understand what you are trying to explain. Surely you can open
merge request against sane-backends if you have something to submit?
> > Looking at your history on this package, have you considered asking
> > for the Debian Maintainer status so that you can upload that package
> > on your own?
>
> I am missing the second signing of my key by a DD. I live here near the oldest
> city in Germany, but for Debian far away from everything.
If you have seen the recent messages, you will see that those signatures
are no longer mandatory. If you have worked with a regular sponsor over a
long period of time, then you can likely go through the process easily.
https://lists.debian.org/debian-devel-announce/2020/09/msg00000.html
Cheers,
--
⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog <hertzog@debian.org>
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋ The Debian Handbook: https://debian-handbook.info/get/
⠈⠳⣄⠀⠀⠀⠀ Debian Long Term Support: https://deb.li/LTS
Reply to: