https://osmocom.org/https://osmocom.org/favicon.ico?16647414092017-09-04T16:03:24ZOpen Source Mobile CommunicationsCellular Network Infrastructure - Bug #2481: osmo-bts with broken dependency in latest nightly https://osmocom.org/issues/2481?journal_id=53022017-09-04T16:03:24Zmsuraev
<ul><li><strong>Subject</strong> changed from <i>osmo-bsc with broken dependency in latest nightly </i> to <i>osmo-bts with broken dependency in latest nightly </i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>Fixed in latest nightly.</p> Cellular Network Infrastructure - Bug #2481: osmo-bts with broken dependency in latest nightly https://osmocom.org/issues/2481?journal_id=53122017-09-05T18:59:14Zzecke
<ul></ul><p>That indicates a packaging issue.. wasn't there a libosmotrau1 package? If not we need to split some lib* packages properly.</p> Cellular Network Infrastructure - Bug #2481: osmo-bts with broken dependency in latest nightly https://osmocom.org/issues/2481?journal_id=57192017-10-11T02:51:56Zlaforge
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>New</i></li><li><strong>Assignee</strong> set to <i>msuraev</i></li></ul> Cellular Network Infrastructure - Bug #2481: osmo-bts with broken dependency in latest nightly https://osmocom.org/issues/2481?journal_id=58332017-10-16T13:10:06Zmsuraev
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>Indeed, there's no such package:<br /><pre>
opkg list |grep libosmotrau
</pre><br />comes up empty on latest nightly. Not sure how further split would have helped with PV variables though.</p> Cellular Network Infrastructure - Bug #2481: osmo-bts with broken dependency in latest nightly https://osmocom.org/issues/2481?journal_id=65132017-12-03T11:16:22Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>msuraev</i> to <i>zecke</i></li></ul><p>msuraev wrote:</p>
<blockquote>
<p>Indeed, there's no such package:<br />[...]<br />comes up empty on latest nightly. Not sure how further split would have helped with PV variables though.</p>
</blockquote>
<p><a class="user active" href="https://osmocom.org/users/5">zecke</a>: Can you please sched some light on this? Would having a separate libosmotrau package have solved/avoided this problem?</p> Cellular Network Infrastructure - Bug #2481: osmo-bts with broken dependency in latest nightly https://osmocom.org/issues/2481?journal_id=65142017-12-03T11:26:31Zzecke
<ul></ul><blockquote>
<p>On 3. Dec 2017, at 11:16, laforge [REDMINE] <<a class="email" href="mailto:redmine@lists.osmocom.org">redmine@lists.osmocom.org</a>> wrote:</p>
<p>Issue <a class="issue tracker-1 status-5 priority-2 priority-default closed" title="Bug: osmo-bts with broken dependency in latest nightly (Closed)" href="https://osmocom.org/issues/2481">#2481</a> has been updated by laforge.</p>
<p>Assignee changed from msuraev to zecke</p>
<p>msuraev wrote:</p>
<blockquote>
<p>Indeed, there's no such package:<br />[...]<br />comes up empty on latest nightly. Not sure how further split would have helped with PV variables though.</p>
</blockquote>
<p><a class="user active" href="https://osmocom.org/users/5">zecke</a>: Can you please sched some light on this? Would having a separate libosmotrau package have solved/avoided this problem?</p>
</blockquote>
<p>Same as before? e.g. SYS#3685. The libosmo-abis package is packaging multiple libraries into the same package. This way "osmo-bts" depends against "libosmo-abis" and not "libosmo-abis23 && libosmotrau1"</p>
<p>=> Add a dedicated libosmotrau package (PACKAGES += and split the files)?</p> Cellular Network Infrastructure - Bug #2481: osmo-bts with broken dependency in latest nightly https://osmocom.org/issues/2481?journal_id=65152017-12-03T13:02:36Zlaforge
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>In Progress</i></li><li><strong>Assignee</strong> changed from <i>zecke</i> to <i>msuraev</i></li></ul> Cellular Network Infrastructure - Bug #2481: osmo-bts with broken dependency in latest nightly https://osmocom.org/issues/2481?journal_id=65162017-12-03T20:40:14Zzecke
<ul></ul><p>I think just doing PACKAGES += "libosmotrau" and then putting FILES_libosmotrau = "../libosmotrau" should be enough. It should rebuild osmo-bts but if it doesn't you can increase <code>META_TELEPHONY_OSMO_INC</code> in meta-telephony to force a rebuild.</p>
<p>"libosmotrau" should just vanish.. but maybe opkg upgrade needs to be called twice. If not we can cheat a bit and put a RREPLACES_libosmotrau = "libosmo-abis". So that the unspecific package will be replaced by libosmotrau. This is because there is a bug where RREPLACES_libosmo-abis = "libosmo-abis" will be ignored by packaging. Confused? Then just try the above and we can solve the rest.</p> Cellular Network Infrastructure - Bug #2481: osmo-bts with broken dependency in latest nightly https://osmocom.org/issues/2481?journal_id=65262017-12-04T10:52:24Zmsuraev
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Stalled</i></li></ul><p>zecke wrote:</p>
<blockquote>
<p>Confused?</p>
</blockquote>
<p>Definitely. Pau, I recall you're did some work on automating PV update. Could you comment on this?</p> Cellular Network Infrastructure - Bug #2481: osmo-bts with broken dependency in latest nightly https://osmocom.org/issues/2481?journal_id=65492017-12-04T15:35:38Zpespin
<ul><li><strong>Status</strong> changed from <i>Stalled</i> to <i>Feedback</i></li><li><strong>Assignee</strong> changed from <i>msuraev</i> to <i>pespin</i></li></ul><p>If I understood correctly, the problem is that if we have more than 2 .so files in a package, then OE cannot apply its magic to name packages depending on the version of the .so file inside (appending the version to the package name), as debian does. As then osmo-bts depends on generic "libosmo-abis" package, if the .so version changes the package is still the same and then I suspects it doesn't recompile osmo-bts to match against the new so version?</p>
<p>I sent a patch to fix it in gerrit: <a class="external" href="https://gerrit.osmocom.org/#/c/5169">https://gerrit.osmocom.org/#/c/5169</a></p>
<p>I confirm that after building it, packages are named correctly with the version appended:<br /><pre>
deploy-ipks/armv5te/libosmoabis-dbg_0.4.0+gitr0+01543a1ea3-r3.18.0.0_armv5te.ipk
deploy-ipks/armv5te/libosmotrau-dev_0.4.0+gitr0+01543a1ea3-r3.18.0.0_armv5te.ipk
deploy-ipks/armv5te/libosmotrau2_0.4.0+gitr0+01543a1ea3-r3.18.0.0_armv5te.ipk
deploy-ipks/armv5te/libosmoabis-dev_0.4.0+gitr0+01543a1ea3-r3.18.0.0_armv5te.ipk
deploy-ipks/armv5te/libosmoabis6_0.4.0+gitr0+01543a1ea3-r3.18.0.0_armv5te.ipk
</pre></p>
<p>Regarding the automatic PV version, there's a different task for that and it's in progress as we need to do some development in a new bbclass to support it.</p> Cellular Network Infrastructure - Bug #2481: osmo-bts with broken dependency in latest nightly https://osmocom.org/issues/2481?journal_id=65622017-12-04T20:45:31Zzecke
<ul></ul><blockquote>
<p>On 4. Dec 2017, at 15:35, pespin [REDMINE] <<a class="email" href="mailto:redmine@lists.osmocom.org">redmine@lists.osmocom.org</a>> wrote:</p>
<p>Issue <a class="issue tracker-1 status-5 priority-2 priority-default closed" title="Bug: osmo-bts with broken dependency in latest nightly (Closed)" href="https://osmocom.org/issues/2481">#2481</a> has been updated by pespin.</p>
</blockquote>
<blockquote>
<p>If I understood correctly, the problem is that if we have more than 2 .so files in a package, then OE cannot apply its magic to name packages depending on the version of the .so file inside (appending the version to the package name), as debian does. As then osmo-bts depends on generic "libosmo-abis" package, if the .so version changes the package is still the same and then I suspects it doesn't recompile osmo-bts to match against the new so version?</p>
</blockquote>
<p>Right. So we can have libosmoabis5 and libosmoabis6 installed in parallel. You are right that if two .so files the renaming will/can't not be done.</p>
<blockquote>
<p>I confirm that after building it, packages are named correctly with the version appended:<br /><pre>
> deploy-ipks/armv5te/libosmoabis-dbg_0.4.0+gitr0+01543a1ea3-r3.18.0.0_armv5te.ipk
> deploy-ipks/armv5te/libosmotrau-dev_0.4.0+gitr0+01543a1ea3-r3.18.0.0_armv5te.ipk
> deploy-ipks/armv5te/libosmotrau2_0.4.0+gitr0+01543a1ea3-r3.18.0.0_armv5te.ipk
> deploy-ipks/armv5te/libosmoabis-dev_0.4.0+gitr0+01543a1ea3-r3.18.0.0_armv5te.ipk
> deploy-ipks/armv5te/libosmoabis6_0.4.0+gitr0+01543a1ea3-r3.18.0.0_armv5te.ipk</p>
</blockquote></pre> Cellular Network Infrastructure - Bug #2481: osmo-bts with broken dependency in latest nightly https://osmocom.org/issues/2481?journal_id=67292017-12-11T10:49:35Zpespin
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul> Cellular Network Infrastructure - Bug #2481: osmo-bts with broken dependency in latest nightly https://osmocom.org/issues/2481?journal_id=74912018-02-06T08:26:42Zlaforge
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>