Description of problem: the command line tool "urifind" fails with: bash: /bin/urifind: /usr/local/bin/perl: bad interpreter: No such file or directory I put a symlink where it's looking and it seems to run now. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. invoke urifind at the command line. e.g "urifind -h"
CC'ing registered maintainer, assigning to Perl maintainers
Assignee: bugsquad => perlCC: (none) => marja11, shlomif
Should be fixed in perl-URI-Find-20140709.0.0-6.1.mga6 in core/updates_testing. Please test.
Assignee: perl => qa-bugs
MGA6-64 Plasma on Lenovo B50 No installation issues. At CLI: $ urifind -h urifind - find URIs in a document and dump them to STDOUT. urifind [OPTIONS] file1 [file2[, file3[, ...]]] Options: -s Sort results. -r Reverse sort results (implies -s). -u Return unique results only. -n Don't include filename in output. -p Include filename in output (0 by default, but 1 if multiple files are included on the command line). -P $re Print only lines matching regex '$re' (may be specified multiple times). -S $scheme Only this scheme (may be specified multiple times). -h This help screen. -v Display version and exit. -d Dump compiled regexes and continue. -D Dump compiled regexes and exit. $ urifind -v urifind v.20140709.00 $ cd Documenten/ this contains an old webkit trace file $ urifind -s * Use of uninitialized value in substitution (s///) at /usr/lib/perl5/vendor_perl/5.22.3/URI/Find.pm line 137. webkit2.txt: file:///home/tester6/Documenten webkit2.txt: file:///home/tester6/Documenten webkit2.txt: http://ww webkit2.txt: http://ww webkit2.txt: http://ww webkit2.txt: http://www.w3.org/20 webkit2.txt: http://www.w3.org/20 webkit2.txt: http://www.w3.org/20 webkit2.txt: http://www.w3.org/20 and a lot more. So seems OK.
CC: (none) => herman.viaeneWhiteboard: (none) => MGA6-64-OK
Good enough for me. Validating.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
CC: (none) => tmbKeywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2018-0162.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED