March 2023 - gerrit-log - lists.osmocom.org

[S] Change in osmo-gsm-manuals[master]: chapters/spectrum: Extend disclaimer to Osmocom authors
by laforge 21 Mar '23

21 Mar '23

laforge has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32011 ) Change subject: chapters/spectrum: Extend disclaimer to Osmocom authors ...................................................................... chapters/spectrum: Extend disclaimer to Osmocom authors Change-Id: I22dc5bde7a8d48c1a7dc876343ee66954afc2f8d --- M common/chapters/spectrum.adoc 1 file changed, 11 insertions(+), 2 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/11/32011/1 diff --git a/common/chapters/spectrum.adoc b/common/chapters/spectrum.adoc index 25e474e..5a6286f 100644 --- a/common/chapters/spectrum.adoc +++ b/common/chapters/spectrum.adoc @@ -14,8 +14,8 @@ operator of the interfered network, but is punishable as a crime under most jurisdictions. -sysmocom disclaims any responsibility for illegal / unlicensed use of -its products. +sysmocom and/or the authors of the Osmocom software disclaim any +responsibility for illegal / unlicensed use of its products. === Regulatory authorities by country -- To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32011 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Change-Id: I22dc5bde7a8d48c1a7dc876343ee66954afc2f8d Gerrit-Change-Number: 32011 Gerrit-PatchSet: 1 Gerrit-Owner: laforge <laforge(a)osmocom.org> Gerrit-MessageType: newchange

1 0

[S] Change in osmo-gsm-manuals[master]: chapters/abis: clarify which tool is used on what BTS model
by laforge 21 Mar '23

21 Mar '23

laforge has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32004 ) Change subject: chapters/abis: clarify which tool is used on what BTS model ...................................................................... chapters/abis: clarify which tool is used on what BTS model Change-Id: I256b38ff78e88529e9eb045f7b299a46e552f3f8 --- M common/chapters/abis.adoc 1 file changed, 18 insertions(+), 6 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/04/32004/1 diff --git a/common/chapters/abis.adoc b/common/chapters/abis.adoc index a46abfa..8542a1d 100644 --- a/common/chapters/abis.adoc +++ b/common/chapters/abis.adoc @@ -28,17 +28,18 @@ === Locate Abis/IP based BTS -We can use a tool called abisip-find to be able to find BTS which is +We can use a tool called `abisip-find` to be able to find BTS which is connected in the network. This tool is located in the OsmoBSC project -repository under: +source code repository under: './src/ipaccess' ==== abisip-find -abisip-find is a small command line tool which is used to search and -find BTS devices in your network (e.g. sysmoBTS, nanoBTS). +`abisip-find` is a small command line tool which is used to search and +find BTS devices in your network (e.g. sysmoBTS, nanoBTS, or in general +any BTS using `osmo-bts`). It uses broadcast packets of the UDP variant of the Abis-IP protocol on port 3006, and thus will find any BTS that can be reached by the @@ -82,8 +83,10 @@ ==== ipaccess-config This program is very helpful tool which is used to configure Unit ID and -Primary OML IP. You can find this tool in the OsmoBSC repository under: -'./src/ipaccess' +Primary OML IP of ip.access nanoBTS devices. It is specific to those +devices and *not compatible with osmo-bts*. + +You can find this tool in the OsmoBSC repository under: './src/ipaccess' .Example: using ipaccess-config to configure Unit ID and Primary OML IP of -- To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32004 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Change-Id: I256b38ff78e88529e9eb045f7b299a46e552f3f8 Gerrit-Change-Number: 32004 Gerrit-PatchSet: 1 Gerrit-Owner: laforge <laforge(a)osmocom.org> Gerrit-MessageType: newchange

1 0

[S] Change in osmo-gsm-manuals[master]: chapters/*: Fix typos
by laforge 21 Mar '23

21 Mar '23

laforge has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32006 ) Change subject: chapters/*: Fix typos ...................................................................... chapters/*: Fix typos Change-Id: I3c5cc64435c808f981d705d1d99c89fde2a6a74e --- M common/chapters/gb-ns2.adoc M common/chapters/glossary.adoc M common/chapters/installation.adoc M common/chapters/logging.adoc M common/chapters/mgwpool.adoc M common/chapters/oap.adoc M common/chapters/preface.adoc M common/chapters/qos-dscp-pcp.adoc 8 files changed, 23 insertions(+), 14 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/06/32006/1 diff --git a/common/chapters/gb-ns2.adoc b/common/chapters/gb-ns2.adoc index 925f515..e72fa50 100644 --- a/common/chapters/gb-ns2.adoc +++ b/common/chapters/gb-ns2.adoc @@ -249,7 +249,7 @@ static configuration The static configuration requires to configure all endpoints on the BSS and SGSN. -In constrast the dynamic configuration allows the SGSN to have only a reduced configuration. +In contrast the dynamic configuration allows the SGSN to have only a reduced configuration. ===== Gb over IP "ip.access style" dynamic configuration diff --git a/common/chapters/glossary.adoc b/common/chapters/glossary.adoc index 7c706b9..bbddcc5 100644 --- a/common/chapters/glossary.adoc +++ b/common/chapters/glossary.adoc @@ -136,7 +136,7 @@ GSM tap; pseudo standard for encapsulating GSM protocol layers over UDP/IP for analysis GSUP:: - Generic ubscriber Update Protocol. Osmocom-specific alternative to TCAP/MAP + Generic Subscriber Update Protocol. Osmocom-specific alternative to TCAP/MAP GT:: Global Title; an address in SCCP GTP:: diff --git a/common/chapters/installation.adoc b/common/chapters/installation.adoc index a3193fa..55b7e60 100644 --- a/common/chapters/installation.adoc +++ b/common/chapters/installation.adoc @@ -60,9 +60,9 @@ In general, the usual approach is to -* start with `libosmocore` and all the required librarires and build +* start with `libosmocore` and all the required libraries and build them in order until you have the full chain of dependencies in place. As a final step, build the actual application you want to use. -* perform `autoreconf -fi`, `./confiugre` and `make install` for each of +* perform `autoreconf -fi`, `./configure` and `make install` for each of the projects. Check the `./configure --help` output to see which optional compile-time features you might want to enable or disable. diff --git a/common/chapters/logging.adoc b/common/chapters/logging.adoc index b0a1f5e..a832ca4 100644 --- a/common/chapters/logging.adoc +++ b/common/chapters/logging.adoc @@ -32,7 +32,7 @@ different category, allowing fine-grained control over which log messages you will or will not see. For example, in OsmoBSC, there are categories for the protocol layers `rsl`, `rr`, `mm`, -`cc` and many others. To get a a list of categories interactively +`cc` and many others. To get a list of categories interactively on the vty, type: `logging level ?` [[log_levels]] diff --git a/common/chapters/mgwpool.adoc b/common/chapters/mgwpool.adoc index c8f2009..c4cf28a 100644 --- a/common/chapters/mgwpool.adoc +++ b/common/chapters/mgwpool.adoc @@ -66,7 +66,7 @@ The VTY implements a 'show mgw-pool' command that lists the currently configured MGW pool members, their status and call utilization. The following snippet shows an output example run on OsmoBSC, but it should be also available on other -applications supporting the MGW pooling VTY featues: +applications supporting the MGW pooling VTY features: ---- OsmoBSC> show mgw-pool @@ -88,7 +88,7 @@ However it is still possible to assign any number from 0-255. The enumeration also may contain gaps. The following snippet shows an output example run on OsmoBSC, but it should be also available on other applications supporting the -MGW pooling VTY featues: +MGW pooling VTY features: ---- OsmoBSC> enable @@ -163,7 +163,7 @@ happens locally to forward the UDP datagrams properly. Also (unless a reset endpoint is configured like in the example config above) there will be no immediate interaction with the MGW. However, the log should at least confirm -the the connect worked and the MGCP client has been created successfully. +the connect worked and the MGCP client has been created successfully. ---- Mon Aug 2 17:15:00 2021 DLMGCP mgcp_client.c:788 MGCP client: using endpoint domain '@mgw' diff --git a/common/chapters/oap.adoc b/common/chapters/oap.adoc index ad91f36..425ff75 100644 --- a/common/chapters/oap.adoc +++ b/common/chapters/oap.adoc @@ -81,7 +81,7 @@ authenticity and validity of the sequence number (included in AUTN), and, if valid, reply with a CHALLENGE_RES message. This shall contain an XRES authentication token generated by milenage from the same random bytes received -from the server and the same shared secet. If the client decides to cancel the +from the server and the same shared secret. If the client decides to cancel the registration (e.g. invalid AUTN), it shall not reply to the CHALLENGE_REQ; a CHALLENGE_ERR message may be sent, but is not mandatory. For example, the client may directly start with a new REGISTER_REQ message. diff --git a/common/chapters/preface.adoc b/common/chapters/preface.adoc index b8f7e72..272f84a 100644 --- a/common/chapters/preface.adoc +++ b/common/chapters/preface.adoc @@ -117,13 +117,13 @@ is about sharing ideas and code, but also about sharing the effort of software development and maintenance. -If your organization is benefitting from using Osmocom software, please +If your organization is benefiting from using Osmocom software, please consider ways how you can contribute back to that community. Such contributions can be many-fold, for example * sharing your experience about using the software on the public mailing lists, helping to establish best practises in using/operating it, -* providing qualified bug reports, work-arounds +* providing qualified bug reports, workarounds * sharing any modifications to the software you may have made, whether bug fixes or new features, even experimental ones * providing review of patches diff --git a/common/chapters/qos-dscp-pcp.adoc b/common/chapters/qos-dscp-pcp.adoc index 3f97941..81a9e4e 100644 --- a/common/chapters/qos-dscp-pcp.adoc +++ b/common/chapters/qos-dscp-pcp.adoc @@ -77,7 +77,7 @@ header. NOTE:: This means that PCP functionality requires the use of IEEE 802.q -VLAN. You cannot use PCP without VLAN +VLAN. You cannot use PCP without VLAN. The Linux kernel assigns IEEE 802.1q PCP bits based on a _mapping_ between the _priority_ and the PCP value. Each VLAN network device @@ -148,7 +148,7 @@ . configure the osmocom program to set the DSCP value . use the default DSCP -> priority mapping, if possible -. configure an egrees QoS map to map from priority to PCP +. configure an egress QoS map to map from priority to PCP If the desired combination of DSCP + PCP cannot be achieved that way, due to the rather static default kernel mapping table, one needs to go @@ -156,6 +156,6 @@ . configure the osmocom program to set the DSCP value . use packet filter rules to set the priority based on DSCP -. configure an egrees QoS map to map from priority to PCP +. configure an egress QoS map to map from priority to PCP include::{srcdir}/chapters/qos-example.adoc[] -- To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32006 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Change-Id: I3c5cc64435c808f981d705d1d99c89fde2a6a74e Gerrit-Change-Number: 32006 Gerrit-PatchSet: 1 Gerrit-Owner: laforge <laforge(a)osmocom.org> Gerrit-MessageType: newchange

1 0

[M] Change in osmo-gsm-manuals[master]: chapters/cell-broadcast: Bring up-to-date with reality
by laforge 21 Mar '23

21 Mar '23

laforge has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32005 ) Change subject: chapters/cell-broadcast: Bring up-to-date with reality ...................................................................... chapters/cell-broadcast: Bring up-to-date with reality This chapter was written at a time where OsmoCBC and the related BSC support didn't exist yet. Change-Id: If02adf2f9e7beeb7f238ab1c3aa74e8c0155db2b --- M common/chapters/cell-broadcast.adoc 1 file changed, 32 insertions(+), 26 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/05/32005/1 diff --git a/common/chapters/cell-broadcast.adoc b/common/chapters/cell-broadcast.adoc index 842e8d1..c1d9581 100644 --- a/common/chapters/cell-broadcast.adoc +++ b/common/chapters/cell-broadcast.adoc @@ -3,7 +3,7 @@ Normally, all user plane data in GSM/GPRS networks are sent in point-to-point channels from the network to the user. Those are called -"dedicated" radio channels which exist between the network and one +_dedicated_ radio channels which exist between the network and one given phone/subscriber at a time. Cell Broadcast is an exception to that rule. It permits user data @@ -35,39 +35,33 @@ === Osmocom Cell Broadcast support -* OsmoBTS implements the "SMS BROADCAST COMMAND" Message in RSL - according to Section 8.5.8 of 3GPP TS 08.58 -* OsmoNITB and OsmoBSC implement a VTY command - `bts <0-255> smscb-command <1-4> HEXSTRING` to send a given hex-formatted cell - broadcast message to a specified BTS +* OsmoBTS implements the `SMS BROADCAST COMMAND` Message in A-bis RSL + according to Section 8.5.8 of 3GPP TS 48.058 +* low-level testing/debugging features +** OsmoNITB and OsmoBSC implement a VTY command + `bts <0-255> smscb-command <1-4> HEXSTRING` to send a given hex-formatted cell + broadcast message to a specified BTS. This can be used for low-level debugging +* proper 3GPP-specified CBS/PWS elements and protocols +** OsmoBSC supports routing and distribution of CBS and warning messages +** OsmoBSC implements the BSC-CBC interface using the CBSP protocol +** OsmoCBC implements the central function of a _Cell Broadcast Centre_, + receiving cell broadcast and warning messages from external entities + via a REST based HTTP interface, and distributing it throughout the + cellular network. +** OsmoCBC implements the BSC-CBC interface using the CBSP protocol (for + 2G/GSM RAN) +** OsmoCBC implements the MME-CBC interface using the SBcAP protocol (for + 4G/LTE RAN) + [mscgen] ---- include::osmocom-cbs.msc[] ---- -==== What's missing - -What's missing (for production operation in larger networks) - -* mechanism to broadcast one (set of) cell broadcast messages from the - BSC to multiple/all BTSs, rather than one BTS individually -* OsmoBTS reporting of current CBCH load -* BSC scheduler scheduling multiple alternating sets of CBCH messages - based on the current CBCH load reported by BTS -* external interface from BSC to a Cell Broadcast Center (CBC), e.g. - according to 3GPP TS 48.049 -* an Osmocom implementation of the Cell Broadcast Center (OsmoCBC) - which can manage and distribute messages to multiple BSCs and which - has an external interface by which cell-broadcast can be entered - into the network - -If you would like to contribute in any of those areas (by means of -code or funding), please reach out to us any time. - === Message Structure -* Each message has a meximum of 15 pages +* Each message has a maximum of 15 pages * Each page is 82 bytes of data, resulting in 93 characters in GSM 7-bit default alphabet * Messages are broadcast on logical channels (more like an address) -- To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32005 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Change-Id: If02adf2f9e7beeb7f238ab1c3aa74e8c0155db2b Gerrit-Change-Number: 32005 Gerrit-PatchSet: 1 Gerrit-Owner: laforge <laforge(a)osmocom.org> Gerrit-MessageType: newchange

1 0

[S] Change in osmo-gsm-manuals[master]: chapters/mncc: Update the wording to be less confusing and more up-to...
by laforge 21 Mar '23

21 Mar '23

laforge has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32003 ) Change subject: chapters/mncc: Update the wording to be less confusing and more up-to-date ...................................................................... chapters/mncc: Update the wording to be less confusing and more up-to-date Change-Id: Ic8876509878e565f140508dc2e3494b0e21c566c --- M common/chapters/mncc.adoc 1 file changed, 14 insertions(+), 4 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/03/32003/1 diff --git a/common/chapters/mncc.adoc b/common/chapters/mncc.adoc index 3c67998..e56afeb 100644 --- a/common/chapters/mncc.adoc +++ b/common/chapters/mncc.adoc @@ -56,10 +56,11 @@ to disable the internal MNCC handler and specify the MNCC socket path in the configuration file. -At the time of this writing, the only external application implementing the -MNCC interface compatible with the Osmocom MNCC socket is `lcr`, the Linux Call -Router. More widespread integration of external call routing is available via -the OsmoSIPConnector. +At the time of this writing, there are only two known open source application implementing the +MNCC interface compatible with the Osmocom MNCC socket: + +* historically `lcr`, the Linux Call Router (support for modern MNCC protocol versions may be missing) +* `osmo-sip-connector`, the more up-to-date integration of external call routing by translating MNCC into a SIP trunk towards an external SIP PBX / switch. === DTMF considerations -- To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/32003 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Change-Id: Ic8876509878e565f140508dc2e3494b0e21c566c Gerrit-Change-Number: 32003 Gerrit-PatchSet: 1 Gerrit-Owner: laforge <laforge(a)osmocom.org> Gerrit-MessageType: newchange

1 0

[S] Change in osmo-sip-connector[master]: doc: fix typo
by laforge 21 Mar '23

21 Mar '23

laforge has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-sip-connector/+/32001 ) Change subject: doc: fix typo ...................................................................... doc: fix typo Change-Id: Ie001645e9b44cb5e16090813ca4f053118ac39a4 --- M doc/manuals/chapters/overview.adoc 1 file changed, 10 insertions(+), 1 deletion(-) git pull ssh://gerrit.osmocom.org:29418/osmo-sip-connector refs/changes/01/32001/1 diff --git a/doc/manuals/chapters/overview.adoc b/doc/manuals/chapters/overview.adoc index 24fe8b9..c65e5ad 100644 --- a/doc/manuals/chapters/overview.adoc +++ b/doc/manuals/chapters/overview.adoc @@ -8,7 +8,7 @@ === About OsmoSIPConnector OsmoSIPConnector translates between Mobile Network Call Control (MNCC) -used in the GSM newtwork and Voice over IP SIP call control messages so that +used in the GSM network and Voice over IP SIP call control messages so that speech calls can traverse through the mobile network to SIP and vice versa. It has the following interfaces: -- To view, visit https://gerrit.osmocom.org/c/osmo-sip-connector/+/32001 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-sip-connector Gerrit-Branch: master Gerrit-Change-Id: Ie001645e9b44cb5e16090813ca4f053118ac39a4 Gerrit-Change-Number: 32001 Gerrit-PatchSet: 1 Gerrit-Owner: laforge <laforge(a)osmocom.org> Gerrit-MessageType: newchange

1 0

[S] Change in osmo-sip-connector[master]: doc: Expand the virtually empty user manual with some basics
by laforge 21 Mar '23

21 Mar '23

laforge has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-sip-connector/+/32002 ) Change subject: doc: Expand the virtually empty user manual with some basics ...................................................................... doc: Expand the virtually empty user manual with some basics Change-Id: Id42904a183b045eefac15a94139221a3bc65ecdd --- M doc/manuals/chapters/overview.adoc 1 file changed, 30 insertions(+), 0 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-sip-connector refs/changes/02/32002/1 diff --git a/doc/manuals/chapters/overview.adoc b/doc/manuals/chapters/overview.adoc index c65e5ad..a06b410 100644 --- a/doc/manuals/chapters/overview.adoc +++ b/doc/manuals/chapters/overview.adoc @@ -16,6 +16,27 @@ - SIP towards the PBX - The Osmocom typical telnet VTY interface. +The SIP implemented by osmo-sip-connector can be characterized as follows: + +Only a SIP trunk is supported; it will appear to the remote SIP server (PBX) like +another PBX (or a public network) interfaced via a trunk. Specifically, this means +there is no SIP REGISTER or any form of authentication supported. You +will need to configure the SIP peer to implicitly authorize the trunk by +its IP address / port. + +osmo-sip-connector handles only the signaling translation between GSM CC +and SIP, but does not handle RTP. The RTP user plane is passed +transparently from the MSC-colocated osmo-mgw to the SIP side. This also +means that no transcoding is performed. The RTP streams contain whatever +cellular specific codec you have configured your network to use for this +call (FR, EFR, HR, AMR). Hence, **the SIP peer must support the +codec[s] you have configured on your MSC/BSC** + +As the osmo-sip-connector attaches to the external MNCC socket of +OsmoMSC, running osmo-sip-connector will disable the internal call +routing of OsmoMSC, see the related OsmoMSC documentation. All mobile +originated calls originating in GSM will be passed to the SIP connector. + Find the OsmoSIPConnector issue tracker and wiki online at - https://osmocom.org/projects/osmo-sip-connector -- To view, visit https://gerrit.osmocom.org/c/osmo-sip-connector/+/32002 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-sip-connector Gerrit-Branch: master Gerrit-Change-Id: Id42904a183b045eefac15a94139221a3bc65ecdd Gerrit-Change-Number: 32002 Gerrit-PatchSet: 1 Gerrit-Owner: laforge <laforge(a)osmocom.org> Gerrit-MessageType: newchange

1 0

[M] Change in docker-playground[master]: debian-bullseye-jenkins-arm: add new container
by pespin 21 Mar '23

21 Mar '23

Attention is currently required from: osmith. pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/docker-playground/+/31998 ) Change subject: debian-bullseye-jenkins-arm: add new container ...................................................................... Patch Set 2: Code-Review+1 -- To view, visit https://gerrit.osmocom.org/c/docker-playground/+/31998 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: docker-playground Gerrit-Branch: master Gerrit-Change-Id: I8e1741f86ffb8abd658d1e4e0415dfd11fb1a8a1 Gerrit-Change-Number: 31998 Gerrit-PatchSet: 2 Gerrit-Owner: osmith <osmith(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Attention: osmith <osmith(a)sysmocom.de> Gerrit-Comment-Date: Tue, 21 Mar 2023 17:19:58 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment

1 0

[M] Change in docker-playground[master]: debian-bullseye-jenkins-arm: add new container
by osmith 21 Mar '23

21 Mar '23

Attention is currently required from: pespin. osmith has posted comments on this change. ( https://gerrit.osmocom.org/c/docker-playground/+/31998 ) Change subject: debian-bullseye-jenkins-arm: add new container ...................................................................... Patch Set 1: (1 comment) File debian-bullseye-jenkins-arm/Makefile: https://gerrit.osmocom.org/c/docker-playground/+/31998/comment/e9d2b95b_3f7… PS1, Line 1: UPSTREAM_DISTRO=debian:buster-slim > Shouldn't this be bullseye? Done -- To view, visit https://gerrit.osmocom.org/c/docker-playground/+/31998 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: docker-playground Gerrit-Branch: master Gerrit-Change-Id: I8e1741f86ffb8abd658d1e4e0415dfd11fb1a8a1 Gerrit-Change-Number: 31998 Gerrit-PatchSet: 1 Gerrit-Owner: osmith <osmith(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Attention: pespin <pespin(a)sysmocom.de> Gerrit-Comment-Date: Tue, 21 Mar 2023 17:13:45 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: pespin <pespin(a)sysmocom.de> Gerrit-MessageType: comment

1 0

[M] Change in docker-playground[master]: debian-bullseye-jenkins-arm: add new container
by osmith 21 Mar '23

21 Mar '23

Attention is currently required from: osmith. Hello Jenkins Builder, pespin, I'd like you to reexamine a change. Please visit https://gerrit.osmocom.org/c/docker-playground/+/31998 to look at the new patch set (#2). Change subject: debian-bullseye-jenkins-arm: add new container ...................................................................... debian-bullseye-jenkins-arm: add new container Add a bullseye based container that can be used instead of debian-buster-jenkins-arm. The master-builds jenkins jobs will attempt to use this jenkins job for the arm builds after setting the main default image from debian-buster-jenkins to debian-bullseye-jenkins. Related: OS#5949 Change-Id: I8e1741f86ffb8abd658d1e4e0415dfd11fb1a8a1 --- A debian-bullseye-jenkins-arm/Dockerfile A debian-bullseye-jenkins-arm/Makefile 2 files changed, 96 insertions(+), 0 deletions(-) git pull ssh://gerrit.osmocom.org:29418/docker-playground refs/changes/98/31998/2 -- To view, visit https://gerrit.osmocom.org/c/docker-playground/+/31998 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: docker-playground Gerrit-Branch: master Gerrit-Change-Id: I8e1741f86ffb8abd658d1e4e0415dfd11fb1a8a1 Gerrit-Change-Number: 31998 Gerrit-PatchSet: 2 Gerrit-Owner: osmith <osmith(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Attention: osmith <osmith(a)sysmocom.de> Gerrit-MessageType: newpatchset

1 0