Bug 2125027 - libell-0.58 is available
Summary: libell-0.58 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libell
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-07 19:21 UTC by Upstream Release Monitoring
Modified: 2023-09-15 18:40 UTC (History)
1 user (show)

Fixed In Version: libell-0.58-1.fc38 libell-0.58-1.fc39
Clone Of:
Environment:
Last Closed: 2023-08-28 01:30:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 0.53 (#2125027) (891 bytes, patch)
2022-09-07 19:21 UTC, Upstream Release Monitoring
no flags Details | Diff
Update to 0.54 (#2125027) (892 bytes, patch)
2022-11-18 09:47 UTC, Upstream Release Monitoring
no flags Details | Diff
Update to 0.55 (#2125027) (892 bytes, patch)
2022-12-18 20:36 UTC, Upstream Release Monitoring
no flags Details | Diff
Update to 0.56 (#2125027) (1017 bytes, patch)
2023-01-23 19:13 UTC, Upstream Release Monitoring
no flags Details | Diff
Update to 0.57 (#2125027) (892 bytes, patch)
2023-05-24 15:27 UTC, Upstream Release Monitoring
no flags Details | Diff
Update to 0.58 (#2125027) (1017 bytes, patch)
2023-08-24 11:41 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2022-09-07 19:21:26 UTC
Releases retrieved: 0.53
Upstream release that is considered latest: 0.53
Current version/release in rawhide: 0.52-1.fc37
URL: https://git.kernel.org/pub/scm/libs/ell/ell.git/

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://fedoraproject.org/wiki/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/17781/


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

Comment 1 Upstream Release Monitoring 2022-09-07 19:21:32 UTC
Created attachment 1910298 [details]
Update to 0.53 (#2125027)

Comment 2 Upstream Release Monitoring 2022-09-07 19:27:12 UTC
the-new-hotness/release-monitoring.org's scratch build of libell-0.53-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=91751936

Comment 3 Upstream Release Monitoring 2022-11-18 09:47:45 UTC
Releases retrieved: 0.54
Upstream release that is considered latest: 0.54
Current version/release in rawhide: 0.52-1.fc37
URL: https://git.kernel.org/pub/scm/libs/ell/ell.git/

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


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

Comment 4 Upstream Release Monitoring 2022-11-18 09:47:49 UTC
Created attachment 1925278 [details]
Update to 0.54 (#2125027)

Comment 5 Upstream Release Monitoring 2022-11-18 09:53:33 UTC
the-new-hotness/release-monitoring.org's scratch build of libell-0.54-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=94293876

Comment 6 Upstream Release Monitoring 2022-12-18 20:36:14 UTC
Releases retrieved: 0.55
Upstream release that is considered latest: 0.55
Current version/release in rawhide: 0.54-1.fc38
URL: https://git.kernel.org/pub/scm/libs/ell/ell.git/

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


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

Comment 7 Upstream Release Monitoring 2022-12-18 20:36:18 UTC
Created attachment 1933465 [details]
Update to 0.55 (#2125027)

Comment 8 Upstream Release Monitoring 2022-12-18 20:41:03 UTC
the-new-hotness/release-monitoring.org's scratch build of libell-0.55-1.fc36.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=95511756

Comment 9 Upstream Release Monitoring 2023-01-23 19:13:38 UTC
Releases retrieved: 0.56
Upstream release that is considered latest: 0.56
Current version/release in rawhide: 0.55-1.fc38
URL: https://git.kernel.org/pub/scm/libs/ell/ell.git/

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


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

Comment 10 Upstream Release Monitoring 2023-01-23 19:13:43 UTC
Created attachment 1940064 [details]
Update to 0.56 (#2125027)

Comment 11 Upstream Release Monitoring 2023-05-24 15:27:52 UTC
Releases retrieved: 0.57
Upstream release that is considered latest: 0.57
Current version/release in rawhide: 0.56-1.fc38
URL: https://git.kernel.org/pub/scm/libs/ell/ell.git/

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


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

Comment 12 Upstream Release Monitoring 2023-05-24 15:27:58 UTC
Created attachment 1966643 [details]
Update to 0.57 (#2125027)

Comment 13 Upstream Release Monitoring 2023-05-24 15:33:31 UTC
the-new-hotness/release-monitoring.org's scratch build of libell-0.57-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=101516219

Comment 14 Upstream Release Monitoring 2023-08-24 11:41:54 UTC
Releases retrieved: 0.58
Upstream release that is considered latest: 0.58
Current version/release in rawhide: 0.57-2.fc39
URL: https://git.kernel.org/pub/scm/libs/ell/ell.git/

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


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

Comment 15 Upstream Release Monitoring 2023-08-24 11:41:58 UTC
Scratch build failed. Details below:

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

StdOut:
setting SOURCE_DATE_EPOCH=1692835200
error: Bad file: ./ell-0.58.tar.xz: No such file or directory

RPM build errors:
    Bad file: ./ell-0.58.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 16 Upstream Release Monitoring 2023-08-24 11:41:59 UTC
Created attachment 1985025 [details]
Update to 0.58 (#2125027)

Comment 17 Fedora Update System 2023-08-25 16:44:16 UTC
FEDORA-2023-f9fb8e1b3b has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f9fb8e1b3b

Comment 18 Fedora Update System 2023-08-25 16:44:17 UTC
FEDORA-2023-0a927f20cd has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-0a927f20cd

Comment 19 Fedora Update System 2023-08-26 02:00:27 UTC
FEDORA-2023-0a927f20cd 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-0a927f20cd`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-0a927f20cd

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

Comment 20 Fedora Update System 2023-08-26 02:34:54 UTC
FEDORA-2023-f9fb8e1b3b 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-f9fb8e1b3b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-f9fb8e1b3b

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

Comment 21 Fedora Update System 2023-08-28 01:30:20 UTC
FEDORA-2023-0a927f20cd has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 22 Fedora Update System 2023-09-15 18:40:48 UTC
FEDORA-2023-f9fb8e1b3b 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.