Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#70590 - Bring makepkg --asroot back

Attached to Project: Pacman
Opened by Daniel Mach (dmach) - Monday, 26 April 2021, 09:22 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 26 April 2021, 11:06 GMT
Task Type Feature Request
Category makepkg
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version 5.2.2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
I've been experimenting with basic arch package support in libdnf[1].
Yes, it's primarily built for managing RPMs, but since libsolv[2] has some arch support already,
I was thinking that having support for loading and querying arch repos would be nice.

As part of that, I'd like to run makepkg during the build process to generate test data from source.
These are usually empty packages with minimal dependencies - and they're completely under my control (no untrusted sources).
Since I've been using containers during development a lot,
I frequently face a situation that makepkg cannot be executed, because of running under root.
Back in 2014 when --asroot option was removed, containers weren't used that frequently
and that makes me think, if you wouldn't reconsider the decision and bring it back (probably in a different form).

How about setting an env variable, e.g. DANGEROUS_MAKEPKG_ALLOW_ROOT=1 ?


[1] https://github.com/rpm-software-management/libdnf/tree/dnf-5-devel
[2] https://github.com/openSUSE/libsolv


Steps to Reproduce:
$ podman run -it archlinux:latest
[root@3b23534af88f /]# makepkg
==> ERROR: Running makepkg as root is not allowed as it can cause permanent,
catastrophic damage to your system.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Monday, 26 April 2021, 11:06 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Create a user inside the container. Just like everyone else building packages inside containers.

Loading...