You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/getting-started/advanced-setup/repro.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,20 +41,20 @@ the non-updated repos).
41
41
42
42
The following table lists the codenames of distributions that we currently support:
43
43
44
-
- Ubuntu 20.04:
45
-
- Distribution Version: 20.04
46
-
- Codename: focal
47
44
- Ubuntu 22.04:
48
45
- Distribution Version: 22.04
49
46
- Codename: jammy
50
47
- Ubuntu 24.04:
51
48
- Distribution Version: 24.04
52
49
- Codename: noble
50
+
- Ubuntu 26.04:
51
+
- Distribution Version: 26.04
52
+
- Codename: resolute
53
53
54
54
Depending on your host OS release you might not have `debootstrap` manifests for versions newer than your host OS. Due to this we run the `debootstrap` commands in a container of the latest version itself:
Since we pass the `Dockerfile` through `stdin` the build command will not create a context, i.e., the current directory is not passed to `docker` and it'll be independent of the currently checked out version. This also means that you will be able to reuse the docker image for future builds, and don't have to repeat this dance every time. Verifying the `Dockerfile` therefore is
@@ -102,9 +102,9 @@ Finally, after finishing the environment setup we can perform the actual build.
102
102
We'll need the release directory available for this, so create it now if it doesn't exist:`mkdir release`, then we can simply execute the following command inside the git repository (remember to checkout the tag you are trying to build):
103
103
104
104
```bash
105
-
docker run --rm -v $(pwd):/repo -ti cl-repro-focal
106
105
docker run --rm -v $(pwd):/repo -ti cl-repro-jammy
107
106
docker run --rm -v $(pwd):/repo -ti cl-repro-noble
107
+
docker run --rm -v $(pwd):/repo -ti cl-repro-resolute
108
108
```
109
109
110
110
The last few lines of output also contain the `sha256sum` hashes of all artifacts, so if you're just verifying the build those are the lines that are of interest to you:
@@ -123,7 +123,7 @@ The release captain is in charge of creating the manifest, whereas contributors
123
123
## Script build-release
124
124
1: Pull latest code from master
125
125
126
-
2: Run the `tools/build-release.sh bin-Fedora bin-Ubuntu sign` script. This will create a release directory, build binaries for Fedora, and build binaries for Ubuntu (Focal, Jammy, and Noble). Finally, it will sign the ZIP, Fedora, and Ubuntu builds.
126
+
2: Run the `tools/build-release.sh bin-Fedora bin-Ubuntu sign` script. This will create a release directory, build binaries for Fedora, and build binaries for Ubuntu (Jammy, Noble, and Resolute). Finally, it will sign the ZIP, Fedora, and Ubuntu builds.
127
127
128
128
## Manual
129
129
The release captain creates the manifest as follows:
@@ -143,7 +143,7 @@ gpg -sb --armor SHA256SUMS
143
143
144
144
2: Copy above files in the lightning directory.
145
145
146
-
3: Run `tools/build-release.sh --verify` script. It will build binaries for Ubuntu (Focal, Jammy & Noble), verify zip & Ubuntu builds while copying Fedora checksums from the release captain's file.
146
+
3: Run `tools/build-release.sh --verify` script. It will build binaries for Ubuntu (Jammy, Noble & Resolute), verify zip & Ubuntu builds while copying Fedora checksums from the release captain's file.
147
147
148
148
4. Then send the resulting `release/SHA256SUMS.asc` file to the release captain so it can be merged with the other signatures into `SHASUMS.asc`.
149
149
@@ -200,9 +200,9 @@ Producing output similar to the following:
200
200
```shell
201
201
sha256sum: clightning-v24.11-Fedora-35-amd64.tar.gz: No such file or directory
202
202
clightning-v24.11-Fedora-35-amd64.tar.gz: FAILED open or read
203
-
clightning-v24.11-Ubuntu-20.04.tar.xz: OK
204
203
clightning-v24.11-Ubuntu-22.04.tar.xz: OK
205
204
clightning-v24.11-Ubuntu-24.04.tar.xz: OK
205
+
clightning-v24.11-Ubuntu-26.04.tar.xz: OK
206
206
clightning-v24.11.zip: OK
207
207
sha256sum: WARNING: 1 listed file could not be read
0 commit comments