This is why we don't explicitly trust Wikis or Debian.

Let me clarify the issue:  The issue isn't what the Debian wiki says.
The issue is the 1.1.19 package and what was actually in it.

If 1.1.19 in Debian never had Stub Status, and Debian never intended
Stub Status in 1.1.19 then this is an Invalid bug because your research
only shows what's in 1.2.1 which isn't going to be included in Precise
as Precise is pretty much version fixed to 1.1.19.

If Debian included the stub status code in 1.1.19 and never activated
it, that's an easy SRU to fix the issue if it was intended for inclusion
but oversight caused it to not be included.  But if what I said before
this is true, and 1.1.19 never actually had Stub Status and never was
supposed to in Debian, then to add the module would require some
thorough discussion with the MOTUs to try and get an "Add additional
features" patch into Precise without backports, and for that I'd need to
know more about why Stub Status is needed, what it does, why it's
necessary, etc.

Data  on 1.2.1 won't help, ever, as 1.1.19 is what Precise will have
from now until it's EOL (excluding backports).  We need data about
1.1.19 which I will find tomorrow when I dissect 1.1.19 that was in
Debian..

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170586

Title:
  Naxsi package lacking Stub Status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1170586/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to