Bug 716162

Summary:	app-portage/genlop-0.30.10-r2: executing genlop without parameters produces bad error message
Product:	Portage Development	Reporter:	Johannes Willem (Hans) Fernhout <hfern>
Component:	Tools	Assignee:	Portage Tools Team <tools-portage>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	hfern, jstein
Priority:	Normal	Keywords:	PATCH
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	Patch to avoid the use of a not initialized variable $logfiles[0] in the help message

Description Johannes Willem (Hans) Fernhout 2020-04-04 11:08:52 UTC

If genlop is executed without parameters it gives a weird and unnecessary error message "Use of uninitialized value in concatenation (.) or string at /usr/bin/genlop line 354."

Reproducible: Always

Steps to Reproduce:
# genlop
Use of uninitialized value in concatenation (.) or string at /usr/bin/genlop line 354.
Usage: genlop  [options] [-f logfile] [category/package]

Options:

  -c  display the currently compiling packages (if any)
Actual Results:  
Use of uninitialized value in concatenation (.) or string at /usr/bin/genlop line 354.
Usage: genlop  [options] [-f logfile] [category/package]

Options:

  -c  display the currently compiling packages (if any)
(and more options)

Expected Results:  
Usage: genlop  [options] [-f logfile] [category/package]

Options:

  -c  display the currently compiling packages (if any)

Alternatively maybe the default parameter should be -c or --current because that might be the most common use.

Comment 1 Johannes Willem (Hans) Fernhout 2020-05-31 11:50:49 UTC

Created attachment 642874 [details, diff]
Patch to avoid the use of a not initialized variable $logfiles[0] in the help message

Comment 2 Sam James archtester

2023-07-18 22:00:59 UTC


*** This bug has been marked as a duplicate of bug 447436 ***