THanks! But that's the entire problem: instead of installing the actual packages, you need to install the enablement stack packages that "provide" those virtual packages. So for 12.04.5 you have to install libegl1-mesa-lts-trusty libgles2-mesa-lts-trusty.
The problem comes from the fact that a different set of packages is needed for each point release: for 12.04.4 you need saucy packages, for 12.04.3, raring packages, and for 12.04.2, quantal packages. This is what's proving a bit difficult to express in the preseed.
Ara said that we can potentially ignore all point releases except .5, but we also need to keep 12.04 (no point) installation working; the problem here is that if I force installation of libegl1-mesa-lts-trusty on 12.04.0, it may try to install the entire enablement stack and destroy the installation again.
I'm prototyping a solution which "detects" the point release and installs the appropriate enablement stack packages, I promise I'll have something ready for review today.
THanks! But that's the entire problem: instead of installing the actual packages, you need to install the enablement stack packages that "provide" those virtual packages. So for 12.04.5 you have to install libegl1- mesa-lts- trusty libgles2- mesa-lts- trusty.
The problem comes from the fact that a different set of packages is needed for each point release: for 12.04.4 you need saucy packages, for 12.04.3, raring packages, and for 12.04.2, quantal packages. This is what's proving a bit difficult to express in the preseed.
Ara said that we can potentially ignore all point releases except .5, but we also need to keep 12.04 (no point) installation working; the problem here is that if I force installation of libegl1- mesa-lts- trusty on 12.04.0, it may try to install the entire enablement stack and destroy the installation again.
I'm prototyping a solution which "detects" the point release and installs the appropriate enablement stack packages, I promise I'll have something ready for review today.