Single file version available here.
Last updated on 2008-06-17.
To discuss, comment here.
| Prev | ||
| Home |
http://www.debian-administration.org/articles/332
What is the correct right way to rebuild package in Debian whilst preventing those packages from being downgraded, without applying a hold upon them?
I've increase the package version number in the packages I've rebuilt, with the intention that they will not be updated when I use "apt-get upgrade".
Unfortunately when I try this I receive the error:
The following packages will be DOWNGRADED:
dvd+rw-tools nget
What's the best approach to custom build packages so as not to interfere with upgrades?
In order not to be overwritten by apt-get, I increased my custom build packages by .1, as shown below:
$ apt-cache policy dvd+rw-tools dvd+rw-tools: Installed: 5.21.4.10.8-1.1 Candidate: 5.21.4.10.8-1
$ apt-cache policy nget nget: Installed: 0.27.1-1.1 Candidate: 0.27.1-1
But still apt-get insists that I have to downgrade them.
T Mon 16 Jan 2006
Hold is exactly the thing you want to do — it's designed exactly for this.
You should hold them and manually rebuild them if there's upgrade and you need it.
jooray Mon 16 Jan 2006
> Hold is exactly the thing you want to do -- it's designed exactly for this.
On giving it a 2nd thought, it does make sence. thanks a lot. I'll do that.
T
You may "pin" some packages (yours or those from Debian) to tell your system how to consider upgrading depending on the package origin. Pin'ing doesn't prevent upgrading, but it allows to prioritize between different apt sources, or even enforce downgrade on specific conditions. See "man apt_preferences".
progfou
Yes, but how do you get informed, that an updated version did get released? I get no information at all, if I pin my self-built packages…
That's why I use the +somethingN modifier on my self-built packages.
Marc
Using the packaging page upon the Debian server you can subscribe to new releases by email.
For example the apachetop package I maintain can be found here - with a form to the left to allow you to subscribe/unsubscribe to new releases.
Steve
the parent is the first post that stated the "best" (maybe not "proper") way of doing it.
actually, it depends on the circumstances which way to best keep a self-built package.
i've never had a self-built package downgraded. you probably need to pin your default distro (stable, testing, unstable, experimental) a little below the automatic install level (990?).
the problem i initially encountered was that if i rebuilt a package, keeping the same version string as the original package (by not altering the changelog), then my version on the next "apt-get upgrade" would be reinstall using the official version (but could be due to my pinning of the official repositories).
if i only wanted to keep my package installed until the next version was released (ie i didn't want to wait for a security update or bug fix to propagate to testing), i just added "0.0.1" to the debian-specific version (ie "-1" -> "-1.0.1"). normally the versioning is <upstream version>-<debian package version>.<minor package revision>, so by adding another decimal and number after the "minor package revision" i've never had a conflict. ("minor package revisions" are not regularly used except for security updates in stable, but i prefer to be safe and not increment that number.)
if i want to manage my own package regardless of newer packages then i hold the package.
echo <package> hold | dpkg --set-selections
i believe upon running "apt-get upgrade" it'll tell you which packages were not upgraded due to holds, so you'll notice when i newer version comes out (but not any subsequent newer versions).
i've found pinning to be too complex and error prone for single packages. i only pin whole distros (stable, testing, unstable) or repositories.
undefined, 16 Jan 2006