Linux Distributions » History » Version 10
osmith, 12/05/2023 01:01 PM
1 | 1 | osmith | h2. Linux Distributions |
---|---|---|---|
2 | |||
3 | This article lists for which Linux distributions we provide Osmocom binary packages, and where these distributions are used in our CI infrastructure. |
||
4 | |||
5 | h3. Debian |
||
6 | |||
7 | h4. Releases |
||
8 | |||
9 | 3 | osmith | Binary packages are provided for the following "Debian releases":https://www.debian.org/releases/: |
10 | 2 | osmith | * unstable (sid) |
11 | 1 | osmith | * 12 (bookworm) |
12 | * 11 (bullseye) |
||
13 | * 10 (buster) |
||
14 | |||
15 | h4. CI infrastructure |
||
16 | |||
17 | CI uses the latest stable Debian release where possible (master builds and various other jenkins jobs). |
||
18 | |||
19 | Building Debian packages is verified in gerrit verifications for the oldest and newest Debian release that we build binary packages for. |
||
20 | |||
21 | The <code>ttcn3-*-test</code> and <code>ttcn3-*-test-latest</code> jobs use the latest stable Debian release for testsuites and SUT (system under test, the Osmocom programs). |
||
22 | |||
23 | h4. Adding/removing releases |
||
24 | |||
25 | * Adding binary packages for new Debian releases should be done in our OBS, after they are usable via https://build.opensuse.org. |
||
26 | * Removal of binary packages for releases is not that urgent, as long as we don't see build or unit test failures just on those old releases. |
||
27 | * If we do see build or unit test failures, we should remove the distro from the builds and not invest time in workarounds. |
||
28 | |||
29 | 6 | osmith | h3. Raspberry Pi OS |
30 | 1 | osmith | |
31 | 6 | osmith | h4. Releases |
32 | 1 | osmith | |
33 | 6 | osmith | Binary packages are provided for the *32-bit versions* of the following "Raspberry Pi OS releases":https://en.wikipedia.org/wiki/Raspberry_Pi_OS#Releases: |
34 | 7 | osmith | * 12 (bookworm) |
35 | 6 | osmith | * 11 (bullseye) |
36 | * 10 (buster) |
||
37 | |||
38 | For users of 64-bit Raspberry Pi OS, we recommend using the aarch64 packages we build for Debian. |
||
39 | |||
40 | |||
41 | h4. Adding/removing releases |
||
42 | |||
43 | * Same as for Debian (though the Raspberry Pi OS releases seem to lack behind) |
||
44 | |||
45 | 1 | osmith | h3. Ubuntu |
46 | |||
47 | h4. Releases |
||
48 | |||
49 | Binary packages are provided for the following "Ubuntu releases":https://en.wikipedia.org/wiki/Ubuntu_version_history#Table_of_versions: |
||
50 | 8 | osmith | * 23.10 |
51 | 1 | osmith | * 23.04 |
52 | * 22.04 LTS |
||
53 | * 20.04 LTS |
||
54 | |||
55 | h4. Adding/removing releases |
||
56 | |||
57 | 8 | osmith | * Have the current supported non-LTS release(s) (if any), and the last 2 supported LTS releases |
58 | 1 | osmith | |
59 | h3. CentOS |
||
60 | |||
61 | h4. Releases |
||
62 | |||
63 | Binary packages are provided for the following CentOS releases: |
||
64 | * CentOS 8 |
||
65 | * CentOS 7 (only few packages) |
||
66 | |||
67 | h4. CI infrastructure |
||
68 | |||
69 | 6 | osmith | Building CentOS 8 packages is verified in gerrit verifications against AlmaLinux 8. |
70 | 1 | osmith | |
71 | 6 | osmith | The <code>ttcn3-centos-*</code> jobs use AlmaLinux 8 for the SUT. |
72 | 1 | osmith | |
73 | h4. Adding/removing releases |
||
74 | |||
75 | * CentOS releases are added or removed on demand. |
||
76 | |||
77 | h3. OpenSUSE |
||
78 | |||
79 | h4. Releases |
||
80 | |||
81 | Binary packages are provided for the following "openSUSE releases":https://en.wikipedia.org/wiki/OpenSUSE#Version_history: |
||
82 | 3 | osmith | |
83 | 1 | osmith | * Tumbleweed (rolling) |
84 | |||
85 | h4. Adding/removing releases |
||
86 | |||
87 | 4 | osmith | * OpenSUSE releases are added or removed on demand. |
88 | 10 | osmith | |
89 | h2. See also |
||
90 | |||
91 | * [[Add a new distribution to OBS]] |
||
92 | * [[Binary Packages]] |