I can never resist. When a new version is available I have to have it. Upgrade to WordPress 3.3 was seamless. Devils is always in the details though. I’ll probably find a post or a plugin that doesn’t work the same way.
Oh well, I’m on the latest and greatest right?!
So I left all these servers running gentoo a couple years ago. Now, after all this time (and uptime!), I want to install something.
emerge -av portage
These are the packages that would be merged, in order:
Calculating dependencies |
!!! All ebuilds that could satisfy ">=dev-lang/python-2.5" have been masked.
!!! One of the following masked packages is required to complete your request:
- dev-lang/python-2.5.4-r3 (masked by: required EAPI -1, supported EAPI 0)
- dev-lang/python-2.6.2-r1 (masked by: required EAPI -2, supported EAPI 0)
- dev-lang/python-2.6.2-r2 (masked by: required EAPI -2, supported EAPI 0)
- dev-lang/python-2.6.4 (masked by: required EAPI -2, supported EAPI 0)
- dev-lang/python-3.1.1-r1 (masked by: required EAPI -2, supported EAPI 0)
- dev-lang/python-2.6.3 (masked by: required EAPI -2, supported EAPI 0)
For more information, see MASKED PACKAGES section in the emerge man page or
refer to the Gentoo Handbook.
(dependency required by "sys-apps/portage-188.8.131.52" [ebuild])
Hm. Yeah, I’m way out of date.
Solution: I found other sites that talked about forcing a python/portage install but I that sounded a little harsh. Instead, I found a snapshot of portage-2008.0 and replaced my /usr/portage with the contents of that.
rm -rf portage # or mv portage xxx
tar -xjpf portage-2008.0.tar.bz2
ln -s /usr/portage/profiles/default/linux/x86/2008.0 make.profile
emerge -av portage
That took me to portage-184.108.40.206.
From there, I can now go back to current 10.0 portage and emerge -av portage to get up to the current portage state.
Yeah, I really didn’t want to do a re-install.
I just updated all my blogs to WordPress 2.7. I like the new admin interface. The upgrade was pleasantly easy and quick.
It’s been some time since Python 2.5 became stable and released. Version 2.5 has plenty of new features that have helped me in deciding that it was time to go ahead and start using it for primary development of all my new projects. One of the reasons I was still using version 2.4 is that Gentoo hadn’t upgraded 2.5 to the stable package system.
I decided to go ahead and unmask version 2.5 anyway. Installing Python 2.5 isn’t very complicated and I’ll leave the details out. I’ll just mention that after unmasking Python with the ~x86 keyword and installing the package, you’ll need to run the python-updater. Python-updater had it’s own problems with not being able to find some packages it thought needed to be re-emerged but I found pretty much all of those were unneeded old dependencies and I simply un-emerged them.
When you update Python, you can still get to your old version of Python by tacking on the version number to the python command, e.g., /usr/bin/python2.4. Since the Python updater uses emerge to install your python dependencies in the site-packages of your Python installation and emerge unmerges the old versions, your old Python probably doesn’t have all the site-packages any longer. This is only an issue if you find you need the old Python.
For me, I have a couple applications that didn’t quite want to work with Python 2.5 for some reason. I decided to use VirtualEnv to work on those applications.
To install virtualenv, you need setuptools. That package was one of the packages transfered to the 2.5 site-packages install and was no longer available with python2.4.
To get around the issue, use ez_setup.py to install a 2.4 version of setuptools instead of using emerge.
cd <working dir>
/usr/bin/python2.4 ez_setup.py setuptools
- I simply used the virtualenv command that came with python2.5 but changed the interpreter to by python2.4 instead of python.
cp /usr/bin/virtualenv .
# edit virtualenv to have the correct interpreter line
vim < or whatever editor > virtualenv
------ snip local virtualenv ------
------ snip ----------------------
./virtualenv --no-site-packages <virtual env install dir>
cd <virtual env install dir>/bin/
ln -s python2.4 python
cd <working dir>
- Use the old python in it’s virtual environment:
source <virtual env install dir>/bin/activate
Python 2.4.4 (#1, Mar 5 2008, 10:47:15)
[GCC 4.1.2 (Gentoo 4.1.2)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
Anyway, that’s it. You can have a virtual environment that uses any version of Python you like on your system. I imagine this procedure would be somewhat similar on pretty much any Linux Distribution.
I’m a sucker for bleeding edge technology. After posting before about upgrading to the 8.42.3 ati drivers, I realized I was using Xorg-X11 7.2, not 7.3, which is the latest. The latest 7.3 ebuild contains a block on the ati drivers. The block is no longer necessary though because the 8.42.3 drivers are compatible and have xorg-server 1.4 support built in.
Here is what I did to upgrade. Continue reading “Upgrading to Xorg-X11 7.3 with ati-drivers 8.42.3 on Gentoo”
I’ve barely completed an upgrade to WordPress 2.3. Out of many new improvements, one which stood out to me is the integrated tagging support. No longer, is it necessary to download one of the many tagging plugins.
Some things I noticed during the upgrade:
- My existing tagging plugin broke at the time of the upgrade. I found, after searching on Google, that some of the database schema that most tag and link plugins depend on was removed. (wp_post2cat et. al.) Simply disabling my two plugins for Simple Tagging fixed the database error message at the top of the pages
- WordPress has importers for a lot of tagging widgets. All I had to do was go to the “Manage” tab and choose “Import”. Importing the tags worked flawlessly.
- The new tag cloud widget applies unique styles to each tag. They are in the format < a class=”tag-link-$tag_id” … >. To get around the tags not having a style, I modified my style sheet and added color and link styles to the container div that the tag widget is in.
- I had to modify my page template to print a list of tags at the bottom of each post. There is a pretty good reference for that here.