Closed Bug 265957 Opened 20 years ago Closed 20 years ago

Can't locate Token.pm in @INC after upgrading to 2.16.7

Categories

(Bugzilla :: Installation & Upgrading, defect)

2.16.7
x86
Linux
defect
Not set
trivial

Tracking

()

RESOLVED INVALID

People

(Reporter: brockett, Assigned: zach)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

After upgrading to 2.16.7 I recieve this error:

Can't locate Token.pm in @INC (@INC contains: .
/usr/lib/perl5/5.8.0/i386-linux-thread-multi /usr/lib/perl5/5.8.0
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl) at CGI.pl line 611.
BEGIN failed--compilation aborted at CGI.pl line 611.

I know that Token.pm exists in the bugzilla installation directory, but bugzilla
isn't looking in that directory for this module. I have seen this issue
addressed in other versions, but not 2.16.7.

Reproducible: Always
Steps to Reproduce:
1. upgrade from 2.16.6 to 2.16.7 using the patch
2. go to login page
3.

Actual Results:  
The error above.

Expected Results:  
The login page should be displayed.
submit bug page for bugzilla doesn't allow you to specify the version number. I
added it so searching would be easier.
Version: unspecified → 2.16.7
Did you run checksetup.pl after applying the patch?
That fixed the problem. I've never run that after upgrading before.  Sorry about
that.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
we didn't change anything in Bugzilla to fix this, just fixing the status for
accurate records...
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → INVALID
Severity: critical → trivial
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.