Please review latest commits at https://salsa.debian.org/mariadb-team/mariadb-server/-/commits/ubuntu/23.10-mantic
Based on the autopkgtest url you shared the failure was in ubuntu-security-proposed-ppa. Does re-uploads there require a new changelog entry? Shall I bump it to 1:10.11.6-*1*ubuntu0.23.10.1?
## Details
I figured out how to trigger Ubuntu autopkgtests on Launchpad like you hade done after reading https://wiki.ubuntu.com/ProposedMigration.
I reproduced failing baseline in https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-mysql-ubuntu-mariadb-10.11/mantic/amd64/m/mariadb/20240121_040149_a9319@/log.gz and after my changes it now fully passed in https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-mysql-ubuntu-mariadb-10.11/mantic/amd64/m/mariadb/20240121_065525_cdd96@/log.gz. Since the `main.subselect_*` reproduced on Launchpad autopkgtests I cherry-picked that fix from Debian as well.
As a note to myself, this are to commands to run after the PPA upload at https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all has passed successfully:
``` VERSION_RAW="1:10.11.6-0ubuntu0.23.10.1~bpo23.10.1~1705810339.ca4c2a8b0b0+ubuntu.23.10.mantic" VERSION="$(echo "$VERSION_RAW" | sed 's/+/%2B/g')" echo $VERSION
PPA=mariadb-10.11 SRCPKG=mariadb RELEASE=mantic ARCH=amd64 LPUSER=mysql-ubuntu
browse "https://autopkgtest.ubuntu.com/request.cgi?release=$RELEASE&arch=$ARCH&package=$SRCPKG&ppa=$LPUSER/$PPA&trigger=$SRCPKG/$VERSION"
browse "https://autopkgtest.ubuntu.com/running#pkg-mariadb"
browse "https://autopkgtest.ubuntu.com/results/autopkgtest-$RELEASE-$LPUSER-$PPA/" ```
## Side note on CI health
I checked https://autopkgtest.ubuntu.com/packages/mariadb. The noble CI is failing on Perl migration related issues that are not due to MariaDB. The i386 job that is failing on all platforms is explained in https://bugs.launchpad.net/auto-package-testing/+bug/2021925 (with no replies since May).
Please review latest commits at https:/ /salsa. debian. org/mariadb- team/mariadb- server/ -/commits/ ubuntu/ 23.10-mantic
Based on the autopkgtest url you shared the failure was in ubuntu- security- proposed- ppa. Does re-uploads there require a new changelog entry? Shall I bump it to 1:10.11. 6-*1*ubuntu0. 23.10.1?
## Details
I figured out how to trigger Ubuntu autopkgtests on Launchpad like you hade done after reading https:/ /wiki.ubuntu. com/ProposedMig ration.
I reproduced failing baseline in https:/ /autopkgtest. ubuntu. com/results/ autopkgtest- mantic- mysql-ubuntu- mariadb- 10.11/mantic/ amd64/m/ mariadb/ 20240121_ 040149_ a9319@/ log.gz and after my changes it now fully passed in https:/ /autopkgtest. ubuntu. com/results/ autopkgtest- mantic- mysql-ubuntu- mariadb- 10.11/mantic/ amd64/m/ mariadb/ 20240121_ 065525_ cdd96@/ log.gz. Since the `main.subselect_*` reproduced on Launchpad autopkgtests I cherry-picked that fix from Debian as well.
As a note to myself, this are to commands to run after the PPA upload at https:/ /launchpad. net/~mysql- ubuntu/ +archive/ ubuntu/ mariadb- 10.11/+ builds? build_text= &build_ state=all has passed successfully:
``` RAW="1: 10.11.6- 0ubuntu0. 23.10.1~ bpo23.10. 1~1705810339. ca4c2a8b0b0+ ubuntu. 23.10.mantic"
VERSION_
VERSION="$(echo "$VERSION_RAW" | sed 's/+/%2B/g')"
echo $VERSION
PPA=mariadb-10.11
SRCPKG=mariadb
RELEASE=mantic
ARCH=amd64
LPUSER=mysql-ubuntu
browse "https:/ /autopkgtest. ubuntu. com/request. cgi?release= $RELEASE& arch=$ARCH& package= $SRCPKG& ppa=$LPUSER/ $PPA&trigger= $SRCPKG/ $VERSION"
browse "https:/ /autopkgtest. ubuntu. com/running# pkg-mariadb"
browse "https:/ /autopkgtest. ubuntu. com/results/ autopkgtest- $RELEASE- $LPUSER- $PPA/"
```
## Side note on CI health
I checked https:/ /autopkgtest. ubuntu. com/packages/ mariadb. The noble CI is failing on Perl migration related issues that are not due to MariaDB. The i386 job that is failing on all platforms is explained in https:/ /bugs.launchpad .net/auto- package- testing/ +bug/2021925 (with no replies since May).