Bug 2191700 - ipython-8.13.1 is available
Summary: ipython-8.13.1 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ipython
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lumír Balhar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-28 20:21 UTC by Upstream Release Monitoring
Modified: 2023-05-02 13:10 UTC (History)
8 users (show)

Fixed In Version: ipython-8.13.1-1.fc39
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-02 13:10:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 8.13.0 (#2191700) (927 bytes, patch)
2023-04-28 20:21 UTC, Upstream Release Monitoring
no flags Details | Diff
Update to 8.13.1 (#2191700) (927 bytes, patch)
2023-04-30 01:45 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2023-04-28 20:21:20 UTC
Releases retrieved: 8.12.1, 8.13.0
Upstream release that is considered latest: 8.13.0
Current version/release in rawhide: 8.12.0-1.fc39
URL: https://ipython.org/

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


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

Comment 1 Upstream Release Monitoring 2023-04-28 20:21:26 UTC
Created attachment 1960898 [details]
Update to 8.13.0 (#2191700)

Comment 2 Upstream Release Monitoring 2023-04-28 20:30:59 UTC
the-new-hotness/release-monitoring.org's scratch build of ipython-8.13.0-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=100497465

Comment 3 Upstream Release Monitoring 2023-04-30 01:45:23 UTC
Releases retrieved: 8.13.1
Upstream release that is considered latest: 8.13.1
Current version/release in rawhide: 8.12.0-1.fc39
URL: https://ipython.org/

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


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

Comment 4 Upstream Release Monitoring 2023-04-30 01:45:29 UTC
Created attachment 1961106 [details]
Update to 8.13.1 (#2191700)

Comment 5 Upstream Release Monitoring 2023-04-30 01:53:20 UTC
the-new-hotness/release-monitoring.org's scratch build of ipython-8.13.1-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=100540893

Comment 6 Fedora Update System 2023-05-02 13:07:15 UTC
FEDORA-2023-df68bf5ec9 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-df68bf5ec9

Comment 7 Fedora Update System 2023-05-02 13:10:24 UTC
FEDORA-2023-df68bf5ec9 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.