Re: Better way to handle apt cache needed

["Moessbauer, Felix" <felix.moessbauer@siemens.com>]

On Fri, 2022-12-30 at 09:27 +0100, Roberto A. Foglietta wrote:
> On Fri, 30 Dec 2022 at 07:05, Moessbauer, Felix
> <felix.moessbauer@siemens.com> wrote:
> > 
> > On Fri, 2022-12-30 at 00:15 +0100, Roberto A. Foglietta wrote:
> > > Hi all,
> > > 
> > > I did some changes to reduce disk usage and to speed up the
> > > building.
> > > The results are quite impressing so, before everything else I am
> > > going
> > > to show you the numbers:
> > > 
> > > results before and after the changes
> > > 
> > > 43954 Mb (max)   |  8657 Mb (max)
> > > 26548 Mb (rest)  |  4118 Mb (rest)
> > >  3741 Mb (deb)   |  3741 Mb (deb)
> > >   820 Mb (wic)   |   820 Mb (wic)
> > > 11789 Mb (cache) |   579 Mb (cache)
> > > time: 8m33s      | time: 4m34s
> > > 
> > > The changes has been committed on the default branch (evo) on my
> > > ISAR
> > > fork
> > > 
> > >  https://github.com/robang74/isar
> > > 
> > > * 9fd5282 - changes for a faster build using less disk space, p.1
> > 
> > Hi Roberto,
> > 
> > I tested your patches. In general, the implemented pattern looks
> > good
> > and also result in significantly shorter build times on virtual
> > file
> > systems.
> > 
> > But I discovered some issues on partial rebuilds. Example:
> > > ln: will not overwrite just-created
> > > '/build/tmp/deploy/buildchroot-
> > target/debian-bullseye-amd64/var/cache/apt/archives/libnet-ssleay-
> > perl_1.88-3+b1_arm64.deb' with '/build/downloads/deb/debian-
> > bullseye/libnet-ssleay-perl_1.88-3+b1_arm64.deb'
> > 
> > This happens in the do_install_npm in the npm class of meta-iot2050
> > [1].
> > It could also be an issue with an older sstate cache artifact, or
> > related to the specific implementation in the NPM class.
> > Needs further investigation.
> > 
> > [1]
> > https://github.com/siemens/meta-iot2050/blob/master/classes/npm.bbclass#L105
> 
> Hi Felix, try als with the 2nd part which do not force overwriting of
> exporting packages
> 
> 281bcdd - changes for a faster build using less disk space, p.2

It looks like this did the trick. At least during the last hour I did
not see issues anymore.

> 
> I got this error in building the iot2050 project as proposed in
> README.md:
> 
> ./kas-container build kas-iot2050-example.yml:kas/opt/sdk.yml
> 
> ERROR: python-absl-0.15.0-2-r0 do_fetch: Fetcher failure: Recipe uses
> a floating tag/branch without a fixed SRCREV yet doesn't call
> bb.fetch2.get_srcrev() (use SRCPV in PV for OE).

This is expected, as the meta-coral layer is NOT prepared for bitbake
2.0 yet (same as meta-iot2050). Here, the reason is that bitbake 2.0
does no longer allow git tags as SRCREV, but only SHAs.

> ERROR: Logfile of failure stored in:
> /build/tmp/work/iot2050-debian-arm64/python-absl/0.15.0-2-
> r0/temp/log.do_fetch.746
> ERROR: Task (/build/../work/meta-coral/recipes-python/python-
> absl/python-absl_0.15.0-2.bb:do_fetch)
> failed with exit code '1'
> 
> The only change that I make, is to use my ISAR and obviously I
> converted the syntax to the new bitbake 2.0

Please don't mix things up as this makes the review and testing of
patches much harder. Bitbake 2.0 is not yet integrated in ISAR next, so
please also base your patches on top on ISAR next only.

And please also try to send the patches to the ML (at least the final
versions). While Github is good to get a first overview, it is
impossible to review there (at least in the current working mode) and
this is also not how contributions shall be done in ISAR.

Felix

> 
> Best regards, R-