Debian/stretch (v9) is also EOL, so also get rid of it, and
while at it also get rid of further leftovers from buster and
even older Debian releases.
We support Debian bullseye and newer for now.
* use build profile on distributions that doesn't have libbcg729-dev
available
* libbcg729-dev is available since bullseye and jammy
Change-Id: Ia9037082b6a39c60a6beb5ebec52d6c64d4e29d1
* refresh Ubuntu keyring package (to support new signing key
with ID 871920D1991BC93C)
* install debootstrap from bullseye/backports + zstd on host, otherwise
bootstrapping Ubuntu 22.04/jammy fails due to lack of zstd support in
dpkg (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892664):
dpkg-deb: error: archive './/var/cache/apt/archives/base-files_12ubuntu4_amd64.deb' uses unknown compression for member 'control.tar.zst', giving up
Change-Id: I4b2f07c792a82edb44720b8d34db3fe6b06916d8
> *** Building a tagged version (mr10.2.1.1+bpo11).***
> dpkg-buildpackage: warning: debian/changelog(l1): version
> 'mr10.2.1.1+bpo11' is invalid: version number does not start with digit
> LINE: rtpengine (mr10.2.1.1+bpo11) bullseye; urgency=medium
Change-Id: Id2ab245d7ce958873d993b0b35d3144f6c9ac098
We worked on fixing our failing cowbuilder environment updates:
| E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
| E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
While taking care of this, we noticed that our Debian + Ubuntu
repository configurations aren't up2date anymore:
* Ubuntu/precise is EOL and only lives on old-releases.ubuntu.com nowadays
* Debian/bullseye is stable nowadays, accordingly enable its security repository
While at it, let's create /etc/jenkins/pbuilderrc without variable
replacements, simplifying c/p between ec2/bootstrap.sh and
pbuilder/pbuilderrc therefore.
Change-Id: Ide7f81583dc53e6947dff80b5aee17a6898bff34
https://github.com/kamailio/kamailio/issues/2160
This is happening, every nigthly build version is not greater
than the released one:
> $ dpkg --compare-versions 5.3.3+0~20200417092406.72+bionic gt 5.3.3+bionic; echo $?
> 1
When upgrading from distribution, for instance from stretch to buster,
even if you update your apt source to buster, the version from stretch
already installed is greater, so no automatic upgrade:
> $ dpkg --compare-versions 5.3.1+stretch gt 5.3.1+buster ; echo $?
> 0
* use bpo approach to set order between distributions
* remove sems since we don't build it anymore
* nightly build version on branches should start with the next one
to be released. Trying to support the UNRELEASED case too where the right
version is already in debian/changelog
for instance, if debian/changelog has 5.3.4 (released
version) on branch 5.3 for jessie:
- compare between nightly and future release:
> $ dpkg --compare-versions 5.3.4~bpo9.20200430101647.0 lt 5.3.4+bpo8; echo $?
> 0
- compare between nightly for jessie and nightly for buster:
> $ dpkg --compare-versions 5.3.4~bpo9.20200430101647.0 lt 5.3.4~bpo10.20200430101713.0; echo $?
> 0
for master, it has the next_version~dev already in the changelog:
> dpkg --compare-versions 5.4.0~dev4+bpo8.20200430102749.0 lt 5.4.0+bpo8; echo $?
> 0
Change-Id: Ie474c3c3dd543b69c034dae94e765037ba68f5eb
JFTR, with the following pbuilderrc we're able to bootstrap it:
| squeeze)
| # lacks eatmydata package, so explicitely configure it
| # nowadays also resides on archive
| MIRRORSITE="http://archive.debian.org/debian/"
| # ensure it's unset
| unset LD_PRELOAD
| # we need key id 64481591B98321F9
| DEBOOTSTRAPOPTS=("\${DEBOOTSTRAPOPTS[@]}" "--keyring=/usr/share/keyrings/debian-archive-removed-keys.gpg")
| ;;
But further configuration of the environment fails with:
| W: GPG error: http://archive.debian.org squeeze Release: The following signatures were invalid: KEYEXPIRED 1520281423 KEYEXPIRED 1501892461
Since we no longer build/support squeeze though don't put any further
effort into it.