Bug 7423

Summary:	2: Numerous perl bugs when launching mcc
Product:	Mageia	Reporter:	Bit Twister <bittwister2>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal
Version:	2
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
See Also:	https://bugs.mageia.org/show_bug.cgi?id=7428
Whiteboard:
Source RPM:	drakxtools-14.22.2-1.1.mga2.src.rpm	CVE:
Status comment:
Attachments:	mcc bug text

Description Bit Twister 2012-09-09 23:25:23 CEST

Description of problem:
Numerous perl bugs when launching mcc. See bug.txt attachment

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. click up a terminal
2. su - root
3. mcc

Comment 1 Bit Twister 2012-09-09 23:26:36 CEST

Created attachment 2778 [details]
mcc bug text

Manuel Hiebel 2012-09-11 10:19:03 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=7428
Assignee: bugsquad => thierry.vignaud

Comment 2 Thierry Vignaud 2012-09-11 11:11:50 CEST

Those are not errors but regular warnings.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 3 Bit Twister 2012-09-11 13:57:04 CEST

I feel sorry for the QA people and any other programmers who have to lose time scanning that output looking for new bugs. :(

I really wish I was a competent Perl coder so I could help. 
I would guess it would take about 20 minutes to clear up those messages.

Comment 4 Thierry Vignaud 2012-09-11 16:47:45 CEST

A "use diagnostics" or "use warning" must have remain somewhere...

Comment 5 Bit Twister 2012-09-11 17:53:18 CEST

What little Perl programming I do has made fixing problem faster with Perl telling me about wrong types and whatnot.

I just went to check my memory in harddrake2 where it does not show up. :(
I saw 
Use of uninitialized value in pattern match (m//) at
        /usr/lib/libDrakX/harddrake/data.pm line 25 (#4)
Use of uninitialized value in concatenation (.) or string at
        /usr/sbin/harddrake2 line 437 (#4)

Argument "0x1d6b" isn't numeric in numeric eq (==) at
        /usr/lib/libDrakX/detect_devices.pm line 124 (#6)
    (W numeric) The indicated string was fed as an argument to an operator
    that expected a numeric value instead.  If you're fortunate the message
    will identify which operator was so unfortunate.
    
Guessing some of that clean up would fix bug 5810