Thank you all!
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/888627
Title:
please backport pdns-recursor 3.3-2 from Precise
To manage notifications about this bug go to:
** Changed in: hardy-backports
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/888627
Title:
please backport pdns-recursor 3.3-2 from Precise
To
Tested backported package (no-change) from my PPA, it installs/upgrades
without issues and it's working OK.
root@lls32-pdns:~# dig +short ubuntu.com @localhost
91.189.94.156
root@lls32-pdns:~# dig +short chaos txt version.bind @localhost
PowerDNS Recursor 3.3 $Id: pdns_recursor.cc 1712
Tested and working on Maverick, Natty and Oneiric. All packages are no-
change backports from Precise (3.3-2)
Maverick:
gimre@mms32-pdns:~$ dig +short ubuntu.com @localhost
91.189.94.156
gimre@mms32-pdns:~$ dig +short chaos txt version.bind @localhost
PowerDNS Recursor 3.3 $Id: pdns_recursor.cc
*** This bug is a security vulnerability ***
Public security bug reported:
There is pdns-recursor 3.1.4-6ubuntu1 in Hardy, which has a major
security issue (see bug #502987). This bug was fixed in pdns-recursor
3.1.7 and above for every Ubuntu release except Hardy, because it would
be too much
Sure thing, I'm interested in backporting 3.3-2 to all releases. Should
I open a separate bugreport for every release?
Backporting Lucid's 3.1.7 doesn't make much sense (IMHO), because that
would mean we're backporting only for this one security fix, which - as
I understand - isn't the main
Note on Hardy backport: in pdns-recursor 3.3-2, three things need
changing:
- debian/source/format: lowered to 1.0
- debian/control: lowered builddep for debhelper (in Precise there's Build-Dep:
debhelper = 7.0.50~ , but in hardy-backports there's only debhelper 7.0.13
present, so I've changed
Right. I was trying something like this, but my test messages did not
trigger the OPENWHOIS test...
With your TEST CASE I can confirm that the package from -proposed is
working and it does NOT include the OPENWHOIS test.
--
You received this bug notification because you are a member of Ubuntu
I'm trying to recreate the bug but I can't seem to get it right... Is
there a sure way to get SA to show that test in the header? I'm sending
all kinds of messages to my test box, but it doesn't want to do the
OPENWHOIS test...
--
You received this bug notification because you are a member of
Did some basic tests and seems to be working on Dapper.
--
Please backport clamav 0.96.4 to Maverick, Lucid, Karmic, Hardy, and Dapper.
https://bugs.launchpad.net/bugs/683710
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, which is subscribed to
Tested and NOT working on Maverick (x86_64, desktop). I get the same
error after upgrading from -proposed.
gi...@ximi:/var/lib/clamav$ apt-cache policy clamav-daemon
clamav-daemon:
Installed: 0.96.3+dfsg-2ubuntu1.1
Candidate: 0.96.3+dfsg-2ubuntu1.1
Version table:
***
Ignore the above comment. I did the upgrade wrong. I was still using
libclamav6 from -main. Redid the test on Maverick (both i386 and x86_64)
and the package from -proposed is working OK. The fix works in Maverick.
--
libclamav6: Some PDFs cause Unknown error code ERROR
Exactly, I've tested on Lucid 64bit, and it seems to work fine.
--
libclamav6: Some PDFs cause Unknown error code ERROR
https://bugs.launchpad.net/bugs/658341
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, which is subscribed to Hardy Backports.
--
Tested the package on Intrepid, from intrepid-proposed and I can confirm
it's working.
One small observation: I've set it up through amavisd-new, and after
doing 'apt-get update' (after enabling -proposed), it installed OK, and
I saw the updated /usr/share/spamassassin/72_active.cf, but it did
Verified Jaunty package, too, confirming it's working OK. Same
observation (obviously) as above.
--
FH_DATE_PAST_20XX scores on all mails dated 2010 or later
https://bugs.launchpad.net/bugs/502071
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, which
Installed from jaunty-proposed and tested it with a couple of apps
(klamav, python-clamav, etc), and it's working OK.
r...@utest-jj:~# clamscan -V
ClamAV 0.95.3/1/Sun Nov 8 05:28:38 2009
r...@utest-jj:~# python clamav_test.py
646721
('0.95.3', 1, 1257650918)
0.4.1
(1,
Did some tests on Karmic/Jaunty/Intrepid with clamav 0.95.3 (see
https://wiki.ubuntu.com/MOTU/Clamav matrices).
--
Please update clamav to 0.95.3
https://bugs.launchpad.net/bugs/473707
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, which is
17 matches
Mail list logo
