Bug 2284003 - fragments-3.0.1 is available
Summary: fragments-3.0.1 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fragments
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pete Walter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-05-30 15:53 UTC by Upstream Release Monitoring
Modified: 2024-10-12 01:41 UTC (History)
3 users (show)

Fixed In Version: fragments-3.0.1-1.fc42 fragments-3.0.1-1.fc41 fragments-3.0.1-1.fc40
Clone Of:
Environment:
Last Closed: 2024-10-03 17:56:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 3.0.1 (#2284003) (1.02 KB, patch)
2024-05-30 15:53 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2024-05-30 15:53:44 UTC
Releases retrieved: 3.0.1
Upstream release that is considered latest: 3.0.1
Current version/release in rawhide: 3.0.0-1.fc41
URL: https://gitlab.gnome.org/World/Fragments

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


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

Comment 1 Upstream Release Monitoring 2024-05-30 15:53:49 UTC
Scratch build failed. Details below:

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

StdOut:
setting SOURCE_DATE_EPOCH=1717027200
error: Bad file: ./fragments-3.0.1.tar.xz: No such file or directory

RPM build errors:
    Bad file: ./fragments-3.0.1.tar.xz: 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 2 Upstream Release Monitoring 2024-05-30 15:53:50 UTC
Created attachment 2035737 [details]
Update to 3.0.1 (#2284003)

Comment 3 Fedora Update System 2024-10-03 17:53:50 UTC
FEDORA-2024-faaff411d1 (fragments-3.0.1-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-faaff411d1

Comment 4 Fedora Update System 2024-10-03 17:56:43 UTC
FEDORA-2024-faaff411d1 (fragments-3.0.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 5 Fedora Update System 2024-10-03 19:35:06 UTC
FEDORA-2024-acf9fdec35 (fragments-3.0.1-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-acf9fdec35

Comment 6 Fedora Update System 2024-10-03 19:35:07 UTC
FEDORA-FLATPAK-2024-2a745e8327 (fragments-flatpak-3.0.1-1) has been submitted as an update to Fedora 40 Flatpaks.
https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2024-2a745e8327

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

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

Comment 8 Fedora Update System 2024-10-04 02:40:04 UTC
FEDORA-FLATPAK-2024-2a745e8327 has been pushed to the Fedora 40 Flatpaks testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2024-2a745e8327

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

Comment 9 Fedora Update System 2024-10-04 02:57:08 UTC
FEDORA-2024-acf9fdec35 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-2024-acf9fdec35`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-acf9fdec35

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

Comment 10 Fedora Update System 2024-10-12 00:19:15 UTC
FEDORA-2024-acf9fdec35 (fragments-3.0.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 11 Fedora Update System 2024-10-12 00:24:50 UTC
FEDORA-FLATPAK-2024-2a745e8327 (fragments-flatpak-3.0.1-1) has been pushed to the Fedora 40 Flatpaks stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2024-10-12 01:41:31 UTC
FEDORA-2024-0432dcd71e (fragments-3.0.1-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.