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

Build failure of network:osmocom:nightly/libosmo-abis in Debian_11/i586

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/l… Package network:osmocom:nightly/libosmo-abis failed to build in Debian_11/i586 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-abis Last lines of build log: [ 124s] #define PACKAGE_STRING "libosmo-abis 1.2.0.5-2966" [ 124s] #define PACKAGE_BUGREPORT "openbsc(a)lists.osmocom.org" [ 124s] #define PACKAGE_URL "" [ 124s] #define PACKAGE "libosmo-abis" [ 124s] #define VERSION "1.2.0.5-2966" [ 124s] #define STDC_HEADERS 1 [ 124s] #define HAVE_SYS_TYPES_H 1 [ 124s] #define HAVE_SYS_STAT_H 1 [ 124s] #define HAVE_STDLIB_H 1 [ 124s] #define HAVE_STRING_H 1 [ 124s] #define HAVE_MEMORY_H 1 [ 124s] #define HAVE_STRINGS_H 1 [ 124s] #define HAVE_INTTYPES_H 1 [ 124s] #define HAVE_STDINT_H 1 [ 124s] #define HAVE_UNISTD_H 1 [ 124s] #define HAVE_DLFCN_H 1 [ 124s] #define LT_OBJDIR ".libs/" [ 124s] [ 124s] configure: exit 1 [ 124s] dh_auto_configure: error: ./configure --build=i686-linux-gnu --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=\${prefix}/lib/i386-linux-gnu --libexecdir=\${prefix}/lib/i386-linux-gnu --disable-maintainer-mode --disable-dependency-tracking returned exit code 1 [ 124s] make: *** [debian/rules:12: build] Error 25 [ 124s] dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 [ 124s] ### VM INTERACTION START ### [ 124s] [ 113.024648][ T1] sysrq: Power Off [ 124s] [ 113.027457][ T16] reboot: Power down [ 125s] ### VM INTERACTION END ### [ 125s] [ 125s] lamb13 failed "build libosmo-abis_1.2.0.5.2966.202203250026.dsc" at Fri Mar 25 00:39:18 UTC 2022. [ 125s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

2 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/libosmo-abis in Debian_10/i586

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/l… Package network:osmocom:nightly/libosmo-abis failed to build in Debian_10/i586 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-abis Last lines of build log: [ 120s] #define PACKAGE_STRING "libosmo-abis 1.2.0.5-2966" [ 120s] #define PACKAGE_BUGREPORT "openbsc(a)lists.osmocom.org" [ 120s] #define PACKAGE_URL "" [ 120s] #define PACKAGE "libosmo-abis" [ 120s] #define VERSION "1.2.0.5-2966" [ 120s] #define STDC_HEADERS 1 [ 120s] #define HAVE_SYS_TYPES_H 1 [ 120s] #define HAVE_SYS_STAT_H 1 [ 120s] #define HAVE_STDLIB_H 1 [ 120s] #define HAVE_STRING_H 1 [ 120s] #define HAVE_MEMORY_H 1 [ 120s] #define HAVE_STRINGS_H 1 [ 120s] #define HAVE_INTTYPES_H 1 [ 120s] #define HAVE_STDINT_H 1 [ 120s] #define HAVE_UNISTD_H 1 [ 120s] #define HAVE_DLFCN_H 1 [ 120s] #define LT_OBJDIR ".libs/" [ 120s] [ 120s] configure: exit 1 [ 120s] dh_auto_configure: ./configure --build=i686-linux-gnu --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=\${prefix}/lib/i386-linux-gnu --libexecdir=\${prefix}/lib/i386-linux-gnu --disable-maintainer-mode --disable-dependency-tracking returned exit code 1 [ 120s] make: *** [debian/rules:12: build] Error 2 [ 120s] dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 [ 120s] ### VM INTERACTION START ### [ 120s] [ 110.361064][ T1] sysrq: Power Off [ 120s] [ 110.363997][ T16] reboot: Power down [ 121s] ### VM INTERACTION END ### [ 121s] [ 121s] lamb25 failed "build libosmo-abis_1.2.0.5.2966.202203250026.dsc" at Fri Mar 25 00:39:16 UTC 2022. [ 121s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

2 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-pcap in Debian_10/i586

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-pcap failed to build in Debian_10/i586 Check out the package for editing: osc checkout network:osmocom:nightly osmo-pcap Last lines of build log: [ 132s] [ 132s] ## ----------- ## [ 132s] ## confdefs.h. ## [ 132s] ## ----------- ## [ 132s] [ 132s] /* confdefs.h */ [ 132s] #define PACKAGE_NAME "osmo-pcap" [ 132s] #define PACKAGE_TARNAME "osmo-pcap" [ 132s] #define PACKAGE_VERSION "0.3.0" [ 132s] #define PACKAGE_STRING "osmo-pcap 0.3.0" [ 132s] #define PACKAGE_BUGREPORT "openbsc-devel(a)lists.openbsc.org" [ 132s] #define PACKAGE_URL "" [ 132s] #define PACKAGE "osmo-pcap" [ 132s] #define VERSION "0.3.0" [ 132s] #define STDC_HEADERS 1 [ 132s] [ 132s] configure: exit 1 [ 132s] dh_auto_configure: ./configure --build=i686-linux-gnu --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=\${prefix}/lib/i386-linux-gnu --libexecdir=\${prefix}/lib/i386-linux-gnu --disable-maintainer-mode --disable-dependency-tracking --with-systemdsystemunitdir=/lib/systemd/system --with-pcap-config=/bin/false PCAP_CFLAGS=-I/usr/include PCAP_LIBS=-lpcap returned exit code 1 [ 132s] make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 2 [ 132s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 132s] make: *** [debian/rules:15: build] Error 2 [ 132s] dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 [ 132s] ### VM INTERACTION START ### [ 133s] [ 121.770704][ T1] sysrq: Power Off [ 133s] [ 121.773213][ T16] reboot: Power down [ 133s] ### VM INTERACTION END ### [ 133s] [ 133s] lamb06 failed "build osmo-pcap_0.3.0.202203250026.dsc" at Fri Mar 25 00:39:26 UTC 2022. [ 133s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

2 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-pcap in Debian_11/i586

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-pcap failed to build in Debian_11/i586 Check out the package for editing: osc checkout network:osmocom:nightly osmo-pcap Last lines of build log: [ 124s] [ 124s] ## ----------- ## [ 124s] ## confdefs.h. ## [ 124s] ## ----------- ## [ 124s] [ 124s] /* confdefs.h */ [ 124s] #define PACKAGE_NAME "osmo-pcap" [ 124s] #define PACKAGE_TARNAME "osmo-pcap" [ 124s] #define PACKAGE_VERSION "0.3.0" [ 124s] #define PACKAGE_STRING "osmo-pcap 0.3.0" [ 124s] #define PACKAGE_BUGREPORT "openbsc-devel(a)lists.openbsc.org" [ 124s] #define PACKAGE_URL "" [ 124s] #define PACKAGE "osmo-pcap" [ 124s] #define VERSION "0.3.0" [ 124s] #define STDC_HEADERS 1 [ 124s] [ 124s] configure: exit 1 [ 124s] dh_auto_configure: error: ./configure --build=i686-linux-gnu --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=\${prefix}/lib/i386-linux-gnu --libexecdir=\${prefix}/lib/i386-linux-gnu --disable-maintainer-mode --disable-dependency-tracking --with-systemdsystemunitdir=/lib/systemd/system --with-pcap-config=/bin/false PCAP_CFLAGS=-I/usr/include PCAP_LIBS=-lpcap returned exit code 1 [ 124s] make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 25 [ 124s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 124s] make: *** [debian/rules:15: build] Error 2 [ 124s] dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 [ 124s] ### VM INTERACTION START ### [ 124s] [ 112.767511][ T1] sysrq: Power Off [ 124s] [ 112.776684][ T16] reboot: Power down [ 125s] ### VM INTERACTION END ### [ 125s] [ 125s] lamb16 failed "build osmo-pcap_0.3.0.202203250026.dsc" at Fri Mar 25 00:39:19 UTC 2022. [ 125s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

2 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/libosmo-abis in xUbuntu_20.04/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/l… Package network:osmocom:nightly/libosmo-abis failed to build in xUbuntu_20.04/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-abis Last lines of build log: [ 131s] #define PACKAGE_STRING "libosmo-abis 1.2.0.5-2966" [ 131s] #define PACKAGE_BUGREPORT "openbsc(a)lists.osmocom.org" [ 131s] #define PACKAGE_URL "" [ 131s] #define PACKAGE "libosmo-abis" [ 131s] #define VERSION "1.2.0.5-2966" [ 131s] #define STDC_HEADERS 1 [ 131s] #define HAVE_SYS_TYPES_H 1 [ 131s] #define HAVE_SYS_STAT_H 1 [ 131s] #define HAVE_STDLIB_H 1 [ 131s] #define HAVE_STRING_H 1 [ 131s] #define HAVE_MEMORY_H 1 [ 131s] #define HAVE_STRINGS_H 1 [ 131s] #define HAVE_INTTYPES_H 1 [ 131s] #define HAVE_STDINT_H 1 [ 131s] #define HAVE_UNISTD_H 1 [ 131s] #define HAVE_DLFCN_H 1 [ 131s] #define LT_OBJDIR ".libs/" [ 131s] [ 131s] configure: exit 1 [ 131s] dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu --libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode --disable-dependency-tracking returned exit code 1 [ 131s] make: *** [debian/rules:12: build] Error 25 [ 131s] dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 [ 131s] ### VM INTERACTION START ### [ 131s] [ 121.040868][ T1] sysrq: Power Off [ 131s] [ 121.043560][ T16] reboot: Power down [ 131s] ### VM INTERACTION END ### [ 131s] [ 131s] lamb15 failed "build libosmo-abis_1.2.0.5.2966.202203250026.dsc" at Fri Mar 25 00:38:54 UTC 2022. [ 131s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

2 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-pcap in Debian_9.0/i586

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-pcap failed to build in Debian_9.0/i586 Check out the package for editing: osc checkout network:osmocom:nightly osmo-pcap Last lines of build log: [ 71s] ## confdefs.h. ## [ 71s] ## ----------- ## [ 71s] [ 71s] /* confdefs.h */ [ 71s] #define PACKAGE_NAME "osmo-pcap" [ 71s] #define PACKAGE_TARNAME "osmo-pcap" [ 71s] #define PACKAGE_VERSION "0.3.0" [ 71s] #define PACKAGE_STRING "osmo-pcap 0.3.0" [ 71s] #define PACKAGE_BUGREPORT "openbsc-devel(a)lists.openbsc.org" [ 71s] #define PACKAGE_URL "" [ 71s] #define PACKAGE "osmo-pcap" [ 71s] #define VERSION "0.3.0" [ 71s] #define STDC_HEADERS 1 [ 71s] [ 71s] configure: exit 1 [ 71s] dh_auto_configure: ./configure --build=i686-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=${prefix}/lib/i386-linux-gnu --libexecdir=${prefix}/lib/i386-linux-gnu --disable-maintainer-mode --disable-dependency-tracking --with-systemdsystemunitdir=/lib/systemd/system --with-pcap-config=/bin/false PCAP_CFLAGS=-I/usr/include PCAP_LIBS=-lpcap returned exit code 1 [ 71s] debian/rules:18: recipe for target 'override_dh_auto_configure' failed [ 71s] make[1]: *** [override_dh_auto_configure] Error 2 [ 71s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 71s] debian/rules:15: recipe for target 'build' failed [ 71s] make: *** [build] Error 2 [ 71s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 71s] ### VM INTERACTION START ### [ 71s] [ 61.767917][ T1] sysrq: Power Off [ 71s] [ 61.782891][ T16] reboot: Power down [ 71s] ### VM INTERACTION END ### [ 71s] [ 71s] lamb70 failed "build osmo-pcap_0.3.0.202203250026.dsc" at Fri Mar 25 00:38:15 UTC 2022. [ 71s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

2 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/libosmo-abis in xUbuntu_21.04/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/l… Package network:osmocom:nightly/libosmo-abis failed to build in xUbuntu_21.04/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-abis Last lines of build log: [ 120s] #define PACKAGE_STRING "libosmo-abis 1.2.0.5-2966" [ 120s] #define PACKAGE_BUGREPORT "openbsc(a)lists.osmocom.org" [ 120s] #define PACKAGE_URL "" [ 120s] #define PACKAGE "libosmo-abis" [ 120s] #define VERSION "1.2.0.5-2966" [ 120s] #define STDC_HEADERS 1 [ 120s] #define HAVE_SYS_TYPES_H 1 [ 120s] #define HAVE_SYS_STAT_H 1 [ 120s] #define HAVE_STDLIB_H 1 [ 120s] #define HAVE_STRING_H 1 [ 120s] #define HAVE_MEMORY_H 1 [ 120s] #define HAVE_STRINGS_H 1 [ 120s] #define HAVE_INTTYPES_H 1 [ 120s] #define HAVE_STDINT_H 1 [ 120s] #define HAVE_UNISTD_H 1 [ 120s] #define HAVE_DLFCN_H 1 [ 120s] #define LT_OBJDIR ".libs/" [ 120s] [ 120s] configure: exit 1 [ 120s] dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu --libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode --disable-dependency-tracking returned exit code 1 [ 120s] make: *** [debian/rules:12: build] Error 25 [ 120s] dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 [ 120s] ### VM INTERACTION START ### [ 121s] [ 108.855174][ T1] sysrq: Power Off [ 121s] [ 108.857894][ T16] reboot: Power down [ 121s] ### VM INTERACTION END ### [ 121s] [ 121s] lamb04 failed "build libosmo-abis_1.2.0.5.2966.202203250026.dsc" at Fri Mar 25 00:38:10 UTC 2022. [ 121s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

2 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/libosmo-abis in xUbuntu_20.10/x86_64

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/l… Package network:osmocom:nightly/libosmo-abis failed to build in xUbuntu_20.10/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-abis Last lines of build log: [ 129s] #define PACKAGE_STRING "libosmo-abis 1.2.0.5-2966" [ 129s] #define PACKAGE_BUGREPORT "openbsc(a)lists.osmocom.org" [ 129s] #define PACKAGE_URL "" [ 129s] #define PACKAGE "libosmo-abis" [ 129s] #define VERSION "1.2.0.5-2966" [ 129s] #define STDC_HEADERS 1 [ 129s] #define HAVE_SYS_TYPES_H 1 [ 129s] #define HAVE_SYS_STAT_H 1 [ 129s] #define HAVE_STDLIB_H 1 [ 129s] #define HAVE_STRING_H 1 [ 129s] #define HAVE_MEMORY_H 1 [ 129s] #define HAVE_STRINGS_H 1 [ 129s] #define HAVE_INTTYPES_H 1 [ 129s] #define HAVE_STDINT_H 1 [ 129s] #define HAVE_UNISTD_H 1 [ 129s] #define HAVE_DLFCN_H 1 [ 129s] #define LT_OBJDIR ".libs/" [ 129s] [ 129s] configure: exit 1 [ 129s] dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu --libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode --disable-dependency-tracking returned exit code 1 [ 129s] make: *** [debian/rules:12: build] Error 25 [ 129s] dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 [ 129s] ### VM INTERACTION START ### [ 129s] [ 118.534385][ T1] sysrq: Power Off [ 129s] [ 118.537914][ T16] reboot: Power down [ 130s] ### VM INTERACTION END ### [ 130s] [ 130s] lamb55 failed "build libosmo-abis_1.2.0.5.2966.202203250026.dsc" at Fri Mar 25 00:38:17 UTC 2022. [ 130s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

2 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-trx 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-trx failed to build in openSUSE_Leap_15.2/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-trx Last lines of build log: [ 45s] checking for byteswap.h... yes [ 46s] checking for an ANSI C-conforming const... yes [ 46s] checking for inline... inline [ 46s] checking for size_t... yes [ 46s] checking whether time.h and sys/time.h may both be included... yes [ 46s] checking whether byte ordering is bigendian... no [ 46s] checking for libosmocore >= 1.6.0... no [ 46s] configure: error: Package requirements (libosmocore >= 1.6.0) were not met: [ 46s] [ 46s] Package 'libsctp', required by 'libosmocore', not found [ 46s] [ 46s] Consider adjusting the PKG_CONFIG_PATH environment variable if you [ 46s] installed software in a non-standard prefix. [ 46s] [ 46s] Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS [ 46s] and LIBOSMOCORE_LIBS to avoid the need to call pkg-config. [ 46s] See the pkg-config man page for more details. [ 46s] error: Bad exit status from /var/tmp/rpm-tmp.7EpAf0 (%build) [ 46s] [ 46s] [ 46s] RPM build errors: [ 46s] Bad exit status from /var/tmp/rpm-tmp.7EpAf0 (%build) [ 46s] ### VM INTERACTION START ### [ 46s] [ 41.314820] sysrq: Power Off [ 46s] [ 41.317415] reboot: Power down [ 47s] ### VM INTERACTION END ### [ 47s] [ 47s] sheep86 failed "build osmo-trx.spec" at Fri Mar 25 00:37:48 UTC 2022. [ 47s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

2 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-trx 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-trx failed to build in openSUSE_Leap_15.1/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-trx Last lines of build log: [ 46s] checking for byteswap.h... yes [ 46s] checking for an ANSI C-conforming const... yes [ 46s] checking for inline... inline [ 46s] checking for size_t... yes [ 46s] checking whether time.h and sys/time.h may both be included... yes [ 46s] checking whether byte ordering is bigendian... no [ 46s] checking for libosmocore >= 1.6.0... no [ 46s] configure: error: Package requirements (libosmocore >= 1.6.0) were not met: [ 46s] [ 46s] Package 'libsctp', required by 'libosmocore', not found [ 46s] [ 46s] Consider adjusting the PKG_CONFIG_PATH environment variable if you [ 46s] installed software in a non-standard prefix. [ 46s] [ 46s] Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS [ 46s] and LIBOSMOCORE_LIBS to avoid the need to call pkg-config. [ 46s] See the pkg-config man page for more details. [ 46s] error: Bad exit status from /var/tmp/rpm-tmp.4OkmH8 (%build) [ 46s] [ 46s] [ 46s] RPM build errors: [ 46s] Bad exit status from /var/tmp/rpm-tmp.4OkmH8 (%build) [ 46s] ### VM INTERACTION START ### [ 47s] [ 41.322921] sysrq: SysRq : Power Off [ 47s] [ 41.325681] reboot: Power down [ 47s] ### VM INTERACTION END ### [ 47s] [ 47s] sheep88 failed "build osmo-trx.spec" at Fri Mar 25 00:37:29 UTC 2022. [ 47s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

2 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/libosmo-abis in Debian_9.0/i586

by OBS Notification

Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/l… Package network:osmocom:nightly/libosmo-abis failed to build in Debian_9.0/i586 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-abis Last lines of build log: [ 52s] #define PACKAGE_BUGREPORT "openbsc(a)lists.osmocom.org" [ 52s] #define PACKAGE_URL "" [ 52s] #define PACKAGE "libosmo-abis" [ 52s] #define VERSION "1.2.0.5-2966" [ 52s] #define STDC_HEADERS 1 [ 52s] #define HAVE_SYS_TYPES_H 1 [ 52s] #define HAVE_SYS_STAT_H 1 [ 52s] #define HAVE_STDLIB_H 1 [ 52s] #define HAVE_STRING_H 1 [ 52s] #define HAVE_MEMORY_H 1 [ 52s] #define HAVE_STRINGS_H 1 [ 52s] #define HAVE_INTTYPES_H 1 [ 52s] #define HAVE_STDINT_H 1 [ 52s] #define HAVE_UNISTD_H 1 [ 52s] #define HAVE_DLFCN_H 1 [ 52s] #define LT_OBJDIR ".libs/" [ 52s] [ 52s] configure: exit 1 [ 52s] dh_auto_configure: ./configure --build=i686-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=${prefix}/lib/i386-linux-gnu --libexecdir=${prefix}/lib/i386-linux-gnu --disable-maintainer-mode --disable-dependency-tracking returned exit code 1 [ 52s] debian/rules:12: recipe for target 'build' failed [ 52s] make: *** [build] Error 2 [ 52s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 52s] ### VM INTERACTION START ### [ 52s] [ 46.941606][ T1] sysrq: Power Off [ 52s] [ 46.943532][ T7] reboot: Power down [ 52s] ### VM INTERACTION END ### [ 52s] [ 52s] goat17 failed "build libosmo-abis_1.2.0.5.2966.202203250026.dsc" at Fri Mar 25 00:37:43 UTC 2022. [ 52s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

2 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-pcap 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-pcap failed to build in openSUSE_Leap_15.1/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-pcap Last lines of build log: [ 51s] checking how to run the C preprocessor... gcc -E [ 51s] checking for grep that handles long lines and -e... /usr/bin/grep [ 51s] checking for egrep... /usr/bin/grep -E [ 52s] checking for ANSI C header files... yes [ 52s] checking whether to enable VTY tests... no [ 52s] checking for pcap-config... /usr/bin/pcap-config [ 52s] checking for libosmocore >= 1.6.0... no [ 52s] configure: error: Package requirements (libosmocore >= 1.6.0) were not met: [ 52s] [ 52s] Package 'libsctp', required by 'libosmocore', not found [ 52s] [ 52s] Consider adjusting the PKG_CONFIG_PATH environment variable if you [ 52s] installed software in a non-standard prefix. [ 52s] [ 52s] Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS [ 52s] and LIBOSMOCORE_LIBS to avoid the need to call pkg-config. [ 52s] See the pkg-config man page for more details. [ 52s] error: Bad exit status from /var/tmp/rpm-tmp.psJVLY (%build) [ 52s] [ 52s] [ 52s] RPM build errors: [ 52s] Bad exit status from /var/tmp/rpm-tmp.psJVLY (%build) [ 52s] ### VM INTERACTION START ### [ 52s] [ 45.044352] sysrq: SysRq : Power Off [ 52s] [ 45.047810] reboot: Power down [ 52s] ### VM INTERACTION END ### [ 52s] [ 52s] old-atreju4 failed "build osmo-pcap.spec" at Fri Mar 25 00:37:35 UTC 2022. [ 52s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

2 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/simtrace2 in openSUSE_Leap_15.2/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.2/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly simtrace2 Last lines of build log: [ 47s] checking whether to build shared libraries... yes [ 47s] checking whether to build static libraries... no [ 47s] checking for pkg-config... /usr/bin/pkg-config [ 47s] checking for x86_64-suse-linux-gnu-pkg-config... /usr/bin/x86_64-suse-linux-gnu-pkg-config [ 47s] checking pkg-config is at least version 0.20... yes [ 47s] checking if gcc supports -fvisibility=hidden... yes [ 47s] checking for libosmocore >= 1.4.0... no [ 47s] configure: error: Package requirements (libosmocore >= 1.4.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.T4C0Ot (%build) [ 47s] [ 47s] [ 47s] RPM build errors: [ 47s] Bad exit status from /var/tmp/rpm-tmp.T4C0Ot (%build) [ 47s] ### VM INTERACTION START ### [ 48s] [ 41.597006] sysrq: Power Off [ 48s] [ 41.600047] reboot: Power down [ 48s] ### VM INTERACTION END ### [ 48s] [ 48s] lamb25 failed "build simtrace2.spec" at Fri Mar 25 00:37:32 UTC 2022. [ 48s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

2 years, 3 months

1
0
0 0

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

2 years, 3 months

1
0
0 0

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

2 years, 3 months

1
0
0 0

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

2 years, 3 months

1
0
0 0

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

2 years, 3 months

1
0
0 0

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

2 years, 3 months

1
0
0 0

Build failure of network:osmocom:nightly/osmo-pcap 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-pcap failed to build in openSUSE_Leap_15.2/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-pcap Last lines of build log: [ 31s] checking how to run the C preprocessor... gcc -E [ 31s] checking for grep that handles long lines and -e... /usr/bin/grep [ 31s] checking for egrep... /usr/bin/grep -E [ 31s] checking for ANSI C header files... yes [ 31s] checking whether to enable VTY tests... no [ 31s] checking for pcap-config... /usr/bin/pcap-config [ 31s] checking for libosmocore >= 1.6.0... no [ 31s] configure: error: Package requirements (libosmocore >= 1.6.0) were not met: [ 31s] [ 31s] Package 'libsctp', required by 'libosmocore', not found [ 31s] [ 31s] Consider adjusting the PKG_CONFIG_PATH environment variable if you [ 31s] installed software in a non-standard prefix. [ 31s] [ 31s] Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS [ 31s] and LIBOSMOCORE_LIBS to avoid the need to call pkg-config. [ 31s] See the pkg-config man page for more details. [ 31s] error: Bad exit status from /var/tmp/rpm-tmp.RvyFnY (%build) [ 31s] [ 31s] [ 31s] RPM build errors: [ 31s] Bad exit status from /var/tmp/rpm-tmp.RvyFnY (%build) [ 31s] ### VM INTERACTION START ### [ 32s] [ 26.127056] sysrq: Power Off [ 32s] [ 26.128572] reboot: Power down [ 32s] ### VM INTERACTION END ### [ 32s] [ 32s] sheep85 failed "build osmo-pcap.spec" at Fri Mar 25 00:36:35 UTC 2022. [ 32s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

2 years, 3 months

1
0
0 0

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/)

2 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/)

2 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/)

2 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/)

2 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/)

2 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/)

2 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/)

2 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/)

2 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

2 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

2 years, 3 months

1
0
0 0

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

by lynxis lazus

Hello Jenkins Builder, daniel, I'd like you to reexamine a change. Please visit https://gerrit.osmocom.org/c/libosmocore/+/23184 to look at the new patch set (#2). Change subject: gprs_ns2: add vty `nse <0-65535> restart sns` ...................................................................... gprs_ns2: add vty `nse <0-65535> restart sns` Allow to restart SNS procedure and initiate a SNS-SIZE procedure with Reset. SGSN side SNS restart will stop answer on ALIVE and is sending NS STATUS invalid protocol state. BSS side SNS restart will send a SNS Size procedure to reset the state. Change-Id: Icb55d8449908d348ab10572eebcf971737fba00d --- M src/gb/gprs_ns2_vty.c 1 file changed, 27 insertions(+), 0 deletions(-) git pull ssh://gerrit.osmocom.org:29418/libosmocore refs/changes/84/23184/2 -- 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-MessageType: newpatchset

2 years, 3 months

1
0
0 0

Change in osmo-ttcn3-hacks[master]: hlr: add imsi unknown cause test case

by lynxis lazus

lynxis lazus has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/27569 ) Change subject: hlr: add imsi unknown cause test case ...................................................................... Patch Set 1: (1 comment) Patchset: PS1: It would break all hlr latest test cases. Do we have a configuration which allows us to detect latest or master? -- To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/27569 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-ttcn3-hacks Gerrit-Branch: master Gerrit-Change-Id: I87c3a2d7304b81cfc11a364d933567e1a080b99a Gerrit-Change-Number: 27569 Gerrit-PatchSet: 1 Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Reviewer: Jenkins Builder Gerrit-Comment-Date: Thu, 24 Mar 2022 22:35:39 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

Change in osmo-ttcn3-hacks[master]: hlr: add imsi unknown cause test case

by lynxis lazus

lynxis lazus has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/27569 ) Change subject: hlr: add imsi unknown cause test case ...................................................................... hlr: add imsi unknown cause test case Depends-on: Icea39020c23fbbea9e92847df76af8986fdbf48a (osmo-hlr) Change-Id: I87c3a2d7304b81cfc11a364d933567e1a080b99a --- M hlr/HLR_Tests.ttcn 1 file changed, 16 insertions(+), 0 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/69/27569/1 diff --git a/hlr/HLR_Tests.ttcn b/hlr/HLR_Tests.ttcn index 959c680..2f8b498 100644 --- a/hlr/HLR_Tests.ttcn +++ b/hlr/HLR_Tests.ttcn @@ -152,6 +152,7 @@ f_vty_set_prompts(VTY); f_vty_transceive(VTY, "enable"); f_vty_config(VTY, "mslookup", "no mdns bind"); + f_vty_config(VTY, "hlr", "imsi unknown cause imsi-unknown"); } private altstep as_Tguard() runs on test_CT { @@ -978,6 +979,21 @@ vc_conn := f_start_handler(refers(f_TC_ul_unknown_imsi), pars); vc_conn.done; } + +private function f_TC_ul_unknown_imsi_roaming_not_allowed() runs on HLR_ConnHdlr { + f_perform_UL(g_pars.sub.imsi, ?, 13, source_name := g_pars.source_name); + setverdict(pass); +} +testcase TC_gsup_ul_unknown_imsi_roaming_not_allowed() runs on test_CT { + var hexstring imsi := f_rnd_imsi('26242'H); + var HLR_ConnHdlrPars pars := valueof(t_Pars(imsi)); + var HLR_ConnHdlr vc_conn; + + f_init(false); + vc_conn := f_start_handler(refers(f_TC_ul_unknown_imsi_roaming_not_allowed), pars); + vc_conn.done; +} + testcase TC_gsup_ul_unknown_imsi_via_proxy() runs on test_CT { var hexstring imsi := f_rnd_imsi('26242'H); var HLR_ConnHdlrPars pars := valueof(t_Pars_via_proxy(imsi)); -- To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/27569 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-ttcn3-hacks Gerrit-Branch: master Gerrit-Change-Id: I87c3a2d7304b81cfc11a364d933567e1a080b99a Gerrit-Change-Number: 27569 Gerrit-PatchSet: 1 Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu> Gerrit-MessageType: newchange

2 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. 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 (#5). 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, 43 insertions(+), 1 deletion(-) git pull ssh://gerrit.osmocom.org:29418/osmo-hlr refs/changes/08/16808/5 -- 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: 5 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-MessageType: newpatchset

2 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 has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-hlr/+/16808 ) Change subject: Add vty `imsi unknown cause` to set the reject cause ...................................................................... Patch Set 4: (6 comments) File src/hlr_vty.c: https://gerrit.osmocom.org/c/osmo-hlr/+/16808/comment/c241c228_2fe3afff PS2, Line 345: CAUSE > How about: […] Done File src/hlr_vty.c: https://gerrit.osmocom.org/c/osmo-hlr/+/16808/comment/348b11ef_113e1e30 PS4, Line 49: "roaming-not-allowed" }, > No need to break the line. Ack https://gerrit.osmocom.org/c/osmo-hlr/+/16808/comment/97ff33e6_eb8177ea PS4, Line 88: imsi_cause_code > Why not just g_hlr->imsi_unknown_cause != GMM_CAUSE_IMSI_UNKNOWN (it's the default). ok. That's the correct way to do with vty? Not writing out default values so we can change default later? https://gerrit.osmocom.org/c/osmo-hlr/+/16808/comment/26f1e06e_c91bebd0 PS4, Line 356: imsi unknown cause > You have to add help string for every singe word of the command. […] Ack https://gerrit.osmocom.org/c/osmo-hlr/+/16808/comment/9bd32036_89363c77 PS4, Line 357: GSUP cause > This is actually GSM 04.08 GMM cause if I understand correctly. Yes and not. We use GMM cause for this, even the request comes over CS and retranslate them back into MM cause. Should I use GSUP cause or should I say GSM 04.08 GMM? https://gerrit.osmocom.org/c/osmo-hlr/+/16808/comment/0bd0aecf_3efc07ab PS4, Line 365: Cannot find cause value to %s%s > This shall not happen because VTY would not accept any other values than 'imsi-unknown' and 'roaming […] Done -- 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: 4 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-Comment-Date: Thu, 24 Mar 2022 21:53:42 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

Change in osmo-ci[master]: RFC: lint: annotate lines in gerrit

by lynxis lazus

Attention is currently required from: osmith, laforge. lynxis lazus has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ci/+/26393 ) Change subject: RFC: lint: annotate lines in gerrit ...................................................................... Patch Set 1: (2 comments) Commit Message: https://gerrit.osmocom.org/c/osmo-ci/+/26393/comment/e7d3a471_109657ef PS1, Line 13: The jenkins nodes needs to access the gerrit via ssh > > I would expect one can createa gerrit user that has permission only to provide review and thereby […] We could execute this script from the review job, save the json in the workspace and execute the upload in a second job. How should we continue here? Patchset: PS1: @osmith: how should we continue here? -- To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/26393 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-ci Gerrit-Branch: master Gerrit-Change-Id: I1a48ddb976e0f53bfc0552d0be11e42ba68d9e49 Gerrit-Change-Number: 26393 Gerrit-PatchSet: 1 Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-Attention: osmith <osmith(a)sysmocom.de> Gerrit-Attention: laforge <laforge(a)osmocom.org> Gerrit-Comment-Date: Thu, 24 Mar 2022 21:43:27 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: osmith <osmith(a)sysmocom.de> Comment-In-Reply-To: laforge <laforge(a)osmocom.org> Comment-In-Reply-To: lynxis lazus <lynxis(a)fe80.eu> Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

Change in osmo-bsc[master]: stats: new trackers for lchan life duration

by neels

Attention is currently required from: iedemam, fixeria, pespin. neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/27081 ) Change subject: stats: new trackers for lchan life duration ...................................................................... Patch Set 18: (11 comments) Patchset: PS18: looks like we will merge this soon. Let's sort out these remaining issues: * milliseconds vs tenth seconds, various places marked (1): The time_cc updates the rate_ctr every tenth of a second now, which is nice, thumbs up. However, the naming and doc still suggest that the rate_ctrs are counting milliseconds. * reporting on vty the average activity duration, see the place marked (2) * reporting on vty how long a single active lchan has been active, marked (3) * minor style File include/osmocom/bsc/bts.h: https://gerrit.osmocom.org/c/osmo-bsc/+/27081/comment/bd885a57_1fdc10fe PS18, Line 61: BTS_CTR_CHAN_SDCCH_ACTIVE_MILLISECONDS_TOTAL, (1) File include/osmocom/bsc/gsm_data.h: https://gerrit.osmocom.org/c/osmo-bsc/+/27081/comment/e33c5ad2_cfe40ef9 PS18, Line 890: /* Interval timing to capture duration per activation and cummulative active time */ "cumulative" https://gerrit.osmocom.org/c/osmo-bsc/+/27081/comment/13a6d2ba_5633c0e8 PS18, Line 891: struct osmo_time_cc active_ms; (1) I think it was named active_ms due to my code review ... maybe just 'active' or 'active_cc' is better after all? sorry about that. File src/osmo-bsc/bts.c: https://gerrit.osmocom.org/c/osmo-bsc/+/27081/comment/038dc187_5ac51d5a PS18, Line 1038: "Cumulative number of milliseconds of SDCCH channel activity" }, (1) File src/osmo-bsc/bts_trx_vty.c: https://gerrit.osmocom.org/c/osmo-bsc/+/27081/comment/33b5979b_43ba30bf PS18, Line 576: VTY_NEWLINE); (3) Before, I gave code review to remove the osmo_time_cc_reset(), saying it was not necessary. Which is true, when thinking in terms of rate counters and stats; the normal / intended way to use osmo_time_cc is to always just carry on. I realize there is a "but" that I didn't see before: of course without a reset the total_sum accumulates across all activations of an lchan, and we cannot use it to report how long ago the currently active lchan has been activated. Sorry for not seeing that before. ways to resolve: one of a) drop this vty output and the gsm_lchan_active_duration_ms() function. Then it is fine to not do osmo_time_cc_reset(). b) use a separate simple timestamp to count a single lchan's active time, orthogonal to the osmo_time_cc that does the "magic" rate_ctr stuff. c) re-add the osmo_time_cc_reset() with a comment indicating "/* This reset allows showing on vty how long ago a single active lchan was activated. This reset does not affect rate_ctr statistics. */". The osmo_time_cc still works fine when it is reset at a time when the flag is false. I think either way it would be nicer to first do this patch about rate_ctr and averages only, and add the "activated x seconds ago" in a separate patch -- it is a separate feature. We can then discuss there whether that x should also be exposed to statistics somehow. File src/osmo-bsc/bts_vty.c: https://gerrit.osmocom.org/c/osmo-bsc/+/27081/comment/f2439f5e_3166fad9 PS18, Line 3844: vty_out(vty, "%s", VTY_NEWLINE); (2) the usefulness of this output is disputable because it averages over the entire lifetime of the cell. so if we have a month of normal operation followed by an hour of short-lived lchans, the avg lifespan reported here does not reflect reality in a useful way. We can instead (or in addition to above output?) use the rate in the last interval instead: in rate_ctr->intv, we keep values for the last second, minute, hour and day. For example: const struct rate_ctr *active_time_tch = rate_ctr_group_get_ctr(bts->bts_ctrs, BTS_CTR_CHAN_TCH_ACTIVE_TENTH_SECONDS); const struct rate_ctr *activations_tch = rate_ctr_group_get_ctr(bts->bts_ctrs, BTS_CTR_CHAN_ACT_TCH); vty_out(vty, "avg active duration in the last hour: TCH: %s", /* active_time_tch counts tenths of seconds, so *100 gives an avg in ms */ osmo_int_to_float_str_c(OTC_SELECT, 100 * active_time_tch->intv[RATE_CTR_INTV_HOUR].rate / activations_tch->[RATE_CTR_INTV_HOUR].rate, 3)); Same can be done per minute, per day, and per each lchan type, as you see fit... File src/osmo-bsc/lchan_fsm.c: https://gerrit.osmocom.org/c/osmo-bsc/+/27081/comment/6a9972bf_12de536a PS18, Line 208: struct rate_ctr *rate_ctr; osmocom style requires that this local variable be defined at the start of the scope, at line 203 above https://gerrit.osmocom.org/c/osmo-bsc/+/27081/comment/67698bca_fdd73598 PS18, Line 224: if (lchan->active_ms.cfg.rate_ctr) { (could just set the flag no matter if rate_ctr is set or not.) https://gerrit.osmocom.org/c/osmo-bsc/+/27081/comment/d3012b5b_7d4dbfe5 PS18, Line 546: .active_ms = lchan->active_ms please add a trailing comma. it allows future patches to add a single line, less merge-conflict prone https://gerrit.osmocom.org/c/osmo-bsc/+/27081/comment/5c2f549f_fb724a13 PS18, Line 556: if (lchan->active_ms.cfg.rate_ctr) { (could just set the flag no matter if rate_ctr is set or not.) -- To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/27081 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-bsc Gerrit-Branch: master Gerrit-Change-Id: I1b0670c47cb5e0b7776eda89d1e71545ba0e3347 Gerrit-Change-Number: 27081 Gerrit-PatchSet: 18 Gerrit-Owner: iedemam <michael(a)kapsulate.com> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de> Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-CC: pespin <pespin(a)sysmocom.de> Gerrit-Attention: iedemam <michael(a)kapsulate.com> Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Attention: pespin <pespin(a)sysmocom.de> Gerrit-Comment-Date: Thu, 24 Mar 2022 17:20:56 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

Change in libosmocore[master]: clean-up pkg-config files: Make use of "Requires" as documented

by pespin

pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/27521 ) Change subject: clean-up pkg-config files: Make use of "Requires" as documented ...................................................................... Patch Set 2: (1 comment) File libosmogb.pc.in: https://gerrit.osmocom.org/c/libosmocore/+/27521/comment/eabae010_9ca8f9d8 PS1, Line 9: Requires: libosmocore, libosmovty > Done libosmocore requiring talloc is totally orthogonal to having talloc listed here. libosmogb using talloc directly means it should show up here. IIRC in pkgconfig there's the concept of "internally using" some dep vs really exporting its linking flags to users of the lib. -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/27521 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: I2ab1fe8e4bbfc120b471d6c9f2312a89dbc7d42b Gerrit-Change-Number: 27521 Gerrit-PatchSet: 2 Gerrit-Owner: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Comment-Date: Thu, 24 Mar 2022 15:25:36 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: laforge <laforge(a)osmocom.org> Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

Change in osmo-bsc[master]: stats: new trackers for lchan life duration

by laforge

Attention is currently required from: iedemam, neels, fixeria, pespin. laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/27081 ) Change subject: stats: new trackers for lchan life duration ...................................................................... Patch Set 18: (1 comment) Patchset: PS15: > that patch is now merged, FYI @neels as you did a lot of the review / discussions here, I was hoping that you'd follow up "now" that iedemam has updated the path 7 days ago? Thanks! -- To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/27081 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-bsc Gerrit-Branch: master Gerrit-Change-Id: I1b0670c47cb5e0b7776eda89d1e71545ba0e3347 Gerrit-Change-Number: 27081 Gerrit-PatchSet: 18 Gerrit-Owner: iedemam <michael(a)kapsulate.com> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de> Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-CC: pespin <pespin(a)sysmocom.de> Gerrit-Attention: iedemam <michael(a)kapsulate.com> Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de> Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Attention: pespin <pespin(a)sysmocom.de> Gerrit-Comment-Date: Thu, 24 Mar 2022 15:16:57 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: neels <nhofmeyr(a)sysmocom.de> Comment-In-Reply-To: laforge <laforge(a)osmocom.org> Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

Change in osmo-e1-hardware[master]: Doc Update - Build process for DAHDI on Debian 11

by laforge

Attention is currently required from: nickvsnetworking. laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-e1-hardware/+/27014 ) Change subject: Doc Update - Build process for DAHDI on Debian 11 ...................................................................... Patch Set 1: (1 comment) Patchset: PS1: hi nick, would you mind incorporating the requested feedback so we can get this merged? thanks! -- To view, visit https://gerrit.osmocom.org/c/osmo-e1-hardware/+/27014 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-e1-hardware Gerrit-Branch: master Gerrit-Change-Id: I0679bd14702b7b3d05c3346ce10358f45fef0301 Gerrit-Change-Number: 27014 Gerrit-PatchSet: 1 Gerrit-Owner: nickvsnetworking <nick(a)nickvsnetworking.com> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Attention: nickvsnetworking <nick(a)nickvsnetworking.com> Gerrit-Comment-Date: Thu, 24 Mar 2022 14:59:47 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

Change in simtrace2[master]: firmware: bugfix: disable cardemu comms in local SIM mode

by James Tavares

James Tavares has uploaded this change for review. ( https://gerrit.osmocom.org/c/simtrace2/+/26865 ) Change subject: firmware: bugfix: disable cardemu comms in local SIM mode ...................................................................... firmware: bugfix: disable cardemu comms in local SIM mode This change prevents contention on the ISO7816 bus by disabling the card emulation state machine when the SIM switch is in the local mode. Without this change, the card emulation firmware can clobber ISO7816 communications and cause contention with certain (but not all) SIM cards. Changes: - Add 'enabled' flag to cardemu instance that is set/cleared by usb_command_sim_select() (the only place where sim switch occurs). - Flag is initialized as false (disabled) by default, to match local SIM mode default. - When card emulation is disabled, force SIM VCC to be "OFF", SIM RESET as "not in RESET", and drop bytes bytes received on the ISO7816 interface (but do service buffers). Change-Id: I4010f988712eac4a6af8568ccd60062f9de62449 --- M firmware/libcommon/source/mode_cardemu.c 1 file changed, 31 insertions(+), 13 deletions(-) git pull ssh://gerrit.osmocom.org:29418/simtrace2 refs/changes/65/26865/1 diff --git a/firmware/libcommon/source/mode_cardemu.c b/firmware/libcommon/source/mode_cardemu.c index 8e4acf9..00a062e 100644 --- a/firmware/libcommon/source/mode_cardemu.c +++ b/firmware/libcommon/source/mode_cardemu.c @@ -83,10 +83,21 @@ #ifdef DETECT_VCC_BY_ADC uint32_t vcc_uv; #endif + + /*! real-time state of VCC I/O line, irrespective of enabled flag */ bool vcc_active; + + /*! last VCC state we reported to the card emu state machine (conditioned by enabled flag) */ bool vcc_active_last; + + /*! real-time state of RST I/O line, irrespective of enabled flag */ bool rst_active; + + /*! last RST state we reported to the card emu state machine (conditioned by enabled flag) */ bool rst_active_last; + + /*! flag indicating whether this instance should perform card emulation, or not */ + bool enabled; }; struct cardem_inst cardem_inst[] = { @@ -505,19 +516,25 @@ #endif /* DETECT_VCC_BY_ADC */ -/* called from main loop; dispatches card I/O state changes to card_emu from main loop */ +/** + * called from main loop; dispatches card I/O state changes to card_emu from main loop. + * NOTE: conditions I/O state on the ci->enabled flag; if the instance is disabled, we assume VCC is + * disabled and the device is not in reset + */ static void process_io_statechg(struct cardem_inst *ci) { - if (ci->vcc_active != ci->vcc_active_last) { - card_emu_io_statechg(ci->ch, CARD_IO_VCC, ci->vcc_active); + const bool vcc_active = ci->vcc_active && ci->enabled; + if (vcc_active != ci->vcc_active_last) { + card_emu_io_statechg(ci->ch, CARD_IO_VCC, vcc_active); /* FIXME do this for real */ - card_emu_io_statechg(ci->ch, CARD_IO_CLK, ci->vcc_active); - ci->vcc_active_last = ci->vcc_active; + card_emu_io_statechg(ci->ch, CARD_IO_CLK, vcc_active); + ci->vcc_active_last = vcc_active; } - if (ci->rst_active != ci->rst_active_last) { - card_emu_io_statechg(ci->ch, CARD_IO_RST, ci->rst_active); - ci->rst_active_last = ci->rst_active; + const bool rst_active = ci->rst_active && ci->enabled; + if (rst_active != ci->rst_active_last) { + card_emu_io_statechg(ci->ch, CARD_IO_RST, rst_active); + ci->rst_active_last = rst_active; } } @@ -764,10 +781,8 @@ if (msgb_l2len(msg) < sizeof(*mss)) return -1; - if (mss->remote_sim) - sim_switch_use_physical(ci->num, 0); - else - sim_switch_use_physical(ci->num, 1); + ci->enabled = mss->remote_sim ? true : false; + sim_switch_use_physical(ci->num, !ci->enabled); return 0; } @@ -911,7 +926,10 @@ } uint8_t byte = rbuf_read(&ci->rb); __enable_irq(); - card_emu_process_rx_byte(ci->ch, byte); + + if (ci->enabled) { + card_emu_process_rx_byte(ci->ch, byte); + } //TRACE_ERROR("%uRx%02x\r\n", i, byte); } -- To view, visit https://gerrit.osmocom.org/c/simtrace2/+/26865 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: simtrace2 Gerrit-Branch: master Gerrit-Change-Id: I4010f988712eac4a6af8568ccd60062f9de62449 Gerrit-Change-Number: 26865 Gerrit-PatchSet: 1 Gerrit-Owner: James Tavares <jtavares(a)kvh.com> Gerrit-MessageType: newchange

2 years, 3 months

3
6
0 0

Change in libosmocore[master]: clean-up pkg-config files: Make use of "Requires" as documented

by laforge

laforge has submitted this change. ( https://gerrit.osmocom.org/c/libosmocore/+/27521 ) Change subject: clean-up pkg-config files: Make use of "Requires" as documented ...................................................................... clean-up pkg-config files: Make use of "Requires" as documented According to the pkg-config manual, "Libs" should not contain flags for _required_ packages. Instead, they should be expressed via "Requires". Let's do that Change-Id: I2ab1fe8e4bbfc120b471d6c9f2312a89dbc7d42b --- M libosmocodec.pc.in M libosmocoding.pc.in M libosmocore.pc.in M libosmoctrl.pc.in M libosmogb.pc.in M libosmogsm.pc.in M libosmosim.pc.in M libosmousb.pc.in M libosmovty.pc.in 9 files changed, 22 insertions(+), 21 deletions(-) Approvals: laforge: Looks good to me, approved pespin: Looks good to me, but someone else must approve Jenkins Builder: Verified diff --git a/libosmocodec.pc.in b/libosmocodec.pc.in index 9e058ef..0c4de8d 100644 --- a/libosmocodec.pc.in +++ b/libosmocodec.pc.in @@ -6,6 +6,6 @@ Name: Osmocom Codec related utilities Library Description: C Utility Library Version: @VERSION@ -Libs: -L${libdir} @TALLOC_LIBS@ -losmocodec -Cflags: -I${includedir}/ @TALLOC_CFLAGS@ - +Requires: talloc, libosmocore +Libs: -L${libdir} -losmocodec +Cflags: -I${includedir}/ diff --git a/libosmocoding.pc.in b/libosmocoding.pc.in index d1d03c4..5b91a60 100644 --- a/libosmocoding.pc.in +++ b/libosmocoding.pc.in @@ -6,6 +6,6 @@ Name: Osmocom L1 transcoding Library Description: C Utility Library Version: @VERSION@ -Libs: -L${libdir} @TALLOC_LIBS@ -losmocoding -losmocodec -losmogsm -losmocore -Cflags: -I${includedir}/ @TALLOC_CFLAGS@ - +Requires: talloc, libosmocore, libosmogsm, libosmocodec +Libs: -L${libdir} -losmocoding +Cflags: -I${includedir}/ diff --git a/libosmocore.pc.in b/libosmocore.pc.in index 80f17c8..3bb9b9a 100644 --- a/libosmocore.pc.in +++ b/libosmocore.pc.in @@ -6,6 +6,7 @@ Name: Osmocom Core Library Description: C Utility Library Version: @VERSION@ -Libs: -L${libdir} @TALLOC_LIBS@ -losmocore -Libs.private: @PTHREAD_LIBS@ @LIBSCTP_LIBS@ -Cflags: -I${includedir}/ @TALLOC_CFLAGS@ @PTHREAD_CFLAGS@ +Requires: talloc, libsctp +Libs: -L${libdir} -losmocore +Libs.private: @PTHREAD_LIBS@ +Cflags: -I${includedir}/ @PTHREAD_CFLAGS@ diff --git a/libosmoctrl.pc.in b/libosmoctrl.pc.in index 4676b31..e9947dc 100644 --- a/libosmoctrl.pc.in +++ b/libosmoctrl.pc.in @@ -6,6 +6,6 @@ Name: Osmocom Control Interface Library Description: C Utility Library Version: @VERSION@ -Libs: -L${libdir} @TALLOC_LIBS@ -losmoctrl -losmogsm -losmocore +Requires: talloc, libosmocore, libosmogsm +Libs: -L${libdir} -losmoctrl Cflags: -I${includedir}/ - diff --git a/libosmogb.pc.in b/libosmogb.pc.in index a163cc4..d545ce2 100644 --- a/libosmogb.pc.in +++ b/libosmogb.pc.in @@ -6,6 +6,6 @@ Name: Osmocom GPRS Gb Library Description: Osmocom GPRS Gb Interface (NS/BSSGP) Library Version: @VERSION@ -Libs: -L${libdir} @TALLOC_LIBS@ -losmogb -losmovty -losmocore +Requires: libosmocore, libosmovty +Libs: -L${libdir} -losmogb Cflags: -I${includedir}/ -fno-strict-aliasing - diff --git a/libosmogsm.pc.in b/libosmogsm.pc.in index 0160be8..0aaf51e 100644 --- a/libosmogsm.pc.in +++ b/libosmogsm.pc.in @@ -6,6 +6,6 @@ Name: Osmocom GSM Core Library Description: GSM Core Library Version: @VERSION@ -Libs: -L${libdir} @TALLOC_LIBS@ -losmogsm -losmocore +Requires: talloc, libosmocore +Libs: -L${libdir} -losmogsm Cflags: -I${includedir}/ - diff --git a/libosmosim.pc.in b/libosmosim.pc.in index 83777c3..a8f50d6 100644 --- a/libosmosim.pc.in +++ b/libosmosim.pc.in @@ -6,6 +6,6 @@ Name: Osmocom SIM card related utilities Library Description: C Utility Library Version: @VERSION@ -Libs: -L${libdir} @TALLOC_LIBS@ -losmosim -losmocore +Requires: talloc, libosmocore +Libs: -L${libdir} -losmosim Cflags: -I${includedir}/ - diff --git a/libosmousb.pc.in b/libosmousb.pc.in index ce6d271..dbedb0e 100644 --- a/libosmousb.pc.in +++ b/libosmousb.pc.in @@ -6,6 +6,6 @@ Name: Osmocom libusb (USB) integration Description: C Utility Library Version: @VERSION@ -Libs: -L${libdir} @TALLOC_LIBS@ -losmousb -losmocore +Requires: talloc, libusb-1.0, libosmocore +Libs: -L${libdir} -losmousb Cflags: -I${includedir}/ - diff --git a/libosmovty.pc.in b/libosmovty.pc.in index 6204e45..9a907e0 100644 --- a/libosmovty.pc.in +++ b/libosmovty.pc.in @@ -6,6 +6,6 @@ Name: Osmocom VTY Interface Library Description: C Utility Library Version: @VERSION@ -Libs: -L${libdir} @TALLOC_LIBS@ -losmovty -losmocore +Requires: libosmocore +Libs: -L${libdir} -losmovty Cflags: -I${includedir}/ - -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/27521 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: I2ab1fe8e4bbfc120b471d6c9f2312a89dbc7d42b Gerrit-Change-Number: 27521 Gerrit-PatchSet: 2 Gerrit-Owner: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-MessageType: merged

2 years, 3 months

1
0
0 0

Change in libosmocore[master]: clean-up pkg-config files: Make use of "Requires" as documented

by laforge

Attention is currently required from: fixeria. laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/27521 ) Change subject: clean-up pkg-config files: Make use of "Requires" as documented ...................................................................... Patch Set 1: Code-Review+2 (2 comments) File libosmogb.pc.in: https://gerrit.osmocom.org/c/libosmocore/+/27521/comment/f7a491b3_1913325f PS1, Line 9: Requires: libosmocore, libosmovty > libosmocore 'requires' talloc, so no need to specify it here again. […] Done File libosmovty.pc.in: https://gerrit.osmocom.org/c/libosmocore/+/27521/comment/6f33dce5_0be38113 PS1, Line 9: Requires: libosmocore > talloc is missing here. Done -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/27521 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: I2ab1fe8e4bbfc120b471d6c9f2312a89dbc7d42b Gerrit-Change-Number: 27521 Gerrit-PatchSet: 1 Gerrit-Owner: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Comment-Date: Thu, 24 Mar 2022 14:57:20 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: Yes Comment-In-Reply-To: laforge <laforge(a)osmocom.org> Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

Change in libosmocore[master]: clean-up pkg-config files: Make use of "Requires" as documented

by laforge

Attention is currently required from: fixeria. laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/27521 ) Change subject: clean-up pkg-config files: Make use of "Requires" as documented ...................................................................... Patch Set 1: (1 comment) File libosmogb.pc.in: https://gerrit.osmocom.org/c/libosmocore/+/27521/comment/262bfb9a_2011a6c4 PS1, Line 9: Requires: libosmocore, libosmovty > talloc is missing here. libosmocore 'requires' talloc, so no need to specify it here again. pkg-config does this recursively. -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/27521 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: I2ab1fe8e4bbfc120b471d6c9f2312a89dbc7d42b Gerrit-Change-Number: 27521 Gerrit-PatchSet: 1 Gerrit-Owner: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Comment-Date: Thu, 24 Mar 2022 14:56:56 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

Change in osmo-upf[master]: libosmo-pfcp: implement/generate TLV and IE value coding

by laforge

Attention is currently required from: neels. laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-upf/+/27222 ) Change subject: libosmo-pfcp: implement/generate TLV and IE value coding ...................................................................... Patch Set 11: Code-Review+1 -- To view, visit https://gerrit.osmocom.org/c/osmo-upf/+/27222 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-upf Gerrit-Branch: master Gerrit-Change-Id: I3069045b2d42dac88d955c636230adc64a7a4aa7 Gerrit-Change-Number: 27222 Gerrit-PatchSet: 11 Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de> Gerrit-Comment-Date: Thu, 24 Mar 2022 14:55:42 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

Change in osmo-upf[master]: libosmo-pfcp: add pfcp_proto.h pfcp_strs.h

by laforge

Attention is currently required from: neels, pespin. laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-upf/+/27221 ) Change subject: libosmo-pfcp: add pfcp_proto.h pfcp_strs.h ...................................................................... Patch Set 7: Code-Review+1 -- To view, visit https://gerrit.osmocom.org/c/osmo-upf/+/27221 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-upf Gerrit-Branch: master Gerrit-Change-Id: I568b821e89007ed52eeefcdbcb6edd8052a8b5be Gerrit-Change-Number: 27221 Gerrit-PatchSet: 7 Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de> Gerrit-Attention: pespin <pespin(a)sysmocom.de> Gerrit-Comment-Date: Thu, 24 Mar 2022 14:54:42 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

Change in osmo-upf[master]: libosmo-gtlv: add TLIV capability

by laforge

Attention is currently required from: neels. laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-upf/+/27529 ) Change subject: libosmo-gtlv: add TLIV capability ...................................................................... Patch Set 6: Code-Review+1 -- To view, visit https://gerrit.osmocom.org/c/osmo-upf/+/27529 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-upf Gerrit-Branch: master Gerrit-Change-Id: I0a076e54dfba6038cc779cb7c8f3967d212226aa Gerrit-Change-Number: 27529 Gerrit-PatchSet: 6 Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de> Gerrit-Comment-Date: Thu, 24 Mar 2022 14:53:54 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

Change in osmo-upf[master]: libosmo-gtlv: add C code generator for IE structs and arrays

by laforge

Attention is currently required from: neels. laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-upf/+/27219 ) Change subject: libosmo-gtlv: add C code generator for IE structs and arrays ...................................................................... Patch Set 6: Code-Review+1 -- To view, visit https://gerrit.osmocom.org/c/osmo-upf/+/27219 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-upf Gerrit-Branch: master Gerrit-Change-Id: Ifb3ea54d2797ce060b95834aa117725ec2d6c4cf Gerrit-Change-Number: 27219 Gerrit-PatchSet: 6 Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de> Gerrit-Comment-Date: Thu, 24 Mar 2022 14:53:09 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

Change in osmo-upf[master]: libosmo-gtlv: add generic TLV de- and encoder

by laforge

Attention is currently required from: neels. laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-upf/+/27217 ) Change subject: libosmo-gtlv: add generic TLV de- and encoder ...................................................................... Patch Set 4: Code-Review+1 (1 comment) Patchset: PS4: I would put it straight into the libosmocore repo, avoiding the need to change stuff later on, but it's up to you. -- To view, visit https://gerrit.osmocom.org/c/osmo-upf/+/27217 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-upf Gerrit-Branch: master Gerrit-Change-Id: Ib0fd00d9f288ffe13b7e67701f3e47073587404a Gerrit-Change-Number: 27217 Gerrit-PatchSet: 4 Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-CC: pespin <pespin(a)sysmocom.de> Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de> Gerrit-Comment-Date: Thu, 24 Mar 2022 14:51:22 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: Yes Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

Change in osmo-ggsn[master]: pco.h: Fix typo in reference to spec

by laforge

laforge has submitted this change. ( https://gerrit.osmocom.org/c/osmo-ggsn/+/27568 ) Change subject: pco.h: Fix typo in reference to spec ...................................................................... pco.h: Fix typo in reference to spec Change-Id: Ic428892161123b62d25a7619128ef7325bf85500 --- M ggsn/pco.h 1 file changed, 1 insertion(+), 1 deletion(-) Approvals: Jenkins Builder: Verified fixeria: Looks good to me, but someone else must approve laforge: Looks good to me, approved diff --git a/ggsn/pco.h b/ggsn/pco.h index 7ebe05a..4d999ef 100644 --- a/ggsn/pco.h +++ b/ggsn/pco.h @@ -4,7 +4,7 @@ #include "../gtp/pdp.h" -/* 3GPP TS 24.008 10.6.5.3 */ +/* 3GPP TS 24.008 10.5.6.3 */ enum pco_protocols { PCO_P_LCP = 0xC021, PCO_P_PAP = 0xC023, -- To view, visit https://gerrit.osmocom.org/c/osmo-ggsn/+/27568 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-ggsn Gerrit-Branch: master Gerrit-Change-Id: Ic428892161123b62d25a7619128ef7325bf85500 Gerrit-Change-Number: 27568 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-MessageType: merged

2 years, 3 months

1
0
0 0

Change in osmo-ggsn[master]: pco.h: Fix typo in reference to spec

by laforge

Attention is currently required from: pespin. laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ggsn/+/27568 ) Change subject: pco.h: Fix typo in reference to spec ...................................................................... Patch Set 1: Code-Review+2 -- To view, visit https://gerrit.osmocom.org/c/osmo-ggsn/+/27568 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-ggsn Gerrit-Branch: master Gerrit-Change-Id: Ic428892161123b62d25a7619128ef7325bf85500 Gerrit-Change-Number: 27568 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Attention: pespin <pespin(a)sysmocom.de> Gerrit-Comment-Date: Thu, 24 Mar 2022 14:46:48 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment

2 years, 3 months

1
0
0 0

2024

2023

2022

gerrit-log March 2022