On Sun, Dec 28, 2003 at 10:32:17PM -0500, Joey Hess wrote:
> Somewhat offtopic, but is there any documentation of the format and
> fields in Release files anywhere at all? Or did they spring full-fledged
> (and undocumented) from the sweaty brows of Aj and Jason? :-)
Pretty much.
On Mon, Dec 29, 2003 at 03:25:02PM -0500, Nathaniel W. Turner wrote:
> > You forgot to attach the Release file. It is probably bogus. Use
> > apt-ftparchive to generate one.
> I did use apt-ftparchive to generate it, and it really is at that URI in the
> quoted error message above. =)
It says:
] Origin: Nathaniel W. Turner
] Label: Unofficial Snapshot Packages
I'd expect the spaces there to cause problems. If they don't, I'm out of
ideas too.
Some rough documentation, AIUI:
] Origin: Debian
] Label: Debian
As per the binary-foo/Release files -- Origin is the originating
organisation, Label is name of the overall distribution being provided.
] Suite: stable
] Codename: woody
] Version: 3.0r2
The name of this particular release of the distribution. Suite/Codename
replace "Archive" from apt_preferences. Both Version and Codename are
optional. (The other fields should be the same as in apt_preferences)
Each of these should be one word, usually (always?) all lower case. The
Release file should be accessible as $URLBASE/dists/$SUITE/Release
and $URLBASE/dists/$CODENAME/Release. (Note that that *is* the case
for experimental thanks to the wonders of symlinks)
] Date: Thu, 20 Nov 2003 18:57:17 UTC
The timestamp of the Release file, in "date -uR" format.
] Architectures: alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
] Components: main contrib non-free
Architectures and Components this distribution includes. Multiple words, one
for each arch/component, separated by spaces.
] Description: Debian 3.0r2 Released 20th November 2003
Human readable description. In theory this was meant to also allow for
multiline descriptions (in the normal control-file way) that could tell
you what the difference between unstable and stable is, for example. That
hasn't happened so far though.
] MD5Sum:
] 678eab2d1d603992726f697765dadf33 3208 main/di...
md5sums of all the files that list the contents of the distribution (Packages,
Sources, disks-i386/md5sums.txt, etc) -- each of those should authenticate
the individual files they list. Format is the same as .changes files.
SHA1: likewise.
The Release.gpg file is concatenated, ASCII armoured PGP signatures of
the Release file by different keys.
Cheers,
aj
--
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.
Linux.conf.au 2004 -- Because we can.
http://conf.linux.org.au/ -- Jan 12-17, 2004
Attachment:
pgp9d1HmzaWGv.pgp
Description: PGP signature