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 via bf43319200e2fe123a9d84fc7af8f3e84c6265f6 (commit) from b58904accd730b8505320d62e0c198274b422d7f (commit) 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=bf43319200e2fe123a9d84fc7… commit bf43319200e2fe123a9d84fc7af8f3e84c6265f6 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 ----------------------------------------------------------------------- Summary of changes: recipes-osmocom/libosmo-abis/libosmo-abis_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- Osmocom layer for OpenEmbedded