Fix spk export failing if builds are missing #800
Merged
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.
In our origin repo there are some traces of a package that may have been partually published, where there are "spec build" tags but no "pkg build" tags, as in:
A new build of this package failed to
spk export
due to these remnants found in the origin repo:This commit takes a minimally invasive approach of ignoring PackageNotFoundError when these are generated about specific builds, as in builds that exist as far as
list_package_builds
is concerned, but fail to be loaded. It will still hard error if one attempts to export a specific build that does not exist.We don't think that we should have to manually remove the "spec build" tags from our origin repo in order for
spk export
to work.