Add to FAQ: How to upgrade Bugzilla from CVS

RESOLVED FIXED in Bugzilla 2.16

Status

()

defect
P3
normal
RESOLVED FIXED
16 years ago
7 years ago

People

(Reporter: justdave, Assigned: goobix)

Tracking

2.17.4
Bugzilla 2.16
Bug Flags:
approval +

Details

Attachments

(1 attachment, 1 obsolete attachment)

Posted to developers@bugzilla.org (feel free to rephrase the question)

>   hi, I am using working on bugzilla database running
> under mysql,and i need to update the contents of
> databse via cvs. can anybody suggest how to do it.
> thanks.

1) make a backup of both your Bugzilla directory and the database.
   a) for the Bugzilla directory this is as easy as doing
      "cp -rp bugzilla bugzilla.bak"
   b) for the database, there's a number of options - see the MySQL docs
      and pick the one that fits you best (The easiest is to just make
      a physical copy of the database on the disk, but you have to have
      the database server shut down to do that without dataloss)
2) cd into your Bugzilla directory
3) cvs -q update -AdP     <-- if you want to update to the tip
   cvs -q update -dP -rTAGNAME    <-- if you want a specific version
     make sure to replace TAGNAME with BUGZILLA-2_16_3 or BUGZILLA-2_17_4
   If you've made no local changes, this should be very clean.  If you
   have made local changes, then watch the cvs output for C results...
   if you get any lines that start with a C it means there were conflicts
   between your local changes and what's in CVS.  You'll need to fix those
   manually before continuing.
4) ./checksetup.pl
   This will take care up updating the database for you as well as any
   other changes required for the new version to operate.

WARNING: Once you run checksetup.pl, the only way to go back is to restore
the backups.  You can't "downgrade" the system cleanly under most
circumstances.

Comment 1

16 years ago
There are already upgrade instructions in the guide, but I can compare them to
this text and add the question to the FAQ with a link to that section.

http://www.bugzilla.org/docs/html/upgrading.html
Priority: -- → P3
Assignee

Comment 2

16 years ago
--> FAQ writer
Assignee: jake → justdave
Assignee

Comment 3

16 years ago
I'll put myself as a owner to remember to come back here and attach a patch.
Assignee: justdave → vlad
Assignee

Updated

16 years ago
Status: NEW → ASSIGNED
Assignee

Comment 4

16 years ago
Posted patch Version 1 (obsolete) — Splinter Review
The only thing that it's already covered in the docs is the backing up process.


Everything else seems to be covered already in the link that Jake gave above,
so it's kinda redundant to add that as well.
Assignee

Updated

16 years ago
Attachment #142776 - Attachment is patch: true
Attachment #142776 - Attachment mime type: application/octet-stream → text/plain
Attachment #142776 - Flags: review?(kiko)
Assignee

Comment 5

16 years ago
that it's --> that it's not

(in the previous comment)

Comment 6

16 years ago
Comment on attachment 142776 [details] [diff] [review]
Version 1


First comment: isn't this bug about a FAQ item?

Second comment: two paragraphs before this comment there is text that *does*
talk about backups:

      <para>Upgrading is a one-way process. You should backup your database
      and current Bugzilla directory before attempting the upgrade. If you wish
      to revert to the old Bugzilla version for any reason, you will have to
      restore from these backups.
      </para>

I'm wondering if the text you're adding shouldn't fit in better with that..

>Index: docs/xml/administration.xml
>+    <itemizedlist>
>+      <listitem>
>+        <para>for the Bugzilla directory this is as easy as doing:

I'm looking at other <para>s around this and they all start the phrases
capitalized. for -> For?

>+        <para>
>+          for the database, there's a number of options 

same

>+          the database server shut down to do that without dataloss.

Maybe "without risking dataloss"?

So
Attachment #142776 - Flags: review?(kiko) → review-
Assignee

Comment 7

16 years ago
Posted patch Version 2Splinter Review
Thanks!

Tested this one visually, it applies nice to the FAQ. Passes the runtests.pl
and makedocs.pl scripts nicely as well.
Attachment #142776 - Attachment is obsolete: true
Assignee

Updated

16 years ago
Attachment #142785 - Flags: review?(kiko)

Comment 8

16 years ago
Comment on attachment 142785 [details] [diff] [review]
Version 2

>Index: docs/xml/faq.xml
>+                  if you want a specific version (in that case you'll have to
>+                  replace TAGNAME with BUGZILLA-2_16_5 or BUGZILLA-2_17_6).

... with a CVS tag name such as BUGZILLA-2_16_5 or ..

to avoid this going obsolete as soon as comitted.

>+              <listitem>
>+                <para>
>+                  Running 

I'd add "After resolving any conflicts that the cvs up operation generated,
running..."

>+                <warning>
>+                  <para>
>+                    Once you run checksetup.pl, the only way to go back is
>+                    to restore the backups. You can't 

the *database* backups.

r=kiko with those changes, no need to repatch.
Attachment #142785 - Flags: review?(kiko) → review+
Assignee

Updated

16 years ago
Flags: approval?
Target Milestone: --- → Bugzilla 2.18
Flags: approval? → approval+
Target Milestone: Bugzilla 2.18 → Bugzilla 2.16
Assignee

Comment 9

16 years ago
Checking in faq.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/faq.xml,v  <--  faq.xml
new revision: 1.25; previous revision: 1.24
done

Checking in faq.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/faq.xml,v  <--  faq.xml
new revision: 1.8.2.9; previous revision: 1.8.2.8
done
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.