Bug 2232623 - screen-4.9.1 is available
Summary: screen-4.9.1 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: screen
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Josef Ridky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-17 15:24 UTC by Upstream Release Monitoring
Modified: 2024-03-23 00:23 UTC (History)
3 users (show)

Fixed In Version: screen-4.9.1-1.fc40
Clone Of:
Environment:
Last Closed: 2024-03-23 00:23:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 4.9.1 (#2232623) (1.10 KB, patch)
2023-08-17 15:24 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2023-08-17 15:24:31 UTC
Releases retrieved: 4.9.1
Upstream release that is considered latest: 4.9.1
Current version/release in rawhide: 4.9.0-6.fc39
URL: https://www.gnu.org/software/screen/

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


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

Comment 1 Upstream Release Monitoring 2023-08-17 15:24:36 UTC
Created attachment 1983837 [details]
Update to 4.9.1 (#2232623)

Comment 2 Upstream Release Monitoring 2023-08-17 15:41:43 UTC
the-new-hotness/release-monitoring.org's scratch build of screen-4.9.1-1.fc38.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=104961836

Comment 3 Xose Vazquez Perez 2023-11-01 12:27:26 UTC
(In reply to Upstream Release Monitoring from comment #0)

> Releases retrieved: 4.9.1
> Upstream release that is considered latest: 4.9.1
> Current version/release in rawhide: 4.9.0-6.fc39
> URL: https://www.gnu.org/software/screen/
> Based on the information from Anitya: https://release-monitoring.org/project/4772/
> To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/screen

GNU Screen v.4.9.1:
* Support stop/parity bits on serial port
* Add needed system headers in checks and return values for implicit function declarations
* Fixes:
   - Avoid zombies after shell exit
   - Missed signal sending permission check on failed query messages (CVE-2023-24626)
   - manpage fixes
   - source code fixes during cleanup
   - UTF-8 encoding can emit invalid UTF-8 sequences for out of range unicode values

Comment 4 Xose Vazquez Perez 2024-02-03 21:00:50 UTC
Could it be updated to 4.9.1 for fc40?. Thanks.

Comment 5 Fedora Update System 2024-02-28 08:54:41 UTC
FEDORA-2024-099e1b95e2 (screen-4.9.1-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-099e1b95e2

Comment 6 Fedora Update System 2024-02-29 01:07:33 UTC
FEDORA-2024-099e1b95e2 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-099e1b95e2`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-099e1b95e2

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

Comment 7 Fedora Update System 2024-03-23 00:23:58 UTC
FEDORA-2024-099e1b95e2 (screen-4.9.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.