Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 806196 - media-sound/pulseaudio-15.0: emerge failure with USE=system-wide
Summary: media-sound/pulseaudio-15.0: emerge failure with USE=system-wide
Status: RESOLVED DUPLICATE of bug 805488
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-02 17:22 UTC by Steven Newbury
Modified: 2021-08-02 17:23 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steven Newbury 2021-08-02 17:22:33 UTC
Since the clean-up of the ebuild with pulseaudio-15.0 a "||die" has been added to the end of the unifdef command used to generate the init.d script.  This always triggers irrespective of success or failure.

The reason for this is obvious when looking at the unifdef man page:

EXIT STATUS
     In normal usage the unifdef utility's exit status depends on the mode set using the -x option.

     If the exit mode is zero (the default) then unifdef exits with status 0 if the output is an exact copy
     of the input, or with status 1 if the output differs.

     If the exit mode is one, unifdef exits with status 1 if the output is unmodified or 0 if it differs.

     If the exit mode is two, unifdef exits with status zero in both cases.

     In all exit modes, unifdef exits with status 2 if there is an error.

     The exit status is 0 if the -h or -V command line options are given.

--

As can be seen unifdef only exits with status 0 by default if the output is an exact copy, which obviously isn't going to be case!  Either unifdef should be called with "-x2" or die should be triggered if the exit code is 2.
Comment 1 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2021-08-02 17:23:20 UTC
Thanks, could you add your analysis to the other bug?

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