Open
Bug 77896
Opened 23 years ago
Updated 11 years ago
Prompt for DB connection info when creating localconfig.
Categories
(Bugzilla :: Installation & Upgrading, enhancement, P3)
Tracking
()
NEW
People
(Reporter: CodeMachine, Unassigned)
References
(Depends on 1 open bug)
Details
(Whiteboard: [blocker will fix])
Given we should probably move towards a scenario where MySQL has a password, when creating localconfig in checksetup.pl. This allows us to easily recommend a MySQL password and explain the consequences of not doing so, informing the administrator of this issue. It's probably useful to ask pertinent information like all the database connection info and the web server group.
Reporter | ||
Updated•23 years ago
|
Target Milestone: --- → Bugzilla 2.16
Reporter | ||
Updated•23 years ago
|
Priority: -- → P3
Comment 1•23 years ago
|
||
-> Bugzilla product, Installation component, reassigning.
Assignee: tara → zach
Component: Bugzilla → Installation
Product: Webtools → Bugzilla
Version: Bugzilla 2.11 → 2.11
Updated•23 years ago
|
Status: NEW → ASSIGNED
Comment 2•23 years ago
|
||
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
Comment 3•20 years ago
|
||
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
Updated•20 years ago
|
Severity: normal → enhancement
Comment 4•19 years ago
|
||
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 → ---
Updated•18 years ago
|
QA Contact: mattyt-bugzilla → default-qa
Comment 5•18 years ago
|
||
*** Bug 262085 has been marked as a duplicate of this bug. ***
Updated•14 years ago
|
Assignee: zach → installation
Status: ASSIGNED → NEW
Updated•11 years ago
|
Whiteboard: [blocker will fix]
You need to log in
before you can comment on or make changes to this bug.
Description
•