summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2019-03-20 06:52:19 +0000
committerintrigeri <intrigeri@boum.org>2019-03-20 06:52:19 +0000
commit91a3d74fb6610e171218debb7bf33424aec3b058 (patch)
tree5e777412a56cbc018576b7bbf4fe4994db9e39a1
parent7c7a44df4069d0fc28bb426f2598e7e6f4d812bf (diff)
Custom APT repo: drop obsolete instruction (refs: #16576).
The version of reprepro we currently run does not choke on .buildinfo files. The only remaining issue is that reprepro leaves these files in the "incoming" directory after successfully importing a package, but that should be dealt with elsewhere (e.g. on the infra side) — if at all — instead of requiring everyone who uploads a package to do some extra work.
-rw-r--r--wiki/src/contribute/APT_repository/custom.mdwn4
1 files changed, 0 insertions, 4 deletions
diff --git a/wiki/src/contribute/APT_repository/custom.mdwn b/wiki/src/contribute/APT_repository/custom.mdwn
index e024faa..1311e21 100644
--- a/wiki/src/contribute/APT_repository/custom.mdwn
+++ b/wiki/src/contribute/APT_repository/custom.mdwn
@@ -172,10 +172,6 @@ Carefully check the `.changes` file (especially the `Distribution`
control field, and the included files list; the former can be fixed
with the `changestool(1)` command, from [[!debpkg reprepro]]).
-Remove all `buildinfo` lines from the `.changes` file.
-XXX: still needed? We now run reprepro from Stretch, that supports
-both in theory.
-
If the `.orig.tar.{gz,bz2,xz}` tarball is present neither in the
`.changes` file nor in our custom APT repository, add it using: