← Back to team overview

launchpad-users team mailing list archive

Forking and building "linux-raspi" for Kairos

 

Hi,

_Disclaimer: I'm completely new to launchpad._

In the context of this Kairos issue: https://github.com/kairos-io/kairos/issues/2249 I'm trying to create a ppa by forking this package: https://launchpad.net/ubuntu/+source/linux-raspi

The goal it to apply a single change[1] to the package to re-enable grub efi stub on raspberry PIs. We do this because we don't care about the increase in size which was the reason given here:

https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2053147

but we do care about the Kairos Ubuntu flavor working on Raspberry pi.

So I went on and forked the package, applied my change and then clicked on that link to create a build recipe. Initially I left the default content and the played
a bit with the variables (removing `revtime` I think):

```
# git-build-recipe format 0.4 deb-version {debupstream}-1
lp:~dkarakasilis/ubuntu/+source/linux-raspi ubuntu/noble-devel
```

No matter what I do, the upload fails with errors like:

```
DEBUG Considering changefile 3429361/ubuntu/linux-raspi_6.8.0-1~ubuntu24.04.1_source.changes
DEBUG Finding fresh policy
INFO Processing upload linux-raspi_6.8.0-1~ubuntu24.04.1_source.changes
INFO Upload was rejected:
INFO     6.8.0-1~ubuntu24.04.1: should be 6.8.0-1011.12 according to changes file.
INFO Committing the transaction and any mails associated with this upload.
```

I assumed I needed a line in `debian/changelog` (or maybe one of the other `changelog` files?) so
I made a change like:

```
diff --git a/debian/changelog b/debian/changelog
index 77480403f4..70716064c3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,7 @@
+linux-raspi (6.8.0-1) noble; urgency=medium
+
+  * re-enabled grub efi stub (https://github.com/kairos-io/kairos/issues/2249)
+
 linux-raspi (6.8.0-1011.12) noble; urgency=medium
```

but that didn't help either (still the artifact name doesn't match). I'm reading various document in https://help.launchpad.net/Packaging/PPA but they usually refer
to a flow I didn't follow (with cli tools I didn't use).

Is the problem in my build recipe or the flow I used? Also, is there a way to keep
this package rebased automatically on upstream?

Thanks,
Dimitris Karakasilis




[1]:
```
diff --git a/debian.raspi/config/annotations b/debian.raspi/config/annotations
index f69c52956c..72811a36f4 100644
--- a/debian.raspi/config/annotations
+++ b/debian.raspi/config/annotations
@@ -225,7 +225,6 @@ CONFIG_DW_AXI_DMAC policy<{'arm64': 'y'}> note<'Nee
 CONFIG_DW_I3C_MASTER policy<{'arm64': 'n'}> note<'Different from master'>
 CONFIG_ECRYPT_FS policy<{'arm64': 'm'}> note<'Not essential on Pi (different from master)'>
 CONFIG_EDAC_XGENE policy<{'arm64': 'n'}> note<'Different from master'>
-CONFIG_EFI policy<{'arm64': 'n'}> note<'Not supported on Pi (different from master)'>
 CONFIG_EFIVAR_FS policy<{'arm64': '-'}> note<'Master note override'>
 CONFIG_EFI_ZBOOT policy<{'arm64': '-'}> note<'Master note override'>
 CONFIG_ENA_ETHERNET policy<{'arm64': 'n'}> note<'Different from master'>
 ```