Please update clamav to 0.98.1 for Lucid -> Saucy in security/updates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
clamav (Ubuntu) |
Invalid
|
Undecided
|
Marc Deslauriers | ||
Lucid |
Fix Released
|
High
|
Marc Deslauriers | ||
Precise |
Fix Released
|
High
|
Marc Deslauriers | ||
Quantal |
Fix Released
|
High
|
Marc Deslauriers | ||
Saucy |
Fix Released
|
High
|
Marc Deslauriers |
Bug Description
As discussed in the Ubuntu Security team meeting today, I think it would be prudent to deliver 0.98.1 to all users and not just users of backports. Both 0.98.1 upstream and the packaging for 0.98.1 seem to be in a stable place where a general update would be appropriate. The major reason to do this is that the current packages, 0.97.8, cannot use all current virus definitions. You can see this in this excerpt of the libclamav/others.h diff:
* CL_FLEVEL is the signature f-level specific to the current code and
@@ -53,11 +55,12 @@
* in re-enabling affected modules.
*/
-#define CL_FLEVEL 69
+#define CL_FLEVEL 76
#define CL_FLEVEL_DCONF CL_FLEVEL
#define CL_FLEVEL_SIGTOOL CL_FLEVEL
The packages for precise -> saucy are unmodified from trusty. For lucid, there are a few changes, notable removing use of dh-autoreconf since it doesn't exist and the reconf would fail even if it did and disabling LLVM on powerpc to fix the build (last upload we gave up on powerpc since I didn't think of trying this).
Related branches
- Dmitry Shachnev: Disapprove
- Ubuntu branches: Pending requested
- Diff: 35475 lines
Changed in clamav (Ubuntu): | |
status: | New → Invalid |
assignee: | nobody → Marc Deslauriers (mdeslaur) |
Changed in clamav (Ubuntu Lucid): | |
assignee: | nobody → Marc Deslauriers (mdeslaur) |
Changed in clamav (Ubuntu Precise): | |
assignee: | nobody → Marc Deslauriers (mdeslaur) |
Changed in clamav (Ubuntu Quantal): | |
assignee: | nobody → Marc Deslauriers (mdeslaur) |
Changed in clamav (Ubuntu Saucy): | |
assignee: | nobody → Marc Deslauriers (mdeslaur) |
Changed in clamav (Ubuntu Lucid): | |
status: | New → Triaged |
Changed in clamav (Ubuntu Precise): | |
status: | New → Triaged |
Changed in clamav (Ubuntu Quantal): | |
status: | New → Triaged |
Changed in clamav (Ubuntu Saucy): | |
status: | New → Triaged |
Changed in clamav (Ubuntu Lucid): | |
importance: | Undecided → High |
Changed in clamav (Ubuntu Precise): | |
importance: | Undecided → High |
Changed in clamav (Ubuntu Quantal): | |
importance: | Undecided → High |
Changed in clamav (Ubuntu Saucy): | |
importance: | Undecided → High |
Changed in clamav (Ubuntu Lucid): | |
milestone: | none → lucid-updates |
Changed in clamav (Ubuntu Precise): | |
milestone: | none → precise-updates |
Changed in clamav (Ubuntu Quantal): | |
milestone: | none → quantal-updates |
Changed in clamav (Ubuntu Saucy): | |
milestone: | none → saucy-updates |
This bug was fixed in the package clamav - 0.98.1+ dfsg-4ubuntu1~ ubuntu13. 10.2
--------------- dfsg-4ubuntu1~ ubuntu13. 10.2) saucy-security; urgency=medium
clamav (0.98.1+
* Rebuild as a security update (LP: #1296856)
-- Marc Deslauriers <email address hidden> Thu, 27 Mar 2014 08:51:04 -0400