-
Notifications
You must be signed in to change notification settings - Fork 1
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
Initial Fedora packaging #1
Conversation
|
The errors in question during build: Happened during this build in COPR: Similar error happens when I try to do a build locally using mock. Googling for the error messages I have found this Gist: As for why using 2.6.0 - I've tried also tried 2.4.8 and 2.5.0 and got the same error for both. If using 2.6.0 would be a problem for OSM Scout Server I can certainly package an older version. :) |
|
2.6.0: this shouldn't be a problem, so go ahead. proto/osmformat.proto is a symlink to OSM-binary/src/osmformat.proto, which is submodule. So, we would need to clone it with submodules to resolve it. Alternative, I think, is to disable data tools, as I did for SFOS. However, it would probably be nice to have them available on Fedora. Let's try to fix the build before merging? :) [although, I have to go to sleep now] |
OK. :)
So that basically means their release tarball from GitHub is broken. :) I'll try to create a proper one myself then. :)
Definitely no pressure, this can certainly wait a day or two. :) |
Changes from Sailfish OS packaging: - rebased to 2.6.0 - libzmq-devel is called zeromq-devel on Fedora - libzmq is called zeromq on Fedora - added Python devel BuildRequires - added boost-python2-devel BuildRequires (looks like Valhalla needs Python 2 version of this during build ?) - added lua-devel BuildRequires - added sqlite-devel BuildRequires - added geos-devel BuildRequires - added libspatialite-devel BuildRequires - added some glibc packages as build-requires in a vain attempt to fix the protocol buffer issues during build - fixed the %setup line - disabled a Fedora Python 2 deprecation check for now (Valhalla apparently uses unversioned Python shebang somewhere in its scripts) - removed redundant %files section - disabled debug package generation for now (causes build to fail) - disabled the Python 2 only bindings, asked upstream about Python 3 plans[0] - removed static lib from %files (we build as a dynamic lib on Fedora) Note about the tarball: the tarball generated by GitHub does not contain submodules, so a custom tarball with appropriate tools[1] needs to be generated. [0] valhalla/valhalla#1325 [1] https://github.com/meitar/git-archive-all.sh
d536165
to
56af04b
Compare
|
I've updated the PR:
With these changes and the fixed tarball that includes submodules Valhalla finally builds locally in mock and hopefully should build in COPR as well (running at the moment): I've also reported the broken tarballs upstream: valhalla/valhalla#1324 It's pretty crazy that GitHub does not include submodules in tarballs (given how often those are used) and that even git itself still does not support (AFAIK) directly creating archives that include submodules. |
|
Excellent, it seems that CORP is fine as well! |
NOTE: currently fails to build due to some weird protocol buffer issues
Changes from Sailfish OS packaging:
needs Python 2 version of this during build ?)
attempt to fix the protocol buffer issues during build
(Valhalla apparently uses unversioned Python shebang somewhere
in its scripts)