Problems upgrading from V2.22 to V3.0.3 with Perl - Mozilla
This is a discussion on Problems upgrading from V2.22 to V3.0.3 with Perl - Mozilla ; Hi there,
I am trying to upgrade from Bugzilla V2.22 to V3.0.3 (i.e. Bugzilla_Stable),
running on my Windows 2003 Advanced Server sp2 running Perl V5.8.8.
Following the Byron Jones' instructions for a Windows install, I have done
the update using ...
-
Problems upgrading from V2.22 to V3.0.3 with Perl
Hi there,
I am trying to upgrade from Bugzilla V2.22 to V3.0.3 (i.e. Bugzilla_Stable),
running on my Windows 2003 Advanced Server sp2 running Perl V5.8.8.
Following the Byron Jones' instructions for a Windows install, I have done
the update using CVS, uninstalled my prior version of ActiveState Perl and
installed V5.8.8. I have run the command 'ppm upgrade' and now run
checksetup.pl.
This is where it seems there is a problem. The output states that I need to
do the following two steps:
1>ppm repo add theory58S http://theoryx5.uwinnipeg.ca/ppms
2>ppm repo up theory58S
before continuing on to install the Email-MIME-Modifier:
3>ppm install Email-MIME-Modifier
Step #1 runs fine, however step #2 returns an error saying that there is no
know command 'up'. Step #3 doesn't work because there is no
'Email-MIME-Modifier' found.
It would seem I am not alone on the problem (check out Adrian's posts on the
newsgroup from 2007.Dec.3-4 with a reply by Max Kanat-Alexander), however no
resolution was given.
Any help would be most appreciated for the problem with step #1 or step #3
(or even Bugzilla V3.0.3 on Windows). Thanks in advance,
David
-
Re: Problems upgrading from V2.22 to V3.0.3 with Perl - Resolved
Hi all,
Just wanted to post here to say that this specific issue seems to be
resolved. This whole process of upgrading Bugzilla from V2.22 to V3.0.3 on
my Windows 2003 Adv. Server box has been a painful ordeal, and it is not
over yet. But for others that may have problems related to any of this, I
want to post the resolution.
Essentially, using the ppm GUI, Edit | Preferences | Repositories tab to see
that I had misspelt Winnipeg as Winnepeg (yes, I lose my Cdn citizenship
over this one!). Once I had deleted these misspelt repositories (press the
no-entry sign in the leftmost column) and added it properly, I could then
see the 'Email-MIME-Modifier' package.
Then based upon Thorsten Schöning's post at the bottom of this link
http://archive.netbsd.se/?ml=mozilla...7-05&t=4344928
which states that the PPM program has changed in ActivePerl V5.8.8.820 [NB:
I am running V5.8.8.822], I chose to ignore the message about having to
perform the 'ppm repo up theory58S' command (and the corresponding error
message that 'up' is not recognized. Instead, I simply ran the PPM GUI and
installed 'Email-MIME-Modifier' V1.442, then closed the GUI and re-ran
checksetup.pl.
This solved the problems below. More problems have arisen relating to
needing to remove the duplicate DBI packages and UTF8 encoding, but I'll
close this thread at this point.
Cheers,
David
"David Carr" wrote in message
news:FbGdnUO9jabUMjfanZ2dnUVZ_tijnZ2d@mozilla.org. ..
> Hi there,
>
> I am trying to upgrade from Bugzilla V2.22 to V3.0.3 (i.e.
> Bugzilla_Stable), running on my Windows 2003 Advanced Server sp2 running
> Perl V5.8.8. Following the Byron Jones' instructions for a Windows
> install, I have done the update using CVS, uninstalled my prior version of
> ActiveState Perl and installed V5.8.8. I have run the command 'ppm
> upgrade' and now run checksetup.pl.
>
> This is where it seems there is a problem. The output states that I need
> to do the following two steps:
>
> 1>ppm repo add theory58S http://theoryx5.uwinnipeg.ca/ppms
> 2>ppm repo up theory58S
>
> before continuing on to install the Email-MIME-Modifier:
>
> 3>ppm install Email-MIME-Modifier
>
> Step #1 runs fine, however step #2 returns an error saying that there is
> no know command 'up'. Step #3 doesn't work because there is no
> 'Email-MIME-Modifier' found.
>
> It would seem I am not alone on the problem (check out Adrian's posts on
> the newsgroup from 2007.Dec.3-4 with a reply by Max Kanat-Alexander),
> however no resolution was given.
>
> Any help would be most appreciated for the problem with step #1 or step #3
> (or even Bugzilla V3.0.3 on Windows). Thanks in advance,
> David
>