Apr 19 2013

Evolution Woes and yum magic

I`m an oldschool guy .. I still love pop3(s) to get my mails locally and read them with my fat email client. Evolution.

So when gmail breaks their pop/imap infra I`m screwed for a while. I hate reading mail from a web gui and the collapsed threading model gmail uses makes me nauseus.

So I fiddled with my config .. disabled it.. deleted the account.. created it again. But even after gmail was up again . I couldn't access my mail from my favourite client. Yet from other clients it seemed to work.

This obviously is real fun when you are travelling and trying to keep an eye on a number of different email threads ..

So I`m back home from Paris now and spend some 10 minutes figuring out what could be wrong.

I ran into https://bugzilla.redhat.com/show_bug.cgi?id=949180 which points out that for newly created there is a problem with the keyring prompting

And refers to https://bugzilla.redhat.com/show_bug.cgi?id=953641 accounts Which states that gcr-3.6.2-3 breaks password prompt/keyring unlocks.

And indeed ..

  1. yum shell
  2. Loaded plugins: langpacks, presto, ps, puppetverify, refresh-packagekit
  3. > remove gcr
  4. > install gcr-3.6.2-1.fc18
  5. adobe-linux-x86_64 | 951 B 00:00
  6. fedora/18/x86_64/metalink | 31 kB 00:00
  7. google-chrome | 951 B 00:00
  8. google-earth | 951 B 00:00
  9. google-talkplugin | 951 B 00:00
  10. rpmfusion-free-updates | 3.3 kB 00:00
  11. rpmfusion-nonfree-updates | 3.3 kB 00:00
  12. updates/18/x86_64/metalink | 24 kB 00:00
  13. rpmfusion-free-updates/primary_db | 279 kB 00:01
  14. > run
  15. --> Running transaction check
  16. ---> Package gcr.x86_64 0:3.6.2-1.fc18 will be installed
  17. ---> Package gcr.x86_64 0:3.6.2-3.fc18 will be erased
  18. --> Finished Dependency Resolution
  20. ================================================================================
  21. Package Arch Version Repository Size
  22. ================================================================================
  23. Installing:
  24. gcr x86_64 3.6.2-1.fc18 fedora 627 k
  25. Removing:
  26. gcr x86_64 3.6.2-3.fc18 @updates 2.3 M
  28. Transaction Summary
  29. ================================================================================
  30. Install 1 Package
  31. Remove 1 Package
  33. Total download size: 627 k
  34. Is this ok [y/N]: y
  35. Downloading Packages:
  36. gcr-3.6.2-1.fc18.x86_64.rpm | 627 kB 00:02
  37. Running Transaction Check
  38. Running Transaction Test
  39. Transaction Test Succeeded
  40. Running Transaction
  41. Installing : gcr-3.6.2-1.fc18.x86_64 1/2
  42. Cleanup : gcr-3.6.2-3.fc18.x86_64 2/2
  43. Verifying : gcr-3.6.2-1.fc18.x86_64 1/2
  44. Verifying : gcr-3.6.2-3.fc18.x86_64 2/2
  45. Removed:
  46. gcr.x86_64 0:3.6.2-3.fc18
  47. Installed:
  48. gcr.x86_64 0:3.6.2-1.fc18
  50. Finished Transaction
  51. > quit
  52. > Leaving Shell

Solved the problem

Feb 16 2010

Packaging Drupal Modules or not ?

So John wrote down his experiences on deploying Drupal sites with Puppet .

It's not a secret that I've been thinking about similar stuff and how I could get to the best possible setup.

John starts of with using Puppet to download Drush... while I want to use rpm for that ...

I want my core infrastructure to be fully packaged... not downloaded and untarred. I want to be able to reproduce my platform in a couple of months , with the exact same versions I`m using now .. not with the version that happens to be on ftp.drupal.org at that point in time, or with ftp.drupal.org being down.

Now the next question off course is what's the core infrastructure.
Where does the infrastructure end and does the application start. There's little discussion about having a puppet created vhost , an apache conf.d file, a matching .htaccess file if wanted , and the appropriate settings.php for a multisite drupal config.

There's also little doubt to me on using drush to run the updates, manage the drupal site etc . Reading John's article made me think some further about what and when I want things packaged.

John's post lead to a discussion on #infra-talk on getting all drupal modules packaged for Centos with Karan and some others

In a development environment I probably want to have periodic drush updates getting the latest modules from the interwebs and potentially breaking my devs code. But making sure that when you put a site in production it will be on a fairly up to date platform, and not on the platform you started developing on 24 months ago.

In a production environment however you only want tested updates of your modules as indeed they will break code.

It's probably going to be a mix and match setup having a local rpm/deb repo with packaged modules that have been tested and validated in your setup and using drush to enable or configure them for that production setup.

But also having a CI environment wher Drush will get the new modules from the interwebs when needed. and package them for you.

To me that sounds beter than getting all the available Drupal modules and packaging them, even automated, and preparing a repository of those modules of which only a small percentage will actually be used by people.

But I need to think about it some more :)

Feb 16 2010

To not yum or to not apt-get, that's NOT the question.

Over at the OPenARK blog Shlomi Noach argues that using apt-get or yum to install your MySQL instance will one day most likeley break your MySQL setup. Depdendencies, distros not shipping the MySQL version you want to use and on some distro's indeed the mysql vs MySQL issue, agreed, it all makes things less trivial.

However why give up a clean packaged system if there are other ways out ?

First of all by claiming that such an installation can break a working production environment looks to me like admitting you don't have a split development, production environment and that rather than testing stuff upfront indeed you just hack a long in production.

So rather than using a tarball for the MySQL instance an --force to satisfy the missing dependencies (hence also cluttering your system) , a much cleaner and less error prone setup is to only deploy from your own , self controlled repository , in which you only allow tested packages, most probably not the distro based package , hence packages that won't break your setups ;) But still you will be using apt or yum and deploying rpm's and debs , perfectly satisfying dependency needs.

Apart from that .. watch out for Banquise .. :) Coming to your favourite distro soon..

Apr 18 2008

Yummie MySQL Repository

It seems like Jeremy wants to be MySQL community president this week :)

The announcement of a MySQL yum repository is a good one but it's slightly confusing me .. didn't Jeremy already have this with
Dorsal, where there are also 5.1 builds. So what's the difference between Dorsal and the new yum repo anyway .

But he asks for Adittionals packages , well 5.1 to start with, apart from that the CentosPlus repo also has builds for Cluster , having a uniform place go get those to would be good.

And what about builds for CGE ?
Oh and while you are at it .. can you run genbasedir also .. that way we can also use apt4rpm :)

Now I all need is a repository with all drupal modules packaged separatly :)

Feb 12 2008

Apt to the rescue

So while upgrading python from a limited local repository I broke yum

  1. [root@NTC-BASE-2 ~]# yum -y install foo
  2. Traceback (most recent call last):
  3. File "/usr/bin/yum", line 28, in ?
  4. import yummain
  5. ImportError: No module named yummain
  6. <code>
  8. However apt was still working
  9. <code>
  10. [root@NTC-BASE-2 ~]# rpm -e yum
  11. [root@NTC-BASE-2 sources.list.d]# apt-get update
  13. Fetched 3980kB in 8s (478kB/s)
  14. Reading Package Lists... Done
  15. Building Dependency Tree... Done
  16. [root@NTC-BASE-2 sources.list.d]# apt-get install yum
  17. Reading Package Lists... Done
  18. Building Dependency Tree... Done
  19. The following extra packages will be installed:
  20. yum-metadata-parser
  21. The following NEW packages will be installed:
  22. yum yum-metadata-parser
  23. 0 upgraded, 2 newly installed, 0 removed and 234 not upgraded.
  24. Need to get 419kB of archives.
  25. After unpacking 1412kB of additional disk space will be used.
  26. Do you want to continue? [Y/n] y
  27. Get:1 <a href="http://mirror.centos.org" title="http://mirror.centos.org">http://mirror.centos.org</a> centos/4/apt/i386/os yum-metadata-parser 1.0-8.el4.centos [24.0kB]
  28. Get:2 <a href="http://mirror.centos.org" title="http://mirror.centos.org">http://mirror.centos.org</a> centos/4/apt/i386/os yum 2.4.3-4.el4.centos [395kB]
  29. Fetched 419kB in 1s (417kB/s)
  30. Committing changes...
  31. Preparing... ########################################### [100%]
  32. 1:yum-metadata-parser ########################################### [ 50%]
  33. 2:yum ########################################### [100%]
  34. Done.
  35. [root@NTC-BASE-2 sources.list.d]# y
  36. [root@NTC-BASE-2 sources.list.d]# yum update
  37. Setting up Update Process
  38. Setting up repositories

Back in business :)

Good idea Raskas :)

Aug 31 2007

Identifying the Distribution of a Linux System

So Russel is wondering how to figure out what platform you are on by adding a script or so that will tell you you are on a RPM based machine when trying to run dpkg or tell you you need to use rpm.

Imvho that system is broken .. as everybody with some brains uses apt, even on an rpm based system.