Skip to content
Snippets Groups Projects
New look: Off

pmbootstrap should tell the user if a package in extra-repos/systemd can't be built because systemd is disabled

    • Closed Imported Issue created by Administrator @root

    If a package can't be built, let's add the following logic:

    • check if systemd is disabled
    • check if the package is in extra-repos/systemd
    • if that is the case, then give the user a helpful error message
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Administrator changed milestone to %3.0.0 critical path (blockers only!!) · Imported

      changed milestone to %3.0.0 critical path (blockers only!!)

    • Administrator added difficulty::easy help wanted labels · Imported

      added difficulty::easy help wanted labels

    • Oliver Smith
      Oliver Smith @ollieparanoid ·
      Maintainer

      Still not implemented (I was not sure):

      $ pmbootstrap status              
Channel: edge (pmaports: master_staging_systemd)
Device:  samsung-i9100 (armv7, kernel: mainline)
UI:      console
systemd: no ('never' selected in 'pmbootstrap init')
      $ pmbootstrap build systemd
[18:45:30] ERROR: Could not find aport for package: systemd
    • Caleb Connolly
      Caleb Connolly @caleb ·
      Maintainer

      I'm in favour of adding this, it seems useful. However it kinda violates some core assumptions encoded into the pkgrepo api currently. I think it will need some reworking to handle this properly, particularly since we support invoking pmbootstrap build $subpackage and then figuring out which package the subpackage belongs to.

      I know it's not nearly as good, but this inspired me to open !2472 (merged) which might help bridge the gap for now. With that it becomes

      $ pmbootstrap build systemd
[17:19:00] ERROR: Could not find aport for package: systemd
[17:19:00] See also: <https://postmarketos.org/troubleshooting>

Run 'pmbootstrap log' for details.

Before you report this error, ensure that pmbootstrap is up to date.
Find the latest version here: https://gitlab.postmarketos.org/postmarketOS/pmbootstrap/-/tags
Your version: 3.0.0_alpha
Channel: edge (pmaports: master, dirty)
Device:  qemu-amd64 (x86_64, kernel: edge)
UI:      console
systemd: no (not supported by pmaports branch)
    • Oliver Smith mentioned in merge request !2480 (merged)

      mentioned in merge request !2480 (merged)

    • Oliver Smith
      Oliver Smith @ollieparanoid ·
      Maintainer

      Printing "pmbootstrap status" output at the end is a good step in that direction and useful in any case, thanks for doing that.

      I'm in favour of adding this, it seems useful. However it kinda violates some core assumptions encoded into the pkgrepo api currently.

      I've reworked it in !2480 (merged), please take a look (currently tests are failing, I'm fixing it.)

    • Oliver Smith assigned to @ollieparanoid

      assigned to @ollieparanoid

    • Oliver Smith closed with merge request !2480 (merged)

      closed with merge request !2480 (merged)

    Please register or sign in to reply