Bug#1033835: polyml: autopkgtest regression: output on stderr

Nilesh Patra nilesh at riseup.net
Sun May 14 15:05:21 BST 2023


Hi Jessica,

On Sun, 2 Apr 2023 15:22:49 +0200 Paul Gevers <elbrus at debian.org> wrote:
> Source: polyml
> Version: 5.7.1-5
> Control: found -1 5.7.1-4
> Severity: serious
> Your package has an autopkgtest, great. However, it fails since July 
> 2020. Can you please investigate the situation and fix it? I copied some 

Looks like polyml is failing its autopkgtest. As the release happens is 
happening soon, would you consider to take a quick look at this?

> autopkgtest [19:23:44]: test upstream-polyc: [-----------------------
> /usr/bin/ld: warning: /tmp/polyobj.2070.o: missing .note.GNU-stack 
> section implies executable stack
> /usr/bin/ld: NOTE: This behaviour is deprecated and will be removed in a 
> future version of the linker
> Test035.ML => Passed
> Test162.ML => Passed
> 
> [...]
> 
> Test026.ML => Passed
> autopkgtest [19:24:05]: test upstream-polyc: -----------------------]
> autopkgtest [19:24:05]: test upstream-polyc:  - - - - - - - - - - 
> results - - - - - - - - - -
> upstream-polyc       FAIL stderr: /usr/bin/ld: warning: 
> /tmp/polyobj.2070.o: missing .note.GNU-stack section implies executable 
> stack

Thanks
Nilesh



More information about the debian-science-maintainers mailing list