reprepro doc: mention contents.cache.db
Today we found a corrupt contents.cache.db; after investigation we found that it is regenerated by the export command. This makes a note of that for future reference. Change-Id: Ib6d698651b9d4c84d0704b79a6ee58d009c89854
This commit is contained in:
parent
473a21d647
commit
96059d52bb
@ -203,6 +203,10 @@ from the checksums database with a command similar to::
|
|||||||
|
|
||||||
They should come back with the next update.
|
They should come back with the next update.
|
||||||
|
|
||||||
|
The ``contents.cache.db`` can be regenerated with the ``export``
|
||||||
|
command; this is run by the ``reprepro`` driver scripts automatically.
|
||||||
|
It will take some time to regenerate, so this should be run manually.
|
||||||
|
|
||||||
In some situations where things are very out of sync, it may be easier
|
In some situations where things are very out of sync, it may be easier
|
||||||
to remove and replace an entire section of the repository. For
|
to remove and replace an entire section of the repository. For
|
||||||
example, if during updates files within ``xenial-security`` are seen
|
example, if during updates files within ``xenial-security`` are seen
|
||||||
|
Loading…
Reference in New Issue
Block a user