Tue, 15 Apr 2008
Install Package Dependencies After a DPKG Package Install
I've had a couple of people mail asking about my "frigging apt" comment in a previous
post (the last paragraph). It's actually as simple as the comment
implies. Here's an example -
wget http://ftp.dk.debian.org/debian/pool/contrib/v/vmware-package/vmware-package_0.22_i386.deb
dpkg -i vmware-package_0.22_i386.deb
apt-get install -f
# get prompted about installing lots of packages
I don't have any really well thought out reasons to not like this approach - in the few cases I've tried it I've found it to work; it just feels a little... icky.
Like this post? - Digg Me! | Add to del.icio.us! | reddit this!
Posted: 2008/04/15 16:44 | /operatingsystems/linux/debian | Permanent link to this entry | This entry and same date
Rebuilding Debian Packages - Debian Delvings
Ever wanted a Debian package to be just a -little- bit different?
Here's how.
While most of the software we're pulling in from Debian is fine for our
uses there are a couple of applications that we'd like to be a little
different than the stock versions. Rather than go away and package them
ourselves (which would require a lot more packing skills and time than I
currently have - improving those skills is one of the reasons I'm doing
this series) it's possible to download a source version of a Debian
package, make a small amendment and then repackage it for personal use.
In this example we'll have a look at how to do this with NginX, a very fast and stripped down
webserver I'm evaluating for a couple of services.
Firstly let's be nosey and have a look at the Nginx source package.
Assuming you have a deb-src line in your
/etc/apt/sources.list file getting a copy of the source
package is as simple as apt-get source nginx; it's worth
noting that this command doesn't need you to be root to run. While we're
here let's pull down the dependencies required to rebuild nginx once
we've made our modifications - sudo apt-get build-dep nginx
- note the build-dep argument - and then pull down the other packages
required but are not specific to this package.sudo apt-get install
build-essential devscripts fakeroot (sudo or as root).
It's a bit of a tangent (and an annoyance) but the package of Nginx in Debian stable (nginx 0.4.13-2) has a Nginx package removal bug that stops you from removing the package without hacking the init script. I only point this out as when I was trying to learn how to repackage I couldn't remove it and so assumed I'd broken something.
Before we make any amendments to the package let's try and rebuild
it. cd in to the versioned source directory (nginx-0.4.13 in our
example) and run debuild -us -uc. A few screens of text
later and we've got a package - ../nginx_0.4.13-2_i386.deb.
Now we know we can round trip let's be intrusive and make some amendments to the package. We'll add an optional module (http_realip_module) to the nginx package (you should be able to do something like this to add SSL support for example. In this case it's a small, one line, change -
$ cd nginx-0.4.13 # this is the etch version when I wrote this
$ vi debian/rules # add '--with-http_realip_module' to the ./configure line.
$ dch --nmu "Rebuild of package and addition of the http_realip_module module"
$ vi debian/changelog # change the name and email as required.
# build the new package with the extra module
$ DEBFULLNAME="Dean Wilson" DEBEMAIL=dwilson@example.com debuild -us -uc
$ ls -alh ../nginx_0.4.13-2.1_i386.deb
# if you have a repo drop it in now and regenerate the index for clients to see it.
dch simplifies adding changelog entries to
debian/changelog. The two variables before the command tell it who's
made the change. In our case we're logging that we added the new
module and that this package is a "Non maintainer upload" (NMU). This
is important for future users of the package - in essence we're
taking responsibility for the repack away from the oringinal
maintainer, who knows nothing of the changes you've made, and making
ourselves the correct contact point. And if you don't do this lintian
will complain when you build the package.
Closing notes - you may need to pin or hold the package to stop it getting overwritten when future (maintainer) upgrades become available - but that's outside the scope of this post.
Bonus Debian Nginx package Evil. Bad idea but useful for some testing I was doing.
Like this post? - Digg Me! | Add to del.icio.us! | reddit this!
Posted: 2008/04/15 08:11 | /operatingsystems/linux/debian | Permanent link to this entry | This entry and same date
Creating Virtual Debian Packages - Debian Delving
Now that we have a local apt repository we can start to
fill it with our own custom goodness. One of the first things I'm going
to need is virtual packages. At work we'll be using them to pull
reusable components together in to a number of full applications (and
using the apt mechanisms to force upgrades when a component changes) and
to group Nagios plugins (we'll be packaging some of those in a later
blog post) in to sensible sections; we're going to have a lot of Nagios
plugins.
Unfortunately I can't talk about those in detail on a public website that not enough people read, so we'll need a more contrived example. Although I understand the reasons behind it (and appreciate them on servers) the fact that Debian doesn't have a perl package that INCLUDES THE CORE PERLDOC bites me every now and again so we'll make our own perl package that pulls in a handful of the existing packages.
Tangent - I think the three packages should be perl-base, perl-modules and perl-doc which anal people like me can pick for their systems. The perl package should be a virtual one that includes (and forces the install of) all three of those so you get a more intuitive setup for people that don't need huge amounts of customisation. This could also be done with Ruby to hide some of the bat shit splitting of it's libraries under Debian. But that's all personal opinion; and now I've got virtual packages and an apt repo I can do what I want. Bwhahahaha.
While I was trying to work out how to do this I found the equivs package and it's got one of the best descriptions I've ever read:
$ apt-cache show equivs | less
... snip ...
Description: Circumvent Debian package dependencies
This package provides a tool to create Debian packages that only
contain dependency information.
.
One use for this is to create a meta-package: a package whose sole
purpose is to declare dependencies and conflicts on other packages so
that these will be automatically installed, upgraded, or removed.
... snip ...
In additional to being a very clear statement of intent this is obviously the command for us. So how do we use it?
# on the build machine, which also hosts our sample repo.
$ apt-get install equivs
$ equivs-control perl-full
# edit the file to suit - example linked to from the next paragraph
vi perl-full
# build the meta package
equivs-build perl-full
# copy it in to our repo - which lives under
cp perl-full_1.0_all.deb $repo_base/dists/pool/main/
# rebuild the index
pushd $repo_base && apt-ftparchive generate $repo_base/apt-ftparchive.conf
Here's an inline version of the perl-full example control file that I used.
Section: misc
Priority: optional
Standards-Version: 3.6.2
Package: perl-full
Version: 1.0
Maintainer: Dean Wilson <dean.wilson@example.com>
Depends: perl,perl-doc,libdbi-perl
Architecture: all
Description: Perl install that includes perl-doc and libdbi-perl packages.
I'm fed up of installing perl and not getting perl-doc. This virtual
package fixes that for my local systems and any other that can reach my
apt repo
.
I don't recommend anyone else using this as it was written as an
experiment and to voice how much having to install perl-doc bugs me.
Oh, and this isn't a good example of a description. Look at real Debian
packages for much better ones.
On the client you can do an apt-get update ; apt-get install -s
perl-full and you should get a list of the packages that will be
installed, which on a system that's not already got a perl install should
now include perl-doc.
While this example is a bit forced (and very opinionated) the technique and technology behind it are useful tools that are worth knowing.
Like this post? - Digg Me! | Add to del.icio.us! | reddit this!
Posted: 2008/04/15 08:05 | /operatingsystems/linux/debian | Permanent link to this entry | This entry and same date
Creating a Personal Apt Repository - Debian Delving
Ever wanted your own apt-repo? If not hit the back button
about.... now.
My new employers are going to be very Debian heavy on the systems side of the project I'm on so I'm currently in the process of sharpening my Debian specific skills (I've always tried to avoid Unix solutions that were tied to a single OS or distro but in this case we might as well do it The Debian Way).
One of the first things to come up was the need for a local apt repository - for internal packages, third party ones we wanted to use, some backported from other Debian releases and even some rebuilt ones. In this, the first of who knows how many, Debian focused blog post I'll be describing my first pass at setting up a repo for holding these and how I'm using it. I should probably say that this is all from bits and pieces I've picked up across the web so be careful before you blindly follow my advice.
First of all let's set a victory condition - I want to be able to
apt-get install puppet and have it install the version
currently from testing (Lenny as I write this) under a stable system (Etch)
without any pinning, apt magic etc. Before we start, run apt-get
install -s puppet | grep 'Inst puppet' and see what version you get
back - I get 'Inst puppet (0.20.1-1 Debian:4.0r3/stable)' so it'll be
pretty easy for me to see if this works; when it does the version number
will change.
We're going to serve packages over http so you'll need a webserver
(apt-get install apache2 in my experiments) and a couple of
other debian packages (apt-utils and bzip2). Rather than go in to a line
by line description grab my simple make-repo.sh
Debian Repository creation script and my
sample apt-ftparchive.conf.
Once you've got local copies of both, had a quick look at them (you
wouldn't run arbitrary shell scripts you've downloaded from the net would
you?) and made any config adjustments run make-repo.sh and
watch as it adds directories to your system. You now have a skeleton repo
on your machine; but without any packages it's about as much use as a
Westham fan at a cup final. So let's add a package.
$ cd dists/pool/main/ # this is under your repo base
# grab the puppet version from lenny (at time of writing)
$ wget http://ftp.de.debian.org/debian/pool/main/p/puppet/puppet_0.24.4-3_all.deb
# generate the index files
$ cd /var/www/debian # my repo base
$ apt-ftparchive generate /var/www/debian/apt-ftparchive.conf
On the client side edit /etc/apt/sources.list and add a
line that looks like deb http://apt-repo.example.com/debian/ etch
main - replacing apt-repo.example.com with your web host. Do an
apt-get update and you should get a couple of 'Ign'
warnings but all should work. If not, then get debugging. Now for the
moment of truth, on the client -
$ apt-get install -s puppet | grep 'Inst puppet'
Inst puppet (0.24.4-3 apt-repo.example.com)
You now have a local apt repository with a sensible version of puppet ready for use by all your Etch hosts. It's also a good building block for fulfilling some of our other requirements. But well get to those in other blog posts. Now go and add the process and website checks to Nagios.
Notes - while you can pull the packages down and dpkg -i
them one by one on each machine this requires you to copy them to each
host and (this is the annoying part) install the dependencies by hand
(yes, you can frig this with apt-get -f and let it try to do this for
you but that's horrible). I should also say that if I'm doing any of
this horribly wrong then feel free to mail me with corrections. I'd
love to know how the Debian pros do it. (don't send me emails with the
word "Alone").
Like this post? - Digg Me! | Add to del.icio.us! | reddit this!
Posted: 2008/04/15 08:01 | /operatingsystems/linux/debian | Permanent link to this entry | This entry and same date
Copyright © 2000-2010 Dean Wilson
