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 amavisd running without - nvidia nvcc installed => amavisd is broken by this bug, but then can be fixed with a conscious config file change 3. had amavisd running without - norman AV nvcc installed => Things working fine WITH norman AV Now if we would SRU something we would: - not help #1 being not affected - #2 was broken, so we fix something unused (and flagging all mails can be a thing as well since https://xkcd.com/1172/) - for those people in #3 we would break a valid working setup It is sort of unfortunate, but at least in my limited POV the risk actually outweighs the gain in this case. Also setting up "new" Xenial should no more be a major tasks these days with Bionic being available for quite a while now. just my 2 cents, feel free to discuss if you think otherwise. ** Also affects: amavisd-new (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: amavisd-new (Ubuntu Xenial) Status: New => Won't 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 CUDA is on the same system To manage notifications about this bug go to: https://bugs.launchpad.net/amavisd-new/+bug/1582318/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
