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

[Manuel Traut]

On Thu, Feb 08, 2018 at 11:27:29AM +0100, John Ogness wrote:
> On 2018-02-08, Lukasz Walewski <lwalewski at s-can.at> wrote:
> >>> 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>
> >
> > Yes, that (sort of) works! I came up with this idea myself, but I
> > consider it to be a hack rather than a solution. The default behavior
> > for base system packages is different from that for all other
> > packages, which is extremely confusing: the user doesn't have to know
> > which packages are "base system" and which are not. Besides, that
> > might change without notice and is out of control of elbe.
> >
> > Another disadvantage of the above is that the version reported in the
> > "Installed Packages List" section of elbe-report.txt is the "base
> > system" version and not the actually installed version. In particular,
> > the version reported there is wrong, if the package was upgraded in
> > <finetuning/>.
> >
> > Any other ideas?
> 
> Change elbe so that it automatically upgrades packages after completing
> debootstrap.
> 
> Looking at the code, it might be enough to do something like this
> (untested):
> 
> --- a/elbepack/elbeproject.py
> +++ b/elbepack/elbeproject.py
> @@ -661,7 +661,7 @@ class ElbeProject (object):
>              for p in self.xml.node("debootstrappkgs"):
>                  debootstrap_pkgs.append(p.et.text)
>  
> -            pkgs = self.buildenv.xml.get_target_packages()
> +            pkgs = self.buildenv.xml.get_target_packages() + debootstrap_pkgs
>  
>              if buildenv:
>                  pkgs = pkgs + self.buildenv.xml.get_buildenv_packages()

Probably also needed to ensure that the same result is produced if rebuilding
from bin-cdrom.iso because there debootstrap will always use the newer package,
because the repos are merged.