And changed packages in the staging branch are not being built. The systemd branch is currently broken because there's an update to linux-pam, the version in that branch is being replaced by Alpine's version (also see: https://gitlab.com/postmarketOS/pmaports/-/issues/3170).
I do not have access to SSH to failed jobs in builds.sr.ht that run from bpo/postmarketos account, so I wasn't able to get more logs or try to reproduce/debug it
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
[17:04:55] Username [user]: [17:04:55] Username [user]: user(024544) [17:04:56] ERROR: Package gnome-settings-daemon-mobile found in multiple aports subfolders. Please put it only in one folder.(024544) [17:04:56] See also: <https://postmarketos.org/troubleshooting>(024544) [17:04:56] Traceback (most recent call last): File "/home/clayton/src/pmbootstrap/pmb/__init__.py", line 60, in main return config_init.frontend(args) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/clayton/src/pmbootstrap/pmb/config/init.py", line 691, in frontend ask_for_provider_select_pkg(args, "postmarketos-base", cfg["providers"]) File "/home/clayton/src/pmbootstrap/pmb/config/init.py", line 322, in ask_for_provider_select_pkg apkbuild = pmb.helpers.pmaports.get(args, pkgname, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/clayton/src/pmbootstrap/pmb/helpers/pmaports.py", line 217, in get path = _find_apkbuilds(args).get(pkgname) ^^^^^^^^^^^^^^^^^^^^^ File "/home/clayton/src/pmbootstrap/pmb/helpers/pmaports.py", line 27, in _find_apkbuilds raise RuntimeError(f"Package {package} found in multiple aports "RuntimeError: Package gnome-settings-daemon-mobile found in multiple aports subfolders. Please put it only in one folder.
So I guess I broke this when I reverted a patch in the staging branch, the patch removed temp/gnome-settings-daemon-mobile because it was forked into extra-repos/systemd.
tl;dr: bpo needs to use pmb v3, which can properly handle this. In the meantime, I'm going to push a patch to the staging branch that re-removes these forked packages from pmaports/temp...
FYI: pmbootstrap v3 is now used again for master and staging branches (master_staging_systemd).
I have not tested having the duplicate packages in the branch, it may work now and it certainly should not fail at the same pmbootstrap error. But there is also a chance that it fails elsewhere as bpo isn't really aware of multiple repositories yet, and I can imagine that there is a code path that it builds or deletes the wrong package (within master_staging_systemd), if one of the packages gets built or deleted.
So I would not recommend reverting that just yet, but I'm working hard on making the split repo work in bpo, and making it use pmb v3 is a big step towards that.