On 05/11/2018 16:40, Roberto C. Sánchez wrote: > On Mon, Nov 05, 2018 at 04:22:46PM +0100, Emilio Pozuelo Monfort wrote: >> On 05/11/2018 15:58, Roberto C. Sánchez wrote: >>> Just a few minutes ago I uploaded a mysql-5.5 package to >>> jessie-security. I was monitoring the buildd logs [0] and was surprised >>> to see that the build on armel failed after just 4 minutes. The source >>> of the error is not immediately apparent to me, but I think I can work >>> on figuring that out later. >> >> Hmm, I don't see any clear error there. I have retried the build, let's see >> if >> it works now or if it still fails in this (obscure) way. >> > OK. Thanks for taking a look. I am curious to know the outcome of your > build attempt. > >>> The reason for my question is that since the package I uploaded included >>> an amd64 package and the builds on i386 and armhf appear to be >>> proceeding nominally, should I publish the DLA now even with the build >>> on armel broken, or should I wait until I can fix that build? If the >>> former, would I add a note to the DLA indicating the missing build on >>> armel and then later follow up with a -2 advisory once the package is >>> available on armel? >> >> If you don't expect to fix the problem quickly, I think an advisory now, >> followed up by a newer one once the problem is fixed would be appropriate. >> > > That is generally what I was thinking, but I wanted a second opinion. > Thanks for confirming. > > I have the advisory ready to send, but I have had to turn my attention > elsewhere for the moment. > > If you could let me know the outcome of your build attempt then I can > make any required adjustment to the advisory text and send it. If the > build is still failing, any additional investigation can be handled > afterward.
I retried it on the buildds, you can follow up here: https://buildd.debian.org/status/package.php?p=mysql-5.5&suite=jessie-security Cheers, Emilio
