Bug#836571: jessie-pu: package rabbitvcs/0.16-1
On Sun, 2016-09-04 at 19:19 +0100, Christopher Hoskin wrote:
[...]
> > Given the fact that the package has no reverse-dependencies and before
> > your NMU in unstable had not been updated for two years, I wonder
> > whether removal might have been a better option.
>
> That's a fair point - but presumably a matter for the PAPT rather than me?
If you're not the maintainer, yeah. It was a pondering.
> > I assume your rationale for suggesting a release via stable-updates,
> > rather than simply waiting for the next point release (which will be in
> > just under two weeks time) is the potential for data loss.
>
> This may be me misunderstanding the roles of stable-updates and point releases.
> The next point release sounds fine, particularly given that #817231 had already
> been open for some time.
All updates for stable are uploaded to proposed-updates, which is then
merged into stable at a point release. The Stable Release Managers may
optionally decide to also release some of those updates via
stable-updates before the point release, in order to make them available
to users more quickly.
There's some more explanation at
https://lists.debian.org/debian-devel-announce/2011/03/msg00010.html ,
which should probably be cleaned up and published somewhere. (Other than
in the footer of each mail to debian-stable-announce.)
> I've rebuilt the diff with version 0.16-1+deb8u1 as I started from the Jessie
> source package. Hopefully I have got it right this time?
That looks fine, thanks.
Regards,
Adam
Reply to: