-
Notifications
You must be signed in to change notification settings - Fork 376
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
feat: Enhance the RPM build #1522
Merged
Merged
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
MichaelsJP
force-pushed
the
fix/rpmbuild
branch
5 times, most recently
from
August 8, 2023 16:23
2050fad
to
5434f79
Compare
MichaelsJP
force-pushed
the
fix/rpmbuild
branch
20 times, most recently
from
August 9, 2023 15:35
1c94201
to
7e5b14f
Compare
jhaeu
requested changes
Aug 10, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent, much work! Just some small notes.
MichaelsJP
force-pushed
the
fix/rpmbuild
branch
6 times, most recently
from
August 11, 2023 10:06
a3cc0ff
to
ab0d17e
Compare
A base script provides abstract check functions. The three check scripts test the docker container before and after the installation and after removing to ensure that the installation environment is at all times as expected. The spec file now enforces fixed file permissions. The github workflow now signs, builds, installs, uninstalls and checks the rpm file at any given point.
MichaelsJP
force-pushed
the
fix/rpmbuild
branch
from
August 11, 2023 11:27
473bd4a
to
4b9a250
Compare
jhaeu
requested changes
Aug 11, 2023
Co-authored-by: jhaeu <138764906+jhaeu@users.noreply.github.com>
…ng checks This allows the user to see the complete environment check even if one fails. That should allow for quicker bug fixing.
jhaeu
approved these changes
Aug 11, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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.
Pull Request Checklist
have been resolved.
[Unreleased] heading.
along with a short description of what it is for, and documented this in the Pull Request (below).
(at least Germany), and the graphs build without problems (i.e. no out-of-memory errors).
importer etc.), I have generated longer distance routes for the affected profiles with different options
(avoid features, max weight etc.) and compared these with the routes of the same parameters and start/end
points generated from the current live ORS.
If there are differences then the reasoning for these MUST be documented in the pull request.
and why the change was needed.
Fixes # .
Information about the changes
Examples and reasons for differences between live ORS routes, and those generated from this pull request
Required changes to ors config (if applicable)