-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown buildreqs should be removed from buildreq_cache #480
Labels
bug
A defect in autospec's operation
Comments
phmccarty
added a commit
to phmccarty/autospec
that referenced
this issue
Jan 11, 2020
The buildreq cache should only contain names/symbols/etc that are resolvable at build time. The names may indicate missing packages, but they may also be invalid, so it is best to avoid adding the names to the cache in the first place. Fixes clearlinux#480 Signed-off-by: Patrick McCarty <[email protected]>
phmccarty
added a commit
to phmccarty/autospec
that referenced
this issue
Jan 11, 2020
The buildreq cache should only contain names/symbols/etc that are resolvable at build time. The names may indicate missing packages, but they may also be invalid, so it is best to avoid adding the names to the cache in the first place. Fixes clearlinux#480 Signed-off-by: Patrick McCarty <[email protected]>
phmccarty
added a commit
to phmccarty/autospec
that referenced
this issue
Jan 11, 2020
The buildreq cache should only contain names/symbols/etc that are resolvable at build time. The names may indicate missing packages, but they may also be invalid, so it is best to avoid adding the names to the cache in the first place. Fixes clearlinux#480 Signed-off-by: Patrick McCarty <[email protected]>
phmccarty
added a commit
to phmccarty/autospec
that referenced
this issue
Jan 13, 2020
The buildreq cache should only contain names/symbols/etc that are resolvable at build time. The names may indicate missing packages, but they may also be invalid, so it is best to avoid adding the names to the cache in the first place. If the name is only present in the cache, retry the build. Any presence of the name in buildreq_add will halt the build. Fixes clearlinux#480 Signed-off-by: Patrick McCarty <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If an unknown buildreq is detected for a particular build round, autospec adds that buildreq to
buildreq_cache
. Autospec should avoid adding the unknown buildreq tobuildreq_cache
to avoid the need to manually remove it in later autospec runs.Typically, the user will add the missing buildreq, or
buildreq_ban
it, so this is not an urgent issue to fix.The text was updated successfully, but these errors were encountered: