diff options
authorintrigeri <>2019-03-18 06:45:24 +0000
committerintrigeri <>2019-03-18 06:45:24 +0000
commit66562a10334d22aec6264a0b1c5423f45fe6a271 (patch)
parent6b727c11f1c995e452490c809250248de3a23177 (diff)
Custom APT repo: move relevant info to the place where one is looking when they want to upload a package.
The Overview section explains the branch → APT suite mapping, but it's easy to miss when one is focused on the "Importing a new package" howto, which can waste developer time: if they don't push a branch before uploading, their upload will be rejected. In practice, there's rarely any reason to follow the doc we have for "Creating a new branch" except before uploading a new package. So let's move these instructions to where they're needed, i.e. "Importing a new package".
1 files changed, 4 insertions, 5 deletions
diff --git a/wiki/src/contribute/APT_repository/custom.mdwn b/wiki/src/contribute/APT_repository/custom.mdwn
index b048e42..51775f0 100644
--- a/wiki/src/contribute/APT_repository/custom.mdwn
+++ b/wiki/src/contribute/APT_repository/custom.mdwn
@@ -103,8 +103,10 @@ The custom APT repository can be browsed at <>.
-Creating a new branch
+Importing a new package
+### Creating a new branch
Push your branch to Git and wait a few minutes for the new APT suite
to appear on <>. You can look up the
@@ -114,9 +116,6 @@ Then, you probably want to drop a new file in
`config/APT_overlays.d/`, named after the APT suite corresponding to
your new branch. See details in the *Build system* section above.
-Importing a new package
### Building a package
Make sure the `Distribution:` field in your `.changes` file matches