Hi Christian,
I actually agree. Mostly because of the points you raised, but maybe even on a
4th point. Most users use (and should use) a virtualized or container-ized
environment, where in this case this bug also does not apply. I realized this a
bit after I wrote the original comment.
I still
Hi Helge,
You are right, the issue exists there.
But IMHO the backport has as SRU to Xenial has quite some regression risk and
actually low gain.
Let me outline why I think so:
Looking at people that:
1. had amavisd running without - nvidia nvcc not installed
=> Things working fine
2. had amav
Just encountered this bug on a xenial lts server. Isn't it supposed to be fixed
there?
If it's not should we open a SRU? It seems low risk and potentially high gain.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Changed in: amavisd-new
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582318
Title:
amavis virus check fails when nvidia CUDA is on the same system
To manage
Debian lost the fix along the last uploads so I reopened the Debian bug
to ensure they get the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582318
Title:
amavis virus check fails when nvidia
** Changed in: amavisd-new
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582318
Title:
amavis virus check fails when nvidia CUDA is on the same system
To manage
** Changed in: amavisd-new
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582318
Title:
amavis virus check fails when nvidia CUDA is on the same system
To manage
FYI - Debian merged my patch and closed the bug, Delta can be dropped on
next merge
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582318
Title:
amavis virus check fails when nvidia CUDA is on the s
This bug was fixed in the package amavisd-new - 1:2.10.1-4ubuntu1
---
amavisd-new (1:2.10.1-4ubuntu1) yakkety; urgency=medium
* Merge from Debian, remaining changes:
+ Add information in README.Debian about Ubuntu specific changes
+ Ubuntu configuration changes in 21-ubuntu_
** Changed in: amavisd-new
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582318
Title:
amavis virus check fails when nvidia CUDA is on the same system
To manage notif
Reported to Debian and linked bug
** Bug watch added: Debian Bug tracker #832511
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832511
** Also affects: amavisd-new via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832511
Importance: Unknown
Status: Unknown
--
You received t
Thank you for your report, I checked around and can confirm that the
packaged nvidia-cuda-toolkit causes this conflict.
I added the disabling to the merge of amavisd-new which I prepared for
Yakkety as I think it is right to disable the "out-of-archive" solution
in this case.
** Changed in: amavi
12 matches
Mail list logo
