Open dantje opened 9 years ago
Upon further investigation, this seems to be a secondary bug in the error path. The VirtualBox module is not building for some reason (https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1457776), and when trying to generate the error report for that apport fails because of an API change (adding insult to injury). So not direct ZOL issue, but an update that supports the new apport API would be nice.
edit: added vbox build issue link
I ran into this via a different route, install of ubuntu-zfs went along fine, but on the following upgrade I had the following:
# apt-get upgrade -V
---SNIP---
The following packages will be DOWNGRADED:
dkms (2.2.0.3-1.1ubuntu5.14.04.5 => 2.2.0.3-1.1ubuntu5.14.04.1+zfs10~trusty)
---SNIP---
I haven't a clue as to whether this could/has caused any issues, as I started playing with ZFS directly after installing, and I didn't have any intact zpools before rebooting.
@phizev, the DKMS package downgrade is expected and necessary. The ubuntu-zfs package pins the PPA so that packages with ZoL support are installed.
DKMS is getting a major update in the Wily release, which is due next week, and I'm hoping that the ZoL features will be backported. If not, then the dkms packages in the PPA will be updated along with the next ZoL point release.
Alternatively, you could try installing the dkms package for Wily on Trusty. It should be compatible, and has several general fixes that should resolve the VirtualBox glitch.
The fix released with dkms 2.2.0.3-1.1ubuntu5.14.04.5 as described in
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1499842
is not available in the dkms package i'm running (2.2.0.3-1.1ubuntu5.14.04.1+zfs10~trusty)
Because of this I'm getting errors when installing VirtualBox.