Bug#882909: Acknowledgement (jessie-pu: package mariab-10.1/10.0.33-1)

["Adam D. Barratt" <adam@adam-barratt.org.uk>]

Ping? (I realise it's only been a few days, but the window for 8.10 is
closing this weekend.)

On Tue, 2017-11-28 at 14:01 +0000, Adam D. Barratt wrote:
> Control: tags -1 + moreinfo
> 
> On 2017-11-27 20:05, Otto Kekäläinen wrote:
> > Attached the final debdiff (also visible at
> > https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/diff/deb
> > ian/?id2=debian/10.0.32-1&id=debian/10.0.33-0%2bdeb8u1)
> 
> That's not a debdiff, unless you're proposing that the upload
> contains 
> no actual code changes. (As a side note, the changelog doesn't
> mention 
> the change to Uploaders.)
> 
> The previous jessie upload (1.0.32, via the security archive) FTBFS
> on 
> mips, mipsel, powerpc and s390x. While the Security Team have
> decided 
> that it's an acceptable trade-off to release packages in that state,
> as 
> it means that at least some users get the update, that's not how
> things 
> work with p-u - the package will need to build without regressions 
> before it gets into jessie. As far as I can see, the relevant fixes
> are 
> already applied in unstable (to the mariadb-10.1 source package);
> it's 
> possible that they're applied in some way to 10.0.33 as well, but
> it's 
> impossible to tell from the diff that was provided. Specifically,
> the 
> mips, mipsel and powerpc issues appear to all be #864298 (also
> linked 
> from https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1698
> 689 
> , when the same issue arose in Ubuntu) and the "fix" for s390x thus
> far 
> seems to be disabling the relevant testcase.
> 
> Please provide a _full_ tested debdiff, including fixes for the
> build 
> issues if they're required with 10.0.33.
> 
> Regards,
> 
> Adam