So the way to fix this to release 1.2.1-5 the works with pppd 2.4.2 (depends on ppp 2.4.2), then release 1.2.1-6 that works with pppd 2.4.3 (depends on ppp 2.4.3). That way the latest version that depends on the version of ppp in testing will work with the same version.
so take pptpd 1.2.1-2 and re-release it as pptpd 1.2.1-5? (depends ppp 2.4.2), and then you can take pptpd 1.2.1-4 as pptpd 1.2.1-6 (depends ppp 2.4.3). On 4/20/05, Colin Watson <[EMAIL PROTECTED]> wrote: > On Wed, Apr 20, 2005 at 11:29:34AM +0200, Norman Rasmussen wrote: > > * Updated depends on ppp to 2.4.3-20041231 to prevent automatic > > upgrades of pptpd in sarge. In fact, the only change to the version > > presently in sarge is the update of headers for the new ppp, so > > reflect this in the depends. > > Thanks to Norman Rasmussen for actually suggesting this simple fix for > > this bug report. > > Closes: #305012: logwtmp plugin is for pppd version 2.4.3, but version > > is 2.4.2 > > > > Now the trick is to remove 1.2.1-3 from testing somehow, otherwise apt > > will still see it as a valid install candidate. i.e. undo the > > automigration of the previous package to testing. > > No, packages may never regress their version numbers in any suite, > including testing; this is an absolute rule for a number of good > reasons. pptpd 1.2.1-4 can be promoted to testing once the corresponding > version of ppp is in testing. > > Cheers, > > -- > Colin Watson [EMAIL PROTECTED] > -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.org/