Closed #2574 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2574#event-9831818911
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint ma
Life is confusing and RPM reflects that. There is no bug here and we are not
changing the version comparison breaking thousands of packages.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2574#issuecomment-1637196292
You are receiving
I may well be the intended behavior, but my opinion is that it is really
confusing.
For example,
```
$ rpmdev-vercmp 1.7.0a 1.7.0b
1.7.0a < 1.7.0b
```
is quite understandable, as it is evaluated as `rpmdev-vercmp 1.7.0.a 1.7.0.b`,
but
```
$ rpmdev-vercmp 1.7.0.1a 1.7.0.ab
1.7.0.1a > 1.7.0.ab
```
originally filed here:
https://pagure.io/rpmdevtools/issue/113
As I said in that ticket, I don't think this is a bug. It's a result of
concatenating date + commit hash without separator character - hexadecimal
commit hashes start with different number of decimal digits - so even a number
that s
Trying to compare two package versions with snapshot information produces wrong
comparison:
```
$ rpmdev-vercmp 1.7.0~202307168f43b0b 1.7.0~20230709062d5b2
1.7.0~202307168f43b0b < 1.7.0~20230709062d5b2
```
The first has `~20230716...` so it should evaluate higher than `~20230709`.
The version com
