The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: wordpress (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: wordpress (Ubuntu Quantal)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1221040
Title:
Sync wordpress 3.6.1 (universe) from Debian
** Changed in: wordpress (Ubuntu Raring)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1221040
Title:
Sync wordpress 3.6.1 (universe) from Debian
13.10 has 3.6.1+dfsg-1.
** Also affects: wordpress (Ubuntu Saucy)
Importance: High
Status: New
** Changed in: wordpress (Ubuntu Saucy)
Status: New = Fix Released
** Changed in: wordpress (Ubuntu Precise)
Status: New = Confirmed
** Changed in: wordpress (Ubuntu Quantal)
I believe upgrading to a new release will break existing installations
until an administrator does some migration work. I don't think this is
acceptable as a security update.
If you feel strongly that we should update our stable releases to 3.6.1,
please discuss this with the SRU team and see if
When testing with my PPA, it looks like the 3.6.1 .orig.tar.gz uploaded
to saucy/sid is not the same as was uploading to Debian stable-security
so a straight sync might be rejected by Launchpad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
