Daniel Richard G.

> I tried your instructions today from scratch and ran into a compilation issue in step 7: Make sure that your `ORIG_SOURCE` variable is pointing to an unpacked source tree...

This is a question of workflow. I can't tell you exactly what to do, because it depends on what you want to do, but I'll clarify what you have there:...

If you use `INPLACE=1`, then no `ungoogled-chromium-src` tree is created, because all the modifications are made to the original source tree (presumably the unpacked Debian sources that you started with).

If you are working with a single tree, then you don't need to create that source package. You can skip its creation by invoking the `convert` target in the makefile...

Yes, the problem is that your unpacked source tree already has the Debian patches applied, and the conversion process changes the set of patches that should be applied. So you...

Ah yes, the conversion process applies its own patches as well. You'd have to do `quilt pop -afq` in the tree before running `chromium.sh` to avoid the warning.

All right, you made it! All those `.deb` files are part of the normal build; there isn't really a way to leave them out. In a typical installation, you will...

The "Download is performed unsandboxed" warning is an unrelated APT issue. The "No usable sandbox" error implies that your system does not have user namespaces enabled, which is not the...

Thanks for looking further into this. Not only have I successfully reproduced the issue on a 24.04 system here, I've found that recent changes in AppArmor are in fact interfering...

You can't rebuild Debian source packages incrementally---not without hacking up the build process, anyway---because the first thing it does is clear out any existing build tree. If you just want...