forwarding ..
----- Forwarded message from sean finney <[EMAIL PROTECTED]> -----
From: sean finney <[EMAIL PROTECTED]>
Date: Sun, 4 Jun 2006 07:03:26 -0400
To: Michael Ablassmeier <[EMAIL PROTECTED]>
Subject: Re: [Dbconfig-common-devel] dbconfig-common: wrong handling of
versions including epoch?
Cc: [EMAIL PROTECTED]
hi michael,
On Sun, Jun 04, 2006 at 11:35:35AM +0200, Michael Ablassmeier wrote:
> [..]
> applying upgrade sql for 1.1beta9-2 -> 1:1.1-1.
> applying upgrade sql for 1.1beta9-2 -> 1.1beta10.
> applying upgrade sql for 1.1beta9-2 -> 1.1beta12.
> [..]
>
> this is not a problem as the changes from 1.1beta12 to 1:1.1-1 are trivial and
> do not depend on earlier patches, however, this doesnt seem right to me, the
> patch for 1:1.1-1 should be applied *after* the patches for 1.1beta10 and
> 1.1beta12. Am i right?
i think so, yes. dbconfig-common should defer to "dpkg --compare-versions"
for version ordering, and:
numanuma[~]12:53:22$ dpkg --compare-versions 1:1.1-1 lt 1.1beta10
numanuma[~]12:54:26$ echo $?
1
taking a closer look at things, it seems like there's a bug in the
postinst helper script where it uses plain old "sort" for generating the
list of available upgrades. so hey, thanks for finding that :)
i'll take a look at fixing that RSN, but feel free to open a bug report
if you want to know when the fix goes into unstable.
sean
----- End forwarded message -----
bye,
- michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
