For example, if someone installs from the ubuntu-server image but forgets to select (or doesn't know about) the minimal virtual machine option in the F4 boot menu, and then post install tries to convert over to using the -virtual kernel (this actually happened to me with a jaunty install, which is how I knew about the conflict that was present in that release's packages).
For example, if someone installs from the ubuntu-server image but forgets to select (or doesn't know about) the minimal virtual machine option in the F4 boot menu, and then post install tries to convert over to using the -virtual kernel (this actually happened to me with a jaunty install, which is how I knew about the conflict that was present in that release's packages).
What I can't figure out is why the conflict isn't getting set to server; http:// kernel. ubuntu. com/git? p=ubuntu/ ubuntu- karmic. git;a=blob; f=debian. master/ sub-flavours/ virtual. vars already contains:
8 darch=" `dpkg-architect ure -qDEB_HOST_ARCH`" "generic- pae" "redhat- cluster- modules" "linux- image-PKGVER- ABINUM- ${based_ on}"
9 if [ "$darch" = "i386" ]
10 then
11 based_on=
12 else
13 based_on="server"
14 fi
15 # The provides and conflicts are REQUIRED
16 provides=
17 conflicts=
which ought to set the conflicts to server when the amd64 kernels are built, but as evidenced by the published packages, doesn't actually do so.