17 Sep
2017
17 Sep
'17
7:17 p.m.
Hi ,
i’m trying to build osmo-trx master branch .
What i’am doing :
autoreconf -i
./configure
make
In make step i get this error :
Evaluating ‘parse’ option: ‘(?P\d+).(?P\d+).(?P\d+)’ does not parse
current version 'P2.8TRUNK’
usage: bumpversion [-h] [–config-file FILE] [–verbose] [–list]
[–allow-dirty] [–parse REGEX] [–serialize FORMAT]
[–search SEARCH] [–replace REPLACE]
[–current-version VERSION] [–dry-run] --new-version
VERSION [–commit | --no-commit] [–tag | --no-tag]
[–tag-name TAG_NAME] [–message COMMIT_MSG]
part [file [file …]]
bumpversion: error: the following arguments are required: --new-version
make all-recursive
18 Sep
18 Sep
3:38 a.m.
Hi Mohammad,
I hope that Max has some more on this, but AFAIK the 'bumpversion' part has
been added recently as part of the "release helper from libosmocore", currently
osmo-trx's last master revision.
As a workaround until the problem is clear, you could try to revert the last
master revision and try rebuilding with that:
git revert 099a44abfbe9f573ae553ba24945ef452c9982b8
autoreconf -fi
./configure
make
'bumpversion' has been discussed elsewhere, with an indication that we may want
to remove this dependency again. It should anyway just be needed for making a
release, I'm not sure why this appears during normal build from source.
~N
On Sun, Sep 17, 2017 at 08:47:00PM +0430, mohammad nejati wrote:
Hi ,
i’m trying to build osmo-trx master branch .
What i’am doing :
autoreconf -i
./configure
make
In make step i get this error :
Evaluating ‘parse’ option: ‘(?P\d+).(?P\d+).(?P\d+)’ does not parse
current version 'P2.8TRUNK’
usage: bumpversion [-h] [–config-file FILE] [–verbose] [–list]
[–allow-dirty] [–parse REGEX] [–serialize FORMAT]
[–search SEARCH] [–replace REPLACE]
[–current-version VERSION] [–dry-run] --new-version
VERSION [–commit | --no-commit] [–tag | --no-tag]
[–tag-name TAG_NAME] [–message COMMIT_MSG]
part [file [file …]]
bumpversion: error: the following arguments are required: --new-version
make all-recursive
--
- Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte
21 Sep
21 Sep
1:39 p.m.
On 18.09.2017 02:38, Neels Hofmeyr wrote:
'bumpversion' has been discussed elsewhere,
with an indication that we may want
to remove this dependency again. It should anyway just be needed for making a
release, I'm not sure why this appears during normal build from source.
It's already removed as of 98f6482ec7eb603b17e5a99fb92d28c17fcf61e9 in
libosmocore.
Also, https://gerrit.osmocom.org/#/c/3973/ suppress error message. I don't believe it
have anything to do with the build problem but let's wait for complete logs.
--
Max Suraev <msuraev(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
4:09 p.m.
On Thu, Sep 21, 2017 at 12:39:11PM +0200, Max wrote:
On 18.09.2017 02:38, Neels Hofmeyr wrote:
This is not accurate. You have removed the debian packaging dependency on
bumpversion, but you are still using it from libosmocore, which IMHO is a
questionable approach. The idea was to not use bumpversion *at all*.
Could you explain briefly what the input and output of the bumpversion step
are? Like, does it always bump the patch version, never the minor or major
versions?
I would expect version bumping to be a human choice, i.e. I decide to tag a new
release with patch, minor or major version bumped, then 'make release' takes
that tag's version as a basis?
If tagging should happen automatically, we could ask the user to enter the new
version at a prompt or by makefile parameter.
'bumpversion' has been discussed
elsewhere, with an indication that we may want
to remove this dependency again. It should anyway just be needed for making a
release, I'm not sure why this appears during normal build from source.
It's already removed as of 98f6482ec7eb603b17e5a99fb92d28c17fcf61e9 in libosmocore.
Also, https://gerrit.osmocom.org/#/c/3973/ suppress
error message.
Nice, added review.
I don't believe it have anything to do with the
build problem
Indeed, probably not.
~N
--
- Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte
18 Sep
18 Sep
12:07 p.m.
That's odd - I've seen this error message but it never prevented the binaries
from
being built. That's why I haven't come around to fixing this yet.
Could you please attach the complete output of 'make' command and your
config.log?
On 17.09.2017 18:17, mohammad nejati wrote:
Evaluating ‘parse’ option: ‘(?P\d+).(?P\d+).(?P\d+)’
does not parse
current version 'P2.8TRUNK’
usage: bumpversion [-h] [–config-file FILE] [–verbose] [–list]
[–allow-dirty] [–parse REGEX] [–serialize FORMAT]
[–search SEARCH] [–replace REPLACE]
[–current-version VERSION] [–dry-run] --new-version
VERSION [–commit | --no-commit] [–tag | --no-tag]
[–tag-name TAG_NAME] [–message COMMIT_MSG]
part [file [file …]]
bumpversion: error: the following arguments are required: --new-version
make all-recursive
--
Max Suraev <msuraev(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
2462
days inactive
2466
days old
4 comments
3 participants
participants (3)
-
Max -
mohammad nejati -
Neels Hofmeyr