New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
needsrestart perl warnings under perl 5.20 #6
Comments
some external module versions: perl-Module-Find-0.12-1.noarch |
Hi, perl 5.20 should work - running needrestart on Debian jessie (perl 5.20.2) is not that noisy. # needrestart -h
Ran into unknown state (hex char: 29) at /usr/share/perl5/vendor_perl/NeedRestart/Utils.pm line 47.
Ran into unknown state (hex char: 29) at /usr/share/perl5/vendor_perl/NeedRestart/Utils.pm line 47.
Ran into unknown state (hex char: 29) at /usr/share/perl5/vendor_perl/NeedRestart/Utils.pm line 47. It seems to be triggered by a bug in Proc::ProcessTable. It was fixed some time ago: jwbargsten/perl-proc-processtable@c4d07f8
Which version of needrestart did you try (git HEAD / github release)? Btw: only longopts --help/--version is supported.
The warning during kernel probing seems to be triggered by a dangling symlink (/boot/vmlinuz.old), isn't it? |
for perl-proc-processtable@c4d07f8 maybe you bump your i am using 2.0 release tarball from github yes, both for short |
now with 601ab27:
|
Thanks for giving 601ab27 a try. The warning in line 305 is related to jwbargsten/perl-proc-processtable@c4d07f8. Using the Ignoring unknown argv parameters is required while using the debconf frontend on Debian GNU/Linux systems. |
Do you know what is the version that is required for the Proc::ProcessTable bug to disappear? for the sake when somebody else gets this error and reaches this ticket. |
fixes '[' or ']' in ps listing liske/needrestart#6 (comment)
Seems to be fixed in Proc::ProcessTable 0.49+ (jwbargsten/perl-proc-processtable@1dc2ddc) |
it prints too many notices here and there....
tried to see what options it supports:
tried to see what is it's version:
so the actual run:
let me know if you need more info!
The text was updated successfully, but these errors were encountered: