Bug 14218 - Recipe rebuilds can contaminate builds (and sstate)
Summary: Recipe rebuilds can contaminate builds (and sstate)
Status: NEW
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 3.3
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 6.1 M2
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2021-02-04 15:30 UTC by Richard Purdie
Modified: 2026-05-07 15:02 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Purdie 2021-02-04 15:30:51 UTC 
bitbake core-image-sato-sdk
with glibc 2.33
then revert back to glibc 2.32
bitbake core-image-sato-sdk

and see failures in:

syslinux
perl
avahi
btrfs-tools
iproute2
libcap
zip
unzip

all referencing symbols (GLIBC_2.33) which no longer exist.
Comment 1 Randy MacLeod 2021-02-04 16:07:49 UTC 
pulseaudio is also affected.

It would be nice to be able to test for this more frequently.
Only affects downgrades so you'd have to use separate build directories.
Comment 2 Randy MacLeod 2023-07-26 21:22:04 UTC 
Bulk move of 64 bugs to 4.3 M3 after a quick review.
If a bug is actually fixed, please add a commit link and resolve it.
-- Randy for YP bug team.
Comment 3 Trevor Gamblin 2023-09-14 16:43:59 UTC 
Moved to M4.
Comment 4 Randy MacLeod 2023-10-30 15:29:14 UTC 
Bulk move to 5.0 M1. -- Randy
Comment 5 Randy MacLeod 2023-12-21 23:28:28 UTC 
Bulk move of 52 5.0-M1 bugs to M2.
Comment 6 Randy MacLeod 2024-01-25 14:28:52 UTC 
Bulk move of bugs owned by "unassigned" from 5.0-M2 to 5.0-M3.
Comment 7 Randy MacLeod 2024-02-22 19:53:18 UTC 
Bulk move of bugs from 5.0-M3 to 5.99.
The bugs in this list are all unassigned and are ones that I consider to be nice to do some time but not essential track from milestone to milestone in 5.0 or 5.1. We agreed on this bug handling approach in the YP bug review on Feb 22, 2024.

If you disagree, please move back to a 5.[012...]-M* milestone.