20 Feb
2019
20 Feb
'19
9:46 a.m.
Dear Osmocom community,
for the last 10 days our "Debian installation test" job is consistently
failing,
see https://jenkins.osmocom.org/jenkins/job/Osmocom-Debian-install-latest/
It somehow seems to be related to soapySDR mismatching versions where we use a 0.5
package
from the debian feed:
Get:358 http://deb.debian.org/debian stretch/main
amd64 libsoapysdr0.5-2 amd64 0.5.4-1 [64.4 kB]
and mix that with a 0.7 lms7 module from our feed:
Get:425
http://download.opensuse.org/repositories/network:/osmocom:/latest/Debian_9… ./
soapysdr0.7-module-lms7 19.01.0-1 [49.9 kB]
Unpacking soapysdr0.7-module-lms7:amd64 (19.01.0-1)
...
dpkg: error processing archive
/tmp/apt-dpkg-install-aYn9qf/398-soapysdr0.7-module-lms7_19.01.0-1_amd64.deb (--unpack):
trying to overwrite
'/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.5-2/libLMS7Support.so', which is also
in package
...
Errors were encountered while processing:
/tmp/apt-dpkg-install-aYn9qf/398-soapysdr0.7-module-lms7_19.01.0-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Build step 'Execute shell' marked build as failure
Finished: FAILURE
Does anyone know of any change that would have triggered this?
I've created https://osmocom.org/issues/3809 to track this.
Regards,
Harald
--
- Harald Welte <hwelte(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
20 Feb
20 Feb
4:20 p.m.
Hello,
I have created a short patch to fix this (see the linked issue for
details, reviews welcome).
Now I'm wondering about e-mail notifications for failed builds (so we
can react faster in the future). So far I have created a patch to add
only myself to the list of e-mail receivers:
https://gerrit.osmocom.org/#/c/osmo-ci/+/12978/
Vadim has asked about adding the whole mailing list to the receivers, so
I'm wondering what members of this ML are thinking about that.
Regards,
Oliver
On 2/20/19 9:46 AM, Harald Welte wrote:
Dear Osmocom community,
for the last 10 days our "Debian installation test" job is consistently
failing,
see https://jenkins.osmocom.org/jenkins/job/Osmocom-Debian-install-latest/
It somehow seems to be related to soapySDR mismatching versions where we use a 0.5
package
from the debian feed:
--
- Oliver Smith <osmith(a)sysmocom.de> https://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
Get:358 http://deb.debian.org/debian stretch/main
amd64 libsoapysdr0.5-2 amd64 0.5.4-1 [64.4 kB]
and mix that with a 0.7 lms7 module from our feed:
Get:425
http://download.opensuse.org/repositories/network:/osmocom:/latest/Debian_9… ./
soapysdr0.7-module-lms7 19.01.0-1 [49.9 kB]
Unpacking soapysdr0.7-module-lms7:amd64
(19.01.0-1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-aYn9qf/398-soapysdr0.7-module-lms7_19.01.0-1_amd64.deb (--unpack):
trying to overwrite
'/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.5-2/libLMS7Support.so', which is also
in package
...
Errors were encountered while processing:
/tmp/apt-dpkg-install-aYn9qf/398-soapysdr0.7-module-lms7_19.01.0-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Build step 'Execute shell' marked build as failure
Finished: FAILURE
Does anyone know of any change that would have triggered this?
I've created https://osmocom.org/issues/3809 to track this.
Regards,
Harald
7:09 p.m.
Hi Oliver,
On Wed, Feb 20, 2019 at 04:20:13PM +0100, Oliver Smith wrote:
I have created a short patch to fix this (see the
linked issue for
details, reviews welcome).
Thanks a lot for the quick follow-up!
Now I'm wondering about e-mail notifications for
failed builds (so we
can react faster in the future).
Vadim has asked about adding the whole mailing list to
the receivers, so
I'm wondering what members of this ML are thinking about that.
not this list, as the amount of auto-generated mails would by far outweight the
amount of human-generated mails and basically make this list unusable.
In the past we argued sending the notifications to the commitlog or gerrit-log
lists, but I think there e.g. I would never look at them as I don't read those
lists frequently.
So maybe yet another list? This way we can make sure to only notify those people
who have actively signed up.
I guess unless there's significant disagreement, I'll create something like
jenkins-notifications(a)lists.osmocom.org ?
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
3 Mar
3 Mar
3:55 p.m.
On Wed, Feb 20, 2019 at 07:09:28PM +0100, Harald Welte wrote:
I guess unless there's significant disagreement,
I'll create something like
jenkins-notifications(a)lists.osmocom.org ?
done. Will be adding this address to our jenkins build jobs in a patch asap.
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
1889
days inactive
1900
days old
4 comments
4 participants
participants (4)
-
Harald Welte -
Harald Welte -
Neels Hofmeyr -
Oliver Smith