> @OpenSides.be: from IRC I learned, that you see failing unit tests
> without the first patch applied. But what else?
Our software crash immediatly after login, no page can be loaded because our
main template contains comparisons with 0 in some places.
Côme
signature.asc
Description: This
Control: reassing -1 smarty-lexer
Control: severity -1 grave
Control: tag -1 patch
Justification: Breaks various page renderings in FusionDirectory and GOsa
Hi,
On Mo 06 Feb 2017 15:47:53 CET, come wrote:
Package: smarty3
Version: 3.1.31+20161214.1.c7d42e4+selfpack1-1
Followup-For: Bug
Package: smarty3
Version: 3.1.31+20161214.1.c7d42e4+selfpack1-1
Followup-For: Bug #847571
Dear Maintainer,
The bug still exists with 3.1.31.
I can reproduce the same error with the test example given by mike_w
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500,
Hi Mike W.,
I just uploaded smarty 3.1.31 to unstable. Should be available within
the next 24h.
[...]
After substituting function yylex3 in installed file with that from
github test script compiles and correctly returns
1
3.1.30
Could you check if this issue still exists with
Hi Mike,
my question... see at the bottom...
On Fr 09 Dez 2016 16:08:10 CET, mike_w wrote:
Package: smarty3
Version: 3.1.30-1
Severity: important
After upgrade to 3.1.30 on Debian testing some templates failed to
compile with the fatal error
[:error] [pid 1203] [client 127.0.0.1:35140]
Package: smarty3
Version: 3.1.30-1
Severity: important
After upgrade to 3.1.30 on Debian testing some templates failed to compile with
the fatal error
[:error] [pid 1203] [client 127.0.0.1:35140] PHP Fatal error: Uncaught
Exception: Error: lexing failed because a rule matched an empty string.
6 matches
Mail list logo