Bug 2229127 - gnutls-3.8.1 is available
Summary: gnutls-3.8.1 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnutls
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Red Hat Crypto Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-04 09:53 UTC by Upstream Release Monitoring
Modified: 2023-09-15 18:42 UTC (History)
6 users (show)

Fixed In Version: gnutls-3.8.1-1.fc38 gnutls-3.8.1-1.fc37 gnutls-3.8.1-1.fc39
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-01 01:29:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 3.8.1 (#2229127) (605 bytes, patch)
2023-08-04 09:53 UTC, Upstream Release Monitoring
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-908 0 None None None 2023-08-04 09:53:48 UTC

Description Upstream Release Monitoring 2023-08-04 09:53:06 UTC
Releases retrieved: 3.7.10, 3.8.1
Upstream release that is considered latest: 3.8.1
Current version/release in rawhide: 3.8.0-7.fc39
URL: http://www.gnutls.org

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


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

Comment 1 Upstream Release Monitoring 2023-08-04 09:53:24 UTC
Scratch build failed. Details below:

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

StdOut:
cat: ./SPECS/gnutls.spec: No such file or directory
cat: ./gnutls-3.8.1.tar.xz: No such file or directory
cat: ./gnutls-3.8.1.tar.xz.sig: No such file or directory
setting SOURCE_DATE_EPOCH=1691107200
error: Bad file: ./gnutls-3.8.1.tar.xz.sig: No such file or directory
error: Bad file: ./gnutls-3.8.1.tar.xz: No such file or directory

RPM build errors:
    Bad file: ./gnutls-3.8.1.tar.xz.sig: No such file or directory
    Bad file: ./gnutls-3.8.1.tar.xz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.11/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.11/site-packages/hotness/builders/koji.py", line 229, 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-08-04 09:53:25 UTC
Created attachment 1981614 [details]
Update to 3.8.1 (#2229127)

Comment 3 Fedora Update System 2023-08-28 09:48:53 UTC
FEDORA-2023-7ef3bc8d6d has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7ef3bc8d6d

Comment 4 Fedora Update System 2023-08-28 09:48:54 UTC
FEDORA-2023-e194bfaef7 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e194bfaef7

Comment 5 Fedora Update System 2023-08-28 09:48:56 UTC
FEDORA-2023-683d1e20b4 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-683d1e20b4

Comment 6 Fedora Update System 2023-08-29 01:21:23 UTC
FEDORA-2023-e194bfaef7 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-2023-e194bfaef7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e194bfaef7

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

Comment 7 Fedora Update System 2023-08-29 01:24:51 UTC
FEDORA-2023-7ef3bc8d6d 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-2023-7ef3bc8d6d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-7ef3bc8d6d

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

Comment 8 Fedora Update System 2023-08-29 02:19:09 UTC
FEDORA-2023-683d1e20b4 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-683d1e20b4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-683d1e20b4

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

Comment 9 Fedora Update System 2023-09-01 01:29:30 UTC
FEDORA-2023-e194bfaef7 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2023-09-13 01:35:01 UTC
FEDORA-2023-683d1e20b4 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2023-09-15 18:42:04 UTC
FEDORA-2023-7ef3bc8d6d has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.