Support having the same package in both systemd and non-systemd repositories

Related: #140 (closed)

This is complex and buggy in bpo, I'll leave this out for the initial version of split systemd repository.

What I've run into so far:

• too much additional complexity in bpo to support this (especially given that I would need to write tests for it too)
• "pmbootstrap checksum" updates the checksum of the wrong package when having 2 with the same name
• "pmbootstrap repo_missing" only shows either the systemd or non-systemd package depending on if systemd is enabled or not; this is unexpected by bpo code and would need adjustments in either bpo or pmbootstrap
• in general not well tested using this feature in pmbootstrap I would assume, given that we currently don't use it
• pmbootstrap behaves unintuitively IMHO with this, you need to enable and disable systemd to work on both packages at the same time, e.g. if you want to upgrade both

changed the description

By Oliver Smith on 2024-09-22T11:53:53

changed the description

By Oliver Smith on 2024-09-22T11:54:05

mentioned in issue #140 (closed)

By Oliver Smith on 2024-09-22T13:43:53

added systemd label

changed the description

By Oliver Smith on 2024-09-22T16:04:17

As discussed with @calebccff and @craftyguy, I'll put this in the initial version after all. After some more research, the only real blocker is adjusting repo_missing and that shouldn't be too hard, so I'll do that.

By Oliver Smith on 2024-09-23T22:09:33

mentioned in merge request pmbootstrap!2410 (merged)

mentioned in issue #140 (closed)

mentioned in merge request !119 (merged)

closed with merge request !119 (merged)