Closed
Bug 270404
Opened 20 years ago
Closed 20 years ago
sendbugmail.pl doesn't work
Categories
(Bugzilla :: Email Notifications, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.18
People
(Reporter: nb+bz, Assigned: nb+bz)
Details
Attachments
(2 files)
|
3.00 KB,
text/plain
|
Details | |
|
583 bytes,
patch
|
justdave
:
review+
|
Details | Diff | Splinter Review |
the contrib/sendbugmail.pl script which we added to fix bug 239343 is a little
broken, at least with the version of Perl I have installed here.
1. It puts .. on PERL's @INC path, but that doesn't actually work. If I invoke
from the contrib directory then it can't find some stuff:
$ perl -T sendbugmail.pl 1 rb@ravenbrook.com
No value for param loginmethod (try running checksetup.pl again) at
../Bugzilla/Config.pm line 161.
BEGIN failed--compilation aborted at ../Bugzilla/Auth.pm line 42.
Compilation failed in require at ../Bugzilla.pm line 27.
BEGIN failed--compilation aborted at ../Bugzilla.pm line 27.
Compilation failed in require at ../globals.pl line 1667.
BEGIN failed--compilation aborted at ../globals.pl line 1667.
Compilation failed in require at sendbugmail.pl line 19.
$
and if I invoke from the main directory then it can't find anything:
perl -T contrib/sendbugmail.pl 1 rb@ravenbrook.com
Can't locate Bugzilla/BugMail.pm in @INC (@INC contains: ..
/usr/local/lib/perl5/site_perl/5.6.1/mach /usr/local/lib/perl5/site_perl/5.6.1
/usr/local/lib/perl5/site_perl/5.005/i386-freebsd
/usr/local/lib/perl5/site_perl/5.005 /usr/local/lib/perl5/site_perl
/usr/local/lib/perl5/5.6.1/BSDPAN /usr/local/lib/perl5/5.6.1/mach
/usr/local/lib/perl5/5.6.1) at ./contrib/sendbugmail.pl line 20.
BEGIN failed--compilation aborted at ./contrib/sendbugmail.pl line 20.
$
2. In taint mode, it fails because we don't detaint the first parameter (the bug
number):
$ perl -T contrib/sendbugmail.pl 1 rb@ravenbrook.com
Insecure dependency in parameter 1 of DBI::db=HASH(0x85a664c)->prepare method
call while running with -T switch at Bugzilla/DB.pm line 60.
$
3. The usage comment at the head refers to the script as bugmail, not sendbugmail.
I have a patched version, and will attach it.
| Assignee | ||
Comment 1•20 years ago
|
||
| Assignee | ||
Comment 2•20 years ago
|
||
| Assignee | ||
Comment 3•20 years ago
|
||
The attached patch (attachment 166231 [details] [diff] [review]) simply changes the existing (2.18rc3)
contrib/sendbugmail.pl into the attached one (attachment 166230 [details]).
Updated•20 years ago
|
Flags: blocking2.20+
Flags: blocking2.18+
OS: FreeBSD → All
Target Milestone: --- → Bugzilla 2.18
Comment 4•20 years ago
|
||
Comment on attachment 166231 [details] [diff] [review]
patch to sendbugmail.pl from 2.18rc3
Looks good to me
Attachment #166231 -
Flags: review+
Updated•20 years ago
|
Flags: approval2.18+
Flags: approval+
Updated•20 years ago
|
Assignee: justdave → Nick.Barnes
| Assignee | ||
Comment 5•20 years ago
|
||
Thanks for moving so quickly on this, guys. What happens next? Does "review+"
mean that it's been reviewed and found OK? The bug is assigned to me but I
can't do anything with it because I don't have CVS write access. What's the
procedure here?
Comment 6•20 years ago
|
||
Checking in contrib/sendbugmail.pl;
/cvsroot/mozilla/webtools/bugzilla/contrib/sendbugmail.pl,v <-- sendbugmail.pl
new revision: 1.2; previous revision: 1.1
done
Checking in contrib/sendbugmail.pl;
/cvsroot/mozilla/webtools/bugzilla/contrib/sendbugmail.pl,v <-- sendbugmail.pl
new revision: 1.1.2.1; previous revision: 1.1
done
(In reply to comment #5)
> Thanks for moving so quickly on this, guys. What happens next? Does "review+"
> mean that it's been reviewed and found OK? The bug is assigned to me but I
> can't do anything with it because I don't have CVS write access. What's the
> procedure here?
If you don't have CVS write access someone will check it in for you :) (like me,
for example - I have a query that returns pending bugs that are approved but
still opened, and I commit those to CVS if the name of the assignee doesn't
indicate a person with CVS write access)
Review+ means that the code was reviewed and found ok. To be checked in, the
patch needs approval from justdave or myk, which means one of those two gave
their "stamp" for code integration with the rest of the code-base.
Status: NEW → RESOLVED
Closed: 20 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
•