Re: Build failure of network:osmocom:nightly/simtrace2 in xUbuntu_18.04/x86_64
These build failures are continuously piling up in my inbox. Would it make sense to either fix or disable it? ~N On Sat, Sep 22, 2018 at 08:01:31PM +0000, OBS Notification wrote:
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/si...
Package network:osmocom:nightly/simtrace2 failed to build in xUbuntu_18.04/x86_64
Check out the package for editing: osc checkout network:osmocom:nightly simtrace2
Hi Neels, On Sun, Sep 23, 2018 at 04:12:11PM +0200, Neels Hofmeyr wrote:
These build failures are continuously piling up in my inbox.
Welcome to the club.
Would it make sense to either fix or disable it?
The problem is that the person (likely) responsible for the commit breaking the build has been on holidays for two weeks and hence (understandably) not responding my related e-mail. commit faf1e88e48c216456bdea6060a623b7c31f07c70 is likely the cause of this, as it introduced the use of pkg-config for libpcsc-lite. [ 131s] Package libpcsclite was not found in the pkg-config search path. I guess the only solution to this kind of problem is to ensure nobody pushes/submits any patches immediately before any [scheduled] period of absence. It can happen to any of us. -- - Harald Welte <laforge@gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
On Sun, Sep 23, 2018 at 05:01:04PM +0200, Harald Welte wrote:
I guess the only solution to this kind of problem is to ensure nobody pushes/submits any patches immediately before any [scheduled] period of absence.
You mean like me merging the refactoring code bomb of osmo-bsc the day before going on three weeks of summer vacation? ;) (I'm quite proud/surprised that the fallout from that was so limited.) ~N
participants (2)
-
Harald Welte -
Neels Hofmeyr