Version bump: libodb-sqlite-2.5.0_beta27 and remove old nonworking ebuild #49
Conversation
This file contains 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
|
dev-util/build2 seems to have libodb-sqlite-2.5.0_beta25 hardcoded in build2-toolchain-0.16.0/bpkg/bpkg/version.hxx, meaning that it doesn't compile after the version bump. I'm unsure if the correct course of action is to submit a pull request against build2 or create a patch for it in this repo that changes the hardcoded version number. |
|
This issue has been fixed in this commit. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
beta25 no longer available at https://cppget.org/libodb-sqlite so the package won't build, version bumped to beta27.
This is the first time I've changed a Portage repo, so I'd appreciate if someone could double-check my work to make sure I didn't break or forget anything. The package does build for me after making this change.