Wednesday, 12 January 2011

Backports and meta-packages

I've just made an edit on the Puppet+Nginx+Unicorn entry a couple of posts back to include:
  • rubygems 1.3.4-1~bpo50+1 via backports <- Not actually required for this, but many things require the meta-package as well as the versioned package so getting them together can save you some headaches.


I think this is fairly important as a rule of thumb - if you're installing from backports, you should really check for the associated meta-packages as it can cause dependancy problems later on with other packages should you not have them. I was just installing mcollective on my puppetmaster test rig, and I ran in to this problem.

As I've said before, it's usually easiest to set up your own debian repository using reprepro if you're going to install custom-baked debs simply because it saves on headaches.

0 comments:

Post a Comment

All comments and questions are welcome, just remember that I may not know the answer as I've only worked on my particular implimentation, and I have no responsibility to help you debug your problems.

That said, fire away!