cloud image package list differs from germinate output
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Seeds |
Fix Released
|
Medium
|
Unassigned |
Bug Description
I was playing around with 'germinate' (looking at data at [1]) with regard to the cloud images.
The cloud image for amd64 is a strict superset compared to germinate output.
Below is the additional list of packages in the image.
at
ethtool
fonts-ubuntu-
grub2-common
grub-common
grub-gfxpayload
grub-pc
grub-pc-bin
landscape-client
libfreetype6
libiw30
libnl-3-200
libnl-genl-3-200
libpcsclite1
libreadline5
linux-headers-
linux-headers-
linux-headers-
linux-headers-
linux-image-
linux-image-virtual
linux-virtual
os-prober
python-pycurl
python-
python-twisted-web
wireless-tools
wpasupplicant
I did some initial digging, and it seems like many of those probably come in as depends from the kernel installation.
I noticed that the build process's live-build branch [2] declares in package-
The and the cloud-image seed includes 'landscape-common'.
So, the changes I'd like to be made are:
* either change 'STRUCTURE' at [3] to make cloud-image depend on 'server' or not, but remove the 'server' task from the installation.
* remove landscape-client from manual installation
* remove ubuntu-minimal from manual installation. I'm not sure why we would have this, or actually the reason for its being (compared with a task). Probably should figure that out.
* figure out if 'landscape-client' (package-
* maybe add 'grub-pc' to the seed as '[amd64 i386]'. grub-pc makes the packages list from live-builds scripts/
--
[1] http://
[2] https:/
[3] https:/
Related branches
affects: | ubuntu → uec-live-build |
affects: | uec-live-build → cloud-images |
I think the path forward is to canonize the idea that Cloud images are server + cloudy packages.
With that I would put landscape-client in the server seed. Then I can change the live-build recipe for Saucy.