Closed Bug 428414 Opened 17 years ago Closed 17 years ago

Need to contact UoW to include CGI for Perl 5.10

Categories

(Bugzilla :: Installation & Upgrading, defect)

3.1.3
defect
Not set
major

Tracking

()

VERIFIED FIXED
Bugzilla 3.0

People

(Reporter: Wurblzap, Unassigned)

Details

This is a regression of bug 416382, which for good reasons, made us require CGI 3.33. Neither ActiveState's PPM repository nor the one of the University of Winnipeg we recommend via Bugzilla/Install/Requirements.pm offers this version of CGI, though. What can be done about this? Perhaps one of the following: - blacklist Perl 5.10, at least on Windows - require another repository (Frédéric pointed me to one offering CGI 3.33) - Other ideas?
Flags: blocking3.2?
It's very easy to contact the UWinnipeg maintainer and ask him to provide that version of CGI.pm.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
If the UWinnipeg guy doesn't respond, this would be a blocker and we could re-open it and figure out what to do. It affects 3.0 users just as much, though.
Flags: blocking3.2?
Reopening in order to track this. I don't understand why this isn't a blocker *now*, and simply has the potential to get resolved quickly and before the last of the currently existing blockers gets resolved. Frédéric, Max mentioned that you contacted UoW already?
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Summary: ActivePerl 5.10 users are effectively locked out → Need to contact UoW to include CGI
Sure, I'd agree that we should fix this before 3.2.
Flags: blocking3.2+
Summary: Need to contact UoW to include CGI → Need to contact UoW to include CGI for Perl 5.10
This is going to be a problem for 3.0.4 too. (In reply to comment #3) > Frédéric, Max mentioned that you contacted UoW already? Yes, I did it today.
Status: REOPENED → NEW
Flags: blocking3.0.4+
Keywords: regression
OS: Windows XP → All
Target Milestone: Bugzilla 3.2 → Bugzilla 3.0
CGI.pm 3.34 is now available at http://cpan.uwinnipeg.ca/PPMPackages/10xx/.
Status: NEW → RESOLVED
Closed: 17 years ago17 years ago
Resolution: --- → FIXED
Followed up in bug 428569.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.