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 http://changelogs.credativ.org/ Any reason this functionality can't be incorporated into packages.debian.org? Andrew
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 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 http://changelogs.credativ.org/ ... and now I had to find out that this service went offline a while ago... Regards, Joey -- WARNING: Do not execute! This call violates patent DE10108564. http://www.elug.de/projekte/patent-party/patente/DE10108564 wget -O patinfo-`date +%Y%m%d`.html http://patinfo.ffii.org/
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 changelog. 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 http://changelogs.credativ.org/ Correct, most people have never heard of this thing. Furthermore, it's broken (zero-sized replies). -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | Dept. of Computing, `. `' | Imperial College, `- -- | London, UK pgp3C912GkzJX.pgp Description: PGP signature
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 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 http://changelogs.credativ.org/ You can get the changelog with qa.debian.org: 1) go to http://packages.debian.org/foo 2) go to link 'developer information for foo' 3) go to link Accepted foo 17.42-143 (i386 source) And here is the last changelogs entry Alternatively, you can replace step 1-2) with 1-2) go to link http://packages.qa.debian.org/foo Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here.
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 changelog, I know of, but all other infos can be seen on the package tracking system: I guess that you've never heard of http://changelogs.credativ.org/ Regards, Joey -- Let's call it an accidental feature. -- Larry Wall Please always Cc to me when replying to me on the lists.
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 infos can be seen on the package tracking system: http://packages.qa.debian.org/a/adns.html This also includes the change notification mails. For me, this is good enough, but I could understand when people want to have this offline available. Greetings Bernd -- (OO) -- [EMAIL PROTECTED] -- ( .. ) [EMAIL PROTECTED],linux.de,debian.org} http://home.pages.de/~eckes/ o--o *plush* 2048/93600EFD [EMAIL PROTECTED] +497257930613 BE5-RIPE (OO) When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!
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 date: Caches like apt-proxy combined with out-of-date debian mirrors sometimes work against you and give apt-get (and cache) a really old Packages.gz file, that contains obsolete Packages. It would be nice if there was some automatic way of determining that the Packages.gz/Sources.gz files downloaded are in fact up-to-date, without manually inspecting them. (I am just worried that one day I will do a lot of packporting from unstable to stable and suddenly realize all my backports were obsolete before I even created them...). -- Brian May [EMAIL PROTECTED]
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 otherwise we offline users have no idea if were looking at something that hasn't changed since the 90's, or was just updated last week, without having to connect our modems to find out. 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.
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 updated somehow helps you find out who created the package? ls -l /var/lib/apt/lists/*Packages This would give you the time your Packages files were last updated. Is this what you were looking for? Your message does not exactly make it clear. - Keegan
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 -- Overfiend BWAHAHAHAHAHAHHA Overfiend MOAHAHAHAHAHA --- Overfiend is now known as PUREFUCKINGEVIL PUREFUCKINGEVIL BWAHAHAHAHA
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 knowing the date you last updated somehow helps you find out who created the package? ls -l /var/lib/apt/lists/*Packages This would give you the time your Packages files were last updated. Is this what you were looking for? Your message does not exactly make it clear. 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. I've wanted the same from time to time. It's a funny omission from the Packages format. And yes, that can be useful information. If you're looking for anything resembling a driver, or the like, or if you just want to make sure a package has had an upload in the past .. 3 years before wasting your time with it. I prefer not to install packages whose maintainers have been asleep for 3 years. -- see shy jo pgpsOJ8r10Gnz.pgp Description: PGP signature
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 there. That and/or search the list archive. But having a build date in the (processed) package control file would mean that the information, or at least a snapshot of it, is available off-line as well. -- | Darren Salt | nr. Ashington, | linux (or ds) at | woody, sarge, | Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | We've got Shearer, you haven't Statistics are used as a drunk uses lamp posts - support, not illumination.
