Update on Michael’s Domain

Updating drupal

Tue, 19 Feb 2013 00:00:00 +0000

Here’s what I need to to to update drupal (minor updates, e.g. from 7.18 to 7.19) on my Ubuntu server. I have installed drupal from the drupal source itself and not from the Ubuntu repository (because the Ubuntu repository is usually quite old and not updated as frequently). Actually the update is quite painless; I am sure somebody automated that already somewhere…cd /var/wwwsuwget http://ftp.drupal.org/files/projects/drupal-7.19.tar.gztar -xvzf drupal-7.19.tar.gz chown -R jeltsch:www-data drupal-7.19rm drupal-7.19.tar.gz cp -a drupal-7.18/sites/ drupal-7.19/The above cp command makes a copy of the complete site, which can take a long time and use lots of disk space. Instead, you can delete the “sites” subdirectory in the new drupal folder and make a link to the old “sites” subdirectory:cd drupal-7.19rm -rf sitesln -s ../drupal-sites/ sitesHere you should log into your site and put it into maintenance mode! mysqldump -u root -p --databases drupal7_jeltsch_org drupal7_claudia_jeltsch_org drupal7_lammertlab_org > drupal7_all.sqlrm drupal7ln -s drupal-7.19/ drupal7Here you should click the link to the update script. After the updates were successfully performed you can put your site online again.** ****Drupal 9**Updating Drupal 9 is most easily done using composer:composer update "drupal/core-*" --with-all-dependenciesAlso the modules can be updated. However, in my case the update was not always targeting the module that was actually in use but a module that was lower in the priority list in some other directory. For minor version updates:composer update drupal/modulename --with-dependenciesFor major version updates:composer require drupal/modulename:^2.0After this, don’t forget to visit https://yoursite.com/update.php !

Updating Suse Linux 9.0 to 9.1

Wed, 04 Apr 2007 00:00:00 +0000

The .0 to .1 update suggests, that it’s not a big deal. In fact, it is. Many things do brake and most people advise to do a clean install of 9.1. Because of extensive third party installations and customization I wanted to upgrade. In case the upgrade appeared unusable, I wanted to have the possibility to go back to 9.0. This appeared easily possible because we had a free 8.6 GB partition (hdb3) on the harddisk. Actually it was not free, but it was the root partition of our RedHat 9 installation. I did the following things: I wanted to preserve all the user-specific configurations. Thus I backed up all the hidden files and directories from the main user’s home directory: tar -cvf configuration_files.tar .[a-zA-Z0-9]* Then I reformatted hdb3 (it was ext3) into reiserfs via Yast Then went into runlevel 1 with sudo /sbin/telinit 1 and mounted the newly formatted partition mount /dev/hdb3 /redhat Then I duplicated the current root partition (/dev/hdb2) cd redhat cp -ax / . Then I edited /redhat/etc/fstab: I changed the entry for the root partition from /dev/hdb2 to /dev/hdb3. The current root partition (/dev/hdb2) uses already reiserfs, so no other changes are needed here. However, you have to uncomment all “special” file systems. Otherwise the Suse Installer will try to mount these and fail and then give you some bogus error messages. I had e.g. two entries for colinux (/dev/cob2 /) and got the following error message: " The root partition in /etc/fstab has a wrong root device. See http://portal.suse.com/sdb7en/2004/01/sata.html" . Also special file systems create similar trouble. I first left the proc, usbfs, etc. entries and got again an error: “Partitions could not be mounted.” Then I edited the fstab and left only /, /boot, swap, /home and then the Suse installer managed. Then I edited /boot/grub/menu.lst and added an entry for the new system (I just duplicated the existing, renamed it and changed the root partition from to hda3; additionally I specified vmlinuz and initrd directly and not via symbolic links as the links will point to thefiles of the new kernel after the upgrade). Before I started the actual installation I checked that I can select in grub both installations and successfully boot During installation the installer complained about 1200 conflicts. Most of them I ignored as many packages of the old system had been manually added and were too new for the 9.1 installer CD. But since I was going to update online immediately after the install, this shouldn’t be much of a problem. I also chose to keep installed packages that are not any longer maintained.

Updating gallery via CVS

Tue, 06 Mar 2007 00:00:00 +0000

Run as root cvs update -Pd in the gallery2 directory
Once your files have been updated, open up your Gallery 2 in your web browser and it will take you right to the upgrader automatically
More info if needed on the Gallery site

Updating gallery

Mon, 14 Aug 2006 00:00:00 +0000

Backup the albums, the working gallery code and dump the databases
Put all the Gallery sites into the maintanance mode
Get the newest full version of Gallery
Unzip the file over the existing version of the Gallery
Navigate as an admin to the main page
Run the updater
Run the cleanup script if necessary
Check whether everything works fine
Change the sites mode to active