path: root/wiki/src/blueprint/freezable_APT_repository.mdwn
diff options
authorintrigeri <>2015-10-24 08:02:05 +0000
committerintrigeri <>2015-10-24 08:02:05 +0000
commit39df2692cef107377fed5fc36f419dc6001ad961 (patch)
tree2b1d42ba5f3891e10a395cbbb9910a42937a9fbd /wiki/src/blueprint/freezable_APT_repository.mdwn
parent1c1f3fb1d0f6c1847164382bbc318cd032fab761 (diff)
Diffstat (limited to 'wiki/src/blueprint/freezable_APT_repository.mdwn')
1 files changed, 8 insertions, 0 deletions
diff --git a/wiki/src/blueprint/freezable_APT_repository.mdwn b/wiki/src/blueprint/freezable_APT_repository.mdwn
index 7aa680c..eeb09e5 100644
--- a/wiki/src/blueprint/freezable_APT_repository.mdwn
+++ b/wiki/src/blueprint/freezable_APT_repository.mdwn
@@ -414,6 +414,14 @@ XXX:
* use a leading dash for `Update: - ...` in `conf/distributions`?
* compare fields in generated `Release` files, with what can be found
in the official Debian archive
+ * "Reprepro uses berkeley db, which was a big mistake. The most
+ annoying problem not yet worked around is database corruption when
+ the disk runs out of space. (Luckily if it happens while
+ downloading packages while updating, only the files database is
+ affected, which is easy (though time consuming) to rebuild, see
+ recovery file in the documentation). *Ideally put the database on
+ another partition to avoid that.*" (emphasis mine, from
+ [reprepro(1)](
There's a race condition when updating a local mirror with `reprepro
update`: if it's not finished before the next dinstall + mirror sync'