Compare commits

...

12 commits

Author SHA1 Message Date
1d94be10b5 - updated to 2.2.3 (security release) 2007-09-11 16:45:21 +00:00
John Berninger
933c83d89a update to upstream 2.2.2 and license tag update 2007-08-29 14:54:42 +00:00
John Berninger
bb1dfc5077 update to 2.2.1 2007-07-04 22:22:09 +00:00
John Berninger
7008296f0c update to 2.1.3 final 2007-04-16 15:13:46 +00:00
John Berninger
9247f27815 update for bz 233703 2007-03-26 15:42:19 +00:00
John Berninger
92da5c1d0b update to 2.1.2 - bz 230825 2007-03-03 13:34:05 +00:00
John Berninger
6237923d48 bz 229991 update to 2.1.1 2007-02-27 16:08:16 +00:00
John Berninger
17871ed1ef update to v2.1 to fix multiple bz/vuln's 2007-02-01 02:45:58 +00:00
John Berninger
f38988bf6e Update to 2.0.5 to fix bz 220818 2006-12-27 16:05:20 +00:00
John Berninger
53afb9d753 Actually remove mysql-server dependency this time 2006-12-05 01:41:12 +00:00
John Berninger
c5e495b588 Fix for BZ 213985 2006-12-03 18:27:22 +00:00
John Berninger
f8e88b0452 Fix for BZ 213985 2006-12-03 18:09:18 +00:00
4 changed files with 75 additions and 6 deletions

View file

@ -1 +1,2 @@
wordpress-2.0.4.tar.gz
wordpress-2.2.2.tar.gz
wordpress-2.2.3.tar.gz

View file

@ -1,6 +1,9 @@
Wordpress is a database driven blogging program designed to make it exceedingly
easy to publish an online blog, sometimes also called a weblog or journal.
CONFIGURING WORDPRESS FOR THE FIRST TIME
----------------------------------------
Once this package is installed, there are a few configuration items which need
to be performed before the blog is usable. First, you need to establish a
username and password to connect to your MySQL database as, and make both
@ -43,3 +46,28 @@ Once that's done and the database server and web server have been started,
open a web browser to http://localhost/wordpress/wp-admin/install.php and
follow the instructions given to you on the pages you see to set up the
database tables and begin publishing your blog.
UPGRADING WORDPRESS
-------------------
In order to upgrade from a 2.1 series package, there are several steps you
will need to take. If you've already performed the 'yum update', all is not
lost, and you more than likely still be able to complete the upgrade
painlessly.
First, you will want to back up your entire database. This is simply common
sense, but it is also mentioned explicitly in Wordpress's upgrade instructions.
You should have disabled all your plugins. Having old plugins still active
could cause problems, as the old plugins may not be compatible with the new
version of Wordpress.
Once all the plugins are disabled, run the actual yum update. Once this
completes, you should point a browser at
http://<your wordpress host>/wordpress/wp-admin/upgrade.php and follow the
instructions that appear in the browser window. Once this is completed, you
can begin reactivating plugins one at a time.
If you need a more detailed upgrade document, or you run into problems, please
see the Wordpress upgrade documentation at
http://codex.wordpress.org/Upgrading_WordPress#Detailed_Instructions

View file

@ -1 +1,2 @@
0de8e4b2051ce9313a23d7726210d5e3 wordpress-2.0.4.tar.gz
a87666c6fe6cb4db94e2ae0531e5b633 wordpress-2.2.2.tar.gz
98c1e611f8533d4fe4e8f995b8d83110 wordpress-2.2.3.tar.gz

View file

@ -1,10 +1,10 @@
Summary: WordPress blogging software
URL: http://www.wordpress.org
Name: wordpress
Version: 2.0.4
Version: 2.2.3
Group: Applications/Publishing
Release: 1%{?dist}
License: GPL
Release: 0%{?dist}
License: GPLv2
# Source0 with name-version does not work for web retrieval,
# latest.tar.gz does not work for build
# Source0: http://wordpress.org/latest.tar.gz
@ -12,7 +12,7 @@ Source0: http://wordpress.org/%{name}-%{version}.tar.gz
Source1: wordpress-httpd-conf
Source2: README.fedora.wordpress
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
Requires: php >= 4.1.0, httpd, mysql-server, php-mysql
Requires: php >= 4.2.0, httpd, php-mysql
BuildArch: noarch
%description
@ -50,6 +50,7 @@ rm -rf ${RPM_BUILD_ROOT}
%doc license.txt
%doc readme.html
%doc README.fedora
%{_datadir}/wordpress/wp-app.php
%{_datadir}/wordpress/wp-atom.php
%{_datadir}/wordpress/wp-blog-header.php
%{_datadir}/wordpress/wp-comments-post.php
@ -57,6 +58,7 @@ rm -rf ${RPM_BUILD_ROOT}
%{_datadir}/wordpress/wp-config-sample.php
%{_datadir}/wordpress/wp-config.php
%config(noreplace) %{_sysconfdir}/wordpress/wp-config.php
%{_datadir}/wordpress/wp-cron.php
%{_datadir}/wordpress/wp-feed.php
%{_datadir}/wordpress/wp-links-opml.php
%{_datadir}/wordpress/wp-login.php
@ -72,6 +74,43 @@ rm -rf ${RPM_BUILD_ROOT}
%dir %{_sysconfdir}/wordpress
%changelog
* Tue Sep 11 2007 Adrian Reber <adrian@lisas.de> - 2.2.3-0
- updated to 2.2.3 (security release)
* Wed Aug 29 2007 John Berninger <john at ncphotography dot com> - 2.2.2-0
- update to upstream 2.2.2
- license tag update
* Wed Jul 4 2007 John Berninger <john at ncphotography dot com> - 2.2.1-1
- update to upstream 2.2.1 to fix various vulnerabilities
* Mon Apr 16 2007 John Berninger <jwb at redhat dot com> - 2.1.3-1
- update to 2.1.3 final - bz235912
* Mon Mar 26 2007 John Berninger <jwb at redhat dot com> - 2.1.3-rc2
- update to 2.1.3rc2 for bz 233703
* Sat Mar 3 2007 John Berninger <jwb at redhat dot com> - 2.1.2-0
- update to 2.1.2 - backdoor exploit introduced upstream in 2.1.1 - bz 230825
* Tue Feb 27 2007 John Berninger <jwb at redhat dot com> - 2.1.1-0
- update to 2.1.1 for vuln fix - bz 229991
* Wed Jan 31 2007 John Berninger <jwb at redhat dot com> - 2.1-0
- update to v 2.1 to fix multiple bz/vuln's
* Wed Dec 27 2006 John Berninger <jwb at redhat dot com> - 2.0.5-1
- ver 2.0.5 to fix bz 220818
* Sun Dec 3 2006 John Berninger <jwb at redhat dot com> - 2.0.4-4
- Remove mysql-server dependency for real this time.
* Sun Dec 3 2006 John Berninger <jwb at redhat dot com> - 2.0.4-3
- Remove mysql-server dependency
* Sun Dec 3 2006 John Berninger <jwb at redhat dot com> - 2.0.4-2
- Fix wp-db-backup.php vuln in BZ 213985
* Thu Oct 26 2006 John Berninger <jwb at redhat dot com> - 2.0.4-1
- Doc fix for BZ 207822