Hi,
On Tue, Jun 04, 2019 at 10:09:29AM -1000, David Prévot wrote:
> Hi,
>
> Le 04/06/2019 à 09:56, Paul Gevers a écrit :
>
> > Normally I copy some of the output at the bottom of this report, but in
> > this case I couldn't spot the real failure
>
> Here it is (the trick is to grep for the “KO” string).
>
> > Testing src/Symfony/Component/Validator
> >
> > […]
> >
> > There were 2 errors:
> >
> > 1)
> > Symfony\Component\Validator\Tests\Constraints\EmailValidatorTest::testStrictWithInvalidEmails
> > with data set #26 ('�@iana.org')
> > Invalid argument supplied for foreach()
> >
> > /usr/share/php/Doctrine/Common/Lexer/AbstractLexer.php:261
> > /usr/share/php/Doctrine/Common/Lexer/AbstractLexer.php:96
> > /usr/share/php/Egulias/EmailValidator/EmailParser.php:41
> > /usr/share/php/Egulias/EmailValidator/Validation/RFCValidation.php:30
> > /usr/share/php/Egulias/EmailValidator/Validation/NoRFCWarningsValidation.php:21
> > /usr/share/php/Egulias/EmailValidator/EmailValidator.php:37
> > /usr/share/php/Symfony/Component/Validator/Constraints/EmailValidator.php:66
> > /tmp/autopkgtest-lxc.ass2zlnj/downtmp/build.22F/src/src/Symfony/Component/Validator/Tests/Constraints/EmailValidatorTest.php:116
> >
> > 2)
> > Symfony\Component\Validator\Tests\Constraints\EmailValidatorTest::testStrictWithInvalidEmails
> > with data set #27 ('test@�.org')
> > Invalid argument supplied for foreach()
> >
> > /usr/share/php/Doctrine/Common/Lexer/AbstractLexer.php:261
> > /usr/share/php/Doctrine/Common/Lexer/AbstractLexer.php:96
> > /usr/share/php/Egulias/EmailValidator/EmailParser.php:41
> > /usr/share/php/Egulias/EmailValidator/Validation/RFCValidation.php:30
> > /usr/share/php/Egulias/EmailValidator/Validation/NoRFCWarningsValidation.php:21
> > /usr/share/php/Egulias/EmailValidator/EmailValidator.php:37
> > /usr/share/php/Symfony/Component/Validator/Constraints/EmailValidator.php:66
> > /tmp/autopkgtest-lxc.ass2zlnj/downtmp/build.22F/src/src/Symfony/Component/Validator/Tests/Constraints/EmailValidatorTest.php:116
Any news here? If that's a non issue, and still be accepted by the
release team, allowing to unblock the php7.3 package for buster would
from security team point of view prefered, as we will need to follow
upstream 7.3 releases for buster-security at some point.
Regards,
Salvatore
