[elbe-devel] Install newest available version of a package that belongs to the base system

[John Ogness]

Hi Lukasz
On 2018-02-08, Lukasz Walewski <lwalewski at s-can.at> wrote:
> Assume I want to have package "some-package" installed in my RFS image
> at the newest version available. The main Debian mirror
> (e.g. http://deb.debian.org/debian) contains version 1.1.1-1 of
> some-package. The other Debian mirror that publishes regular updates
> (e.g. http://security.debian.org/debian-security) contains version
> 2.2.2-2 of some-package. Here is what I do:
>
> 1. include the desired package in the <pkg-list/>:
> <pkg-list>
> <pkg>some-package</pkg>
> </pkg-list>
>
> 2. specify the main Debian mirror in the <primary_host/>:
> <primary_host>http://deb.debian.org/debian</primary_host>
>
> 3. specify the update mirror in the <url-list/>:
> <url-list>
> <url>
> <binary>http://security.debian.org/debian-security stretch/updates main</binary>
> </url>
> </url-list>
>
> That works as expected in most cases, i.e. version 2.2.2-2 of
> some-package gets installed in the resulting RFS image. However, if
> "some-package" happens to be part of the base system (the set of
> packages installed by debootstrap before <pkg-list/> gets processed),
> the version 1.1.1-1 gets installed instead. Apparently elbe does not
> upgrade packages installed by debootstrap, even though newer versions
> are available from secondary mirrors.
>
> How can I get the newest available version of a package that belongs
> to the base system?

How about adding a finetuning command?

    <command>apt-get -y upgrade</command>

John Ogness