Problem migrating database from bugzilla 2.20.2 to bugzilla 3.0
I installed bugzilla 3.0 and was working fine till I tried migrating
the mysql db from previous version of bugzilla 2.20.2. These two
versions are on different machines. I created .dmp file to get the
data in bugzilla 2.20.2 to update it to bugzilla 3.0. Tables seemed to
be updated(not sure if there is mismatch between the table structure),
but after that upon trying to run checksetup.pl script, I am getting
the following message
"There was an error connecting to MySQL:
Access denied for user 'bugs'@'localh...Migrating from Bugzilla 2.20. to Bugzilla 4.4
I am currently using bugzilla 2.20. I want to upgrade it to bugzilla
4.4 (latest version) restoring all the data and user information from
the previous installation. I am unable to find the required document to
perform this action.
Kindly let me know how to go about doing this.
...Upgrade bugzilla-2.20 to bugzilla-3.1.4
Hi Team ,
I am using bugzilla-2.20 . i want to upgrade my bugzilla
to 3.1.4 . while upgrading to new i am getting following error message
can any help me out resolving this issue .
1, DBD::mysql::db do failed: Duplicate entry 'eGOV' for key 2 [for
Statement "ALTER TABLE series_categories CHANGE COLUMN name name
varchar(64) CHARACTER SET utf8 NOT NULL"] at Bugzilla/DB/Mysql.pm line
called at ./checksetup.pl line 143
2, Before continuing with checksetup, yo...Migration of customized bugzilla 2.12 to bugzilla 3.6
We have modified the bugzilla 2.12 to facilitate the requirements of
the company. But since it's a very old code base and we want to be in
sync with the current bugzilla release we want to migrate.
So our first step is to migrate the data.
The current customized bugzilla database dosen't have any references
Steps I followed was as per the instructions. Please correct me and
provide me your suggestions
1) Took the dump and restored it
2) Downloaded the tar ball and extracted
3) Ran the checksetup.pl and co...Migrating from Bugzilla 2.18/MySQL 4.1.11 to Bugzilla 2.22/Postgres 8.1.3
What is the best way to migrate a bugzilla installation 2.18/MySQL
4.1.11 on machine A to a bugzilla installation 2.22/Postgres 8.1.3 on
Ey�un E. Jacobsen
On Wed, 2006-04-26 at 00:25 +0100, "Eyðun E. Jacobsen" wrote:
> What is the best way to migrate a bugzilla installation 2.18/MySQL
> 4.1.11 on machine A to a bugzilla installation 2.22/Postgres 8.1.3 on
> machine B?
1. Upgrade the MySQL/2.18 to 2.22. (Follow the upgrade instructions in
the release notes.)
2. Run checksetup in a Pg version of 2.22.
3. Use contrib/bzdbcopy.pl. ...Testopia 1.3 (Bugzilla 3.0) and Testopia 1.2.2 (Bugzilla 2.22.x) Released
Testopia 1.3 has been released.=20
This Testopia is compatible with Bugzilla 3.0 and mod_perl and provides
For those of you still running Bugzilla 2.22.x, I am also releasing
1.2.2 which is a (major) bug fix release.
They are available from the project home page at
Thanks for all the feedback. Keep it coming.
...How to upgrade Bugzilla 2.22 to Bugzilla 3.2
Could some one guide me to upgrade Bugzilla 2.22 to Bugzilla 3.2.2
What are the steps to upgrade.
...Upgrade Bugzilla 2.22.3 to Bugzilla 3.4.6 under Windows-XP. #2
This is a multi-part message in MIME format.
* I=92m using the Bugzilla-2.22.3 under Windows-XP and would like
upgrading to new release of Bugzilla-3.4.6 (also under Windows-XP).=20
* I have followed the instructions of the following (correspondingly
to Windows-XP): http://www.bugzilla.org/docs/3.4/en/html/upgrade.html.=20
* I have installed the full required Perl-modules regarding the output
of checks...Issue With Migrating Bugzilla 3.0.5 to Bugzilla 4.0.2
ERROR: There are invalid values for the assigned_to column in the bugs
table. (These values do not exist in the profiles table, in the userid
column.) Before continuing with checksetup, you will need to fix these
values, either by deleting these rows from the database, or changing
the values of assigned_to in bugs to point to valid values in
profiles.userid. The bad values from the bugs.assigned_to column are:
13, 16, 22, 23, 38, 40
On 01/12/11 11:33, Krishnaraj B wrote:
> ERROR: There are invalid values for the assigned_to column in the bugs
> table. (These values do not exist...Restoring Bugzilla 3.2 mysql backup on bugzilla 3.6.3 mysql
Hi Everyone -
* Installed Bugzilla 3.6.3 on new machine
* Took the MYSQL backup from old Bugzilla 3.2.
* Restored the MYSQL back up on Bugzilla 3.6.3, now while login I a=
DBD::mysql::db do failed: Column 'ipaddr' cannot be null [for Statement "IN=
SERT INTO logincookies (cookie, userid, ipaddr, lastused)
VALUES (?, ?, ?, NOW())"] at Bugzilla/Auth/Persist/Cookie.pm =
sist::Cookie=3DHASH(0x2a709b4)', ...Security Advisory for Bugzilla 3.0.3, 3.1.3, 2.22.3, and 2.20.5
Content-Type: text/plain; charset=UTF-8
Bugzilla is a Web-based bug-tracking system, used by a large number of
This advisory covers three security issues that have recently been
fixed in the Bugzilla code:
* Users without the "canconfirm" privilege could enter a bug as NEW
or ASSIGNED by using the XML-RPC interface.
* When viewing several bugs at once, there was a Cross-Site Scripting
* The inbound email interface allowed you t...Migrating the Bugzilla database from 2.20.5 to 3.1.3
Hello; I have been searching for a utility, Perl script, etc., to assist
in migrating the Bugzilla database from 2.20.5 to 3.1.3.=20
Will move.pl work for this? Do I need to CVS?=20
Any help will be appreciated,=20
On 6/24/2008 11:41 AM, Grant, Bruce J wrote:
> Hello; I have been searching for a utility, Perl script, etc., to assist
> in migrating the Bugzilla database from 2.20.5 to 3.1.3.
That's what checksetup.pl is for.
...P4DTI 2.3.0 released to support Bugzilla 2.20
I have made release 2.3.0 of the Perforce Defect Tracking Integration
This release works with Bugzilla 2.20 and with Perforce servers in
Unicode mode, and the User's Guide includes instructions for P4V
This release has not yet been approved by Perforce Inc. As and when
it is approved, it will be uploaded to the Perforce public repository.
Unless and until it is approved, it is not a supported product of
In the meantime, I welcome feedback from anyone prepared to try this
release...upgrade bugzilla and migrate database from 2.16.3 to 2.20
i tried to migrate our bugzilla installation (suse linux) from version
2.16.3 to 2.20. I used the CVS upgrade and it seemed to work perfect. The
check checksetup.pl script dedected errors in the database (mysql). Droping
the database and running the checksetup spript worked fine, but I want to
migrate the existing database to version 2.20. I did not find any HOWTO.
Can anybody help?
regards Thomas Mayer
Thomas Mayer wrote:
> i tried to migrate our bugzilla installation (suse linux) from version
> 2.16.3 to 2.20. I used the CVS upgrade and it seemed to ...