-
Notifications
You must be signed in to change notification settings - Fork 0
/
template.yaml
100 lines (92 loc) · 3.38 KB
/
template.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
---
# Change the toplevel key to the name for your repository. This should
# be unique within the extrepo repository; it is what users should pass
# as an argument to "extrepo enable".
# If the repository name starts with a dot ("."), it is ignored. This
# can be used for copying in templates (see below).
reponame:
description: Describe your repository here. May be multiline
source:
# Add any Deb822 sources.list(5) keys you want to add. Note that a
# Signed-By: key is added automatically; if you add one explicitly,
# it will be ignored and overridden.
#
# The special value <SUITE> will be replaced by the suite the user
# is running; it can appear in any of the below keys.
#
# The special value <COMPONENTS> will be replaced by the
# (space-separated) components (as listed in the "components:" top
# level key), after filtering by the policies which the user has
# enabled. It can occur in any of the below keys; but it will
# probably not work well unless used in the "Components:" key.
Types: deb deb-src
URIs: https://deb.example.com/debian/
Suites: <SUITE>
Components: <COMPONENTS>
Architectures: amd64 i386
# If there are differences in this section on a per-suite basis that can't
# be expressed by way of <SUITE>, you can add per-suite keys; e.g.,
# suite-buster-Architectures: amd64 i386
# creates a line "Architectures:" in the .sources file, but *only* on buster.
# Update the list below by the list of Debian codenames which you support
suites:
- bullseye
- bookworm
# List all the components your repository supports. If there is only
# one, or they all have the same license policy, it's fine to drop the
# "components" and "policies" keys and hardcode the component(s) in
# the "Components:" key of the "source" key above. In that case,
# however, the "policy" key is required (see below).
components:
- main
- alternate
- alternate-nonfree
# For every component above, there should be an entry in the
# "policies" key that states the policy for that repository.
#
# The values here should be one of:
# - "main": only contains DFSG-free software that may only
# (build-)depend on DFSG-free software.
# - "contrib": only contains DFSG-free software. However, it may
# (build-)depend on software which is not DFSG-free.
# - "non-free": all other repositories.
policies:
main: main
alternate: main
alternate-nonfree: non-free
# If there is no "components" key, drop the "policies" one and add a
# "policy" key instead:
#policy: main
# Some way of contacting the maintainers of the repository.
# Informational only.
contact: [email protected]
# Some way of filing issues with the repository. Informational only.
bugs: https://bugzilla.example.com/
# Add the ASCII-armored version of your signing key below.
gpg-key: |
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQINBFyy...
...
-----END PGP PUBLIC KEY BLOCK-----
# If you have multiple repositories that differ only slightly, you can
# use templating:
#
# .common: &common
# source:
# Types: deb deb-src
# Architectures: i386 amd64
# Components: <COMPONENTS>
# Suites: <SUITE>
# components:
# - main
# - contrib
# policies:
# main: main
# contrib: contrib
# gpg-key: |
# ...
#
# repo-1:
# <<: *common
# source:
# URIs: https://deb.example.com/repo-1/debian