Age | Commit message (Collapse) | Author | Files | Lines |
|
Because the systemd install directory does not use --prefix as
base. For this reason, the build failed before, because installing
to /lib/systemd failed.
Change-Id: I39b491fc09f0db0efd8d9d09e8f4cba4ba49cdde
|
|
Otherwise the last modified branch will be build.
Change-Id: I0b68ebae025e0dc9dbfd22b97731b59be30e7823
|
|
Change-Id: I9eba05995fc53b72b04a4a9d63ebd5a236304f7c
|
|
Change-Id: Ia3bd58b98d1e248a92ddd171fb16a23ca8e0b29d
|
|
cmake is required to build LimeSuite, and its not currently installed in
the build slave.
Change-Id: I1808a2394798cd11a0bee8f664c7d18fa71cd5b8
|
|
Change-Id: Ic0fddfc0eaf884cdd5436139675a5a19fafa96b9
|
|
Change-Id: I9e6b01f465470f77c58268979d3608afe2005b1c
|
|
Change-Id: Idab162dd11c631d5e72f09b08ed04610e16f05a9
|
|
than git.osmocom.org
Change-Id: Ia37b5f761c47411ac7eab092f3437acecc492f22
|
|
Change-Id: I0e4fec571c3c373000c755cfdb5e56dc09d17413
|
|
A compatible package for debian8 as it does not support limesdr.
This patch depend on: I261302d2ed16e76540073589504e7426e23d00a1
Change-Id: I8477b580976b376ee5abdde98a651d47199ef6d9
|
|
For some reason almost all projects allow to permit building a
specific non-master branch, only osmo-hlr was missing that parameter.
Untested.
Change-Id: Ia4199aa5cfd1f39d34ed7c6104881c68d00dcffa
|
|
We're using the build() function not only to build osmocom projects
requiring a .tarball-version file, but also other projects such as
libusrp. Let's make the related git-buildpackage arguments conditional
to whether or not a .tarball-version file exists at all.
Change-Id: I0683cff036a240b1b819f91fbd230d5f9211074c
|
|
osmo-msc now needs libosmo-gsup-client, which is built+installed
as part of osmo-hlr
Change-Id: I581d86cf9679ef978a018a5ba8deb8b0f034677b
|
|
We're using the build() function not only to build osmocom projects
requiring a .tarball-version file, but also other projects such as
libusrp. Let's make the related git-buildpackage arguments conditional
to whether or not a .tarball-version file exists at all.
Change-Id: I0312a6671e739b803beb583769e4dfc6f44fa091
|
|
We add a bogus .tarball-version file to make limesuite look like
osmocom projects.
Change-Id: Idbe34df54743d346cf4194d6ea377e886132042d
|
|
If a new package is uploaded to OBS, prior to this change,
only the .dsc file is uploaded, not the actual .tar.xz containing
the source code. Let's fix that.
Change-Id: Id1c9e6d112781004238a516b24dd446af0beb95a
|
|
At the "autorecon -fi" stage, Osmocom programs either need the .git
directory peresent, or a .tarball-version file in order to determine
the exact source code version.
Normally, "make dist" exists exactly for this purpose: It runs
git-version-gen and saves the result to .tarball-version, and we then
include this file in the .tar.gz we generate.
However, as the nightly paackaging scripts use git-buildpackage, it
bypasses the "make dist" logic and hence we need to
1) manually generate the .tarball-version file
2) copy it over to the directory specified as --git-export-dir
This way, the .tarball-version is inside the tar.xz generated by gbp,
and autoreconf then has something to use as PACKAGE_VERSION.
This commit fixes "UNKNOWN-dirty" in .pc files of libraries, as well
as in "show version" commands on the vty.
Closes: OS#3449
Change-Id: I76e3713f0b01a6110091ff90e8e53aa79533c374
|
|
Change-Id: I3967d7b4203f5361dc03074dcd82c870d60c8aac
|
|
pysim will be tested on the simtester which has real hardware.
Change-Id: I180cc4a83a41f3ef2e4b1e316ea0371cc83be654
|
|
osmo-mgw is duplicated and osmo-bsc is not there.
Change-Id: Ib0ab7f8796b8b78d5f21b7a4f541fd3ddffc95a4
|
|
Change-Id: Iab74a2b3fc3148bce815b2dadd1fd683c4b64c44
|
|
To select if some utilities including qemu/debootstrap/fakeroot will be installed.
Usefull for small setups e.g. simtester
Change-Id: I72f4460b8550da191e74a44be0ee3eeb3b2d7769
|
|
Pulls a lot of packages
Change-Id: I894455ea779ece84c403f768a1260a1cf2528389
|
|
own file
For small nodes (e.g. simtester) the full blown packages are not required nor supported.
In this case only the jenkins user and the ssh keys will be setted up.
Change-Id: I469a8012b124516bfd9c4d4dd3a3fe0e1ff80bb6
|
|
Change-Id: I878ed30ee2f44d98635511011c17f0f0e986bcc9
|
|
If string eval encounters an uncovered parse error, it's useful to know which
file it happened in.
Change-Id: I5fe9a3bbdbfb8a995f24596bf09e70ca5bb3fe8a
|
|
Change-Id: I439ee65cd65cf42e1005ca71aa7d4b680b18c0e5
|
|
Change-Id: Ib75c8f5a99ed556d85896b7f8c65fb9446a2fbce
|
|
Would miss those where the fmt string starts on a new line.
Change-Id: If61a36a014a799b94030e5e08a50dfef4207a8a2
|
|
This came up in
https://gerrit.osmocom.org/#/c/osmo-bsc/+/9671/6//COMMIT_MSG@36
The errors it finds in the current code base are numerous, and many are
intended LOGP .. LOGPC calls. It doesn't make sense to enforce this, but so far
this can be used manually.
Change-Id: Id79389f090a2fded7ff01dc7e3fe9774e7f22ca0
|
|
Kevin would like to upload simtrace firmware to ftp.osmocom.org from master
builds. To facilitate, add '--publish' arg, like in master-osmo-gsm-manuals (to
distinguish and not upload from gerrit verification jobs).
Change-Id: I93435aa6f39e9a072754011ae7696b10315f6092
|
|
This is the same as done for the master builds in
I6f025c642d5ae57cdda9d7b34bbaeb82ca119354,
seems I forgot to follow up with this one.
Change-Id: I9204ca2f083c8a6a04c6c0fc7d51752a4f1a4830
|
|
So far we call with a $(find . -name "*.[hc]") argument list, which might
become too long at some point. Rather include dir walking in the script itself
and allow passing dir arguments as well.
This is backwards compatible, calling with above file args still works.
Change-Id: I36456383906b6295c798b82aa131dda21f8efc02
|
|
Change-Id: Iedf3b43c164ae7e3e653820284c4d4ddaa545784
|
|
This seems to resolve the issue where the jenkins job fails due to
missing ssh credentials.
Other jobs can also use this by setting the node property
Change-Id: I23cf2c98f02278a5deb9c4ae8d13438b76538287
Ticket: OS#3338
|
|
Change-Id: I708960790e330a24c653f162b767d3b3ca4d145d
|
|
We currently use range around 10.42.42.1-10 for local dynamically
assigned IP addresses (osmo-msc, osmo-bsc, etc.).
The range 10.42.42.50-60 for local statically assigned IP addresses
(to run osmo-bts-trx sysmocell-5k for instance, where the other end
is cofigured with a static dst addr).
For remote addresses, we use IPs in the range 10.42.42.110-120.
Let's create a new range in 10.42.42.120-130 for remote addressess
assigned by udhcpd server.
nanobts assigned assdresses are moved to the latest group to
differentiate them easily and show that they are not IP addr used
locally.
Change-Id: I9eadb0329a670ce6c2254520d9c86bfbdc898b3a
|
|
Change-Id: Ib4da0011337d5a591944821411479f1c6bcc64ee
|
|
Change-Id: Id8b4b4d7a1e4328565b06faff2eaccea7efa74e2
|
|
osmo-trx-lms requires limesuite newer than 17.02, as there were a lot of
features and bug fixes which osmo-trx relies on. Furthermore,
osmo-trx-lms cannot build with that version since it doesn't provide
yet a pkgconfig file.
We cannot use latest tagged release (18.06) since that version has some
build related bugs which have been fixed later on
(c1496679cadff2913cacdaa84afe93bbee76d8e4), hence why we are using
latest available master instead.
Change-Id: If47a3767c7fefbb75923cbfc8eeb921e29393285
|
|
Let's move limesuite first since it doesn't depend itself on any osmocom
related package, and osmo-trx depends on it.
Change-Id: I0cdc85a2d0212432bf0c2586230660d363212dcc
|
|
Writing '{ 0, NULL }' is actually identical to just '{}', and that's what I use
these days in all sorts of other contexts. So allow this notation as well in
the C code grepper.
Change-Id: I0822d2d997dccbfb31316953a7b6024c317d92cf
|
|
Change-Id: I9d22cd6e4d3a3c8c685362bb62cd2a6ef467c461
|
|
Change-Id: I35da5f2276730c7f81d5a1c2e6878ea3e23bca3b
|
|
Change-Id: I43169dfb39525ffe16a3ed1cbf5360b47f9f8a00
|
|
Change-Id: Ib0169c858c3c0610e49d01f1dafee5c725ddc7df
|
|
Change-Id: Ia39284acce65c5779b71154662f3f55349a86960
|
|
In the production setup, there are only 3 valid modems.
Moving the variable into the host_vars so they can have
different amount of modem between rnd & prod.
Change-Id: Ic51a14a339bb9be50504a27a724f6f428ee7304f
|
|
uhubctl -p 123456 -a 1 is rejecting because uhubctl detects two hubs.
Selecting only one hub.
Fixes the error message:
Error: changing port state for multiple hubs at once is not supported.
Use -l to limit operation to one hub!
Change-Id: I2e3c248e4eaef39f18ff38d1055db6d552fc4d20
|