Closed Bug 843291 Opened 13 years ago Closed 11 years ago

"Use of uninitialized value in string eq at Bugzilla/BugUrl/Bugzilla/Local.pm" warning during a 4.0 to 4.2 upgrade

Categories

(Bugzilla :: Installation & Upgrading, defect)

defect
Not set
minor

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: gerv, Unassigned)

Details

I just pulled the bmo-4.2 repo, pointed it at a clone of a bmo-4.0 database, and ran checksetup. I got: Use of uninitialized value in string eq at Bugzilla/BugUrl/Bugzilla/Local.pm line 64. 887 times. 887 is the number of rows in the bug_see_also table. The URLs in the table are all of this form: http://localhost/src/bugzilla-3.4/show_bug.cgi?id=1 This only happened on the first run of checksetup.pl, between the lines: Adding new column 'class' to the 'bug_see_also' table... and Updating column bug_file_loc in table bugs ... If nothing else, I think this probably points up the need for some better error handling in that class... (Feel free to punt this over if it's not bmo-specific.) Gerv
these are warnings, not errors, and are probably harmless > http://localhost/src/bugzilla-3.4/show_bug.cgi?id=1 that url doesn't generate a warning for me. i don't see any warnings when upgrading bmo-4.0 to 4.2, so it's possible this is triggered by an older URI module version (i have v1.60). either way, this isn't a bmo specific customisation, shifting upstream.
Assignee: nobody → installation
Component: General → Installation & Upgrading
Product: bugzilla.mozilla.org → Bugzilla
QA Contact: default-qa
Summary: Errors in 4.2 repo when running checksetup.pl → Warnings in 4.2 repo when running checksetup.pl
Version: Production → 4.0.9
Summary: Warnings in 4.2 repo when running checksetup.pl → "Use of uninitialized value in string eq at Bugzilla/BugUrl/Bugzilla/Local.pm" warning during a 4.0 to 4.2 upgrade
Severity: normal → minor
Version: 4.0.9 → 4.2
I don't remember having seen this problem either. Reopen if you can reproduce.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.