This bug was fixed in the package clamav - 0.102.2+dfsg-0ubuntu0.19.10.1
---
clamav (0.102.2+dfsg-0ubuntu0.19.10.1) eoan-security; urgency=medium
* Updated to 0.102.2 to fix security issue (CVE-2020-3123)
- debian/patches/*: synced patches with 0.102.2+dfsg-1.
-
This bug was fixed in the package clamav - 0.102.2+dfsg-0ubuntu0.18.04.1
---
clamav (0.102.2+dfsg-0ubuntu0.18.04.1) bionic-security; urgency=medium
* Updated to 0.102.2 to fix security issue (CVE-2020-3123)
- debian/patches/*: synced patches with 0.102.2+dfsg-1.
-
This bug was fixed in the package clamav - 0.102.2+dfsg-0ubuntu0.16.04.1
---
clamav (0.102.2+dfsg-0ubuntu0.16.04.1) xenial-security; urgency=medium
* Updated to 0.102.2 to fix security issue (CVE-2020-3123)
- debian/patches/*: synced patches with 0.102.2+dfsg-1.
-
autopkgtest have been test with both :
The current SRU'd package [clamav/0.102.1+dfsg-0ubuntu0.19.10.3]:
The current SRU'd package -1 [clamav/0.102.1+dfsg-0ubuntu0.19.10.2]:
https://autopkgtest.ubuntu.com/packages/pg-snakeoil/eoan/amd64
The same failures occurs in both, meaning the failure
autopkgtest have been test with both the current SRU'd package and
curren SRU'd package -1:
https://autopkgtest.ubuntu.com/packages/pg-snakeoil/eoan/amd64
The same failures occurs in both, meaning the failure isn't introduce by
this particular SRU.
It looks like a test output mismatch against
@cash.williams
no worries I revert it back to "Fix Committed"
** Changed in: clamav (Ubuntu Xenial)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860217
I was trying to see the various status for the 16.04 fix and clicked
released on accident.
A - I can't change it back to committed
B - Why does my user have permission to change it in the first place!
** Changed in: clamav (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You
Focal uses postgresql-12:
---
/usr/lib/postgresql/12/lib/pgxs/src/makefiles/../../src/test/regress/pg_regress
--inputdir=./ --bindir='/usr/lib/postgresql/12/bin'
--dbname=contrib_regression pg_snakeoil
(using postmaster on localhost, port 5433)
==
"pg-snakeoil" seems to have been first introduced starting disco, which
explain why X and B doesn't get any failures even if at same clamav
upstream version (0.102.1)
$ rmadison pg-snakeoil
pg-snakeoil | 1.1-1 | disco/universe | source
pg-snakeoil | 1.1-1build0.1 |
With regards to the "pg_snakeoil" autopkgtest failures in Eoan.
It doesn't fails for any other release than Eoan (nothing reported in F/B/X)
Please note that it's the first time the test are run since the upstream
version bump to fix CVE-2019-15961[0] has been introduced.
I don't think the
[BIONIC VERIFICATION]
No more loop detected.
All of the debconf prompts that are supposed to be there are actually
reachable, including the one modified by this SRU "LogTime"[0] and
"LogRotate"[1].
[0]- Do you want to log time information with each message?
[1]- Do you want to enable log
[EOAN VERIFICATION]
No more loop detected.
All of the debconf prompts that are supposed to be there are actually
reachable, including the one modified by this SRU "LogTime"[0] and
"LogRotate"[1].
[0]- Do you want to log time information with each message?
[1]- Do you want to enable log
[XENIAL VERIFICATION]
No more loop detected.
All of the debconf prompts that are supposed to be there are actually
reachable, including the one modified by this SRU "LogTime"[0] and
"LogRotate"[1].
[0]- Do you want to log time information with each message?
[1]- Do you want to enable log
** Description changed:
[Impact]
There appears to be another issue with
> dpkg-reconfigure clamav-daemon
Like in #1792051, the command ends up in an infinite loop, just that
this time it happens between 'Log file for clamav-daemon' and 'Do you
want to enable log rotation?', with
Hello Konrad, or anyone else affected,
Accepted clamav into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/clamav/0.102.1+dfsg-
0ubuntu0.16.04.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Konrad, or anyone else affected,
Accepted clamav into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/clamav/0.102.1+dfsg-
0ubuntu0.18.04.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Description changed:
[Impact]
There appears to be another issue with
> dpkg-reconfigure clamav-daemon
Like in #1792051, the command ends up in an infinite loop, just that
this time it happens between 'Log file for clamav-daemon' and 'Do you
want to enable log rotation?', with
Hello Konrad, or anyone else affected,
Accepted clamav into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/clamav/0.102.1+dfsg-
0ubuntu0.19.10.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
vorlon's comment has been answered in the 'Regression Potential' section
of the SRU template.
** Description changed:
[Impact]
There appears to be another issue with
> dpkg-reconfigure clamav-daemon
Like in #1792051, the command ends up in an infinite loop, just that
this time it
The debdiff is basically impossible to review without further context
due to the use of magic strings as argument names and no way to tell
they're the right magic strings without tracing the code.
I think a regression test for this SRU should include verifying not only
that the infinite loop is
** Changed in: clamav (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: clamav (Ubuntu Bionic)
Importance: Undecided => Critical
** Changed in: clamav (Ubuntu Bionic)
Importance: Critical => Medium
** Changed in: clamav (Ubuntu Xenial)
Importance: Undecided => Medium
--
Uploaded in E/B/X.
It is now waiting for the SRU team to approve the build in -proposed.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860217
Title:
dpkg-reconfigure clamav-daemon in
Uploaded in E & B.
It is now waiting for the SRU team to approve the build in -proposed.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860217
Title:
dpkg-reconfigure clamav-daemon in
** Description changed:
[Impact]
There appears to be another issue with
> dpkg-reconfigure clamav-daemon
Like in #1792051, the command ends up in an infinite loop, just that
this time it happens between 'Log file for clamav-daemon' and 'Do you
want to enable log rotation?', with
** Description changed:
+ [Impact]
+
There appears to be another issue with
> dpkg-reconfigure clamav-daemon
Like in #1792051, the command ends up in an infinite loop, just that
this time it happens between 'Log file for clamav-daemon' and 'Do you
want to enable log rotation?', with
This bug was fixed in the package clamav - 0.102.1+dfsg-2ubuntu2
---
clamav (0.102.1+dfsg-2ubuntu2) focal; urgency=medium
* d/clamav-daemon.config.in: Correct error from ScanOnAccess option
removal so that setting LogFile options via DebConf works again.
(Closes: #950296)
I have just uploaded the fix in focal for the new package to start building.
Once the package is found in -release, I'll start the SRU to fix the stable
release.
Stay tuned.
- Eric
** Changed in: clamav (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: clamav (Ubuntu
Can't reproduce with version mentioned in comment #10 using Debian sid.
debconf (developer): --> 0
debconf (developer): <-- STOP
debconf (db config): saving database
debconf (db passwords): no database changes, not saving
debconf (db templatedb): saving database
I'll backport the fix into
btw, I've been able to reproduce it with focal/20.04LTS which is for now
still an active development release.
That doesn't seems to be a resolved issue in later version.
** Also affects: clamav (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: clamav (Ubuntu Xenial)
Looking into salsa git report, it seems to have a fix in Debian upstream
$ git show 089b6136
commit 089b6136e95dd34b3ac8a4d0753bffb48c48ebdb (HEAD -> unstable, tag:
debian-0.102.1+dfsg-3, origin/unstable, origin/HEAD)
Author: Scott Kitterman
Date: Fri Jan 31 16:54:06 2020 -0500
The use of 'DEBCONF_DEBUG='.*'' can be helpful here for debugging purpose.
Simply need to set and export.
Add this link:
https://wiki.debian.org/MaintainerScripts
with possibly the add of 'set -xv' in the clamav-daemon maintainer
scripts to find what is causing the loop.
I actually took a few
The use of 'DEBCONF_DEBUG='.*'' can be helpful here for debugging purpose.
Simply need to set and export.
And this link:
https://wiki.debian.org/MaintainerScripts
Following the appropriate workflow to understand what it is doing under
the hood.
As a debug exercise, one ca also add 'set -xv' in
Impact: production servers are not provisioning
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860217
Title:
dpkg-reconfigure clamav-daemon in infinite loop
To manage notifications about this bug
I have reproduced it on Xenial.
$ cat /etc/lsb-release
..
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS"
$ uname -rv
4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019
$ dpkg -l | grep clam
ii clamav 0.102.1+dfsg-0ubuntu0.16.04.2
ii clamav-base
Upstream bug from Debian has been fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860217
Title:
dpkg-reconfigure clamav-daemon in infinite loop
To manage notifications about this bug go to:
I had filed
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1861497, but just
found this and closed it as a duplicate.
This is critical bug for us as we have `DEBIAN_FRONTEND=noninteractive
DEBCONF_NONINTERACTIVE_SEEN=true dpkg-reconfigure clamav-daemon` in our
provisioning which will hang
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950296
** Bug watch added: Debian Bug tracker #950296
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950296
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: clamav (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860217
Title:
** Description changed:
There appears to be another issue with
> dpkg-reconfigure clamav-daemon
Like in #1792051, the command ends up in an infinite loop, just that
this time it happens between 'Log file for clamav-daemon' and 'Do you
want to enable log rotation?', with one more step
39 matches
Mail list logo
