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

Build failure of network:osmocom:nightly/osmo-gbproxy in openSUSE_Leap_15.2/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-gbproxy failed to build in openSUSE_Leap_15.2/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-gbproxy Last lines of build log: [ 33s] checking whether to build static libraries... yes [ 33s] checking for pkg-config... /usr/bin/pkg-config [ 33s] checking for x86_64-suse-linux-gnu-pkg-config... /usr/bin/x86_64-suse-linux-gnu-pkg-config [ 33s] checking pkg-config is at least version 0.20... yes [ 33s] checking for library containing dlopen... -ldl [ 33s] checking for library containing dlsym... -ldl [ 33s] checking for libosmocore >= 1.6.0... no [ 33s] configure: error: Package requirements (libosmocore >= 1.6.0) were not met: [ 33s] [ 33s] Package 'libsctp', required by 'libosmocore', not found [ 33s] [ 33s] Consider adjusting the PKG_CONFIG_PATH environment variable if you [ 33s] installed software in a non-standard prefix. [ 33s] [ 33s] Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS [ 33s] and LIBOSMOCORE_LIBS to avoid the need to call pkg-config. [ 33s] See the pkg-config man page for more details. [ 33s] error: Bad exit status from /var/tmp/rpm-tmp.61lCiS (%build) [ 33s] [ 33s] [ 33s] RPM build errors: [ 33s] Bad exit status from /var/tmp/rpm-tmp.61lCiS (%build) [ 33s] ### VM INTERACTION START ### [ 34s] [ 28.779590] sysrq: Power Off [ 34s] [ 28.781053] reboot: Power down [ 34s] ### VM INTERACTION END ### [ 34s] [ 34s] sheep85 failed "build osmo-gbproxy.spec" at Fri Mar 25 00:36:36 UTC 2022. [ 34s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

3 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-ggsn in openSUSE_Leap_15.1/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-ggsn failed to build in openSUSE_Leap_15.1/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-ggsn Last lines of build log: [ 47s] checking for getopt_long... yes [ 47s] checking whether build environment is sane... yes [ 47s] checking for a thread-safe mkdir -p... /usr/bin/mkdir -p [ 47s] checking whether make sets $(MAKE)... yes [ 47s] checking for style of include used by make... GNU [ 47s] checking dependency style of gcc... none [ 47s] checking for libosmocore >= 1.5.0... no [ 47s] configure: error: Package requirements (libosmocore >= 1.5.0) were not met: [ 47s] [ 47s] Package 'libsctp', required by 'libosmocore', not found [ 47s] [ 47s] Consider adjusting the PKG_CONFIG_PATH environment variable if you [ 47s] installed software in a non-standard prefix. [ 47s] [ 47s] Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS [ 47s] and LIBOSMOCORE_LIBS to avoid the need to call pkg-config. [ 47s] See the pkg-config man page for more details. [ 47s] error: Bad exit status from /var/tmp/rpm-tmp.TV69dd (%build) [ 47s] [ 47s] [ 47s] RPM build errors: [ 47s] Bad exit status from /var/tmp/rpm-tmp.TV69dd (%build) [ 47s] ### VM INTERACTION START ### [ 49s] [ 43.026365] sysrq: SysRq : Power Off [ 49s] [ 43.029031] reboot: Power down [ 49s] ### VM INTERACTION END ### [ 49s] [ 49s] hci-cnode2-m0 failed "build osmo-ggsn.spec" at Fri Mar 25 00:35:54 UTC 2022. [ 49s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

3 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/libosmo-netif in openSUSE_Leap_15.2/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/l… Package network:osmocom:nightly/libosmo-netif failed to build in openSUSE_Leap_15.2/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-netif Last lines of build log: [ 48s] checking syslog.h presence... yes [ 48s] checking for syslog.h... yes [ 48s] checking ctype.h usability... yes [ 48s] checking ctype.h presence... yes [ 48s] checking for ctype.h... yes [ 48s] checking if gcc supports -fvisibility=hidden... yes [ 48s] checking for libosmocore >= 1.5.0... no [ 48s] configure: error: Package requirements (libosmocore >= 1.5.0) were not met: [ 48s] [ 48s] Package 'libsctp', required by 'libosmocore', not found [ 48s] [ 48s] Consider adjusting the PKG_CONFIG_PATH environment variable if you [ 48s] installed software in a non-standard prefix. [ 48s] [ 48s] Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS [ 48s] and LIBOSMOCORE_LIBS to avoid the need to call pkg-config. [ 48s] See the pkg-config man page for more details. [ 48s] error: Bad exit status from /var/tmp/rpm-tmp.Oqzv7r (%build) [ 48s] [ 48s] [ 48s] RPM build errors: [ 48s] Bad exit status from /var/tmp/rpm-tmp.Oqzv7r (%build) [ 48s] ### VM INTERACTION START ### [ 49s] [ 42.377260] sysrq: Power Off [ 49s] [ 42.379363] reboot: Power down [ 49s] ### VM INTERACTION END ### [ 49s] [ 49s] lamb59 failed "build libosmo-netif.spec" at Fri Mar 25 00:35:56 UTC 2022. [ 49s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

3 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/simtrace2 in openSUSE_Leap_15.1/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/s… Package network:osmocom:nightly/simtrace2 failed to build in openSUSE_Leap_15.1/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly simtrace2 Last lines of build log: [ 38s] checking whether to build shared libraries... yes [ 38s] checking whether to build static libraries... no [ 38s] checking for pkg-config... /usr/bin/pkg-config [ 38s] checking for x86_64-suse-linux-gnu-pkg-config... /usr/bin/x86_64-suse-linux-gnu-pkg-config [ 38s] checking pkg-config is at least version 0.20... yes [ 38s] checking if gcc supports -fvisibility=hidden... yes [ 38s] checking for libosmocore >= 1.4.0... no [ 38s] configure: error: Package requirements (libosmocore >= 1.4.0) were not met: [ 38s] [ 38s] Package 'libsctp', required by 'libosmocore', not found [ 38s] [ 38s] Consider adjusting the PKG_CONFIG_PATH environment variable if you [ 38s] installed software in a non-standard prefix. [ 38s] [ 38s] Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS [ 38s] and LIBOSMOCORE_LIBS to avoid the need to call pkg-config. [ 38s] See the pkg-config man page for more details. [ 38s] error: Bad exit status from /var/tmp/rpm-tmp.LN5TnV (%build) [ 38s] [ 38s] [ 38s] RPM build errors: [ 38s] Bad exit status from /var/tmp/rpm-tmp.LN5TnV (%build) [ 38s] ### VM INTERACTION START ### [ 39s] [ 33.277166] sysrq: SysRq : Power Off [ 39s] [ 33.279116] reboot: Power down [ 39s] ### VM INTERACTION END ### [ 39s] [ 39s] sheep86 failed "build simtrace2.spec" at Fri Mar 25 00:35:42 UTC 2022. [ 39s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

3 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/libosmo-netif in openSUSE_Leap_15.1/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/l… Package network:osmocom:nightly/libosmo-netif failed to build in openSUSE_Leap_15.1/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-netif Last lines of build log: [ 42s] checking syslog.h presence... yes [ 42s] checking for syslog.h... yes [ 42s] checking ctype.h usability... yes [ 42s] checking ctype.h presence... yes [ 42s] checking for ctype.h... yes [ 42s] checking if gcc supports -fvisibility=hidden... yes [ 42s] checking for libosmocore >= 1.5.0... no [ 42s] configure: error: Package requirements (libosmocore >= 1.5.0) were not met: [ 42s] [ 42s] Package 'libsctp', required by 'libosmocore', not found [ 42s] [ 42s] Consider adjusting the PKG_CONFIG_PATH environment variable if you [ 42s] installed software in a non-standard prefix. [ 42s] [ 42s] Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS [ 42s] and LIBOSMOCORE_LIBS to avoid the need to call pkg-config. [ 42s] See the pkg-config man page for more details. [ 42s] error: Bad exit status from /var/tmp/rpm-tmp.WB0ck8 (%build) [ 42s] [ 42s] [ 42s] RPM build errors: [ 42s] Bad exit status from /var/tmp/rpm-tmp.WB0ck8 (%build) [ 42s] ### VM INTERACTION START ### [ 43s] [ 36.305864] sysrq: SysRq : Power Off [ 43s] [ 36.308123] reboot: Power down [ 43s] ### VM INTERACTION END ### [ 43s] [ 43s] lamb18 failed "build libosmo-netif.spec" at Fri Mar 25 00:35:00 UTC 2022. [ 43s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

3 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-pcu in openSUSE_Leap_15.1/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-pcu failed to build in openSUSE_Leap_15.1/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-pcu Last lines of build log: [ 44s] checking dynamic linker characteristics... (cached) GNU/Linux ld.so [ 44s] checking how to hardcode library paths into programs... immediate [ 44s] checking for pkg-config... /usr/bin/pkg-config [ 44s] checking for x86_64-suse-linux-gnu-pkg-config... /usr/bin/x86_64-suse-linux-gnu-pkg-config [ 44s] checking pkg-config is at least version 0.20... yes [ 44s] checking for ANSI C header files... (cached) yes [ 44s] checking for libosmocore >= 1.6.0... no [ 44s] configure: error: Package requirements (libosmocore >= 1.6.0) were not met: [ 44s] [ 44s] Package 'libsctp', required by 'libosmocore', not found [ 44s] [ 44s] Consider adjusting the PKG_CONFIG_PATH environment variable if you [ 44s] installed software in a non-standard prefix. [ 44s] [ 44s] Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS [ 44s] and LIBOSMOCORE_LIBS to avoid the need to call pkg-config. [ 44s] See the pkg-config man page for more details. [ 45s] error: Bad exit status from /var/tmp/rpm-tmp.a2sD7q (%build) [ 45s] [ 45s] [ 45s] RPM build errors: [ 45s] Bad exit status from /var/tmp/rpm-tmp.a2sD7q (%build) [ 45s] ### VM INTERACTION START ### [ 45s] [ 38.922297] sysrq: SysRq : Power Off [ 45s] [ 38.926186] reboot: Power down [ 45s] ### VM INTERACTION END ### [ 45s] [ 45s] lamb27 failed "build osmo-pcu.spec" at Fri Mar 25 00:35:04 UTC 2022. [ 45s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

3 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-ggsn in openSUSE_Leap_15.2/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-ggsn failed to build in openSUSE_Leap_15.2/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-ggsn Last lines of build log: [ 50s] checking for getopt_long... yes [ 50s] checking whether build environment is sane... yes [ 50s] checking for a thread-safe mkdir -p... /usr/bin/mkdir -p [ 50s] checking whether make sets $(MAKE)... yes [ 50s] checking for style of include used by make... GNU [ 50s] checking dependency style of gcc... none [ 50s] checking for libosmocore >= 1.5.0... no [ 50s] configure: error: Package requirements (libosmocore >= 1.5.0) were not met: [ 50s] [ 50s] Package 'libsctp', required by 'libosmocore', not found [ 50s] [ 50s] Consider adjusting the PKG_CONFIG_PATH environment variable if you [ 50s] installed software in a non-standard prefix. [ 50s] [ 50s] Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS [ 50s] and LIBOSMOCORE_LIBS to avoid the need to call pkg-config. [ 50s] See the pkg-config man page for more details. [ 50s] error: Bad exit status from /var/tmp/rpm-tmp.SNWZRE (%build) [ 50s] [ 50s] [ 50s] RPM build errors: [ 50s] Bad exit status from /var/tmp/rpm-tmp.SNWZRE (%build) [ 50s] ### VM INTERACTION START ### [ 51s] [ 45.052674] sysrq: Power Off [ 51s] [ 45.055047] reboot: Power down [ 51s] ### VM INTERACTION END ### [ 51s] [ 51s] lamb05 failed "build osmo-ggsn.spec" at Fri Mar 25 00:35:08 UTC 2022. [ 51s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

3 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-sip-connector in openSUSE_Leap_15.2/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-sip-connector failed to build in openSUSE_Leap_15.2/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-sip-connector Last lines of build log: [ 42s] checking whether we are using the GNU C compiler... yes [ 42s] checking whether gcc accepts -g... yes [ 42s] checking for gcc option to accept ISO C89... none needed [ 42s] checking whether gcc understands -c and -o together... yes [ 42s] checking for style of include used by make... GNU [ 42s] checking dependency style of gcc... none [ 42s] checking for libosmocore >= 1.5.0... no [ 42s] configure: error: Package requirements (libosmocore >= 1.5.0) were not met: [ 42s] [ 42s] Package 'libsctp', required by 'libosmocore', not found [ 42s] [ 42s] Consider adjusting the PKG_CONFIG_PATH environment variable if you [ 42s] installed software in a non-standard prefix. [ 42s] [ 42s] Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS [ 42s] and LIBOSMOCORE_LIBS to avoid the need to call pkg-config. [ 42s] See the pkg-config man page for more details. [ 43s] error: Bad exit status from /var/tmp/rpm-tmp.c4l7Bn (%build) [ 43s] [ 43s] [ 43s] RPM build errors: [ 43s] Bad exit status from /var/tmp/rpm-tmp.c4l7Bn (%build) [ 43s] ### VM INTERACTION START ### [ 43s] [ 36.926093] sysrq: Power Off [ 43s] [ 36.931862] reboot: Power down [ 43s] ### VM INTERACTION END ### [ 43s] [ 43s] lamb58 failed "build osmo-sip-connector.spec" at Fri Mar 25 00:35:02 UTC 2022. [ 43s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

3 years, 3 months

1
0
0 0

Change in osmo-hlr[master]: Add vty `imsi unknown cause` to set the reject cause

by lynxis lazus

Attention is currently required from: fixeria, lynxis lazus. Hello Jenkins Builder, laforge, fixeria, I'd like you to reexamine a change. Please visit https://gerrit.osmocom.org/c/osmo-hlr/+/16808 to look at the new patch set (#6). Change subject: Add vty `imsi unknown cause` to set the reject cause ...................................................................... Add vty `imsi unknown cause` to set the reject cause Allow to set the reject cause when an IMSI is unknown to the HLR. Most common on reject causes are GMM_CAUSE_IMSI_UNKNOWN (2) or CAUSE_ROAMING_NOTALLOWED (11). Change-Id: Icea39020c23fbbea9e92847df76af8986fdbf48a --- M doc/examples/osmo-hlr.cfg M include/osmocom/hlr/hlr.h M src/hlr.c M src/hlr_vty.c M tests/test_nodes.vty 5 files changed, 42 insertions(+), 1 deletion(-) git pull ssh://gerrit.osmocom.org:29418/osmo-hlr refs/changes/08/16808/6 -- To view, visit https://gerrit.osmocom.org/c/osmo-hlr/+/16808 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-hlr Gerrit-Branch: master Gerrit-Change-Id: Icea39020c23fbbea9e92847df76af8986fdbf48a Gerrit-Change-Number: 16808 Gerrit-PatchSet: 6 Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: lynxis lazus <lynxis(a)fe80.eu> Gerrit-CC: pespin <pespin(a)sysmocom.de> Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu> Gerrit-MessageType: newpatchset

3 years, 3 months

1
0
0 0

Change in libosmocore[master]: gprs_ns2: add vty `nse <0-65535> restart sns`

by lynxis lazus

Attention is currently required from: laforge, daniel. lynxis lazus has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/23184 ) Change subject: gprs_ns2: add vty `nse <0-65535> restart sns` ...................................................................... Patch Set 2: (1 comment) File src/gb/gprs_ns2_vty.c: https://gerrit.osmocom.org/c/libosmocore/+/23184/comment/b8e55242_a2aa0020 PS1, Line 1920: gprs_ns2_free_nsvcs(nse); > I think this makes sense in both roles (BSS and SGSN) if it works like the side just restarted. […] Done -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/23184 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: Icb55d8449908d348ab10572eebcf971737fba00d Gerrit-Change-Number: 23184 Gerrit-PatchSet: 2 Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: daniel <dwillmann(a)sysmocom.de> Gerrit-CC: laforge <laforge(a)osmocom.org> Gerrit-CC: pespin <pespin(a)sysmocom.de> Gerrit-Attention: laforge <laforge(a)osmocom.org> Gerrit-Attention: daniel <dwillmann(a)sysmocom.de> Gerrit-Comment-Date: Thu, 24 Mar 2022 23:37:59 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: laforge <laforge(a)osmocom.org> Comment-In-Reply-To: daniel <dwillmann(a)sysmocom.de> Comment-In-Reply-To: lynxis lazus <lynxis(a)fe80.eu> Gerrit-MessageType: comment

3 years, 3 months

1
0
0 0

2025

2024

2023

2022

gerrit-log March 2022