Bug 2247884

Summary: cabal-rpm-2.2.1 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: cabal-rpmAssignee: Jens Petersen <petersen>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: petersen
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cabal-rpm-2.2.1-1.fc39 cabal-rpm-2.2.1-1.fc40 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-08-11 03:29:54 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.2.0 (#2247884) none

Description Upstream Release Monitoring 2023-11-04 04:12:46 UTC
Releases retrieved: 2.1.4
Upstream release that is considered latest: 2.1.4
Current version/release in rawhide: 2.1.3-1.fc40
URL: http://hackage.haskell.org/package/cabal-rpm

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


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

Comment 1 Upstream Release Monitoring 2023-11-04 04:12:49 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['git', 'commit', '-a', '-m', 'Update to 2.1.4 (#2247884)']' returned non-zero exit status 1.

StdOut:
On branch rawhide
Your branch is up to date with 'origin/rawhide'.

nothing to commit, working tree clean


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 185, 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 2023-11-24 13:21:28 UTC
Releases retrieved: 2.1.5
Upstream release that is considered latest: 2.1.5
Current version/release in rawhide: 2.1.4-1.fc40
URL: http://hackage.haskell.org/package/cabal-rpm

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


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

Comment 3 Upstream Release Monitoring 2023-11-24 13:21:30 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['git', 'commit', '-a', '-m', 'Update to 2.1.5 (#2247884)']' returned non-zero exit status 1.

StdOut:
On branch rawhide
Your branch is up to date with 'origin/rawhide'.

nothing to commit, working tree clean


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 185, 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 4 Upstream Release Monitoring 2024-03-27 16:34:49 UTC
Releases retrieved: 2.2.0
Upstream release that is considered latest: 2.2.0
Current version/release in rawhide: 2.1.5-4.fc40
URL: http://hackage.haskell.org/package/cabal-rpm

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


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

Comment 5 Upstream Release Monitoring 2024-03-27 16:34:53 UTC
Created attachment 2023865 [details]
Update to 2.2.0 (#2247884)

Comment 6 Upstream Release Monitoring 2024-03-27 16:40:53 UTC
the-new-hotness/release-monitoring.org's scratch build of cabal-rpm-2.2.0-1.fc38.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=115518014

Comment 7 Upstream Release Monitoring 2024-08-02 10:38:45 UTC
Releases retrieved: 2.2.1
Upstream release that is considered latest: 2.2.1
Current version/release in rawhide: 2.2.0-3.fc41
URL: http://hackage.haskell.org/package/cabal-rpm

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


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

Comment 8 Upstream Release Monitoring 2024-08-02 10:38:48 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['git', 'commit', '-a', '-m', 'Update to 2.2.1 (#2247884)']' returned non-zero exit status 1.

StdOut:
On branch rawhide
Your branch is up to date with 'origin/rawhide'.

nothing to commit, working tree clean


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 185, 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 9 Fedora Update System 2024-08-03 07:45:06 UTC
FEDORA-2024-b2eaf28d92 (cabal-rpm-2.2.1-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-b2eaf28d92

Comment 10 Fedora Update System 2024-08-03 07:47:57 UTC
FEDORA-2024-8ec96898a5 (cabal-rpm-2.2.1-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-8ec96898a5

Comment 11 Fedora Update System 2024-08-11 03:29:54 UTC
FEDORA-2024-8ec96898a5 (cabal-rpm-2.2.1-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-08-11 04:48:39 UTC
FEDORA-2024-b2eaf28d92 (cabal-rpm-2.2.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.