| 2008-05-07 00:38:14 |
Rolf Leggewie |
bug |
|
|
added bug |
| 2008-07-13 12:37:33 |
Emanuele Gentili |
wordpress: status |
New |
Confirmed |
|
| 2008-07-13 12:37:33 |
Emanuele Gentili |
wordpress: importance |
Undecided |
Wishlist |
|
| 2008-07-23 00:45:06 |
Launchpad Janitor |
wordpress: status |
Confirmed |
Fix Released |
|
| 2008-11-13 11:57:19 |
Rolf Leggewie |
wordpress: status |
Fix Released |
In Progress |
|
| 2008-11-13 11:57:19 |
Rolf Leggewie |
wordpress: statusexplanation |
|
fixed for Intrepid, reopening to nominate for hardy. Should this be backported to other releases as well? |
|
| 2008-11-14 16:12:55 |
Rolf Leggewie |
bug |
|
|
added attachment 'wordpress_LP227547.debdiff' (debdiff for hardy) |
| 2008-11-14 16:43:34 |
Rolf Leggewie |
bug |
|
|
added attachment 'wordpress_intrepid.debdiff' (debdiff for intrepid) |
| 2008-11-14 16:54:33 |
Rolf Leggewie |
bug |
|
|
added attachment 'wordpress_jaunty.debdiff' (debdiff for jaunty) |
| 2008-11-15 14:08:44 |
Rolf Leggewie |
bug |
|
|
added subscriber Ubuntu Sponsors for universe |
| 2008-11-20 09:50:11 |
Rolf Leggewie |
bug |
|
|
added subscriber MOTU Stable Release Updates |
| 2008-11-23 12:32:41 |
Rolf Leggewie |
bug |
|
|
added attachment 'lp227547.diff' (lp227547.diff) |
| 2008-11-23 17:16:20 |
Rolf Leggewie |
bug |
|
|
added attachment 'wordpress_hardy.debdiff' (updated debdiff for hardy) |
| 2008-11-23 17:50:59 |
Rolf Leggewie |
bug |
|
|
assigned to wordpress (Debian) |
| 2008-11-23 18:26:49 |
Rolf Leggewie |
bug |
|
|
added attachment 'wordpress_intrepid.debdiff' (updated debdiff for intrepid) |
| 2008-11-24 15:33:08 |
Rolf Leggewie |
description |
Binary package hint: wordpress
I let ubuntu manage my wordpress install and I want to continue doing that. Thus, I don't think the built-in function from wordpress to inform about a new upstream release makes any sense and can easily be counterproductive. Somebody who is not so well-versed with the whole FOSS-process of upstream->debian->ubuntu might well be irritated that the software keeps telling about the available upgrade when "sudo aptitude" disagrees. |
Binary package hint: wordpress
I let ubuntu manage my wordpress install and I want to continue doing that. Thus, I don't think the built-in function from wordpress to inform about a new upstream release makes any sense and can easily be counterproductive. Somebody who is not so well-versed with the whole FOSS-process of upstream->debian->ubuntu might well be irritated that the software keeps telling about the available upgrade when "sudo aptitude" disagrees.
executive summary (as per SRU wiki page, subheading "Procedure"):
2.1 impact:
blog admin users are instructed to update which runs counter to the idea of a distribution to manage packages
2.2 upstream dev branch:
this is not applicable upstream, the aim is to disable a feature which has a purpose but not in the context of a managed distribution
2.3 minimal patch
see attached debdiffs. I worked together with james_w to iron out a few minor kinks still present in even the latest versions. To keep the bug-spam low, I did not attach them here.
2.4 TEST CASE:
install and configure wordpress in hardy (I think the same thing should already be observable in Intrepid, too). log in as a blog admin. You are presented with a message that your installation of wordpress is out of date and you should update.
2.5 regression potential
low. The patch disables certain portions of a page only visible to wiki admins. I guess the worst case would be that something becomes unbalanced and the page would not validate as HTML (I assume this indeed happened with the patch as it is now applied in Intrepid) for those users on administrative pages. Browsers are usually quite tolerant of incorrect HTML. pages served to regular visitors are completely unchanged. |
|
| 2008-11-24 15:39:27 |
Rolf Leggewie |
description |
Binary package hint: wordpress
I let ubuntu manage my wordpress install and I want to continue doing that. Thus, I don't think the built-in function from wordpress to inform about a new upstream release makes any sense and can easily be counterproductive. Somebody who is not so well-versed with the whole FOSS-process of upstream->debian->ubuntu might well be irritated that the software keeps telling about the available upgrade when "sudo aptitude" disagrees.
executive summary (as per SRU wiki page, subheading "Procedure"):
2.1 impact:
blog admin users are instructed to update which runs counter to the idea of a distribution to manage packages
2.2 upstream dev branch:
this is not applicable upstream, the aim is to disable a feature which has a purpose but not in the context of a managed distribution
2.3 minimal patch
see attached debdiffs. I worked together with james_w to iron out a few minor kinks still present in even the latest versions. To keep the bug-spam low, I did not attach them here.
2.4 TEST CASE:
install and configure wordpress in hardy (I think the same thing should already be observable in Intrepid, too). log in as a blog admin. You are presented with a message that your installation of wordpress is out of date and you should update.
2.5 regression potential
low. The patch disables certain portions of a page only visible to wiki admins. I guess the worst case would be that something becomes unbalanced and the page would not validate as HTML (I assume this indeed happened with the patch as it is now applied in Intrepid) for those users on administrative pages. Browsers are usually quite tolerant of incorrect HTML. pages served to regular visitors are completely unchanged. |
Binary package hint: wordpress
I let ubuntu manage my wordpress install and I want to continue doing that. Thus, I don't think the built-in function from wordpress to inform about a new upstream release makes any sense and can easily be counterproductive. Somebody who is not so well-versed with the whole FOSS-process of upstream->debian->ubuntu might well be irritated that the software keeps telling about the available upgrade when "sudo aptitude" disagrees.
executive summary (as per SRU wiki page, subheading "Procedure"):
2.1 impact:
blog admin users are instructed to update which runs counter to the idea of a distribution to manage packages
2.2 dev branch:
fixed since version 2.5.1-5ubuntu1 in Intrepid, but there is a more elegant solution put forth here and suggested for the next Jaunty merge in bug 301340. The fix currently in Intrepid and Jaunty is only partial.
2.3 minimal patch
see attached debdiffs. I worked together with james_w to iron out a few minor kinks still present in even the latest versions. To keep the bug-spam low, I did not attach them here.
2.4 TEST CASE:
install and configure wordpress in hardy (I think the same thing should already be observable in Intrepid, too). log in as a blog admin. You are presented with a message that your installation of wordpress is out of date and you should update.
2.5 regression potential
low. The patch disables certain portions of a page only visible to wiki admins. I guess the worst case would be that something becomes unbalanced and the page would not validate as HTML (I assume this indeed happened with the patch as it is now applied in Intrepid) for those users on administrative pages. Browsers are usually quite tolerant of incorrect HTML. pages served to regular visitors are completely unchanged. |
|
| 2008-11-24 15:41:31 |
Rolf Leggewie |
description |
Binary package hint: wordpress
I let ubuntu manage my wordpress install and I want to continue doing that. Thus, I don't think the built-in function from wordpress to inform about a new upstream release makes any sense and can easily be counterproductive. Somebody who is not so well-versed with the whole FOSS-process of upstream->debian->ubuntu might well be irritated that the software keeps telling about the available upgrade when "sudo aptitude" disagrees.
executive summary (as per SRU wiki page, subheading "Procedure"):
2.1 impact:
blog admin users are instructed to update which runs counter to the idea of a distribution to manage packages
2.2 dev branch:
fixed since version 2.5.1-5ubuntu1 in Intrepid, but there is a more elegant solution put forth here and suggested for the next Jaunty merge in bug 301340. The fix currently in Intrepid and Jaunty is only partial.
2.3 minimal patch
see attached debdiffs. I worked together with james_w to iron out a few minor kinks still present in even the latest versions. To keep the bug-spam low, I did not attach them here.
2.4 TEST CASE:
install and configure wordpress in hardy (I think the same thing should already be observable in Intrepid, too). log in as a blog admin. You are presented with a message that your installation of wordpress is out of date and you should update.
2.5 regression potential
low. The patch disables certain portions of a page only visible to wiki admins. I guess the worst case would be that something becomes unbalanced and the page would not validate as HTML (I assume this indeed happened with the patch as it is now applied in Intrepid) for those users on administrative pages. Browsers are usually quite tolerant of incorrect HTML. pages served to regular visitors are completely unchanged. |
Binary package hint: wordpress
I let ubuntu manage my wordpress install and I want to continue doing that. Thus, I don't think the built-in function from wordpress to inform about a new upstream release makes any sense and can easily be counterproductive. Somebody who is not so well-versed with the whole FOSS-process of upstream->debian->ubuntu might well be irritated that the software keeps telling about the available upgrade when "sudo aptitude" disagrees.
*** executive summary *** (as per SRU wiki page, subheading "Procedure"):
2.1 impact:
blog admin users are instructed to update which runs counter to the idea of a distribution to manage packages
2.2 dev branch:
fixed since version 2.5.1-5ubuntu1 in Intrepid, but there is a more elegant solution put forth here and suggested for the next Jaunty merge in bug 301340. The fix currently in Intrepid and Jaunty is only partial.
2.3 minimal patch
see attached debdiffs. I worked together with james_w to iron out a few minor kinks still present in even the latest versions. To keep the bug-spam low, I did not attach them here.
2.4 TEST CASE:
install and configure wordpress in hardy (I think the same thing should already be observable in Intrepid, too). log in as a blog admin. You are presented with a message that your installation of wordpress is out of date and you should update.
2.5 regression potential
low. The patch disables certain portions of a page only visible to blog admins. I guess the worst case would be that something becomes unbalanced and the page would not validate as HTML (I assume this indeed happened with the patch as it is now applied in Intrepid) for those users on administrative pages. Browsers are usually quite tolerant of incorrect HTML. pages served to regular visitors are completely unchanged. |
|
| 2008-11-24 15:44:18 |
James Westby |
bug |
|
|
added attachment 'wordpress_hardy.debdiff' (wordpress_hardy.debdiff) |
| 2008-11-24 15:44:44 |
James Westby |
bug |
|
|
added attachment 'wordpress_intrepid.debdiff' (wordpress_intrepid.debdiff) |
| 2008-11-24 15:46:45 |
James Westby |
bug |
|
|
added attachment 'wordpress_intrepid.debdiff' (wordpress_intrepid.debdiff) |
| 2008-11-24 16:05:06 |
Launchpad Janitor |
wordpress: status |
In Progress |
Fix Released |
|
| 2008-11-24 16:26:07 |
Rolf Leggewie |
wordpress: status |
Fix Released |
In Progress |
|
| 2008-11-24 16:26:07 |
Rolf Leggewie |
wordpress: statusexplanation |
fixed for Intrepid, reopening to nominate for hardy. Should this be backported to other releases as well? |
reopening for hardy and intrepid |
|
| 2008-11-24 16:50:51 |
James Westby |
wordpress: status |
In Progress |
Fix Released |
|
| 2008-11-24 16:50:51 |
James Westby |
wordpress: statusexplanation |
reopening for hardy and intrepid |
Hi,
The Hardy and Intrepid tasks are still open, the Jaunty one is closed
with the upload of the merge, which is what the "Fix Released" there
signifies.
Thanks,
James
|
|
| 2008-11-24 16:52:07 |
James Westby |
bug |
|
|
added attachment 'wordpress_intrepid.debdiff' (wordpress_intrepid.debdiff) |
| 2008-12-07 19:04:14 |
Martin Pitt |
wordpress: status |
New |
Fix Committed |
|
| 2008-12-07 19:04:14 |
Martin Pitt |
wordpress: statusexplanation |
|
|
|
| 2008-12-07 19:04:45 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2008-12-07 19:17:11 |
Martin Pitt |
wordpress: status |
New |
Fix Committed |
|
| 2008-12-07 19:17:11 |
Martin Pitt |
wordpress: statusexplanation |
|
|
|
| 2009-01-20 08:54:08 |
Launchpad Janitor |
wordpress: status |
Fix Committed |
Fix Released |
|
| 2009-01-20 08:54:22 |
Launchpad Janitor |
wordpress: status |
Fix Committed |
Fix Released |
|
| 2009-03-10 03:44:00 |
Bug Watch Updater |
wordpress: status |
Unknown |
New |
|
| 2009-06-11 01:39:04 |
Aaron Peromsik |
removed subscriber Aaron Peromsik |
|
|
|
| 2009-07-19 19:47:07 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic/wordpress |
|
| 2009-07-19 19:55:44 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/hardy-updates/wordpress |
|
| 2009-07-19 19:57:10 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/intrepid-updates/wordpress |
|
| 2009-09-19 08:54:08 |
Artur Rona |
tags |
verification-done |
patch verification-done |
|
| 2009-09-19 08:54:57 |
Artur Rona |
wordpress (Debian): importance |
Unknown |
Undecided |
|
| 2009-09-19 08:54:57 |
Artur Rona |
wordpress (Debian): remote watch |
Debian Bug tracker #506685 |
|
|
| 2009-09-19 08:55:14 |
Artur Rona |
cve linked |
|
2008-6762 |
|
| 2009-09-19 08:55:14 |
Artur Rona |
cve linked |
|
2008-6767 |
|
| 2009-09-19 08:55:14 |
Artur Rona |
cve linked |
|
2009-2334 |
|
| 2009-09-19 08:55:14 |
Artur Rona |
cve linked |
|
2009-2335 |
|
| 2009-09-19 08:55:14 |
Artur Rona |
cve linked |
|
2009-2336 |
|
| 2009-09-19 08:55:14 |
Artur Rona |
cve linked |
|
2009-2431 |
|
| 2009-09-19 08:55:14 |
Artur Rona |
cve linked |
|
2009-2432 |
|
| 2009-09-19 08:55:14 |
Artur Rona |
wordpress (Debian): status |
New |
Fix Released |
|
