---------- Forwarded message ----------
From: Jon Ciesla <limb(a)jcomserv.net>
Date: Mon, Mar 21, 2011 at 08:21
Subject: Wordpress(-mu): Big changes coming
To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org>
Hi, Wordpress maintainer here.
In order to protect against two CVEs*, I'm upgrading Wordpress in all
releases to 3.1. In addition, this will obsolete wordpress-mu, since
this functionality has been migrated to the main wordpress release as of
wordpress 3.0, and wordpress-mu has been deprecated upstream. I would
not normally make so drastic a change on any stable release, especially
EPEL, but backporting patches to the 2.x series is becoming increasingly
unmaintainable. This is already done for rawhide and F15, and I intend
to build for F13, F14, EL5 and EL6 today, and send them to testing, and
then push to stable one the appropriate period has elapsed.
Please redistribute this to anyone you know who might be affected and
may not be on this list.
in your fear, seek only peace
in your fear, seek only love
devel mailing list
Stephen J Smoogen.
"The core skill of innovators is error recovery, not failure avoidance."
Randy Nelson, President of Pixar University.
"Let us be kind, one to another, for most of us are fighting a hard
battle." -- Ian MacLaren
As many folks have lamented, the current git-18.104.22.168 in EL-5 is quite
a bit stale. Updating it has been discussed on several occassions,
but was held up until recently due to compatibility issues with the
emacs-git package. With great thanks to Kevin Fenzi for dusting off
an old emacs habit, that is now resolved and git-22.214.171.124 is heading to
The update should be a welcome enhancement and not cause current users
any trouble. Please test and provide feedback via the URL above.
Since 126.96.36.199 there have been a huge amount of bug fixes and
improvements in all areas of git. Of particular interest are the
release notes from 1.6.0 and 1.7.0:
Links to release notes for each version of git can be found here:
In git-1.6.0, most git-* commands were moved out of the standard path.
Use of "git $command" is preferred. It is a very good idea to migrate
scripts to use the dashless form. However, to retain compatibility
the EL-5 packages keep the git-* commands in /usr/bin.
Other noteworthy changes since 188.8.131.52:
* "git push" into a branch that is currently checked out (i.e. pointed at by
HEAD in a repository that is not bare) is refused by default.
Similarly, "git push $there :$killed" to delete the branch $killed
in a remote repository $there, when $killed branch is the current
branch pointed at by its HEAD, will be refused by default.
Setting the configuration variables receive.denyCurrentBranch and
receive.denyDeleteCurrent to 'ignore' in the receiving repository
can be used to override these safety features.
* "git send-email" does not make deep threads by default when sending a
patch series with more than two messages. All messages will be sent
as a reply to the first message, i.e. cover letter.
It has been possible already to configure send-email to send "shallow thread"
by setting sendemail.chainreplyto configuration variable to false. The
only thing this release does is to change the default when you haven't
configured that variable.
* "git status" will not be "git commit --dry-run". This change does not
affect you if you run the command without pathspec.
Nobody sane found the current behaviour of "git status Makefile" useful
nor meaningful, and it confused users. "git commit --dry-run" has been
provided as a way to get the current behaviour of this command since
For folks using git over HTTP, git now supports a 'smart' HTTP
protocol which is much more efficient than the older ('dumb') HTTP
protocol. Refer to the git http-backend documentation for more
Thanks to all the folks who have helped test the updated git packages
on EL-5 and reported issues.
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
It is impossible to enjoy idling thoroughly unless one has plenty of
work to do.
-- Jerome K. Jerome