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

Bug#930637: unblock: monit/1:5.25.2-3+deb10u1



On 2019-07-04 13:52, Sergey B Kirpichev wrote:
On Thu, Jul 04, 2019 at 12:48:23PM +0200, Bas Couwenberg wrote:
Are you willing to maintain the monit backport if I sponsor the NEW uploads

No.  Next time _you_ may be unavailable to sponsor backport for
a buster+1.  I won't give package users impression that backports
are supported, when it's not the case.

While I'm unlikely to be unavailable for Debian work, I can't exclude the possibility of getting hit by a bus some time in the future.

How often do you expect to need NEW processing for monit? It doesn't build any library packages that get renamed for SONAME bumps for example.

Once monit is in backports, you won't need to pass NEW again until you introduce new binary package names.

For bullseye the backport hopefully won't be required to have the package available in stable, so it will be less of an issue if there is no sponsor for the initial upload of the backport because I got hit by a bus.

Feel free to provide backport yourself.  I also can add you as
a co-maintainer and/or step down as a package maintainer.

You should definitely not step down as maintainer, you seem to have done a good job maintaining the package since you got involved.

The package would benefit from team maintenance, but that assumes there are others willing and able to contribute to co-maintenance. This is not a given.

Do you know any users of the package who have contributed patches or other maintainer type bugreports that could be recruited to help co-maintain the package?

They don't need to be DDs, but it would help to provide some redundancy for the NEW scenario.

I'm reluctant to maintain the backport as I already maintain too many packages, but I also need monit in buster at $DAYJOB. So I'm in a bit of a bind.

My strong preference is for you to maintain the backport as you are the most able maintainer of the package, so I hope we can find a solution where I can support you with the unpleasant bureaucracy to enable you keep doing your work on the monit package (and its backports).

Kind Regards,

Bas


Reply to: