building packages from source, and preventing their upgrade

[oz123]

Hi,

I followed http://www.lucas-nussbaum.net/blog/?p=683 and I see a very strange behaviour.

After I build a package from source e.g. with

1) apt-get souce grep
2) cd grep-<version from repo>
3) dpkg-buildpackage -us -uc
4) dpkg -i ../grep-version

everything is fine. But if I do:
5) aptitude update
6) aptitude upgrade

apt wants to re-install the package from the repositories although the version is the same.

So my question is why? Is it because my package is unsigned? If that's not the reason, what is the reason?
And the question is how can I change this behavior in aptitude (i don't want to hold each package I build from source)


This is also the case with synaptic, but not with apt-get upgrade...

I would appreciate it if you find the time to answer me.

Cheers,
Oz

[stevepusser]

There's probably some method using apt/preferences, but what I do is just add an "epoch" to the version in debian/changelog (or bump it up a notch).

Example:

foo (0.1.2-1)

would become

foo (1:0.1.2-1)

It's up to you now to keep on top of security updates.

[oz123]

It's up to you now to keep on top of security updates.

Then it takes the whole point of using a package manager.

apt-get does not try to re-install my compiled package.
aptitude and synaptic do... and I find it rude of them

I hope someone here knows the answer.

[oz123]

bump

[stevepusser]

I meant if you prevent security upgrades by "locking in" your build, you shoud check packages.debian.org to see if there have been any security fixes, and rebuild your version to incorporate the fixes. You can't prevent upgrades without preventing all security upgrades, too.

Wait....
Possibly you could give your build a small point upgrade, then a security upgrade should appear as newer:

Original:

foo (0.1.2-3)

Your build:

foo (0.1.2-3.0.1)