Bug 2047688

Summary: libnfs-5.0.2 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: libnfsAssignee: Xavier Bachelot <xavier>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: ross
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libnfs-5.0.2-2.fc39 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-02 16:16:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Update to 5.0.1 (#2047688)
none
Update to 5.0.2 (#2047688) none

Description Upstream Release Monitoring 2022-01-28 09:56:25 UTC
Latest upstream release: 5.0.0
Current version/release in rawhide: 4.0.0-6.fc36
URL: https://github.com/sahlberg/libnfs

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/7325/

Comment 1 Upstream Release Monitoring 2022-01-28 09:56:29 UTC
Scratch build failed. Details bellow:

GenericError: File upload failed: cli-build/1643363788.5062218.UwEKaQhT/libnfs-5.0.0-1.fc34.src.rpm
Traceback:
  File "/usr/local/lib/python3.9/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.9/site-packages/hotness/builders/koji.py", line 198, in build
    output["build_id"] = self._scratch_build(session, package.name, srpm)
  File "/usr/local/lib/python3.9/site-packages/hotness/builders/koji.py", line 451, in _scratch_build
    session.uploadWrapper(source, serverdir)
  File "/usr/lib/python3.9/site-packages/koji/__init__.py", line 3000, in uploadWrapper
    self.fastUpload(localfile, path, name, callback, blocksize, overwrite, volume=volume)
  File "/usr/lib/python3.9/site-packages/koji/__init__.py", line 2935, in fastUpload
    raise GenericError("File upload failed: %s/%s" % (path, name))

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

Comment 2 Upstream Release Monitoring 2022-02-01 09:33:07 UTC
Latest upstream release: 5.0.1
Current version/release in rawhide: 4.0.0-6.fc36
URL: https://github.com/sahlberg/libnfs

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/7325/

Comment 3 Upstream Release Monitoring 2022-02-01 09:33:10 UTC
Created attachment 1858287 [details]
Update to 5.0.1 (#2047688)

Comment 4 Upstream Release Monitoring 2022-02-01 09:42:39 UTC
the-new-hotness/release-monitoring.org's scratch build of libnfs-5.0.1-1.fc34.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=82228387

Comment 5 Upstream Release Monitoring 2022-08-10 20:50:49 UTC
Releases retrieved: 5.0.2
Upstream release that is considered latest: 5.0.2
Current version/release in rawhide: 4.0.0-7.fc37
URL: https://github.com/sahlberg/libnfs

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/7325/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/libnfs

Comment 6 Upstream Release Monitoring 2022-08-10 20:50:54 UTC
Created attachment 1904813 [details]
Update to 5.0.2 (#2047688)

Comment 7 Upstream Release Monitoring 2022-08-10 20:57:54 UTC
the-new-hotness/release-monitoring.org's scratch build of libnfs-5.0.2-1.fc36.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=90686118

Comment 8 Fedora Admin user for bugzilla script actions 2023-03-30 00:09:51 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 9 Fedora Update System 2023-06-02 15:59:46 UTC
FEDORA-2023-e3d7be44f2 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e3d7be44f2

Comment 10 Fedora Update System 2023-06-02 16:16:29 UTC
FEDORA-2023-e3d7be44f2 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.