Ticket #210 (closed defect: fixed)

Opened 12 years ago

Last modified 12 years ago

"now" causes frequent rebuilds and fills disks

Reported by: werner@… Owned by: henryk@…
Priority: high Milestone:
Component: OE bitbake recipes / build system Version: current svn head
Severity: major Keywords:
Cc: buglog@…, henryk@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:


Packages that reflect the "now" state, such as the kernel, are rebuilt
on each "bitbake openmoko-devel-image" or similar. This not only wastes
time, but due to how bitbake caches old builds, it also consumes disk
space rapidly, possibly causing hard to find unrelated failures.

Change History

comment:1 Changed 12 years ago by hrw@…

consider updating bitbake to 1.6.6 to get better SVN fetcher

comment:2 Changed 12 years ago by laforge@…

  • Owner changed from mickey@… to henryk@…
  • Cc henryk@… added

I have written a proof-of-concept implementation against bitbake-1.6.2 which
calls 'svn info' on the repository to obtain the current revision number and
then use this for tarball filenames and within PR.

Henryk (new owner of this bug) has more of a clue about python and will clean it
up and port it to other fetchers (git at least), and then merge it with current
upstream bitbake.

Henryk: Please have a look at bitbake 1.6.6 and see whether the new svn fetcher
would help us.

comment:3 Changed 12 years ago by henryk@…

  • Status changed from new to assigned

bitbake 1.6.6 doesn't help here: its SVN fetcher now keeps the working directory
(instead of deleting it) and does an svn update when it finds an already checked
out working directory. This saves download volume on subsequent builds but does
not solve the "it's building the same code again" problem.

Will take Harald's PoC code and implement revision awareness for svn and co.
(based on bitbake 1.6.6 because there's also some other bugfixes in there.)

comment:4 Changed 12 years ago by henryk@…

Status update: I have some temporary fix in place which is good enough to work
and for example is in MokoMakefile?. This includes a modified base.bbclass in
which is in openmoko svn and a patched bitbake 1.6.6 with patch

Note that this is not the right way as appending to PR is not something that
should be done.

I had a discussion on bitbake-devel about how this should be done and am
currently implementing a more elegant solution in bitbake 1.8. (Reason for 1.8
and not 1.6: Some of the changes which I already made locally have already
independently made in bitbake 1.8, reducing the amount of code changes.)

comment:5 Changed 12 years ago by alphaone@…

With bitbake-1.8.8 rmwork is working again and the SRCREV feature only rebuilds
an application if there is a new revision.
Does this fix your problem?

comment:6 Changed 12 years ago by mickey@…

  • Status changed from assigned to closed
  • Resolution set to fixed

Fixed thanks to BitBake? 1.8.8.

Note: See TracTickets for help on using tickets.