Bug 2295340 - dnf install: warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
Summary: dnf install: warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2n...
Keywords:
Status: CLOSED DUPLICATE of bug 2291869
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-07-03 06:57 UTC by Jens Petersen
Modified: 2024-07-03 13:37 UTC (History)
19 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-03 13:37:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jens Petersen 2024-07-03 06:57:52 UTC
Frequently when updating or installing packages with dnf5 I see these warnings:

>>> Running trigger-install scriptlet: glibc-common-0:2.39.9000-26.fc41.x86_64warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.exec(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead

Is this coming from dnf5 or glibc?


Reproducible: Always

Steps to Reproduce:
1. run dnf update in rawhide

Actual Results:  
Running trigger-install scriptlet: glibc-common-0:2.39.9000-26.fc41.x86_64 warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead

Expected Results:  
No warnings

Do not happen in F40

Comment 1 Marek Blaha 2024-07-03 07:22:40 UTC
The message originates in the rpm (see PR https://github.com/rpm-software-management/rpm/pull/2948), but is caused by glibc scriptlets which use deprecated functionality.
Re-assigning to glibc for further actions.

Comment 2 Carlos O'Donell 2024-07-03 13:37:56 UTC

*** This bug has been marked as a duplicate of bug 2291869 ***


Note You need to log in before you can comment on or make changes to this bug.