[debian-mysql] MariaDB 10.1.38 update pending

[Salvatore Bonaccorso]

Hi Otto,

On Sun, Feb 24, 2019 at 01:24:18AM +0200, Otto Kekäläinen wrote:
> Hello!
> 
> la 23. helmikuuta 2019 klo 16.58 Moritz Muehlenhoff <jmm at inutil.org> kirjoitti:
> ..
> > > Doe to personal constraints I think I will not be able to review your
> > > changes, but here my opinion: Given the lack of information for the
> > > two CVEs we might be better of to (this time) release a DSA, and in
> > > particular include as well the changes to adress the build failures
> > > (not sure on the others, an imput from SRM if they are okay would be
> > > good I think). At least wo security updates (coturn and dovecot) were
> > > blocked on last point release to enter 9.8 because they picked up the
> > > dependency for mariadb on security, which was then not available on
> > > all previous built architectures.
> 
> Please keep in mind that for jessie-security build logs are visible at
> https://buildd.debian.org/status/package.php?p=mariadb-10.0&suite=jessie-security
> but for Stretch only the original 10.1.26 builds are visible at
> https://buildd.debian.org/status/package.php?p=mariadb-10.1&suite=stretch
> - so for the latest status of build failures I don't have a quick
> summary anywhere (unlike you security team).

Yes that is true, build logs for stretch-security, given there might
be embargoed issues, are not pulicly visible. But for the mips,
mips64el, mipsel, and s390x build fialures I did wrote on 16. Nov.
2018 a mail forwarding you the build logs
(<20181116201503.GA15949 at eldamar.local>). We then decided to still go
forward with the upload and later on integrate the fixes you found in
the nxt upload.

So all is fine on this end.

Regards,
Salvatore