[mirror-admin] ERROR: chroot failed for fedora-web

[Jesse Keating]

On Tue, 2009-01-13 at 23:54 -0200, Carlos Carvalho wrote:
> I'm not sure of what you mean by "the like" but it's not what I said,
> otherwise it'd already have the info.
> 
>  >What "other info" is necessary?
> 
> That provided by rsync.

Rsync man pages are extremely vague as to what the contents of the
filelist should be, but it seems to me that it should be just file
names, either new line terminated or null terminated.  No room for
things like checksums or datestamps or anything else.

> 
>  >We're generating something that rsync can consume directly, rather
>  >than building up some other infrastructure around it.
> 
> What do you mean by "rsync can consume"? Using the filelist generated
> by rsync has the info

erm, I mean exactly what I say.  It appears that rsync --files-from can
only consume a file that has paths, either null or newline terminated.
No other information.  So again, I'm not sure what value you're getting
from using rsync vs find to generate the filelist.  Perhaps you could
point me to some better documentation on --files-from that explains what
you mean.

> 
>  >> If you want to get fancy you should create a list of checksums. It can
>  >> be used for the same purpose with the added bonus of allowing mirrors
>  >> to check if their repository is correct without having to deal with
>  >> rpm, besides making checking much faster than with it. The best format
>  >> is the one created by *sum family. This would be a most welcome
>  >> improvement to the fedora archive.
>  >
>  >Again that would be something that rsync can't consume, and beyond the
>  >scope of what we're trying to address here.  We already have tools that
>  >will compare packages on disk to their checksums in repodata, which can
>  >also verify things like image files, etc...  It should only be necessary
>  >to verify the repomd.xml and .treeinfo files themselves for upstream
>  >checksums, everything else is self checksummed in the trees.
> 
> I'd like to learn how to do it. It's useful to check for data
> corruption on the filesystem. Note that the tools should not need to
> open the .rpm files because this isn't necessary to check their
> integrity.
> 

That's correct.  verifytree, which is in yum-utils, does not need to
open the rpms themselves.  There is a .treeinfo file in most trees that
points to where the repodata is and what the checksum of the repodata
should be.  The repodata itself contains checksums of all the individual
rpms.  So as long as you can trust and verify .treeinfo, you should have
a path of verification down to the individual rpms, but in release trees
inclusive of the install images and kernel images, and the iso files.

-- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://mail.ale.org/pipermail/mirror-admin/attachments/20090115/f025c87d/attachment.bin 
-------------- next part --------------
--