README: point to new source location
flasher: heimdall-bootimg: add support for '--no-reboot' and '--resume' Reviewed-by: Oliver Smith <ollieparanoid@postmarketos.org> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C170534361606.26168.17672643433174186875-0@git.sr.ht%3E
helpers/envkernel.fish: add deactivate & reactivate function for fish Signed-off-by: xtex <xtexchooser@duck.com> Reviewed-by: Oliver Smith <ollieparanoid@postmarketos.org> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20240113123358.6142-3-xtex@envs.net%3E
helpers/envkernel.fish: set prompt prefix in fish-shell Signed-off-by: xtex <xtexchooser@duck.com> Reviewed-by: Oliver Smith <ollieparanoid@postmarketos.org> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20240113123358.6142-2-xtex@envs.net%3E
helpers/envkernel.fish: export pmbootstrap_dir Signed-off-by: xtex <xtexchooser@duck.com> Reviewed-by: Oliver Smith <ollieparanoid@postmarketos.org> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20240113123358.6142-1-xtex@envs.net%3E
install: initial implementation of flat btrfs layout Reviewed-by: Oliver Smith <ollieparanoid@postmarketos.org> Tested-by: Oliver Smith <ollieparanoid@postmarketos.org> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C170436606365.31622.8646592258649313487-0@git.sr.ht%3E
pmb.config: add new newapkbuild arguments Add support for passing through the correct argument for Python (gpep517) and Rust to newapkbuild. Reviewed-by: Oliver Smith <ollieparanoid@postmarketos.org> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20240108222736.1143841-1-luca@z3ntu.xyz%3E
pmb.install.format: Write boot mountpoint to log Reviewed-by: Oliver Smith <ollieparanoid@postmarketos.org> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C170397557240.20130.18133458588122463459-0@git.sr.ht%3E
pmb.install: add --zap option I zap chroots a lot, since I've found that it often "fixes" a lot of weird issues that come about if you have stale chroots laying around. So a common pattern I do is "pmb zap && pmb install ...". Having an option to pmb install let's me simplify this. Reviewed-by: Oliver Smith <ollieparanoid@postmarketos.org> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20231214234051.4673-1-clayton@craftyguy.net%3E
pmb.install._install.get_recommends: tweak comment Fix comment style to be consistent with other functions, and reword the part about skipping packages.
pmb.install: support pmb_recommends for any package This refactors the get_recommends function that was originally used for UI packages to support pmb_recommends for any package (and subpackage). Extending pmb_recommends will, for example, help us create better generic device packages [1] and can be used to improve packaging for UIs with shared pmb_recommends[2]. 1. https://gitlab.com/postmarketOS/pmaports/-/merge_requests/4673 2. https://gitlab.com/postmarketOS/pmaports/-/merge_requests/3700 Reviewed-by: Oliver Smith <ollieparanoid@postmarketos.org> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20240102074605.23248-2-clayton@craftyguy.net%3E
parse.apkbuild.parse_subpackage: don't inherit pmb_recommends Reviewed-by: Oliver Smith <ollieparanoid@postmarketos.org> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20240102074605.23248-1-clayton@craftyguy.net%3E
install: throw error if boot_size is too small Make sure the user has at least 256 MiB set as their installation size, refuse to start the installation otherwise. The default was changed in 2021, 03e9fb05 ("pmb.config.init.boot_size: set to 256 MiB (MR 2037)"). If the user ran "pmbootstrap init" before that commit, the pmbootstrap config will have the old default set. It is very annoying when you do an installation with it and only realize it when you run into errors, e.g. while upgrading. I had that when testing the upgrade to the v23.12 release and also adjusted postmarketos-release-upgrade to warn if the boot partition is smaller than expected. Reviewed-by: Luca Weiss <luca@z3ntu.xyz> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20231208222714.4601-1-ollieparanoid@postmarketos.org%3E
aportgen: Only warn if binary version > APKBUILD version Sometimes I want to build an older version of a package from Alpine, and since package upgrades can involve things like patches and other externalities just changing the pkgver and running checksum in pmaports may not be enough. As such, it tends to be easier to revert the change in the local aports repo and then fork than forking and then trying to manually revert the changes yourself (since you can't have git do that for you given that they are distinct repositories). Prior to this patch, that was not possible since pmbootstrap would assume older aport version equals outdated aports in general and as such cancel the whole operation. Instead, just print a warning and helpful information to make this workflow possible while also warning users that they may want to update their local aports. Reviewed-by: Oliver Smith <ollieparanoid@postmarketos.org> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20231209111813.37756-1-newbyte@postmarketos.org%3E
install: do not fail on alpine-appstream-downloader error Having AppStream data is great for installation that make use of GNOME Software or KDE Discover, however it's not a must. The generation of AppStream data in alpine (which we maintain) is still certainly improvable, and we have bumped into problems, unreliabilities and such from time to time. Installations without AppStream data are totally functional, even if the first experience on those apps is not the best. Still, users are one refresh away on Software or Discover from getting such data downloaded. So failing to generate installations for this reason is unnecessarily breaking. Signed-off-by: Pablo Correa Gómez <ablocorrea@hotmail.com> Reviewed-by: Oliver Smith <ollieparanoid@postmarketos.org> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20231205160205.13916-1-pabloyoyoista@postmarketos.org%3E
Prepare 2.1.0 release
pmb.helpers.frontend: Convert kconfig check --file argument Stop using --file as a boolean argument and just use the value behind the argument as file to check. This also unbreaks this functionality after the recent change now that args.package is a list since you can pass multiple kernel packages as arguments. Fixes: 41daa850 ("parse.arguments: Allow providing multiple packages for kconfig_check") Closes: https://gitlab.com/postmarketOS/pmbootstrap/-/issues/2282 Reviewed-by: Oliver Smith <ollieparanoid@postmarketos.org> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20231203094559.413672-1-luca@z3ntu.xyz%3E
aportgen: remove binutils Remove the code for generating binutils-aarch64 etc. packages, as these live upstream in Alpine now. Having the generator scripts for binutils cross pkgs is therefore not useful anymore and would just bitrot if we kept it. Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20231126121617.3855-1-ollieparanoid@postmarketos.org%3E
aportgen: build gcc-x86_64 etc. pkgs for aarch64 Instead of building cross packages for the native architecture, add a new get_cross_packages_arches() function that returns the desired architectures no matter what the current native architecture is. So gcc-x86_64 will always have arch="aarch64", and gcc-aarch64 will always have arch="x86_64". We can tweak the function in the future if e.g. it becomes viable to cross compile from riscv64. Or even better, remove this and the cross compile packages upstreamed into alpine (see pmb#551). Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20231126104823.3723-1-ollieparanoid@postmarketos.org%3E
pkg resolver: don't guess if pmaport was found If we found an APKBUILD already, with the exact name of the package we are looking for, then don't also guess what other package could contain the package as subpackage. The guess was thrown away with the previous logic, but it caused misleading verbose logs like: lomiri-history-service: guessed to be a subpackage of lomiri Also this is slightly faster. While at it, tweak the related comments to make this easier to understand. Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20231121222457.2871-1-ollieparanoid@postmarketos.org%3E