Bug 2007854

Summary: cadvisor-0.44.1 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: cadvisorAssignee: Jan Chaloupka <jchaloup>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: eparis, go-sig, jchaloup, vbatts
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cadvisor-0.44.1-1.fc37 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-11 08:16:53 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 0.44.0 (#2007854) none

Description Upstream Release Monitoring 2021-09-25 14:23:39 UTC
Latest upstream release: 0.41.0-containerd-fix-rc.1
Current version/release in rawhide: 0.40.0-2.fc36
URL: https://github.com/google/cadvisor

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

Comment 1 Upstream Release Monitoring 2021-09-25 14:23:42 UTC
Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-fbrvyovc/cadvisor.spec'] returned 1: b"error: line 31: Illegal char '-' (0x2d) in: Release:        containerd-fix-rc.1\n"

Comment 2 Upstream Release Monitoring 2021-10-12 13:49:32 UTC
Latest upstream release: 0.42.0
Current version/release in rawhide: 0.40.0-2.fc36
URL: https://github.com/google/cadvisor

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

Comment 3 Upstream Release Monitoring 2021-10-12 13:49:36 UTC
Skipping the scratch build because an SRPM could not be built: ['git', 'commit', '-a', '-m', 'Update to 0.42.0 (#2007854)'] returned 1: b'On branch rawhide\nYour branch is up to date with \'origin/rawhide\'.\n\nUntracked files:\n  (use "git add <file>..." to include in what will be committed)\n\tSRPMS/\n\nnothing added to commit but untracked files present (use "git add" to track)\n'

Comment 4 Upstream Release Monitoring 2021-11-10 21:40:31 UTC
Latest upstream release: 0.43.0
Current version/release in rawhide: 0.40.0-2.fc36
URL: https://github.com/google/cadvisor

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

Comment 5 Upstream Release Monitoring 2021-11-10 21:40:35 UTC
An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!

Comment 6 Upstream Release Monitoring 2022-03-01 19:13:01 UTC
Latest upstream release: 0.44.0
Current version/release in rawhide: 0.40.0-3.fc36
URL: https://github.com/google/cadvisor

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

Comment 7 Upstream Release Monitoring 2022-03-01 19:13:07 UTC
Created attachment 1863750 [details]
Update to 0.44.0 (#2007854)

Comment 8 Upstream Release Monitoring 2022-03-01 19:26:56 UTC
the-new-hotness/release-monitoring.org's scratch build of cadvisor-0.44.0-1.fc34.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=83523535

Comment 9 Upstream Release Monitoring 2022-04-26 16:18:58 UTC
Latest upstream release: 0.44.1
Current version/release in rawhide: 0.40.0-3.fc36
URL: https://github.com/google/cadvisor

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

Comment 10 Upstream Release Monitoring 2022-04-26 16:19:03 UTC
Scratch build failed. Details below:

GenericError: File upload failed: cli-build/1650989941.70223.xnFsbsld/cadvisor-0.44.1-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 3053, in uploadWrapper
    self.fastUpload(localfile, path, name, callback, blocksize, overwrite, volume=volume)
  File "/usr/lib/python3.9/site-packages/koji/__init__.py", line 2988, 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 11 Fedora Update System 2022-06-11 08:15:33 UTC
FEDORA-2022-b8b53260ba has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b8b53260ba

Comment 12 Fedora Update System 2022-06-11 08:16:53 UTC
FEDORA-2022-b8b53260ba has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.