You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HI,
I'm building package for p4lang-p4c , while it has worked perfectly for 2 years.
Not sure why, set_version append to changelog -0 to obs_scm-versionformat. The result is that this breaks debuild build mentioning:
dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision
Looking at the log shows indeed that the issue is related to p4c_202110209b969dd6e1.2.2~nightly-0
It should not be -0. I tried various solution in order to change this, without luck.
Can you please let me know if there is a work around so that we can recover a changelog version such as p4c_202110209b969dd6e1.2.2~nightly-0+40.1 for example (+40.1 being an example, not sure if this is a random number)
PS: I'm not sure if the issue is on set_version or more globally to obs_scm. Feel free to change the issue queue in the relevant software.
Thanks !
Frederic
The text was updated successfully, but these errors were encountered:
I found the culprit ! Basically the software (from an external repository) i cloned during obs_scm build had included recently a debian folder. This debian folder has a file format in source sub-folder that forced quilt to 3.0. DEBTRANSFORM only support quilt format 1.0. Do you know if it is possible to force the usage of quilt from OBS using _service or use a specific tag in dsc file ?
frederic-loui
changed the title
set_version set package version to "-0"
obs_scm set package version to "-0"
Nov 4, 2021
HI,
I'm building package for p4lang-p4c , while it has worked perfectly for 2 years.
Not sure why, set_version append to changelog -0 to obs_scm-versionformat. The result is that this breaks debuild build mentioning:
dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision
Looking at the log shows indeed that the issue is related to p4c_20211020
9b969dd6e1.2.2~nightly-0It should not be -0. I tried various solution in order to change this, without luck.
Can you please let me know if there is a work around so that we can recover a changelog version such as p4c_20211020
9b969dd6e1.2.2~nightly-0+40.1 for example (+40.1 being an example, not sure if this is a random number)PS: I'm not sure if the issue is on set_version or more globally to obs_scm. Feel free to change the issue queue in the relevant software.
Thanks !
Frederic
The text was updated successfully, but these errors were encountered: