Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: Trying to perform cvs update, receiving fatal error no such user

34 views
Skip to first unread message

Gervase Markham

unread,
Dec 16, 2009, 2:19:45 PM12/16/09
to
On 15/12/09 15:08, Peter Shipway wrote:
> cvs update: Updating template/en/extension/hook
>
> Fatal error, aborting.
>
> bwhitecross: no such user

Have you looked in the CVS docs?

My _guess_ would be that the person who did the original checkout did
some sort of CVS login, and those credentials persist. But I don't know.

Gerv

Peter Shipway

unread,
Dec 16, 2009, 11:31:42 PM12/16/09
to support-...@lists.mozilla.org
Thanks for the response Gerv,

The thing is that there are no cvs folders/files in the installation
that I am using. Im trying to move an old outdated system to a new
server and upgrade it to the latest (old version is 2.17.3).

I'm following the instructions and logging as as anonymous. The problem
is that there where some changes made to the system that are to be kept
(I've done a diff and it seems to mainly be the templates folder plus a
couple of changes to the way data is handled) but upgrade to the latest
version. Mabye I should just grab the latest version, upgrade the
database and reapply the customisations.

Regards,

Gerv
_______________________________________________
support-bugzilla mailing list
support-...@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-bugzilla
PLEASE put support-...@lists.mozilla.org in the To: field when you
reply.

Gervase Markham

unread,
Dec 17, 2009, 1:41:18 PM12/17/09
to
On 16/12/09 20:31, Peter Shipway wrote:
> The thing is that there are no cvs folders/files in the installation
> that I am using. Im trying to move an old outdated system to a new
> server and upgrade it to the latest (old version is 2.17.3).

Ah. You can't upgrade a system using CVS unless it was originally
checked out using CVS. The best thing to do is install a new copy of
Bugzilla in a new directory, pointed at the same database. Then, run the
upgrade process (checksetup.pl) and move the new directory to where the
old one was.

> I'm following the instructions and logging as as anonymous. The problem
> is that there where some changes made to the system that are to be kept
> (I've done a diff and it seems to mainly be the templates folder plus a
> couple of changes to the way data is handled) but upgrade to the latest
> version. Mabye I should just grab the latest version, upgrade the
> database and reapply the customisations.

That sounds like a plan :-) If you want to do it with no downtime, clone
the database and use that clone on your new copy while you reapply and
test the modifications. When you are ready, change the new copy to use
the production database, run the upgrade script again, and move the new
code to where the old stuff was so that URLs still work.

Gerv

0 new messages