-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Cannot build Bisq rpm on Debian 10.3 VM #4006
Comments
I think we something similar already in Windows as far as I remember (@devinbileck) Not super high prio IMO, but probably nice to get it fixed at some point. |
This is a duplicate of #2860. We could restore this behaviour to strip everything after the dash. |
Yes, it was removed by mistake in this merge be70eb1. As it was me I'll create a quick PR for it 😬 |
Description
The desktop/package/linux/package.sh script fails while trying to create an rpm for version=1.2.7-SNAPSHOT
Version
1.2.7-SNAPSHOT
Steps to reproduce
Expected behaviour
Bisq-1.2.7-SNAPSHOT.deb and Bisq-1.2.7-SNAPSHOT.rpm are created with no errors.
Actual behaviour
Bisq-1.2.7-SNAPSHOT.rpm could not be created because of the hyphen in the rpm version.
Device or machine
Debian 10.3 VM running inside Ubuntu 18.0.4
Intel i7, Nvidia GTX 960
Additional info
package.sh debug output:
rpm-build-error.log
According to https://twiki.cern.ch/twiki/bin/view/Main/RPMAndDebVersioning
According to https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-version:
Debian 10.3 can create Bisq-1.2.7-SNAPSHOT.deb, but not Bisq-1.2.7-SNAPSHOT.rpm
Workaround:
I created the rpm Bisq-1.2.7+SNAPSHOT.rpm on Debian 10.3 by creating a variable in linux/package.sh that replaces "-" with a valid "+"
and substituting $rpmVersion for $version in the rpm generation related code in package.sh.
I also created Bisq-1.2.7SNAPSHOT.rpm by replacing "-" with "".
The Bisq-1.2.7+SNAPSHOT.rpm file I created on the debian vm was installed using dnf on another rpm based fedora vm; it created the fedora menu item and bisq started with no problems.
The text was updated successfully, but these errors were encountered: