Richard Broersma Jr wrote:
>
> I am not familiar with pgZilla. But my guest would be that the checksetup.pl is trying to create
> a new DB scheme on top of the existing DB scheme. This process fails because these relations
> already exist. I don't know if this is true for your pgZilla, but if you were trying to connect
> to and existing Bugzilla database you would not have to following the installation instructions
> where you re-create the DB schema. Just edit your configuration files to point to the correct
> server and database.


Hi,

What you suggest is exactly what I am trying to to. I have the 2.15
install of PgZilla working on a new machine with a copy of the database
from the existing live PgZilla. I installed alongside a 2.22 (and 2.20)
BugZilla and used the existing localconfig file in the same way you
would do a standard upgrade between regular Bugzilla versions.

Hi,

This certainly seems like a faq item, so please point me to the right resource if I missed it.

We have customizations to bugzilla (changed the templates, CSS, etc).

What's the best practice for keeping these customizations under source control? Keep the whole bugzilla-2-18 (or whatever) tree in a local CVS project, and check the changes out directly to the /usr/loca/bugzilla/ directory on our production box? (By 'local cvs project' I mean an independent copy of the mozilla bugzilla cvs project).

Finally, I had a problem where permission one some of the files got whacked when I checked out from cvs. (I don't recall which one, but I believe it lost 'Are there any secrets to preserving permissions with cvs?).

thanks,

bill m

On Thu, 2006-09-21 at 03:30 -0700, Al wrote:
> I have inherited a RedHat PgZilla 2.15 installation that I would love
> to migrate onto a current BugZilla.

That won't be possible without a custom script. Perhaps ask Red Hat if
they've written one.

Otherwise, you could perhaps contract a consultant to write one, or
write one yourself.

-Max
--
http://www.everythingsolved.com/
Everything Solved: Competent, Friendly Bugzilla and Linux Services

Bill Milbratz wrote:

> We have customizations to bugzilla (changed the templates, CSS, etc).
> What's the best practice for keeping these customizations under source control?

Officially, you should be keeping your modifications in the "custom"
directory, and checking those into your own source control.

But I found keeping such parallel custom directories painful because I
had to do a lot of manual merging each time I CVS update'd the main
Bugzilla.

So now what I do is that I have created my own local repository of the
entire Bugzilla tree. I started with the standard Bugzilla 2.18 tree
(back then), imported on a "vendor branch", and then merged that into
the head, and applied our site customizations, and checked them in.

Now, when new releases come out, I import those into the same "vendor
branch", and do a merge of the changes between the last release and the
current release into the head, and then deal with whatever breakages
occur (very few, really).

This way, we can perform fairly automatic updates to new releases as
they come out. Though I've recently been stuck on the 2.20.x series,
because our server is an FC3 server which doesn't have MySQL 4.x. (Sure,
I could get it, but it's a pain to slide it past IT controls..)

Max Kanat-Alexander wrote:
> That won't be possible without a custom script. Perhaps ask Red Hat if
> they've written one.
>
> Otherwise, you could perhaps contract a consultant to write one, or
> write one yourself.
>
> -Max

I figured as much, but I thought I'd ask I'd best get looking at the
schema.

Thanks,
Alastair