* Josip Rodin <[EMAIL PROTECTED]> [2003-04-07 13:27]:
> On Mon, Apr 07, 2003 at 10:48:13AM +0200, Gerfried Fuchs wrote:
>>  And that's not better, thats even bader.  The version in testing _is_
>> 2.3.1-16.  The question is, _why_ this is happening.  I see that it
>> shows somehow the version of the security updates for testing instead of
>> the testing version on packages.debian.org.
> 
> This is inverse from what #153556 wants.

 No, it is not.  I may cite the title: "as appropriate".  apt-get won't
get you version 2.2.5-woody.3 but will get you 2.3.1-16.  This is
nothing that I would call "appropriate" for it is counter-intuitive and
counter-realistic.  If the version from testing-security would be
actually *newer* I would say yes, it is correct.  But it is not.

 The current status quo is:

 stable | security     | packages.debian.org | apt-get      | correct
 =======T==============T=====================T==============T========
   1.0  | n/a          | 1.0                 | 1.0          | [X]
   1.0  | 1.0-stable.1 | 1.0-stable.1        | 1.0-stable.1 | [X]
   1.0  | 0.9-stable.1 | 0.9-stable.1        | 1.0          | [ ]
   n/a  | 1.0-stable.1 | 1.0-stable.1        | 1.0-stable.1 | [x] (1)

 Footnote:
 (1) Joey would like to see this as an error, too, and packages.d.o
display nothing.  On the other hand it would behave differently than
apt-get in that respect.

 I don't think that packages.debian.org should work differently than
apt-get.  It is not a good idea to have it behave differently.  And I
really /don't/ think that this different behavior was the intention of
era's request.

 So long,
Alfie
-- 
"Life is too important to take seriously."
                -- Corky Siegel

Attachment: pgpvXfAiOKnN0.pgp
Description: PGP signature

Reply via email to