On Monday, 23 January 2012 at 18:05, Jaimos Skriletz wrote: > The last note is the debian package for some reason (I am still unsure > why Manjo did this) has an epoch version and the package you made will > not. Because of this epoch version the version in the debian repos > 1:2.5.30 is considered greater than the version you compiled 2.6.3 for > instance, and if you upgrade/dist-upgrade you system it will install > the version from the debian repo effectivally downgrading your fvwm > package. To prevent this you need to put the fvwm package on hold
Looks like a typo in 2005 was the cause: fvwm (2.5.130.CVS.2005.07.19.01-1) unstable; urgency=low fvwm (1:2.5.13-0.CVS.2005.08.08.01-1) unstable; urgency=low So to have apt recognize the 2.5.13 package as larger than 2.5.130, the epoch was necessary. Solution: set the epoch of dpkg scripts in the source distribution to something like 10, then it'll take a while until the repo package overrides the custom one (assuming that someone who compiles a custom package doesn't want it autoupgraded to a repo package at some random point in time).
