Assert error when there are multiple shlib_providers for the same file #50
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In the case where multiple packages provide the same file, we want to assert an error. Otherwise, python will generate a different build depending on which provider appears first in the dictionary. On my system this order changes every time I run bitbake causing intermittent build differences. Signed-off-by: Jonathan Marler <[email protected]>
marler8997
force-pushed
the
assertMultiShlibs
branch
from
26651b5 to
bf37464
Compare
Contributor
Author
|
@kergoth helped me submit this to the mailing list manually via create-pull-request and copying the cover-letter and email fields to gmail manually. I'm closing NOT because I'm abandoning the change but because I will now be using the mailing list from here on. |
halstead
pushed a commit
that referenced
this pull request
Feb 23, 2022
determinism.patch removed since it's included in 0.20.5 Changelog: ========= * Drop autotools-based build [!44] * Use G_GNUC_NULL_TERMINATED where appropriate [!65] * collection, methods, prompt: Port to GTask [!66, !93] * Detect local storage in snaps in the same way as flatpaks [!67] * Add bash-completion for secret-tool [!70, #50, !72] * secret-tool: Add locking capabilities to secret tool [#28, !75] * secret-file-backend: Avoid closing the same file descriptor twice [!78] * Add support for TPM2 based secret storage [!83, !90, !95] * Create default collection after DBus.Error.UnknownObject [!94] * Port documentation to gi-docgen [!101] * GI annotation and documentation fixes [!63, !64, !102, !103, #66] * Build fixes [#54, !62, !68, #59, !73, !77, !82, !84, !85, !88] * Updated translations Signed-off-by: Wang Mingyu <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
halstead
pushed a commit
that referenced
this pull request
Feb 23, 2022
determinism.patch removed since it's included in 0.20.5 Changelog: ========= * Drop autotools-based build [!44] * Use G_GNUC_NULL_TERMINATED where appropriate [!65] * collection, methods, prompt: Port to GTask [!66, !93] * Detect local storage in snaps in the same way as flatpaks [!67] * Add bash-completion for secret-tool [!70, #50, !72] * secret-tool: Add locking capabilities to secret tool [#28, !75] * secret-file-backend: Avoid closing the same file descriptor twice [!78] * Add support for TPM2 based secret storage [!83, !90, !95] * Create default collection after DBus.Error.UnknownObject [!94] * Port documentation to gi-docgen [!101] * GI annotation and documentation fixes [!63, !64, !102, !103, #66] * Build fixes [#54, !62, !68, #59, !73, !77, !82, !84, !85, !88] * Updated translations Signed-off-by: Wang Mingyu <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I know this isn't the way to submit patches I'm currently having a hard time figuring out how to configure
git send-emailto go through a proxy. I can fetch/push changes to repositories via any protocol on any port, butgit send-emailseems to ignore the proxy settings. It seems likegit send-emaildoesn't support proxies so I'm not sure what to do here.Commit Description
In the case where multiple packages provide the same file, we want to assert an error. Otherwise, python will generate a different build depending on which provider appears first in the dictionary. On my system this order changes every time I run bitbake causing different runtime dependencies every time I run the build.