rabbitmq-server maintainers, are there any other RC bugs that you're
planning to file on the package?
No other RC bugs. I submitted
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773259, which I hope
has an appropriate severity of important.
I've asked a couple developers their opinion on
That new upstream version was uploaded at urgency=high the day before
the freeze, with no explanation other than new upstream release.
Given that 3.4.0 had been out for a fortnight by that point, it looks
very much like trying to game the freeze. :-(
It indeed looks bad. I believe this is
Control: tags -1 + confirmed moreinfo
On 2014-12-16 15:47, Thomas Goirand wrote:
Now, seeing that 3.4.0 is in Sid, is it ok to target
testing-proposed-updates for 3.3.5-1.1 here? We would also update Sid
to
3.4.1 then.
Please let me know, and I'll work out with Blair Hester and probably
Matt
Control: tag -1 confirmed moreinfo
On Tue, Dec 16, 2014 at 03:07:20AM -0800, Blair Hester wrote:
rabbitmq-server maintainers, are there any other RC bugs that you're
planning to file on the package?
No other RC bugs. I submitted
Ok, the t-p-u upload can go ahead. Please remove the
Control: tags -1 + moreinfo
On 2014-12-14 23:07, Matt Kraai wrote:
Is it OK to uploade rabbitmq-server/3.3.5-1.1 to
testing-proposed-updates?
773134 reports that it is insecure because it trusts the
X-Forwarded-For HTTP
header. The following patches were applied upstream to fix this:
*
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Is it OK to uploade rabbitmq-server/3.3.5-1.1 to testing-proposed-updates?
773134 reports that it is insecure because it trusts the X-Forwarded-For HTTP
header. The following patches were
6 matches
Mail list logo
