Marking as invalid. Eric's analysis is correct: The correct kernel is
installed. What Daniel sees is simply an artifact of the way the
-virtual kernel is packaged.
** Changed in: vm-builder (Ubuntu)
Status: Triaged = Invalid
--
vmbuilder does not respect flavour option
** Changed in: vm-builder (Ubuntu)
Status: New = Triaged
** Changed in: vm-builder (Ubuntu)
Importance: Undecided = Low
--
vmbuilder does not respect flavour option
https://bugs.launchpad.net/bugs/403144
You received this bug notification because you are a member of Ubuntu
Bugs, which
Marking as invalid. Eric's analysis is correct: The correct kernel is
installed. What Daniel sees is simply an artifact of the way the
-virtual kernel is packaged.
** Changed in: vm-builder (Ubuntu)
Status: Triaged = Invalid
--
vmbuilder does not respect flavour option
I noticed this too. Turns out it's not an issue with vmbuilder but
rather with how the virtual kernel is now packaged. The -virtual kernel
is virtually the same as the -server kernel so Ubuntu stopped building a
separate -virtual kernel. See bug #307924, comment #5 for details.
vmbuilder is
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/29398304/Dependencies.txt
--
vmbuilder does not respect flavour option
https://bugs.launchpad.net/bugs/403144
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
