Even max-rpm philosophy section points out that rpm builds are unattended, but then we do nothing at all to prevent it? I first though maybe this regressed when we switched the build scripts to use rpmfcExec() a few years ago, but there wasn't anything before that either. Weird. You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/2898 -- Commit Summary -- * Run build scriptlets with closed stdin to enforce unattended builds -- File Changes -- M build/rpmfc.c (11) A tests/data/SPECS/interact.spec (12) M tests/rpmbuild.at (12) -- Patch Links -- https://github.com/rpm-software-management/rpm/pull/2898.patch https://github.com/rpm-software-management/rpm/pull/2898.diff -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/2898 You are receiving this because you are subscribed to this thread. Message ID: <rpm-software-management/rpm/pull/2...@github.com>
_______________________________________________ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
