Bug 2401239 - barman-3.16.1 is available
Summary: barman-3.16.1 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: barman
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Simone Caronni
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-03 14:22 UTC by Upstream Release Monitoring
Modified: 2025-10-25 21:09 UTC (History)
1 user (show)

Fixed In Version: barman-3.16.1-1.el10_1 barman-3.16.1-1.el10_2 barman-3.16.1-1.el10_0 barman-3.16.1-1.fc42 barman-3.16.1-1.fc41 barman-3.16.1-1.el9 barman-3.16.1-1.fc43
Clone Of:
Environment:
Last Closed: 2025-10-25 00:36:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 3.16.0 (#2401239) (598 bytes, patch)
2025-10-03 14:22 UTC, Upstream Release Monitoring
no flags Details | Diff
Update to 3.16.1 (#2401239) (599 bytes, patch)
2025-10-15 02:25 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2025-10-03 14:22:25 UTC
Releases retrieved: 3.16.0
Upstream release that is considered latest: 3.16.0
Current version/release in rawhide: 3.15.0-2.fc44
URL: https://pypi.python.org/pypi/barman

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


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

Comment 1 Upstream Release Monitoring 2025-10-03 14:22:36 UTC
Created attachment 2108383 [details]
Update to 3.16.0 (#2401239)

Comment 2 Upstream Release Monitoring 2025-10-03 14:28:06 UTC
the-new-hotness/release-monitoring.org's scratch build of barman-3.16.0-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=137729757

Comment 3 Upstream Release Monitoring 2025-10-15 02:25:10 UTC
Releases retrieved: 3.16.1
Upstream release that is considered latest: 3.16.1
Current version/release in rawhide: 3.15.0-2.fc44
URL: https://pypi.python.org/pypi/barman

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


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

Comment 4 Upstream Release Monitoring 2025-10-15 02:25:14 UTC
Scratch build failed. Details below:

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

StdOut:
setting SOURCE_DATE_EPOCH=1760486400
error: Bad file: ./barman-release-3.16.1.tar.gz: No such file or directory

RPM build errors:
    Bad file: ./barman-release-3.16.1.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.12/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.12/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 5 Upstream Release Monitoring 2025-10-15 02:25:16 UTC
Created attachment 2109773 [details]
Update to 3.16.1 (#2401239)

Comment 6 Fedora Update System 2025-10-16 13:07:11 UTC
FEDORA-2025-3364f2ae09 (barman-3.16.1-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-3364f2ae09

Comment 7 Fedora Update System 2025-10-16 13:07:11 UTC
FEDORA-EPEL-2025-ed961bfb64 (barman-3.16.1-1.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-ed961bfb64

Comment 8 Fedora Update System 2025-10-16 13:07:12 UTC
FEDORA-EPEL-2025-173a07ccfc (barman-3.16.1-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-173a07ccfc

Comment 9 Fedora Update System 2025-10-16 13:07:13 UTC
FEDORA-2025-38c7031636 (barman-3.16.1-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-38c7031636

Comment 10 Fedora Update System 2025-10-17 01:00:32 UTC
FEDORA-2025-38c7031636 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-38c7031636`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-38c7031636

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

Comment 11 Fedora Update System 2025-10-17 01:09:36 UTC
FEDORA-EPEL-2025-726ba7bf55 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-726ba7bf55

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

Comment 12 Fedora Update System 2025-10-17 01:16:04 UTC
FEDORA-2025-3364f2ae09 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-3364f2ae09`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-3364f2ae09

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

Comment 13 Fedora Update System 2025-10-17 01:20:47 UTC
FEDORA-EPEL-2025-c467795a6e has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c467795a6e

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

Comment 14 Fedora Update System 2025-10-17 01:23:00 UTC
FEDORA-EPEL-2025-ed961bfb64 has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-ed961bfb64

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

Comment 15 Fedora Update System 2025-10-17 01:43:03 UTC
FEDORA-2025-688a0a013b has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-688a0a013b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-688a0a013b

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

Comment 16 Fedora Update System 2025-10-17 02:39:45 UTC
FEDORA-EPEL-2025-173a07ccfc 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-2025-173a07ccfc

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

Comment 17 Fedora Update System 2025-10-25 00:36:26 UTC
FEDORA-EPEL-2025-c467795a6e (barman-3.16.1-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 18 Fedora Update System 2025-10-25 00:55:34 UTC
FEDORA-EPEL-2025-726ba7bf55 (barman-3.16.1-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 19 Fedora Update System 2025-10-25 01:10:44 UTC
FEDORA-EPEL-2025-ed961bfb64 (barman-3.16.1-1.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 20 Fedora Update System 2025-10-25 01:14:02 UTC
FEDORA-2025-38c7031636 (barman-3.16.1-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 21 Fedora Update System 2025-10-25 01:37:29 UTC
FEDORA-2025-3364f2ae09 (barman-3.16.1-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 22 Fedora Update System 2025-10-25 03:05:58 UTC
FEDORA-EPEL-2025-173a07ccfc (barman-3.16.1-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 23 Fedora Update System 2025-10-25 21:09:53 UTC
FEDORA-2025-688a0a013b (barman-3.16.1-1.fc43) has been pushed to the Fedora 43 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.