From 96059d52bbe1e382414674409210efeb0d7ca80b Mon Sep 17 00:00:00 2001 From: Ian Wienand Date: Wed, 14 Sep 2022 11:29:37 +1000 Subject: [PATCH] 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 --- doc/source/reprepro.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/source/reprepro.rst b/doc/source/reprepro.rst index 2b8d43c8d2..20479a7341 100644 --- a/doc/source/reprepro.rst +++ b/doc/source/reprepro.rst @@ -203,6 +203,10 @@ from the checksums database with a command similar to:: 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 to remove and replace an entire section of the repository. For example, if during updates files within ``xenial-security`` are seen