https://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-09-10T13:48:17ZOpen Source Mobile CommunicationsOsmoTRX - Bug #3542: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7https://osmocom.org/issues/3542?journal_id=112342018-09-10T13:48:17Zosmith
<ul><li><strong>Project</strong> changed from <i>Cellular Network Infrastructure</i> to <i>SDR (Software Defined Radio)</i></li></ul> OsmoTRX - Bug #3542: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7https://osmocom.org/issues/3542?journal_id=112392018-09-10T14:02:55Zosmith
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-1 status-3 priority-3 priority-high3 closed parent" href="/issues/3176">Bug #3176</a>: osmocom debian packages are not install / upgrade tested</i> added</li></ul> OsmoTRX - Bug #3542: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7https://osmocom.org/issues/3542?journal_id=112412018-09-10T14:05:43Zosmith
<ul></ul><p>I could not set this as a subtask of <a class="issue tracker-1 status-3 priority-3 priority-high3 closed parent" title="Bug: osmocom debian packages are not install / upgrade tested (Resolved)" href="https://osmocom.org/issues/3176">#3176</a> after creating the issue, probably because I don't have the rights in the SDR project. So I set it as blocker for the other issue, now they are linked together that way.</p> OsmoTRX - Bug #3542: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7https://osmocom.org/issues/3542?journal_id=112432018-09-10T15:03:20Zlaforge
<ul></ul><p>On Mon, Sep 10, 2018 at 02:05:43PM +0000, osmith [REDMINE] wrote:</p>
<blockquote>
<p>I could not set this as a subtask of <a class="issue tracker-1 status-3 priority-3 priority-high3 closed parent" title="Bug: osmocom debian packages are not install / upgrade tested (Resolved)" href="https://osmocom.org/issues/3176">#3176</a> after creating the issue, probably because I don't have the rights in the SDR project. So I set it as blocker for the other issue, now they are linked together that way.</p>
</blockquote>
<p>I don't think the redmine UI can do this. If you find some documentation, I'd be interested.</p>
<p>The only way how I have so far created subtasks is directly from the master issue, never by<br />later somehow attaching any other tickets.</p> OsmoTRX - Bug #3542: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7https://osmocom.org/issues/3542?journal_id=112512018-09-11T13:59:24Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>about subtasks, I used to use them a lot, but the complex relations between them often made me regret that. These days all I do is just set "Related to".</p> OsmoTRX - Bug #3542: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7https://osmocom.org/issues/3542?journal_id=112612018-09-11T19:01:59Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>osmith</i></li></ul><p>Hmm, are we really packaging soapysdr from the Osmocom opensuse builds?<br />Are the differing soapy versions dependencies pulled in by Osmo packages?</p>
<p>About the modules of 0.5 and 0.6 conflicting, I'm not sure that this is related, but the LIBVERSION markers of .so files does not at all correspond to major.minor.patch software version tags.<br />This modules-0.5-2 looks like it isn't related to LIBVERSION either. Not sure what to make of this.</p> OsmoTRX - Bug #3542: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7https://osmocom.org/issues/3542?journal_id=112662018-09-11T19:23:29Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-2 priority-default closed child" href="/issues/3540">Bug #3540</a>: Conflicting Debian packages: osmocom-bsc-sccplite and osmo-bsc-mgcp</i> added</li></ul> OsmoTRX - Bug #3542: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7https://osmocom.org/issues/3542?journal_id=112862018-09-12T13:20:03Zosmith
<ul></ul><p>neels wrote:</p>
<blockquote>
<p>Hmm, are we really packaging soapysdr from the Osmocom opensuse builds?</p>
</blockquote>
<p>This is a good question. We have the following packages in the OBS repo (<a href="https://download.opensuse.org/repositories/network:/osmocom:/latest/Debian_9.0/amd64/" class="external">directory listing</a>), as found by aptitude:<br /><pre>
soapysdr-module-lms7
soapysdr0.6-module-lms7
soapysdr0.6-module-lms7-dbgsym
</pre></p>
<p>So no <code>soapysdr0.5</code> there.</p>
<blockquote>
<p>Are the differing soapy versions dependencies pulled in by Osmo packages?</p>
</blockquote>
<p>Yes, they are. I'm figuring out where they come from. What I can tell so far is, that they still get pulled in, even after blacklisting packages coming from the obsolete <code>openbsc.git</code>.</p>
<p>EDIT: It might also be that <code>soapysdr-module-lms7</code> pulls in the 0.5 package for some reason.</p> OsmoTRX - Bug #3542: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7https://osmocom.org/issues/3542?journal_id=112982018-09-12T13:40:15Zlaforge
<ul></ul><p>On Tue, Sep 11, 2018 at 07:01:59PM +0000, neels [REDMINE] wrote:</p>
<blockquote>
<p>Hmm, are we really packaging soapysdr from the Osmocom opensuse builds?</p>
</blockquote>
<p>we used to do, but now that we have osmo-trx-lms, we should deprecate that.</p> OsmoTRX - Bug #3542: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7https://osmocom.org/issues/3542?journal_id=113032018-09-12T14:09:00Zosmith
<ul></ul><blockquote>
<p>we used to do, but now that we have osmo-trx-lms, we should deprecate that.</p>
</blockquote>
<p>That was a very useful clue! I've created a <code>blacklist.txt</code> for the cronjob with packages from the repository, that it will not try to install (originally to blacklist all <code>openbsc.git</code> derived packages). Now I've added the following packages, and the <code>apt install</code> runs through successfully!</p>
<pre>
# SoapySDR is not used anymore (see OS#3542)
soapysdr-module-lms7
soapysdr0.6-module-lms7
soapysdr0.6-module-lms7-dbgsym
</pre>
<p>This issue can now be closed (I don't get the UI to change the status here, probably because of missing rights).</p>
<p>I am not really sure where the soapysdr packages come from (they don't seem to be in <a href="http://git.osmocom.org/osmo-ci/tree/scripts/osmocom-latest-packages.sh" class="external">osmocom-latest-packages.sh</a>). If somebody could give me a pointer, I could look into removing the binary soapysdr packages from the Debian package repository if that is desired.</p> OsmoTRX - Bug #3542: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7https://osmocom.org/issues/3542?journal_id=118132018-10-01T09:21:17Zosmith
<ul><li><strong>Blocks</strong> deleted (<i><a class="issue tracker-1 status-3 priority-3 priority-high3 closed parent" href="/issues/3176">Bug #3176</a>: osmocom debian packages are not install / upgrade tested</i>)</li></ul> OsmoTRX - Bug #3542: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7https://osmocom.org/issues/3542?journal_id=118162018-10-01T09:47:16Zlaforge
<ul><li><strong>Project</strong> changed from <i>SDR (Software Defined Radio)</i> to <i>OsmoTRX</i></li></ul><p>This is due to the fact that <a class="issue tracker-1 status-6 priority-2 priority-default closed" title="Bug: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7 (Rejected)" href="https://osmocom.org/issues/3542">#3542</a> is a different osmocom sub-project. <br />OsmoSDR and/or its child projects rtl-sdr, gr-osmosdr, osmo-fl2k, gr-gsm<br />are all projects in which sysmocom is not involved, and where sysmocom<br />developers do not automatically get 'developer' privileges.<br /><a class="external" href="https://osmocom.org/projects/sdr">https://osmocom.org/projects/sdr</a> will show you that the sysmocom<br />developers / employees are only listed in the 'Reporters' category.</p>
<p>Should sysmocom get involved in related projects, we could change that,<br />but I think in general it would be awkward to those projects and their <br />maintainers if employee status at sysmocm would automatically introduce<br />some role there.</p>
<p>I think the key problem is that this particular issue <a class="issue tracker-1 status-6 priority-2 priority-default closed" title="Bug: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7 (Rejected)" href="https://osmocom.org/issues/3542">#3542</a> was filed in<br />the "Osmocom SDR" project. Sure, it affects SDR hardware or drivers, <br />but not the Osmocom SDR software projects, which I've listed above. <br />Sorry for the confusion :).</p>
<p>I'm moving it now.</p> OsmoTRX - Bug #3542: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7https://osmocom.org/issues/3542?journal_id=121752018-10-12T12:21:08Zosmith
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Rejected</i></li></ul> OsmoTRX - Bug #3542: Conflicting Debian packages: soapysdr0.5-module-lms7 and soapysdr0.6-module-lms7https://osmocom.org/issues/3542?journal_id=134072019-02-20T10:00:31Zosmith
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-4 priority-high2 closed" href="/issues/3809">Bug #3809</a>: Osmocom-Debian-install-test fails since February 9</i> added</li></ul>