[Bug 505963] Re: extfs/uzip does not parse new 'unzip -v' format correctly

2010-01-12 Thread Helge Doering
Package mc_4.7.0-1ubuntu1 from Lucid does not have this bug. It uses the new date format already. -- extfs/uzip does not parse new 'unzip -v' format correctly https://bugs.launchpad.net/bugs/505963 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1634584] [NEW] package mysql-server-5.7 5.7.15-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-18 Thread Helge Doering
Public bug reported: Probably relates to #1612517 Looks like mysql is not able to upgrade from 5.5 to 5.7 (trusty to xenial). I'm not sure from which version the config originates. After the option to send this report, I also saw this message in the terminal: Setting up mysql-server-5.7

[Bug 1634584] Re: package mysql-server-5.7 5.7.15-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-18 Thread Helge Doering
** Description changed: - Probably relates to #1612517 + Probably relates to + https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1612517 Looks like mysql is not able to upgrade from 5.5 to 5.7 (trusty to xenial). I'm not sure from which version the config originates. After the

[Bug 1582318] Re: amavis virus check fails when nvidia CUDA is on the same system

2018-09-02 Thread Helge Doering
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.

[Bug 1582318] Re: amavis virus check fails when nvidia CUDA is on the same system

2018-09-19 Thread Helge Doering
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

[Bug 1903920] Re: Warning message about cryptsetup during boot

2022-04-03 Thread Helge Doering
The correct way to disable the warning seems to be to add RESUME=none to /etc/initramfs-tools/conf.d/resume if your swap has a /dev/urandom key. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.