Bug 2267148 - xarchiver-0.5.4.23 is available
Summary: xarchiver-0.5.4.23 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xarchiver
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michael DePaulo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-03-01 02:02 UTC by Upstream Release Monitoring
Modified: 2024-03-23 00:25 UTC (History)
5 users (show)

Fixed In Version: xarchiver-0.5.4.23-1.fc41 xarchiver-0.5.4.23-1.fc39 xarchiver-0.5.4.23-1.el9 xarchiver-0.5.4.23-1.fc40
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-03-01 09:17:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 0.5.4.23 (#2267148) (1.06 KB, patch)
2024-03-01 02:02 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2024-03-01 02:02:16 UTC
Releases retrieved: 0.5.4.23
Upstream release that is considered latest: 0.5.4.23
Current version/release in rawhide: 0.5.4.22-2.fc40
URL: https://github.com/ib/xarchiver/

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


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

Comment 1 Upstream Release Monitoring 2024-03-01 02:02:25 UTC
Created attachment 2019539 [details]
Update to 0.5.4.23 (#2267148)

Comment 2 Upstream Release Monitoring 2024-03-01 02:09:31 UTC
the-new-hotness/release-monitoring.org's scratch build of xarchiver-0.5.4.23-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=114260569

Comment 3 Fedora Update System 2024-03-01 09:14:07 UTC
FEDORA-2024-d8e8413bc5 (xarchiver-0.5.4.23-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-d8e8413bc5

Comment 4 Fedora Update System 2024-03-01 09:17:15 UTC
FEDORA-2024-d8e8413bc5 (xarchiver-0.5.4.23-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2024-03-01 09:45:34 UTC
FEDORA-2024-02db732bb7 (xarchiver-0.5.4.23-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-02db732bb7

Comment 6 Fedora Update System 2024-03-01 09:45:34 UTC
FEDORA-2024-ce6d566ee0 (xarchiver-0.5.4.23-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-ce6d566ee0

Comment 7 Fedora Update System 2024-03-01 09:45:35 UTC
FEDORA-EPEL-2024-89a5f58ea8 (xarchiver-0.5.4.23-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-89a5f58ea8

Comment 8 Fedora Update System 2024-03-02 00:58:49 UTC
FEDORA-EPEL-2024-89a5f58ea8 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-89a5f58ea8

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

Comment 9 Fedora Update System 2024-03-02 01:02:20 UTC
FEDORA-2024-ce6d566ee0 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-ce6d566ee0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-ce6d566ee0

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

Comment 10 Fedora Update System 2024-03-02 01:41:16 UTC
FEDORA-2024-02db732bb7 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-02db732bb7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-02db732bb7

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

Comment 11 Fedora Update System 2024-03-06 01:05:21 UTC
FEDORA-2024-ce6d566ee0 (xarchiver-0.5.4.23-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2024-03-10 00:39:16 UTC
FEDORA-EPEL-2024-89a5f58ea8 (xarchiver-0.5.4.23-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Roscoe Battles 2024-03-18 06:49:47 UTC
(In reply to Fedora Update System from comment #10)
> FEDORA-2024-02db732bb7 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-02db732bb7`
> You can provide feedback for this update here:
> https://bodhi.fedoraproject.org/updates/FEDORA-2024-02db732bb7
> 
> See also https://fedoraproject.org/wiki/QA:Updates_Testing for more
> information on how to test updates.

Nice information!

Comment 14 Fedora Update System 2024-03-23 00:25:10 UTC
FEDORA-2024-02db732bb7 (xarchiver-0.5.4.23-1.fc40) has been pushed to the Fedora 40 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.