[MDBF-330] aarch64-debian-sid broken Created: 2022-02-03  Updated: 2022-02-17  Resolved: 2022-02-17

Status: Closed
Project: MariaDB Foundation Development
Component/s: None
Affects Version/s: None
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Vlad Bogolin Assignee: Vlad Bogolin
Resolution: Fixed Votes: 0
Labels: aarch64, buildbot, sid
Remaining Estimate: 0d
Time Spent: 1d 1h
Original Estimate: Not Specified

Issue Links:
PartOf
is part of MDBF-41 Milestone 5: Desirable fixes Open

 Description   

Builds fail on aarch64-debian-sid since changing to the quai.io image with the following message:

dch warning: Unable to determine Debian's backport distributions.
 
dch warning: Recognised distributions are: 
experimental, unstable, testing, stable, oldstable, oldoldstable,
 
{bullseye,buster,stretch,jessie,wheezy}-proposed-updates,
 
{testing,stable,oldstable,oldoldstable}-proposed-updates,
 
{bullseye,buster,stretch,jessie,wheezy}-security,
 
{testing,stable,oldstable,oldoldstable}}-security and UNRELEASED.
 
Using your request anyway.
 
dch: error: 1:10.8.0+maria~n/a is not a valid version



 Comments   
Comment by Daniel Black [ 2022-02-11 ]

looks odd, why would sid have backports?

Comment by Faustin Lammler [ 2022-02-11 ]

I think the relevant error is:
> dch: error: 1:10.8.0+maria~n/a is not a valid version

vladbogo can you provide a bit more context.

Comment by Vlad Bogolin [ 2022-02-11 ]

So, I suspect the issues comes from:

dch warning: Unable to determine Debian's backport distributions.

faust the error you are referring to I guess is related to failing to identify the distribution. It is usually something along 

1:10.7.2+maria~sid

(note the missing sid) so this definitely explains the error.

I suspect to be a problem with the sid base image. Online I could find little references. Build wise, there isn't much going on. This is the full log

debian/autobake-deb.sh
 
 in dir /home/buildbot/aarch64-debian-sid-deb-autobake/build (timeout 1200 secs)
 
 watching logfiles {'CMakeCache.txt': './builddir/CMakeCache.txt'}
 
 argv: [b'debian/autobake-deb.sh']
 
 environment:
 
  BUILDMASTER=buildbot.mariadb.org
 
  BUILDMASTER_PORT=9992
 
  CCACHE_DIR=/mnt/ccache
 
  DEB_BUILD_OPTIONS=parallel=25
 
  HOME=/home/buildbot
 
  HOSTNAME=50ae71189bbb
 
  LC_CTYPE=C.UTF-8
 
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
 
  PWD=/home/buildbot/aarch64-debian-sid-deb-autobake/build
 
  WORKERNAME=aarch64-bbw5-docker-debian-sid
 
 using PTY: False
 
'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.install' -> 'debian/mariadb-plugin-columnstore.install'
 
'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.postinst' -> 'debian/mariadb-plugin-columnstore.postinst'
 
'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.postrm' -> 'debian/mariadb-plugin-columnstore.postrm'
 
'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.prerm' -> 'debian/mariadb-plugin-columnstore.prerm'
 
'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.triggers' -> 'debian/mariadb-plugin-columnstore.triggers'
 
Incrementing changelog and starting build scripts
 
dch warning: Unable to determine Debian's backport distributions.
 
dch warning: Recognised distributions are: 
experimental, unstable, testing, stable, oldstable, oldoldstable,
 
{bullseye,buster,stretch,jessie,wheezy}-proposed-updates,
 
{testing,stable,oldstable,oldoldstable}-proposed-updates,
 
{bullseye,buster,stretch,jessie,wheezy}-security,
 
{testing,stable,oldstable,oldoldstable}}-security and UNRELEASED.
 
Using your request anyway.
 
dch: error: 1:10.8.0+maria~n/a is not a valid version
 
libdistro-info-perl is not installed, Debian release names are not known.
 
libdistro-info-perl is not installed, Ubuntu release names are not known.
 
program finished with exit code 25
 
elapsedTime=1.025734

while a successful run looks like this:

debian/autobake-deb.sh
 
 in dir /buildbot/aarch64-debian-sid-deb-autobake/build (timeout 1200 secs)
 
 watching logfiles {'CMakeCache.txt': './builddir/CMakeCache.txt'}
 
 argv: [b'debian/autobake-deb.sh']
 
 environment:
 
  BUILDMASTER=buildbot.mariadb.org
 
  BUILDMASTER_PORT=9992
 
  CCACHE_DIR=/mnt/ccache
 
  DEB_BUILD_OPTIONS=parallel=25
 
  HOME=/home/buildbot
 
  HOSTNAME=fffc086295fe
 
  LC_CTYPE=C.UTF-8
 
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
 
  PWD=/buildbot/aarch64-debian-sid-deb-autobake/build
 
  WORKERNAME=aarch64-bbw5-docker-debian-sid
 
 using PTY: False
 
'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.install' -> 'debian/mariadb-plugin-columnstore.install'
 
'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.postinst' -> 'debian/mariadb-plugin-columnstore.postinst'
 
'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.postrm' -> 'debian/mariadb-plugin-columnstore.postrm'
 
'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.prerm' -> 'debian/mariadb-plugin-columnstore.prerm'
 
'storage/columnstore/columnstore/debian/mariadb-plugin-columnstore.triggers' -> 'debian/mariadb-plugin-columnstore.triggers'
 
Incrementing changelog and starting build scripts
 
Creating package version 1:10.7.2+maria~sid ... 
/usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead.
 
dpkg-buildpackage: info: source package mariadb-10.7
 
dpkg-buildpackage: info: source version 1:10.7.2+maria~sid
 
dpkg-buildpackage: info: source distribution sid
 
dpkg-buildpackage: info: source changed by MariaDB Developers <maria-developers@lists.launchpad.net>
 
 dpkg-source -I --before-build .
 
dpkg-buildpackage: info: host architecture arm64
 
 debian/rules clean
 
dh clean --parallel --with systemd --list-missing
 
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
 
   debian/rules override_dh_auto_clean
 
make[1]: Entering directory '/buildbot/aarch64-debian-sid-deb-autobake/build'

So, I think that autobake-deb.sh fails to identify the distribution and it fails at some point. As to why it fails, I suspect to be an error with the debian sid base image, but I am not sure if we can find any workarounds.

danblack no idea why it would look for backports. The build script only calls debian/autobake-deb.sh.

Comment by Faustin Lammler [ 2022-02-14 ]

I can't reproduce this manually neither with the quay.io nor with the debian:sid image.
Here are the hash tested:

"quay.io/mariadb-foundation/bb-worker@sha256:eeffb45d9f63050f69a2cf7872f83cd483d351b74a5848258c3e5e132d1258d6",
 
"quay.io/mariadb-foundation/bb-worker@sha256:efa9d50cb630db1c248d87d7557db3074996809c7df0e0880fff2ba6bc699eea"
 
 
 
"docker.io/library/debian@sha256:0e6e082a988ec6f880c76864c68705f47e4af4a319e0a56d5a1817282767336c",
 
"docker.io/library/debian@sha256:fef6ee5820c9d3e095f556457bc01bbb6d288a4f10fefa9f08fdd598e88f5761"

And I am trying to build 10.8 branch (commit 63b9d6e) with:

export DEB_BUILD_OPTIONS="parallel=$(($(nproc) - 2)) noautodbgsym"
 
debian/autobake-deb.sh

Comment by Vlad Bogolin [ 2022-02-14 ]

It seems that the solution was in the error message, but somehow all of use missed that:

libdistro-info-perl is not installed, Debian release names are not known.

I can confirm that installing libdistro-info-perl solves the issue for my manual run.

Comment by Faustin Lammler [ 2022-02-14 ]

Yep, should be automatically installed by the devscripts package...
Let's rebuild CI images and see

Comment by Faustin Lammler [ 2022-02-15 ]

The libdistro-info-perl package is probably not installed because we use --no-install-recommends:

apt-get -y install --no-install-recommends devscripts

vladbogo please review fix:
https://github.com/MariaDB/mariadb.org-tools/pull/106

Comment by Faustin Lammler [ 2022-02-15 ]

vladbogo the new images with the fix has been pushed to quay.io, please confirm that BB is now able to build on ARM Debian sid and close if OK.
Thanks!

Comment by Vlad Bogolin [ 2022-02-15 ]

The issue doesn't seem to be solved (https://buildbot.mariadb.org/#/builders/136/builds/3959). On a manual check, I can confirm that the issue is reproducible, but it seems that a simple 

apt-get update

solves the issue.

Comment by Faustin Lammler [ 2022-02-17 ]

Second attempt: https://github.com/MariaDB/mariadb.org-tools/pull/107

The only thing that comes to my mind if apt-get update resolves it is to not remove /var/lib/apt/lists/* in the container image...

Comment by Vlad Bogolin [ 2022-02-17 ]

Manually and other tests to try to find the problem. Thanks faust for the help

Generated at Thu Feb 08 03:37:06 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.