Re: [Apt4rpm-devel] release.XXX files

[Richard B. <al...@fr...>]

Which apt version are you using (cvs 1.1...), if you have >=3D 1.123 all =
should=20
work well....

I've compared and check aptate versus genbasedir and as far as I know the=
ir=20
checksum functionality is the same.  Can you provide an overview of your=20
SuSE/.../base directory =3D> are the files release and hashfile present. =
 Are=20
the usual files manus and extra-local present (ls *manus* *extra-local*).
What information do they contain?


Op woensdag 24 juli 2002 12:53, schreef Ralf Corsepius:
> Richard,
>
> These two items from apt-rpm-0.5 seem to have broken apt4rpm:
> {from http://moin.conectiva.com.br/AptRpm)
> -------
> A new version of APT-RPM, already in the 0.5 series, was just released.
> Here are some of the most visible changes you'll find in the RPM port.
> Please, read it carefuly before upgrading.
>
>       New release/hash/authentication system
>           This version of APT-RPM uses a new system for storing
> information about the repository. A file named release will now sit in
> the base directory, and carry meta information about the repository,
> including the hashes of component specific release files and pkglists.
> It means that the old hashfile{,.gpg} is now obsolete, even though you
> can still use the --oldhashfile genbasedir option to create repositorie=
s
> compatible with old versions of APT. Signed repositories scheme has als=
o
> changed a little bit; now there's just one single file, which will be
> searched for signatures at client side (don't worry about it, genbasedi=
r
> will take care for you).
>
>       Updated genbasedir
>           Besides being improved to support the new repository scheme,
> the new genbasedir script is more user friendly. It will now create all
> the base directory itself and all necessary information in the
> repository with a simple "genbasedir /my/topdir", including templates
> for the global and component release files. It will also update the
> timestamp and the component metainformation available on release files
> automatically. You can still specify which components you want it to
> create, if needed.
> -------
>
> AFAIU, at the first item above seems to be responsible for these
> warnings with aptate generated repositories (This is with
> apt-rpm-0.5.4-cnc2 and SuSE-8.0):
>
> # apt-get update:
> [..]
> Get:29 ftp://ftp SuSE/8.0-i386/suse srclist [14B]
> Get:30 ftp://ftp SuSE/8.0-i386/base srclist [401kB]
> Fetched 3847kB in 15s
> (244kB/s)
> Reading Package Lists... Done
> Collecting File Provides... Done
> Building Dependency Tree... Done
> W: Release file did not contain checksum information for
> ftp://ftp/pub/linux/apt/SuSE/8.0-i386/base/release.manus
> W: Release file did not contain checksum information for
> ftp://ftp/pub/linux/apt/SuSE/8.0-i386/base/srclist.manus
> W: Release file did not contain checksum information for
> ftp://ftp/pub/linux/apt/SuSE/8.0-i386/base/pkglist.extra-local
> [..]
>
> AFAIU, the release.XXX file format has changed.
>
> Could you please look into this?
>
> Ralf

--=20
Richard Bos
Without a home the journey is endless