Attention is currently required from: fixeria.
osmith has posted comments on this change by osmith. ( https://gerrit.osmocom.org/c/osmo-ci/+/41393?usp=email )
Change subject: OBS: sync_obs_projects: fix for OSC 1.12.1
......................................................................
Patch Set 1: Code-Review+2
(1 comment)
Patchset:
PS1:
> What a weird behavior. […]
yes. apparently they are moving the OBS sources from their custom versioning protocol to git (https://en.opensuse.org/openSUSE:OBS_to_Git - e.g. https://src.opensuse.org/llyyr/neovim - I guess we probably want to adapt that too at some point but it will need a lot of reworking probably on our part), and have added a lot of git-related code to osc. I didn't find a way to restore the previous behavior, this seemed the simplest solution without spending a lot of time on it.
--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/41393?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: I1236a065e2998fb46343df3968f7bb4dabeea55a
Gerrit-Change-Number: 41393
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Tue, 11 Nov 2025 06:57:56 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>
Attention is currently required from: lynxis lazus.
pespin has posted comments on this change by lynxis lazus. ( https://gerrit.osmocom.org/c/libosmo-sigtran/+/41310?usp=email )
Change subject: Add rate counters for loadshare-tcap
......................................................................
Patch Set 9:
(1 comment)
Patchset:
PS8:
> @laforge@gnumonks.org @osmith@sysmocom. […]
When generating the manuals it's also the matrix job where we also enable tcap, so they should show up there.
--
To view, visit https://gerrit.osmocom.org/c/libosmo-sigtran/+/41310?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: libosmo-sigtran
Gerrit-Branch: master
Gerrit-Change-Id: Id67704991feacf54e3123f76e9506dd323b2498b
Gerrit-Change-Number: 41310
Gerrit-PatchSet: 9
Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: daniel <dwillmann(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-CC: osmith <osmith(a)sysmocom.de>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Comment-Date: Mon, 10 Nov 2025 18:33:17 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: lynxis lazus <lynxis(a)fe80.eu>
Attention is currently required from: daniel, laforge, lynxis lazus.
pespin has posted comments on this change by lynxis lazus. ( https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309?usp=email )
Change subject: Add TCAP based loadsharing/routing
......................................................................
Patch Set 9: Code-Review-1
(11 comments)
Patchset:
PS8:
> @pespin: I like to keep most of the #ifdef / #endif out of the code. […]
I don't want to be looking at functions which turn to be noops 99% of the setups while reading at the code. And the amount of places where the tcap functionaltities need to be hooked is so small I don't see a problem with having some extra ifdefs in the few places where the calls are done.
that also helps by a simple grep ENABLE_TCAP figuring out all the places where tcap related features are hooked.
File examples/sccp_demo_user.c:
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/8ec02608_e29c8… :
PS8, Line 30: void *talloc_asn1_ctx;
> Will check it again, if it is still required. The asn1 library changed.
If it is required, do you mind explaining why? Doesn't seem obvious to me.
File src/ipa.c:
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/f08d589b_c5964… :
PS8, Line 316: ss7_asp_tcap_rx_sccp(as, asp, opc, dpc, msg);
> I want to keep the code changes to the other files minimal. […]
To start with, I'd prefix it with tcap_* tbh. I can also have a look whether this is the best place to lookup the content.
File src/ss7_as_loadshare_tcap.c:
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/02c34788_99b16… :
PS8, Line 138: ssn ^= ((pc >> 24) & 0xff);
> Wikipedia says it's 14 bits for ITU. […]
3+8+3=14 indeed, I counted wrong from the top of my head :D
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/349aace2_4a47a… :
PS8, Line 273: /** Traffic from the TCAP ASP -> AS -> osmo-stp, only used to update transaction tracking
> Yes it is. If TCAP is enabled on the ASP, it must track both, Rx and Tx.
Done
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/f5e0cd0c_b7bd1… :
PS8, Line 380: static int sent_back_utds(struct osmo_ss7_as *as,
> It sends back an SCCP/UTDS back to the origin
I need to investigate about this:
* The meanding of sending that UTDS thing I don't know about
* Whether ROUTE-FAIL.ind would be enough
* Whether the sending back up the stack would require some sort of async queue like ROUTE-FAIL.ind to avoid sending a primtiive to the user while it's busy sending the previous request primitive.
Also, some spec reference here would be nice.
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/a1dbbab8_4ca39… :
PS8, Line 487: /* decode SCCP and convert to a SUA/xUA representation */
> I don't really see the gain from move the code back into an own function with a lot of pointers. […]
Done
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/0b32957c_ff879… :
PS8, Line 560: sent_back_utds(as, xua, sua, SCCP_RETURN_CAUSE_SUBSYSTEM_FAILURE);
> An UTDS was requested. I don't know enough of SCCP. […]
I need to investigate about this:
* The meanding of sending that UTDS thing I don't know about
* Whether ROUTE-FAIL.ind would be enough
* Whether the sending back up the stack would require some sort of async queue like ROUTE-FAIL.ind to avoid sending a primtiive to the user while it's busy sending the previous request primitive.
Also, some spec reference here would be nice.
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/bff75e23_5ec77… :
PS8, Line 607: * @return 0 on success
> There is a difference between (rc = EPROTONOSUPPORT) and (rc = 0 && asp == NULL.) […]
afaiu this should only return the asp, no need to return an rc?
File src/ss7_asp.h:
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/9b30ad68_34e55… :
PS8, Line 96: bool enabled;
> Not all ASP of an AS has it enabled. […]
Does that make sense? why would somebody want to have TCAP routing enabled on some and not all of the ASPs serving an AS?
File src/ss7_asp.c:
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/04268b90_8a906… :
PS8, Line 1344: tcap_asp_down(asp);
> Where do you think it belongs exactly? I'm not used to this code base.
I can have a look.
--
To view, visit https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: libosmo-sigtran
Gerrit-Branch: master
Gerrit-Change-Id: Ibcb48aa0e515ad346f59ddd84b24c6e2c026144d
Gerrit-Change-Number: 41309
Gerrit-PatchSet: 9
Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: daniel <dwillmann(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: daniel <dwillmann(a)sysmocom.de>
Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Comment-Date: Mon, 10 Nov 2025 18:32:35 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Comment-In-Reply-To: lynxis lazus <lynxis(a)fe80.eu>
Attention is currently required from: lynxis lazus.
pespin has posted comments on this change by lynxis lazus. ( https://gerrit.osmocom.org/c/libosmo-sigtran/+/41308?usp=email )
Change subject: Add test for tcap decoding/encoding
......................................................................
Patch Set 7: Code-Review-2
(1 comment)
Patchset:
PS6:
> This test does not cover (nor require) any API from libosmo-sigtran. […]
I confirm my agreement with fixeria, this commit doesn't belong here and I vote against merging it.
--
To view, visit https://gerrit.osmocom.org/c/libosmo-sigtran/+/41308?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: libosmo-sigtran
Gerrit-Branch: master
Gerrit-Change-Id: I8a0dbfaaa7182a5a72b279908be09e3adab254a2
Gerrit-Change-Number: 41308
Gerrit-PatchSet: 7
Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: daniel <dwillmann(a)sysmocom.de>
Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Comment-Date: Mon, 10 Nov 2025 18:22:09 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Comment-In-Reply-To: lynxis lazus <lynxis(a)fe80.eu>
Attention is currently required from: lynxis lazus.
Hello Jenkins Builder, pespin,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41307?usp=email
to look at the new patch set (#5).
The following approvals got outdated and were removed:
Verified+1 by Jenkins Builder
Change subject: build-system: depend on libosmo-asn1-tcap
......................................................................
build-system: depend on libosmo-asn1-tcap
To support tcap based loadsharing, tcap must
be decoded.
Co-authored-by: Daniel Willmann <dwillmann(a)sysmocom.de>
Related: SYS#5423
Change-Id: Ib485f786217166635377f931ab894e43a0680634
---
M configure.ac
M contrib/jenkins.sh
M libosmo-sigtran.pc.in
M src/Makefile.am
4 files changed, 29 insertions(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/libosmo-sigtran refs/changes/07/41307/5
--
To view, visit https://gerrit.osmocom.org/c/libosmo-sigtran/+/41307?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: libosmo-sigtran
Gerrit-Branch: master
Gerrit-Change-Id: Ib485f786217166635377f931ab894e43a0680634
Gerrit-Change-Number: 41307
Gerrit-PatchSet: 5
Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: daniel <dwillmann(a)sysmocom.de>
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu>
Attention is currently required from: pespin.
lynxis lazus has posted comments on this change by lynxis lazus. ( https://gerrit.osmocom.org/c/libosmo-sigtran/+/41311?usp=email )
Change subject: Add VTY command to list TCAP ranges for an AS
......................................................................
Patch Set 8:
(3 comments)
File src/Makefile.am:
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41311/comment/f3f4af85_d7ade… :
PS8, Line 13: ss7_as_loadshare_tcap_vty.h \
> tcap_loadshare_vty.{c,h}? […]
No, I have static inline functions which no-ops, when the feature is not used. IMHO: this keeps the code cleaner, because it reduces the amount of #ifdef/#endif in the code.
File src/ss7_as_loadshare_tcap_vty.h:
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41311/comment/db119fe6_56cdf… :
PS8, Line 6: #ifdef WITH_TCAP_LOADSHARING
> Drop this, simply only include the header when ifdef BUILD_WITH_TCAP_LOADSHARING
No, I like to have static inlines instead if the feature isn't enabled.
File src/ss7_as_loadshare_tcap_vty.c:
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41311/comment/0f115d86_b02b5… :
PS8, Line 50: "show cs7 instance <0-15> as tcap-ranges name AS_NAME",
> are we using the same ordering in other vty command? looks weird ot have "as", then "tcap-ranges" an […]
@dwillmann@sysmocom.de?
--
To view, visit https://gerrit.osmocom.org/c/libosmo-sigtran/+/41311?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: libosmo-sigtran
Gerrit-Branch: master
Gerrit-Change-Id: I8026248d9897aadab5bf13a425269ec1e948dfdf
Gerrit-Change-Number: 41311
Gerrit-PatchSet: 8
Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: daniel <dwillmann(a)sysmocom.de>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 10 Nov 2025 17:32:44 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
lynxis lazus has posted comments on this change by lynxis lazus. ( https://gerrit.osmocom.org/c/libosmo-sigtran/+/41310?usp=email )
Change subject: Add rate counters for loadshare-tcap
......................................................................
Patch Set 8:
(1 comment)
Patchset:
PS8:
@laforge@gnumonks.org @osmith@sysmocom.de what is the right way to handle it? If we have no rate counters for the non-tcap builds, do we run into problems when generating the manuals?
--
To view, visit https://gerrit.osmocom.org/c/libosmo-sigtran/+/41310?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: libosmo-sigtran
Gerrit-Branch: master
Gerrit-Change-Id: Id67704991feacf54e3123f76e9506dd323b2498b
Gerrit-Change-Number: 41310
Gerrit-PatchSet: 8
Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: daniel <dwillmann(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-CC: osmith <osmith(a)sysmocom.de>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 10 Nov 2025 17:30:17 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Attention is currently required from: daniel, laforge, pespin.
lynxis lazus has posted comments on this change by lynxis lazus. ( https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309?usp=email )
Change subject: Add TCAP based loadsharing/routing
......................................................................
Patch Set 8:
(16 comments)
File src/ss7_as_loadshare_tcap.c:
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/4c39a77e_48ad4… :
PS8, Line 138: ssn ^= ((pc >> 24) & 0xff);
> A point code is 13 bits in ITU iirc, you seem to be dropping 5 bits here. […]
Wikipedia says it's 14 bits for ITU. I've reserved 24 bits here for the point code (even we don't do ANSI).
We don't drop any bits here. XOR the high 8 bits of PC with the SSN. In case this is a WILDCARD.
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/80b1e111_674e0… :
PS8, Line 273: /** Traffic from the TCAP ASP -> AS -> osmo-stp, only used to update transaction tracking
> I wonder whether this step is mandatory or should be enabled depending on setup?
Yes it is. If TCAP is enabled on the ASP, it must track both, Rx and Tx.
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/5f0d23f4_c6c54… :
PS8, Line 380: static int sent_back_utds(struct osmo_ss7_as *as,
> Please add a description for this function, I'm not getting what's its purpose.
It sends back an SCCP/UTDS back to the origin
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/90047b54_6af95… :
PS8, Line 487: /* decode SCCP and convert to a SUA/xUA representation */
> I think you have similar code logic in one of the above functions, you may want to see if it makes s […]
I don't really see the gain from move the code back into an own function with a lot of pointers. It complicates the code for a minimal gain of code de-duplication.
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/d94640e6_2c112… :
PS8, Line 560: sent_back_utds(as, xua, sua, SCCP_RETURN_CAUSE_SUBSYSTEM_FAILURE);
> You may want to look at whether it makes more sense to send a routing failure: […]
An UTDS was requested. I don't know enough of SCCP. But the feature request explicit requeseted an UTDS.
I don't know why we never sent back an UTDS before.
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/6e8e96e1_d79ae… :
PS8, Line 607: * @return 0 on success
> EPROTONOSUPPORT is not documented here. In case, I'd drop EPROTONOSUPPORT and return asp instead.
There is a difference between (rc = EPROTONOSUPPORT) and (rc = 0 && asp == NULL.)
PROTONOSUPPORTED will do a regular AS loadsharing.
While rc = 0; asp = NULL will drop the message. (Because an UTDS is already sent to the origin).
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/ed73b488_7cf0a… :
PS8, Line 921: /** Called when the ASP is going down or free'd
> Then you are currently calling it fromthe wrong place apparently.
Why?
File src/ss7_as_vty.c:
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/6244559b_27aaa… :
PS8, Line 39: #include "ss7_as_loadshare_tcap.h"
> #ifdef WITH_TCAP_LOADSHARING
No
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/bb387f15_ffbf2… :
PS8, Line 158: tcap_disable(as);
> #ifdef WITH_TCAP_LOADSHARING
No, not needed.
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/3f6f022b_d1a5b… :
PS8, Line 165: "traffic-mode (loadshare|loadshare-tcap) [bindings] [sls] [opc-sls] [opc-shift] [<0-2>]",
> IMHO loadshare-tcap feature should have a separate command to enable/disable it. […]
traffic-mode loadshare-tcap is an extension to the general loadshare.
@dwillmann@sysmocom.de @laforge@osmocom.org I took this over from your origin work.
Maybe you have an opinion on it.
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/3cf2e9b7_cd913… :
PS8, Line 186: vty_out(vty, "tcap loadsharing is not supported in this build.\n");
This is wrong, will fix it in v2
File src/ss7_asp.h:
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/08f4fd96_cfca5… :
PS8, Line 96: bool enabled;
> is this really needed? Does it make sense to have tcap loadsharing enabled in only some ASPs of the […]
Not all ASP of an AS has it enabled. Only when the IPA/TCAP is called, it is enabled for this particular ASP.
File src/ss7_asp.c:
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/c71f3567_91895… :
PS8, Line 1344: tcap_asp_down(asp);
> nooo way you are calling this here. […]
Where do you think it belongs exactly? I'm not used to this code base.
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/bbfce463_87102… :
PS8, Line 1435: /*! Received an unknown packet on asp
> Unrelated to this commit, please submit another one.
Will look into it.
File src/tcap_transaction_tracking.c:
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/9436428f_999a0… :
PS8, Line 122: LOGPASP(entry->asp, DLSS7, LOGL_DEBUG, "Creating tcap cache, entry (own) pc/ssn/tid %u/%u/%u -> %u/%u/%u\n",
> we always want to log PC in both numeric and configured format. See osmo_ss7_pointcode_print_buf().
Ack
File stp/stp_main.c:
https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309/comment/d28158a7_3d5de… :
PS8, Line 52: void *talloc_asn1_ctx;
> Why is this needed?
Need to check it again, if it is still required.
--
To view, visit https://gerrit.osmocom.org/c/libosmo-sigtran/+/41309?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: libosmo-sigtran
Gerrit-Branch: master
Gerrit-Change-Id: Ibcb48aa0e515ad346f59ddd84b24c6e2c026144d
Gerrit-Change-Number: 41309
Gerrit-PatchSet: 8
Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: daniel <dwillmann(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: daniel <dwillmann(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 10 Nov 2025 17:29:12 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Attention is currently required from: osmith.
fixeria has posted comments on this change by osmith. ( https://gerrit.osmocom.org/c/osmo-ci/+/41393?usp=email )
Change subject: OBS: sync_obs_projects: fix for OSC 1.12.1
......................................................................
Patch Set 1: Code-Review+1
(1 comment)
Patchset:
PS1:
What a weird behavior. Did you investigate why they suddenly require a git repository now?
--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/41393?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: I1236a065e2998fb46343df3968f7bb4dabeea55a
Gerrit-Change-Number: 41393
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 10 Nov 2025 17:14:57 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes