Bug 116827 - Wordpress 2.0 (version bump)
Bug#: 116827 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: enhancement Priority: P2
Resolution: FIXED Assigned To: superlag@gentoo.org Reported By: shoegoo@gmail.com
Component: Applications
URL:  http://wordpress.org/
Summary: Wordpress 2.0 (version bump)
Keywords:  
Status Whiteboard: 
Opened: 2005-12-26 16:55 0000
Description:   Opened: 2005-12-26 16:55 0000 
Wordpress 2.0 is out, and I was unable to find a version bump request, so here
it is.

------- Comment #1 From Carsten Lohrke 2005-12-26 18:47:38 0000 ------- 
*** Bug 116830 has been marked as a duplicate of this bug. ***

------- Comment #2 From Aaron Kulbe (RETIRED) 2005-12-26 21:18:28 0000 ------- 
Since my dev box is dead, due a failed motherboard, I'm going to have to find
another one of the devs willing to bump this for me.  It might take a little
bit, but I should have this taken care of in the next day or so.

Cheers.

------- Comment #3 From Jakub Moc (RETIRED) 2005-12-26 23:05:47 0000 ------- 
*** Bug 116834 has been marked as a duplicate of this bug. ***

------- Comment #4 From Manuel Friedli 2005-12-29 17:10:47 0000 ------- 
when short PHP tags are disabled in the webserver, there's a problem with
/wp-admin/templates.php. i've already reported this issue upstream, but if you
decide to include an ebuild based on the official WP 2.0 tarball that is served
on the servers now, i thik it would be good to fix the problem. i'll attach a
patch that should fix the problem.

------- Comment #5 From Manuel Friedli 2005-12-29 17:12:09 0000 ------- 
Created an attachment (id=75758) [details]
fix short PHP tags in templates.php

------- Comment #6 From Michael Hampton 2006-01-01 21:17:18 0000 ------- 
Hm, that patch definitely should go upstream.

The upgrade from version 1.5 to 2.0 is a pretty major thing, and 2.0's turned
out to be quite buggy; it might be worth waiting until a bugfix comes out from
upstream.

------- Comment #7 From Aaron Kulbe (RETIRED) 2006-01-01 23:03:58 0000 ------- 
This is what I was thinking, as well.  It has been buggy for me, as well as
many other users.

If I put it in the tree, it's going to package.mask, due to the bugs.

I think it makes more sense just to wait until a 2.0.1 or some other release is
made.

------- Comment #8 From Jakub Moc (RETIRED) 2006-01-04 11:14:27 0000 ------- 
*** Bug 117765 has been marked as a duplicate of this bug. ***

------- Comment #9 From David Grant 2006-01-09 17:26:36 0000 ------- 
Good idea guys, I'm glad I saw this bug. I almost installed wordpress2 today
manually (without ebuild). Didn't realize it was so buggy though!

------- Comment #10 From Jakub Moc (RETIRED) 2006-01-15 00:08:27 0000 ------- 
*** Bug 119045 has been marked as a duplicate of this bug. ***

------- Comment #11 From Carsten Lohrke 2006-01-18 16:43:11 0000 ------- 
*** Bug 119495 has been marked as a duplicate of this bug. ***

------- Comment #12 From Mike Slinn 2006-01-18 17:05:30 0000 ------- 
A checklist of steps for the ebuild to follow when upgrading an existing
installation is described here: http://codex.wordpress.org/Upgrading_WordPress

------- Comment #13 From Aaron Kulbe (RETIRED) 2006-01-18 19:23:45 0000 ------- 
Mike, 

All of what is referred to in that document takes place *after* the ebuild is
upgraded.  That's not relevant to the Gentoo update process.

I will mention again here, for anyone still following this bug, I'm not putting
2.0 into the tree.  We're going to wait until another release comes out.

------- Comment #14 From Jakub Moc (RETIRED) 2006-01-23 08:04:03 0000 ------- 
*** Bug 120056 has been marked as a duplicate of this bug. ***

------- Comment #15 From Mark Shields 2006-01-23 08:24:49 0000 ------- 
Created an attachment (id=77908) [details]
wordpress-2.0.ebuild

wordpress-2.0.ebuild.  Needs work but does install wordpress-2.0 correctly.

------- Comment #16 From Aaron Kulbe (RETIRED) 2006-01-23 08:53:48 0000 ------- 
Mark, 

I mean no offense, so please understand that ahead of time.  Did you read the
rest of the comments on this bug request?

2.0 is *not* going into the tree.  I'm going to wait for at least a released
2.0.1 or newer before putting it into the tree.

Cheers.

Aaron Kulbe
"SuperLag"

------- Comment #17 From Mark Shields 2006-01-23 08:59:45 0000 ------- 
(In reply to comment #16)
> Mark, 
> 
> I mean no offense, so please understand that ahead of time.  Did you read the
> rest of the comments on this bug request?
> 
> 2.0 is *not* going into the tree.  I'm going to wait for at least a released
> 2.0.1 or newer before putting it into the tree.
> 
> Cheers.
> 
> Aaron Kulbe
> "SuperLag"
> 

I don't expect 2.0 to go into the tree.  I posted it for people who use portage
overlay to use the ebuild, since my other post was closed resolved and marked
as duplicate.

------- Comment #18 From Jakub Moc (RETIRED) 2006-01-25 10:47:09 0000 ------- 
*** Bug 120327 has been marked as a duplicate of this bug. ***

------- Comment #19 From Aaron Kulbe (RETIRED) 2006-01-31 18:29:26 0000 ------- 
Version 2.0.1 was released today.  I just commited that to the tree.  Enjoy.

------- Comment #20 From Aaron Kulbe (RETIRED) 2006-01-31 18:30:00 0000 ------- 
Reopen, to set proper resolution.

------- Comment #21 From Aaron Kulbe (RETIRED) 2006-01-31 18:31:16 0000 ------- 
Bumped to 2.0.1

Closing bug RESOLVED - FIXED.