Hello,

You can run extra-x86_64-build as root, this should work fine.

No this does not work:

eureka-notes on  master took 9s ❯ doas su [root@PolarianLaptop eureka-notes]# ls PKGBUILD README.md [root@PolarianLaptop eureka-notes]# extra-x86_64-build :: Synchronizing package databases... core downloading... extra downloading... community downloading... :: Starting full system upgrade... there is nothing to do ==> Building in chroot for [extra] (x86_64)... ==> Synchronizing chroot copy [/var/lib/archbuild/extra-x86_64/root] -> [copy]...done ==> ERROR: Running makepkg as root is not allowed.

Using doas:

eureka-notes on  master ❯ doas extra-x86_64-build :: Synchronizing package databases... core downloading... extra downloading... community downloading... :: Starting full system upgrade... there is nothing to do ==> Building in chroot for [extra] (x86_64)... ==> Synchronizing chroot copy [/var/lib/archbuild/extra-x86_64/root] -> [copy]...done ==> ERROR: Running makepkg as root is not allowed.

With su:

eureka-notes on  master took 9s ❯ extra-x86_64-build Password: :: Synchronizing package databases... core downloading... extra downloading... community downloading... :: Starting full system upgrade... there is nothing to do ==> Building in chroot for [extra] (x86_64)... ==> Synchronizing chroot copy [/var/lib/archbuild/extra-x86_64/root] -> [polarian]...done /usr/bin/makechrootpkg: line 561: sudo: command not found ==> ERROR: Could not download sources.

Like I have highlighted above, sudo is hard depended on, not having it causes it to break!

Thanks,

Hello,

My bad, I thought it was only used inside the chroot and sudo was just a there to evaluate privileges. But no, it's used to download the sources outside of the chroot with --preserve-env which doas does not support. So supporting doas is impossible for devtools as doas has no equivalent option for this.

So no dilemma really, just install sudo.

So I am going to make this intentionally harder, screw the devtools, what do I need in order to create an arch chroot manually and enter the chroot using the chroot binary, and then manually cloning the package and building it within the chroot?

I can extract the built package from outside the chroot if I like as well, but this is mainly for debugging purposes not for actual building.

Thanks for the help,

Wait,

I just realised the installation of arch linux is literally this process... I am an idiot!!!

Thanks for the help though,

Am 25.01.23 um 10:15 schrieb Polarian:

I ran into a small issue, there is "no available disk space" if this is not done on its own partition, aka if you do not mount a partition to the chroot.

Is there any method without having to partition up my disk to allocate storage to a chroot, as currently it has no root storage...

All you need is a directory to store the files of your build environment. Of course the filesystem this directory lives in needs enough free space to hold a minimal Arch installation, which is about 3 GBytes. If the system, you want to try this on, is short of storage, and / is a filesystem that supports reflinks (btrfs and newest xfs), you could snapshot or reflink all files of your running system into the new build-root (skipping pacstrap)

# btrfs subvolume snapshot / build-root

or

# cd / # mkdir build-root # cp --reflink=always -ax /{bin,lib,var,etc,lib64,root,sbin,usr} build-root/ # mkdir -p build-root/{boot,dev,home,opt,proc,run,srv,sys,tmp}

then, after chroot-ing into it, use pacman to uninstall everything that is not a dependency of base or base-devel. I did something similar to clean up a machine:

# arch-chroot build-root /bin/bash # cd /tmp # pactree -u base | sed 's/[<>=].*$//' | sort -u > base.deps # pacman -Qg base-devel | cut -d' ' -f2 | sort -u > base-devel.deps # sort -um base.deps base-devel.deps > clean-pkgs # pacman -Qe | cut -d' ' -f1 | sort -u > current-pkgs

After that,

# diff --suppress-common-lines clean-pkgs current-pkgs | sed -n 's/^> //p' | pacman -Rcsn -

would uninstall everything that does not belong to base or base-devel. Base-devel.deps is a bit misleading, it does not contain all dependencies, but as only explicit packages are uninstalled later, this seems to work alright. I am not implying that this would be my preferred course of action, but it is fast and space efficient.

Next time you write about a problem you ran into, better show everything you did and the error message you got, using copy and paste.

BR

Hello,

It may be the issue described in the arch-chroot man page.

Yes it seems like it was!

I had trouble in the past with pacman estimating available disk space in chroots and it was resolved by following this advice.

Yes it worked, thank you so much man, I know it is not conventional to build in manual chroots, and you are meant to use dev-tools but I far prefer this method, so that you so much :)

Hello,

Thanks for the history lesson, it was genuinely kind of interesting, I guess opendoas is not as secure on Linux as everyone makes it out to be, it is still faster and lighter weight which does mean theoretically it should be eaiser to maintain and thus more secure, and also it is less bloated.

I guess using sudo for the dev scripts is a good thing, as for once the bloated features have come in useful within the dev scripts. I still would rather avoid setting up sudo just to use the dev scripts. I will try manual chroot building through pacstrap and chrooting as its always more fun to do things manually in my opinion and I will see how that goes.

If it goes badly I will take your suggestion, and install and configure sudo for building the packages using the dev scripts, but I at least want a crack at doing it manually.

Thanks for the suggestion, and the history :)

Hello,

The only thing stopping doas from being supported is --preserve-env support, hardly a bloated feature.

I guess this is a requested feature... if I have time I will submit it to the Linux opendoas repository

Thanks,