Closed
Bug 177351
Opened 22 years ago
Closed 22 years ago
checksetup.pl tells about deleting templates in silent-running mode
Categories
(Bugzilla :: Installation & Upgrading, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.18
People
(Reporter: justdave, Assigned: zach)
Details
(Keywords: regression)
Attachments
(1 file)
669 bytes,
patch
|
justdave
:
review+
justdave
:
review+
|
Details | Diff | Splinter Review |
The checkin from bug 168191 has caused me to start receiving email from landfill.bugzilla.org/bugzilla-tip on an hourly basis informing me that the compiled templates are being deleted. Output from checksetup.pl which happens every time you run it no matter what is supposed to have "unless $silent" after it so it doesn't output in silent-running mode (i.e. via a cron job). The only output from checksetup.pl in silent-running mode is supposed to be things the admin needs to know about (i.e. changes to database structure, or something that requires input from the admin before it can continue).
Reporter | ||
Updated•22 years ago
|
Keywords: regression
Target Milestone: --- → Bugzilla 2.18
Comment 1•22 years ago
|
||
This whole "if $silent" thing is a nasty architecture anyway; sub sprint { if (!$silent) { print @_; } } Then s/print/sprint/ everywhere would have been a much better solution. Seperate logic from presentation :-) Anyway, I guess we're stuck with it now. I'll whip up a patch. Gerv
Comment 2•22 years ago
|
||
Yeah, that patch was written before 'silent' mode, IIRC
Comment 3•22 years ago
|
||
Simple one-line fix. Gerv
Reporter | ||
Comment 4•22 years ago
|
||
Comment on attachment 104610 [details] [diff] [review] Patch v.1 2xr= justdave
Attachment #104610 -
Flags: review+
Comment 5•22 years ago
|
||
Fixed. Checking in checksetup.pl; /cvsroot/mozilla/webtools/bugzilla/checksetup.pl,v <-- checksetup.pl new revision: 1.201; previous revision: 1.200 done Gerv
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•