Oh please no. For one thing, we shouldn't need this anymore now that livecd-rootfs calls germinate directly. For another thing, 'ubuntu-live' is not a correct task name that appears anywhere in the archive. And thirdly, these packages shouldn't be injected into the platform-independent tasks.
> Package: ubuntu-concept-x13s
Immediately I notice this uses a completely different structure to what's used on raspberry pi. We should have a think about how to handle platform metapackages consistently in the archive.
Also I have no idea why 'concept' appears in the package name here, it appears to be a reference to the PPA name only and has nothing to do with the hardware platform branding.
> * agree subarch name, proposed "x13s"
This is fine.
> * install ubuntu-concept-x13s meta package
[...]
> no signer
> * Auto build.
> -- Launchpad Package Builder <email address hidden> Thu, 21 Sep 2023 11:31:33 +0000
Interesting. So where does this come from? https:/ /launchpad. net/~ubuntu- concept/ +archive/ ubuntu/ x13s points to https:/ /code.launchpad .net/~ubuntu- concept/ +recipe/ ubuntu- concept- x13s which 404s.
> XB-Task: ubuntu-live, ubuntu-desktop, ubuntu- desktop- minimal
Oh please no. For one thing, we shouldn't need this anymore now that livecd-rootfs calls germinate directly. For another thing, 'ubuntu-live' is not a correct task name that appears anywhere in the archive. And thirdly, these packages shouldn't be injected into the platform- independent tasks.
> Package: ubuntu-concept-x13s
Immediately I notice this uses a completely different structure to what's used on raspberry pi. We should have a think about how to handle platform metapackages consistently in the archive.
Also I have no idea why 'concept' appears in the package name here, it appears to be a reference to the PPA name only and has nothing to do with the hardware platform branding.