Bug#836571: jessie-pu: package rabbitvcs/0.16-1

2016-09-04 Thread Adam D. Barratt
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 pre

Bug#836571: jessie-pu: package rabbitvcs/0.16-1

2016-09-04 Thread Christopher Hoskin
Package: release.debian.org Tags: jessie Followup-For: Bug #836571 User: release.debian@packages.debian.org Usertags: pu > *No*. The bug you're fixing may be critical, the request to fix it in > stable is at most normal. Appologies - my misunderstanding. > Given the fact that the package has

Bug#836571: jessie-pu: package rabbitvcs/0.16-1

2016-09-04 Thread Adam D. Barratt
Control: tags -1 +confirmed -patch +jessie Control: severity -1 normal On Sun, 2016-09-04 at 07:32 +0100, Christopher Hoskin wrote: > Package: release.debian.org > Severity: critical *No*. The bug you're fixing may be critical, the request to fix it in stable is at most normal. > Tags: patch > U

Bug#836571: jessie-pu: package rabbitvcs/0.16-1

2016-09-03 Thread Christopher Hoskin
Package: release.debian.org Severity: critical Tags: patch User: release.debian@packages.debian.org Usertags: pu The attached patch fixes bug #817231 in the rabbitvcs package. This is classified as a critical bug on the grounds that it can cause serious data loss (e.g. loss of entire home fo