The rpm version disagrees with the libtirpc version that is supposed to be in this update (1.3.6-0.rc1.fc41 versus libtirpc-1-3-7-rc1, respectively), and predates the rpm version that it is supposed to supersede, 1.3.6-0.fc41.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
The rpm version disagrees with the libtirpc version that is supposed to be in this update (1.3.6-0.rc1.fc41 versus libtirpc-1-3-7-rc1, respectively), and predates the rpm version that it is supposed to supersede, 1.3.6-0.fc41.
The latest upstream tag is libtirpc-1-3-7-rc1 and the latest version is 1.3.6-0.rc1... My apologies but I don't see the problem.
Your release package should probably have a release number starting at 1 and then going up. For example: 1.3.6-1. Your RC package should probably be something like: 1.3.7-0.rc1. Right?
The versioning of the previous build (libtirpc-1.3.6-0.fc41) is invalid under the guidelines, but there's no actual version ordering error here, 1.3.6-0.rc1.fc41 is greater than 1.3.6-0.fc41 so this update is higher versioned than the previous build. But in future please don't version packages with just a bare 0 as the release, @steved , it is not in line with the policy and it is unclear what it means. See https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/ for the current versioning guidelines.
I also agree with @bojan that it seems unclear what this package contains. The description of the update says it contains "libtirpc-1-3-7-rc1" but the version is 1.3.6-0.rc1.fc41. Looking into what it actually contains, the sources file says:
...that is, it actually appears to contain 1.3.6 final. However, it includes a single patch, which contains a commit with summary "getnetconfig.c: free linep to avoid memory leakage", and looking at http://git.linux-nfs.org/?p=steved/libtirpc.git;a=summary , we can see that commit is actually the only thing that changed between 1.3.6 final and 1.3.7 rc1.
So it looks like the previous build was actually 1.3.6 final (and so should have been versioned 1.3.6-1), and this build is in fact equivalent to 1.3.7 rc1, so should be versioned 1.3.7-0.1.rc1 (old-style) or 1.3.7~rc1-1 (new-style).
Anyhow, this update seems to have a bigger issue - it consistently causes rpc.mountd to crash when starting nfs-server.service. See https://bugzilla.redhat.com/show_bug.cgi?id=2325584 . Weirdly, this is not happening with the equivalent update for F40 or Rawhide, but it is consistently happening with this update (it's happened 7/7 times the test has run on this update, and never happened on any other F41 update over that time period).
For help debugging failed Fedora CI tests (fedora-ci.*), contact the Fedora CI team.
For help debugging failed Fedora CoreOS tests (coreos.*), contact the Fedora CoreOS team.
For help debugging failed openQA tests (update.*), contact the Fedora Quality team, who will usually investigate and diagnose all failures within 24 hours.
This update has been submitted for testing by steved.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
The rpm version disagrees with the libtirpc version that is supposed to be in this update (1.3.6-0.rc1.fc41 versus libtirpc-1-3-7-rc1, respectively), and predates the rpm version that it is supposed to supersede, 1.3.6-0.fc41.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This update's test gating status has been changed to 'failed'.
This update has been pushed to testing.
It is also possibly functionally broken. See nfs-utils feedback.
This update's test gating status has been changed to 'waiting'.
Works
This update's test gating status has been changed to 'failed'.
The latest upstream tag is libtirpc-1-3-7-rc1 and the latest version is 1.3.6-0.rc1... My apologies but I don't see the problem.
Your release package should probably have a release number starting at 1 and then going up. For example: 1.3.6-1. Your RC package should probably be something like: 1.3.7-0.rc1. Right?
The versioning of the previous build (
libtirpc-1.3.6-0.fc41) is invalid under the guidelines, but there's no actual version ordering error here,1.3.6-0.rc1.fc41is greater than1.3.6-0.fc41so this update is higher versioned than the previous build. But in future please don't version packages with just a bare 0 as the release, @steved , it is not in line with the policy and it is unclear what it means. See https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/ for the current versioning guidelines.I also agree with @bojan that it seems unclear what this package contains. The description of the update says it contains "libtirpc-1-3-7-rc1" but the version is
1.3.6-0.rc1.fc41. Looking into what it actually contains, the sources file says:...that is, it actually appears to contain 1.3.6 final. However, it includes a single patch, which contains a commit with summary "getnetconfig.c: free linep to avoid memory leakage", and looking at http://git.linux-nfs.org/?p=steved/libtirpc.git;a=summary , we can see that commit is actually the only thing that changed between 1.3.6 final and 1.3.7 rc1.
So it looks like the previous build was actually 1.3.6 final (and so should have been versioned
1.3.6-1), and this build is in fact equivalent to 1.3.7 rc1, so should be versioned1.3.7-0.1.rc1(old-style) or1.3.7~rc1-1(new-style).Anyhow, this update seems to have a bigger issue - it consistently causes rpc.mountd to crash when starting
nfs-server.service. See https://bugzilla.redhat.com/show_bug.cgi?id=2325584 . Weirdly, this is not happening with the equivalent update for F40 or Rawhide, but it is consistently happening with this update (it's happened 7/7 times the test has run on this update, and never happened on any other F41 update over that time period).This update has been unpushed.