Latest upstream release: 3.3.17rc1 Current version/release in rawhide: 3.3.16-2.fc34 URL: https://sourceforge.net/projects/procps-ng/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/3708/
Created attachment 1749644 [details] [patch] Update to 3.3.17rc1 (#1919128)
the-new-hotness/release-monitoring.org's scratch build of procps-ng-3.3.17rc1-1.fc32.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=60199058
Latest upstream release: 3.3.17 Current version/release in rawhide: 3.3.16-4.fc34 URL: https://sourceforge.net/projects/procps-ng/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/3708/
An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!
This new version needs "BuildRequires: po4a" to generate localized man pages (shipped as .po files in man-po/). That's why the scratch build didn't work (see comment #4).
Latest upstream release: 4.0.0 Current version/release in rawhide: 3.3.17-4.fc36 URL: https://sourceforge.net/projects/procps-ng/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/3708/
Created attachment 1867430 [details] Update to 4.0.0 (#1919128)
the-new-hotness/release-monitoring.org's scratch build of procps-ng-4.0.0-1.fc34.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=84549191
Please don't use this tarball. The translation sync prior to the tarball creation is failed, and moreover, there was no pre-release tarball before v4.0.0 where translators had a chance to update the .po files. See also https://gitlab.com/procps-ng/procps/-/issues/230.
Shall we CLOSE_DEFERRED as procps-ng-4.0.0 was marked as experimental by upstream [1]? [1] https://gitlab.com/procps-ng/procps/-/issues/230#note_885049094
Yes, but one day there will be released a *real* 4.0.0 … Don't know what to do here. The current (experimental) v4.0.0 is also available from the official SourceForge download page, even from the "Production" releases. I already told the upstream maintainer about the risks of such thoughtless versioning of experimental releases; hope this won't happen anymore in the future. Under such circumstances, we can't even fix anything in the Fedora toolchain which detects new tarballs for packaging, because it would break the detection rules for other tarballs which are versioned correctly.
Or I can mark this CondNAK:Upstream, so we don't forget about this rebase while waiting for the "right" version and close it alternatively later, just for the case the new version will be 4.0.0 also and the version-watch script won't work.
In the Gitlab issue [1], I've proposed to don't use 4.0.0 for the *real* final release, instead 4.0.1 or anything similar. This would keep the version-watch mechanism usable in this case. [1] https://gitlab.com/procps-ng/procps/-/issues/230#note_885559012
(In reply to Mario Blättermann from comment #9) > Please don't use this tarball. The translation sync prior to the tarball > creation is failed, and moreover, there was no pre-release tarball before > v4.0.0 where translators had a chance to update the .po files. See also > https://gitlab.com/procps-ng/procps/-/issues/230. FYI: procps-ng-4.0.0.tar.xz is also available at "Production" dir : https://sourceforge.net/projects/procps-ng/files/Production/
(In reply to Xose Vazquez Perez from comment #14) > (In reply to Mario Blättermann from comment #9) > > Please don't use this tarball. The translation sync prior to the tarball > > creation is failed, and moreover, there was no pre-release tarball before > > v4.0.0 where translators had a chance to update the .po files. See also > > https://gitlab.com/procps-ng/procps/-/issues/230. > > FYI: > > procps-ng-4.0.0.tar.xz is also available at "Production" dir : > https://sourceforge.net/projects/procps-ng/files/Production/ Yes, I saw it yesterday, and I already told Craig Small about the risks of providing such a tarball, silently assuming the users and packagers would also treat it as an experimental one. But I still haven't got an answer. For the time being, there's no 4.0.0 package available anywhere, at least not for the mainstream distributions, but I will keep an eye on them.
Releases retrieved: 4.0.1rc1 Upstream release that is considered latest: 4.0.1rc1 Current version/release in rawhide: 3.3.17-6.fc37 URL: https://sourceforge.net/projects/procps-ng/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/3708/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/procps-ng
Scratch build failed. Details below: BuilderException: Build failed: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-k1baswas/procps-ng.spec']' returned non-zero exit status 1. StdOut: error: Bad source: ./procps-ng-4.0.1rc1.tar.xz: No such file or directory Traceback: File "/usr/local/lib/python3.10/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build result = self.builder.build(request.package, request.opts) File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line 188, in build raise BuilderException( If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues
Releases retrieved: 4.0.1 Upstream release that is considered latest: 4.0.1 Current version/release in rawhide: 3.3.17-8.fc38 URL: https://sourceforge.net/projects/procps-ng/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/3708/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/procps-ng
Created attachment 1919225 [details] Update to 4.0.1 (#1919128)
the-new-hotness/release-monitoring.org's scratch build of procps-ng-4.0.1-1.fc36.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=93242272
Releases retrieved: 4.0.2 Upstream release that is considered latest: 4.0.2 Current version/release in rawhide: 3.3.17-8.fc38 URL: https://sourceforge.net/projects/procps-ng/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/3708/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/procps-ng
Created attachment 1930047 [details] Update to 4.0.2 (#1919128)
the-new-hotness/release-monitoring.org's scratch build of procps-ng-4.0.2-1.fc36.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=94972044
FEDORA-2023-59637e6dd7 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-59637e6dd7
FEDORA-2023-59637e6dd7 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.