Last modified: 2010-05-15 15:48:33 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 8974 - UPGRADE comments
UPGRADE comments
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Documentation (Other open bugs)
1.9.x
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-13 20:46 UTC by Dan Jacobson
Modified: 2010-05-15 15:48 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Dan Jacobson 2007-02-13 20:46:09 UTC
Here are some comments on file "UPGRADE"

  Having downloaded the desired new version of the software, either as a package
  from SourceForge, or via an export from Subversion, decompress the files as
  needed, and replace the existing MediaWiki files with the new.

Note that reading that, many people will just untar into existing
directories, so any old unused php files will just accumulate if they
don't get overwritten.

Much different than the developer's world where one only sees current
files.

Perhaps tell them to untar into newdir, copy
  * The LocalSettings.php file
  * The AdminSettings.php file, where it exists
  * The extensions directory
  * The images directory
into newdir, then move dir to olddir and newdir to dir. And if all is
OK one day rm -r olddir.

Or no big deal if you can guarantee that the accumulating crud won't bite
one one day.

  === Perform the database upgrade ===

  From the command line, browse to the maintenance directory and run the 
  update.php script to check and update the schema. This will insert missing
  tables, update existing tables, and move data around as needed. In most cases,
  this is successful and nothing further needs to be done.

Too bad you blur "update" and "upgrade". I would say
  === Perform the database update ===
or change update.php to upgrade.php.

At least in Debian apt parlance, update and upgrade are very
different. Here you upgrade actually.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links