| 1 |
Source: netplan.io |
| 2 |
Maintainer: Debian Networking Team <[email protected]> |
| 3 |
Uploaders: |
| 4 |
Andrej Shadura <[email protected]>, |
| 5 |
Lukas Märdian <[email protected]>, |
| 6 |
Section: net |
| 7 |
Priority: optional |
| 8 |
Standards-Version: 4.7.2 |
| 9 |
Rules-Requires-Root: no |
| 10 |
Build-Depends: |
| 11 |
debhelper-compat (= 13), |
| 12 |
dh-sequence-python3, |
| 13 |
pkgconf, |
| 14 |
bash-completion, |
| 15 |
libyaml-dev, |
| 16 |
libglib2.0-dev, |
| 17 |
uuid-dev, |
| 18 |
python3, |
| 19 |
python3-cffi, |
| 20 |
python3-coverage <!nocheck>, |
| 21 |
python3-pytest <!nocheck>, |
| 22 |
python3-pytest-cov <!nocheck>, |
| 23 |
python3-rich <!nocheck>, |
| 24 |
python3-yaml <!nocheck>, |
| 25 |
libcmocka-dev <!nocheck>, |
| 26 |
libpython3-dev, |
| 27 |
libsystemd-dev, |
| 28 |
udev <!nocheck>, |
| 29 |
systemd <!nocheck>, |
| 30 |
systemd-dev, |
| 31 |
dbus-daemon <!nocheck>, |
| 32 |
pyflakes3 <!nocheck>, |
| 33 |
pycodestyle <!nocheck>, |
| 34 |
pandoc, |
| 35 |
openvswitch-switch [ !armel !armhf !i386 !hppa !m68k !powerpc !sh4 !x32 ] <!nocheck>, |
| 36 |
meson (>= 1.3.0), |
| 37 |
iproute2 <!nocheck>, |
| 38 |
Vcs-Git: https://salsa.debian.org/debian/netplan.io.git |
| 39 |
Vcs-Browser: https://salsa.debian.org/debian/netplan.io |
| 40 |
Homepage: https://netplan.io/ |
| 41 |
|
| 42 |
Package: netplan.io |
| 43 |
Architecture: linux-any |
| 44 |
Multi-Arch: foreign |
| 45 |
Depends: |
| 46 |
${python3:Depends}, |
| 47 |
${shlibs:Depends}, |
| 48 |
${misc:Depends}, |
| 49 |
ethtool, |
| 50 |
iproute2, |
| 51 |
libnetplan1 (= ${binary:Version}), |
| 52 |
netplan-generator, |
| 53 |
python3-netplan, |
| 54 |
python3-yaml, |
| 55 |
systemd (>= 258~), |
| 56 |
udev, |
| 57 |
Recommends: |
| 58 |
python3-rich, |
| 59 |
Suggests: |
| 60 |
systemd-resolved, |
| 61 |
Description: Declarative network configuration for various backends at runtime |
| 62 |
Netplan reads YAML network configuration files which are written |
| 63 |
by administrators, installers, cloud image instantiations, or other OS |
| 64 |
deployments. During early boot it then generates backend specific |
| 65 |
configuration files in /run to hand off control of devices to a particular |
| 66 |
networking daemon. |
| 67 |
. |
| 68 |
Currently supported backends are networkd and NetworkManager. |
| 69 |
. |
| 70 |
This package provides a runtime CLI to control the Netplan backends, |
| 71 |
e.g. to re-generate configuration or apply changes. |
| 72 |
|
| 73 |
Package: netplan-generator |
| 74 |
Architecture: linux-any |
| 75 |
Multi-Arch: foreign |
| 76 |
Depends: |
| 77 |
${shlibs:Depends}, |
| 78 |
${misc:Depends}, |
| 79 |
libnetplan1 (= ${binary:Version}), |
| 80 |
systemd (>= 258~), |
| 81 |
Suggests: |
| 82 |
network-manager | wpasupplicant, |
| 83 |
openvswitch-switch, |
| 84 |
iw, |
| 85 |
Breaks: netplan.io (<< 0.106.1-8~), |
| 86 |
Replaces: netplan.io (<< 0.106.1-8~), |
| 87 |
Description: Declarative network configuration for various backends at boot |
| 88 |
Netplan reads YAML network configuration files which are written |
| 89 |
by administrators, installers, cloud image instantiations, or other OS |
| 90 |
deployments. During early boot it then generates backend specific |
| 91 |
configuration files in /run to hand off control of devices to a particular |
| 92 |
networking daemon. |
| 93 |
. |
| 94 |
Currently supported backends are networkd and NetworkManager. |
| 95 |
. |
| 96 |
This package provides a systemd-generator to configure various networking |
| 97 |
daemons at boot time. |
| 98 |
|
| 99 |
Package: python3-netplan |
| 100 |
Section: python |
| 101 |
Architecture: linux-any |
| 102 |
Multi-Arch: foreign |
| 103 |
Depends: |
| 104 |
${python3:Depends}, |
| 105 |
${shlibs:Depends}, |
| 106 |
${misc:Depends}, |
| 107 |
libnetplan1 (= ${binary:Version}), |
| 108 |
python3-cffi-backend, |
| 109 |
Breaks: netplan.io (<< 0.107-3~) |
| 110 |
Replaces: netplan.io (<< 0.107-3~) |
| 111 |
Description: Declarative network configuration Python bindings |
| 112 |
Netplan reads YAML network configuration files which are written |
| 113 |
by administrators, installers, cloud image instantiations, or other OS |
| 114 |
deployments. During early boot it then generates backend specific |
| 115 |
configuration files in /run to hand off control of devices to a particular |
| 116 |
networking daemon. |
| 117 |
. |
| 118 |
Currently supported backends are networkd and NetworkManager. |
| 119 |
. |
| 120 |
This package provides a CFFI based Python bindings to libnetplan. |
| 121 |
|
| 122 |
Package: libnetplan1 |
| 123 |
Section: libs |
| 124 |
Architecture: linux-any |
| 125 |
Multi-Arch: same |
| 126 |
Depends: |
| 127 |
${shlibs:Depends}, |
| 128 |
${misc:Depends}, |
| 129 |
Description: Declarative network configuration runtime library |
| 130 |
Netplan reads YAML network configuration files which are written |
| 131 |
by administrators, installers, cloud image instantiations, or other OS |
| 132 |
deployments. During early boot it then generates backend specific |
| 133 |
configuration files in /run to hand off control of devices to a particular |
| 134 |
networking daemon. |
| 135 |
. |
| 136 |
Currently supported backends are networkd and NetworkManager. |
| 137 |
. |
| 138 |
This package contains the necessary runtime library files. |
| 139 |
|
| 140 |
Package: libnetplan-dev |
| 141 |
Section: libdevel |
| 142 |
Architecture: linux-any |
| 143 |
Multi-Arch: same |
| 144 |
Depends: ${misc:Depends}, |
| 145 |
libnetplan1 (= ${binary:Version}), |
| 146 |
Description: Development files for Netplan's libnetplan runtime library |
| 147 |
Netplan reads YAML network configuration files which are written |
| 148 |
by administrators, installers, cloud image instantiations, or other OS |
| 149 |
deployments. During early boot it then generates backend specific |
| 150 |
configuration files in /run to hand off control of devices to a particular |
| 151 |
networking daemon. |
| 152 |
. |
| 153 |
Currently supported backends are networkd and NetworkManager. |
| 154 |
. |
| 155 |
This package contains development files for developers wanting to use |
| 156 |
libnetplan in their applications. |