[Spacewalk-list] How to force a channel repodata rebuild?

[Tomas Lestach]

> So, about the regeneration of the repodata.... when I manually
> removed the data and triggered the rebuild, the datetime
> modification information on the files were the same as before I
> removed the data.

Do you mean repomd.xml, primary.xml.gz, ... ?
Do you check it on the server or on the client?

> It was as if the regeneration of the data was
> using cached valued to reproduce the same data. It was only when we
> make package changes to the channel that we actually got a "fresh"
> repodata.
> 
> This morning I took a closer look at the repodata, from a backup I
> took prior to deleting it, and could not find any differences except
> with the repomd.xml file that had updated timestamp and sha.

So, here you write something different than above, when you wrote the
datetime modification information on the files were the same.

> Could
> this imply something "else" was corrupted within Spacewalk? What
> sort of metadata does SW store about the RPMs that reside in the
> channels?

We cache only the repodata parts for every rpm. When regenerating
repodata, we put all the repodata rpm parts together (according to the
channel rpms) and generate whole repodata files. All the files are
newly created, so the modification dates shall be set accordingly.


Regards,
--
Tomas Lestach
RHN Satellite Engineering, Red Hat