Latest Builds » History » Version 47
osmith, 07/22/2024 07:39 AM
update checksum of Release.key; the previous checksum was from the opensuse build server before we moved to the selfhosted one (OS#6505)
| 1 | 1 | laforge | {{>toc}} |
|---|---|---|---|
| 2 | |||
| 3 | h1. _Latest_ Builds |
||
| 4 | |||
| 5 | 9 | pespin | If you require current master version of the Osmocom GSM related software, go have a look at the [[Nightly_Builds]] alternative. NOTE: USE NIGHTLY BUILDS ONLY FOR DEVELOPMENT/TESTING. |
| 6 | 8 | pespin | |
| 7 | 34 | osmith | sysmocom has set up package builds for the _latest_ version tag of the Osmocom GSM related software. |
| 8 | 28 | laforge | |
| 9 | 34 | osmith | The packages are built for various Linux distributions, find the complete list at the OBS page: https://obs.osmocom.org/project/show/osmocom:latest |
| 10 | 1 | laforge | |
| 11 | A nice status overview on the builds is available at https://obs.osmocom.org/project/monitor/osmocom:latest |
||
| 12 | |||
| 13 | 34 | osmith | Browse the published binary packages at: https://downloads.osmocom.org/packages/osmocom:/latest/ |
| 14 | |||
| 15 | 1 | laforge | h2. How to use the _osmocom:latest_ builds |
| 16 | 32 | laforge | |
| 17 | 34 | osmith | h3. Debian based distributions |
| 18 | 1 | laforge | |
| 19 | 44 | osmith | h4. Using extrepo (Debian only) |
| 20 | 41 | osmith | |
| 21 | <pre> |
||
| 22 | # apt install extrepo |
||
| 23 | # extrepo enable osmocom-latest |
||
| 24 | </pre> |
||
| 25 | |||
| 26 | 44 | osmith | h4. Manually (Debian, Ubuntu, Raspberry Pi OS) |
| 27 | 41 | osmith | |
| 28 | 40 | osmith | Replace Debian_XX with your distribution name, as found "here":https://downloads.osmocom.org/packages/osmocom:/latest/. |
| 29 | 1 | laforge | |
| 30 | <pre> |
||
| 31 | 34 | osmith | $ sudo su |
| 32 | 40 | osmith | # OSMOCOM_REPO="https://downloads.osmocom.org/packages/osmocom:/latest/Debian_XX" |
| 33 | 38 | fixeria | # wget $OSMOCOM_REPO/Release.key |
| 34 | 1 | laforge | # sha256sum Release.key |
| 35 | 47 | osmith | 5c317407aef0671b7795d79942b4b9118dca199884d88accab2aae92a5ad08ba Release.key |
| 36 | 39 | osmith | # mv Release.key /etc/apt/trusted.gpg.d/osmocom-latest.asc |
| 37 | # echo "deb [signed-by=/etc/apt/trusted.gpg.d/osmocom-latest.asc] $OSMOCOM_REPO/ ./" > /etc/apt/sources.list.d/osmocom-latest.list |
||
| 38 | 34 | osmith | # apt-get update |
| 39 | # exit |
||
| 40 | 2 | laforge | </pre> |
| 41 | 3 | laforge | |
| 42 | 42 | osmith | h4. Raspberry Pi OS |
| 43 | |||
| 44 | Follow the instructions above, and replace Debian_XX with: |
||
| 45 | * 64-bit: Debian_11 |
||
| 46 | * 32-bit: Raspbian_11 |
||
| 47 | |||
| 48 | This example is for Raspberry Pi OS 11, adjust the number accordingly. |
||
| 49 | |||
| 50 | 37 | laforge | h2. Apt Pinning |
| 51 | |||
| 52 | 46 | laforge | With the above you now have osmocom packages as *one* package feed, but others (including your distribution) may be shipping packages incompatible with those supplied by osmocom. Mixing e.g. some libraries from distributions with applications from osmocom may render unwanted results. |
| 53 | |||
| 54 | In order to make sure that osmocom packages are always preferred over your distribution's upstream packages with the same name, see [[Apt_Pinning]] |
||
| 55 | 37 | laforge | |
| 56 | 34 | osmith | h2. How are those builds created? |
| 57 | 24 | laforge | |
| 58 | 34 | osmith | See [[OBS Maintenance]]. |
| 59 | 25 | laforge | |
| 60 | h2. Historical Archives / Older Packages |
||
| 61 | |||
| 62 | 43 | laforge | If you are interested in a historical archive of previous / older packages, you can find it at https://package-archive.osmocom.org/obs-mirror/ - it contains a daily mirror of the entire *osmocom:* OBS hierarchy, including the *latest* builds. The full URL e.g. for Raspbian 10 of April 22nd, 2021 would be https://package-archive.osmocom.org/obs-mirror/20210422-002301/latest/Raspbian_10/ |
