On Monday 14 November 2011 2:37:44 am Laurent Dard wrote:
> Le 14/11/2011 02:41, Greg Madden a écrit :
> > Thanks for the script, not something I would figure out myself.
>
> Thanks for the feedback.
>
> > I have used it successfully on three 3.5..13 machines here, though they
> > were running okay.
>
> If we had kept "3:3.3.8-d-" versions installed, it would have been okay to
> run trinity now but we would have been unable to upgrade in the future
> (until qt >= "3:3.3.9").
>
> (The tricky thing I understood is that dpkg considers that "3:3.3.8b" is a
> greater version than "3:3.3.8-d" BUT it also considers that "3:3.3.8-d-" is
> greater than "3:3.3.8d", "3:3.3.8e" and so on.)

Following is what Debian Squeeze, or apt-cache policy, thinks about versioning.

Should there be both the 3:33:3.3.8d  3:3.3.8-d in the repos at this time? When I 
do an 'update' on my system, 3:3.3.8-d always wants to be installed ...again. I 
have put  3:3.3.8-d on hold as a work around, just wondering if both opies of the 
package need to be in the repos.

$ apt-cache policy libqt3-mt
libqt3-mt:
  Installed: 3:3.3.8d-0ubuntu0+sr73+pr181~squeeze
  Candidate: 3:3.3.8-d-0ubuntu0+sr73+pr181~squeeze
  Version table:
     3:3.3.8-d-0ubuntu0+sr73+pr181~squeeze 0
        500 file:/pub/ TDE_3.5.13/ Packages
 *** 3:3.3.8d-0ubuntu0+sr73+pr181~squeeze 0
        500 
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/debian/ 
squeeze/main amd64 Packages
        500 
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/ubuntu/ 
squeeze/main amd64 Packages
        100 /var/lib/dpkg/status
     3:3.3.8b-7+b1 0
        990 http://192.168.0.4/debian/ squeeze/main amd64 Packages

-- 
Peace,

Greg