|
|
[[!tag archived]]
|
|
|
|
|
|
Corresponding ticket: [[!tails_ticket 8616]], that's a blocker for [[!tails_ticket 8617]].
|
|
|
|
|
|
[[!toc levels=2]]
|
|
|
Corresponding ticket: tails/tails#8616, that's a blocker for tails/tails#8617.
|
|
|
|
|
|
|
|
|
[[_TOC_]]
|
|
|
|
|
|
|
|
|
Initial design
|
|
|
==============
|
... | ... | @@ -32,7 +34,7 @@ branches that were already merged. |
|
|
|
|
|
### Exception: branches created just to get an APT suite
|
|
|
|
|
|
**Update**: [[!tails_ticket 8654]] has been implemented in a way that
|
|
|
**Update**: tails/tails#8654 has been implemented in a way that
|
|
|
makes all this moot (any branch that's created to get an APT suite
|
|
|
will have one commit to add that suite to `config/APT_overlays.d/` --
|
|
|
the only exception being branches that would be created to create an
|
... | ... | @@ -40,7 +42,7 @@ APT suite that they don't plan to use, but for that use case, so far |
|
|
we've instead hard-coded the additional suite names we need in the
|
|
|
scripts that generate the reprepro configuration).
|
|
|
|
|
|
Given how our [[custom APT repository|contribute/APT_repository/custom]]
|
|
|
Given how our [custom APT repository](https://tails.boum.org/contribute/APT_repository/custom)
|
|
|
currently works, we sometimes push
|
|
|
Git branches merely to have an APT suite created, and be able to upload Debian
|
|
|
packages to it. Such a branch will look like it has been merged (it has no
|
... | ... | @@ -58,7 +60,7 @@ were created merely to get an APT branch; and 2. were actually not merged yet. |
|
|
Of course that's a bit painful and error-prone.
|
|
|
|
|
|
Longer term, if/once we have each branch contain a config file with the list of
|
|
|
APT suites that shall be used (as mentioned on [[!tails_ticket 8654]]), then for
|
|
|
APT suites that shall be used (as mentioned on tails/tails#8654), then for
|
|
|
each branch that is a candidate for deletion we can:
|
|
|
|
|
|
1. Check if that APT suite list file, in that branch, contains anything but
|
... | ... | @@ -75,7 +77,7 @@ corresponds to each branch we're going to delete. It's going to be sub-optimal, |
|
|
as most branches don't introduce Debian packages, but it would probably be good
|
|
|
enough, and the code will be reusable for the long-term solution anyway.
|
|
|
|
|
|
Another mid-term solution would be to piggy-back on [[!tails_ticket 8689]]:
|
|
|
Another mid-term solution would be to piggy-back on tails/tails#8689:
|
|
|
a branch that 1. has no commit on top of master; and 2. has no such change file;
|
|
|
probably was created only to get an APT suite, and should not be deleted.
|
|
|
|
... | ... | @@ -93,3 +95,4 @@ Push access to the official main Git repository. |
|
|
So far, only humans have write access there and we would like to not replace
|
|
|
them with robots yet. That is for the future (e.g. the system that hosts our APT
|
|
|
repository already has privileges akin to Git commit rights).
|
|
|
|