Bug 2062847

Summary: APLpy-2.2.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: APLpyAssignee: Sergio Pascual <sergio.pasra>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: gracca, sergio.pasra
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: APLpy-2.2.0-1.fc42 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-04-23 01:46:56 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:
Bug Depends On: 2213588, 2348759    
Bug Blocks:    
Attachments:
Description Flags
Update to 2.2.0 (#2062847) none

Description Upstream Release Monitoring 2022-03-10 16:54:26 UTC
Latest upstream release: 2.1.0
Current version/release in rawhide: 2.0.3-15.fc37
URL: https://pypi.python.org/pypi/APLpy

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

Comment 1 Upstream Release Monitoring 2022-03-10 16:54:31 UTC
Scratch build failed. Details bellow:

BuilderException: Build started, but failure happened during post build operations:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-8nvsst_r/APLpy.spec']' returned non-zero exit status 1.

StdOut:
error: Bad source: ./APLpy-2.1.0.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.9/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.9/site-packages/hotness/builders/koji.py", line 188, 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 Sergio Pascual 2022-04-24 17:49:16 UTC
Requires:

pyregion>=2.0
pyavm>=0.9.4

Not in Fedora

Comment 3 Upstream Release Monitoring 2024-11-15 00:34:04 UTC
Releases retrieved: 2.2.0
Upstream release that is considered latest: 2.2.0
Current version/release in rawhide: 2.0.3-31.fc42
URL: https://pypi.python.org/pypi/APLpy

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


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

Comment 4 Upstream Release Monitoring 2024-11-15 00:34:08 UTC
Scratch build failed. Details below:

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

StdOut:
setting SOURCE_DATE_EPOCH=1731628800
error: Bad file: ./APLpy-2.2.0.tar.gz: No such file or directory

RPM build errors:
    Bad file: ./APLpy-2.2.0.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 2024-11-15 00:34:09 UTC
Created attachment 2057813 [details]
Update to 2.2.0 (#2062847)

Comment 6 Fedora Update System 2025-04-14 12:24:35 UTC
FEDORA-2025-369cefac1b (APLpy-2.2.0-1.fc42 and python-pyregion-2.3.0-1.fc42.1) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-369cefac1b

Comment 7 Fedora Update System 2025-04-15 20:22:59 UTC
FEDORA-2025-369cefac1b has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-369cefac1b \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-369cefac1b

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

Comment 8 Fedora Update System 2025-04-23 01:46:56 UTC
FEDORA-2025-369cefac1b (APLpy-2.2.0-1.fc42 and python-pyregion-2.3.0-1.fc42.1) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.