OpenMP is no longer used since commit 4f617b70 ("box: introduce
memtx_sort_threads config parameter"). All dependencies on libgomp
should be removed.

Follow-up #7689

NO_DOC=build
NO_TEST=build

Part of tarantool/tt#286

NO_TEST=third-party dependency
NO_DOC=third-party dependency

Curl 7.87 uses CMake's keywords (for example GREATER_EQUAL [0])
available since CMake 3.7. However, we are still supporting old Ubuntu
version where CMake version lower than 3.7 is used. This patch adds a
script that enables CMake repository with newer CMake packages for
Ubuntu 16.04 (Xenial) and bumps a required version of CMake.

NOTE (regarding cmake3 package):

Commit 1a62d874 ("build: update CMake minimum version to 3.1") [1]
added an additional package requirement with "cmake3". This package has
been created in addition to package "cmake", because CMake 3 had
breaking changes [2]. Package "cmake3" has been provided only in Ubuntu
14.04 LTS (Trusty Tahr) [4], that will be EOLed in 2024, and CentOS 7,
that was EOLed in Aug 2020 and will have end of security support in Jun
2024 [5]. Latest version of package "cmake3" for Ubuntu 14.04 is 3.5.1
[3], so it is not worth to bump version of cmake3 in requirements and I
left it the same.

0. https://cmake.org/cmake/help/latest/command/if.html#greater-equal
1. https://github.com/tarantool/tarantool/commit/1a62d874db5f4780da5b35b6d4d0e3a296148920
2. https://cmake.org/cmake/help/latest/release/3.0.html#id4
3. https://launchpad.net/ubuntu/trusty/+package/cmake3
4. https://ubuntu.com/about/release-cycle
5. https://wiki.centos.org/About/Product

Needed for #8150

NO_CHANGELOG=see the next commit
NO_DOC=libcurl submodule bump
NO_TEST=libcurl submodule bump

The dependency is redundant, because the library is now bundled into
tarantool (see PR #6877).

There is a practical reason to remove it: this way we'll verify that
presence of system libunwind headers is not necessary to build
tarantool. In other words, we'll verify that #8025 will not appear
again.

Follows up #8025
Follows up #6877
Part of #6998

NO_DOC=No user visible changes, just some validation for a build fix.
NO_TEST=See NO_DOC.
NO_CHANGELOG=See a changelog entry in the previous commit.

Now we base on some unreleased state of libunwind. This is by itself not
a good practice. Yet the main motivation is that in the current version of
libunwind fast path for backtrace detection on x86_64 does not work.
I guess this is because of libunwind/libunwind@400b3f819ad4 (" x86_64: Stop
aliasing RSP and CFA"). See libunwind/libunwind#440. Fortunately this
commit is not present it the latest release.

Using fast or slow path has a great impact on performance of debug build
where collecting fiber gc allocation backtrace is turned on by default.
It surely depends on frequency and pattern of allocation. Test
sql/delete3 depends on backtrace performance most dramatically. On some
installations collecting backtraces slowed down the test up to 10 times.

If fast path is available then collecting backtrace does not affect
performance in a noticeable way.

I propose not to keep autotools products in the libunwind fork repo as
it is done previously. LOG_CONFIGURE is removed because it somehow
incompatible with using && in CONFIGURE_COMMAND command and not critical
to the build.

Also add autotools build dependencies for packpack package specs.
Currently not all packpack images have autotools preinstalled so this is
required for build to success. Anyway we'b better have precise build
requirements in build specs.

Follow-up #5665

NO_DOC=internal
NO_TEST=internal
NO_CHANGELOG=internal

This patch adds the tzdata package as a dependency for DEB/RPM tarantool
package since some tarantool datetime functionality needs this.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Now the test-run dependencies (pyyaml, gevent) have the corresponding
deb packages installable via the 'apt' package manager and finally it's
time to enable running tests in the package build process.

Closes #1341

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Before this patch Tarantool http client did not support HTTP/2.
The reasons to enable HTTP/2 support are efficiency offered by
the protocol and potential ability to interact with a GRPC server.
The CMake version requirement is updated from 3.2 to 3.3, because
we need generator expressions in cmake for setting multiple paths
in CMAKE_FIND_ROOT_PATH for nghttp2 support.

Closes #5771

@TarantoolBot document
Title: Now we require CMake 3.3 to build tarantool

In tarantool/doc#2065 we requested to update
the CMake minimum version to 3.2. Now it is time for 3.3.
See details in the linked commit.

tarantool debian package MUST NOT depends on binutils package. This is
due to the fact that binutils include linker and assembler, what in most
cases forbidden on production servers.

This dependency is a residual from times, when tarantool did use libbfd
for stack unwinding. Now it simply does not required at all.

Fixes #6699

This patch fixes ancient-standards-version lintian warning for modern
systems. Standards-Version is 4.5.1 recommended for Debian Bullseye,
Ubuntu Groovy and Hirsute. Older versions do not support 4.5.1 and thus
yield newer-standards-version warning. This patch overrides it.

Most notable changes:

- Packages must not call /etc/init.d scripts directly even as a fallback,
  and instead must always use invoke-rc.d (which is essential and
  shouldn’t require any conditional).

- Packages may not install files in both /path and /usr/path, and must
  manage any backward-compatibility symlinks so that they don’t break
  if /path and /usr/path are the same directory.

- Packages are recommended to build reproducibly even when build paths
  and most environment variables are allowed to vary.

- Clarify that programs may invoke either /usr/bin/editor and
  /usr/bin/pager directly, or use editor and pager and rely on PATH.

- If /etc/staff-group-for-usr-local does not exist, /usr/local and all
  subdirectories created by packages should have permissions 0755 and
  be owned by root:root. If the file exists, the old permissions of 2775
  and ownership of root:staff should remain.

- Packages should not contain a non-default series file. That is, dpkg’s
  vendor-specific patch series feature should not be used for packages
  in the Debian archive.

- Binaries should be stripped using strip --strip-unneeded
  --remove-section=.comment --remove-section=.note
  (as dh_strip already does).

- Packages that include system services should include systemd service
  units to start or stop those services.

- Use of update-rc.d is required if the package includes an init script
  (previously, Policy said in one place that it was required, and
  in another said that it was recommended).

- Shared libraries must now invoke ldconfig by means of triggers,
  instead of maintscripts.

- Required targets must not write outside of the unpacked source package
  tree, except for TMPDIR, /tmp and /var/tmp.

You can read full changelog here:
https://www.debian.org/doc/debian-policy/upgrading-checklist.html

No changes was introduced in package building pipeline after upgrade
since there aren't any affecting behavior changes.

Part of #6390

Before this patch all PackPack-builded packages was treated as
non-maintainer updates. It fixes no-nmu-in-changelog and
source-nmu-has-incorrect-version-number lintian warnings.

Part of #6390

Bump debian/compat to 10 since 9 is deprecated. Bump minimal required
debhelper to 10 (except for Ubuntu Trusty and Xenial) since it is the
recommended practice for compatibility level setup.

Closes #6393

Promote @Totktonada to be a new maintainer for debian packages.

Closes #6392

Bump tarantool-common dependency to use luarocks 3.
Prior to this patch, it was permitted to have
new tarantool package (version >= 2.2.1) installed with
pre-luarocks 3 tarantool-common package (version << 2.2.1).
It caused rocks install to fail.

Closes #5429

The reason of the update is to protect us against possible MITM attack
from a malicious HTTPS proxy server with trusted certificate when TLS
1.3 is used (CVE-2021-22890, [1]). libcurl versions prior to 7.76.0 can
skip a TLS handshake with a target host in this circumstances.

Other vulnerabilities fixed in the (7.71.1; 7.76.0] version range do not
look relevant to our built-in http client. See [2] for the full list.

The CMake version requirement is updated from 3.1 to 3.2, because curl's
CMakeLists.txt has the following clause at beginning:

 | cmake_minimum_required(VERSION 3.2...3.16 FATAL_ERROR)

(It was there in vanilla curl 7.71.1 too and we had to remove it in
order to support CMake 2. Now we don't support CMake 2, so it is good
time to get rid of the extra patch upward vanilla curl repository.)

According to the CMake versions table in
8a7702b1 ('github-ci: purge Debian
Jessie from CI'), CMake 3.2+ is available on all supported OSes.

[1]: https://curl.se/docs/CVE-2021-22890.html
[2]: https://curl.se/docs/vulnerabilities.html

@TarantoolBot document
Title: Now we require CMake 3.2 to build tarantool

In https://github.com/tarantool/doc/issues/1780 we requested to update
the CMake minimum version to 3.1. Now it is time for 3.2. See details in
the linked commit.

Please, update the 'Building from source' manual.

LuaJIT submodule is bumped to introduce the following changes:
* test: run luacheck static analysis via CMake
* test: fix warnings found with luacheck in misclib*
* test: run LuaJIT tests via CMake
* build: replace GNU Make with CMake
* build: preserve the original build system

Since LuaJIT build system is ported to CMake in scope of the changeset
mentioned above, the module building the LuaJIT bundled in Tarantool is
completely reworked. There is no option to build Tarantool against
another prebuilt LuaJIT due to a91962c0
('Until Bug#962848 is fixed, don't try to compile with external
LuaJIT'), so all redundant options defining the libluajit to be used in
Tarantool are dropped with the related auxiliary files.

To run LuaJIT related tests or static analysis for Lua files within
LuaJIT repository, <LuaJIT-test> and <LuaJIT-luacheck> targets are used
respectively as a dependency of the corresponding Tarantool targets.

As an additional dependency to run LuaJIT tests, prove[1] utility is
required, so the necessary binary packages are added to the lists with
build requirements.

[1]: https://metacpan.org/pod/TAP::Harness#prove



Closes #4862
Closes #5470
Closes #5631

Reviewed-by: Sergey Kaplun <skaplun@tarantool.org>
Reviewed-by: Timur Safin <tsafin@tarantool.org>
Signed-off-by: Igor Munkin <imun@tarantool.org>

In scope of implementing self-sufficient testing environment LuaJIT
build system is partially ported to CMake. While integrating the new
build system with Tarantool it was found (on practice of course) that
using generator expressions[1] in target DEPENDS section is introduced
only in CMake 3.1[2]. This CMake feature is used to pass so called
"LuaJIT binary" to be used in LuaJIT tests, so one can run the same
testing machinery with both Tarantool and LuaJIT with no changes in it.

[1]: https://cmake.org/cmake/help/v3.1/manual/cmake-generator-expressions.7.html
[2]: https://cmake.org/cmake/help/latest/release/3.1.html#commands



Relates to #4862

Reviewed-by: Alexander V. Tikhonov <avtikhon@tarantool.org>
Signed-off-by: Igor Munkin <imun@tarantool.org>

@TarantoolBot document
Title: Update CMake minimum required version in build documentation

This commit updates the CMake minimum required version to be used in
Tarantool build infrastructure. However, one can build Tarantool from
sources and the required toolchain list should be updated. CMake minimum
required version is 3.1 since this commit. See the commit message for
more info.

After cURL was changed to use cmake in commit

  2b076019 ('build: enable cmake in curl build')

there is no need to set dependencies to autotools. So removed it from:

  - rpm build spec for packages builds
  - deb build control for packages builds
  - OSX build targets
  - static OSX build target
  - freebsd VBOX VM image setup

Make build dependency on dh-systemd optional, as this package is
deprecated and removed from Debian 11. It part of debhelper (>=
9.20160709) now. No new dependencies, as tarantool already depends on
debhelper (> 9).

After we started using bundled version of libyaml by default (see commit
47b91e90), we can remove it from
building dependencies for RPM and DEB packages.

Closes #4442

Reviewed-by: Alexander Turenko <alexander.turenko@tarantool.org>

Hold libcurl-7.65.3. This version is not affected by the following
issues:

* #4180 ('httpc: redirects are broken with libcurl-7.30 and older');
* #4389 ('libcurl memory leak');
* #4397 ('HTTPS seem to be unstable').

After this patch libcurl will be statically linked when
ENABLE_BUNDLED_LIBCURL option is set. This option is set by default.

Closes #4318

@TarantoolBot document
Title: Tarantool dependency list was changed

* Added build dependencies: autoconf, automake, libtool, zlib-devel
  (zlib1g-dev on Debian).
* Added runtime dependencies: zlib (zlib1g on Debian).
* Removed build dependencies: libcurl-devel (libcurl4-openssl-dev on
  Debian).
* Removed runtime dependencies: curl.

The reason is that now we use compiled-in libcurl: so we don't depend on
a system libcurl, but inherit its dependencies.

Remove libbfd from dependencies and use libunwind for stack traces.

Closes #2103

LuaRocks requires openssl and curl in order to download
manifest from rocks.tarantool.org.

Fixes #2612

Inpspired by tarantool/curl module by Vasiliy Soshnikov.
Reviewed and refactored by Roman Tsisyk.

Closes #2083

Set LimitNOFILE to 65535 to provide the best Vinyl experience
out of the box.

Closes #2465

Force tarantool-common upgrade to support systemd notifications.

+ Add missing "s" suffix to TimeoutStartSec= option.

See #1923

This patch removes following source files regeneration:
  1. keywordhash.h
  2. opcodes.[hc]
  3. parse.[hc]
  4. sqlite3.h
adding them to the source tree.

To re-generate them (p.p. 1-3) one must pass
-DSQL_MAINTAINER_MODE=ON option to cmake. Files will be
copied to source tree automatically iif actual difference will
be detected.

As far we don't need such platform variety - remove sqlite3.h
re-generation at all.
Remove TCL script responsible for generation and template header
as well.

Compilation of auxilary SQL tools was also moved under this option:
  1. Lemon parser
  2. mkkeywordhash
since they redundant in non-maintainer mode.

Finally it removes dependency on TCL from all Tarantool package
variants.

Remove sqliteConfig.h, we don't use it.

SQLite uses TCL shell to generate common headers.
Add dependency in Travis to TCL shell for linux targets.
OSX comes with TCL pre-installed - no need to add dependency.

	* .travis.mk (deps_linux): Add tcl.

sql: Add dependency to TCL in packages.

As far as SQLite sources depend on TCLsh we need to
add dependency to TCL in package info.

	* debian/control: Add dependency on TCL.
	* rpm/tarantool.spec: Ditto.
	* snapcraft.yaml: Ditto.

sql: Avoid multiline string to satisfy older cmake

RHEL uses some old cmake which doesn't work with long string
which span over few lines w/ '\' terminator. Make it single line.

	* src/box/CMakeLists.txt (set_source_files_properties): Use
	single line instead of vreaks w/ '\'.

See #1927

Follow up previous commit

* Bug#842086: tarantool-dev: removal of tarantool-dev makes files disappear
  from tarantool-lts-dev
* Bug#842073: tarantool-common: unowned symlink after purge
* Lintian warning about debian/compact version

Use strong dependency on `netbase` for Debian and weak dependencies on
/etc/protocols and /etc/services files for RPM.

Thanks to Ivan Kosenko

Closes #1794