In case the user does not specify for which arch packages should be built with `pmbootstrap build`, we detect it automatically. Previous logic was, that if the APKBUILD's arch is "all" or "noarch", then prefer the native arch, and otherwise use the first one in the list of available arches. New behavior is, that we also check if the list of possible arches contains the native arch (and if that fails, the device arch). If that is the case, we return the native/device arch instead of the first one in the list. ### Use case The arch from `gcc-armhf` and similar packages (as generated by `pmbootstrap aportgen`) used to be "all", but is nowadays a specific list of arches. This means, that after updating the `gcc-armhf` and `gcc-aarch64` packages, and calling `pmbootstrap build gcc-armhf`, it will try to build `gcc-armhf` for `aarch64` instead of the native architecture, because that is the first one listed. And since compiling to `aarch64` requires `gcc-aarch64`, it will build that for the native architecture first. So you're asking for `gcc-armhf` and it compiles `gcc-aarch64`, which is very confusing (see #1272). |
||
---|---|---|
aports | ||
helpers | ||
keys | ||
pmb | ||
test | ||
.gitignore | ||
.travis.yml | ||
CONTRIBUTING.md | ||
LICENSE | ||
MANIFEST.in | ||
pmbootstrap.py | ||
README.md | ||
setup.cfg | ||
setup.py |
pmbootstrap
Introduction | Security Warning | Supported Devices | |
Sophisticated chroot/build/flash tool to develop and install postmarketOS.
For in-depth information please refer to the postmarketOS wiki.
Requirements
- 2 GB of RAM recommended for compiling
- Linux distribution (
x86
,x86_64
, oraarch64
)- Windows subsystem for Linux (WSL) does not work! Please use VirtualBox instead.
- Kernels based on the grsec patchset do not work (Alpine: use linux-vanilla instead of linux-hardened, Arch: linux-hardened is not based on grsec)
- On Alpine Linux only:
apk add coreutils
- Python 3.4+
- OpenSSL
Usage
Assuming you have a supported device, you can build and flash a postmarketOS image by running through the following steps. For new devices check the porting guide.
First, clone the git repository and initialize your pmbootstrap environment:
$ git clone https://github.com/postmarketOS/pmbootstrap
$ cd pmbootstrap
$ ./pmbootstrap.py init
While running any pmbootstrap command, it's always useful to have a log open in a separate window where further details can be seen:
$ ./pmbootstrap.py log
It's now time to run a full build which will create the boot and system images:
$ ./pmbootstrap.py install
Once your device is connected and is ready to be flashed (e.g. via fastboot), you can run a flash of the kernel (boot) and system partitions:
$ ./pmbootstrap.py flasher flash_kernel
$ ./pmbootstrap.py flasher flash_system
After a reboot, the device will prompt for the full-disk encryption password, which you typed in the install step (unless you have disabled full-disk encryption with --no-fde
). Once the partition has been unlocked it is possible to connect via SSH:
$ dhclient -v enp0s20f0u1
$ ssh user@172.16.42.1
Development
Testing
Install pytest
(via your package manager or pip) and run it inside the pmbootstrap folder.