tree 4674275b5c09b56e3dbbd06c3432eccd6d6d56cd
parent 5baaf5e976c9a28d0a5449586189e985c2e17165
author Pau Espin Pedrol <pespin@sysmocom.de> 1504692592 +0200
committer Pau Espin Pedrol <pespin@sysmocom.de> 1506684142 +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