New error message on tonight's update - relating to a "just prior" update to DNF perhaps?

Every Fedora41 based non-minimal template tonight shows the following although they supposedly complete successfully.

One template (untrusted-dvm-f41) for example:

untrusted-dvm-f41:err: warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
untrusted-dvm-f41:err: warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
untrusted-dvm-f41:err: warning: posix.exec(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead

Maybe nothing but…I don’t believe that it’s been witnessed by anyone else yet.

1 Like

I have witnessed it. It also happens on vanilla Fedora 41 installations. There are related Github issues on rpm repository.

2 Likes

Fedora 41 has been particularly bug-ridden… Hope you guys (the devs, I mean) make the F41 templates stable before May 28th when F40 reaches end-of-support.

2 Likes

This one is a sad case where the confusing message is going to remain. Quoting one of the rpm devs from the PR:

Issuing deprecation warnings on packages built long time ago is just antisocial behavior when the user is powerless to do anything about it.

And the end user still got this:

fprintf(stderr,
	    "warning: %s(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead\n", func);

Instead of “…use…”, I would have re-phrased it like: “…package maintainer should use…”.

And finally the devs opinion :man_facepalming:t4::

No, the point is that we need to warn on all new usages of these functions to scare people away from using them. Otherwise, we’ll be in the same situation ten years from now and still can’t remove those functions.

2 Likes

“Facepalm”, indeed. :face_with_diagonal_mouth:

1 Like