Support #2834
closed
2018-01: we should update the 'latest' feeds
Added by neels about 6 years ago.
Updated almost 6 years ago.
Description
Recently, I recommended someone to use the latest feeds, and that then ran into numerous config problems since the config described by Osmocom Network In The Box only works on nightly. In the end we built from source.
Also:
On Tue, Jan 16, 2018 at 11:12:20AM -0200, Rafael Diniz wrote:
Hi all,
_
Anyone experiencing this error in Latest packages (Debian 9):
"The following packages have unmet dependencies:
osmo-mgw : Depends: libosmo-mgcp0 but it is not installable"
- Status changed from New to Feedback
- Assignee set to laforge
laforge, can you decide how important that is and assign to someone or reject?
- Assignee changed from laforge to pespin
the osmo-mgw debian package is broken, it depends on libosmo-mgcp0 which is not satisfied. On master, this is fixed by not installing libosmo-mgcp at all but keeping it as a local lib. One more reason to update latest.
I've seen the same issue reported when using the binaries for deb and xUbuntu, x64 and ARM.
is this resolved if i build from sources or the same occurs there?
I've just pushed a "1.2.1" patch release that should fix "latest", but we have to
wait for the re-builds to happen until the binary packages are updated/fixed.
On Thu, Apr 12, 2018 at 09:40:02PM +0000, gassman [REDMINE] wrote:
I've seen the same issue reported when using the binaries for deb and xUbuntu, x64 and ARM.
with "latest"? yes, that is irrespective of the architecture.
is this resolved if i build from sources or the same occurs there?
it would not happen from source, and also not with the "nightly" builds.
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
latest feeds have been updated, we can close this issue.
Also available in: Atom
PDF
