Closed Bug 69746 Opened 24 years ago Closed 19 years ago

Should fail in a more friendly manner if wrong server group set.

Categories

(Bugzilla :: Installation & Upgrading, defect, P3)

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: CodeMachine, Assigned: zach)

Details

I didn't remember to update the web server group on local config and checksetup.pl complained. An informative error message would be nice. Checking user setup ... Use of uninitialized value in chown at ./checksetup.pl line 529 (#1) (W uninitialized) An undefined value was used as if it were already defined. It was interpreted as a "" or a 0, but maybe it was a mistake. To suppress this warning assign a defined value to your variables.
Target Milestone: --- → Bugzilla 2.16
Priority: -- → P3
->New (old by now?) product Bugzilla
Assignee: tara → zach
Component: Bugzilla → Installation
Product: Webtools → Bugzilla
Version: other → unspecified
Status: NEW → ASSIGNED
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
These unloved bugs have been sitting untouched since June 2002 or longer. If nobody does anything else to them, they certainly won't make 2.18 Retargetting to 2.20. If you really plan to push them right now, you might pull them back in.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
This bug has not been touched by its owner in over six months, even though it is targeted to 2.20, for which the freeze is 10 days away. Unsetting the target milestone, on the assumption that nobody is actually working on it or has any plans to soon. If you are the owner, and you plan to work on the bug, please give it a real target milestone. If you are the owner, and you do *not* plan to work on it, please reassign it to nobody@bugzilla.org or a .bugs component owner. If you are *anybody*, and you get this comment, and *you* plan to work on the bug, please reassign it to yourself if you have the ability.
Target Milestone: Bugzilla 2.20 → ---
mkanat, is this bug still valid?? I don't think so.
Yeah, we must have fixed this some time ago. checksetup now goes: no such group: apacheoo at ./checksetup.pl line 783.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.