Python 2 is EOL at the end of 2019, so don't depend on it anymore.
Remove pychart support, because upstream is dead and there is no python3
version. We were only using it for one graph, and that has been
replaced in osmo-bsc I36b721f895caee9766528e14d854b6aa2a2fac85.
Depends: osmo-bsc I36b721f895caee9766528e14d854b6aa2a2fac85
Related: OS#2819
Change-Id: I57522e57e39682d6d123af4584785d327361e5a3
Adjust vty_reference_combine.sh, so we can change the output dir from
"generated" to a subdir inside "generated" when building anything but
the first VTY reference.
Add a generic pattern to Makefile.vty-reference for additional VTY
references, that uses slightly different paths compared to the first VTY
reference, in order to avoid collisions.
Related: OS#4292
Change-Id: I4dea3e07b88175b2a88e577129360af7ec5f87e1
As seen by https://packages.debian.org, python-nwdiag is only available
in buster and older stables, while python3-nwdiag is available in both
old and new releases as well as testing and unstable.
Related: OS#4246
Depends: osmo-ci I0ebee6ac11df779ab954bd6648a0bebefc3350a2
Change-Id: Ia2c0c833329f8ecab1c427e0d2c002f17ab49a94
Make sure that glossary.adoc is the last file, when building the test
pdf with all common chapters included. Otherwise, newer asciidoc
versions will complain that we cannot have subchapters after the
glossary began:
asciidoc: ERROR: mgcp_extension_osmux.adoc: line 2: glossary section cannot contain sub-sections
Related: OS#4183
Change-Id: I91e857255b1b6d5b8708cc7f7b303a58403120d3
Only check for asciidoc warnings in "make check" if
ASCIIDOC_WARNINGS_CHECK is set. Enable it in jenkins.sh by using the
new ./configure --enable-asciidoc-warnings-check parameter (similar to
--enable-werror in other Osmocom projects' configure.ac files).
Related: OS#4140
Change-Id: Iac993a0d1b17205397a1f1ef1a7bd3f9df739e36
a2x is a "toolchain manager" for asciidoc, that runs the asciidoc
command internally. Replace the previous logic of first running a2x
without any verbose flags, and on failure running asciidoc standalone,
with a verbose flag, to print the errors the occured. Always run a2x
with -vv, so it runs asciidoc in verbose mode.
This prevents losing the error message in case asciidoc or a2x fail
when running with a2x, but then asciidoc succeeds when running
standalone.
Related: OS#4132
Change-Id: I2cbd2985645ecdecc7851849be6a9a95d4b3246e
Several fixes and improvements to the documentation.
This documentation still doesn't contain infrmation about TRXDv1, it
will be added in a follow-up commit.
Change-Id: I36e6206b90435964842f9f1ebd982cdaf9777018
The Osmux documentation that will be introduced in [1] creates a
common/chapters/osmux/ subdir. Update tests/Makefile.am to pick up the
files in that directory too, so they get built by jenkins during gerrit
verification.
[1] I182d94c63f7d74ef882b77be59a95b1b7d8a4e5e
Change-Id: I4d1f440b7bfef159c98f918a2d23069594c4bc95
Otherwise, adoc files in osmo-*/doc/manuals/chapters/*.adoc cannot
include files from osmo-gsm-manuals/common/chapters/*.adoc, since
symbolic link to common/ is only available in builddir, but not in
srcdir.
This way, those files can include commons files like this:
include::{commondir}/chapters/foobar.adoc
Change-Id: Ifc2fdaf1a87d0715213b4eab13c6c9a4f8a987fd
Add dh-autoreconf to build dependencies, and libxml2-utils (provides
xmllint) to dependencies. Both need to be explicitly installed on
debian 8.
Related: OS#3899
Change-Id: If929fca73e3a88567e144eb296e7fadd32904dd5
Message formats of the new messages look mostly the same (IMSI,
Message Class, Source Name, Destination Name, AN-APDU). That is, because
AN-APDU is storing results, error reasons etc. This can be seen clearly
in osmo-msc.git:
* src/libmsc/msc_a_remote.c:msc_a_remote_fsm_communicating()
* src/libmsc/msc_i_remote.c:msc_i_remote_fsm_ready()
The message squence charts in the E Procedures section are directly
based on Neels' interMSC_HO_GSUP_msgs.txt [1].
It seems that using AN-APDU made some other new IEs redundant: RR Cause,
BSSAP Cause, Session Management Cause had been added to GSUP for the MSC
handover, and are documented now, but they are currently not used in
osmo-msc.git. The new message OSMO_GSUP_MSGT_E_ABORT is not used either,
so I left a stub for it in the message format section.
I mentioned in the Source Name IE section, that source and destination
names are sent as nul-terminated strings. This is for legacy reasons,
Neels wrote a nice summary in the commit message of [2].
[1] https://osmocom.org/attachments/3720/interMSC_HO_GSUP_msgs.txt
[2] Change-Id: I9ca8c9eef104519ed1ea46e2fef46dcdc0d554eb (osmo-msc)
Related: OS#3774, OS#3619
Change-Id: I6b9f23d08cfe53c8b77f51c6afb900c2badc9e2c
Replace '--with autotools_dev' with '--with autoreconf' in
debian/rules, so a ./configure file gets generated from configure.ac,
and the debian package scripts don't generate an empty package.
I did not notice this earlier, because when building the package locally
with dpkg-buildpackage, it was not empty. (That is probably, because my
local dir already had the configure script generated.)
Related: OS#3899
Change-Id: I483136cd28395ae8fc2c112cf659ee83255afe87
Add a patch file that removes the asciidoc-dblatex dependency in
debian/control, so the package builds for debian 8. In debian 8, the
files are all in the asciidoc package, which does get installed.
The jenkins scripts will copy the source package, apply the patch, and
upload it separately to OBS [1]. A similar debian 8 patch exists for
osmo-trx.
I have also tried to do it without a patch, by changing the OBS
configuration. It is possible to bypass the dependency check from OBS
and get the build started, but there's an additional check by
dpkg-checkbuilddepends and this one does not pass. So we really need
the patch method.
[1]: Change-Id I3570599ede51b974d350064f44f77e360fafd8b0 (osmo-ci)
Related: OS#3899
Change-Id: I5b9575ceb1141961e570643a5755a2bd6b6a4254
Allow including pdf manuals in each Osmocom repositories -doc debian
package, by depending on osmo-gsm-manuals-dev.
Related: OS#3899
Example usage: I4c184c62804c0b805a0a2425a5bd0312e94e49ab (osmo-bts.git)
Change-Id: I7edb5093e5b58eb3b0f7af2376476db4026db735
Don't install the noarch osmo-gsm-manuals.pc file to
$prefix/lib/x86_64-linux-gnu/pkgconfig when building a debian package
(dpkg-buildpackage seems to set $libdir accordingly). Always install to
$prefix/lib/pkgconfig.
The debian dir for creating a package from this repository will be added
in a follow up patch.
Related: OS#3899
Change-Id: I63bc8ab6d2845751079f40383d2aa92c709ce2fe
Allow installing generated pdfs with 'make install' in all Osmocom
projects using osmo-gsm-manuals. This makes proper debian packaging of
the manuals easier.
Autotools will automatically run this file's install target, when
running 'make install' in the top source dir. Do not install anything,
when OSMO_GSM_MANUALS_NO_INSTALL is set, and set this variable for the
tests dir, so we don't install the test pdfs.
Related: OS#3899
Change-Id: I66f33172fa410681acbaef4592e9405627948705
Remove git from depends, because it isn't needed when building the
manuals from a source tarball. Avoid having git in the build
dependencies of the upcoming manuals packaging for debian.
Related: OS#3899
Change-Id: I46ad818a1d009c03357821f7c8100ecb5d62962e
Don't explicitly depend on python 3, so we don't need to have python 2
*and* python 3 installed to build osmo-gsm-manuals.
The script is short and works fine with either python version.
Related: OS#3899
Change-Id: I8af9b8159f5c7e39b905f85edd1584cb4d5a33ef
Move the "IMEI" and "IMEI Check Result" IEs from the "Session
(transaction) management" chapter (which describes session IEs) to the
"Information Elements" chapter. Add a comment to prevent this mistake in
the future.
Related: OS#2541
Change-Id: I6fd66419350e018a763b8fac3daf567b339a2637
Change-Id: I9a0536f285f98f24fec4d7318f1923782ed2e18c
Related Change-Id: Ie0150756c33c1352bc4eb49421824542c711175c
Related Change-Id: I549b6c8840a1e86caac09e77fb8bc5042d939e62
Make this part of the specification, so we can simplify libosmocore
code by knowing that error message is (request message | 0x000001).
Related: I46d9f2327791978710e2f90b4d28a3761d723d8f (libosmocore)
Change-Id: Iec1b4ce4b7d8eb157406f006e1c4241e8fba2cd6
The 'check' target is only available when including
Makefile.asciidoc.inc, which is not always the case. Some projects only
build the VTY reference. Do not depend on check, so publishing the
VTY reference for these projects is working as expected.
Related: OS#3385
Change-Id: I64aae0016095d81ca9e9ebda9a2e3336ac126639
Oliver Smith
Harald Welte
Pau Espin
Martin Hauke
Daniel Willmann
Vadim Yanitskiy