README.md (1839B)
1 # Aptly repository layout 2 3 The package repository on `taler-packaging@taler.net` has one mutable testing 4 repo for each supported distribution: 5 6 | Build distro | Testing repo | Publish prefix | 7 | --- | --- | --- | 8 | `debian-trixie` | `taler-debian-trixie-testing` | `apt/debian` | 9 | `ubuntu-noble` | `taler-ubuntu-noble-testing` | `apt/ubuntu` | 10 11 These prefixes use aptly's default filesystem endpoint. Aptly therefore 12 publishes them below its default publish directory as 13 `$rootDir/public/apt/debian` and `$rootDir/public/apt/ubuntu`; no named 14 filesystem endpoint is involved. 15 16 All repositories use the `main` component and publish `amd64` and `arm64`. 17 Testing distributions are `trixie-testing` and `noble-testing`; stable 18 distributions are `trixie` and `noble`. 19 20 Run the initialization from `packaging/ng`: 21 22 ``` 23 ./taler-pkg init 24 ``` 25 26 The command creates anything missing for both distributions. It publishes a 27 snapshot of each testing repo, creates an empty initial snapshot, and publishes 28 that empty snapshot as stable. Rerunning the command validates the existing 29 topology and otherwise does nothing. It deliberately refuses to replace 30 incompatible publications. 31 32 Normal uploads go only to the testing repos. `taler-pkg publish DISTRO` 33 snapshots the complete testing repo and switches the testing publication to 34 that snapshot. `taler-pkg promote DISTRO` switches stable to the snapshot 35 currently published in testing. Pending imports are excluded from promotion 36 and from `show-published DISTRO-testing` until successfully published. 37 38 Testing repos retain all imported versions. Snapshots, including those from 39 failed publish attempts, are retained for manual rollback. Both stable and 40 testing publications must use snapshots from their distribution's testing 41 repo, except that stable may still use its empty initial snapshot.