Error message not suggesting solution

RESOLVED FIXED in Bugzilla 2.18

Status

()

Bugzilla
Installation & Upgrading
RESOLVED FIXED
14 years ago
5 years ago

People

(Reporter: Vlad Dascalu, Assigned: Vlad Dascalu)

Tracking

unspecified
Bugzilla 2.18
Bug Flags:
approval +

Details

Attachments

(1 attachment)

(Assignee)

Description

14 years ago
Some people use the CVS version, and usually do a "cvs upgrade" from time to time.

However, a new param is also added in the CVS from time to time, and this causes
an error message if checksetup.pl is not launched after every cvs upgrade.

Unfortunately, the error message doesn't hint the user with the solution (re-run
checksetup.pl) in case new params get added.
(Assignee)

Comment 1

14 years ago
Created attachment 140077 [details] [diff] [review]
Patch version 1
Assignee: zach → vlad987
Status: NEW → ASSIGNED
(Assignee)

Updated

14 years ago
Attachment #140077 - Flags: review?(kiko)
(Assignee)

Comment 2

14 years ago
Kiko, any chance to take a look at this? Every day that goes by with a "r?"
request pending results in a murdered kitten ;-)
(Assignee)

Comment 3

14 years ago
Ok, just read about the Consave thing, so I think murdering kittens will be
delayed with a few hours to give you time to get up to speed. :-)

Comment 4

14 years ago
Comment on attachment 140077 [details] [diff] [review]
Patch version 1

Sorry this took so long.

Add a period to the phrase before checking in, ok?
Attachment #140077 - Flags: review?(kiko) → review+
(Assignee)

Comment 5

14 years ago
>> Add a period to the phrase before checking in, ok?

Sure thing. Thanks!
Flags: approval?
Flags: approval? → approval+
(Assignee)

Comment 6

14 years ago
While investigating, I found out that die usually adds the line number on which
the error occured.

So without the dot it looks something like:

>> No value for param $param (try running checksetup.pl again) at line 34343

and with the dot it looks something like:

>> No value for param $param (try running checksetup.pl again). at line 34343

Talked with justdave about it and he said that no dot is better.

Too bad we can't add a dot at the end of the error message ;-)
(Assignee)

Comment 7

14 years ago
Checking in Bugzilla/Config.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/Config.pm,v  <--  Config.pm
new revision: 1.19; previous revision: 1.18
done
Status: ASSIGNED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → Bugzilla 2.18
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.