Closed
Bug 319691
Opened 19 years ago
Closed 17 years ago
Disallow development DBD versions
Categories
(Bugzilla :: Installation & Upgrading, defect, P2)
Tracking
()
RESOLVED
FIXED
Bugzilla 3.0
People
(Reporter: mkanat, Assigned: mkanat)
Details
(Whiteboard: fixed by blocker)
Attachments
(1 file)
905 bytes,
patch
|
LpSolit
:
review-
|
Details | Diff | Splinter Review |
We have a *lot* of people run into trouble because they try to install Bugzilla using a development DBD::mysql or DBD::Pg. You can always tell a development version because it has an underscore and then a number at the end. We just need to die, if we hit a DBD::mysql or DBD::Pg like that.
Assignee | ||
Comment 1•19 years ago
|
||
OK, this should work. I haven't been able to test it, since I don't have a development DBD installed anywhere handy. However, I have tested that it doesn't break normal installs at all.
Attachment #205393 -
Flags: review?(wurblzap)
Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P2
Comment 2•19 years ago
|
||
Comment on attachment 205393 [details] [diff] [review] Disallow DBD versions with underscores >+ if ($vok and $pkg =~ /^DBD/ and $vnum =~ /_/) { >+ print " $vstr\n" >+ . " $pkg $vstr is a development version, which Bugzilla" >+ . " does not support.\n Downgrade to a version without" >+ . " an underscore (_) in the version number."; >+ return !$vok; >+ } My opinion is that we should warn the user, but not stop checksetup.pl from running. I would remove "return !$vok;" and keep the warning only. I'm not going to deny review, but it has not my vote.
Comment 3•19 years ago
|
||
(In reply to comment #2) > My opinion is that we should warn the user, but not stop checksetup.pl from > running. My suggestion would be to add the --force option to ./checksetup.pl to force him to omit this test, for those users who really want to use their dev. DBD despite the warning.
Updated•19 years ago
|
Attachment #205393 -
Flags: review?(wurblzap) → review?
Comment 4•19 years ago
|
||
I'm with Frédéric -- disallowing development DBDs could potentially break working installs all of a sudden. I'd call the parameter something less generic, though, for example --allow-development-dbd or something along these lines.
Assignee | ||
Comment 5•19 years ago
|
||
I've never seen a development DBD with a working Bugzilla, but I'll add the parameter.
Comment 6•19 years ago
|
||
Comment on attachment 205393 [details] [diff] [review] Disallow DBD versions with underscores per previous comments
Attachment #205393 -
Flags: review? → review-
Comment 7•18 years ago
|
||
2.20 and 2.22 have been released. Let's leave them alone.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.24
Assignee | ||
Comment 8•17 years ago
|
||
Fixed in bug 360710.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Whiteboard: fixed by blocker
You need to log in
before you can comment on or make changes to this bug.
Description
•