Upgrading via CVS with Firewall.

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Upgrading via CVS with Firewall.

boydd_uk

I wish to upgrade my Bugzilla installation, without having to create a
new installation and thus lose all my changes.

However, the CVS update fails.  I'm pretty sure this is due to our
corporate firewall policy.

Like most coporations the chance of "Operations" opening a firewall
port (or doing anything else useful for that matter) is equivilent to
me winning the lottery this Saturday without buying a ticket.

Surely there must be another way to upgrade?

_______________________________________________
mozilla-webtools mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-webtools
Reply | Threaded
Open this post in threaded view
|

Re: Upgrading via CVS with Firewall.

David T. Ashley-3
First, I agree that most IT departments are nearly useless.  There are a
lot of components to this, including:

a)They typically are undereducated and unable to deploy solutions well.

b)In the case of your particular problem, if it doesn't affect them (which
usually means your management banging on their management), they have
little incentive to help.  Opening any port in the firewall (from their
point of view) introduces risk with no gain to them.

Here is what I would do, in order:

a)Work in good faith with your management and the IT department to _try_
to get the port opened.  (I agree your odds are not good, but you should
_try_.)

b)Look for any route around the firewall into a Unix machine.  Try the SSH
port, for example.

If you control an external Unix machine, then you have other options.  For
example, you could run SSH on port 443, which will make it around many or
most corporate firewalls.

c)If you can achieve (b), then get an account on a *nix machine somewhere.
 Do the CVS checkout on that Unix machine (you connect to it on the SSH
port, it connects via 2401 to get the source).  After the code is checked
out, SFTP it down to yourself and then to the machine of interest (which I
assume is behind your firewall).

Please don't interpret my response as a scofflaw attitude.  However,
sometimes there are barriers to productivity in the workplace, and
sometimes ... extraordinary measures are necessary.

Feel free to write back if any questions.

Good luck,
Dave.

>
> I wish to upgrade my Bugzilla installation, without having to create a
> new installation and thus lose all my changes.
>
> However, the CVS update fails.  I'm pretty sure this is due to our
> corporate firewall policy.
>
> Like most coporations the chance of "Operations" opening a firewall
> port (or doing anything else useful for that matter) is equivilent to
> me winning the lottery this Saturday without buying a ticket.
>
> Surely there must be another way to upgrade?
>
> _______________________________________________
> mozilla-webtools mailing list
> [hidden email]
> http://mail.mozilla.org/listinfo/mozilla-webtools
>


---------------------------------------
David T. Ashley
[hidden email]

_______________________________________________
mozilla-webtools mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-webtools
Reply | Threaded
Open this post in threaded view
|

Re: Upgrading via CVS with Firewall.

boydd_uk
In reply to this post by boydd_uk
Hi David,

Unfortuantely I'm on the Windows Platform.

I would like to think that I could get Ops to open a port.  But this is
a financial organisation and Bugzilla for us is a non-essential
applicaiton.  My chances are very low.  And even if I could, it would
go via a change control system that would take approximately three of
my lifetimes to complete.

I must admit (speaking from a very Windows perspective so please
forgive me), that not having a method/installer to carry out a local
upgrade is a little troublesome.

I've heard of a product called GrabCVS, that claims to resolve this
issue by allowing downloads (only) from CVS through firewalls.
However, this solution requires ViewCVS installed server-side.  Is this
something to be considered?  After all, I'm sure this must affect many
users.

Regards








David T. Ashley wrote:

> First, I agree that most IT departments are nearly useless.  There are a
> lot of components to this, including:
>
> a)They typically are undereducated and unable to deploy solutions well.
>
> b)In the case of your particular problem, if it doesn't affect them (which
> usually means your management banging on their management), they have
> little incentive to help.  Opening any port in the firewall (from their
> point of view) introduces risk with no gain to them.
>
> Here is what I would do, in order:
>
> a)Work in good faith with your management and the IT department to _try_
> to get the port opened.  (I agree your odds are not good, but you should
> _try_.)
>
> b)Look for any route around the firewall into a Unix machine.  Try the SSH
> port, for example.
>
> If you control an external Unix machine, then you have other options.  For
> example, you could run SSH on port 443, which will make it around many or
> most corporate firewalls.
>
> c)If you can achieve (b), then get an account on a *nix machine somewhere.
>  Do the CVS checkout on that Unix machine (you connect to it on the SSH
> port, it connects via 2401 to get the source).  After the code is checked
> out, SFTP it down to yourself and then to the machine of interest (which I
> assume is behind your firewall).
>
> Please don't interpret my response as a scofflaw attitude.  However,
> sometimes there are barriers to productivity in the workplace, and
> sometimes ... extraordinary measures are necessary.
>
> Feel free to write back if any questions.
>
> Good luck,
> Dave.
>
> >
> > I wish to upgrade my Bugzilla installation, without having to create a
> > new installation and thus lose all my changes.
> >
> > However, the CVS update fails.  I'm pretty sure this is due to our
> > corporate firewall policy.
> >
> > Like most coporations the chance of "Operations" opening a firewall
> > port (or doing anything else useful for that matter) is equivilent to
> > me winning the lottery this Saturday without buying a ticket.
> >
> > Surely there must be another way to upgrade?
> >
> > _______________________________________________
> > mozilla-webtools mailing list
> > [hidden email]
> > http://mail.mozilla.org/listinfo/mozilla-webtools
> >
>
>
> ---------------------------------------
> David T. Ashley
> [hidden email]

_______________________________________________
mozilla-webtools mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-webtools
Reply | Threaded
Open this post in threaded view
|

Re: Upgrading via CVS with Firewall.

David T. Ashley-3
A few words of advice:

a)First, run Bugzilla on a *nix box, not on Windows.  You'll run into far
fewer problems with a *nix box.  If your IT department objects to that,
beg.

b)Walk (i.e. quit your job) if the trend of performance interference keeps
up.  Don't forget that employers compete for employees just as surely as
employees compete for employers.  Find something else that is more
self-actualizing.

My advice?

http://www.monster.co.uk

(hope that is the right URL--I'm just guessing.)

Dave.

> Hi David,
>
> Unfortuantely I'm on the Windows Platform.
>
> I would like to think that I could get Ops to open a port.  But this is
> a financial organisation and Bugzilla for us is a non-essential
> applicaiton.  My chances are very low.  And even if I could, it would
> go via a change control system that would take approximately three of
> my lifetimes to complete.
>
> I must admit (speaking from a very Windows perspective so please
> forgive me), that not having a method/installer to carry out a local
> upgrade is a little troublesome.
>
> I've heard of a product called GrabCVS, that claims to resolve this
> issue by allowing downloads (only) from CVS through firewalls.
> However, this solution requires ViewCVS installed server-side.  Is this
> something to be considered?  After all, I'm sure this must affect many
> users.
>
> Regards
>
> David T. Ashley wrote:
>> First, I agree that most IT departments are nearly useless.  There are a
>> lot of components to this, including:
>>
>> a)They typically are undereducated and unable to deploy solutions well.
>>
>> b)In the case of your particular problem, if it doesn't affect them
>> (which
>> usually means your management banging on their management), they have
>> little incentive to help.  Opening any port in the firewall (from their
>> point of view) introduces risk with no gain to them.
>>
>> Here is what I would do, in order:
>>
>> a)Work in good faith with your management and the IT department to _try_
>> to get the port opened.  (I agree your odds are not good, but you should
>> _try_.)
>>
>> b)Look for any route around the firewall into a Unix machine.  Try the
>> SSH
>> port, for example.
>>
>> If you control an external Unix machine, then you have other options.
>> For
>> example, you could run SSH on port 443, which will make it around many
>> or
>> most corporate firewalls.
>>
>> c)If you can achieve (b), then get an account on a *nix machine
>> somewhere.
>>  Do the CVS checkout on that Unix machine (you connect to it on the SSH
>> port, it connects via 2401 to get the source).  After the code is
>> checked
>> out, SFTP it down to yourself and then to the machine of interest (which
>> I
>> assume is behind your firewall).
>>
>> Please don't interpret my response as a scofflaw attitude.  However,
>> sometimes there are barriers to productivity in the workplace, and
>> sometimes ... extraordinary measures are necessary.
>>
>> Feel free to write back if any questions.
>>
>> Good luck,
>> Dave.
>>
>> >
>> > I wish to upgrade my Bugzilla installation, without having to create a
>> > new installation and thus lose all my changes.
>> >
>> > However, the CVS update fails.  I'm pretty sure this is due to our
>> > corporate firewall policy.
>> >
>> > Like most coporations the chance of "Operations" opening a firewall
>> > port (or doing anything else useful for that matter) is equivilent to
>> > me winning the lottery this Saturday without buying a ticket.
>> >
>> > Surely there must be another way to upgrade?
>> >
>> > _______________________________________________
>> > mozilla-webtools mailing list
>> > [hidden email]
>> > http://mail.mozilla.org/listinfo/mozilla-webtools
>> >
>>
>>
>> ---------------------------------------
>> David T. Ashley
>> [hidden email]
>
> _______________________________________________
> mozilla-webtools mailing list
> [hidden email]
> http://mail.mozilla.org/listinfo/mozilla-webtools

_______________________________________________
mozilla-webtools mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-webtools
Reply | Threaded
Open this post in threaded view
|

Re: Upgrading via CVS with Firewall.

Dave Miller
In reply to this post by boydd_uk
boydd_uk wrote:

> I wish to upgrade my Bugzilla installation, without having to create a
> new installation and thus lose all my changes.
>
> However, the CVS update fails.  I'm pretty sure this is due to our
> corporate firewall policy.
>
> Like most coporations the chance of "Operations" opening a firewall
> port (or doing anything else useful for that matter) is equivilent to
> me winning the lottery this Saturday without buying a ticket.
>
> Surely there must be another way to upgrade?

The only place data is stored within Bugzilla is in the data directory
and the localconfig file (other than the database).  Unless you've made
modifications to the perl code, you can safely copy the localconfig file
and the data directory into your new copy of Bugzilla.

If you have made modification to the perl code or templates, you can try
to cvs update if you have access to an external linux or unix box via
ssh...  use the port forwarding options to forward port 2401 on your
local machine through your ssh connection to port 2401 on
cvs-mirror.mozilla.org.

Another option if you happen to have the rsync ports open (about as
likely as cvs, but worth a shot), is to rsync the cvs repository to a
local copy, then check out from there instead.  This would be a much
larger download (getting the entire history of every file instead of
just the current versions).  The rsync version is available at
rsync://cvs-mirror.mozilla.org/mozilla

Yet another thing you could try (which would be a little more work)
would be to grab a current tarball, and the old tarball from the version
you had installed currently, and unpack them side by side, and use the
"diff" program to compare them to each other and see what changed from
one version to the next, then make those same changes to your local
install.  It will probably be easier (and safer) to compare an
unmodified copy of the same Bugzilla version you're running with your
production code, to see what local changes you've made to it, and then
make those same changes again to the current version.

--
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Foundation       http://www.mozilla.org/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/
_______________________________________________
mozilla-webtools mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-webtools
Reply | Threaded
Open this post in threaded view
|

Re: Upgrading via CVS with Firewall.

byron jones
In reply to this post by boydd_uk
first of all, appoligies for feeding the troll.

> a)First, run Bugzilla on a *nix box, not on Windows.  You'll run into far
> fewer problems with a *nix box.  If your IT department objects to that,
> beg.

bugzilla runs with the same number of problems on windows or unix.  windows is
a stable server platform.

it just comes down to what you're familar with -- i'm willing to bet that
someone with no unix familiarity will have more issues running anything on
unix than they ever will have on windows.

> b)Walk (i.e. quit your job) if the trend of performance interference keeps
> up.  Don't forget that employers compete for employees just as surely as
> employees compete for employers.  Find something else that is more
> self-actualizing.

rolls eyes.



back to the problem at hand.

if you have not made any modifications to your bugzilla installation, you can
just grab the tarball and extract over the top of your existing install, then
run checksetup.

if you have made modifications, thus you need cvs's smart updating stuff,
perhaps a viable solution would be to copy your existing bugzilla directory to
a machine that does have cvs access.  you don't need the database or web
server; just copy the directory, do a cvs update, and copy the files back
again.

a third solution is to grab the new tarball and manually apply any
modifications to it.



-byron

begin-base64 644 signature.gif
R0lGODlhbQAHAIAAAABPo////ywAAAAAbQAHAAACfAxuGAnch+Bibkn7FL1p
XgVl4Ig1jjlZRoqybgun2Cur5uOunq7u/Ipq7WIyIc7XG9JquEgumPzdlhTf
h0O83kDJaXEm8mRHwXKJy5sac7qYOpT+gtv0n+0ujQOfdqh16caWt0foBViH
N1PRMXimiLUGt3ElVimlgbllWAAAOw==
====

_______________________________________________
mozilla-webtools mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-webtools
Reply | Threaded
Open this post in threaded view
|

RE: Upgrading via CVS with Firewall.

David T. Ashley-3
> first of all, appoligies for feeding the troll.

That remark is without basis.  The definition of a troll is somebody who
says inflammatory things with the intent of getting replies.  Nothing I said
was inflammatory; either deliberately or accidentally.

> > a)First, run Bugzilla on a *nix box, not on Windows.  You'll
> run into far
> > fewer problems with a *nix box.  If your IT department objects to that,
> > beg.
>
> bugzilla runs with the same number of problems on windows or
> unix.  windows is
> a stable server platform.

This remark is also without basis.

If you look at the Bugzilla discussion in various list archives, you'll find
people with nebulous problems on Windows platforms who couldn't get support
or resolve their problems.  That isn't a judgement on the relative merits of
*nix versus Windows--it is just an economic matter.

a)With fewer users running Bugzilla on Windows, any compatibility issues are
less likely to be discovered, reported, and corrected.

b)With fewer users running Bugzilla on Windows, there is a smaller body of
users who can offer help.

c)With fewer users running MySQL on Windows, trouble is more likely there,
too.

If you want URLs ...

One runs into the same problems choosing hardware for Windows platforms.  It
pays to stay away from chipsets and peripherals that nobody else is using.
Without a large volume of users, driver problems and the like are less
likely to get fixed.

_______________________________________________
mozilla-webtools mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-webtools
Reply | Threaded
Open this post in threaded view
|

Re: Upgrading via CVS with Firewall.

Marc Schumann
In reply to this post by boydd_uk
boydd_uk,

11 Jul 2005 06:59:29 -0700, boydd_uk <[hidden email]>:
> I wish to upgrade my Bugzilla installation, without having to create a
> new installation and thus lose all my changes.
>
> However, the CVS update fails.  I'm pretty sure this is due to our
> corporate firewall policy.

what you can do is this.
Prepare two directories. The first contains an unmodified version of
Bugzilla your installation is based upon. The second contains an
unmodified version of Bugzilla you want to upgrade to.
Then, generate a patch file (using the diff -u command). On a copy of
your Bugzilla directory, try to apply the patch file (using the patch
command).

   Kind regards
      Marc

--
http://wurblzap.net/
Bugzilla hosting and professional support

_______________________________________________
mozilla-webtools mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-webtools