Re: no freshness dating inside Packages.gz

On Mon, Jun 23, 2003 at 03:14:26PM +0200, Martin Schulze wrote: > > > > It is unfortunate, that there is no easy access to the changelog, I know of, > > but all other infos can be seen on the package tracking system: > > I guess that you've never heard of > Any

Re: no freshness dating inside Packages.gz

Martin Schulze wrote: > Bernd Eckenfels wrote: > > On Tue, Jun 17, 2003 at 08:29:14PM -0400, Joey Hess wrote: > > > He wants to know when a particular package was last updated, > > > without > > > having to download it and examine the gzip time stamp and/or > > > changelog. > > > > It is unfortun

Re: no freshness dating inside Packages.gz

On Mon, Jun 23, 2003 at 03:14:26PM +0200, Martin Schulze wrote: > Bernd Eckenfels wrote: > > On Tue, Jun 17, 2003 at 08:29:14PM -0400, Joey Hess wrote: > > > He wants to know when a particular package was last updated, without > > > having to download it and examine the gzip time stamp and/or chang

Re: no freshness dating inside Packages.gz

Martin Schulze wrote: > Bernd Eckenfels wrote: > > On Tue, Jun 17, 2003 at 08:29:14PM -0400, Joey Hess wrote: > > > He wants to know when a particular package was last updated, without > > > having to download it and examine the gzip time stamp and/or changelog. > > > > It is unfortunate, that the

Re: no freshness dating inside Packages.gz

Bernd Eckenfels wrote: > On Tue, Jun 17, 2003 at 08:29:14PM -0400, Joey Hess wrote: > > He wants to know when a particular package was last updated, without > > having to download it and examine the gzip time stamp and/or changelog. > > It is unfortunate, that there is no easy access to the change

Re: no freshness dating inside Packages.gz

On Wed, Jun 18, 2003 at 06:09:55AM +0800, Dan Jacobson wrote: > Sure, "you don't need to know the date, as you are using sid and did > apt-get update, you are assured it's the latest version". Well, one > doesn't need the maintainer field either etc. Here is a good reason for wanting to know the

Re: no freshness dating inside Packages.gz

On Tue, Jun 17, 2003 at 08:29:14PM -0400, Joey Hess wrote: > He wants to know when a particular package was last updated, without > having to download it and examine the gzip time stamp and/or changelog. It is unfortunate, that there is no easy access to the changelog, I know of, but all other inf

Re: no freshness dating inside Packages.gz

I demand that Michael Banck may or may not have written... > On Wed, Jun 18, 2003 at 06:09:55AM +0800, Dan Jacobson wrote: >> But one they forgot when making the spec was some kind of date >> information. > Just subscribe to debian-devel-changes. You can get all the necessary > information from t

Re: no freshness dating inside Packages.gz

Keegan Quinn wrote: > On Tuesday 17 June 2003 03:09 pm, Dan Jacobson wrote: > > Sure, "you don't need to know the date, as you are using sid and did > > apt-get update, you are assured it's the latest version". Well, one > > doesn't need the maintainer field either etc. > > Are you implying that

Re: no freshness dating inside Packages.gz

On Wed, Jun 18, 2003 at 06:09:55AM +0800, Dan Jacobson wrote: > But one they forgot when making the spec was some kind of date > information. Just subscribe to debian-devel-changes. You can get all the necessary information from there. HTH & HAND, Michael -- BWAHAHAHAHAHAHHA MOAHAHAHA

Re: no freshness dating inside Packages.gz

On Tuesday 17 June 2003 03:09 pm, Dan Jacobson wrote: > Sure, "you don't need to know the date, as you are using sid and did > apt-get update, you are assured it's the latest version". Well, one > doesn't need the maintainer field either etc. Are you implying that knowing the date you last update

no freshness dating inside Packages.gz

There are tons of information categories in the apt Packages file. But one they forgot when making the spec was some kind of date information. For unless a maintainer somehow smuggles it in, say in the version number, $ apt-cache policy icom Installed: 19990819-3 Candidate: 20020923-2 otherwis