Bug 2279206

Summary: keepassxc-2.7.8 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: keepassxcAssignee: Germano Massullo (Thetra) <germano.massullo>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: brian, daniel, dimitris.on.linux, germano.massullo, mikel, nixuser, nonamedotc, redhat
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: keepassxc-2.7.8-1.fc40 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-14 01:26:28 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 2.7.8 (#2279206) none

Description Upstream Release Monitoring 2024-05-05 23:13:42 UTC
Releases retrieved: 2.7.8
Upstream release that is considered latest: 2.7.8
Current version/release in rawhide: 2.7.7-3.fc41
URL: https://keepassxc.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/15656/


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

Comment 1 Upstream Release Monitoring 2024-05-05 23:13:48 UTC
Scratch build failed. Details below:

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

StdOut:
setting SOURCE_DATE_EPOCH=1714867200
error: Bad file: ./keepassxc-2.7.8-src.tar.xz.sig: No such file or directory
error: Bad file: ./keepassxc-2.7.8-src.tar.xz: No such file or directory

RPM build errors:
    Bad file: ./keepassxc-2.7.8-src.tar.xz.sig: No such file or directory
    Bad file: ./keepassxc-2.7.8-src.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 2024-05-05 23:13:50 UTC
Created attachment 2031515 [details]
Update to 2.7.8 (#2279206)

Comment 3 Brian J. Murrell 2024-05-09 21:39:59 UTC
Any progress on getting this updated?

Comment 4 Fedora Update System 2024-05-10 11:16:48 UTC
FEDORA-2024-e69d8a311c (keepassxc-2.7.8-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-e69d8a311c

Comment 5 Brian J. Murrell 2024-05-10 14:20:07 UTC
Do backports to F39 (and I suppose F38 is still supported) happen automatically in some way or do those need to be specifically initiated by the maintainer?

Comment 6 Germano Massullo (Thetra) 2024-05-10 16:18:47 UTC
(In reply to Brian J. Murrell from comment #5)
> Do backports to F39 (and I suppose F38 is still supported) happen
> automatically in some way or do those need to be specifically initiated by
> the maintainer?

Please check
https://src.fedoraproject.org/rpms/keepassxc
under button "Updates Status"

Comment 7 Fedora Update System 2024-05-11 03:52:22 UTC
FEDORA-2024-e69d8a311c has been pushed to the Fedora 40 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-e69d8a311c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-e69d8a311c

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

Comment 8 Fedora Update System 2024-05-14 01:26:28 UTC
FEDORA-2024-e69d8a311c (keepassxc-2.7.8-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.