Draft: systemd/abuild: drop
we have abuild in both the systemd and edge repos due to #3452
it seems like just adding an explicit bootstrap step is enough to get things going properly. That probably isn't even needed since it seems like the bootstrap failure we saw was specific to that scenario and probably wouldn't show up again. but better safe than sorry.
Fixes: #3452
Merge request reports
Activity
requested review from @ollieparanoid
Thanks for the patch! I don't think this fixes it for bpo unfortunately, from #3452:
Without this change, BPO builds abuild, but then detects that this package does not belong in extra-repos/systemd and refuses to finish the bootstrap step. This is a safety mechanism, so we don't build unrelated packages in bootstrap by accident.
So I'll need to fix this in bpo probably.
Caleb wrote:
it seems like just adding an explicit bootstrap step is enough to get things going properly. That probably isn't even needed since it seems like the bootstrap failure we saw was specific to that scenario and probably wouldn't show up again. but better safe than sorry.
We'll see the same bootstrap errors when branching v25.06 and other future releases.
mentioned in merge request !6065 (merged)
added status::mr-stale label
Sorry to bother you @caleb,
but we've detected that this merge request hasn't seen any recent activity. If you need help, want to discuss your approach with developers, or you are all done and this is waiting for review, you can ping
@postmarketOS
. You can also ask on matrix in #devel:postmarketos.org or #postmarketos-devel on OFTC.Thanks for your contribution.
I plan to completely remove the bootstrap logic in favor of a simple systemd-stage0 package: #3604 (comment 474051) - as part of this, the extra-repos/systemd/abuild package can be dropped.