Hi David. On Fri, 2012-03-16 at 18:54 +0100, David Kalnischkies wrote: > Your problem is that you think that it is the same version. Just because it > has the same version number doesn't mean that it is the same version. > APT has in your case three versions with the same version number: > - the one from debian > - the one from you > - the one you have installed Yeah I've understood that but.. see below... > For these two we need to choose one to be above the other, for us it is the > version which is parsed at first, so move the deb-line for your archive above > the one for debian and you should be "fine". ...it's _really_ strange that this happens even though you set a higher priority?! I mean a) what the manpage says, by the words I've quoted before is that first it doesn't downgrade, then it takes the highest priority version (which would be mine in my example)... So this must mean that reinstalling the same version is considered as downgrading... Of course the 3 "versions" are considered different... but then the rule: take the one with highest prio, unless you'd have to downgrade should match. > I would recommend to avoid the practice of rebuilding with the same version- > number through. It's harder to find out if its an official or a self-build > package in case of a bug and you have problems like this one. Well it has it's problems,.. but if I change the version number, how can I guarantee, that the maintainer/security team chooses one that is considered as higher, than mine... > Especially, it gets insane if you have applied a patch but for some strange > reasons the package ends up having the same metadata as the one from > debian - APT will then think that these are the same versions … Well in that case it's not really a patch (technically it is but not functionally)... I change the DH parameters in NRPE,... which is like exchanging the host key of ssh... Thanks, Chris.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature