This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Osmocom layer for OpenEmbedded". The branch, laforge/nightly has been updated discards bf43319200e2fe123a9d84fc7af8f3e84c6265f6 (commit) discards b58904accd730b8505320d62e0c198274b422d7f (commit) discards 7798207c8795d1337c9525f527b760dcfb7b8348 (commit) discards 5f424a919fd57caf5482e7d9da510a116febd2cd (commit) via d25f58b013fccb3c34219ca161dbb120173396f5 (commit) via 2415ab3b4191157aaef2de00491c3085e65c7326 (commit) via 53c9c389e4da9ed170995abaf35feabb62f8c4ea (commit) via 30916ff90e96b27e3ab84a8bb72769896ded4419 (commit) via 687b683bb80a4c368248491ac18ef5e439aa48af (commit) This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this: * -- * -- B -- O -- O -- O (bf43319200e2fe123a9d84fc7af8f3e84c6265f6) \ N -- N -- N (d25f58b013fccb3c34219ca161dbb120173396f5) When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B. Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/meta-telephony/commit/?id=d25f58b013fccb3c34219ca16… commit d25f58b013fccb3c34219ca161dbb120173396f5 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Wed Sep 6 12:09:52 2017 +0200 libosmo-abis: modify PV to match recent release The upstream release commit is 7f17b8c45d094941292036143f3292a1d5789cf5. This should fix current issue with 201705/nightly package feed: $ opkg upgrade Not selecting libosmo-abis 0.3.2+gitr0+d3292913ac as installing it would break existing dependencies. $ opkg list_installed | grep libosmo-abis libosmo-abis - 0.3.2+gitr2+d3292913ac-r2.18.1.0 See that gitr in repos is 0 while the previously installed one has gitr2, which is higher. Explanations I can find for this: - PR server was somehow reset? - the value in gitr is calculated based on offset from latest tag. As new release introduced new tag, gitr may have been reset. In any case, updating PV to have the correct value should fix this issue. Change-Id: I9f27661d9e5241efe7725b7d1efcf4aef55e2efe http://cgit.osmocom.org/meta-telephony/commit/?id=2415ab3b4191157aaef2de004… commit 2415ab3b4191157aaef2de00491c3085e65c7326 Author: Harald Welte <laforge(a)gnumonks.org> Date: Thu Aug 17 00:53:51 2017 +0200 update PV versions for libosmocore, libosmo-sccp and openggsn As we're building git master, we need to make sure PV is not lagging behind. I wish there was some OE magic by which it could discover PV from the source it builds. Change-Id: Ib45238e95156f215412d51d975b1acb33633a3e1 http://cgit.osmocom.org/meta-telephony/commit/?id=53c9c389e4da9ed170995abaf… commit 53c9c389e4da9ed170995abaf35feabb62f8c4ea Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Fri Jun 2 18:33:02 2017 +0800 libosmo-sccp: Attempt to fix link issue on 201705-nightly builds This project will build some static libraries needed for testing and also for downstream users. Do not disable the static build on newer Poky versions. arm-poky-linux-gnueabi-libtool: link: arm-poky-linux-gnueabi-gcc -march=armv5te -marm --sysroot=/home/jenkinsdebian8amd64/jenkins/workspace/201705-nightly/label/Debian8-AMD64/build/tmp/work/armv5te-poky-linux-gnueabi/libosmo-sccp/git-r1.18.1/recipe-sysroot -Wall -I/home/jenkinsdebian8amd64/jenkins/workspace/201705-nightly/label/Debian8-AMD64/build/tmp/work/armv5te-poky-linux-gnueabi/libosmo-sccp/git-r1.18.1/recipe-sysroot/usr/include/ -I/home/jenkinsdebian8amd64/jenkins/workspace/201705-nightly/label/Debian8-AMD64/build/tmp/work/armv5te-poky-linux-gnueabi/libosmo-sccp/git-r1.18.1/recipe-sysroot/usr/include/ -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/jenkinsdebian8amd64/jenkins/workspace/201705-nightly/label/Debian8-AMD64/build/tmp/work/armv5te-poky-linux-gnueabi/libosmo-sccp/git-r1.18.1=/usr/src/debug/libosmo-sccp/git-r1.18.1 -fdebug-prefix-map=/home/jenkinsdebian8amd64/jenkins/workspace/201705-nightly/label/Debian8-AMD64/build/tmp/work/armv5te-poky-linux-gnueabi/libosmo-sccp/git-r1.18.1/recipe-sysroot-native= -fdebug-prefix-map=/home/jenkinsdebian8amd64/jenkins/workspace/201705-nightly/label/Debian8-AMD64/build/tmp/work/armv5te-poky-linux-gnueabi/libosmo-sccp/git-r1.18.1/recipe-sysroot= -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -o xua_test xua_test.o sccp_test_data.o ../../src/.libs/libosmo-sigtran.so -losmogsm -ltalloc -losmovty -losmocore -losmonetif -lsctp | xua_test.o: In function `test_helpers': | /usr/src/debug/libosmo-sccp/git-r1.18.1/git/tests/xua/xua_test.c:160: undefined reference to `xua_part_add_gt' | /usr/src/debug/libosmo-sccp/git-r1.18.1/git/tests/xua/xua_test.c:168: undefined reference to `sua_parse_gt' | xua_test.o: In function `test_sccp2sua_case': Change-Id: I80eea9ac888ab4b13614ff475bebacb94b72b0f2 http://cgit.osmocom.org/meta-telephony/commit/?id=30916ff90e96b27e3ab84a8bb… commit 30916ff90e96b27e3ab84a8bb72769896ded4419 Author: Harald Welte <laforge(a)gnumonks.org> Date: Thu Jun 23 08:51:51 2016 +0200 set up osmocom recipes with AUTOREV to track git master This is for the upcoming nightly builds, where all our osmo* recipes are going to track current master of their respective upstream git repository. ----------------------------------------------------------------------- Summary of changes: recipes-misc/lksctp-tools/lksctp-tools_1.0.16.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- Osmocom layer for OpenEmbedded