Bug 2177321

Summary: snapd-2.59.2 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: snapdAssignee: Zygmunt Krynicki <me>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: go-sig, maciek.borzecki, me, ngompa13
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: snapd-2.61.1-0.fc39 snapd-2.61.1-0.fc38 snapd-2.61.1-0.el8 snapd-2.61.1-0.el9 snapd-2.61.1-0.el7 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-01-27 01:28:43 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:

Description Upstream Release Monitoring 2023-03-10 21:36:34 UTC
Releases retrieved: 2.59
Upstream release that is considered latest: 3.9.9-0sdhd5
Current version/release in rawhide: 2.58.3-1.fc39
URL: https://github.com/snapcore/snapd

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


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

Comment 1 Upstream Release Monitoring 2023-03-10 21:36:39 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-rojwbp7c/snapd.spec']' returned non-zero exit status 1.

StdOut:
error: Bad source: ./snapd_3.9.9.no-vendor.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

Comment 2 Upstream Release Monitoring 2023-03-29 13:35:26 UTC
Releases retrieved: 2.59.1
Upstream release that is considered latest: 3.9.9-0sdhd5
Current version/release in rawhide: 2.58.3-1.fc39
URL: https://github.com/snapcore/snapd

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


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

Comment 3 Upstream Release Monitoring 2023-03-29 13:35:30 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-qwsoasfk/snapd.spec']' returned non-zero exit status 1.

StdOut:
error: Bad source: ./snapd_3.9.9.no-vendor.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

Comment 4 Upstream Release Monitoring 2023-04-19 11:03:58 UTC
Releases retrieved: 2.59.2
Upstream release that is considered latest: 3.9.9-0sdhd5
Current version/release in rawhide: 2.58.3-1.fc39
URL: https://github.com/snapcore/snapd

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


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

Comment 5 Upstream Release Monitoring 2023-04-19 11:04:03 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-c3dkf6y9/snapd.spec']' returned non-zero exit status 1.

StdOut:
error: Bad source: ./snapd_3.9.9.no-vendor.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

Comment 6 Fedora Update System 2024-01-18 13:14:27 UTC
FEDORA-2024-aae86b77ea has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-aae86b77ea

Comment 7 Fedora Update System 2024-01-18 14:23:45 UTC
FEDORA-2024-b5800ca988 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-b5800ca988

Comment 8 Fedora Update System 2024-01-19 03:33:39 UTC
FEDORA-2024-b5800ca988 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-b5800ca988`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-b5800ca988

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2024-01-19 18:03:41 UTC
FEDORA-2024-aae86b77ea has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-aae86b77ea`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-aae86b77ea

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2024-01-23 12:32:38 UTC
FEDORA-EPEL-2024-6c34072117 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-6c34072117

Comment 11 Fedora Update System 2024-01-23 13:45:30 UTC
FEDORA-EPEL-2024-5155af1ba2 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-5155af1ba2

Comment 12 Fedora Update System 2024-01-23 14:15:27 UTC
FEDORA-EPEL-2024-13ea4713f9 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-13ea4713f9

Comment 13 Fedora Update System 2024-01-24 01:43:26 UTC
FEDORA-EPEL-2024-5155af1ba2 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-5155af1ba2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 14 Fedora Update System 2024-01-24 01:50:43 UTC
FEDORA-EPEL-2024-6c34072117 has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-6c34072117

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 15 Fedora Update System 2024-01-24 01:53:49 UTC
FEDORA-EPEL-2024-13ea4713f9 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-13ea4713f9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 16 Fedora Update System 2024-01-27 01:28:43 UTC
FEDORA-2024-aae86b77ea has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2024-01-27 02:12:07 UTC
FEDORA-2024-b5800ca988 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 18 Fedora Update System 2024-02-01 01:43:07 UTC
FEDORA-EPEL-2024-5155af1ba2 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 19 Fedora Update System 2024-02-01 01:58:04 UTC
FEDORA-EPEL-2024-13ea4713f9 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 20 Fedora Update System 2024-02-01 02:02:38 UTC
FEDORA-EPEL-2024-6c34072117 has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.