#_preseed_V1 ############################ #### anna_1.91_amd64.udeb ############################ ### Description: Installer components to load: # All components of the installer needed to complete the install # will be loaded automatically and are not listed here. Some other # (optional) installer components are shown below. They are probably # not necessary, but may be interesting to some users. # . # Note that if you select a component that requires others, those # components will also be loaded. # d-i anna/choose_modules multiselect # Possible choices: ${CHOICES} ### Description: Installer components to load: # To save memory, only components that are certainly needed for an install # are selected by default. The other installer components are not all necessary # for a basic install, but you may need some of them, especially certain kernel # modules, so look through the list carefully and select the components you # need. # . # Note that if you select a component that requires others, those # components will also be loaded. # d-i anna/choose_modules_lowmem multiselect # Possible choices: ${CHOICES} ### Description: Continue the install without loading kernel modules? # No kernel modules were found. This probably is due to a mismatch between # the kernel used by this version of the installer and the kernel version # available in the archive. # . # You should make sure that your installation image is up-to-date, or - if # that's the case - try a different mirror, preferably deb.debian.org. # . # The installation will probably fail to work if you continue without kernel # modules. # d-i anna/no_kernel_modules boolean false ### Description: for internal use only # Default retriever # d-i anna/retriever string ### Description: for internal use; can be preseeded # Install standard modules? # d-i anna/standard_modules boolean true ############################ #### apt-cdrom-setup_0.182_all.udeb ############################ ### Description: Scan extra installation media? # Scanning your installation media finds the label: # . # ${LABEL} # . # You now have the option of scanning additional media for use by the package # manager (apt). Normally these should be from the same set as the one you # booted from. If you do not have any additional media, this step can just be # skipped. # . # If you wish to scan more media, please insert another one now. # d-i apt-setup/cdrom/set-first boolean false ### Description: Scan extra installation media? # The image with the following label has been scanned: # . # ${LABEL} # . # If you wish to scan more media, please insert another one now. # d-i apt-setup/cdrom/set-next boolean false ### Description: Scan extra installation media? # The image with the following label has already been scanned: # . # ${LABEL} # . # Please replace it now, if you wish to scan another. # d-i apt-setup/cdrom/set-double boolean true ### Description: Scan extra installation media? # An attempt to configure apt to install additional packages from the # media failed. # . # Please check that the media has been inserted correctly. # d-i apt-setup/cdrom/set-failed boolean true ### Description: for internal use; can be preseeded # When set to true, apt-setup always disables cdrom entries from APT's # configuration. Otherwise, it disables them only when a netinst image # has been used. # . # This option can be preseeded for automated installations that should # not reference the installation media in the target system. # d-i apt-setup/disable-cdrom-entries boolean false ############################ #### apt-mirror-setup_0.182_all.udeb ############################ ### Description: Use non-free firmware? # Some non-free firmware has been made to work with Debian. Though this # firmware is not at all a part of Debian, standard Debian tools can be used # to install it. This firmware has varying licenses which may prevent you # from using, modifying, or sharing it. # . # Please choose whether you want to have it available anyway. # d-i apt-setup/non-free-firmware boolean false ### Description: Use non-free software? # Some non-free software has been made to work with Debian. Though this # software is not at all a part of Debian, standard Debian tools can be used # to install it. This software has varying licenses which may prevent you # from using, modifying, or sharing it. # . # Please choose whether you want to have it available anyway. # d-i apt-setup/non-free boolean false ### Description: Use contrib software? # Some additional software has been made to work with Debian. Though this # software is free, it depends on non-free software for its operation. This # software is not a part of Debian, but standard Debian tools can be # used to install it. # . # Please choose whether you want this software to be made available to you. # d-i apt-setup/contrib boolean false ### Description: Downloading a file failed: # The installer failed to access the mirror. This may be a problem with your # network, or with the mirror. You can choose to retry the download, select # a different mirror, or ignore the problem and continue without all the # packages from this mirror. # d-i apt-setup/mirror/error select Retry # Possible choices: Retry, Change mirror, Ignore ### Description: Use a network mirror? # A network mirror can be used to supplement the software that is included # on the installation media. This may also make newer versions of software # available. # . # ${EXPLANATION} # d-i apt-setup/use_mirror boolean ### Description: Continue without a network mirror? # No network mirror was selected. # . # If you are installing from a netinst CD image and choose not to use a mirror, # you will end up with only a very minimal base system. # d-i apt-setup/no_mirror boolean false ############################ #### apt-setup-udeb_0.182_amd64.udeb ############################ ### Description: Downloading local repository key failed: # The installer failed to download the public key used to sign the local # repository at ${MIRROR}: # . # ${URL} # . # This may be a problem with your network, or with the server hosting this # key. You can choose to retry the download, or ignore the problem and # continue without all the packages from this repository. # d-i apt-setup/local/key-error select Retry # Possible choices: Retry, Ignore ### Description: for internal use; can be preseeded # Host to use for security updates # d-i apt-setup/security_host string security.debian.org ### Description: Services to use: # Debian has two services that provide updates to releases: security and # release updates. # . # Security updates help to keep your system secured against attacks. Enabling # this service is strongly recommended. # . # Release updates provide more current versions for software that changes # relatively frequently and where not having the latest version could reduce # the usability of the software. It also provides regression fixes. # This service is only available for stable and oldstable releases. # . # Backported software are adapted from the development version to work with # this release. Although this software has not gone through such complete # testing as that contained in the release, it includes newer versions of # some applications which may provide useful features. Enabling backports # here does not cause any of them to be installed by default; it only # allows you to manually select backports to use. # d-i apt-setup/services-select multiselect security, updates # Possible choices: security updates (from ${SEC_HOST}), release updates, backported software ### Description: Enable source repositories in APT? # By default source repositories are listed in /etc/apt/sources.list (with # appropriate "deb-src" lines) so that "apt-get source" works. However, if # you don't need this feature, you can disable those entries and save some # bandwidth during "apt-get update" operations. # d-i apt-setup/enable-source-repositories boolean true ### Description: for internal use; can be preseeded # Set to the list of architectures for which packages can be installed # without using 'dpkg --force-architecture', in addition to the native # architecture. If empty, only allow installing packages from the native # architecture. # d-i apt-setup/multiarch string ############################ #### base-installer_1.213_all.udeb ############################ ### Description: Proceed with installation to unclean target? # The target file system contains files from a past installation. These files # could cause problems with the installation process, and if you proceed, # some of the existing files may be overwritten. # d-i base-installer/use_unclean_target boolean true ### Description: for internal use; can be preseeded # Will configure APT in the target system not to install recommened # packages by default. For experienced users only. # d-i base-installer/install-recommends boolean true ############################ #### bootstrap-base_1.213_amd64.udeb ############################ ### Description: Tool to use to generate boot initrd: # The list shows the available tools. If you are unsure which to select, # you should select the default. If your system fails to boot, you can # retry the installation using the other options. # d-i base-installer/initramfs/generator select # Possible choices: ${GENERATORS} ### Description: Drivers to include in the initrd: # The primary function of an initrd is to allow the kernel to mount the # root file system. It therefore needs to contain all drivers and supporting # programs required to do that. # . # A generic initrd is much larger than a targeted one and may even be so # large that some boot loaders are unable to load it but has the advantage that # it can be used to boot the target system on almost any hardware. With the # smaller targeted initrd there is a very small chance that not all needed # drivers are included. # d-i base-installer/initramfs-tools/driver-policy select # Possible choices: generic: include all available drivers, targeted: only include drivers needed for this system ### Description: Kernel to install: # The list shows the available kernels. Please choose one of them in order # to make the system bootable from the hard drive. # d-i base-installer/kernel/image select # Possible choices: ${KERNELS}, none ### Description: Continue without installing a kernel? # No installable kernel was found in the defined APT sources. # . # You may try to continue without a kernel, and manually install your own # kernel later. This is only recommended for experts, otherwise you will # likely end up with a machine that doesn't boot. # d-i base-installer/kernel/skip-install boolean false ### Description: for internal use; can be preseeded # Packages to be included in base installation # d-i base-installer/includes string ### Description: for internal use; can be preseeded # Packages to be excluded in base installation # d-i base-installer/excludes string ### Description: for internal use; can be preseeded # Force use of a specific debootstrap script # d-i base-installer/debootstrap_script string ### Description: for internal use only # Use an (initramfs) initrd (linux 2.6 and later only) # d-i base-installer/kernel/linux/initrd-2.6 boolean true ### Description: for internal use # Default driver inclusion policy for initramfs-tools # d-i base-installer/kernel/linux/initramfs-tools/driver-policy string most ### Description: for internal use; can be preseeded # d-i base-installer/kernel/linux/extra-packages string ### Description: for internal use; can be preseeded # d-i base-installer/kernel/linux/extra-packages-2.6 string ### Description: for internal use only # Kernel needs a link in /boot/ (linux only) # d-i base-installer/kernel/linux/link_in_boot boolean false ############################ #### cdebconf-gtk-udeb_0.270_amd64.udeb ############################ ############################ #### cdebconf-newt-udeb_0.270_amd64.udeb ############################ ############################ #### cdebconf-priority_0.270_all.udeb ############################ ############################ #### cdebconf-text-udeb_0.270_amd64.udeb ############################ ############################ #### cdebconf-udeb_0.270_amd64.udeb ############################ ### Description: for internal use only # Default language # d-i debconf/language string en ### Description: Ignore questions with a priority less than: # Packages that use debconf for configuration prioritize the questions they # might ask you. Only questions with a certain priority or higher are # actually shown to you; all less important questions are skipped. # . # You can select the lowest priority of question you want to see: # - 'critical' is for items that will probably break the system # without user intervention. # - 'high' is for items that don't have reasonable defaults. # - 'medium' is for normal items that have reasonable defaults. # - 'low' is for trivial items that have defaults that will work in # the vast majority of cases. # . # For example, this question is of medium priority, and if your priority # were already 'high' or 'critical', you wouldn't see this question. # d-i debconf/priority select high # Possible choices: critical, high, medium, low ### Description: for internal use only # Frontend to use. Change this setting in your script to # switch the cdebconf frontend upon the next GO command. # d-i debconf/frontend string ### Description: for internal use only # Display again already asked questions # d-i debconf/showold boolean false ### Description: for internal use only # Set to true by cdebconf when translations have been permanently dropped # from the database due to DEBCONF_DROP_TRANSLATIONS=1 and cannot be # reloaded. # d-i debconf/translations-dropped boolean false ############################ #### cdebconf-gtk-entropy_0.52_amd64.udeb ############################ ############################ #### cdebconf-newt-entropy_0.52_amd64.udeb ############################ ############################ #### cdebconf-text-entropy_0.52_amd64.udeb ############################ ############################ #### cdebconf-gtk-terminal_0.43_amd64.udeb ############################ ############################ #### cdrom-checker_1.61_amd64.udeb ############################ ### Description: Check integrity of the installation media? # Warning: this check depends on your hardware and may take some time. # d-i cdrom-checker/start boolean false ### Description: Check the integrity of another installation image? # d-i cdrom-checker/nextcd boolean false ############################ #### cdrom-detect_1.106_all.udeb ############################ ### Description: Load drivers from removable media? # No device for installation media was detected. # . # You may need to load additional drivers from removable media, such as a # driver floppy or a USB stick. If you have these available now, insert the # media, and continue. Otherwise, you will be given the option to manually # select some modules. # d-i cdrom-detect/load_media boolean true ### Description: Manually select a module and device for installation media? # No device for installation media (like a CD-ROM device) was detected. # . # If your CD-ROM drive is an old Mitsumi or another non-IDE, non-SCSI CD-ROM # drive, you should choose which module to load and the device to use. If you # don't know which module and device are needed, look for some documentation # or try a network installation. # d-i cdrom-detect/manual_config boolean true ### Description: Retry mounting installation media? # Your installation media couldn't be mounted. When installing from CD-ROM, # this probably means that the disk was not in the drive. If so you can # insert it and try again. # d-i cdrom-detect/retry boolean true ### Description: Module needed for accessing the installation media: # The automatic detection didn't find a drive for installation media. When # installing from CD-ROM and you have an unusual CD-ROM drive (that is # neither IDE nor SCSI), you can try to load a specific module. # d-i cdrom-detect/cdrom_module select none # Possible choices: ${choices} ### Description: Device file for accessing the installation media: # In order to access your installation media (like your CD-ROM), please enter # the device file that should be used. Non-standard CD-ROM drives use # non-standard device files (such as /dev/mcdx). # . # You may switch to the shell on the second terminal (ALT+F2) to check the # available devices in /dev with "ls /dev". You can return to this screen # by pressing ALT+F1. # d-i cdrom-detect/cdrom_device string /dev/cdrom ### Description: for internal use only # File system used on cdrom-detect/cdrom_device. # d-i cdrom-detect/cdrom_fs string iso9660 ### Description: for internal use only # Set if the CD appears to be on a USB stick. # d-i cdrom-detect/hybrid boolean false ### Description: for internal use only # Set if the CD appears to be a live USB-HDD image. # d-i cdrom-detect/usb-hdd boolean false ### Description: for internal use; can be preseeded # Set to false to prevent the system from ejecting the CD-ROM before rebooting # d-i cdrom-detect/eject boolean true ### Description: for internal use only # Debian version to install # d-i cdrom/suite select # Possible choices: stable, testing, unstable ### Description: for internal use only # Codename for the selected suite # d-i cdrom/codename string ############################ #### cdrom-retriever_1.63_all.udeb ############################ ### Description: Failed to copy file from installation media. Retry? # There was a problem reading data. Please make sure you have inserted the # installation media correctly. If retrying does not work, you should check # the integrity of your installation media (there is an associated entry in # the main menu for that). # d-i retriever/cdrom/error boolean true ############################ #### load-cdrom_1.63_all.udeb ############################ ############################ #### choose-mirror-bin_2.123_amd64.udeb ############################ ### Description: country code or "manual" (for internal use) # d-i mirror/country string ### Description: Debian version to install: # Debian comes in several flavors. Stable is well-tested and rarely changes. # Unstable is untested and frequently changing. Testing is a middle ground, # that receives many of the new versions from unstable if they are not too # buggy. # . # Only flavors available on the selected mirror are listed. # d-i mirror/suite select # Possible choices: ${CHOICES} ### Description: for internal use only # d-i mirror/codename string ### Description: Go back and try a different mirror? # The specified (default) Debian version (${RELEASE}) is not available from # the selected mirror. It is possible to continue and select a different # release for your installation, but normally you should go back and select # a different mirror that does support the correct version. # d-i mirror/no-default boolean true ### Description: Debian archive mirror country: # The goal is to find a mirror of the Debian archive that is close to you on the network -- be # aware that nearby countries, or even your own, may not be the best choice. # d-i mirror/http/countries select US # Possible choices: enter information manually, Argentina, Armenia, Australia, Austria, Belarus, Belgium, Brazil, Bulgaria, Cambodia, Canada, Chile, China, Costa Rica, Croatia, Czechia, Denmark, Estonia, Finland, France, Georgia, Germany, Greece, Hong Kong, Hungary, Iceland, India, Indonesia, Iran, Israel, Italy, Japan, Kazakhstan, Kenya, Latvia, Lithuania, Luxembourg, Moldova, Netherlands, New Caledonia, New Zealand, North Macedonia, Norway, Poland, Portugal, Romania, Russian Federation, Réunion, Singapore, Slovakia, Slovenia, South Africa, South Korea, Spain, Sweden, Switzerland, Taiwan, Thailand, Türkiye, Ukraine, United Kingdom, United States, Uruguay, Vietnam ### Description: Debian archive mirror: # Please select a Debian archive mirror. You should use a mirror in # your country or region if you do not know which mirror has the best # Internet connection to you. # . # Usually, deb.debian.org is a good choice. # d-i mirror/http/mirror select deb.debian.org # Possible choices: ${mirrors} ### Description: Debian archive mirror hostname: # Please enter the hostname of the mirror from which Debian will be downloaded. # . # An alternate port can be specified using the standard [hostname]:[port] # format. # d-i mirror/http/hostname string deb.debian.org ### Description: Debian archive mirror directory: # Please enter the directory in which the mirror of the Debian archive is # located. # d-i mirror/http/directory string /debian/ ### Description: HTTP proxy information (blank for none): # If you need to use a HTTP proxy to access the outside world, enter the # proxy information here. Otherwise, leave this blank. # . # The proxy information should be given in the standard form of # "http://[[user][:pass]@]host[:port]/". # d-i mirror/http/proxy string ### Description: Debian archive mirror country: # The goal is to find a mirror of the Debian archive that is close to you on the network -- be # aware that nearby countries, or even your own, may not be the best choice. # d-i mirror/https/countries select US # Possible choices: enter information manually ### Description: Debian archive mirror hostname: # Please enter the hostname of the mirror from which Debian will be downloaded. # . # An alternate port can be specified using the standard [hostname]:[port] # format. # d-i mirror/ftp/hostname string mirror ### Description: Debian archive mirror directory: # Please enter the directory in which the mirror of the Debian archive is # located. # d-i mirror/ftp/directory string /debian/ ### Description: FTP proxy information (blank for none): # If you need to use a FTP proxy to access the outside world, enter the # proxy information here. Otherwise, leave this blank. # . # The proxy information should be given in the standard form of # "http://[[user][:pass]@]host[:port]/". # d-i mirror/ftp/proxy string ### Description: Protocol for file downloads: # Please select the protocol to be used for downloading files. If unsure, # select "http"; it is less prone to problems involving firewalls. # d-i mirror/protocol select http # Possible choices: ${protocols} ############################ #### clock-setup_0.161_amd64.udeb ############################ ### Description: Is the system clock set to UTC? # System clocks are generally set to Coordinated Universal Time (UTC). # The operating system uses your time zone to convert system time into # local time. This is recommended unless you also use another operating # system that expects the clock to be set to local time. # d-i clock-setup/utc boolean true ### Description: Set the clock using NTP? # The Network Time Protocol (NTP) can be used to set the system's clock. # Your system works best with a correctly set clock. # d-i clock-setup/ntp boolean true ### Description: NTP server to use: # The default NTP server is almost always a good choice, but if # you prefer to use another NTP server, you can enter it here. # d-i clock-setup/ntp-server string 0.debian.pool.ntp.org ### Description: Wait another 30 seconds for hwclock to set the clock? # Setting the hardware clock is taking longer than expected. The 'hwclock' # program used to set the clock may have problems talking to the hardware clock. # . # Check /var/log/syslog or see virtual console 4 for the details. # . # If you choose to not wait for hwclock to finish setting the clock, this # system's clock may not be set correctly. # d-i clock-setup/hwclock-wait boolean false ### Description: for internal use only # Set to true when rdate actually updates the system clock. # d-i clock-setup/system-time-changed boolean false ############################ #### console-keymaps-acorn_1.12-9_all.udeb ############################ ### Description: Keymap to use: # d-i console-keymaps-acorn/keymap select # Possible choices: American English, Belarusian, Belgian, Brazilian (ABNT2 layout), Brazilian (EUA layout), British English, Bulgarian, Canadian Multilingual, Croatian, Czech, Danish, Dutch, Dvorak, Estonian, Finnish, French, German, Greek, Hebrew, Hungarian, Icelandic, Italian, Japanese, Kirghiz, Latin American, Latvian, Lithuanian, Macedonian, Norwegian, Polish, Portuguese, Romanian, Russian, Serbian, Slovakian, Slovene, Spanish, Swedish, Swiss French, Swiss German, Turkish (F layout), Turkish (Q layout), Ukrainian ############################ #### console-keymaps-amiga_1.12-9_all.udeb ############################ ### Description: Keymap to use: # d-i console-keymaps-amiga/keymap select # Possible choices: American English, French, German, Italian, Spanish, Swedish, Swiss German ############################ #### console-keymaps-at_1.12-9_all.udeb ############################ ### Description: Keymap to use: # d-i console-keymaps-at/keymap select # Possible choices: American English, Belarusian, Belgian, Brazilian (ABNT2 layout), Brazilian (EUA layout), British English, Bulgarian, Canadian French, Canadian Multilingual, Croatian, Czech, Danish, Dutch, Dvorak, Estonian, Finnish, French, German, Greek, Hebrew, Hungarian, Icelandic, Italian, Japanese, Kirghiz, Latin American, Latvian, Lithuanian, Macedonian, Norwegian, Polish, Portuguese, Romanian, Russian, Serbian, Slovakian, Slovene, Spanish, Swedish, Swiss French, Swiss German, Thai, Turkish (F layout), Turkish (Q layout), Ukrainian ############################ #### console-keymaps-atari_1.12-9_all.udeb ############################ ### Description: Keymap to use: # d-i console-keymaps-atari/keymap select # Possible choices: American English, British English, French, German, Swedish ############################ #### console-keymaps-dec_1.12-9_all.udeb ############################ ### Description: Keymap to use: # d-i console-keymaps-dec/keymap select # Possible choices: American English ############################ #### console-keymaps-mac_1.12-9_all.udeb ############################ ### Description: Keymap to use: # d-i console-keymaps-mac/keymap select # Possible choices: American English (82 keys), American English (extended kbd), French (alternate), French (extended kbd), German (extended kbd) ############################ #### console-keymaps-sun_1.12-9_all.udeb ############################ ### Description: Keymap to use: # d-i console-keymaps-sun/keymap select # Possible choices: American English, British English, Czech, Finnish, French, German, Japanese (type 4), Japanese (type 5), Norwegian (type 4), Norwegian (type 5), Polish, Russian, Spanish (type 4), Spanish (type 5), Turkish (Q layout) ############################ #### console-keymaps-usb_1.12-9_all.udeb ############################ ### Description: Keymap to use for a USB keyboard: # d-i console-keymaps-usb/keymap select # Possible choices: American English, Belgian, British English, Danish, Dvorak, Finnish, French, German, Italian, Italian, Portuguese, Spanish, Swedish, Swiss French, Swiss German ############################ #### console-setup-udeb_1.221_all.udeb ############################ ### Description: Keyboard model: # Please select the model of the keyboard of this machine. # d-i keyboard-configuration/model select # Possible choices: ${CHOICES} ### Description: Country of origin for the keyboard: # The layout of keyboards varies per country, with some countries # having multiple common layouts. Please select the country of origin # for the keyboard of this computer. # d-i keyboard-configuration/layout select # Possible choices: ${CHOICES} ### Description: Keyboard layout: # Please select the layout matching the keyboard for this machine. # d-i keyboard-configuration/variant select # Possible choices: ${CHOICES} ### Description: Keep the current keyboard layout in the configuration file? # The current keyboard layout in the configuration file # /etc/default/keyboard is defined as XKBLAYOUT="${XKBLAYOUT}" and # XKBVARIANT="${XKBVARIANT}". # . # Please choose whether you want to keep it. If you choose this option, # no questions about the keyboard layout will be asked and the current # configuration will be preserved. # d-i keyboard-configuration/unsupported_config_layout boolean true ### Description: Keep default keyboard layout (${XKBLAYOUTVARIANT})? # The default value for the keyboard layout is XKBLAYOUT="${XKBLAYOUT}" # and XKBVARIANT="${XKBVARIANT}". This default value is based on the # currently defined language/region and the settings in # /etc/X11/xorg.conf. # . # Please choose whether you want to keep it. If you choose this option, # no questions about the keyboard layout will be asked. # d-i keyboard-configuration/unsupported_layout boolean true ### Description: Keep current keyboard options in the configuration file? # The current keyboard options in the configuration file # /etc/default/keyboard are defined as XKBOPTIONS="${XKBOPTIONS}". # . # If you choose to keep these options, no questions about the keyboard # options will be asked. # d-i keyboard-configuration/unsupported_config_options boolean true ### Description: Keep default keyboard options (${XKBOPTIONS})? # The default value for the options of the keyboard layout is # XKBOPTIONS="${XKBOPTIONS}". It is based on the currently defined # language/region and the settings in /etc/X11/xorg.conf. # . # If you choose to keep it, no questions about the keyboard options # will be asked. # d-i keyboard-configuration/unsupported_options boolean true ### Description: Method for toggling between national and Latin mode: # You will need a way to toggle the keyboard between the national # layout and the standard Latin layout. # . # Right Alt or Caps Lock keys are often chosen for ergonomic reasons # (in the latter case, use the combination Shift+Caps Lock for normal Caps # toggle). Alt+Shift is also a popular combination; it will # however lose its usual behavior in Emacs and other programs # that use it for specific needs. # . # Not all listed keys are present on all keyboards. # d-i keyboard-configuration/toggle select Alt+Shift # Possible choices: Caps Lock, Right Alt (AltGr), Right Control, Right Shift, Right Logo key, Menu key, Alt+Shift, Control+Shift, Control+Alt, Alt+Caps Lock, Left Control+Left Shift, Left Alt, Left Control, Left Shift, Left Logo key, Scroll Lock key, No toggling ### Description: Method for temporarily toggling between national and Latin input: # When the keyboard is in national mode and one wants to type only a few # Latin letters, it might be more appropriate to switch temporarily to # Latin mode. The keyboard remains in that mode as long as the chosen key is # kept pressed. That key may also be used to input national letters when # the keyboard is in Latin mode. # . # You can disable this feature by choosing "No temporary switch". # d-i keyboard-configuration/switch select No temporary switch # Possible choices: No temporary switch, Both Logo keys, Right Alt (AltGr), Right Logo key, Left Alt, Left Logo key ### Description: Key to function as AltGr: # With some keyboard layouts, AltGr is a modifier key used to input # some characters, primarily ones that are unusual for the language of the # keyboard layout, such as foreign currency symbols and accented letters. # These are often printed as an extra symbol on keys. # d-i keyboard-configuration/altgr select Right Alt (AltGr) # Possible choices: The default for the keyboard layout, No AltGr key, Right Alt (AltGr), Right Control, Right Logo key, Menu key, Left Alt, Left Logo key, Keypad Enter key, Both Logo keys, Both Alt keys ### Description: Compose key: # The Compose key (known also as Multi_key) causes the computer to interpret # the next few keystrokes as a combination in order to produce a character # not found on the keyboard. # . # On the text console the Compose key does not work in Unicode mode. If not # in Unicode mode, regardless of what you choose here, you can always also # use the Control+period combination as a Compose key. # d-i keyboard-configuration/compose select No compose key # Possible choices: No compose key, Right Alt (AltGr), Right Control, Right Logo key, Menu key, Left Logo key, Caps Lock ### Description: Use Control+Alt+Backspace to terminate the X server? # By default the combination Control+Alt+Backspace does nothing. If # you want it can be used to terminate the X server. # d-i keyboard-configuration/ctrl_alt_bksp boolean false ### Description: Keymap to use: # d-i keyboard-configuration/xkb-keymap select # Possible choices: American English, Albanian, Arabic, Asturian, Bangladesh, Belarusian, Bengali, Belgian, Berber (Latin), Bosnian, Brazilian, British English, Bulgarian (BDS layout), Bulgarian (phonetic layout), Burmese, Canadian French, Canadian Multilingual, Catalan, Chinese, Croatian, Czech, Danish, Dutch, Dvorak, Dzongkha, Esperanto, Estonian, Ethiopian, Finnish, French, Georgian, German, Greek, Gujarati, Gurmukhi, Hebrew, Hindi, Hungarian, Icelandic, Irish, Italian, Japanese, Kannada, Kazakh, Khmer, Kirghiz, Korean, Kurdish (F layout), Kurdish (Q layout), Lao, Latin American, Latvian, Lithuanian, Macedonian, Malayalam, Nepali, Northern Sami, Norwegian, Persian, Philippines, Polish, Portuguese, Punjabi, Romanian, Russian, Serbian (Cyrillic), Sindhi, Sinhala, Slovak, Slovenian, Spanish, Swedish, Swiss French, Swiss German, Tajik, Tamil, Telugu, Thai, Tibetan, Turkish (F layout), Turkish (Q layout), Ukrainian, Uyghur, Vietnamese ### Description: for internal use # d-i keyboard-configuration/modelcode string ### Description: for internal use # d-i keyboard-configuration/layoutcode string ### Description: for internal use # d-i keyboard-configuration/variantcode string ### Description: for internal use # d-i keyboard-configuration/optionscode string ### Description: for internal use # d-i keyboard-configuration/store_defaults_in_debconf_db boolean true ############################ #### debian-edu-install-udeb_2.12.10~deb12u1_all.udeb ############################ ############################ #### debian-edu-profile-udeb_2.12.10~deb12u1_all.udeb ############################ ### Description: Profile(s) to apply to this machine: # Profiles determine how the machine can be used out-of-the-box: # . # - Main Server: reserved for the Debian Edu server. It does not include # any GUI (Graphical User Interface). There should only # be one such server on a Debian Edu network. # - Workstation: for normal machines on the Debian Edu network. # - Roaming Workstation: for single user machines on the Debian Edu # network which some times travel outside the network. # - LTSP Server: includes 'Workstation' and requires two network cards. # - Standalone: for machines meant to be used outside the Debian Edu # network. It includes a GUI and conflicts with other # profiles. # - Minimal: fully integrated into the Debian Edu network but # contains only a basic system without any GUI. # d-i debian-edu-install/profile multiselect # Possible choices: Main Server, Workstation, Roaming Workstation, LTSP Server, Standalone, Minimal ### Description: Really use the automatic partitioning tool? # This will destroy the partition table on all disks in the machine. # REPEAT: THIS WILL WIPE CLEAN ALL HARD DISKS IN THE MACHINE! # If you have important data that are not backed up, you may want to # stop now in order to do a backup. In that case, you'll have to # restart the installation later. # d-i debian-edu-install/confirm boolean false ### Description: Participate in the package usage survey? # The system may anonymously supply the distribution developers with # statistics about the most used packages on this system. This # information influences decisions such as which packages should go on # the first distribution CD. # . # If you choose to participate, the automatic submission script will # run once every week, sending statistics to the distribution developers. # The collected statistics can be viewed on http://popcon.debian.org/. # . # This choice can be later modified by running "dpkg-reconfigure # popularity-contest". # d-i debian-edu-install/participate-popcon boolean ### Description: Available disk space is too small. Abort the installation? # The available disk space is too small for the selected profiles. # Please choose whether you want to abort the installation or continue # without setting up the recommended partitioning setup # . # If you choose to continue, one single partition will be used # for all system files _and_ user files. Note that this can cause stability # problems after a while. # d-i debian-edu-install/disk-too-small boolean true ### Description: for internal use - disable sync when installing packages # This value can be preseeded to true if tasksel/apt/dpkg should run # within a eatmydata environment disabling file system sync. # d-i debian-edu-install/quick-install boolean true ############################ #### di-utils_1.146_amd64.udeb ############################ ### Description: for internal use; can be preseeded # Extra (custom) boot options to add for target system. # d-i debian-installer/add-kernel-opts string ### Description: Dummy template for preseeding unavailable questions # The answer to this question has been preseeded (${ID}). # If you see this template, you've found a bug in the installer; # please file a report. # d-i debian-installer/dummy string ### Description: ${TITLE} # d-i debian-installer/shell-plugin terminal ############################ #### di-utils-exit-installer_1.146_all.udeb ############################ ############################ #### di-utils-reboot_1.146_all.udeb ############################ ### Description: Are you sure you want to exit now? # If you have not finished the install, your system may be left in an # unusable state. # d-i di-utils-reboot/really_reboot boolean false ############################ #### di-utils-shell_1.146_all.udeb ############################ ############################ #### depthcharge-tools-installer_2_all.udeb ############################ ### Description: Reconfigure initramfs policies? # Could not generate a small enough boot image for this board. Usually # this can be resolved by including less modules in the initramfs. # d-i depthcharge-tools-installer/initramfs_too_big boolean ### Description: for internal use; can be preseeded # If set, this template will override this package's board detection # and configure depthcharge-tools in the target system to do so as well. # d-i depthcharge-tools-installer/board string ############################ #### espeakup-udeb_0.90-13_amd64.udeb ############################ ### Description: for internal use # d-i espeakup/voice string ### Description: for internal use # d-i espeakup/card string ############################ #### finish-install_2.117_all.udeb ############################ ### Description: for internal use; can be preseeded # Don't comment out regular Virtual Consoles during serial console installs # d-i finish-install/keep-consoles boolean false ############################ #### grub-installer_1.194_amd64.udeb ############################ ### Description: Install the GRUB boot loader to your primary drive? # The following other operating systems have been detected on this # computer: ${OS_LIST} # . # If all of your operating systems are listed above, then it should be safe to # install the boot loader to your primary drive (UEFI partition/boot record). # When your computer boots, you will be able to choose to load one of these # operating systems or the newly installed Debian system. # d-i grub-installer/with_other_os boolean true ### Description: Install the GRUB boot loader to your primary drive? # It seems that this new installation is the only operating system # on this computer. If so, it should be safe to install the GRUB boot loader # to your primary drive (UEFI partition/boot record). # . # Warning: If your computer has another operating system that the installer # failed to detect, this will make that operating system temporarily # unbootable, though GRUB can be manually configured later to boot it. # d-i grub-installer/only_debian boolean true ### Description: Install the GRUB boot loader to the multipath device? # Installation of GRUB on multipath is experimental. # . # GRUB is always installed to the master boot record (MBR) of the multipath # device. It is also assumed that the WWID of this device is selected as boot # device in the system's FibreChannel adapter BIOS. # . # The GRUB root device is: ${GRUBROOT}. # d-i grub-installer/multipath boolean true ### Description: Device for boot loader installation: # You need to make the newly installed system bootable, by installing # the GRUB boot loader on a bootable device. The usual way to do this is to # install GRUB to your primary drive (UEFI partition/boot record). You may # instead install GRUB to a different drive (or partition), or to removable # media. # . # The device notation should be specified as a device in /dev. Below are some # examples: # - "/dev/sda" will install GRUB to your primary drive (UEFI partition/boot # record); # - "/dev/sdb" will install GRUB to a secondary drive (which may for instance # be a thumbdrive); # - "/dev/fd0" will install GRUB to a floppy. # d-i grub-installer/bootdev string ### Description: Device for boot loader installation: # You need to make the newly installed system bootable, by installing # the GRUB boot loader on a bootable device. The usual way to do this is to # install GRUB to your primary drive (UEFI partition/boot record). You may # instead install GRUB to a different drive (or partition), or to removable # media. # d-i grub-installer/choose_bootdev select # Possible choices: Enter device manually, ${DESCRIPTIONS} ### Description: GRUB password: # The GRUB boot loader offers many powerful interactive features, which could # be used to compromise your system if unauthorized users have access to the # machine when it is starting up. To defend against this, you may choose a # password which will be required before editing menu entries or entering the # GRUB command-line interface. By default, any user will still be able to # start any menu entry without entering the password. # . # If you do not wish to set a GRUB password, leave this field blank. # d-i grub-installer/password password ### Description: Re-enter password to verify: # Please enter the same GRUB password again to verify that you have typed it # correctly. # d-i grub-installer/password-again password ### Description: for internal use; can be preseeded # d-i grub-installer/password-crypted password ### Description: for internal use; can be preseeded # Set this to false to install GRUB Legacy rather than GRUB 2, if possible. # d-i grub-installer/grub2_instead_of_grub_legacy boolean true ### Description: Install GRUB? # GRUB 2 is the next generation of GNU GRUB, the boot loader that is commonly # used on i386/amd64 PCs. It is now also available for ${ARCH}. # . # It has interesting new features but is still experimental software # for this architecture. If you choose to install it, you should be prepared # for breakage, and have an idea on how to recover your system if it # becomes unbootable. You're advised not to try this in production # environments. # d-i grub-installer/grub_not_mature_on_this_platform boolean false ### Description: for internal use; can be preseeded # Skip installing grub? # d-i grub-installer/skip boolean false ### Description: for internal use; can be preseeded # Make sure that at least one partition is marked as active (bootable). # d-i grub-installer/make_active boolean true ### Description: Force GRUB installation to the EFI removable media path? # It seems that this computer is configured to boot via EFI, but maybe # that configuration will not work for booting from the hard # drive. Some EFI firmware implementations do not meet the EFI # specification (i.e. they are buggy!) and do not support proper # configuration of boot options from system hard drives. # . # A workaround for this problem is to install an extra copy of the EFI # version of the GRUB boot loader to a fallback location, the # "removable media path". Almost all EFI systems, no matter how buggy, # will boot GRUB that way. # . # Warning: If the installer failed to detect another operating system # that is present on your computer that also depends on this fallback, # installing GRUB there will make that operating system temporarily # unbootable. GRUB can be manually configured later to boot it if # necessary. # d-i grub-installer/force-efi-extra-removable boolean false ### Description: Update NVRAM variables to automatically boot into Debian? # GRUB can configure your platform's NVRAM variables so that it boots into # Debian automatically when powered on. However, you may prefer to disable # this behavior and avoid changes to your boot configuration. For example, # if your NVRAM variables have been set up such that your system contacts a # PXE server on every boot, this would preserve that behavior. # d-i grub-installer/update-nvram boolean true ### Description: Run os-prober automatically to detect and boot other OSes? # GRUB can use the os-prober tool to attempt to detect other # operating systems on your computer and add them to its list of boot # options automatically. # . # If your computer has multiple operating systems installed, then this # is probably what you want. However, if your computer is a host for # guest OSes installed via LVM or raw disk devices, running os-prober # can cause damage to those guest OSes as it mounts filesystems to look # for things. # . # The following other operating systems have been detected on this # computer: ${OS_LIST} # d-i grub-installer/enable_os_prober_otheros_yes boolean true ### Description: Run os-prober automatically to detect and boot other OSes? # GRUB can use the os-prober tool to attempt to detect other # operating systems on your computer and add them to its list of boot # options automatically. # . # If your computer has multiple operating systems installed, then this # is probably what you want. However, if your computer is a host for # guest OSes installed via LVM or raw disk devices, running os-prober # can cause damage to those guest OSes as it mounts filesystems to look # for things. # . # os-prober did not detect any other operating systems on your computer # at this time, but you may still wish to enable it in case you install # more in the future. # d-i grub-installer/enable_os_prober_otheros_no boolean false ############################ #### disk-detect_1.159_amd64.udeb ############################ ### Description: Driver needed for your disk drive: # No disk drive was detected. If you know the name of the driver # needed by your disk drive, you can select it from the list. # d-i disk-detect/module_select select continue with no disk drive # Possible choices: continue with no disk drive, ${CHOICES}, none of the above ### Description: for internal use; can be preseeded # Check for the presence of multipath devices? # d-i disk-detect/multipath/enable boolean false ############################ #### driver-injection-disk-detect_1.159_all.udeb ############################ ### Description: Load drivers from internal virtual driver disk? # Installing on this hardware may require some drivers provided by the # manufacturer to be loaded from the built-in driver injection disk. # d-i driver-injection-disk/load boolean true ############################ #### ethdetect_1.159_all.udeb ############################ ### Description: Driver needed by your Ethernet card: # No Ethernet card was detected. If you know the name of the driver # needed by your Ethernet card, you can select it from the list. # d-i ethdetect/module_select select no ethernet card # Possible choices: no ethernet card, ${CHOICES}, none of the above ### Description: Do you intend to use FireWire Ethernet? # No Ethernet card was detected, but a FireWire interface is present. # It's possible, though unlikely, that with the right FireWire hardware # connected to it, this could be your primary Ethernet interface. # d-i ethdetect/use_firewire_ethernet boolean false ### Description: for internal use; can be preseeded # Prompt for missing firmware to be provided before the network is up? # d-i ethdetect/prompt_missing_firmware boolean true ############################ #### hw-detect_1.159_amd64.udeb ############################ ### Description: Modules to load: # The following Linux kernel modules were detected as matching your # hardware. If you know some are unnecessary, or cause problems, you can # choose not to load them. If you're unsure, you should leave them all # selected. # d-i hw-detect/select_modules multiselect # Possible choices: ${list} ### Description: Start PC card services? # Please choose whether PC card services should be started in order to allow # the use of PCMCIA cards. # d-i hw-detect/start_pcmcia boolean true ### Description: PCMCIA resource range options: # Some PCMCIA hardware needs special resource configuration options in # order to work, and can cause the computer to freeze otherwise. For # example, some Dell laptops need "exclude port 0x800-0x8ff" to be # specified here. These options will be added to /etc/pcmcia/config.opts. # See the installation manual or the PCMCIA HOWTO for more information. # . # For most hardware, you do not need to specify anything here. # d-i hw-detect/pcmcia_resources string ### Description: Additional parameters for module ${MODULE}: # The module ${MODULE} failed to load. You may need to pass parameters # to the module to make it work; this is common with older hardware. # These parameters are often I/O port and IRQ numbers that vary from machine # to machine and cannot be determined from the hardware. An example string # looks something like "irq=7 io=0x220" # . # If you don't know what to enter, consult your documentation, or leave it # blank to not load the module. # d-i hw-detect/retry_params string ### Description: Load missing drivers from removable media? # A driver for your hardware is not available. You may need # to load drivers from removable media, such as a USB stick, or driver floppy. # . # If you have such media available now, insert it, and continue. # d-i hw-detect/load_media boolean false ### Description: Load missing firmware from removable media? # Some of your hardware needs non-free firmware files to operate. The # firmware can be loaded from removable media, such as a USB stick or # floppy. # . # The missing firmware files are: ${FILES} # . # If you have such media available now, insert it, and continue. # d-i hw-detect/load_firmware boolean true ### Description: for internal use; can be preseeded # d-i hw-detect/load-ide boolean false ############################ #### save-logs_2.89_all.udeb ############################ ### Description: How should the debug logs be saved or transferred? # Debugging log files for the installer are accessible in /var/log/. They can # be served up over the network (a small webserver is started on this machine, # to achieve that), saved to some mounted file system (like the one on a USB # stick), or to a floppy. # d-i save-logs/menu select # Possible choices: serve over network, mounted file system, floppy ### Description: Directory in which to save debug logs: # Please make sure the file system you want to save debug logs on is mounted # before you continue. # d-i save-logs/directory string /mnt ############################ #### iso-scan_1.90_all.udeb ############################ ### Description: for internal use only # Suite to install # d-i cdrom/suite select # Possible choices: stable, testing, unstable ### Description: for internal use only # Codename for the selected suite # d-i cdrom/codename string ### Description: Do full disk search for installer ISO image? # The quick scan for installer ISO images, which looks only in common # places, did not find an installer ISO image. It's possible that a # more thorough search will find the ISO image, but it may take a long # time. # d-i iso-scan/ask_second_pass boolean false ### Description: Device or partition to search for installation ISO(s): # You can select a device, manually specify a non-detected device, or # rescan available devices (useful for slow USB devices). # d-i shared/ask_device select all # Possible choices: All detected devices, ${DEVICES_LIST}, Enter device manually ### Description: Device name: # d-i shared/enter_device string ### Description: ISO file to use: # One or multiple ISO files have been detected on the selected device(s). # Please choose which one you want to use, or ask for a more thorough search. # d-i iso-scan/ask_which_iso select # Possible choices: ${ISOS_LIST}, Full search ### Description: Is ISO file ${FILENAME} the correct image for installation? # The ISO file ${FILENAME} on ${DEVICE} (${SUITE}, code ${CODENAME}, # self-described as '${DESCRIPTION}') will be used as the # installation ISO image. # . # If multiple ISO files exist on the same installer drive, # you may select which one you want to use. # d-i iso-scan/ask_right_iso boolean true ### Description: Copy the ISO image into RAM before mounting it? # There is enough available memory to be able to copy the ISO image into # RAM. # . # Choosing this option allows reusing the disk hosting the ISO image. If you # don't do it, the disk will be actively used to access the ISO image and # it can't be partitioned by the installer. # . # Note however that if you overwrite the disk containing the ISO image, you # should not reboot before the end of the installation as you will not be # able to restart the installer since the ISO image will be gone from the # hard disk and memory. # d-i iso-scan/copy_iso_to_ram boolean false ############################ #### load-iso_1.90_all.udeb ############################ ############################ #### kbd-chooser_1.71_amd64.udeb ############################ ### Description: Type of keyboard: # Please choose the type of keyboard to configure. # d-i console-tools/archs select # Possible choices: ${KBD-ARCHS-L10N} ### Description: For internal use (keyboard chosen by user) # d-i debian-installer/keymap string ### Description: For internal use (Is a serial console in use?) # d-i debian-installer/serial-console boolean false ### Description: For internal use (Is a User Mode Linux console in use?) # d-i debian-installer/uml-console boolean false ############################ #### initrd-kickseed_0.63_all.udeb ############################ ############################ #### live-installer_58_amd64.udeb ############################ ### Description: Type of installation: # The live system can be installed to hard disk using one of the following # options. # . # If you choose 'normal', the system will be installed as a regular system. # If you choose 'live', the installed system will continue to act as a # live system but it can then be launched directly from the hard disk. # d-i live-installer/mode select normal # Possible choices: normal, live ### Description: for internal use; can be preseeded # If false, uses base-installer for installation # d-i live-installer/enable boolean true ############################ #### localechooser_2.103_amd64.udeb ############################ ### Description: for internal use only # d-i debian-installer/language string ### Description: for internal use; can be preseeded # d-i debian-installer/country string ### Description: System locale: # Select the default locale for the installed system. # d-i debian-installer/locale select # Possible choices: ${LOCALELIST} ### Description: for internal use only # d-i debian-installer/consoledisplay string ### Description: Language: # Choose the language to be used for the installation process. The selected # language will also be the default language for the installed system. # d-i localechooser/languagelist select en # Possible choices: ${NAMES_EN} ### Description: Continue the installation in the selected language? # The translation of the installer is incomplete for the selected language. # . # ${TXT-WARN} # . # ${TXT-ABORT} # d-i localechooser/translation/warn-severe boolean false ### Description: Continue the installation in the selected language? # The translation of the installer is not fully complete for the selected # language. # . # ${TXT-WARN} # d-i localechooser/translation/warn-light boolean true ### Description: Country to base default locale settings on: # ${TXT} # d-i localechooser/preferred-locale select # Possible choices: ${CHOICES} ### Description: Additional locales: # Based on your previous choices, the default locale currently selected for the # installed system is '${LOCALE}'. # . # If you wish to use a different default or to also have other locales available, # you may choose additional locales to be installed. If you are unsure it is # best to just use the selected default. # d-i localechooser/supported-locales multiselect # Possible choices: ${LOCALELIST} ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/countrylist/Africa select # Possible choices: Algeria, Angola, Benin, Botswana, Burkina Faso, Burundi, Cabo Verde, Cameroon, Central African Republic, Chad, Congo, Congo\, The Democratic Republic of the, Côte d'Ivoire, Djibouti, Egypt, Equatorial Guinea, Eritrea, Eswatini, Ethiopia, Gabon, Gambia, Ghana, Guinea, Guinea-Bissau, Kenya, Lesotho, Liberia, Libya, Malawi, Mali, Mauritania, Morocco, Mozambique, Namibia, Niger, Nigeria, Rwanda, Sao Tome and Principe, Senegal, Sierra Leone, Somalia, South Africa, South Sudan, Sudan, Tanzania, Togo, Tunisia, Uganda, Western Sahara, Zambia, Zimbabwe ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/countrylist/Antarctica select # Possible choices: Antarctica ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/countrylist/Asia select # Possible choices: Afghanistan, Bahrain, Bangladesh, Bhutan, Brunei Darussalam, Cambodia, China, Hong Kong, India, Indonesia, Iran, Iraq, Israel, Japan, Jordan, Kazakhstan, Kuwait, Kyrgyzstan, Laos, Lebanon, Macao, Malaysia, Mongolia, Myanmar, Nepal, North Korea, Oman, Pakistan, Palestine\, State of, Philippines, Qatar, Saudi Arabia, Singapore, South Korea, Sri Lanka, Syria, Taiwan, Tajikistan, Thailand, Timor-Leste, Turkmenistan, Türkiye, United Arab Emirates, Uzbekistan, Vietnam, Yemen ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/countrylist/Atlantic_Ocean select # Possible choices: Bouvet Island, Falkland Islands (Malvinas), Saint Helena\, Ascension and Tristan da Cunha, South Georgia and the South Sandwich Islands ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/countrylist/Caribbean select # Possible choices: Anguilla, Antigua and Barbuda, Aruba, Bahamas, Barbados, Bermuda, Bonaire\, Sint Eustatius and Saba, Cayman Islands, Cuba, Curaçao, Dominica, Dominican Republic, Grenada, Guadeloupe, Haiti, Jamaica, Martinique, Montserrat, Puerto Rico, Saint Barthélemy, Saint Kitts and Nevis, Saint Lucia, Saint Martin (French part), Saint Vincent and the Grenadines, Sint Maarten (Dutch part), Trinidad and Tobago, Turks and Caicos Islands, Virgin Islands\, British, Virgin Islands\, U.S. ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/countrylist/Central_America select # Possible choices: Belize, Costa Rica, El Salvador, Guatemala, Honduras, Nicaragua, Panama ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/countrylist/Europe select # Possible choices: Albania, Andorra, Armenia, Austria, Azerbaijan, Belarus, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, Faroe Islands, Finland, France, Georgia, Germany, Gibraltar, Greece, Greenland, Guernsey, Holy See (Vatican City State), Hungary, Iceland, Ireland, Isle of Man, Italy, Jersey, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta, Moldova, Monaco, Montenegro, Netherlands, North Macedonia, Norway, Poland, Portugal, Romania, Russian Federation, San Marino, Serbia, Slovakia, Slovenia, Spain, Svalbard and Jan Mayen, Sweden, Switzerland, Ukraine, United Kingdom, Åland Islands ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/countrylist/Indian_Ocean select # Possible choices: British Indian Ocean Territory, Christmas Island, Cocos (Keeling) Islands, Comoros, French Southern Territories, Heard Island and McDonald Islands, Madagascar, Maldives, Mauritius, Mayotte, Réunion, Seychelles ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/countrylist/North_America select # Possible choices: Canada, Mexico, Saint Pierre and Miquelon, United States ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/countrylist/Oceania select # Possible choices: American Samoa, Australia, Cook Islands, Fiji, French Polynesia, Guam, Kiribati, Marshall Islands, Micronesia\, Federated States of, Nauru, New Caledonia, New Zealand, Niue, Norfolk Island, Northern Mariana Islands, Palau, Papua New Guinea, Pitcairn, Samoa, Solomon Islands, Tokelau, Tonga, Tuvalu, United States Minor Outlying Islands, Vanuatu, Wallis and Futuna ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/countrylist/South_America select # Possible choices: Argentina, Bolivia, Brazil, Chile, Colombia, Ecuador, French Guiana, Guyana, Paraguay, Peru, Suriname, Uruguay, Venezuela ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/continentlist select # Possible choices: Africa, Antarctica, Asia, Atlantic Ocean, Caribbean, Central America, Europe, Indian Ocean, North America, Oceania, South America ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/ar select # Possible choices: Syria, Jordan, United Arab Emirates, Bahrain, Algeria, Saudi Arabia, Sudan, Iraq, Kuwait, Morocco, India, Yemen, Tunisia, South Sudan, Oman, Qatar, Lebanon, Libya, Egypt, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/bn select # Possible choices: Bangladesh, India, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/bo select # Possible choices: China, India, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/ca select # Possible choices: Andorra, Spain, France, Italy, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/de select # Possible choices: Belgium, Germany, Italy, Liechtenstein, Luxembourg, Switzerland, Austria, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/el select # Possible choices: Greece, Cyprus, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/en select # Possible choices: Antigua and Barbuda, Australia, Botswana, Canada, Hong Kong, India, Ireland, Israel, New Zealand, Nigeria, Philippines, Seychelles, Singapore, South Africa, United Kingdom, United States, Zambia, Zimbabwe, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/es select # Possible choices: Argentina, Bolivia, Chile, Colombia, Costa Rica, Cuba, Ecuador, El Salvador, Spain, United States, Guatemala, Honduras, Mexico, Nicaragua, Panama, Paraguay, Peru, Puerto Rico, Dominican Republic, Uruguay, Venezuela, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/eu select # Possible choices: Spain, France, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/fr select # Possible choices: Belgium, Canada, France, Luxembourg, Switzerland, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/it select # Possible choices: Italy, Switzerland, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/nl select # Possible choices: Aruba, Belgium, Netherlands, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/pa select # Possible choices: Pakistan, India, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/pt select # Possible choices: Brazil, Portugal, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/pt_BR select # Possible choices: Brazil, Portugal, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/ru select # Possible choices: Russian Federation, Ukraine, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/sq select # Possible choices: North Macedonia, Albania, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/sr select # Possible choices: Serbia, Montenegro, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/sv select # Possible choices: Finland, Sweden, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/ta select # Possible choices: India, Sri Lanka, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/tr select # Possible choices: Cyprus, Türkiye, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/zh_CN select # Possible choices: China, Taiwan, Singapore, Hong Kong, other ### Description: ${TXT1} # ${TXT2} # . # ${TXT3} # d-i localechooser/shortlist/zh_TW select # Possible choices: China, Singapore, Taiwan, Hong Kong, other ############################ #### lowmem_1.51_all.udeb ############################ ############################ #### lowmemcheck_1.51_amd64.udeb ############################ ############################ #### lvmcfg_1.63_all.udeb ############################ ############################ #### lvmcfg-utils_1.63_all.udeb ############################ ### Description: Activate existing volume groups? # ${COUNT} existing volume groups have been found. Please # indicate whether you want to activate them. # d-i lvmcfg/activevg boolean true ### Description: LVM configuration action: # This is the Logical Volume Manager configuration menu. # d-i lvmcfg/mainmenu select # Possible choices: Modify volume groups (VG), Modify logical volumes (LV), Leave ### Description: Volume groups configuration action: # d-i lvmcfg/vgmenu select # Possible choices: Create volume groups, Delete volume groups, Extend volume groups, Reduce volume groups, Leave ### Description: Logical volumes configuration action: # d-i lvmcfg/lvmenu select # Possible choices: Create logical volumes, Delete logical volumes, Leave ### Description: Devices for the new volume group: # Please select the devices for the new volume group. # . # You can select one or more devices. # d-i lvmcfg/vgcreate_parts multiselect # Possible choices: ${PARTITIONS} ### Description: Volume group name: # Please enter the name you would like to use for the new volume group. # d-i lvmcfg/vgcreate_name string ### Description: Volume group to delete: # Please select the volume group you wish to delete. # d-i lvmcfg/vgdelete_names select # Possible choices: ${GROUPS} ### Description: Really delete the volume group? # Please confirm the ${VG} volume group removal. # d-i lvmcfg/vgdelete_confirm boolean true ### Description: Volume group to extend: # Please select the volume group you wish to extend. # d-i lvmcfg/vgextend_names select # Possible choices: ${GROUPS} ### Description: Devices to add to the volume group: # Please select the devices you wish to add to the volume group. # . # You can select one or more devices. # d-i lvmcfg/vgextend_parts multiselect # Possible choices: ${PARTITIONS} ### Description: Volume group to reduce: # Please select the volume group you wish to reduce. # d-i lvmcfg/vgreduce_names select # Possible choices: ${GROUPS} ### Description: Device to remove from volume group: # Please select the device you wish to remove from the volume group. # d-i lvmcfg/vgreduce_parts select # Possible choices: ${PARTITIONS} ### Description: Logical volume name: # Please enter the name you would like to use for the new logical volume. # d-i lvmcfg/lvcreate_name string ### Description: Volume group: # Please select the volume group where the new logical volume # should be created. # d-i lvmcfg/lvcreate_vgnames select # Possible choices: ${GROUPS} ### Description: Logical volume size: # Please enter the size of the new logical volume. The size may be # entered in the following formats: 10K (Kilobytes), 10M (Megabytes), # 10G (Gigabytes), 10T (Terabytes). The default unit is Megabytes. # d-i lvmcfg/lvcreate_size string ### Description: Volume group: # Please select the volume group which contains the logical volume to # be deleted. # d-i lvmcfg/lvdelete_vgnames select # Possible choices: ${GROUPS} ### Description: Logical volume: # Please select the logical volume to be deleted on ${VG}. # d-i lvmcfg/lvdelete_lvnames select # Possible choices: ${LVS} ############################ #### main-menu_1.65_amd64.udeb ############################ ### Description: Choose the next step in the install process: # d-i debian-installer/main-menu select ${DEFAULT} # Possible choices: ${MENU} ### Description: Choose an installation step: # This installation step depends on one or more other steps that # have not yet been performed. # d-i debian-installer/missing-provide select ${DEFAULT} # Possible choices: ${CHOICES} ############################ #### mdcfg-utils_1.77_all.udeb ############################ ### Description: Multidisk configuration actions # This is the Multidisk (MD) and software RAID configuration menu. # . # Please select one of the proposed actions to configure multidisk devices. # d-i mdcfg/mainmenu select # Possible choices: Create MD device, Delete MD device, Finish ### Description: Multidisk device type: # Please choose the type of the multidisk device to be created. # d-i mdcfg/createmain select # Possible choices: RAID0, RAID1, RAID5, RAID6, RAID10, Cancel ### Description: Active devices for the RAID0 multidisk device: # You have chosen to create a RAID0 array. Please choose the active devices # in this array. # d-i mdcfg/raid0devs multiselect # Possible choices: ${PARTITIONS} ### Description: Number of active devices for the RAID${LEVEL} array: # The RAID${LEVEL} array will consist of both active and spare partitions. The active # partitions are those used, while the spare devices will only be used if one or # more of the active devices fail. A minimum of ${MINIMUM} active devices is # required. # . # NOTE: this setting cannot be changed later. # d-i mdcfg/raiddevcount string ### Description: Active devices for the RAID${LEVEL} multidisk device: # You have chosen to create a RAID${LEVEL} array with ${COUNT} active devices. # . # Please choose which partitions are active devices. # You must select exactly ${COUNT} partitions. # d-i mdcfg/raiddevs multiselect # Possible choices: ${PARTITIONS} ### Description: Number of spare devices for the RAID${LEVEL} array: # d-i mdcfg/raidsparecount string ### Description: Spare devices for the RAID${LEVEL} multidisk device: # You have chosen to create a RAID${LEVEL} array with ${COUNT} spare devices. # . # Please choose which partitions will be used as spare devices. # You may choose up to ${COUNT} partitions. If you choose less than ${COUNT} # devices, the remaining partitions will be added to the array as "missing". # You will be able to add them later to the array. # d-i mdcfg/raidsparedevs multiselect # Possible choices: ${PARTITIONS} ### Description: Layout of the RAID10 multidisk device: # The layout must be n, o, or f (arrangement of the copies) followed # by a number (number of copies of each chunk). The number must be # smaller or equal to the number of active devices. # . # The letter is the arrangement of the copies: # n - near copies: Multiple copies of one data block are at similar # offsets in different devices. # f - far copies: Multiple copies have very different offsets # o - offset copies: Rather than the chunks being duplicated within a # stripe, whole stripes are duplicated but are rotated by one # device so duplicate blocks are on different devices. # . # NOTE: this setting cannot be changed later. # d-i mdcfg/raid10layout string ### Description: Multidisk device to be deleted: # Deleting a multidisk device will stop it and clear the superblock of all its # components. # . # Please note this will not immediately allow you to reuse the # partitions or devices in a new multidisk device. The array will however # be unusable after the deletion. # . # If you select a device for deletion, you will get some information about it # and you will be given the option of aborting this operation. # d-i mdcfg/deletemenu select # Possible choices: ${DEVICES}, Cancel ### Description: Really delete this multidisk device? # Please confirm whether you really want to delete the following multidisk # device: # . # Device: ${DEVICE} # Type: ${TYPE} # Component devices: # . # ${DEVICES} # d-i mdcfg/deleteverify boolean false ############################ #### load-media_1.57_all.udeb ############################ ### Description: Load drivers from removable media now? # You probably need to load drivers from removable media before continuing # with the installation. If you know that the install will work without extra # drivers, you can skip this step. # . # If you do need to load drivers, insert the appropriate removable media, # such as a driver floppy or USB stick before continuing. # d-i retriever/media/loadnow boolean true ### Description: Unknown removable media. Try to load anyway? # Detected removable media that is not a known driver media. Please make sure # that the correct media is inserted. You can still continue if you have an # unofficial removable media you want to use. # d-i retriever/media/unknown boolean false ### Description: Load drivers from another removable media? # To load additional drivers from another removable media, please insert # the appropriate removable media, such as a driver floppy or USB stick # before continuing. # d-i retriever/media/loadanother boolean true ############################ #### media-retriever_1.57_all.udeb ############################ ############################ #### download-installer_1.57_all.udeb ############################ ############################ #### net-retriever_1.57_all.udeb ############################ ### Description: Downloading a file failed: # The installer failed to download a file from the mirror. This may be a # problem with your network, or with the mirror. You can choose to retry # the download, select a different mirror, or cancel and choose another # installation method. # d-i retriever/net/error select Retry # Possible choices: Retry, Change mirror, Cancel ############################ #### netcfg_1.187_amd64.udeb ############################ ### Description: for internal use; can be preseeded # Set to false to disable netcfg entirely via preseed. # d-i netcfg/enable boolean true ### Description: Auto-configure networking? # Networking can be configured either by entering all the information # manually, or by using DHCP (or a variety of IPv6-specific methods) to # detect network settings automatically. If you choose to use # autoconfiguration and the installer is unable to get a working # configuration from the network, you will be given the opportunity to # configure the network manually. # d-i netcfg/use_autoconfig boolean true ### Description: Domain name: # The domain name is the part of your Internet address to the right of your # host name. It is often something that ends in .com, .net, .edu, or .org. # If you are setting up a home network, you can make something up, but make # sure you use the same domain name on all your computers. # d-i netcfg/get_domain string ### Description: Name server addresses: # The name servers are used to look up host names on the network. # Please enter the IP addresses (not host names) of up to 3 name servers, # separated by spaces. Do not use commas. The first name server in the list # will be the first to be queried. If you don't want to use any name server, # just leave this field blank. # d-i netcfg/get_nameservers string ### Description: Primary network interface: # Your system has multiple network interfaces. Choose the one to use as # the primary network interface during the installation. If possible, the # first connected network interface found has been selected. # d-i netcfg/choose_interface select # Possible choices: ${ifchoices} ### Description: Wireless ESSID for ${iface}: # ${iface} is a wireless network interface. Please enter the name (the ESSID) # of the wireless network you would like ${iface} to use. If you would like # to use any available network, leave this field blank. # d-i netcfg/wireless_essid string ### Description: Wireless ESSID for ${iface}: # Attempting to find an available wireless network failed. # . # ${iface} is a wireless network interface. Please enter the name (the ESSID) # of the wireless network you would like ${iface} to use. To connect to any # available network, leave this field blank. # d-i netcfg/wireless_essid_again string ### Description: Wireless network type for ${iface}: # Choose WEP/Open if the network is open or secured with WEP. # Choose WPA/WPA2 if the network is protected with WPA/WPA2 PSK # (Pre-Shared Key). # d-i netcfg/wireless_security_type select wpa # Possible choices: WEP/Open Network, WPA/WPA2 PSK ### Description: WEP key for wireless device ${iface}: # If applicable, please enter the WEP security key for the wireless # device ${iface}. There are two ways to do this: # . # If your WEP key is in the format 'nnnn-nnnn-nn', 'nn:nn:nn:nn:nn:nn:nn:nn', # or 'nnnnnnnn', where n is a number, just enter it as it is into this field. # . # If your WEP key is in the format of a passphrase, prefix it with 's:' # (without quotes). # . # Of course, if there is no WEP key for your wireless network, leave this # field blank. # d-i netcfg/wireless_wep string ### Description: WPA/WPA2 passphrase for wireless device ${iface}: # Enter the passphrase for WPA/WPA2 PSK authentication. This should be the # passphrase defined for the wireless network you are trying to use. # d-i netcfg/wireless_wpa string ### Description: Hostname: # Please enter the hostname for this system. # . # The hostname is a single word that identifies your system to the network. # If you don't know what your hostname should be, consult your network # administrator. If you are setting up your own home network, you can make # something up here. # d-i netcfg/get_hostname string debian ### Description: for internal use; can be preseeded # Hostname to set for the system; ignores names provided by DHCP or DNS. # d-i netcfg/hostname string ### Description: Type of wireless network: # Wireless networks are either managed or ad-hoc. If you use a real access # point of some sort, your network is Managed. If another computer is your # 'access point', then your network may be Ad-hoc. # d-i netcfg/wireless_adhoc_managed select Infrastructure (Managed) network # Possible choices: Infrastructure (Managed) network, Ad-hoc network (Peer to peer) ### Description: for internal use; can be preseeded # Set to true to force static network configuration # d-i netcfg/disable_autoconfig boolean false ### Description: for internal use; can be preseeded (deprecated) # Set to true to force static network configuration (deprecated) # d-i netcfg/disable_dhcp boolean false ### Description: for internal use; can be preseeded # Specifies what kind of network connection management tool should be # configured post-installation if multiple are available. Automatic # selection is used in this order when not specified: network-manager if # available (on Linux only), ethernet configuration through ifupdown on wired # installation and loopback configuration through ifupdown on wireless # installations. # d-i netcfg/target_network_config select # Possible choices: Network Manager, ifupdown (/etc/network/interfaces), No network configuration ### Description: Waiting time (in seconds) for link detection: # Please enter the maximum time you would like to wait for network link # detection. # d-i netcfg/link_wait_timeout string 3 ### Description: Wireless network: # Select the wireless network to use during the installation process. # d-i netcfg/wireless_show_essids select # Possible choices: ${essid_list} Enter ESSID manually ### Description: DHCP hostname: # You may need to supply a DHCP host name. If you are using # a cable modem, you might need to specify an account number here. # . # Most other users can just leave this blank. # d-i netcfg/dhcp_hostname string ### Description: Network configuration method: # From here you can choose to retry DHCP network autoconfiguration # (which may succeed if your DHCP server takes a long time to respond) # or to configure the network manually. Some DHCP servers require # a DHCP hostname to be sent by the client, so you can also choose # to retry DHCP network autoconfiguration with a hostname that you # provide. # d-i netcfg/dhcp_options select Configure network manually # Possible choices: Retry network autoconfiguration, Retry network autoconfiguration with a DHCP hostname, Configure network manually, ${wifireconf}, Do not configure the network at this time ### Description: Continue without a default route? # The network autoconfiguration was successful. However, no default route # was set: the system does not know how to communicate with hosts on the # Internet. This will make it impossible to continue with the installation # unless you have the first image from a set of installation media, a 'Netinst' # image, or packages available on the local network. # . # If you are unsure, you should not continue without a default route: # contact your local network administrator about this problem. # d-i netcfg/no_default_route boolean ### Description: for internal use; can be preseeded # Timeout for trying DHCP # d-i netcfg/dhcp_timeout string 25 ### Description: for internal use; can be preseeded # Timeout for trying DHCPv6 # d-i netcfg/dhcpv6_timeout string 15 ### Description: IP address: # The IP address is unique to your computer and may be: # . # * four numbers separated by periods (IPv4); # * blocks of hexadecimal characters separated by colons (IPv6). # . # You can also optionally append a CIDR netmask (such as "/24"). # . # If you don't know what to use here, consult your network administrator. # d-i netcfg/get_ipaddress string ### Description: Point-to-point address: # The point-to-point address is used to determine the other endpoint of the # point to point network. Consult your network administrator if you do not # know the value. The point-to-point address should be entered as four numbers # separated by periods. # d-i netcfg/get_pointopoint string ### Description: Netmask: # The netmask is used to determine which machines are local to your # network. Consult your network administrator if you do not know the # value. The netmask should be entered as four numbers separated by # periods. # d-i netcfg/get_netmask string ### Description: Gateway: # The gateway is an IP address (four numbers separated by periods) that # indicates the gateway router, also known as the default router. All # traffic that goes outside your LAN (for instance, to the Internet) is # sent through this router. In rare circumstances, you may have no # router; in that case, you can leave this blank. If you don't know # the proper answer to this question, consult your network # administrator. # d-i netcfg/get_gateway string ### Description: Is this information correct? # Currently configured network parameters: # . # interface = ${interface} # ipaddress = ${ipaddress} # netmask = ${netmask} # gateway = ${gateway} # pointopoint = ${pointopoint} # nameservers = ${nameservers} # d-i netcfg/confirm_static boolean true ############################ #### netcfg-static_1.187_amd64.udeb ############################ ### Description: IP address: # The IP address is unique to your computer and may be: # . # * four numbers separated by periods (IPv4); # * blocks of hexadecimal characters separated by colons (IPv6). # . # You can also optionally append a CIDR netmask (such as "/24"). # . # If you don't know what to use here, consult your network administrator. # d-i netcfg/get_ipaddress string ### Description: Point-to-point address: # The point-to-point address is used to determine the other endpoint of the # point to point network. Consult your network administrator if you do not # know the value. The point-to-point address should be entered as four numbers # separated by periods. # d-i netcfg/get_pointopoint string ### Description: Netmask: # The netmask is used to determine which machines are local to your # network. Consult your network administrator if you do not know the # value. The netmask should be entered as four numbers separated by # periods. # d-i netcfg/get_netmask string ### Description: Gateway: # The gateway is an IP address (four numbers separated by periods) that # indicates the gateway router, also known as the default router. All # traffic that goes outside your LAN (for instance, to the Internet) is # sent through this router. In rare circumstances, you may have no # router; in that case, you can leave this blank. If you don't know # the proper answer to this question, consult your network # administrator. # d-i netcfg/get_gateway string ### Description: Is this information correct? # Currently configured network parameters: # . # interface = ${interface} # ipaddress = ${ipaddress} # netmask = ${netmask} # gateway = ${gateway} # pointopoint = ${pointopoint} # nameservers = ${nameservers} # d-i netcfg/confirm_static boolean true ### Description: for internal use; can be preseeded # Set to false to disable netcfg entirely via preseed. # d-i netcfg/enable boolean true ### Description: Auto-configure networking? # Networking can be configured either by entering all the information # manually, or by using DHCP (or a variety of IPv6-specific methods) to # detect network settings automatically. If you choose to use # autoconfiguration and the installer is unable to get a working # configuration from the network, you will be given the opportunity to # configure the network manually. # d-i netcfg/use_autoconfig boolean true ### Description: Domain name: # The domain name is the part of your Internet address to the right of your # host name. It is often something that ends in .com, .net, .edu, or .org. # If you are setting up a home network, you can make something up, but make # sure you use the same domain name on all your computers. # d-i netcfg/get_domain string ### Description: Name server addresses: # The name servers are used to look up host names on the network. # Please enter the IP addresses (not host names) of up to 3 name servers, # separated by spaces. Do not use commas. The first name server in the list # will be the first to be queried. If you don't want to use any name server, # just leave this field blank. # d-i netcfg/get_nameservers string ### Description: Primary network interface: # Your system has multiple network interfaces. Choose the one to use as # the primary network interface during the installation. If possible, the # first connected network interface found has been selected. # d-i netcfg/choose_interface select # Possible choices: ${ifchoices} ### Description: Wireless ESSID for ${iface}: # ${iface} is a wireless network interface. Please enter the name (the ESSID) # of the wireless network you would like ${iface} to use. If you would like # to use any available network, leave this field blank. # d-i netcfg/wireless_essid string ### Description: Wireless ESSID for ${iface}: # Attempting to find an available wireless network failed. # . # ${iface} is a wireless network interface. Please enter the name (the ESSID) # of the wireless network you would like ${iface} to use. To connect to any # available network, leave this field blank. # d-i netcfg/wireless_essid_again string ### Description: Wireless network type for ${iface}: # Choose WEP/Open if the network is open or secured with WEP. # Choose WPA/WPA2 if the network is protected with WPA/WPA2 PSK # (Pre-Shared Key). # d-i netcfg/wireless_security_type select wpa # Possible choices: WEP/Open Network, WPA/WPA2 PSK ### Description: WEP key for wireless device ${iface}: # If applicable, please enter the WEP security key for the wireless # device ${iface}. There are two ways to do this: # . # If your WEP key is in the format 'nnnn-nnnn-nn', 'nn:nn:nn:nn:nn:nn:nn:nn', # or 'nnnnnnnn', where n is a number, just enter it as it is into this field. # . # If your WEP key is in the format of a passphrase, prefix it with 's:' # (without quotes). # . # Of course, if there is no WEP key for your wireless network, leave this # field blank. # d-i netcfg/wireless_wep string ### Description: WPA/WPA2 passphrase for wireless device ${iface}: # Enter the passphrase for WPA/WPA2 PSK authentication. This should be the # passphrase defined for the wireless network you are trying to use. # d-i netcfg/wireless_wpa string ### Description: Hostname: # Please enter the hostname for this system. # . # The hostname is a single word that identifies your system to the network. # If you don't know what your hostname should be, consult your network # administrator. If you are setting up your own home network, you can make # something up here. # d-i netcfg/get_hostname string debian ### Description: for internal use; can be preseeded # Hostname to set for the system; ignores names provided by DHCP or DNS. # d-i netcfg/hostname string ### Description: Type of wireless network: # Wireless networks are either managed or ad-hoc. If you use a real access # point of some sort, your network is Managed. If another computer is your # 'access point', then your network may be Ad-hoc. # d-i netcfg/wireless_adhoc_managed select Infrastructure (Managed) network # Possible choices: Infrastructure (Managed) network, Ad-hoc network (Peer to peer) ### Description: for internal use; can be preseeded # Set to true to force static network configuration # d-i netcfg/disable_autoconfig boolean false ### Description: for internal use; can be preseeded (deprecated) # Set to true to force static network configuration (deprecated) # d-i netcfg/disable_dhcp boolean false ### Description: for internal use; can be preseeded # Specifies what kind of network connection management tool should be # configured post-installation if multiple are available. Automatic # selection is used in this order when not specified: network-manager if # available (on Linux only), ethernet configuration through ifupdown on wired # installation and loopback configuration through ifupdown on wireless # installations. # d-i netcfg/target_network_config select # Possible choices: Network Manager, ifupdown (/etc/network/interfaces), No network configuration ### Description: Waiting time (in seconds) for link detection: # Please enter the maximum time you would like to wait for network link # detection. # d-i netcfg/link_wait_timeout string 3 ### Description: Wireless network: # Select the wireless network to use during the installation process. # d-i netcfg/wireless_show_essids select # Possible choices: ${essid_list} Enter ESSID manually ############################ #### network-console_1.93_amd64.udeb ############################ ### Description: Network console option: # This is the network console for the Debian installer. From here, you # may start the Debian installer, or execute an interactive shell. # . # To return to this menu, you will need to log in again. # d-i network-console/login select Start menu # Possible choices: Start installer, Start installer (expert mode), Start shell ### Description: Remote installation password: # You need to set a password for remote access to the Debian installer. A # malicious or unqualified user with access to the installer can have # disastrous results, so you should take care to choose a password that # is not easy to guess. It should not be a word found in the dictionary, # or a word that could be easily associated with you, like your middle # name. # . # This password is used only by the Debian installer, and will be # discarded once you finish the installation. # d-i network-console/password password ### Description: Re-enter password to verify: # Please enter the same remote installation password again to verify that # you have typed it correctly. # d-i network-console/password-again password ### Description: for internal use; can be preseeded # This variable contains the URL that provides a list of authorized # SSH public keys # d-i network-console/authorized_keys_url string ############################ #### nobootloader_1.67_all.udeb ############################ ############################ #### partman-auto_162_amd64.udeb ############################ ### Description: Partitioning method: # The installer can guide you through partitioning a disk (using different # standard schemes) or, if you prefer, you can do it manually. With guided # partitioning you will still have a chance later to review and customise # the results. # . # If you choose guided partitioning for an entire disk, you will next be # asked which disk should be used. # d-i partman-auto/init_automatically_partition select # Possible choices: ${DESCRIPTIONS} ### Description: for internal use; can be preseeded # Device to partition, in either devfs or non format # d-i partman-auto/disk string ### Description: for internal use; can be preseeded # Method to use for partitioning # d-i partman-auto/method string ### Description: for internal use; can be preseeded # Cap RAM size to specified size in MB, when calculating the swap # partition size. Defaults to 1024, meaning 1GB, and since swap is # maximum 200% of RAM in the default recipes, it results in swap # partitions to be capped at 2GB. To revert to previous behaviour of # uncapped swap size with respect to available ram, preseed this key to # any string, e.g. partman-auto/cap-ram=false # d-i partman-auto/cap-ram string 1024 ### Description: Partitioning method: # If you choose guided partitioning for an entire disk, you will next be # asked which disk should be used. # d-i partman-auto/automatically_partition select # Possible choices: ${DESCRIPTIONS} ### Description: Partitioning scheme: # Selected for partitioning: # . # ${TARGET} # . # The disk can be partitioned using one of several different schemes. # If you are unsure, choose the first one. # d-i partman-auto/choose_recipe select # Possible choices: ${DESCRIPTIONS} ### Description: for internal use; can be preseeded # File to load for expert recipe # d-i partman-auto/expert_recipe_file string ### Description: for internal use; can be preseeded # Expert recipe content # d-i partman-auto/expert_recipe string ### Description: Select disk to partition: # Note that all data on the disk you select will be erased, but not before # you have confirmed that you really want to make the changes. # d-i partman-auto/select_disk select # Possible choices: ${DESCRIPTIONS} ############################ #### partman-auto-crypto_34_all.udeb ############################ ### Description: for internal use; can be preseeded # Set to false if you want to skip disk erase. # d-i partman-auto-crypto/erase_disks boolean true ############################ #### partman-auto-lvm_91_all.udeb ############################ ### Description: Name of the volume group for the new system: # d-i partman-auto-lvm/new_vg_name string ### Description: Name of the volume group for the new system: # The selected volume group name is already in use. Please choose # another name. # d-i partman-auto-lvm/new_vg_name_exists string ### Description: Continue installation without /boot partition? # The recipe you selected does not contain a separate partition for /boot. # This is normally needed to allow you to boot the system when using LVM. # . # You can choose to ignore this warning, but that may result in a failure to # reboot the system after the installation is completed. # d-i partman-auto-lvm/no_boot boolean ### Description: Amount of volume group to use for guided partitioning: # You may use the whole volume group for guided partitioning, or part of it. # If you use only part of it, or if you add more disks later, then you will # be able to grow logical volumes later using the LVM tools, so using a # smaller part of the volume group at installation time may offer more # flexibility. # . # The minimum size of the selected partitioning recipe is ${MINSIZE} (or # ${PERCENT}); please note that the packages you choose to install may # require more space than this. The maximum available size is ${MAXSIZE}. # . # Hint: "max" can be used as a shortcut to specify the maximum size, or # enter a percentage (e.g. "20%") to use that percentage of the maximum size. # d-i partman-auto-lvm/guided_size string some number ############################ #### partman-auto-raid_51_all.udeb ############################ ### Description: for internal use; can be preseeded # RAID recipe for automated install # d-i partman-auto-raid/recipe string ### Description: for internal use only # Initial RAID device used # d-i partman-auto-raid/raidnum string ############################ #### partman-base_226_amd64.udeb ############################ ### Description: ${TYPE} # ${DESCRIPTION} # d-i partman/exception_handler select # Possible choices: ${CHOICES} ### Description: This is an overview of your currently configured partitions and mount points. Select a partition to modify its settings (file system, mount point, etc.), a free space to create partitions, or a device to initialize its partition table. # d-i partman/choose_partition select # Possible choices: ${DESCRIPTIONS} ### Description: Continue with the installation? # No partition table changes and no creation of file systems have been planned. # . # If you plan on using already created file systems, be aware that existing # files may prevent the successful installation of the base system. # d-i partman/confirm_nochanges boolean false ### Description: Write the changes to disks? # If you continue, the changes listed below will be written to the disks. # Otherwise, you will be able to make further changes manually. # . # WARNING: This will destroy all data on any partitions you have # removed as well as on the partitions that are going to be formatted. # . # ${ITEMS} # d-i partman/confirm boolean false ### Description: Write the changes to disks? # If you continue, the changes listed below will be written to the disks. # Otherwise, you will be able to make further changes manually. # . # ${ITEMS} # d-i partman/confirm_nooverwrite boolean false ### Description: What to do with this device: # d-i partman/storage_device select # Possible choices: ${DESCRIPTIONS} ### Description: How to use this free space: # d-i partman/free_space select # Possible choices: ${DESCRIPTIONS} ### Description: Partition settings: # You are editing partition #${PARTITION} of ${DEVICE}. ${OTHERINFO} ${DESTROYED} # d-i partman/active_partition select # Possible choices: ${DESCRIPTIONS} ### Description: for internal use; can be preseeded # Shell command or commands to run immediately before partitioning # d-i partman/early_command string ### Description: for internal use; can be preseeded # Default filesystem used for new partitions # d-i partman/default_filesystem string ext4 ### Description: for internal use; can be preseeded # Adjust the policy for starting and ending alignment of new partitions. You # can generally leave this alone unless optimal alignment causes some kind of # problem. # . # Cylinder alignment was required by very old DOS-era systems, and is not # usually needed nowadays. However, a few buggy BIOSes may try to calculate # cylinder/head/sector addresses for partitions and get confused if # partitions aren't cylinder-aligned. # . # Minimal alignment ensures that new partitions are aligned to physical # blocks on the disk, avoiding performance degradation that may occur with # cylinder alignment particularly on modern disks. # . # Optimal alignment ensures that new partitions are aligned to a suitable # multiple of the physical block size, guaranteeing optimal performance. # d-i partman/alignment select optimal # Possible choices: cylinder, minimal, optimal ############################ #### partman-basicfilesystems_164_amd64.udeb ############################ ### Description: Go back to the menu and correct errors? # The test of the file system with type ${TYPE} in partition #${PARTITION} # of ${DEVICE} found uncorrected errors. # . # If you do not go back to the partitioning menu and correct these errors, # the partition will be used as is. # d-i partman-basicfilesystems/check_failed boolean ### Description: Go back to the menu and correct errors? # The test of the swap space in partition #${PARTITION} of ${DEVICE} found # uncorrected errors. # . # If you do not go back to the partitioning menu and correct these errors, # the partition will be used as is. # d-i partman-basicfilesystems/swap_check_failed boolean ### Description: Do you want to return to the partitioning menu? # You have not selected any partitions for use as swap space. Enabling swap # space is recommended so that the system can make better use of the # available physical memory, and so that it behaves better when physical # memory is scarce. You may experience installation problems if you do not # have enough physical memory. # . # If you do not go back to the partitioning menu and assign a swap partition, # the installation will continue without swap space. # d-i partman-basicfilesystems/no_swap boolean true ### Description: Do you want to return to the partitioning menu? # No mount point is assigned for the ${FILESYSTEM} file system in partition # #${PARTITION} of ${DEVICE}. # . # If you do not go back to the partitioning menu and assign a mount point # from there, this partition will not be used at all. # d-i partman-basicfilesystems/no_mount_point boolean ### Description: Mount point for this partition: # d-i partman-basicfilesystems/mountpoint select # Possible choices: / - the root file system, /boot - static files of the boot loader, /home - user home directories, /tmp - temporary files, /usr - static data, /var - variable data, /srv - data for services provided by this system, /opt - add-on application software packages, /usr/local - local hierarchy, Enter manually, Do not mount it ### Description: Mount point for this partition: # d-i partman-basicfilesystems/fat_mountpoint select # Possible choices: /dos, /windows, Enter manually, Do not mount it ### Description: Mount point for this partition: # d-i partman-basicfilesystems/mountpoint_manual string ### Description: Label for the file system in this partition: # d-i partman-basicfilesystems/choose_label string ### Description: Percentage of the file system blocks reserved for the super-user: # d-i partman-basicfilesystems/specify_reserved string ### Description: Typical usage of this partition: # Please specify how the file system is going to be used, so that # optimal file system parameters can be chosen for that use. # . # standard = standard parameters, # news = one inode per 4KB block, # largefile = one inode per megabyte, # largefile4 = one inode per 4 megabytes. # d-i partman-basicfilesystems/specify_usage select # Possible choices: ${CHOICES} ### Description: Mount options: # Mount options can tune the behavior of the file system. # d-i partman-basicfilesystems/mountoptions multiselect # Possible choices: ${descriptions} ### Description: Go back to the menu and correct this problem? # Your boot partition has not been configured with the ext2 # file system. This is needed by your machine in order to boot. Please go # back and use the ext2 file system. # . # If you do not go back to the partitioning menu and correct this error, # the partition will be used as is. This means that you may not be able # to boot from your hard disk. # d-i partman-basicfilesystems/boot_not_ext2 boolean ### Description: Go back to the menu and correct this problem? # Your boot partition is not located on the first partition of your # hard disk. This is needed by your machine in order to boot. Please go # back and use your first partition as a boot partition. # . # If you do not go back to the partitioning menu and correct this error, # the partition will be used as is. This means that you may not be able # to boot from your hard disk. # d-i partman-basicfilesystems/boot_not_first_partition boolean ############################ #### partman-basicmethods_74_all.udeb ############################ ### Description: Go back to the menu? # No file system is specified for partition #${PARTITION} of ${DEVICE}. # . # If you do not go back to the partitioning menu and assign a file system # to this partition, it won't be used at all. # d-i partman-basicmethods/method_only boolean ############################ #### partman-btrfs_59_all.udeb ############################ ############################ #### partman-cros_3_all.udeb ############################ ### Description: Go back to the menu and resume partitioning? # No usable ChromeOS kernel partition is found. At least one such # partition is necessary for your machine to be bootable with ChromeOS' # verified boot methods (with CTRL+D or CTRL+U). These partitions must # reside on the same physical disk as either the root or the boot # partition. Two 512 MB partitions should be fine for most installations. # . # If you cannot boot into the installed system in another way (like # legacy boot with CTRL+L), continuing the installation would result in # an unbootable machine. # d-i partman-cros/no_cros boolean ############################ #### partman-crypto_121_amd64.udeb ############################ ### Description: Encryption method for this partition: # Changing the encryption method will set other encryption-related fields # to their default values for the new encryption method. # d-i partman-crypto/crypto_type select # Possible choices: ${DESCRIPTIONS} ### Description: Encryption for this partition: # d-i partman-crypto/cipher select # Possible choices: ${CHOICES} ### Description: Key size for this partition: # d-i partman-crypto/keysize select # Possible choices: ${DESCRIPTIONS} ### Description: Initialization vector generation algorithm for this partition: # Different algorithms exist to derive the initialization vector # for each sector. This choice influences the encryption security. # Normally, there is no reason to change this from the # recommended default, except for compatibility with older systems. # d-i partman-crypto/ivalgorithm select # Possible choices: ${DESCRIPTIONS} ### Description: Type of encryption key for this partition: # d-i partman-crypto/keytype select # Possible choices: ${DESCRIPTIONS} ### Description: Type of encryption key hash for this partition: # The encryption key is derived from the passphrase by applying a # one-way hash function to it. Normally, there is no reason to change # this from the recommended default and doing so in the wrong way # can reduce the encryption strength. # d-i partman-crypto/keyhash select # Possible choices: ${DESCRIPTIONS} ### Description: Really erase the data on ${DEVICE}? # The data on ${DEVICE} will be overwritten with zeroes. It can no longer be # recovered after this step has completed. This is the last opportunity to # abort the erase. # d-i partman-crypto/plain_warn_erase boolean false ### Description: Really erase the data on ${DEVICE}? # The data on ${DEVICE} will be overwritten with random data. It can no # longer be recovered after this step has completed. This is the last # opportunity to abort the erase. # d-i partman-crypto/crypto_warn_erase boolean false ### Description: Write the changes to disk and configure encrypted volumes? # Before encrypted volumes can be configured, the current # partitioning scheme has to be written to disk. These changes # cannot be undone. # . # After the encrypted volumes have been configured, no additional # changes to the partitions on the disks containing encrypted volumes # are allowed. Please decide if you are satisfied with the current # partitioning scheme for these disks before continuing. # . # ${ITEMS} # d-i partman-crypto/confirm boolean false ### Description: Keep current partition layout and configure encrypted volumes? # After the encrypted volumes have been configured, no additional changes # to the partitions on the disks containing encrypted volumes are # allowed. Please decide if you are satisfied with the current # partitioning scheme for these disks before continuing. # d-i partman-crypto/confirm_nochanges boolean false ### Description: Encryption passphrase: # You need to choose a passphrase to encrypt ${DEVICE}. # . # The overall strength of the encryption depends strongly on this # passphrase, so you should take care to choose a passphrase that is # not easy to guess. It should not be a word or sentence found in # dictionaries, or a phrase that could be easily associated with you. # . # A good passphrase will contain a mixture of letters, numbers and # punctuation. Passphrases are recommended to have a length of 20 or # more characters. # d-i partman-crypto/passphrase password ### Description: Re-enter passphrase to verify: # Please enter the same passphrase again to verify that you have typed it # correctly. # d-i partman-crypto/passphrase-again password ### Description: Use weak passphrase? # You entered a passphrase that consists of less than ${MINIMUM} characters, # which is considered too weak. You should choose a stronger passphrase. # d-i partman-crypto/weak_passphrase boolean false ### Description: The encryption key for ${DEVICE} is now being created. # d-i partman-crypto/entropy entropy ### Description: Are you sure you want to use a random key? # You have chosen a random key type for ${DEVICE} but requested the # partitioner to create a file system on it. # . # Using a random key type means that the partition data is going to # be destroyed upon each reboot. This should only be used for # swap partitions. # d-i partman-crypto/use_random_for_nonswap boolean false ### Description: Proceed to install crypto components despite insufficient memory? # There does not seem to be sufficient memory available to install # additional crypto components. If you choose to go ahead and continue # anyway, the installation process could fail. # d-i partman-crypto/install_udebs_low_mem boolean ### Description: Encryption configuration actions # This menu allows you to configure encrypted volumes. # d-i partman-crypto/mainmenu select # Possible choices: Create encrypted volumes, Finish ### Description: Devices to encrypt: # Please select the devices to be encrypted. # . # You can select one or more devices. # d-i partman-crypto/create/partitions multiselect # Possible choices: ${PARTITIONS} ############################ #### partman-efi_101_amd64.udeb ############################ ### Description: Go back to the menu and resume partitioning? # No EFI partition was found. # d-i partman-efi/no_efi boolean ### Description: Force UEFI installation? # This machine's firmware has started the installer in UEFI mode but # it looks like there may be existing operating systems already # installed using "BIOS compatibility mode". If you # continue to install Debian in UEFI mode, it might be difficult to # reboot the machine into any BIOS-mode operating systems later. # . # If you wish to install in UEFI mode and don't care about # keeping the ability to boot one of the existing systems, you have the # option to force that here. If you wish to keep the option to boot an # existing operating system, you should choose NOT to force UEFI # installation here. # d-i partman-efi/non_efi_system boolean ############################ #### partman-ext3_112_all.udeb ############################ ### Description: Go back to the menu and correct this problem? # Your boot partition has not been configured with the ext2 or ext3 # file system. This is needed by your machine in order to boot. Please go # back and use either the ext2 or ext3 file system. # . # If you do not go back to the partitioning menu and correct this error, # the partition will be used as is. This means that you may not be able # to boot from your hard disk. # d-i partman-ext3/boot_not_ext2_or_ext3 boolean ### Description: Go back to the menu and correct this problem? # Your boot partition is not located on the first primary partition of your # hard disk. This is needed by your machine in order to boot. Please go # back and use your first primary partition as a boot partition. # . # If you do not go back to the partitioning menu and correct this error, # the partition will be used as is. This means that you may not be able # to boot from your hard disk. # d-i partman/boot_not_first_partition boolean ### Description: Return to the menu to set the bootable flag? # The boot partition has not been marked as a bootable partition, even # though this is required by your machine in order to boot. You should go # back and set the bootable flag for the boot partition. # . # If you don't correct this, the partition will be used as is and it is # likely that the machine cannot boot from its hard disk. # d-i partman-ext3/boot_not_bootable boolean ### Description: Do you want to return to the partitioning menu? # The partition ${PARTITION} assigned to ${MOUNTPOINT} starts at an offset of # ${OFFSET} bytes from the minimum alignment for this disk, which may lead to # very poor performance. # . # Since you are formatting this partition, you should correct this problem # now by realigning the partition, as it will be difficult to change later. # To do this, go back to the main partitioning menu, delete the partition, # and recreate it in the same position with the same settings. This will # cause the partition to start at a point best suited for this disk. # d-i partman-ext3/bad_alignment boolean ############################ #### partman-iscsi_76_all.udeb ############################ ### Description: iSCSI configuration actions # This menu allows you to configure iSCSI volumes. # d-i partman-iscsi/mainmenu select # Possible choices: Log into iSCSI targets, Finish ### Description: iSCSI target portal address: # Enter an IP address to scan for iSCSI targets. To use a port other than the # default of 3260, use "IP:port" notation, for example "1.2.3.4:3261". # d-i partman-iscsi/login/address string ### Description: iSCSI initiator username for ${PORTAL}: # Some iSCSI targets require the initiator (client) to authenticate using a # username and password. If that is the case for this target, enter the # username here. Otherwise, leave this blank. # d-i partman-iscsi/login/username string ### Description: iSCSI initiator password for ${PORTAL}: # Enter the initiator password needed to authenticate to this iSCSI target. # d-i partman-iscsi/login/password password ### Description: iSCSI target username for ${PORTAL}: # In some environments, the iSCSI target needs to authenticate to the # initiator as well as the other way round. If that is the case here, enter # the incoming username which the target is expected to supply. Otherwise, # leave this blank. # d-i partman-iscsi/login/incoming_username string ### Description: iSCSI target password for ${PORTAL}: # Enter the incoming password which the iSCSI target is expected to supply. # d-i partman-iscsi/login/incoming_password password ### Description: for internal use; can be preseeded # If true, automatically log into all discovered targets. # d-i partman-iscsi/login/all_targets boolean false ### Description: iSCSI targets on ${PORTAL}: # Select the iSCSI targets you wish to use. # d-i partman-iscsi/login/targets multiselect # Possible choices: ${TARGETS} ############################ #### partman-jfs_62_all.udeb ############################ ############################ #### partman-lvm_146_all.udeb ############################ ### Description: Write the changes to disks and configure LVM? # Before the Logical Volume Manager can be configured, the current # partitioning scheme has to be written to disk. These changes cannot # be undone. # . # After the Logical Volume Manager is configured, no additional changes # to the partitioning scheme of disks containing physical volumes are # allowed during the installation. Please decide if you are satisfied # with the current partitioning scheme before continuing. # . # ${ITEMS} # d-i partman-lvm/confirm boolean false ### Description: Keep current partition layout and configure LVM? # After the Logical Volume Manager is configured, no additional changes # to the partitions in the disks containing physical volumes are # allowed. Please decide if you are satisfied with the current # partitioning scheme in these disks before continuing. # d-i partman-lvm/confirm_nochanges boolean false ### Description: LVM configuration action: # Summary of current LVM configuration: # . # Free Physical Volumes: ${FREE_PVS} # Used Physical Volumes: ${USED_PVS} # Volume Groups: ${VGS} # Logical Volumes: ${LVS} # d-i partman-lvm/mainmenu select # Possible choices: ${CHOICES_L10N} ### Description: Devices for the new volume group: # Please select the devices for the new volume group. # . # You can select one or more devices. # d-i partman-lvm/vgcreate_parts multiselect # Possible choices: ${PARTITIONS} ### Description: Volume group name: # Please enter the name you would like to use for the new volume group. # d-i partman-lvm/vgcreate_name string ### Description: Volume group to delete: # Please select the volume group you wish to delete. # d-i partman-lvm/vgdelete_names select # Possible choices: ${GROUPS} ### Description: Really delete the volume group? # Please confirm the ${VG} volume group removal. # d-i partman-lvm/vgdelete_confirm boolean true ### Description: Volume group to extend: # Please select the volume group you wish to extend. # d-i partman-lvm/vgextend_names select # Possible choices: ${GROUPS} ### Description: Devices to add to the volume group: # Please select the devices you wish to add to the volume group. # . # You can select one or more devices. # d-i partman-lvm/vgextend_parts multiselect # Possible choices: ${PARTITIONS} ### Description: Volume group to reduce: # Please select the volume group you wish to reduce. # d-i partman-lvm/vgreduce_names select # Possible choices: ${GROUPS} ### Description: Devices to remove from the volume group: # Please select the devices you wish to remove from the volume group. # . # You can select one or more devices. # d-i partman-lvm/vgreduce_parts multiselect # Possible choices: ${PARTITIONS} ### Description: Logical volume name: # Please enter the name you would like to use for the new logical volume. # d-i partman-lvm/lvcreate_name string ### Description: Volume group: # Please select the volume group where the new logical volume # should be created. # d-i partman-lvm/lvcreate_vgnames select # Possible choices: ${GROUPS} ### Description: Logical volume size: # Please enter the size of the new logical volume. The size may be # entered in the following formats: 10K (Kilobytes), 10M (Megabytes), # 10G (Gigabytes), 10T (Terabytes). The default unit is Megabytes. # d-i partman-lvm/lvcreate_size string ### Description: Logical volume: # Please select the logical volume to delete. # d-i partman-lvm/lvdelete_lvnames select # Possible choices: ${LVS} ### Description: Remove existing logical volume data? # The selected device already contains the following LVM logical volumes, # volume groups and physical volumes which are about to be removed: # . # Logical volume(s) to be removed: ${LVTARGETS} # . # Volume group(s) to be removed: ${VGTARGETS} # . # Physical volume(s) to be removed: ${PVTARGETS} # . # Note that this will also permanently erase any data currently on the # logical volumes. # d-i partman-lvm/device_remove_lvm boolean false ############################ #### partman-md_106_all.udeb ############################ ### Description: Software RAID configuration actions # This is the software RAID (or MD, "multiple device") configuration menu. # . # Please select one of the proposed actions to configure software RAID. # d-i partman-md/mainmenu select # Possible choices: Create MD device, Delete MD device, Finish ### Description: Software RAID device type: # Please choose the type of the software RAID device to be created. # d-i partman-md/createmain select # Possible choices: RAID0, RAID1, RAID5, RAID6, RAID10 ### Description: Active devices for the RAID0 array: # You have chosen to create a RAID0 array. Please choose the active devices # in this array. # d-i partman-md/raid0devs multiselect # Possible choices: ${PARTITIONS} ### Description: Number of active devices for the RAID${LEVEL} array: # The RAID${LEVEL} array will consist of both active and spare devices. The # active devices are those used, while the spare devices will only be used if # one or more of the active devices fail. A minimum of ${MINIMUM} active # devices is required. # . # NOTE: this setting cannot be changed later. # d-i partman-md/raiddevcount string ### Description: Active devices for the RAID${LEVEL} array: # You have chosen to create a RAID${LEVEL} array with ${COUNT} active devices. # . # Please choose which partitions are active devices. # You must select exactly ${COUNT} partitions. # d-i partman-md/raiddevs multiselect # Possible choices: ${PARTITIONS} ### Description: Number of spare devices for the RAID${LEVEL} array: # d-i partman-md/raidsparecount string ### Description: Spare devices for the RAID${LEVEL} array: # You have chosen to create a RAID${LEVEL} array with ${COUNT} spare devices. # . # Please choose which partitions will be used as spare devices. # You may choose up to ${COUNT} partitions. If you choose less than ${COUNT} # devices, the remaining partitions will be added to the array as "missing". # You will be able to add them to the array later. # d-i partman-md/raidsparedevs multiselect # Possible choices: ${PARTITIONS} ### Description: Layout of the RAID10 array: # The layout must be n, o, or f (arrangement of the copies) followed # by a number (number of copies of each chunk). The number must be # smaller or equal to the number of active devices. # . # The letter is the arrangement of the copies: # n - near copies: Multiple copies of one data block are at similar # offsets in different devices. # f - far copies: Multiple copies have very different offsets # o - offset copies: Rather than the chunks being duplicated within a # stripe, whole stripes are duplicated but are rotated by one # device so duplicate blocks are on different devices. # . # NOTE: this setting cannot be changed later. # d-i partman-md/raid10layout string n2 ### Description: Software RAID device to be deleted: # Deleting a software RAID device will stop it and clear the superblock of # all its components. # . # Please note this will not immediately allow you to reuse the partitions or # devices in a new software RAID device. The array will however be unusable # after the deletion. # . # If you select a device for deletion, you will get some information about it # and you will be given the option of aborting this operation. # d-i partman-md/deletemenu select # Possible choices: ${DEVICES} ### Description: Really delete this software RAID device? # Please confirm whether you really want to delete the following software # RAID device: # . # Device: ${DEVICE} # Type: ${TYPE} # Component devices: # . # ${DEVICES} # d-i partman-md/deleteverify boolean false ### Description: Write the changes to the storage devices and configure RAID? # Before RAID can be configured, the changes # have to be written to the storage devices. These changes cannot be # undone. # . # When RAID is configured, no additional changes # to the partitions in the disks containing physical volumes are # allowed. Please convince yourself that you are satisfied with the # current partitioning scheme in these disks. # . # ${ITEMS} # d-i partman-md/confirm boolean false ### Description: Keep current partition layout and configure RAID? # When RAID is configured, no additional changes # to the partitions in the disks containing physical volumes are # allowed. Please convince yourself that you are satisfied with the # current partitioning scheme in these disks. # d-i partman-md/confirm_nochanges boolean false ### Description: Remove existing software RAID partitions? # The selected device contains partitions used for software RAID devices. # The following devices and partitions are about to be removed: # . # Software RAID devices about to be removed: ${REMOVED_DEVICES} # . # Partitions used by these RAID devices: ${REMOVED_PARTITIONS} # . # Note that this will also permanently erase any data currently on the # software RAID devices. # d-i partman-md/device_remove_md boolean false ############################ #### partman-nbd_0.72_all.udeb ############################ ### Description: NBD configuration action: # There are currently ${NUMBER} devices connected. # d-i partman-nbd/mainmenu select # Possible choices: ${CHOICES} ### Description: Network Block Device server: # Please enter the host name or the IP address of the system running # nbd-server. # d-i partman-nbd/server string ### Description: Name for NBD export # Please enter the NBD export name needed to access nbd-server. The name # entered here should match an existing export on the server. # d-i partman-nbd/name string ### Description: Network Block Device device node: # Please select the NBD device node that you wish to connect or # disconnect. # d-i partman-nbd/device select # Possible choices: ${CHOICES} ############################ #### partman-partitioning_147_amd64.udeb ############################ ### Description: Write previous changes to disk and continue? # Before you can select a new partition size, any previous changes have to be # written to disk. # . # You cannot undo this operation. # . # Please note that the resize operation may take a long time. # d-i partman-partitioning/confirm_resize boolean ### Description: New partition size: # The minimum size for this partition is ${MINSIZE} (or ${PERCENT}) and its # maximum size is ${MAXSIZE}. # . # Hint: "max" can be used as a shortcut to specify the maximum size, or # enter a percentage (e.g. "20%") to use that percentage of the maximum size. # d-i partman-partitioning/new_size string some number ### Description: New partition size: # The maximum size for this partition is ${MAXSIZE}. # . # Hint: "max" can be used as a shortcut to specify the maximum size, or # enter a percentage (e.g. "20%") to use that percentage of the maximum size. # d-i partman-partitioning/new_partition_size string some number ### Description: Location for the new partition: # Please choose whether you want the new partition to be created at the # beginning or at the end of the available space. # d-i partman-partitioning/new_partition_place select # Possible choices: Beginning, End ### Description: Type for the new partition: # d-i partman-partitioning/new_partition_type select # Possible choices: Primary, Logical ### Description: Flags for the new partition: # d-i partman-partitioning/set_flags multiselect # Possible choices: ${CHOICES} ### Description: Partition name: # d-i partman-partitioning/set_name string ### Description: Continue with partitioning? # This partitioner doesn't have information about the default type of # the partition tables on your architecture. Please send an e-mail # message to debian-boot@lists.debian.org with information. # . # Please note that if the type of the partition table is unsupported by # libparted, then this partitioner will not work properly. # d-i partman-partitioning/unknown_label boolean true ### Description: Continue with partitioning? # This partitioner is based on the library libparted which doesn't have # support for the partition tables used on your architecture. It is # strongly recommended that you exit this partitioner. # . # If you can, please help to add support for your partition table type # to libparted. # d-i partman-partitioning/unsupported_label boolean false ### Description: for internal use; can be preseeded # You may preseed this template to override the partitioner's # platform-specific default choice of disk label. For example, on x86 # architectures it may be useful to set this to "gpt" to cause new partition # tables to be created using GPT. # d-i partman-partitioning/default_label string ### Description: Partition table type: # Select the type of partition table to use. # d-i partman-partitioning/choose_label select # Possible choices: ${CHOICES} ### Description: Create new empty partition table on this device? # You have selected an entire device to partition. If you proceed with # creating a new partition table on the device, then all current partitions # will be removed. # . # Note that you will be able to undo this operation later if you wish. # d-i partman-partitioning/confirm_new_label boolean false ### Description: Write a new empty partition table? # Because of limitations in the current implementation of the Sun # partition tables in libparted, the newly created partition table has # to be written to the disk immediately. # . # You will NOT be able to undo this operation later and all existing # data on the disk will be irreversibly removed. # . # Confirm whether you actually want to create a new partition table and # write it to disk. # d-i partman-partitioning/confirm_write_new_label boolean false ### Description: Are you sure you want a bootable logical partition? # You are trying to set the bootable flag on a logical partition. The # bootable flag is generally only useful on primary partitions, so setting it # on logical partitions is normally discouraged. Some BIOS versions are known # to fail to boot if there is no bootable primary partition. # . # However, if you are sure that your BIOS does not have this problem, or if # you are using a custom boot manager that pays attention to bootable logical # partitions, then setting this flag may make sense. # d-i partman-partitioning/bootable_logical boolean false ############################ #### partman-target_127_all.udeb ############################ ### Description: Do you want to resume partitioning? # The attempt to mount a file system with type ${TYPE} in ${DEVICE} at # ${MOUNTPOINT} failed. # . # You may resume partitioning from the partitioning menu. # d-i partman-target/mount_failed boolean true ### Description: How to use this partition: # d-i partman-target/choose_method select # Possible choices: ${DESCRIPTIONS} ### Description: for internal use; can be preseeded # Normally, filesystems are mounted using a universally unique identifier # (UUID) as a key; this allows them to be mounted properly even if their # device name changes. UUIDs are long and difficult to read, so, if you # prefer, the installer can mount filesystems based on the traditional device # names, or based on a label you assign. However, note that traditional # device names may change based on the order in which the kernel discovers # devices at boot, which may cause the wrong filesystem to be mounted; # similarly, labels are likely to clash if you plug in a new disk or a USB # drive, and if that happens your system's behaviour when started will be # random. # . # If you set "label" here, any filesystems without a label will be mounted # using a UUID instead. # . # Devices with stable names, such as LVM logical volumes, will continue to # use their traditional names rather than UUIDs. # d-i partman/mount_style select uuid # Possible choices: traditional, label, uuid ############################ #### partman-xfs_68_all.udeb ############################ ############################ #### pkgsel_0.79_all.udeb ############################ ### Description: for internal use; can be preseeded # type of upgrade to perform # d-i pkgsel/upgrade select safe-upgrade # Possible choices: none, safe-upgrade, full-upgrade ### Description: for internal use; can be preseeded # whether tasksel should be run or not # d-i pkgsel/run_tasksel boolean true ### Description: for internal use; can be preseeded # Comma/space-separated list of extra packages to install # d-i pkgsel/include string ### Description: Updates management on this system: # Applying updates on a frequent basis is an important part of keeping the # system secure. # . # By default, security updates are not automatically installed, as security # advisories should be reviewed before manual installation of the updates # using standard package management tools. # . # Alternatively the unattended-upgrades package can be installed, which will # install security updates automatically. Note however that automatic # installation of updates may occasionally cause unexpected downtime of # services provided by this machine in the rare cases where the update is # not fully backward-compatible, or where the security advisory requires the # administrator to perform some other manual operation. # d-i pkgsel/update-policy select none # Possible choices: No automatic updates, Install security updates automatically ### Description: for internal use; can be preseeded # If mlocate is installed, update its database after installing packages. # This is time-consuming, so you may wish to set this to false to disable it. # d-i pkgsel/updatedb boolean true ############################ #### ppp-udeb_2.4.9-1+1.1+b1_amd64.udeb ############################ ### Description: Interface name: # Please enter the name of the network interface connected to the PPPoE # modem. # d-i ppp/interface string _ ### Description: ISP account username: # Please enter the username for the PPP connection. # . # This information should have been provided by your Internet Service # Provider. # d-i ppp/username string ### Description: ISP account password: # Please enter the password for the PPP connection. # . # This information should have been provided by your Internet Service # Provider. # d-i ppp/password password ############################ #### file-preseed_1.117_all.udeb ############################ ### Description: for internal use; can be preseeded # Path to debconf preconfiguration file (or files) to load # d-i preseed/file string ### Description: for internal use; can be preseeded # Optional md5sum (or sums) for the preconfiguration files # d-i preseed/file/checksum string ############################ #### network-preseed_1.117_all.udeb ############################ ### Description: Location of initial preconfiguration file: # In order to perform an automated install, you need to supply a # preconfiguration file (which can in turn pull in other files). # To do that, you need to provide a (perhaps partial) URL. # . # This can be as simple as the machine name where your preseed # files reside up to a full URL. Any of these could be made to work: # intra [for example.com, these three are equivalent] # intra.example.com # http://intra.example.com/d-i/./lenny/preseed.cfg # http://192.168.0.1/~phil/test47.txt # floppy://preseed.cfg # file:///hd-media/kiosk/./preseed.cfg # . # For fully automated installs, preseed/url should itself be preseeded # (via kernel command line, DHCP, or syslinux.cfg on customised media). # . # See http://wiki.debian.org/DebianInstaller/Preseed for inspiration. # d-i preseed/url string ### Description: for internal use; can be preseeded # Optional md5sum (or sums) for the preconfiguration files # d-i preseed/url/checksum string ### Description: for internal use; can be preseeded # If true, attempt a fully automatic install # d-i auto-install/enable boolean false ### Description: for internal use; can be preseeded # Path added to local server to give the preseed root # d-i auto-install/defaultroot string d-i/bookworm/./preseed.cfg ############################ #### preseed-common_1.117_all.udeb ############################ ### Description: for internal use; can be preseeded # Shell command or commands to run in the d-i environment during boot # d-i preseed/boot_command string ### Description: for internal use; can be preseeded # Shell command or commands to run in the d-i environment as early as possible # d-i preseed/early_command string ### Description: for internal use; can be preseeded # Shell command or commands to run in the d-i environment as late as possible # d-i preseed/late_command string ### Description: for internal use; can be preseeded # Programs to be obtained & run # d-i preseed/run string ### Description: for internal use; can be preseeded # md5sums of programs to be obtained & run # d-i preseed/run/checksum string ### Description: for internal use; can be preseeded # Additional preseed files to load # d-i preseed/include string ### Description: for internal use; can be preseeded # md5sums of additional preseed files to load # d-i preseed/include/checksum string ### Description: for internal use; can be preseeded # Shell command to run that may output a list of preseed files to load # d-i preseed/include_command string ### Description: for internal use; can be preseeded # If true, preseed questions but don't mark them as seen # d-i preseed/interactive boolean false ############################ #### rescue-check_1.93_all.udeb ############################ ### Description: for internal use; can be preseeded # Enable rescue mode? # d-i rescue/enable boolean false ############################ #### rescue-mode_1.93_all.udeb ############################ ### Description: Device to use as root file system: # Enter a device you wish to use as your root file system. You will be able # to choose among various rescue operations to perform on this file system. # . # If you choose not to use a root file system, you will be given a reduced # choice of operations that can be performed without one. This may be useful # if you need to correct a partitioning problem. # d-i rescue/root select # Possible choices: ${PARTITIONS}, Assemble RAID array, Do not use a root file system ### Description: Rescue operations # d-i rescue/menu select # Possible choices: ${CHOICES} ### Description: Passphrase for ${DEVICE}: # Please enter the passphrase for the encrypted volume ${DEVICE}. # . # If you don't enter anything, the volume will not be available during # rescue operations. # d-i rescue/passphrase password ### Description: Partitions to assemble: # Select the partitions to assemble into a RAID array. If you select # "Automatic", then all devices containing RAID physical volumes will be # scanned and assembled. # . # Note that a RAID partition at the end of a disk may sometimes cause that # disk to be mistakenly detected as containing a RAID physical volume. In # that case, you should select the appropriate partitions individually. # d-i rescue/assemble-raid multiselect # Possible choices: Automatic, ${PARTITIONS} ### Description: Mount separate ${FILESYSTEM} partition? # The installed system appears to use a separate ${FILESYSTEM} partition. # . # It is normally a good idea to mount it as it will allow operations such # as reinstalling the boot loader. However, if the file system on ${FILESYSTEM} is # corrupt then you may want to avoid mounting it. # d-i rescue/separate-fs boolean true ############################ #### rootskel_1.136_amd64.udeb ############################ ### Description: for internal use; can be preseeded # Enable frame buffer console on boot # d-i debian-installer/framebuffer boolean true ### Description: for internal use only # Always halt the machine # d-i debian-installer/exit/always_halt boolean false ### Description: for internal use; can be preseeded # Halt the machine # d-i debian-installer/exit/halt boolean false ### Description: for internal use; can be preseeded # Power off the machine # d-i debian-installer/exit/poweroff boolean false ### Description: for internal use; can be preseeded # Theme to use for the (newt or gtk) frontend # d-i debian-installer/theme string ### Description: for internal use; can be preseeded # d-i debian-installer/allow_unauthenticated boolean false ### Description: for internal use; can be preseeded # d-i debian-installer/allow_unauthenticated_ssl boolean false ############################ #### rootskel-gtk_12.0.2_amd64.udeb ############################ ### Description: for internal use; can be preseeded # Enable directfb hardware acceleration # d-i directfb/hw-accel boolean false ### Description: for internal use; can be preseeded # Set the mouse protocol for directfb # d-i mouse/protocol string ### Description: for internal use; can be preseeded # Set mouse device (serial port) for directfb # d-i mouse/device string ### Description: for internal use; can be preseeded # Set left-handed mouse for directfb # d-i mouse/left boolean false ############################ #### tzsetup-udeb_0.122_all.udeb ############################ ### Description: ${DESCRIPTION} # If the desired time zone is not listed, then please go back to the step # "Choose language" and select a country that uses the desired time zone # (the country where you live or are located). # d-i time/zone select # Possible choices: ${CHOICES} ### Description: location # d-i tzsetup/country/AQ select # Possible choices: McMurdo, Rothera, Palmer, Mawson, Davis, Casey, Vostok, Dumont-d'Urville, Syowa ### Description: state # d-i tzsetup/country/AU select Australia/Canberra # Possible choices: Australian Capital Territory, New South Wales, Victoria, Northern Territory, Queensland, South Australia, Tasmania, Western Australia, Eyre Highway, Yancowinna County, Lord Howe Island ### Description: state # d-i tzsetup/country/BR select America/Sao_Paulo # Possible choices: Acre, Alagoas, Amazonas, Amapá, Bahia, Ceará, Distrito Federal, Espírito Santo, Fernando de Noronha, Goiás, Maranhão, Minas Gerais, Mato Grosso do Sul, Mato Grosso, Pará, Paraíba, Pernambuco, Piauí, Paraná, Rio de Janeiro, Rio Grande do Norte, Rondônia, Roraima, Rio Grande do Sul, Santa Catarina, Sergipe, São Paulo, Tocantins ### Description: zone # d-i tzsetup/country/CA select Canada/Eastern # Possible choices: Newfoundland, Atlantic, Eastern, Central, East Saskatchewan, Saskatchewan, Mountain, Pacific ### Description: city # d-i tzsetup/country/CD select Africa/Kinshasa # Possible choices: Kinshasa, Lubumbashi ### Description: zone # d-i tzsetup/country/CL select America/Santiago # Possible choices: Santiago, Easter Island ### Description: location # d-i tzsetup/country/EC select America/Guayaquil # Possible choices: Guayaquil, Galapagos ### Description: location # d-i tzsetup/country/ES select Europe/Madrid # Possible choices: Madrid, Ceuta, Canary Islands ### Description: location # d-i tzsetup/country/FM select Pacific/Ponape # Possible choices: Yap, Truk, Pohnpei, Kosrae ### Description: location # d-i tzsetup/country/GL select America/Godthab # Possible choices: Godthab, Danmarkshavn, Scoresbysund, Thule ### Description: city # d-i tzsetup/country/ID select Asia/Jakarta # Possible choices: Western (Sumatra\, Jakarta\, Java\, West and Central Kalimantan), Central (Sulawesi\, Bali\, Nusa Tenggara\, East and South Kalimantan), Eastern (Maluku\, Papua) ### Description: zone # d-i tzsetup/country/KI select Pacific/Tarawa # Possible choices: Tarawa (Gilbert Islands), Enderbury (Phoenix Islands), Kiritimati (Line Islands) ### Description: city # d-i tzsetup/country/KZ select Asia/Almaty # Possible choices: Almaty, Qyzylorda, Aqtobe, Atyrau, Oral ### Description: city # d-i tzsetup/country/MN select Asia/Ulaanbaatar # Possible choices: Ulaanbaatar, Hovd, Choibalsan ### Description: zone # d-i tzsetup/country/MX select Mexico/General # Possible choices: North-West, Pacific, Sonora, Central, South-East ### Description: location # d-i tzsetup/country/NZ select Pacific/Auckland # Possible choices: Auckland, Chatham Islands ### Description: location # d-i tzsetup/country/PF select Pacific/Tahiti # Possible choices: Tahiti (Society Islands), Marquesas Islands, Gambier Islands ### Description: location # d-i tzsetup/country/PT select Europe/Lisbon # Possible choices: Lisbon, Madeira Islands, Azores ### Description: zone # d-i tzsetup/country/RU select Europe/Moscow # Possible choices: Moscow-01 - Kaliningrad, Moscow+00 - Moscow, Moscow+01 - Samara, Moscow+02 - Yekaterinburg, Moscow+03 - Omsk, Moscow+04 - Krasnoyarsk, Moscow+05 - Irkutsk, Moscow+06 - Yakutsk, Moscow+07 - Vladivostok, Moscow+08 - Magadan, Moscow+09 - Kamchatka ### Description: location # d-i tzsetup/country/UM select Pacific/Midway # Possible choices: Johnston Atoll, Midway Islands, Wake Island ### Description: zone # d-i tzsetup/country/US select US/Eastern # Possible choices: Eastern, Central, Mountain, Pacific, Alaska, Hawaii, Arizona, East Indiana, Samoa ### Description: zone # d-i tzsetup/country/PG select # Possible choices: Port Moresby, Bougainville ### Description: zone # d-i tzsetup/country/CY select # Possible choices: Asia/Nicosia (most of Cyprus), Asia/Famagusta (Northern Cyprus) ############################ #### usb-discover_1.13_all.udeb ############################ ### Description: for internal use; can be preseeded # Probe for USB devices? # d-i debian-installer/probe/usb boolean true ############################ #### user-setup-udeb_1.95_all.udeb ############################ ### Description: for internal use only # d-i passwd/root-password-crypted password ### Description: for internal use only # d-i passwd/user-password-crypted password ### Description: for internal use only # d-i passwd/user-uid string ### Description: for internal use only # d-i passwd/user-default-groups string audio cdrom dip floppy video plugdev netdev scanner bluetooth debian-tor lpadmin ### Description: Allow login as root? # If you choose not to allow root to log in, then a user account will be # created and given the power to become root using the 'sudo' command. # d-i passwd/root-login boolean true ### Description: Root password: # You need to set a password for 'root', the system administrative # account. A malicious or unqualified user with root access can have # disastrous results, so you should take care to choose a root password # that is not easy to guess. It should not be a word found in dictionaries, # or a word that could be easily associated with you. # . # A good password will contain a mixture of letters, numbers and punctuation # and should be changed at regular intervals. # . # The root user should not have an empty password. If you leave this # empty, the root account will be disabled and the system's initial user # account will be given the power to become root using the "sudo" # command. # . # Note that you will not be able to see the password as you type it. # d-i passwd/root-password password ### Description: Re-enter password to verify: # Please enter the same root password again to verify that you have typed it # correctly. # d-i passwd/root-password-again password ### Description: Create a normal user account now? # It's a bad idea to use the root account for normal day-to-day activities, # such as the reading of electronic mail, because even a small mistake can # result in disaster. You should create a normal user account to use for # those day-to-day tasks. # . # Note that you may create it later (as well as any additional account) by # typing 'adduser ' as root, where is an username, # like 'imurdock' or 'rms'. # d-i passwd/make-user boolean true ### Description: Full name for the new user: # A user account will be created for you to use instead of the root # account for non-administrative activities. # . # Please enter the real name of this user. This information will be used # for instance as default origin for emails sent by this user as well as # any program which displays or uses the user's real name. Your full # name is a reasonable choice. # d-i passwd/user-fullname string ### Description: Username for your account: # Select a username for the new account. Your first name is a reasonable choice. # The username should start with a lower-case letter, which can be # followed by any combination of numbers and more lower-case letters. # d-i passwd/username string ### Description: Choose a password for the new user: # A good password will contain a mixture of letters, numbers and punctuation # and should be changed at regular intervals. # d-i passwd/user-password password ### Description: Re-enter password to verify: # Please enter the same user password again to verify you have typed it # correctly. # d-i passwd/user-password-again password ############################ #### eject-udeb_2.38.1-5+b1_amd64.udeb ############################ ############################ #### abook_0.6.1-2+b1_amd64.deb ############################ ### Description: Do you want to enable abook system wide for mutt? # abook offers the possibility to be used as query backend from within # mutt. If you acknowledge this question the package will create an # /etc/Muttrc.d/abook.rc file that enables querying the abook database and # adding mail addresses to abook with pressing "A" from pager mode. # d-i abook/muttrc.d boolean true ############################ #### adjtimex_1.29-11+b1_amd64.deb ############################ ### Description: Run adjtimexconfig when adjtimex is installed or upgraded? # The adjtimexconfig script will use adjtimex to find values for the kernel # variables "tick" and "frequency" that will make the system clock approximately # agree with the hardware clock (also known as the CMOS clock). It then # saves these values in the configuration file /etc/default/adjtimex so the # settings will be restored on every boot, when /etc/init.d/adjtimex runs. # . # The script takes 70 seconds to run, so running it for every upgrade # may be a waste of time. Alternatively, you can run adjtimexconfig # manually when needed, or determine the kernel variables by using other # methods and set them manually in /etc/default/adjtimex. # d-i adjtimex/compare_rtc boolean false ############################ #### aide-common_0.18.3-1+deb12u2_all.deb ############################ ### Description: Initialize AIDE database? # Before AIDE can be used, you will have to initialize a database. You # can immediately do this here, or run the '/usr/sbin/aideinit' script # from a shell later. # d-i aide/aideinit boolean false ### Description: Overwrite existing /var/lib/aide/aide.db.new? # You have already a newly generated AIDE database in # /var/lib/aide/aide.db.new. If you choose this option, the existing file # will be be overwritten by the new data obtained from the current state # of your file system. # d-i aideinit/overwritenew boolean true ### Description: Copy aide.db.new to aide.db? # It is advisable for you to first look over /var/lib/aide/aide.db.new # file before replacing the existing db. You can have the package # replace the database anyway here. # . # If you do not choose this option, you will need to copy the file # /var/lib/aide/aide.db.new to /var/lib/aide/aide.db before AIDE can use # it. # d-i aideinit/copynew boolean false ############################ #### amanda-common_3.5.1-11+deb12u1_amd64.deb ############################ ############################ #### analog_6.0.17-3_amd64.deb ############################ ### Description: Enable the anlgform web interface to analog? # Analog includes a CGI script called anlgform that provides a web interface # to the software. # . # Enabling it may have security implications and expose # information, such as web site logs, that shouldn't be public. # d-i analog/anlgform boolean false ############################ #### aodh-api_15.0.0-3_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i aodh/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i aodh/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i aodh/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i aodh/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i aodh/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i aodh/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i aodh/api-endpoint-address string ### Description: This service endpoint protocol: # d-i aodh/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i aodh/api-endpoint-region-name string regionOne ############################ #### aodh-common_15.0.0-3_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i aodh/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i aodh/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i aodh/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i aodh/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i aodh/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i aodh/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i aodh/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i aodh/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i aodh/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i aodh/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i aodh/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i aodh/ksat-admin-password password ### Description: Auth server service username: # d-i aodh/ksat-service-username string ### Description: Auth server service project name: # d-i aodh/ksat-service-project-name string service ### Description: Auth server service password: # d-i aodh/ksat-service-password password ############################ #### apparmor_3.0.8-3_amd64.deb ############################ ### Description: Additional home directory locations: # Please enter a space separated list of any additional locations for user # home directories. These locations are in addition to those specified in # /etc/apparmor.d/tunables/home and must end with a '/'. # . # Example: if user's directories are stored in /srv/nfs/home and /mnt/homes, # you should enter "/srv/nfs/home/ /mnt/homes/". # d-i apparmor/homedirs string ############################ #### apt-build_0.12.49_amd64.deb ############################ ### Description: Directory used by apt-build to download and build packages: # d-i apt-build/build_dir string /var/cache/apt-build/build ### Description: Directory used to store packages built by apt-build: # d-i apt-build/repository_dir string /var/cache/apt-build/repository ### Description: Add apt-build repository to sources.list? # In order to install built package via APT, you must add a line like this # to your sources.list: # deb file:${repo} apt-build main # d-i apt-build/add_to_sourceslist boolean true ### Description: Optimization level: # These are equivalent to -O1, -O2 and -O3. Optimization level is time # dependant. The higher optimization level you choose, more time will be # required for compiling, but the faster your programs will be. # Warning: Strong optimization may lead to stability problems. # d-i apt-build/olevel select Medium # Possible choices: Light, Medium, Strong ### Description: Architecture: # If your architecture is not here, choose one and edit your configuration # file (/etc/apt/apt-build.conf) by hand, and please do a wishlist bugreport. # d-i apt-build/arch_intel select native # Possible choices: generic, native, i386, i486, i586, pentium, pentium-mmx, pentiumpro, i686, pentium2, pentium3, pentium3m, pentium-m, pentium4, pentium4m, prescott, nocona, core2, corei7, corei7-avx, core-avx-i, atom ### Description: Architecture: # If your architecture is not here, choose one and edit your configuration # file (/etc/apt/apt-build.conf) by hand, and please do a wishlist bugreport. # d-i apt-build/arch_amd select native # Possible choices: native, k6, k6-2, k6-3, athlon, athlon-tbird, athlon-4, athlon-xp, athlon-mp, k8, opteron, athlon64, athlon-fx, i8-sse3, opteron-sse3, athlon64-sse3, amdfam10, barcelona, bdver1, btver1 ### Description: Architecture: # If your architecture is not here, choose one and edit your configuration # file (/etc/apt/apt-build.conf) by hand, and please do a wishlist bugreport. # d-i apt-build/arch_amd64 select native # Possible choices: native, nocona, core2, corei7, corei7-avx, core-avx-i, atom, k8, opteron, athlon64, athlon-fx, k8-sse3, opteron-sse3, athlon64-sse3, amdfam10, barcelona, bdver1, btver1 ### Description: Architecture: # If your architecture is not here, choose one and edit your configuration # file (/etc/apt/apt-build.conf) by hand, and please do a wishlist bugreport. # d-i apt-build/arch_sparc select native # Possible choices: native, v7, v8, sparclite, sparclet, v9, cypress, supersparc, hypersparc, leon, f930, f934, sparclite86x, tsc701, ultrasparc, ultrasparc3, niagara, niagara2, niagara3, niagara4 ### Description: Architecture: # If your architecture is not here, choose one and edit your configuration # file (/etc/apt/apt-build.conf) by hand, and please do a wishlist bugreport. # d-i apt-build/arch_arm select native # Possible choices: native, armv2, armv2a, armv3, armv3m, armv4, armv4t, armv5, armv5t, armv5te, armv6, armv6j, armv6t2, armv6zk, armv6-m, armv7, armv7-a, armv7-r, armv7-m, iwmmxt, iwmmxt2, ep9312 ### Description: Architecture: # If your architecture is not here, choose one and edit your configuration # file (/etc/apt/apt-build.conf) by hand, and please do a wishlist bugreport. # d-i apt-build/arch_alpha select native # Possible choices: native, ev4, ev5, ev56, pca56, ev6, ev67 ### Description: Options to add to gcc: # d-i apt-build/options string ### Description: Options to add to make: # d-i apt-build/make_options string ### Description: for internal use # d-i apt-build/archtype string ############################ #### apt-cacher_1.7.29_all.deb ############################ ### Description: Daemon mode for apt-cacher: # Please select the method for starting the apt-cacher daemon. # . # Choose "daemon" to run as a stand-alone daemon, "inetd" to run under inetd or # "manual" to use the (deprecated) CGI mode or some other manual configuration. # d-i apt-cacher/mode select daemon # Possible choices: daemon, inetd, manual ############################ #### apt-cacher-ng_3.7.4-1+b2_amd64.deb ############################ ### Description: Automatic remapping of client requests: # Apt-Cacher NG can download packages from repositories other than those # requested by the clients. This allows it to cache content effectively, # and makes it easy for an administrator to switch to another mirror later. # The URL remapping can be set up automatically, using a configuration # based on the current state of /etc/apt/sources.list. # . # Please specify whether the remapping should be configured once now, or # reconfigured on every update of Apt-Cacher NG (modifying the # configuration files each time), or left unconfigured. # . # Selecting "No automated setup" will leave the existing configuration # unchanged. It will need to be updated manually. # d-i apt-cacher-ng/gentargetmode select Set up once # Possible choices: Set up once, Set up now and update later, No automated setup ### Description: Listening address(es) for Apt-Cacher NG: # Please specify the local addresses that Apt-Cacher NG should listen on # (multiple entries must be separated by spaces). # . # Each entry must be an IP address or hostname associated with a local # network interface. Generic protocol-specific addresses are also # supported, such as 0.0.0.0 for listening on all IPv4-enabled interfaces. # . # If this field is left empty, Apt-Cacher NG will listen on all # interfaces, with all supported protocols. # . # The special word "keep" keeps the value from the current (or default) # configuration unchanged. # d-i apt-cacher-ng/bindaddress string keep ### Description: Listening TCP port: # Please specify the TCP port that Apt-Cacher NG should listen on for # incoming HTTP (proxy) requests. The default value is port 3142, but it # can be set to 9999 to emulate apt-proxy. # . # If this field is left empty, the value from the current configuration # remains unchanged. # d-i apt-cacher-ng/port string keep ### Description: Top-level directory for package cache: # The main cache storage directory should be located on a file system without # file name restrictions. # . # If this field is left empty, the value from the current configuration # remains unchanged or is set to the default of /var/cache/apt-cacher-ng. # d-i apt-cacher-ng/cachedir string keep ### Description: Proxy to use for downloads: # Please specify the proxy server to use for downloads. # . # Username and password for the proxy server can be included here following the # user:pass@host:port scheme. However, please check the documentation for limitations. # . # If this field is left empty, Apt-Cacher NG will not use any proxy # server. # . # The special word "keep" keeps the value from the current (or default) # configuration unchanged. # d-i apt-cacher-ng/proxy string keep ### Description: Allow HTTP tunnels through Apt-Cacher NG? # Apt-Cacher NG can be configured to allow users to create HTTP tunnels, # which can be used to access remote servers that might otherwise be # blocked by (for instance) a firewall filtering HTTPS connections. # . # This feature is usually disabled for security reasons; enable it only for # trusted LAN environments. # d-i apt-cacher-ng/tunnelenable boolean false ############################ #### apt-listchanges_3.24_all.deb ############################ ### Description: Method to be used to display changes: # Changes in packages can be displayed in various ways by apt-listchanges: # . # pager : display changes one page at a time; # browser : display HTML-formatted changes using a web browser; # xterm-pager : like pager, but in an xterm in the background; # xterm-browser: like browser, but in an xterm in the background; # gtk : display changes in a GTK window; # text : print changes to the terminal (without pausing); # mail : only send changes via e-mail; # none : do not run automatically from APT. # . # This setting can be overridden at execution time. By default, all the # options except for 'none' will also send copies by mail. # d-i apt-listchanges/frontend select pager # Possible choices: pager, browser, xterm-pager, xterm-browser, gtk, text, mail, none ### Description: E-mail address(es) which will receive changes: # Optionally, apt-listchanges can e-mail a copy of displayed changes to # a specified address. # . # Multiple addresses may be specified, delimited by commas. Leaving this # field empty disables mail notifications. # d-i apt-listchanges/email-address string root ### Description: Format of e-mail messages: # Please choose a format for e-mail copies of the displayed changes - # either plain text or HTML with clickable links. # d-i apt-listchanges/email-format select text # Possible choices: text, html ### Description: Prompt for confirmation after displaying changes? # After displaying the list of changes, apt-listchanges can pause with # a confirmation prompt. This is useful when running from APT, as it # offers an opportunity to abort the upgrade if a change is unwelcome. # . # This can be overridden at execution time, and has no effect if the # configured frontend option is 'mail' or 'none'. # d-i apt-listchanges/confirm boolean false ### Description: Insert headers before changelogs? # apt-listchanges can insert a header before each package's changelog # showing the name of the package, and the names of the binary packages # which are being upgraded (when different from the source package name). # . # Note however that displaying headers might make the output a bit harder # to read as they might contain long lists of names of binary packages. # d-i apt-listchanges/headers boolean false ### Description: Disable retrieving changes over network? # In rare cases when a binary package does not contain a changelog file, # apt-listchanges by default executes the command "apt-get changelog", # which tries to download changelog entries from the network. # . # This option can disable this behavior, which might for example be # useful for systems with limited network connectivity. # d-i apt-listchanges/no-network boolean false ### Description: Show changes in reverse order? # By default apt-listchanges shows changes for each package in the order # of their appearance in the relevant changelog or news files - from the # most recent version of the package to the oldest. # . # Optionally apt-listchanges can display changes in the opposite order, # which some may find more natural: from the oldest changes in the # package to the newest. # d-i apt-listchanges/reverse boolean false ### Description: Should apt-listchanges skip changes that have already been seen? # A record of already displayed changes can be kept in order to avoid # displaying them again. This is useful, for example, when retrying an upgrade. # d-i apt-listchanges/save-seen boolean true ### Description: Changes displayed with APT: # Please choose which type of changes should be displayed with APT. # . # news : important news items only; # changelogs: detailed changelogs only; # both : news and changelogs. # d-i apt-listchanges/which select news # Possible choices: news, changelogs, both ############################ #### apt-listdifferences_1.20230122_all.deb ############################ ### Description: Initialize the apt-listdifferences source packages database now? # The source packages database for apt-listdifferences can be initialized now. # Depending on your Internet connection, this may take a while, but it will also # provide immediate functionality for the tool. # . # If you do not choose this option, apt-listdifferences will instead become functional slowly # over time as more and more reference source packages get added to its database # when they are first seen. # d-i apt-listdifferences/initialize boolean true ### Description: Remove the apt-listdifferences source packages database? # The apt-listdifferences source packages database is currently still present on disk. You can save # a lot of space by removing it now, but if you ever plan to reinstall # apt-listdifferences, the data will need to be downloaded again. # d-i apt-listdifferences/purge boolean false ############################ #### arno-iptables-firewall_2.1.1-8_all.deb ############################ ### Description: External network interfaces: # The external network interfaces connect this machine # to untrusted networks (e.g. the Internet). The firewall will only permit # connections attempts with explicitly allowed source/destination-port # combinations on these interfaces. You have to specify all external # interfaces (e.g. eth0 and/or ppp0). # . # For a ppp-interface that doesn't exist yet you can use the wildcard device # called "ppp+", but you can only use ppp+ if there aren't any other ppp # interfaces! # . # If no interfaces are specified here, no firewall setup will # be performed. # . # Multiple interfaces should be specified space separated. # d-i arno-iptables-firewall/config-ext-if string ppp+ ### Description: Is DHCP used on external interfaces? # This machine might use DHCP to dynamically obtain its IP address from # your Internet service provider (ISP). This will be almost always the case # if you have a non-permanent (e.g. dialup) connection. # . # If DHCP is not explicitly enabled, the firewall will block all DHCP-related # network traffic. # . # Leave this enabled, if you are unsure. # d-i arno-iptables-firewall/dynamic-ip boolean true ### Description: Open external TCP-ports: # The default firewall policy is to deny all incoming traffic on the # external interfaces. If this machine provides services to the outside # world (e.g. the Internet) they have to be explicitly enabled. # . # Please specify the TCP-ports numbers associated with the services that # shall be accessible from the outside world. Some frequently used ports are: 80 # (http), 443 (https) or 22 (ssh). # . # In addition to single port numbers you may also specify port ranges (e.g. # 10000:11000). Multiple entries should be entered space separated. # . # If unsure, leave this empty. # d-i arno-iptables-firewall/services-tcp string ### Description: Open external UDP-ports: # The default firewall policy is to deny all incoming traffic on the # external interfaces. If this machine provides services for the outside # world (e.g. the Internet) they have to be explicitly enabled. # . # Please specify the UDP-ports numbers associated with the services that # shall be accessible from the outside world. # . # In addition to single port numbers you may also specify port ranges (e.g. # 10000:11000). Multiple entries should be entered space separated. # . # If unsure, leave this empty. # d-i arno-iptables-firewall/services-udp string ### Description: Should the firewall be (re)started now? # For security reasons the new firewall setup is not applied # automatically. You might want to perform a manual inspection of the # firewall configuration in /etc/arno-iptables-firewall/firewall.conf, especially # when upgrading to a new version, as configuration variables might have changed. # . # In order to later manually apply the new # firewall settings before the next reboot, invoke 'invoke-rc.d # arno-iptables-firewall start'. # . # If you do not need manual inspection, the firewall-setup can be applied now. # d-i arno-iptables-firewall/restart boolean true ### Description: Do you want to enable NAT? # If the connected internal networks should be able to access the outside # world (e.g. the Internet) through the firewall, masquerading (NAT) has # to be enabled. # . # When in doubt, you can safely leave this disabled. # d-i arno-iptables-firewall/nat boolean false ### Description: Internal network interfaces: # The internal network interfaces connect this machine # to trusted networks (e.g. the office or home LAN). The firewall will permit # all connection attempts on these interfaces. If you specify such interfaces, # you will be able to permit the internal networks to access the Internet through # this host. If there are no such interfaces, leave this empty. # . # Multiple interfaces should be entered space separated. # d-i arno-iptables-firewall/config-int-if string ### Description: Internal subnets: # You have to specify which subnets are connected to the internal network # interfaces. Hosts in the internal networks can connect to all the services on # this machine. # . # Give subnets in CIDR notation (e.g. 192.168.1.0/24). If you have # multiple internal networks, they should be space separated. # d-i arno-iptables-firewall/config-int-net string ### Description: Internal networks with access to external networks: # If you want to restrict the access to the external networks, you can specify # the allowed internal subnets in CIDR notation (e.g. 192.168.1.0/24). It is # also possible to specify single hosts by their IP addresses. If you have # multiple internal networks and/or hosts, they should be given space separated. # . # If you leave this empty, the value is automatically set to equal the internal # network. Therefore the WHOLE internal network will have access to the external # networks, so be careful to only specify networks that should have access to # the outside world. # . # If you are unsure, leave this empty. # d-i arno-iptables-firewall/config-int-nat-net string ### Description: Should the machine be pingable from the outside world? # For increased security the firewall can be setup to ignore ICMP echo # requests (pings). While this is generally a good idea (the host seems to # be down at a first glance), this is sometimes not useful (e.g. failure # diagnostics). # . # If you are not sure, leave this disabled. # d-i arno-iptables-firewall/icmp-echo boolean false ### Description: Do you want to manage the firewall setup with debconf? # A basic firewall setup that is suitable for most purposes can be created by # answering a few questions. This should be the preferred option for all who are # not familiar with firewall-related topics. # . # If you do not want that, the firewall will not work before you have edited # the configuration manually. # d-i arno-iptables-firewall/debconf-wanted boolean true ############################ #### libasedrive-serial_3.7-9_amd64.deb ############################ ### Description: Communication port to use with the smart card reader: # The driver needs to know which serial port the Athena ASEDrive IIIe card # reader is connected to. # d-i libasedrive-serial/port select # Possible choices: ttyS0, ttyS1, ttyS2, ttyS3, none ############################ #### atftpd_0.8.0-3_amd64.deb ############################ ### Description: Server timeout: # How many seconds the main thread waits before exiting. # d-i atftpd/tftpd-timeout string 300 ### Description: Retry timeout: # How many seconds to wait for a reply before retransmitting a packet. # d-i atftpd/retry-timeout string 5 ### Description: Maximum number of threads: # Maximum number of concurrent threads that can be running. # d-i atftpd/maxthread string 100 ### Description: Verbosity level: # Level of logging. 7 logs everything including debug logs. 1 will log only # the system critical logs. 5 (LOG_NOTICE) is the default value. # d-i atftpd/verbosity select 5 (LOG_NOTICE) # Possible choices: 7 (LOG_DEBUG), 6 (LOG_INFO), 5 (LOG_NOTICE), 4 (LOG_WARNING), 1 (LOG_ALERT) ### Description: Enable 'timeout' support? # d-i atftpd/timeout boolean true ### Description: Enable 'tsize' support? # d-i atftpd/tsize boolean true ### Description: Enable 'blksize' support? # d-i atftpd/blksize boolean true ### Description: Enable 'windowsize' support? # d-i atftpd/windowsize boolean true ### Description: Enable multicast support? # d-i atftpd/multicast boolean true ### Description: TTL for multicast packets: # d-i atftpd/ttl string 1 ### Description: Port to listen for tftp request: # d-i atftpd/port string 69 ### Description: Port range for multicast file transfer: # Multicast transfer will use any available port in a given set. For # example, "2000-2003, 3000" allow atftpd to use port 2000 to 2003 and 3000. # d-i atftpd/mcast_port string 1758 ### Description: Address range for multicast transfer: # Multicast transfer will use any available addresses from a given set of # addresses. Syntax is "a.b.c.d-d,a.b.c.d,..." # d-i atftpd/mcast_addr string 239.239.239.0-255 ### Description: Log to file instead of journal/syslog? # d-i atftpd/logtofile boolean false ### Description: Log file: # A file where atftpd will write its logs. This file will be made writable for # the user 'nobody' and group 'nogroup'. # d-i atftpd/logfile string /var/log/atftpd.log ### Description: Base directory: # The directory tree from where atftpd can serve files. That directory must # be world readable. # d-i atftpd/basedir string /srv/tftp ############################ #### auctex_12.2-1_all.deb ############################ ### Description: (La)TeX macros parsing mode: # To improve the performance of AUCTeX, every currently installed TeX macro # package and LaTeX style file will be parsed. # . # This may take a lot of time, so it should probably be done in the # background. You may also choose to have it done in the foreground, or to # skip that step. # . # The cached data gets automatically updated via dpkg triggers, so that # no specific action is required whenever you install new (La)TeX packages or # remove old ones. # . # This update can be run manually at any moment by running # 'update-auctex-elisp'. # d-i auctex/doauto select Background # Possible choices: Background, Foreground, None ############################ #### awffull_3.10.2-8_amd64.deb ############################ ### Description: Directory to put the output in: # d-i awffull/directory string /var/www/awffull ### Description: Webserver's rotated log filename: # d-i awffull/logfile string /var/log/apache2/access.log.1 ############################ #### ax25-apps_0.0.8-rc5+git20190411+0ff1383-5_amd64.deb ############################ ### Description: Make listen setuid root? # The listen program needs to make calls as the root user. One way of doing # this is to make the program setuid root. This is generally a bad idea as # there are better ways, such as using the sudo program, to do this. # However, you have the option of making it setuid root here if you like. # d-i ax25-apps/suid_listen boolean false ############################ #### backup-manager_0.7.14-1.3_all.deb ############################ ### Description: Archives location: # Please enter the name of the directory where backup-manager will # store the generated archives. # . # The size of archives may be rather important so you should store them # on a disk with enough available space. # d-i backup-manager/backup-repository string /var/archives ### Description: Archives storage format: # d-i backup-manager/filetype select tar.gz # Possible choices: tar, tar.gz, tar.bz2, tar.lz, zip, dar ### Description: Follow symlinks? # The tar, tar.gz and tar.bz2 filetypes may dereference the symlinks in # generated archives. # . # Enabling this feature will dump the files pointed by symlinks and # is likely to generate huge archives. # d-i backup-manager/dump_symlinks boolean false ### Description: Directories to skip in archives: # Please enter a space-separated list of directories which should not be # archived. # d-i backup-manager/blacklist string /var/archives ### Description: Archives name format: # Files generated by backup-manager may use different file naming # conventions. # . # The long format is "host-full-path-to-directory.tar.gz" while the short # format only uses the last directory name. For instance, /home/me # would be named me.tar.gz. # d-i backup-manager/name-format select long # Possible choices: long, short ### Description: Age of kept archives (days): # Please choose the number of days backup-manager will keep the files # before purging them. Combining several directories and a large number of # days for keeping them may lead to huge archives. # d-i backup-manager/time-to-live string 5 ### Description: Directories to backup: # Please enter a space-separated list of all the directories you want # to backup. # . # You should rather enter several subdirectories instead of the # parent in order to have more pertinent files in your backup repository. # . # For instance, "/home/user1 /home/user2 /home/user3" is more appropriate # than "/home" alone. # d-i backup-manager/directories string /etc /home ### Description: Enable automatic burning? # Archives may be burnt on a CDR/CDRW/DVD media. # . # Using this feature requires a writable media to be present at the running # time. # d-i backup-manager/burning-enabled boolean false ### Description: Device to use for burning data: # d-i backup-manager/burning-device string /dev/cdrom ### Description: Maximum size of your media (MB): # d-i backup-manager/burning-maxsize string 650 ### Description: Burning method: # When burning data, backup-manager will try to burn the whole archives # repository. If it does not fit in the media, it will try to burn only the # daily generated archives. # . # The CDRW/DVD-RW methods will first blank the media and then burn the data. # . # The CDR/DVD method will only burn the data, assuming that the media is empty # (or that the disc does not need formatting, like DVD+RW). # d-i backup-manager/burning-method select CDRW # Possible choices: CDRW, CDR, DVD, DVD-RW ### Description: Enable backup-manager's uploading system? # Archives may be uploaded to remote hosts using ftp or ssh. # . # Using this feature requires valid ftp or ssh account on remote hosts. # d-i backup-manager/want_to_upload boolean false ### Description: Transfer mode to use: # The "ftp" transfer mode requires a valid FTP account on remote hosts. # . # The "scp" mode requires a valid SSH account on remote hosts. # SSH Key authentication is used to establish the connection. # d-i backup-manager/transfert_mode select scp # Possible choices: scp, ftp ### Description: Remote hosts list: # Please enter a space-separated list of hosts (IP or FQDN) where archives will # be uploaded. # d-i backup-manager/upload-hosts string ### Description: SSH user's login: # For the scp transfer mode to be possible, a SSH account will be used. The SSH login # to use is required as well as the path to the private key. # . # Remote hosts must have the user's public key listed in their authorized_keys files # (see ssh-keygen(1) for details). # d-i backup-manager/upload-user-scp string bmngr ### Description: FTP user's login: # Please enter the FTP user to use for uploading files to remote hosts. # d-i backup-manager/upload-user-ftp string ### Description: SSH private key file: # Despite of the ftp transfer mode, ssh doesn't require a password. The # authentication is based on the SSH key. # . # Don't forget to add the user's public key to the remote host's # authorized_keys file (see ssh-keygen(1) for details about ssh key # authentication). # d-i backup-manager/upload-key string ### Description: FTP user's password: # Enter the password of the FTP user to use for uploading files to remote # hosts. # d-i backup-manager/upload-passwd password ### Description: Remote host's repository: # Please enter where - on the remote hosts - archives should be stored. # . # If backup-manager is installed on those hosts, it is recommended to use a # subdirectory of its archive repository so that even uploaded archives will be purged # when needed. # d-i backup-manager/upload-dir string /var/archives/uploads ### Description: CRON frequency: # Although backup-manager is designed to make daily archives, it can be run # less frequently, like once a week or even once a month. # . # Note that you can also choose not to run backup-manager at all with CRON. # d-i backup-manager/cron_frequency select never # Possible choices: never, daily, weekly, monthly ### Description: Owner user of the repository: # For security reason, the repository where archives will be stored is accessible # by a specific user. # . # The repository and archives inside will be readable and writeable by this user. # d-i backup-manager/repo_user string root ### Description: Owner group of the repository: # For security reason, the repository where archives will be stored is accessible # by a specific group. # . # The repository and archives inside will be readable and writeable by this group. # d-i backup-manager/repo_group string root ### Description: Remove deprecated file /etc/cron.d/backup-manager? # In previous version, backup-manager uses /etc/cron.d directory but this directory is not # handled by anacron. Thus, it is not possible to run backup-manager's job asynchronously, if # cron.d is used. # . # In order to let anacron handle backup-manager's job, the following CRON subdirectories are used: # /etc/cron.daily, /etc/cron.weekly and /etc/cron.monthly, depending on the chosen frequency. # . # As jobs handled by the cron.d subdirectory may be skipped if the system is not running, # it is recommended to use one of those directories instead. # d-i backup-manager/cron_d_remove_deprecated boolean false ### Description: Encrypt archives? # If you don't trust the physical device where you store your data, you may want # to be sure that your archives won't be accessible by a malicious user. # . # Backup Manager can encrypt your archives with GPG, that means that you will # need a GPG identity to use that feature. # d-i backup-manager/enable_encryption boolean false ### Description: GPG recipient: # You have to set the recipient for which the archive is encrypted. A valid # specification is a short or long key id, or a descriptive name, as explained # in the gpg man page. # . # The public key for this identity must be in the key ring of the user running gpg, # which may be root in most of the cases. # d-i backup-manager/encryption_recipient string ############################ #### backuppc_4.4.0-8_amd64.deb ############################ ### Description: Which web server would you like to reconfigure automatically: # BackupPC supports any web server with CGI enabled, but this automatic # configuration process only supports Apache. # d-i backuppc/reconfigure-webserver multiselect apache2 # Possible choices: apache2 ### Description: Do you want to restart the webservers now if needed? # Remember that in order to activate the new configuration # the webservers have to be restarted. # d-i backuppc/restart-webserver boolean true ### Description: Temporary password for internal use # Temporary password. Should not be translated. # d-i backuppc/tmppass password ############################ #### bandwidthd_2.0.1+cvs20090917-14_amd64.deb ############################ ### Description: Interface to listen on: # Bandwidthd needs to know which interface it should listen for traffic on. # Only a single interface can be specified. If you want to listen on all # interfaces you should specify the metainterface "any". # Running "bandwidthd -l" will list available interfaces. # d-i bandwidthd/dev select # Possible choices: ${interfaces} ### Description: Subnets to log details about: # Bandwidthd can create graphs for one or several ip-subnets. Subnets are # specified either in dotted-quad format (192.168.0.0 255.255.0.0) or in # CIDR format (192.168.0.0/16) and separated by a comma. # Example: 192.168.0.0/16, 10.0.0.0 255.0.0.0, 172.16.1.0/24. # If you don't know what to specify then you can use 0.0.0.0/0 but it is # strongly discouraged. # d-i bandwidthd/subnet string ### Description: Output CDF data logs? # Bandwidthd can log captured traffic information to Common Data File (CDF) # logs. These logs are required if you want to keep old information stored # between restarts of the bandwidthd daemon. Also see the recovercdf # configuration option. # d-i bandwidthd/outputcdf boolean true ### Description: Recover old data from logs on restart? # If old data is going to be outputed in the graphs, it needs to be read # when BandwidthD is restarted. Parsing the CDF logs can take quite some # time on a slow machine so you might want to disable it, but then you'll # lose the information in the graphs after a reboot and similar.... Also make # sure the output_cdf config option is enabled. # d-i bandwidthd/recovercdf boolean true ### Description: Graph webpage autorefresh delay (seconds): # With this option you can tweak the delay used in the html as "META # REFRESH" value. The default is 150 seconds (2.5 minutes). To disable # automatic reloads of the webpage enter 0. This way the visitor will have # to manually push refresh in his browser to get updated graphs. # d-i bandwidthd/metarefresh string ### Description: Put interface in PROMISC mode? # If this option is enabled, all interfaces used to capture traffic # information will be put in promiscuous mode. This way traffic thats not # routed via the machine running bandwidthd might be trackable anyway. # Enabling promiscuous mode will probably not be able to capture any more # traffic in a normal switched network. Also rootkit detectors might warn # about bandwidthd being a virus if using promiscuous mode. You should # probably leave this option disabled. # d-i bandwidthd/promisc boolean false ### Description: This sensors identification string: # Each sensor should have an identification string to be able to tell from # where the traffic in the PostgreSQL-database was detected on. This # option is usually set to the fully qualified hostname of the machine # running the bandwidthd sensor. This needs to be a unique string which # no other bandwidthd sensor that reports to the same database uses. # d-i bandwidthd-pgsql/sensorid string ############################ #### bandwidthd-pgsql_2.0.1+cvs20090917-14_amd64.deb ############################ ### Description: Interface to listen on: # Bandwidthd needs to know which interface it should listen for traffic on. # Only a single interface can be specified. If you want to listen on all # interfaces you should specify the metainterface "any". # Running "bandwidthd -l" will list available interfaces. # d-i bandwidthd/dev select # Possible choices: ${interfaces} ### Description: Subnets to log details about: # Bandwidthd can create graphs for one or several ip-subnets. Subnets are # specified either in dotted-quad format (192.168.0.0 255.255.0.0) or in # CIDR format (192.168.0.0/16) and separated by a comma. # Example: 192.168.0.0/16, 10.0.0.0 255.0.0.0, 172.16.1.0/24. # If you don't know what to specify then you can use 0.0.0.0/0 but it is # strongly discouraged. # d-i bandwidthd/subnet string ### Description: Output CDF data logs? # Bandwidthd can log captured traffic information to Common Data File (CDF) # logs. These logs are required if you want to keep old information stored # between restarts of the bandwidthd daemon. Also see the recovercdf # configuration option. # d-i bandwidthd/outputcdf boolean true ### Description: Recover old data from logs on restart? # If old data is going to be outputed in the graphs, it needs to be read # when BandwidthD is restarted. Parsing the CDF logs can take quite some # time on a slow machine so you might want to disable it, but then you'll # lose the information in the graphs after a reboot and similar.... Also make # sure the output_cdf config option is enabled. # d-i bandwidthd/recovercdf boolean true ### Description: Graph webpage autorefresh delay (seconds): # With this option you can tweak the delay used in the html as "META # REFRESH" value. The default is 150 seconds (2.5 minutes). To disable # automatic reloads of the webpage enter 0. This way the visitor will have # to manually push refresh in his browser to get updated graphs. # d-i bandwidthd/metarefresh string ### Description: Put interface in PROMISC mode? # If this option is enabled, all interfaces used to capture traffic # information will be put in promiscuous mode. This way traffic thats not # routed via the machine running bandwidthd might be trackable anyway. # Enabling promiscuous mode will probably not be able to capture any more # traffic in a normal switched network. Also rootkit detectors might warn # about bandwidthd being a virus if using promiscuous mode. You should # probably leave this option disabled. # d-i bandwidthd/promisc boolean false ### Description: This sensors identification string: # Each sensor should have an identification string to be able to tell from # where the traffic in the PostgreSQL-database was detected on. This # option is usually set to the fully qualified hostname of the machine # running the bandwidthd sensor. This needs to be a unique string which # no other bandwidthd sensor that reports to the same database uses. # d-i bandwidthd-pgsql/sensorid string ############################ #### barbican-api_15.0.1-2_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i barbican/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i barbican/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i barbican/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i barbican/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i barbican/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i barbican/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i barbican/api-endpoint-address string ### Description: This service endpoint protocol: # d-i barbican/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i barbican/api-endpoint-region-name string regionOne ############################ #### barbican-common_15.0.1-2_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i barbican/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i barbican/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i barbican/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i barbican/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i barbican/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i barbican/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i barbican/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i barbican/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i barbican/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i barbican/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i barbican/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i barbican/ksat-admin-password password ### Description: Auth server service username: # d-i barbican/ksat-service-username string ### Description: Auth server service project name: # d-i barbican/ksat-service-project-name string service ### Description: Auth server service password: # d-i barbican/ksat-service-password password ############################ #### base-passwd_3.6.1_amd64.deb ############################ ### Description: Do you want to move the user ${name}? # update-passwd has found a difference between your system accounts and the # current Debian defaults. It is advisable to allow update-passwd to # change your system; without those changes some packages might not work # correctly. For more documentation on the Debian account policies, please # see /usr/share/doc/base-passwd/README. # . # The proposed change is: # . # Move user "${name}" (${id}) to before the NIS compat "+" entry # . # If you allow this change, a backup of modified files will be made with # the extension .org, which you can use if necessary to restore the # current settings. If you do not make this change now, you can make it # later with the update-passwd utility. # d-i base-passwd/user-move boolean true ### Description: Do you want to move the group ${name}? # update-passwd has found a difference between your system accounts and the # current Debian defaults. It is advisable to allow update-passwd to # change your system; without those changes some packages might not work # correctly. For more documentation on the Debian account policies, please # see /usr/share/doc/base-passwd/README. # . # The proposed change is: # . # Move group "${name}" (${id}) to before the NIS compat "+" entry # . # If you allow this change, a backup of modified files will be made with # the extension .org, which you can use if necessary to restore the # current settings. If you do not make this change now, you can make it # later with the update-passwd utility. # d-i base-passwd/group-move boolean true ### Description: Do you want to add the user ${name}? # update-passwd has found a difference between your system accounts and the # current Debian defaults. It is advisable to allow update-passwd to # change your system; without those changes some packages might not work # correctly. For more documentation on the Debian account policies, please # see /usr/share/doc/base-passwd/README. # . # The proposed change is: # . # Add user "${name}" (${id}) # . # If you allow this change, a backup of modified files will be made with # the extension .org, which you can use if necessary to restore the # current settings. If you do not make this change now, you can make it # later with the update-passwd utility. # d-i base-passwd/user-add boolean true ### Description: Do you want to add the group ${name}? # update-passwd has found a difference between your system accounts and the # current Debian defaults. It is advisable to allow update-passwd to # change your system; without those changes some packages might not work # correctly. For more documentation on the Debian account policies, please # see /usr/share/doc/base-passwd/README. # . # The proposed change is: # . # Add group "${name}" (${id}) # . # If you allow this change, a backup of modified files will be made with # the extension .org, which you can use if necessary to restore the # current settings. If you do not make this change now, you can make it # later with the update-passwd utility. # d-i base-passwd/group-add boolean true ### Description: Do you want to remove the user ${name}? # update-passwd has found a difference between your system accounts and the # current Debian defaults. It is advisable to allow update-passwd to # change your system; without those changes some packages might not work # correctly. For more documentation on the Debian account policies, please # see /usr/share/doc/base-passwd/README. # . # The proposed change is: # . # Remove user "${name}" (${id}) # . # If you allow this change, a backup of modified files will be made with # the extension .org, which you can use if necessary to restore the # current settings. If you do not make this change now, you can make it # later with the update-passwd utility. # d-i base-passwd/user-remove boolean true ### Description: Do you want to remove the group ${name}? # update-passwd has found a difference between your system accounts and the # current Debian defaults. It is advisable to allow update-passwd to # change your system; without those changes some packages might not work # correctly. For more documentation on the Debian account policies, please # see /usr/share/doc/base-passwd/README. # . # The proposed change is: # . # Remove group "${name}" (${id}) # . # If you allow this change, a backup of modified files will be made with # the extension .org, which you can use if necessary to restore the # current settings. If you do not make this change now, you can make it # later with the update-passwd utility. # d-i base-passwd/group-remove boolean true ### Description: Do you want to change the UID of user ${name}? # update-passwd has found a difference between your system accounts and the # current Debian defaults. It is advisable to allow update-passwd to # change your system; without those changes some packages might not work # correctly. For more documentation on the Debian account policies, please # see /usr/share/doc/base-passwd/README. # . # The proposed change is: # . # Change the UID of user "${name}" from ${old_uid} to ${new_uid} # . # If you allow this change, a backup of modified files will be made with # the extension .org, which you can use if necessary to restore the # current settings. If you do not make this change now, you can make it # later with the update-passwd utility. # d-i base-passwd/user-change-uid boolean true ### Description: Do you want to change the GID of user ${name}? # update-passwd has found a difference between your system accounts and the # current Debian defaults. It is advisable to allow update-passwd to # change your system; without those changes some packages might not work # correctly. For more documentation on the Debian account policies, please # see /usr/share/doc/base-passwd/README. # . # The proposed change is: # . # Change the GID of user "${name}" from ${old_gid} (${old_group}) to # ${new_gid} (${new_group}) # . # If you allow this change, a backup of modified files will be made with # the extension .org, which you can use if necessary to restore the # current settings. If you do not make this change now, you can make it # later with the update-passwd utility. # d-i base-passwd/user-change-gid boolean true ### Description: Do you want to change the GECOS of user ${name}? # update-passwd has found a difference between your system accounts and the # current Debian defaults. It is advisable to allow update-passwd to # change your system; without those changes some packages might not work # correctly. For more documentation on the Debian account policies, please # see /usr/share/doc/base-passwd/README. # . # The proposed change is: # . # Change the GECOS of user "${name}" from "${old_gecos}" to "${new_gecos}" # . # If you allow this change, a backup of modified files will be made with # the extension .org, which you can use if necessary to restore the # current settings. If you do not make this change now, you can make it # later with the update-passwd utility. # d-i base-passwd/user-change-gecos boolean true ### Description: Do you want to change the home directory of user ${name}? # update-passwd has found a difference between your system accounts and the # current Debian defaults. It is advisable to allow update-passwd to # change your system; without those changes some packages might not work # correctly. For more documentation on the Debian account policies, please # see /usr/share/doc/base-passwd/README. # . # The proposed change is: # . # Change the home directory of user "${name}" from ${old_home} to # ${new_home} # . # If you allow this change, a backup of modified files will be made with # the extension .org, which you can use if necessary to restore the # current settings. If you do not make this change now, you can make it # later with the update-passwd utility. # d-i base-passwd/user-change-home boolean true ### Description: Do you want to change the shell of user ${name}? # update-passwd has found a difference between your system accounts and the # current Debian defaults. It is advisable to allow update-passwd to # change your system; without those changes some packages might not work # correctly. For more documentation on the Debian account policies, please # see /usr/share/doc/base-passwd/README. # . # The proposed change is: # . # Change the shell of user "${name}" from ${old_shell} to ${new_shell} # . # If you allow this change, a backup of modified files will be made with # the extension .org, which you can use if necessary to restore the # current settings. If you do not make this change now, you can make it # later with the update-passwd utility. # d-i base-passwd/user-change-shell boolean true ### Description: Do you want to change the GID of group ${name}? # update-passwd has found a difference between your system accounts and the # current Debian defaults. It is advisable to allow update-passwd to # change your system; without those changes some packages might not work # correctly. For more documentation on the Debian account policies, please # see /usr/share/doc/base-passwd/README. # . # The proposed change is: # . # Change the GID of group "${name}" from ${old_gid} to ${new_gid} # . # If you allow this change, a backup of modified files will be made with # the extension .org, which you can use if necessary to restore the # current settings. If you do not make this change now, you can make it # later with the update-passwd utility. # d-i base-passwd/group-change-gid boolean true ############################ #### bastet_0.43-7+b1_amd64.deb ############################ ### Description: Remove old-format Bastet highscores file? # The new version of Bastet cannot read highscores files in the old # format, like the one at /var/games/bastet.scores. # . # You can decide to remove the old scores file now. If you leave it on # the system it will be ignored by Bastet and will no longer be # tracked by the package management system. # d-i bastet/score_file_compatibility boolean false ############################ #### ibulgarian_4.1-7_amd64.deb ############################ ############################ #### wbulgarian_4.1-7_all.deb ############################ ############################ #### bidentd_1.1.4-1.2_amd64.deb ############################ ### Description: Logging level for bidentd: # Bisqwit's IDENT Daemon can emit various amounts of information to the # daemon facility of the system logs. # . # The choices have the following meaning: # "Be very quiet" Log nothing # "Be quiet" Log only errors # "Log all requests" Log all requests (can generate lots of noise) # "Be somewhat verbose" Log a little more than with "log all requests" # "Be quite verbose" Log even more than "be somewhat verbose" # "Be really verbose" Log very much (will generate lots of noise) # "Manual config" Do not touch inetd.conf # . # You should choose "Log all requests" unless you know you need one of the # other choices. The verbose options are mostly useful for debugging. # d-i bidentd/loglevel select Log all requests # Possible choices: Be very quiet, Be quiet, Log all requests, Be somewhat verbose, Be quite verbose, Be really verbose, Manual config ############################ #### bilibop-rules_0.6.3_amd64.deb ############################ ### Description: Do you intend to install bilibop-rules on a Live System ? # Some bilibop-rules settings can be useful on non-volatile Operating Systems, # when running from a removable and writable media (USB sticks, external HDD # or SD cards); but they are currently useless or even harmful for LiveCD or # LiveUSB systems. # . # If you choose this option, no other question will be asked; bilibop udev # rules will be applied but nothing else will be modified on your system. # Note that in that case, this package is overkill and you should probably # replace it by the lighter but as much as efficient bilibop-udev package. # d-i bilibop-rules/on-live-system boolean false ### Description: Do you want to use custom bilibop rules and build them now ? # If tens of removable media are plugged on the computer your system boots # from, bilibop udev rules can significantly increase boot time. This can be # avoided by using custom udev rules, which are specific to the device your # system is installed on. # . # That said, if this device can boot from different hardware port types (as # USB/Firewire, USB/eSATA, USB/MMC/SD, etc.), you should check the resulting # rules by booting your system on the alternative port type, and if necessary # by running 'dpkg-reconfigure bilibop-rules' again with proper options, or # even by editing '/etc/udev/rules.d/66-bilibop.rules'. # d-i bilibop-rules/bilibop_rules_generator/customize boolean false ### Description: What do you want to do with your custom rules ? # The file '/etc/udev/rules.d/66-bilibop.rules' exists. It is specific to the # drive on which your system is installed and overrides the one, more generic, # that is provided by the bilibop-rules package (in '/usr/lib/udev/rules.d'). # . # If the device hosting the running system is able to boot from different # hardware port types (USB/Firewire, USB/eSATA, USB/MMC/SD-card, etc.), you # should boot it from the alternative port type and check if your custom rules # work fine in all cases. In the doubt, you should remove the custom rules # file. # d-i bilibop-rules/bilibop_rules_generator/overwrite select keep # Possible choices: keep existing custom rules, rebuild custom rules, remove custom rules ### Description: Options to pass to the bilibop rules generator: # Possible options you can pass to the bilibop rules generator are the # followings: # . # -a vendor,model # -a manufacturer,product,serial # -e ID_VENDOR,ID_MODEL,ID_SERIAL_SHORT # -e ID_SERIAL # . # The two first ones cannot be mixed; for example, '-a model,serial' is not a # valid option; use '-a model -e ID_SERIAL' instead. In the doubt, you should # probably set it to an empty string (defaults to # '-a manufacturer,product,serial'). # d-i bilibop-rules/bilibop_rules_generator/options string ### Description: Do you want to hide Physical Volumes your system does not need ? # It seems that the drive on which your system is installed contains Logical # Volumes. It is possible to set LVM to activate only the Physical Volumes # that your system needs. This can mainly avoid name conflicts between the # Volumes used by your system and those that could be found on internal or # external drives plugged on the same computer. # . # If you choose to use this feature, this will overwrite '/etc/lvm/lvm.conf', # and you should read 'README.Debian' in the documentation of the package. # Otherwise, you can do it later with # . # dpkg-reconfigure -p low bilibop-rules # d-i bilibop-rules/physical_volumes_filter/system-only boolean false ### Description: for internal use only # d-i bilibop-rules/physical_volumes_filter/filter string ### Description: for internal use only # d-i bilibop-rules/physical_volumes_filter/global_filter string ### Description: for internal use only # d-i bilibop-rules/physical_volumes_filter/obtain_device_list_from_udev string ############################ #### boinc-client_7.20.5+dfsg-1.1_amd64.deb ############################ ### Description: Do you want to remove the BOINC data directory? # The BOINC data directory /var/lib/boinc-client contains the information to # which projects the BOINC core client is attached, the work unit cache and # several other data. If you no longer need this data, this is your chance to # remove them. # . # If no longer have need of the data being stored in the BOINC data directory, # you should choose this option. If you want to hold this data for another # time, or if you would rather handle this process manually, you should refuse # this option. # d-i boinc-client/remove_boinc_dir boolean true ############################ #### bottlerocket_0.05b3-18_amd64.deb ############################ ### Description: Serial device for bottlerocket to access: # BottleRocket requires the use of a serial device to access the X10 # FireCracker interface. # d-i bottlerocket/x10_port string ttyS0 ############################ #### boxbackup-client_0.13~~git20221201.g166b3fa-1_amd64.deb ############################ ### Description: Should the BoxBackup client be configured automatically? # The package configuration scripts can create the configuration files # for the BoxBackup client. # . # You should choose this option if you are not familiar with BoxBackup's # configuration options. # . # Please read the /usr/share/doc/boxbackup-client/README.Debian for details # about the configuration of the BoxBackup client. # d-i boxbackup-client/debconf boolean false ### Description: Run mode for the BoxBackup client: # The BoxBackup client supports two modes of backup: # . # In the 'lazy' mode, the backup daemon will regularly scan the file system # searching for modified files. It will then upload the files older than a # specified age to the backup server. # . # In the 'snapshot' mode the backup will be explicitly run at regular intervals. # A cron file (/etc/cron.d/boxbackup-client) is provided with the # package and should be adapted to suit your needs. # d-i boxbackup-client/backupMode select # Possible choices: lazy, snapshot ### Description: Account number for this node on the backup server: # The administrator of the BoxBackup server should have assigned this client # a hexadecimal account number. # . # If no account number has been assigned yet, leave this field blank and # configure it later by running 'dpkg-reconfigure boxbackup-client' as root. # d-i boxbackup-client/accountNumber string ### Description: Fully qualified domain name of the backup server: # Please enter the fully qualified domain name of the BoxBackup server which # your client will use. # . # The client will connect to the server on TCP port 2201. # d-i boxbackup-client/backupServer string ### Description: List of directories to backup: # Please give a space-separated list of directories to be backed up onto # the remote server. # . # Those directories should not contain mounted file systems at any level # in their subdirectories. # d-i boxbackup-client/backupDirs string ### Description: Interval (in seconds) between directory scans: # BoxBackup regularly scans the selected directories, looking for modified # files. # . # Please choose the scan interval in seconds. # d-i boxbackup-client/UpdateStoreInterval string 3600 ### Description: Minimum time to wait (in seconds) before uploading a file: # A file will be uploaded to the server only after a certain time after its # last modification. # . # Low interval values will trigger frequent uploads to the server and more # revisions being created with older revisions being removed earlier. # d-i boxbackup-client/MinimumFileAge string 21600 ### Description: Maximum time to wait (in seconds) before uploading a file: # Frequently modified files are likely to never get uploaded if they # never reach the minimum wait time. # . # Please enter the maximum time to reach before the upload of a modified # file to the server is enforced. # d-i boxbackup-client/MaxUploadWait string 86400 ### Description: Recipient for alert notifications: # The BoxBackup client sends alert notifications when a problem occurs # during the backup. # . # Please enter either a local user name (for example 'root') or an email # address (for example 'admin@example.org'). # d-i boxbackup-client/notifyMail string root ### Description: Generate the client private key and X.509 certificate request? # The BoxBackup client needs an RSA private key and the corresponding X.509 # certificate to authenticate itself with the server. # . # Both can be generated automatically. You will need to send the # certificate request to the BoxBackup server administrator who will # sign it and send it back to you along with the server's Certification # Authority certificate. # . # These files should be copied into BoxBackup's configuration # directory. The file names to use are given in the # /etc/boxbackup/bbackupd.conf file. # d-i boxbackup-client/generateCertificate boolean true ############################ #### boxbackup-server_0.13~~git20221201.g166b3fa-1_amd64.deb ############################ ### Description: Should BoxBackup be configured automatically? # The package configuration scripts can create the configuration files # for the BoxBackup server. # . # You should choose this option if you are not familiar with BoxBackup's # configuration options. The configuration can be done manually with the # 'raidfile-config' and 'bbstored-config' scripts. # . # The server will not start if it is not configured. In all cases, # reading the /usr/share/doc/boxbackup-server/README.Debian is # recommended. # d-i boxbackup-server/debconf boolean false ### Description: Location of the RAID directories: # Please choose the location for the three RAID file directories. # . # To enable RAID, the directory names should be a space-separated list of # three partitions, each on different physical hard drives (for example: # '/raid/0.0 /raid/0.1 /raid/0.2'). # . # If you don't want to enable RAID, just specify the path to one directory # where the backups will be stored (for example, /usr/local/lib/boxbackup). # . # These directories will be created if they do not exist. # d-i boxbackup-server/raidDirectories string ### Description: Block size for the userland RAID system: # BoxBackup uses userland RAID techniques. # . # Please choose the block size to use for the storage. # For maximum efficiency, you should choose the block size of the underlying # file system (which can be displayed for ext2 filesystems with the 'tune2fs -l' # command). # . # This value should be set even if you don't plan to use RAID. # d-i boxbackup-server/raidBlockSize string 4096 ### Description: Generate a server private key and X.509 certificate request? # The BoxBackup server needs an RSA private key and the corresponding X.509 # certificate to perform client-server authentication and communication # encryption. # . # Both can be generated automatically. You will need to sign the # certificate with your root CA (see the boxbackup-server package) and # put this signed certificate and the root CA certificate in the # configuration folder. # d-i boxbackup-server/generateCertificate boolean true ############################ #### ibrazilian_3.0~beta4-24_all.deb ############################ ############################ #### wbrazilian_3.0~beta4-24_all.deb ############################ ############################ #### buildbot_3.7.0-2_all.deb ############################ ### Description: Upgrade buildbot master instances when installing new versions? # Stop, run ``buildbot upgrade-master'' and restart all buildbot master # instances when installing new versions. # . # Please note that the ``buildbot upgrade-master'' operation is potentially # destructive and it is irreversible. It is not possible to "downgrade" an # upgraded master instance. For these reasons, some users may want to do backups # before doing it manually. # . # However, this operation is mandatory and buildbot will fail to restart # a master instance if it has not been performed. See buildbot(7) for more # details. # d-i buildbot/upgrade-on-install boolean true ############################ #### byobu_5.133-1.1_all.deb ############################ ### Description: Do you want to launch Byobu at shell login for all users? # Byobu can launch automatically at login (e.g. console, ssh), providing # an attachable/detachable window manager on the command line. # . # If you select this option, Byobu will install a symlink in /etc/profile.d. # This setting is system-wide, for all users logging into the system. # Individual users can disable this by touching # ~/.byobu/disable-autolaunch, or configuring with 'byobu-config'. # d-i byobu/launch-by-default boolean false ############################ #### ca-certificates_20230311_all.deb ############################ ### Description: Trust new certificates from certificate authorities? # This package may install new CA (Certificate Authority) certificates when # upgrading. You may want to check such new CA certificates and select only # certificates that you trust. # . # - yes: new CA certificates will be trusted and installed; # - no : new CA certificates will not be installed by default; # - ask: prompt for each new CA certificate. # d-i ca-certificates/trust_new_crts select yes # Possible choices: yes, no, ask ### Description: New certificates to activate: # During upgrades, new certificates will be added. Please choose # those you trust. # d-i ca-certificates/new_crts multiselect # Possible choices: ${new_crts} ### Description: Certificates to activate: # This package installs common CA (Certificate Authority) certificates in # /usr/share/ca-certificates. # . # Please select the certificate authorities you trust so that their # certificates are installed into /etc/ssl/certs. They will be compiled # into a single /etc/ssl/certs/ca-certificates.crt file. # d-i ca-certificates/enable_crts multiselect # Possible choices: ${enable_crts} ############################ #### cacti_1.2.24+ds1-1+deb12u1_all.deb ############################ ### Description: Web server: # Please select the web server for which Cacti should be automatically # configured. # . # Select "None" if you would like to configure the web server manually. # d-i cacti/webserver select apache2 # Possible choices: apache2, lighttpd, None ############################ #### calamaris_2.99.4.7-1_all.deb ############################ ### Description: Type of proxy log files to analyze: # Calamaris is able to process log files from Squid or Squid3. If you choose # 'auto' it will look first for Squid log files and then for Squid3 log files. # . # Choosing 'auto' is recommended when only one proxy is installed. # Otherwise, the appropriate setting can be enforced here. # d-i calamaris/cache_type select auto # Possible choices: auto, squid, squid3 ### Description: Output method for Calamaris daily analysis reports: # The result of the Calamaris analysis can be sent as an email to a # specified address or stored as a web page. # . # Please choose which of these methods you want to use. # d-i calamaris/daily/task select mail # Possible choices: nothing, mail, web, both ### Description: Recipient for daily analysis reports by mail: # Please choose the address that should receive daily Calamaris # analysis reports. # . # This setting is only needed if the reports are to be sent by email. # d-i calamaris/daily/mail string root ### Description: Directory for storing HTML daily analysis reports: # Please choose the directory where daily Calamaris analysis reports # should be stored. # . # This setting is only needed if the reports are to be generated as # HTML. # d-i calamaris/daily/html string /var/www/calamaris/daily/index.html ### Description: Title of the daily analysis reports: # Please choose the text that will be used as a prefix to the title for # the daily Calamaris analysis reports. # d-i calamaris/daily/title string Squid daily ### Description: Output method for Calamaris weekly analysis reports: # The result of the Calamaris analysis can be sent as an email to a # specified address or stored as a web page. # . # Please choose which of these methods you want to use. # d-i calamaris/weekly/task select mail # Possible choices: nothing, mail, web, both ### Description: Recipient for weekly analysis reports by mail: # Please choose the address that should receive weekly Calamaris # analysis reports. # . # This setting is only needed if the reports are to be sent by email. # d-i calamaris/weekly/mail string root ### Description: Directory for storing HTML weekly analysis reports: # Please choose the directory where weekly Calamaris analysis reports # should be stored. # . # This setting is only needed if the reports are to be generated as # HTML. # d-i calamaris/weekly/html string /var/www/calamaris/weekly/index.html ### Description: Title of the weekly analysis reports: # Please choose the text that will be used as a prefix to the title for # the weekly Calamaris analysis reports. # d-i calamaris/weekly/title string Squid weekly ### Description: Output method for Calamaris monthly analysis reports: # The result of the Calamaris analysis can be sent as an email to a # specified address or stored as a web page. # . # Please choose which of these methods you want to use. # d-i calamaris/monthly/task select mail # Possible choices: nothing, mail, web, both ### Description: Recipient for monthly analysis reports by mail: # Please choose the address that should receive monthly Calamaris # analysis reports. # . # This setting is only needed if the reports are to be sent by email. # d-i calamaris/monthly/mail string root ### Description: Directory for storing HTML monthly analysis reports: # Please choose the directory where monthly Calamaris analysis reports # should be stored. # . # This setting is only needed if the reports are to be generated as # HTML. # d-i calamaris/monthly/html string /var/www/calamaris/monthly/index.html ### Description: Title of the monthly analysis reports: # Please choose the text that will be used as a prefix to the title for # the monthly Calamaris analysis reports. # d-i calamaris/monthly/title string Squid monthly ### Description: Names of proxy log files to analyze: # Calamaris is supposed to run before the logrotation of the Squid logfiles. # If you want to let it run right after the logrotation of Squid (e.g. by # adding Calamaris to /etc/logrotate.d/squid), you should change this entry # to access.log.1. # d-i calamaris/cache_file string access.log ############################ #### canna_3.7p3-20_amd64.deb ############################ ### Description: Should the Canna server run automatically? # This package contains the Canna server and server-related # utilities. If you are only interested in these utilities, # you can disable the Canna server now. # d-i canna/run_cannaserver boolean true ### Description: Should the Canna server run in network mode? # By default the Canna server will run without support for network # connections, and will only accept connections on UNIX domain sockets, # from clients running on the same host. # . # If you choose this option, network support will be activated, and the # Canna server will accept connections on TCP sockets from clients that # may be on remote hosts. Some clients (such as egg and yc-el) require # this mode even if they run on the local host. # d-i canna/run_with_inet boolean false ### Description: Manage /etc/hosts.canna automatically? # The /etc/hosts.canna file lists hosts allowed to connect to the # Canna server. # . # You should not accept this option if you prefer managing the # file's contents manually. # d-i canna/manage_allow_hosts_with_debconf boolean true ### Description: Hosts allowed to connect to this Canna server: # Please enter the names of the hosts allowed to connect to this Canna server, # separated by spaces. # . # You can use "unix" to allow access via UNIX domain sockets. # d-i canna/allow_hosts string unix localhost ############################ #### libcanna1g_3.7p3-20_amd64.deb ############################ ### Description: Canna input style: # Please choose the default Canna input style: # verbose: Canna3.5 default style with verbose comments; # 1.1 : old Canna style (ver. 1.1); # 1.2 : old Canna style (ver. 1.2); # jdaemon: jdaemon style; # just : JustSystems ATOK style; # lan5 : LAN5 style; # matsu : Matsu word processor style; # skk : SKK style; # tut : TUT-Code style; # unix : UNIX style; # vje : vje style; # wx2+ : WX2+ style. # d-i canna/default_style select verbose # Possible choices: verbose, 1.1, 1.2, jdaemin, just, lan5, matsu, skk, tut, unix, vje, wx2+ ############################ #### cdebconf_0.270_amd64.deb ############################ ### Description: Interface to use: # Packages that use debconf for configuration share a common look and feel. # You can select the type of user interface they use. # . # ${descriptions} # d-i cdebconf/frontend select # Possible choices: ${echoices} ### Description: None # 'None' will never ask you any question. # d-i cdebconf/frontend/none string ### Description: Text # 'Text' is a traditional plain text interface. # d-i cdebconf/frontend/text string ### Description: Newt # 'Newt' is a full-screen, character based interface. # d-i cdebconf/frontend/newt string ### Description: GTK # 'GTK' is a graphical interface that may be used in any graphical environment. # d-i cdebconf/frontend/gtk string ############################ #### cdebconf-gtk_0.270_amd64.deb ############################ ############################ #### ceilometer-common_19.0.0-3_all.deb ############################ ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i ceilometer/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i ceilometer/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i ceilometer/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i ceilometer/rabbit-password password ############################ #### charliecloud-common_0.31-1_all.deb ############################ ############################ #### checksecurity_2.0.16+nmu3_all.deb ############################ ############################ #### chemical-structures_2.2.dfsg.0-20_all.deb ############################ ### Description: Should apache2 be restarted? # In order to activate the new configuration, apache2 has # to be restarted. You can also restart apache2 by manually executing # 'invoke-rc.d apache2 restart'. # d-i chemical-structures/restart-webserver boolean false ############################ #### cinder-api_21.1.0-3_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i cinder/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i cinder/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i cinder/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i cinder/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i cinder/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i cinder/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i cinder/api-endpoint-address string ### Description: This service endpoint protocol: # d-i cinder/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i cinder/api-endpoint-region-name string regionOne ############################ #### cinder-common_21.1.0-3_all.deb ############################ ### Description: Cinder volume group: # Please specify the name of the LVM volume group on which Cinder # will create partitions. # d-i cinder/volume_group string ### Description: Value for my_ip: # This value will be stored in the my_ip directive of cinder.conf. # d-i cinder/my-ip string ### Description: Value for glance_api_servers: # A list of the URLs of glance API servers available to cinder ([http[s]://][hostname|ip]:port). # d-i cinder/glance-api-servers string http://127.0.0.1:9292 ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i cinder/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i cinder/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i cinder/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i cinder/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i cinder/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i cinder/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i cinder/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i cinder/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i cinder/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i cinder/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i cinder/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i cinder/ksat-admin-password password ### Description: Auth server service username: # d-i cinder/ksat-service-username string ### Description: Auth server service project name: # d-i cinder/ksat-service-project-name string service ### Description: Auth server service password: # d-i cinder/ksat-service-password password ############################ #### ckermit_402~beta08-1_amd64.deb ############################ ### Description: Enable Internet Kermit Service Daemon (IKSD) in inetd.conf? # The Internet Kermit Service Daemon (IKSD) is the C-Kermit program running # as an Internet service, similar to an FTP or Telnet server. It executes # Telnet protocol just like a Telnet server and it transfers files like an # FTP server. But unlike an FTP server, IKSD uses the Kermit file transfer # protocol (which is more powerful and flexible) and allows both FTP-like # client/server connections as well as direct keyboard interaction. Secure # authentication methods and encrypted sessions are available, as well as a # wide range of file transfer and management functions, which can be # scripted to automate arbitrarily complex tasks. # d-i ckermit/iksd boolean false ### Description: Enable anonymous IKSD logins? # IKSD supports anonymous logins (using chroot), similar to anonymous FTP. # d-i ckermit/iksd-anon boolean false ### Description: Directory for anonymous IKSD logins: # Enter directory for anonymous IKSD logins. A chroot() will be performed # into this directory on login. This directory will NOT be created. # . # The default is /srv/ftp (same as proftpd). # d-i ckermit/iksd-anondir string /srv/ftp ############################ #### clamav-base_1.0.3+dfsg-1~deb12u1_all.deb ############################ ############################ #### clamav-daemon_1.0.3+dfsg-1~deb12u1_amd64.deb ############################ ### Description: Handle the configuration file automatically? # Some options must be configured for clamav-daemon. # . # The ClamAV suite won't work if it isn't configured. If you do not # configure it automatically, you'll have to configure # /etc/clamav/clamd.conf manually or run 'dpkg-reconfigure clamav-daemon' # later. In any case, manual changes in /etc/clamav/clamd.conf will # be respected. # d-i clamav-daemon/debconf boolean true ### Description: Socket type: # Please choose the type of socket clamd will be listening on. # . # If you choose TCP, clamd can be accessed remotely. If you choose local # UNIX sockets, clamd can be accessed through a file. Local UNIX sockets # are recommended for security reasons. # d-i clamav-daemon/TcpOrLocal select UNIX # Possible choices: TCP, UNIX ### Description: Local (UNIX) socket clamd will listen on: # d-i clamav-daemon/LocalSocket string /var/run/clamav/clamd.ctl ### Description: Gracefully handle left-over UNIX socket files? # d-i clamav-daemon/FixStaleSocket boolean true ### Description: Group owner of clamd local (UNIX) socket: # d-i clamav-daemon/LocalSocketGroup string clamav ### Description: Creation mode for clamd local (UNIX) socket: # d-i clamav-daemon/LocalSocketMode string 666 ### Description: TCP port clamd will listen on: # d-i clamav-daemon/TCPSocket string 3310 ### Description: IP address clamd will listen on: # Enter "any" to listen on every IP address configured. If you want # to listen on a single address or host name, enter it here. # d-i clamav-daemon/TCPAddr string any ### Description: Do you want to enable mail scanning? # This option enables scanning mail contents for viruses. # You need this option enabled if you want to use clamav-milter, or if # you want to enable phishing checks. # d-i clamav-daemon/ScanMail boolean true ### Description: Do you want to enable archive scanning? # If archive scanning is enabled, the daemon will extract archives such as # bz2, tar.gz, deb and many more, to check their contents for viruses. # . # For more information about what archives are supported, see # /usr/share/doc/clamav-docs/clamdoc.pdf or the manpage clamscan(5). # d-i clamav-daemon/ScanArchive boolean true ### Description: Maximum stream length (unit Mb) allowed: # You can set a limit on the stream length that can be scanned. # d-i clamav-daemon/StreamMaxLength string 25 ### Description: Maximum directory depth that will be allowed: # This value must be set if you want to allow the daemon to follow # directory symlinks. # . # Entering '0' will disable this limit. # d-i clamav-daemon/MaxDirectoryRecursion string 0 ### Description: Do you want the daemon to follow directory symlinks? # d-i clamav-daemon/FollowDirectorySymlinks boolean false ### Description: Do you want the daemon to follow regular file symlinks? # d-i clamav-daemon/FollowFileSymlinks boolean false ### Description: Timeout for stopping the thread-scanner (seconds): # Entering '0' will disable the timeout. # d-i clamav-daemon/ReadTimeout string 180 ### Description: Number of threads for the daemon: # d-i clamav-daemon/MaxThreads string 12 ### Description: Number of pending connections allowed: # d-i clamav-daemon/MaxConnectionQueueLength string 15 ### Description: Do you want to use the system logger? # It is possible to log the daemon activity to the system logger. This can be # done independently of whether you want to log activity to a special file. # d-i clamav-daemon/LogSyslog boolean false ### Description: Log file for clamav-daemon (enter none to disable): # d-i clamav-daemon/LogFile string /var/log/clamav/clamav.log ### Description: Do you want to log time information with each message? # d-i clamav-daemon/LogTime boolean true ### Description: Do you want to enable log rotation? # d-i clamav-daemon/LogRotate boolean true ### Description: Maximum file size to scan: # A value of 0 disables the limit. # d-i clamav-daemon/OnAccessMaxFileSize string 5M ### Description: Do you want to permit the use of the ALLMATCHSCAN command? # If set to no, clamd will reject any ALLMATCHSCAN command as invalid. # d-i clamav-daemon/AllowAllMatchScan boolean true ### Description: Do you want memory or nested map scans to dump the content to disk? # If you turn on this option, more data is written to disk and is available # when the LeaveTemporaryFiles option is enabled. # d-i clamav-daemon/ForceToDisk boolean false ### Description: Do you want to completely turn off authenticode verification? # Certain PE files contain an authenticode signature. By default the signature # chain in the PE file is checked against a database of trusted and # revoked certificates if the file being scanned is marked as a virus. # If any certificate in the chain validates against any trusted root, but # does not match any revoked certificate, the file is marked as whitelisted. # If the file does match a revoked certificate, the file is marked as virus. # d-i clamav-daemon/DisableCertCheck boolean false ### Description: Do you want to enable scanning within SWF files? # If you turn off this option, the original files will still be scanned, but # without decoding and additional processing. # d-i clamav-daemon/ScanSWF boolean true ### Description: Maximum size of a file to check for embedded PE: # Files larger than this value will skip the additional analysis step. # Note: disabling this limit or setting it too high may result in severe damage # to the system. # d-i clamav-daemon/MaxEmbeddedPE string 10M ### Description: Maximum size of a HTML file to normalize: # HTML files larger than this value will not be normalized or scanned. # Note: disabling this limit or setting it too high may result in severe damage # to the system. # d-i clamav-daemon/MaxHTMLNormalize string 10M ### Description: Maximum size of a normalized HTML file to scan: # HTML files larger than this value after normalization will not be scanned. # Note: disabling this limit or setting it too high may result in severe damage # to the system. # d-i clamav-daemon/MaxHTMLNoTags string 2M ### Description: Maximum size of a script file to normalize: # Script content larger than this value will not be normalized or scanned. # Note: disabling this limit or setting it too high may result in severe damage # to the system. # d-i clamav-daemon/MaxScriptNormalize string 5M ### Description: Maximum size of a ZIP file to reanalyze type recognition: # ZIP files larger than this value will skip the step to potentially reanalyze as PE. # Note: disabling this limit or setting it too high may result in severe damage # to the system. # d-i clamav-daemon/MaxZipTypeRcg string 1M ### Description: Delay in seconds between daemon self checks: # During the SelfCheck the daemon checks if it needs to reload the virus # database. It also tries to repair problems caused by bugs in the daemon, # (that is, in some cases it's able to repair broken data structures). # d-i clamav-daemon/SelfCheck string 3600 ### Description: User to run clamav-daemon as: # It is recommended to run the ClamAV programs as a non-privileged user. # This will work with most MTAs with a little tweaking, but if you want to # use clamd for filesystem scans, running as root is probably unavoidable. # Please see README.Debian in the clamav-base package for details. # d-i clamav-daemon/User string clamav ### Description: Groups for clamav-daemon (space-separated): # Please enter any extra groups for clamd. # . # By default, clamd runs as a non-privileged user. If you need clamd to # be able to access files owned by another user (e.g., in combination with # an MTA), then you will need to add clamd to the group for that piece of # software. Please see README.Debian in the clamav-base package for details. # d-i clamav-daemon/AddGroups string ### Description: Do you want to load bytecode from the database? # d-i clamav-daemon/Bytecode boolean true ### Description: Security level to apply to the bytecode: # . # - TrustSigned : trust bytecode loaded from signed virus database files, # but insert runtime safety checks for bytecode loaded # from unsigned sources # - Paranoid : always insert runtime checks # d-i clamav-daemon/BytecodeSecurity select TrustSigned # Possible choices: TrustSigned, Paranoid ### Description: Bytecode execution timeout in milliseconds: # d-i clamav-daemon/BytecodeTimeout string 60000 ############################ #### clamav-freshclam_1.0.3+dfsg-1~deb12u1_amd64.deb ############################ ### Description: Virus database update method: # Please choose the method for virus database updates. # . # daemon: freshclam is running as a daemon all the time. You should choose # this option if you have a permanent network connection; # ifup.d: freshclam will be running as a daemon as long as your Internet # connection is up. Choose this one if you use a dialup Internet # connection and don't want freshclam to initiate new connections; # cron: freshclam is started from cron. Choose this if you want full control # of when the database is updated; # manual: no automatic invocation of freshclam. This is not recommended, # as ClamAV's database is constantly updated. # d-i clamav-freshclam/autoupdate_freshclam select daemon # Possible choices: daemon, ifup.d, cron, manual ### Description: Local database mirror site: # Please select the closest local mirror site. # . # Freshclam updates its database from a world wide network of mirror # sites. Please select the closest mirror. If you leave # the default setting, an attempt will be made to guess a # nearby mirror. # d-i clamav-freshclam/local_mirror select db.local.clamav.net # Possible choices: db.local.clamav.net, db.ac.clamav.net (Ascension Island), db.ad.clamav.net (Andorra), db.ae.clamav.net (United Arab Emirates), db.af.clamav.net (Afghanistan), db.ag.clamav.net (Antigua and Barbuda), db.ai.clamav.net (Anguilla), db.al.clamav.net (Albania), db.am.clamav.net (Armenia), db.an.clamav.net (Netherlands Antilles), db.ao.clamav.net (Angola), db.aq.clamav.net (Antarctica), db.ar.clamav.net (Argentina), db.as.clamav.net (American Samoa), db.at.clamav.net (Austria), db.au.clamav.net (Australia), db.aw.clamav.net (Aruba), db.ax.clamav.net (Aland Islands), db.az.clamav.net (Azerbaijan), db.ba.clamav.net (Bosnia and Herzegovina), db.bb.clamav.net (Barbados), db.bd.clamav.net (Bangladesh), db.be.clamav.net (Belgium), db.bf.clamav.net (Burkina Faso), db.bg.clamav.net (Bulgaria), db.bh.clamav.net (Bahrain), db.bi.clamav.net (Burundi), db.bj.clamav.net (Benin), db.bm.clamav.net (Bermuda), db.bn.clamav.net (Brunei Darussalam), db.bo.clamav.net (Bolivia), db.br.clamav.net (Brazil), db.bs.clamav.net (Bahamas), db.bt.clamav.net (Bhutan), db.bv.clamav.net (Bouvet Island), db.bw.clamav.net (Botswana), db.by.clamav.net (Belarus), db.bz.clamav.net (Belize), db.ca.clamav.net (Canada), db.cc.clamav.net (Cocos (Keeling) Islands), db.cd.clamav.net (Congo The Democratic Republic of the), db.cf.clamav.net (Central African Republic), db.cg.clamav.net (Congo Republic of), db.ch.clamav.net (Switzerland), db.ci.clamav.net (Cote d'Ivoire), db.ck.clamav.net (Cook Islands), db.cl.clamav.net (Chile), db.cm.clamav.net (Cameroon), db.cn.clamav.net (China), db.co.clamav.net (Colombia), db.cr.clamav.net (Costa Rica), db.cs.clamav.net (Serbia and Montenegro), db.cu.clamav.net (Cuba), db.cv.clamav.net (Cape Verde), db.cx.clamav.net (Christmas Island), db.cy.clamav.net (Cyprus), db.cz.clamav.net (Czech Republic), db.de.clamav.net (Germany), db.dj.clamav.net (Djibouti), db.dk.clamav.net (Denmark), db.dm.clamav.net (Dominica), db.do.clamav.net (Dominican Republic), db.dz.clamav.net (Algeria), db.ec.clamav.net (Ecuador), db.ee.clamav.net (Estonia), db.eg.clamav.net (Egypt), db.eh.clamav.net (Western Sahara), db.er.clamav.net (Eritrea), db.es.clamav.net (Spain), db.et.clamav.net (Ethiopia), db.fi.clamav.net (Finland), db.fj.clamav.net (Fiji), db.fk.clamav.net (Falkland Islands (Malvinas)), db.fm.clamav.net (Micronesia Federal State of), db.fo.clamav.net (Faroe Islands), db.fr.clamav.net (France), db.ga.clamav.net (Gabon), db.gb.clamav.net (United Kingdom), db.gd.clamav.net (Grenada), db.ge.clamav.net (Georgia), db.gf.clamav.net (French Guiana), db.gg.clamav.net (Guernsey), db.gh.clamav.net (Ghana), db.gi.clamav.net (Gibraltar), db.gl.clamav.net (Greenland), db.gm.clamav.net (Gambia), db.gn.clamav.net (Guinea), db.gp.clamav.net (Guadeloupe), db.gq.clamav.net (Equatorial Guinea), db.gr.clamav.net (Greece), db.gs.clamav.net (South Georgia and the South Sandwich Islands), db.gt.clamav.net (Guatemala), db.gu.clamav.net (Guam), db.gw.clamav.net (Guinea-Bissau), db.gy.clamav.net (Guyana), db.hk.clamav.net (Hong Kong), db.hm.clamav.net (Heard and McDonald Islands), db.hn.clamav.net (Honduras), db.hr.clamav.net (Croatia/Hrvatska), db.ht.clamav.net (Haiti), db.hu.clamav.net (Hungary), db.id.clamav.net (Indonesia), db.ie.clamav.net (Ireland), db.il.clamav.net (Israel), db.im.clamav.net (Isle of Man), db.in.clamav.net (India), db.io.clamav.net (British Indian Ocean Territory), db.iq.clamav.net (Iraq), db.ir.clamav.net (Iran Islamic Republic of), db.is.clamav.net (Iceland), db.it.clamav.net (Italy), db.je.clamav.net (Jersey), db.jm.clamav.net (Jamaica), db.jo.clamav.net (Jordan), db.jp.clamav.net (Japan), db.ke.clamav.net (Kenya), db.kg.clamav.net (Kyrgyzstan), db.kh.clamav.net (Cambodia), db.ki.clamav.net (Kiribati), db.km.clamav.net (Comoros), db.kn.clamav.net (Saint Kitts and Nevis), db.kp.clamav.net (Korea Democratic People's Republic), db.kr.clamav.net (Korea Republic of), db.kw.clamav.net (Kuwait), db.ky.clamav.net (Cayman Islands), db.kz.clamav.net (Kazakhstan), db.la.clamav.net (Lao People's Democratic Republic), db.lb.clamav.net (Lebanon), db.lc.clamav.net (Saint Lucia), db.li.clamav.net (Liechtenstein), db.lk.clamav.net (Sri Lanka), db.lr.clamav.net (Liberia), db.ls.clamav.net (Lesotho), db.lt.clamav.net (Lithuania), db.lu.clamav.net (Luxembourg), db.lv.clamav.net (Latvia), db.ly.clamav.net (Libyan Arab Jamahiriya), db.ma.clamav.net (Morocco), db.mc.clamav.net (Monaco), db.md.clamav.net (Moldova Republic of), db.mg.clamav.net (Madagascar), db.mh.clamav.net (Marshall Islands), db.mk.clamav.net (Macedonia The Former Yugoslav Republic of), db.ml.clamav.net (Mali), db.mm.clamav.net (Myanmar), db.mn.clamav.net (Mongolia), db.mo.clamav.net (Macau), db.mp.clamav.net (Northern Mariana Islands), db.mq.clamav.net (Martinique), db.mr.clamav.net (Mauritania), db.ms.clamav.net (Montserrat), db.mt.clamav.net (Malta), db.mu.clamav.net (Mauritius), db.mv.clamav.net (Maldives), db.mw.clamav.net (Malawi), db.mx.clamav.net (Mexico), db.my.clamav.net (Malaysia), db.mz.clamav.net (Mozambique), db.na.clamav.net (Namibia), db.nc.clamav.net (New Caledonia), db.ne.clamav.net (Niger), db.nf.clamav.net (Norfolk Island), db.ng.clamav.net (Nigeria), db.ni.clamav.net (Nicaragua), db.nl.clamav.net (Netherlands), db.no.clamav.net (Norway), db.np.clamav.net (Nepal), db.nr.clamav.net (Nauru), db.nu.clamav.net (Niue), db.nz.clamav.net (New Zealand), db.om.clamav.net (Oman), db.pa.clamav.net (Panama), db.pe.clamav.net (Peru), db.pf.clamav.net (French Polynesia), db.pg.clamav.net (Papua New Guinea), db.ph.clamav.net (Philippines), db.pk.clamav.net (Pakistan), db.pl.clamav.net (Poland), db.pm.clamav.net (Saint Pierre and Miquelon), db.pn.clamav.net (Pitcairn Island), db.pr.clamav.net (Puerto Rico), db.ps.clamav.net (Palestinian Territory Occupied), db.pt.clamav.net (Portugal), db.pw.clamav.net (Palau), db.py.clamav.net (Paraguay), db.qa.clamav.net (Qatar), db.re.clamav.net (Reunion Island), db.ro.clamav.net (Romania), db.ru.clamav.net (Russian Federation), db.rw.clamav.net (Rwanda), db.sa.clamav.net (Saudi Arabia), db.sb.clamav.net (Solomon Islands), db.sc.clamav.net (Seychelles), db.sd.clamav.net (Sudan), db.se.clamav.net (Sweden), db.sg.clamav.net (Singapore), db.sh.clamav.net (Saint Helena), db.si.clamav.net (Slovenia), db.sj.clamav.net (Svalbard and Jan Mayen Islands), db.sk.clamav.net (Slovak Republic), db.sl.clamav.net (Sierra Leone), db.sm.clamav.net (San Marino), db.sn.clamav.net (Senegal), db.so.clamav.net (Somalia), db.sr.clamav.net (Suriname), db.st.clamav.net (Sao Tome and Principe), db.sv.clamav.net (El Salvador), db.sy.clamav.net (Syrian Arab Republic), db.sz.clamav.net (Swaziland), db.tc.clamav.net (Turks and Caicos Islands), db.td.clamav.net (Chad), db.tf.clamav.net (French Southern Territories), db.tg.clamav.net (Togo), db.th.clamav.net (Thailand), db.tj.clamav.net (Tajikistan), db.tk.clamav.net (Tokelau), db.tl.clamav.net (Timor-Leste), db.tm.clamav.net (Turkmenistan), db.tn.clamav.net (Tunisia), db.to.clamav.net (Tonga), db.tp.clamav.net (East Timor), db.tr.clamav.net (Turkey), db.tt.clamav.net (Trinidad and Tobago), db.tv.clamav.net (Tuvalu), db.tw.clamav.net (Taiwan), db.tz.clamav.net (Tanzania), db.ua.clamav.net (Ukraine), db.ug.clamav.net (Uganda), db.uk.clamav.net (United Kingdom), db.um.clamav.net (United States Minor Outlying Islands), db.us.clamav.net (United States), db.uy.clamav.net (Uruguay), db.uz.clamav.net (Uzbekistan), db.va.clamav.net (Holy See (Vatican City State)), db.vc.clamav.net (Saint Vincent and the Grenadines), db.ve.clamav.net (Venezuela), db.vg.clamav.net (Virgin Islands British), db.vi.clamav.net (Virgin Islands U.S.), db.vn.clamav.net (Vietnam), db.vu.clamav.net (Vanuatu), db.wf.clamav.net (Wallis and Futuna Islands), db.ws.clamav.net (Western Samoa), db.ye.clamav.net (Yemen), db.yt.clamav.net (Mayotte), db.yu.clamav.net (Yugoslavia), db.za.clamav.net (South Africa), db.zm.clamav.net (Zambia), db.zw.clamav.net (Zimbabwe), db.ipv6.clamav.net (IPv6 mirror) ### Description: HTTP proxy information (leave blank for none): # If you need to use an HTTP proxy to access the outside world, enter the # proxy information here. Otherwise, leave this blank. # . # Please use URL syntax ("http://host[:port]") here. # d-i clamav-freshclam/http_proxy string ### Description: Proxy user information (leave blank for none): # If you need to supply a username and password to the proxy, enter it here. # Otherwise, leave this blank. # . # When entering user information, use the standard form of # "user:pass". # d-i clamav-freshclam/proxy_user string ### Description: Number of freshclam updates per day: # d-i clamav-freshclam/update_interval string 24 ### Description: Network interface connected to the Internet: # Please enter the name of the network interface connected to the Internet. # Example: eth0. # . # If the daemon runs when the network is down, the log file will be filled # with entries like 'ERROR: Connection with database.clamav.net failed.', # making it easy to miss when freshclam really can't update the database. # . # You can leave this field blank and the daemon will be started from # the initialization scripts instead. You should then make sure the computer is # permanently connected to the Internet to avoid filling the log files. # . # If the computer has multiple network interfaces connecting to the Internet use # a space-separated list of device names. # d-i clamav-freshclam/internet_interface string ### Description: Should clamd be notified after updates? # Please confirm whether clamd should be notified to reload the database after # successful updates. # . # If you do not choose this option, clamd's database reloads will be notably # delayed (it performs this check every 6 hours by default), posing the risk # that a new virus may slip through even if the database is up to date. # Do not use this if you do not use clamd, as it will produce errors. # d-i clamav-freshclam/NotifyClamd boolean true ### Description: Do you want to download the bytecode database? # d-i clamav-freshclam/Bytecode boolean true ### Description: Private mirror for freshclam: # This option allows you to easily point freshclam to private mirrors. # If PrivateMirror is set, freshclam does not attempt to use DNS # to determine whether its databases are out-of-date, instead it will # use the If-Modified-Since request or directly check the headers of the # remote database files. For each database, freshclam first attempts # to download the CLD file. If that fails, it tries to download the # CVD file. This option overrides DatabaseMirror, DNSDatabaseInfo # and ScriptedUpdates. It can be used multiple times to provide # fall-back mirrors. # d-i clamav-freshclam/PrivateMirror string ### Description: Do you want to enable log rotation? # d-i clamav-freshclam/LogRotate boolean true ############################ #### clamav-milter_1.0.3+dfsg-1~deb12u1_amd64.deb ############################ ### Description: Handle the configuration file automatically? # Some options must be configured for clamav-milter. # . # It won't work if it isn't configured. If you do not # configure it automatically, you'll have to configure # /etc/clamav/clamav-milter.conf manually or run "dpkg-reconfigure clamav-milter" # later. In any case, manual changes in /etc/clamav/clamav-milter.conf will # be respected. # d-i clamav-milter/debconf boolean true ### Description: Communication interface with Sendmail: # Please choose the method that should be used by clamav-milter to # communicate with Sendmail. The following formats can be used: # - Unix domain socket: [[unix|local]:]/path/to/file # - IPv4 socket : inet:port@[hostname|ip-address] # - IPv6 socket : inet6:port@[hostname|ip-address] # d-i clamav-milter/MilterSocket string /var/run/clamav/clamav-milter.ctl ### Description: Remove stale socket after unclean shutdown? # d-i clamav-milter/FixStaleSocket boolean true ### Description: Group owner of clamav-milter local (UNIX) socket: # d-i clamav-milter/MilterSocketGroup string clamav ### Description: Creation mode for clamav-milter local (UNIX) socket: # d-i clamav-milter/MilterSocketMode string 666 ### Description: User to run clamav-milter as: # It is recommended to run the ClamAV programs as a non-privileged user. # This will work with most MTAs with a little tweaking. # . # Please see README.Debian in the clamav-base package for details. # d-i clamav-milter/User string clamav ### Description: Groups for clamav-milter (space-separated): # By default, clamav-milter runs as a non-privileged user. If you need # clamav-milter to be able to access files owned by another user (for # instance when it is used in combination with an MTA), the user # running clamav-milter need to be added to the relevant group(s). # . # Please see README.Debian in the clamav-base package for # details. # d-i clamav-milter/AddGroups string ### Description: Wait timeout for data coming from clamd: # Please enter the delay (in seconds) before clamav-milter times out when it is # waiting for incoming data from clamd. # . # Choosing "0" will disable this timeout. # d-i clamav-milter/ReadTimeout string 120 ### Description: Should clamav-milter stay in foreground (not forking)? # d-i clamav-milter/Foreground boolean false ### Description: Chroot to directory: # Clamav-milter can run in a chroot jail. It will enter it after reading # the configuration file and before dropping root privileges. # . # If this field is left empty, no chrooting will occur. # d-i clamav-milter/Chroot string ### Description: PID file: # Please specify the process identifier file location for clamav-milter's # listening daemon (main thread). # d-i clamav-milter/PidFile string /var/run/clamav/clamav-milter.pid ### Description: Temporary directory path: # Please specify the directory for clamav-milter's files that are temporarily # buffered for scanning. If unset, $TMPDIR and $TEMP will be honored. # d-i clamav-milter/TemporaryDirectory string /tmp ### Description: Clamd socket to connect to for scanning: # Please specify the socket to use to connect to the ClamAV daemon for # scanning purposes. Possible choices are: # - a local unix socket using an absolute path, in "unix:path" format # (for example: unix:/var/run/clamd/clamd.socket); # - a local or remote TCP socket in "tcp:host:port" format (for example: # tcp:192.168.0.1). The "host" value can be either a hostname or an IP # address, and the "port" is only required for IPv6 addresses, # defaulting to 3310 otherwise. # . # You may specify multiple choices, separated by spaces. In such case, the # clamd servers will be selected in a round-robin fashion. # d-i clamav-milter/ClamdSocket string unix:/var/run/clamav/clamd.ctl ### Description: Hosts excluded from scanning: # Please specify, in CIDR notation (host(name)/mask), the hosts for # which no scanning should be performed on incoming mail. Multiple entries # should be separated by spaces. The "local" shortcut can be used to # specify locally-originated (non-SMTP) email. # . # If this field is left empty, all incoming mail will be scanned. # d-i clamav-milter/LocalNet string ### Description: Mail addresses whitelist: # Please specify the path to a whitelist file, listing email addresses # that should cause scanning to be bypassed. # . # Each line in this file should be a POSIX regular expression; lines # starting with "#", ":" or "!" will be ignored as comments. # . # Lines may start with "From:" (with no space after the colon) to make # the whitelisting apply to matching sender addresses; otherwise, or # with a "To:" prefix, it affects recipient addresses. # d-i clamav-milter/Whitelist string ### Description: Action to perform on infected messages: # Please choose the action to perform on "infected" messages: # . # - Accept : accept the message for delivery; # - Reject : immediately refuse delivery (with a 5xx error); # - Defer : return a temporary failure message (4xx); # - Blackhole : accept the message then drop it; # - Quarantine: accept the message then quarantine it. With # Sendmail, the quarantine queue can be examined # with "mailq -qQ". With Postfix, such mails are placed # on hold. # d-i clamav-milter/OnInfected select Quarantine # Possible choices: Accept, Reject, Defer, Blackhole, Quarantine ### Description: Action to perform on error conditions: # Please choose the action to perform on errors such as failure to # allocate data structures, no scanners available, # network timeouts, unknown scanner replies...: # . # - Accept: accept the message for delivery; # - Reject: immediately refuse delivery (with a 5xx error); # - Defer : return a temporary failure message (4xx). # d-i clamav-milter/OnFail select Defer # Possible choices: Accept, Reject, Defer ### Description: Specific rejection reason for infected messages: # Please specify the rejection reason that will be included in reject mails. # . # This option is only useful together with "OnInfected Reject". # . # The "%v" string may be used to include the virus name. # d-i clamav-milter/RejectMsg string ### Description: Add headers to processed messages? # If you choose this option, "X-Virus-Scanned" and "X-Virus-Status" headers # will be attached to each processed message, possibly replacing existing # similar headers. # d-i clamav-milter/AddHeader select Replace # Possible choices: Replace, Yes, No, Add ### Description: Log file for clamav-milter: # Specify the full path to the clamav-milter log file, which must be # writable for the clamav daemon. Enter none to disable. # . # Logging via syslog is configured independently of this setting. # d-i clamav-milter/LogFile string /var/log/clamav/clamav-milter.log ### Description: Disable log file locking? # By default the log file is locked for writing. The lock protects against # running clamav-milter multiple times. This option disables log file locking. # d-i clamav-milter/LogFileUnlock boolean false ### Description: Maximum size of the log file (MB): # Please specify the maximum size for the log file. Using "0" will # allow that file to grow indefinitely. # d-i clamav-milter/LogFileMaxSize string 1M ### Description: Log time with each message? # d-i clamav-milter/LogTime boolean true ### Description: Use system logger? # Please choose whether you want to use the system logger (syslog). This # option can be used along with logging in a dedicated file. # d-i clamav-milter/LogSyslog boolean false ### Description: Type of syslog messages: # Please choose the type of syslog messages as detailed in the system # logger's documentation. # d-i clamav-milter/LogFacility string LOG_LOCAL6 ### Description: Enable verbose logging? # d-i clamav-milter/LogVerbose boolean false ### Description: Information to log on infected messages: # Please choose the level of information that will be logged when infected # messages are found: # - Off : no logging; # - Basic: minimal information; # - Full : verbose information. # d-i clamav-milter/LogInfected select Off # Possible choices: Off, Basic, Full ### Description: Information to log if no threat is found: # Please choose the level of information that will be logged when no threat is # found in a scanned message (this is useful in debugging but drastically # increases the log size): # - Off : no logging; # - Basic: minimal information; # - Full : verbose information. # d-i clamav-milter/LogClean select Off # Possible choices: Off, Basic, Full ### Description: Size limit for scanned messages (MB): # Please specify the maximum size for scanned messages. Messages bigger than # this limit will not be scanned. # . # You should check that this value is lower than the value of "StreamMaxLength" # in the clamd.conf file. # d-i clamav-milter/MaxFileSize string 25M ### Description: Do you want clamav-milter to support multiple recipients? # This option affects the behaviour of LogInfected, LogClean and VirusAction # when a message with multiple recipients is scanned: # If SupportMultipleRecipients is off (the default) # then one single log entry is generated for the message and, in case the # message is determined to be malicious, the command indicated by VirusAction # is executed just once. In both cases only the last recipient is reported. # If SupportMultipleRecipients is on: # then one line is logged for each recipient and the command indicated # by VirusAction is also executed once for each recipient. # . # Note: although it's probably a good idea to enable this option, the default value # is currently set to off for legacy reasons. # d-i clamav-milter/SupportMultipleRecipients boolean false ### Description: Do you want to enable log rotation? # d-i clamav-milter/LogRotate boolean true ############################ #### clamsmtp_1.10-17.2_amd64.deb ############################ ### Description: Add a clamsmtp system user and group? # New installations of clamsmtp install with a system user and group of # "clamsmtp". The "clamav" user is added to the clamsmtp group to # allow the clamav-daemon process to view the quarantine directory. If # this option is set, the installation process will also update the ownership # and permissions of the quarantine and run directories. # d-i clamsmtp/addusergroup boolean true ### Description: Fix directory permissions? # clamsmtpd needs read and write permissions to the virus spool directory, # and the run directory in which its PID file is created. Additionally, the # Clam AV daemon must have read access to the spool directory to scan for # viruses. # . # The post-installation script can fix the permissions and ownership of these # two directories. It will consult the /etc/clamsmtpd.conf file for the # administratively assigned TempDirectory, PidFile, User, and Group variables, # and then update the two directories appropriately. # . # Be sure to check directory permissions after running the init script with the # parameters 'start' or 'restart'. # d-i clamsmtp/do-fixperms boolean false ### Description: Purge spool directory on --purge? # The virus spool directory may contain quarantined viruses that can be removed # automatically when purging the package. # d-i clamsmtp/purge boolean true ############################ #### cloudkitty-api_17.0.0-3_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i cloudkitty/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i cloudkitty/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i cloudkitty/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i cloudkitty/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i cloudkitty/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i cloudkitty/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i cloudkitty/api-endpoint-address string ### Description: This service endpoint protocol: # d-i cloudkitty/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i cloudkitty/api-endpoint-region-name string regionOne ############################ #### cloudkitty-common_17.0.0-3_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i cloudkitty/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i cloudkitty/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i cloudkitty/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i cloudkitty/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i cloudkitty/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i cloudkitty/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i cloudkitty/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i cloudkitty/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i cloudkitty/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i cloudkitty/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i cloudkitty/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i cloudkitty/ksat-admin-password password ### Description: Auth server service username: # d-i cloudkitty/ksat-service-username string ### Description: Auth server service project name: # d-i cloudkitty/ksat-service-project-name string service ### Description: Auth server service password: # d-i cloudkitty/ksat-service-password password ############################ #### collectd-core_5.12.0-14_amd64.deb ############################ ### Description: Remove all collected data (e.g. RRD files)? # The /var/lib/collectd/ directory which contains the data files containing the # collected statistics is about to be removed. For example, this directory # includes (in the default configuration) all RRD files. # . # If you're purging the collectd package in order to replace it with a more # recent or custom version or if you want to keep the data for further # analysis, the data should be kept. # d-i collectd/postrm_purge_data boolean true ############################ #### colplot_5.2.0-1.1_all.deb ############################ ### Description: Web server: # Please select the web server for which Colplot should be automatically # configured. # . # Select "None" if you would like to configure the web server manually. # d-i colplot/webserver select apache2 # Possible choices: apache2, lighttpd, None ############################ #### configure-debian_1.0.3+nmu3_all.deb ############################ ### Description: Which subsection do you want? # d-i configure-debian/packages_subsection select # Possible choices: ${CHOICES} ### Description: Which program do you want to configure? # d-i configure-debian/packages_program select # Possible choices: ${CHOICES} ### Description: Would you like to configure another program? # d-i configure-debian/packages_another boolean ############################ #### conserver-client_8.2.7-2+b1_amd64.deb ############################ ### Description: Do you want to configure console automatically? # Setting this to true will edit /etc/conserver/console.cf # and replace CONSERVER_MASTER and CONSERVER_PORT with the # configured values in the next questions # d-i conserver-client/config boolean true ### Description: Hostname where your conserver server is installed: # The conserver hostname is the hostname where the conserver-server # package is installed. The client, 'console', will use the hostname 'console' # if left empty. The server name can be changed during runtime with # the -M option. # d-i conserver-client/server string localhost ### Description: The server port number to connect to: # Set the conserver server port to connect to. This may be either a port # number or a service name. # d-i conserver-client/port string 3109 ############################ #### conserver-server_8.2.7-2+b1_amd64.deb ############################ ### Description: The master port number for the conserver server: # Set the TCP port for the master process to listen on for clients. This may # be either a port number or a service name. The original port number for # conserver is 782, must be higher than 1024 if running as non-root. # d-i conserver-server/port string 3109 ### Description: The base port number for the conserver children: # Set the base port for children to listen on. Each child starts looking for # free ports at this port number and working upward, trying a maximum number # of ports equal to twice the maximum number of groups. If no free ports are # available in that range, conserver exits. By default, conserver lets the # operating system choose a free port. # Empty input selects the default. # (Conserver forks a child for each group of consoles it must manage and # assigns each process a port number to listen on.) # d-i conserver-server/base_port string ### Description: The listen address (defaults to all addresses if empty): # Set the address to listen on. This allows conserver to bind to a # particular IP address (like `127.0.0.1') instead of all interfaces. The # default is to bind to all interfaces. # d-i conserver-server/listen_address string ### Description: Should conserver run as root? # Conserver can be configured to run as root or as 'conservr'. It is not # possible to use the shadow password if running as non-root in # conserver.passwd. (See the manual for conserver.passwd for more details.) # d-i conserver-server/run_as_root boolean false ############################ #### console-common_0.7.91_all.deb ############################ ### Description: Policy for handling keymaps: # The keymap records the layout of symbols on the keyboard. # . # - 'Select keymap from arch list': select one of the predefined keymaps # specific for your architecture (recommended for non-USB keyboards); # - 'Don't touch keymap': don't overwrite the keymap in /etc/console, # which is maintained manually with install-keymap(8); # - 'Keep kernel keymap': prevent any keymap from being loaded next time # the system boots; # - 'Select keymap from full list': list all the predefined keymaps. # Recommended when using cross-architecture (often USB) keyboards. # d-i console-data/keymap/policy select Don't touch keymap # Possible choices: Select keymap from arch list, Don't touch keymap, Keep kernel keymap, Select keymap from full list ### Description: Keyboard layout family: # Please specify the generic family name for the keyboard # layout. Usually, the layout family name is taken from the first keys on the # left of the top letters row of the keymap. # d-i console-data/keymap/family select qwerty # Possible choices: ${choices} ### Description: Keyboard layout: # In order to refine the keymap choice, please select the # physical layout of the keyboard. # d-i console-data/keymap/template/layout select # Possible choices: ${choices} ### Description: Keyboard variant: # The selected keyboard layout has several variants. Please select the # one matching the keyboard. # d-i console-data/keymap/template/variant select # Possible choices: ${choices} ### Description: Keymap: # The selected keyboard allows a choice from a range of keymaps. # Usually these were designed either for specific tastes (for instance # with dead keys) or for specific needs (such as programming). # d-i console-data/keymap/template/keymap select # Possible choices: ${choices} ### Description: Keymap: # If the keyboard is designed for a different computer architecture, you should # choose a specific keymap in the full map. # d-i console-data/keymap/full select # Possible choices: ${choices} ### Description: Are you ready for the ADB key codes transition? # The kernel is configured to have the keyboard send ADB key codes. This # behavior is now deprecated and no longer supported. # . # For best results, you should reconfigure the kernel with # CONFIG_MAC_ADBKEYCODES=n. Alternatively, you can pass # 'keyboard_sends_linux_keycodes=1' as an argument to the kernel. # . # Please be aware that the transition will most probably break the X # configuration, so it is strongly recommended to close all X sessions # now and adapt the configuration afterwards by running # 'dpkg-reconfigure console-data'. # d-i console-data/keymap/powerpcadb boolean ### Description: for internal use # d-i console-data/bootmap-md5sum string none ############################ #### console-data_1.12-9_all.deb ############################ ### Description: Policy for handling keymaps: # The keymap records the layout of symbols on the keyboard. # . # - 'Select keymap from arch list': select one of the predefined keymaps # specific for your architecture (recommended for non-USB keyboards); # - 'Don't touch keymap': don't overwrite the keymap in /etc/console, # which is maintained manually with install-keymap(8); # - 'Keep kernel keymap': prevent any keymap from being loaded next time # the system boots; # - 'Select keymap from full list': list all the predefined keymaps. # Recommended when using cross-architecture (often USB) keyboards. # d-i console-data/keymap/policy select Don't touch keymap # Possible choices: Select keymap from arch list, Don't touch keymap, Keep kernel keymap, Select keymap from full list ### Description: Keyboard layout family: # Please specify the generic family name for the keyboard # layout. Usually, the layout family name is taken from the first keys on the # left of the top letters row of the keymap. # d-i console-data/keymap/family select qwerty # Possible choices: ${choices} ### Description: Keyboard layout: # In order to refine the keymap choice, please select the # physical layout of the keyboard. # d-i console-data/keymap/template/layout select # Possible choices: ${choices} ### Description: Keyboard variant: # The selected keyboard layout has several variants. Please select the # one matching the keyboard. # d-i console-data/keymap/template/variant select # Possible choices: ${choices} ### Description: Keymap: # The selected keyboard allows a choice from a range of keymaps. # Usually these were designed either for specific tastes (for instance # with dead keys) or for specific needs (such as programming). # d-i console-data/keymap/template/keymap select # Possible choices: ${choices} ### Description: Keymap: # If the keyboard is designed for a different computer architecture, you should # choose a specific keymap in the full map. # d-i console-data/keymap/full select # Possible choices: ${choices} ### Description: Are you ready for the ADB key codes transition? # The kernel is configured to have the keyboard send ADB key codes. This # behavior is now deprecated and no longer supported. # . # For best results, you should reconfigure the kernel with # CONFIG_MAC_ADBKEYCODES=n. Alternatively, you can pass # 'keyboard_sends_linux_keycodes=1' as an argument to the kernel. # . # Please be aware that the transition will most probably break the X # configuration, so it is strongly recommended to close all X sessions # now and adapt the configuration afterwards by running # 'dpkg-reconfigure console-data'. # d-i console-data/keymap/powerpcadb boolean ### Description: for internal use # d-i console-data/bootmap-md5sum string none ### Description: Keymap to use: # d-i console-keymaps-acorn/keymap select # Possible choices: American English, Belarusian, Belgian, Brazilian (ABNT2 layout), Brazilian (EUA layout), British English, Bulgarian, Canadian Multilingual, Croatian, Czech, Danish, Dutch, Dvorak, Estonian, Finnish, French, German, Greek, Hebrew, Hungarian, Icelandic, Italian, Japanese, Kirghiz, Latin American, Latvian, Lithuanian, Macedonian, Norwegian, Polish, Portuguese, Romanian, Russian, Serbian, Slovakian, Slovene, Spanish, Swedish, Swiss French, Swiss German, Turkish (F layout), Turkish (Q layout), Ukrainian ### Description: Keymap to use: # d-i console-keymaps-amiga/keymap select # Possible choices: American English, French, German, Italian, Spanish, Swedish, Swiss German ### Description: Keymap to use: # d-i console-keymaps-at/keymap select # Possible choices: American English, Belarusian, Belgian, Brazilian (ABNT2 layout), Brazilian (EUA layout), British English, Bulgarian, Canadian French, Canadian Multilingual, Croatian, Czech, Danish, Dutch, Dvorak, Estonian, Finnish, French, German, Greek, Hebrew, Hungarian, Icelandic, Italian, Japanese, Kirghiz, Latin American, Latvian, Lithuanian, Macedonian, Norwegian, Polish, Portuguese, Romanian, Russian, Serbian, Slovakian, Slovene, Spanish, Swedish, Swiss French, Swiss German, Thai, Turkish (F layout), Turkish (Q layout), Ukrainian ### Description: Keymap to use: # d-i console-keymaps-atari/keymap select # Possible choices: American English, British English, French, German, Swedish ### Description: Keymap to use: # d-i console-keymaps-dec/keymap select # Possible choices: American English ### Description: Keymap to use: # d-i console-keymaps-mac/keymap select # Possible choices: American English (82 keys), American English (extended kbd), French (alternate), French (extended kbd), German (extended kbd) ### Description: Keymap to use: # d-i console-keymaps-sun/keymap select # Possible choices: American English, British English, Czech, Finnish, French, German, Japanese (type 4), Japanese (type 5), Norwegian (type 4), Norwegian (type 5), Polish, Russian, Spanish (type 4), Spanish (type 5), Turkish (Q layout) ### Description: Keymap to use for a USB keyboard: # d-i console-keymaps-usb/keymap select # Possible choices: American English, Belgian, British English, Danish, Dvorak, Finnish, French, German, Italian, Italian, Portuguese, Spanish, Swedish, Swiss French, Swiss German ############################ #### console-setup_1.221_all.deb ############################ ### Description: Character set to support: # Please choose the character set that should be supported by the console font. # . # If you don't use a framebuffer, the choices that start with "." will # reduce the number of available colors on the console. # d-i console-setup/codeset47 select # Possible choices: . Arabic, # Armenian, # Cyrillic - KOI8-R and KOI8-U, # Cyrillic - non-Slavic languages, . Cyrillic - non-Slavic languages (for blind users), # Cyrillic - Slavic languages (also Bosnian and Serbian Latin), . Cyrillic - Slavic languages (for blind users), . Ethiopic, # Georgian, # Greek, . Greek (for blind users), # Hebrew, # Lao, # Latin1 and Latin5 - western Europe and Turkic languages, # Latin2 - central Europe and Romanian, # Latin3 and Latin8 - Chichewa; Esperanto; Irish; Maltese and Welsh, # Latin7 - Lithuanian; Latvian; Maori and Marshallese, . Latin - Vietnamese, # Thai, . Combined - Latin; Slavic Cyrillic; Hebrew; basic Arabic, . Combined - Latin; Slavic Cyrillic; Greek, . Combined - Latin; Slavic and non-Slavic Cyrillic, Guess optimal character set ### Description: Font for the console: # "VGA" has a traditional appearance and has medium coverage of # international scripts. "Fixed" has a simplistic appearance and has # better coverage of international scripts. "Terminus" may help to # reduce eye fatigue, though some symbols have a similar aspect which # may be a problem for programmers. # . # If you prefer a bold version of the Terminus font, choose either # TerminusBold (if you use a framebuffer) or TerminusBoldVGA (otherwise). # d-i console-setup/fontface47 select # Possible choices: ${CHOICES} ### Description: Font size: # Please select the size of the font for the console. For reference, # the font used when the computer boots has size 8x16. # d-i console-setup/fontsize-text47 select # Possible choices: ${CHOICES} ### Description: Font size: # Please select the size of the font for the console. Some font sizes # require framebuffer. # d-i console-setup/fontsize-fb47 select # Possible choices: ${CHOICES} ### Description: Encoding to use on the console: # d-i console-setup/charmap47 select # Possible choices: ${CHOICES} ### Description: for internal use # d-i console-setup/fontsize string ### Description: for internal use # d-i console-setup/codesetcode string ### Description: for internal use # d-i console-setup/store_defaults_in_debconf_db boolean true ############################ #### keyboard-configuration_1.221_all.deb ############################ ### Description: Keyboard model: # Please select the model of the keyboard of this machine. # d-i keyboard-configuration/model select # Possible choices: ${CHOICES} ### Description: Country of origin for the keyboard: # The layout of keyboards varies per country, with some countries # having multiple common layouts. Please select the country of origin # for the keyboard of this computer. # d-i keyboard-configuration/layout select # Possible choices: ${CHOICES} ### Description: Keyboard layout: # Please select the layout matching the keyboard for this machine. # d-i keyboard-configuration/variant select # Possible choices: ${CHOICES} ### Description: Keep the current keyboard layout in the configuration file? # The current keyboard layout in the configuration file # /etc/default/keyboard is defined as XKBLAYOUT="${XKBLAYOUT}" and # XKBVARIANT="${XKBVARIANT}". # . # Please choose whether you want to keep it. If you choose this option, # no questions about the keyboard layout will be asked and the current # configuration will be preserved. # d-i keyboard-configuration/unsupported_config_layout boolean true ### Description: Keep default keyboard layout (${XKBLAYOUTVARIANT})? # The default value for the keyboard layout is XKBLAYOUT="${XKBLAYOUT}" # and XKBVARIANT="${XKBVARIANT}". This default value is based on the # currently defined language/region and the settings in # /etc/X11/xorg.conf. # . # Please choose whether you want to keep it. If you choose this option, # no questions about the keyboard layout will be asked. # d-i keyboard-configuration/unsupported_layout boolean true ### Description: Keep current keyboard options in the configuration file? # The current keyboard options in the configuration file # /etc/default/keyboard are defined as XKBOPTIONS="${XKBOPTIONS}". # . # If you choose to keep these options, no questions about the keyboard # options will be asked. # d-i keyboard-configuration/unsupported_config_options boolean true ### Description: Keep default keyboard options (${XKBOPTIONS})? # The default value for the options of the keyboard layout is # XKBOPTIONS="${XKBOPTIONS}". It is based on the currently defined # language/region and the settings in /etc/X11/xorg.conf. # . # If you choose to keep it, no questions about the keyboard options # will be asked. # d-i keyboard-configuration/unsupported_options boolean true ### Description: Method for toggling between national and Latin mode: # You will need a way to toggle the keyboard between the national # layout and the standard Latin layout. # . # Right Alt or Caps Lock keys are often chosen for ergonomic reasons # (in the latter case, use the combination Shift+Caps Lock for normal Caps # toggle). Alt+Shift is also a popular combination; it will # however lose its usual behavior in Emacs and other programs # that use it for specific needs. # . # Not all listed keys are present on all keyboards. # d-i keyboard-configuration/toggle select Alt+Shift # Possible choices: Caps Lock, Right Alt (AltGr), Right Control, Right Shift, Right Logo key, Menu key, Alt+Shift, Control+Shift, Control+Alt, Alt+Caps Lock, Left Control+Left Shift, Left Alt, Left Control, Left Shift, Left Logo key, Scroll Lock key, No toggling ### Description: Method for temporarily toggling between national and Latin input: # When the keyboard is in national mode and one wants to type only a few # Latin letters, it might be more appropriate to switch temporarily to # Latin mode. The keyboard remains in that mode as long as the chosen key is # kept pressed. That key may also be used to input national letters when # the keyboard is in Latin mode. # . # You can disable this feature by choosing "No temporary switch". # d-i keyboard-configuration/switch select No temporary switch # Possible choices: No temporary switch, Both Logo keys, Right Alt (AltGr), Right Logo key, Left Alt, Left Logo key ### Description: Key to function as AltGr: # With some keyboard layouts, AltGr is a modifier key used to input # some characters, primarily ones that are unusual for the language of the # keyboard layout, such as foreign currency symbols and accented letters. # These are often printed as an extra symbol on keys. # d-i keyboard-configuration/altgr select Right Alt (AltGr) # Possible choices: The default for the keyboard layout, No AltGr key, Right Alt (AltGr), Right Control, Right Logo key, Menu key, Left Alt, Left Logo key, Keypad Enter key, Both Logo keys, Both Alt keys ### Description: Compose key: # The Compose key (known also as Multi_key) causes the computer to interpret # the next few keystrokes as a combination in order to produce a character # not found on the keyboard. # . # On the text console the Compose key does not work in Unicode mode. If not # in Unicode mode, regardless of what you choose here, you can always also # use the Control+period combination as a Compose key. # d-i keyboard-configuration/compose select No compose key # Possible choices: No compose key, Right Alt (AltGr), Right Control, Right Logo key, Menu key, Left Logo key, Caps Lock ### Description: Use Control+Alt+Backspace to terminate the X server? # By default the combination Control+Alt+Backspace does nothing. If # you want it can be used to terminate the X server. # d-i keyboard-configuration/ctrl_alt_bksp boolean false ### Description: Keymap to use: # d-i keyboard-configuration/xkb-keymap select # Possible choices: American English, Albanian, Arabic, Asturian, Bangladesh, Belarusian, Bengali, Belgian, Berber (Latin), Bosnian, Brazilian, British English, Bulgarian (BDS layout), Bulgarian (phonetic layout), Burmese, Canadian French, Canadian Multilingual, Catalan, Chinese, Croatian, Czech, Danish, Dutch, Dvorak, Dzongkha, Esperanto, Estonian, Ethiopian, Finnish, French, Georgian, German, Greek, Gujarati, Gurmukhi, Hebrew, Hindi, Hungarian, Icelandic, Irish, Italian, Japanese, Kannada, Kazakh, Khmer, Kirghiz, Korean, Kurdish (F layout), Kurdish (Q layout), Lao, Latin American, Latvian, Lithuanian, Macedonian, Malayalam, Nepali, Northern Sami, Norwegian, Persian, Philippines, Polish, Portuguese, Punjabi, Romanian, Russian, Serbian (Cyrillic), Sindhi, Sinhala, Slovak, Slovenian, Spanish, Swedish, Swiss French, Swiss German, Tajik, Tamil, Telugu, Thai, Tibetan, Turkish (F layout), Turkish (Q layout), Ukrainian, Uyghur, Vietnamese ### Description: for internal use # d-i keyboard-configuration/modelcode string ### Description: for internal use # d-i keyboard-configuration/layoutcode string ### Description: for internal use # d-i keyboard-configuration/variantcode string ### Description: for internal use # d-i keyboard-configuration/optionscode string ### Description: for internal use # d-i keyboard-configuration/store_defaults_in_debconf_db boolean true ############################ #### courier-base_1.0.16-3+b6_amd64.deb ############################ ### Description: Create directories for web-based administration? # Courier uses several configuration files in /etc/courier. Some of # these files can be replaced by a subdirectory whose contents are # concatenated and treated as a single, consolidated, configuration # file. # . # The web-based administration provided by the courier-webadmin package # relies on configuration directories instead of configuration files. # If you agree, any directories needed for the web-based # administration tool will be created unless there is already a # plain file in place. # d-i courier-base/webadmin-configmode boolean false ### Description: Path to Maildir directory: # Please give the relative path name from each user's home directory to the # Maildir directory where the Courier servers store and access the # user's email. Please refer to the maildir.courier(5) manual page if you are # unfamiliar with the mail storage format used by Courier. # d-i courier-base/maildir string Maildir ############################ #### courier-mta_1.0.16-3+b6_amd64.deb ############################ ### Description: Default domain: # Please specify a valid email domain. Most header rewriting functions will # append this domain to all email addresses which do not specify a domain, # such as local accounts. # d-i courier-mta/defaultdomain string ### Description: "From" header for delivery notifications: # Please specify a valid value for the "From" header for mail delivery # notifications. These notifications cannot be sent without that setting. # d-i courier-mta/dsnfrom string ############################ #### courier-webadmin_1.0.16-3+b6_amd64.deb ############################ ### Description: Activate CGI program? # To allow courier-webadmin to work out of the box, the CGI # program /usr/lib/courier/courier/webmail/webadmin needs to # be installed as /usr/lib/cgi-bin/courierwebadmin with the SUID bit set. # . # This may have serious security implications, because # courierwebadmin runs as root. Moreover, that solution is # not guaranteed to work, # depending on the web server software and its configuration. # . # If you choose this option and the web server setup is # policy-compliant, you can access the administration frontend through # http://localhost/cgi-bin/courierwebadmin. # d-i courier-webadmin/install-cgi boolean false ### Description: Password for Courier administration: # A password is needed to protect access to the Courier administration # web interface. Please choose one now. # d-i courier-webadmin/password password ############################ #### sqwebmail_6.0.5+1.0.16-3+b6_amd64.deb ############################ ### Description: Calendaring mode: # Please specify if you would like to enable calendaring in 'local' mode, # enable groupware or 'net' mode or disable it. # The courier-pcp package is required to use the groupware mode. # . # Local mode adds very little overhead over a disabled calendaring # mode. On the other hand, groupware mode is less resources-friendly and # requires a separate daemon process to be run. # . # For more information, please refer to /usr/share/doc/sqwebmail/PCP.html. # d-i sqwebmail/calendarmode select local # Possible choices: local, net, disabled ### Description: Ispell dictionary: # SqWebMail allows you to spellcheck your emails. Please select an # appropriate dictionary for ispell. # d-i sqwebmail/dictionary select default # Possible choices: ${DICTS} ### Description: Installation method for HTML documents and images: # The HTML documents and images in /usr/share/sqwebmail can be made # accessible at /var/www/sqwebmail via a symbolic link; or by being # copied directly into a directory there; or not at all. # . # The 'copy' option is recommended for security reasons. However, if # 'FollowSymLinks' or 'SymLinksIfOwnerMatch' are already enabled in # Apache configuration, the first option can be considered. The last # option needs manual actions to configure the web server. # . # Please note that /var/www/sqwebmail will be removed if this package is # purged unless the 'custom' option is chosen. # d-i sqwebmail/install-www select symlink # Possible choices: symlink, copy, custom ### Description: for internal use # d-i sqwebmail/install-www-backup string ############################ #### couriergraph_0.25-5_all.deb ############################ ### Description: Should CourierGraph start on boot? # Couriergraph can start on boot time as a daemon. Then it will monitor # your mail logfile for changes. This is recommended. # . # The other method is to call couriergraph.pl by hand with the -l parameter. # d-i couriergraph/start_on_boot boolean true ### Description: Logfile to be used by couriergraph: # Enter the logfile which should be used to create the databases for # couriergraph. If unsure, leave default. # d-i couriergraph/logfile string /var/log/mail.log ### Description: Remove RRD files on purge? # Couriergraph keeps its database files under /var/lib/couriergraph. State # whether this directory should be removed completely on purge or not. # d-i couriergraph/stay_on_purge boolean true ############################ #### cpu_1.4.3-13+b1_amd64.deb ############################ ### Description: Do you want to manage cpu's configuration through debconf? # Please confirm if you want to allow debconf to manage some parts of your # cpu.conf. Please note that any further manual changes to cpu.conf # will never be overwritten by debconf. # d-i cpu/do_debconf boolean true ### Description: LDAP server: # Please insert the URI of the LDAP server you plan to use with CPU. Use # the standard form of "ldap[s]://host[:port]". The default port value is # 389. Use ldaps if you intend to use a TLS encrypted connection. # d-i cpu/ldap/LDAP_URI string ldap://localhost ### Description: Base DN of your user subtree: # Please enter the DN of the part of your directory that contains the users # you wish to manage with CPU. # d-i cpu/ldap/USER_BASE string ### Description: Base DN of your group subtree: # Please enter the DN of the part of your directory that contains the groups # you wish to manage with CPU. # d-i cpu/ldap/GROUP_BASE string ### Description: LDAP user DN: # Please insert the DN of the user CPU will bind to the LDAP server with. # Usually this will be your LDAP admin DN, but can be any other DN, as long # as it is configured to have full control over at least the subtree under # the base you selected before. # . # Example: "cn=admin,dc=domain,dc=tld" # d-i cpu/ldap/BIND_DN string ### Description: LDAP password: # Please enter the password to use when binding to the LDAP directory. Note # that this password will be stored in cleartext in your /etc/cpu/cpu.conf # file, so don't let that file became readable to anyone you don't want to # give the same power of the user cpu will bind with. # d-i cpu/ldap/BIND_PASS password ############################ #### cpufrequtils_008-2_amd64.deb ############################ ### Description: Enable cpufreq governor at install time? (for internal use) # This is an internal (hidden) debconf question. It should not be translated. # d-i cpufrequtils/enable boolean true ############################ #### crm114_20100106-10_amd64.deb ############################ ### Description: Proceed with CRM114 upgrade? # The version of the crm114 package that is about to be installed is # not able to use .css files created by the currently installed version. This means # that any crm114 command is likely to fail with an error code, possibly rejecting # incoming e-mail. # . # If the mail system on this machine depends on crm114, it is highly # recommended that delivery (or just crm114 processing) should be temporarily # disabled before the package is upgraded. # . # If you proceed with the upgrade, you should carefully check whether crm114 # is still properly operating with existing .css files. If it does not, these # files should be rebuilt by using the mailreaver cache, or recreated from # scratch. # d-i crm114/cssupgrade boolean false ### Description: Force CRM114 upgrade? # If you enable this option, crm114 package won't ask any safety questions # during the upgrade. It is your full responsibility to arrange things in # advance in such a way that nothing breaks after the upgrade. # d-i crm114/forceupgrade boolean false ############################ #### cryptsetup_2.6.1-4~deb12u2_amd64.deb ############################ ### Description: Continue with cryptsetup removal? # This system has unlocked dm-crypt devices: ${cryptmap} # . # If these devices are managed with cryptsetup, you might be unable to # lock the devices after the package removal, though other tools can be # used for managing dm-crypt devices. Any system shutdown or reboot will # lock the devices. # . # Do not choose this option if you want to lock the dm-crypt devices # before package removal. # d-i cryptsetup/prerm_active_mappings boolean true ############################ #### cryptsetup-initramfs_2.6.1-4~deb12u2_all.deb ############################ ### Description: Continue with cryptsetup-initramfs removal? # This system has unlocked dm-crypt devices: ${cryptmap} # . # If these devices are managed with cryptsetup and need to be present at # initramfs stage, then you might be unable to boot your system after the # package removal. # d-i cryptsetup-initramfs/prerm_active_mappings boolean true ############################ #### cryptsetup-nuke-password_4_amd64.deb ############################ ### Description: Nuke password: # If you setup a “nuke password”, you will be able to type this password # at the early-boot prompt asking your passphrase to unlock your # luks-encrypted partitions. Instead of decrypting the partitions, typing # this password will instead wipe the encryption keys from the luks # container so that it is no longer possible to unlock the encrypted # partitions. # . # This provides a relatively stealth way to make your data unreadable in # case you fear that your computer is going to be seized. # . # If you want to cancel this operation or disable any nuke password already # configured, simply enter an empty password. If needed, you will be given # the option to pick between both choices. # d-i cryptsetup-nuke-password/password password ### Description: Re-enter password to verify: # Please enter the same nuke password again to verify that you have typed it # correctly. # d-i cryptsetup-nuke-password/password-again password ### Description: A nuke password is already configured, what should be done? # The existence of /etc/cryptsetup-nuke-password/password_hash suggests # that a nuke password is already configured. If you decide to keep the # current nuke password, nothing will be done. If you decide to overwrite the # current nuke password, you will be asked for a new password and it will # replace the currently configured one. If you decide to remove the # nuke password, you will not be asked for a new password and the currently # configured password will be disabled. # d-i cryptsetup-nuke-password/already-configured select overwrite # Possible choices: Keep the current password, Overwrite the current password, Remove the current password ############################ #### cups_2.4.2-3+deb12u5_amd64.deb ############################ ### Description: Do you want CUPS to print unknown jobs as raw jobs? # The Internet Printing Protocol (IPP) enforces a MIME type for all # print jobs. Since not all sources of print jobs can attach an # appropriate type, many jobs get submitted as the MIME type # application/octet-stream and could be rejected if CUPS cannot guess # the job's format. # . # CUPS can handle all such jobs as "raw" jobs, which causes them to be # sent directly to the printer without processing. # . # It is recommended to choose this option if the server will be # accepting print jobs from Windows computers or Samba servers. # d-i cupsys/raw-print boolean true ### Description: Printer communication backends: # CUPS uses backend programs to communicate with the printer device or port. # . # Please choose the backend program to be used by CUPS. The default choice # should fit the most common environments. # d-i cupsys/backend multiselect lpd, socket, usb, snmp, dnssd # Possible choices: lpd, socket, usb, snmp, dnssd ############################ #### cups-bsd_2.4.2-3+deb12u5_amd64.deb ############################ ### Description: Do you want to set up the BSD lpd compatibility server? # The CUPS package contains a server that can accept BSD-style print # jobs and submit them to CUPS. It should only be set up if other # computers are likely to submit jobs over the network via the "BSD" or # "LPR" services, and these computers cannot be converted to use the # IPP protocol that CUPS uses. # d-i cups-bsd/setuplpd boolean false ############################ #### cvsd_1.0.24+b1_amd64.deb ############################ ### Description: Location of chroot jail: # cvsd can run in a chroot jail. This is the preferred method of # operation. Specify the location of the chroot jail. If you make this # 'none' no chroot jail will be created and used. # A chroot file hierarchy will be created in the specified location. # d-i cvsd/rootjail string /var/lib/cvsd ### Description: The maximum number of connections that can be handled: # It is possible to specify a maximum number of connections that cvsd # can handle simultaneously. Specifying 0 (zero) will put no limit to # the number of connections. # d-i cvsd/maxconnections string 10 ### Description: Nice value cvsd should run at: # cvsd can be run at reduced priority so it will not take up too # many resources, especially if a user specifies a -z option to cvs. # The priority can also be increased (negative value here). # d-i cvsd/nice string 1 ### Description: Umask cvsd should run at: # Specify the umask cvsd and cvs should use when creating files. # . # The umask should be specified as an octal value and represents # the permissions that should be taken away when creating a file # (e.g. using 027 will create files with mode 640 or rw-r-----). # d-i cvsd/umask string 027 ### Description: Address and port on which cvsd will listen: # With the first argument you can specify the address cvsd should listen on. # The '*' address specifies that cvsd should listen on all addresses. # You can specify a IPv4 address, IPv6 address, a hostname or '*'. # . # The second argument is the service name (e.g. cvspserver) or port number # (default 2401) cvsd will listen on. # . # The address and port should be separated by a space and you can specify multiple # address-port combinations by separating them with spaces. # d-i cvsd/listen string * 2401 ### Description: Repositories to serve: # The whole idea of cvsd is to serve repositories. Specify a colon ':' # separated list of repositories to serve. The location of these repositories # is relative to the specified chroot jail (${rootjail}) and should start with a '/'. # . # The repositories here should be initialized by hand with something like # 'cvs -d ${rootjail}/myrepos init' after which passwords can be set with # 'cvsd-passwd ${rootjail}/myrepos anonymous'. See the file # /usr/share/doc/cvsd/README.gz for details on creating repositories. # d-i cvsd/repositories string /demo:/myrepos ### Description: Resources of pserver processes to limit: # The pserver wrapper can be configured to limit the resource usage that # a pserver process can have. These resource limits will be set on each # pserver process and not on the wrapper. # . # Choose from the list the resources that you want to limit. # You will be asked to specify limits about every resource you selected here. # . # Note that not all resources may be available on all systems and that # resources may be system and kernel specific so use these with caution. # The results of exceeding the set limits may also be system specific # but will most likely stop the cvs process and close the connection # (may be problematic with write access to cvs repository). # d-i cvsd/limits multiselect # Possible choices: coredumpsize, cputime, datasize, filesize, memorylocked, openfiles, maxproc, memoryuse, stacksize, virtmem ### Description: Maximum file size of a core dump: # Set this to 0 (zero) (should be the system default) to prevent core dumps. # Otherwise this limits the size of core dumps to the specified value. # . # This value may be specified with a suffix of 'b' (bytes), 'k' # (1024 bytes) or 'm' (1024*1024 bytes), where 'k' is the default. # d-i cvsd/limit_coredumpsize string 0 ### Description: Maximum amount of cpu time consumed: # This limits the number of cpu seconds the cvs process can use. # This will prevent too much cpu time from being allocated to a single connection. # . # This value can be formatted as 'mm:ss' or have a 'm' or 's' # suffix where 's' is default. # d-i cvsd/limit_cputime string 1:00 ### Description: Maximum size of program's data segment: # This limits the amount of memory the cvs program can use. This # specific item limits the size of the data segment. # . # This value may be specified with a suffix of 'b' (bytes), 'k' # (1024 bytes) or 'm' (1024*1024 bytes), where 'k' is the default. # d-i cvsd/limit_datasize string 10m ### Description: Maximum size of files created: # This limits the maximum size of a file created by cvs. # Note that the cvs pserver process needs to be able to create # lock files and possibly write history or other files so # don't set this to 0 (zero). # . # This value may be specified with a suffix of 'b' (bytes), 'k' # (1024 bytes) or 'm' (1024*1024 bytes), where 'k' is the default. # d-i cvsd/limit_filesize string 1m ### Description: Maximum amount of locked memory: # This limits the amount of memory the cvs process may lock. # cvs probably doesn't need to lock any memory at all. # . # This value may be specified with a suffix of 'b' (bytes), 'k' # (1024 bytes) or 'm' (1024*1024 bytes), where 'k' is the default. # d-i cvsd/limit_memorylocked string 10m ### Description: Maximum number of open files: # This limits the number of files and connections that the cvs # process can have open at a single moment. The cvs process needs # to access quite a few files so don't set this too low. # d-i cvsd/limit_openfiles string 1024 ### Description: Maximum number of processes: # This limits the maximum number of processes that a single user may have. # cvs may need to spawn additional processes to run scripts or do subtasks # so don't set this too low. # d-i cvsd/limit_maxproc string 20 ### Description: Maximum size of resident memory: # This specifies the amount of physical memory a process may have. # . # This value may be specified with a suffix of 'b' (bytes), 'k' # (1024 bytes) or 'm' (1024*1024 bytes), where 'k' is the default. # d-i cvsd/limit_memoryuse string 10m ### Description: Maximum stack size: # This limits the size of the stack. # . # This value may be specified with a suffix of 'b' (bytes), 'k' # (1024 bytes) or 'm' (1024*1024 bytes), where 'k' is the default. # d-i cvsd/limit_stacksize string 10m ### Description: Maximum amount of virtual memory allocated: # This limits the total amount of virtual memory a process may have allocated. # . # This value may be specified with a suffix of 'b' (bytes), 'k' # (1024 bytes) or 'm' (1024*1024 bytes), where 'k' is the default. # d-i cvsd/limit_virtmem string 10m ### Description: Maximum number of threads: # This limits the number of threads that a single process may have. # . # This is not available under Linux so it is not in the list # for cvsd/limits. If Hurd has it it may be useful. # d-i cvsd/limit_pthreads string 20 ### Description: Remove chroot jail containing repositories? # The following directory is configured as a chroot jail for cvsd: # ${rootjail} # You may choose to remove the chroot jail but you will also lose all the # repositories inside the chroot jail. If you have not backed up your # repositories you want to keep do not remove it now and manually remove # it later once your repositories are safe. # . # If you do choose to remove the chroot directory, all directories under # it will be removed, even if they are on another file system. # . # If you choose to keep the chroot jail please note that the cvsd user and # group will be removed so uid and gid file information may no longer be # consistent. # d-i cvsd/remove_chroot boolean false ############################ #### cxref_1.6e-5_amd64.deb ############################ ### Description: Automatically configure cxref-cpp? # cxref-cpp is a cpp-like program used by cxref for better comment # processing and support. Proper operation of cxref-cpp requires # configuration against the gcc and cpp versions you have installed on your # system. These of course may change with each upgrade. This package can # attempt to automatically keep track of your installed gcc and cpp versions # and reconfigure cxref-cpp accordingly, or it can leave such configuration # up to you. In the latter case, you can run /usr/bin/cxref-cpp-configure # as root whenever you wish, and/or you can edit the file # /etc/cxref/cxref-cpp.defines by hand. In the former case, the defines # file will be automatically updated every time the cxref package is # reconfigured. In addition, cxref-cpp will detect any gcc version mismatch # at runtime and regenerate a temporary cxref-cpp.defines file on the fly, # warning the user of the situation. # d-i cxref/cxref-cpp-autoconf boolean true ############################ #### cyrus-common_3.6.1-4+deb12u1_amd64.deb ############################ ### Description: Remove the mail and news spools? # The Cyrus mail and news spools, as well as users' sieve scripts, # can be removed when the package is purged. # . # This question only applies to the default spools and sieve script # directories in /var. If you modified their location in imapd.conf, the # new locations will not be removed; just the old ones in /var. # d-i cyrus-common/removespools boolean false ############################ #### sasl2-bin_2.1.28+dfsg-10_amd64.deb ############################ ### Description: Remove /etc/sasldb2? # Cyrus SASL can store usernames and passwords in the /etc/sasldb2 database # file. # . # If important data is stored in that file, you should back it up # now or choose not to remove the file. # d-i cyrus-sasl2/purge-sasldb2 boolean false ### Description: Backup file name for /etc/sasldb2: # Cyrus SASL has stored usernames and passwords in the /etc/sasldb2 database # file. # . # That file has to be upgraded to a newer database # format. First, a backup of the current file will be created. # You can use that if you need to manually downgrade Cyrus SASL. # However, automatic downgrades are not supported. # . # Please specify the backup file name. You should check the available # disk space in that location. If the backup file already exists, it will be overwritten. # Leaving this field empty will select the default value # (/var/backups/sasldb2.bak). # d-i cyrus-sasl2/backup-sasldb2 string /var/backups/sasldb2.bak ############################ #### dailystrips_1.0.28-11.2_all.deb ############################ ############################ #### darkstat_3.0.719-1.1_amd64.deb ############################ ### Description: Do you really want to upgrade darkstat ? # The database file format of darkstat has changed, and can't be upgraded. # . # If you confirm the upgrade, the database file # /var/lib/darkstat/darkstat.db will be removed (because it will prevent # darkstat starting). A new database file will be created from scratch when # darkstat restarts. # . # If you don't confirm the upgrade, the package will be left non-configured, # and if you wish to use an older version of darkstat you will have to # downgrade manually. # d-i darkstat/upgrade-question/db_purge-2.5-1 boolean true ############################ #### davfs2_1.6.1-1_amd64.deb ############################ ### Description: Should unprivileged users be allowed to mount WebDAV resources? # The file /sbin/mount.davfs must have the SUID bit set if you want to allow # unprivileged (non-root) users to mount WebDAV resources. # . # If you do not choose this option, only root will be allowed to mount WebDAV # resources. This can later be changed by running 'dpkg-reconfigure davfs2'. # d-i davfs2/suid_file boolean false ### Description: User running the mount.davfs daemon: # Once the davfs resource has been mounted, the daemon will drop the # root privileges and will run with an unprivileged user ID. # . # Please choose which login name should be used by the daemon. # d-i davfs2/user_name string davfs2 ### Description: Group for users who will be allowed to mount WebDAV resources: # Mounting WebDAV resources creates a file in # /var/run/mount.davfs. This directory will be owned by the group # specified here. # d-i davfs2/group_name string davfs2 ### Description: Do you want to create a new user? # The "${user_name}" user does not exist on the system and will be # created if you choose this option. # d-i davfs2/new_user boolean true ### Description: Do you want to create a new group? # The "${group_name}" group does not exist on the system and will be # created if you choose this option. # d-i davfs2/new_group boolean true ############################ #### dbconfig-common_2.0.24_all.deb ############################ ### Description: Will this server be used to access remote databases? # For the database types that support it, dbconfig-common includes support # for configuring databases on remote systems. When installing a package's # database via dbconfig-common, the questions related to remote # configuration are asked with a priority such that they are # skipped for most systems. # . # If you select this option, the default behavior will be to prompt you # with questions related to remote database configuration when you install # new packages. # . # If you are unsure, you should not select this option. # d-i dbconfig-common/remote-questions-default boolean false ### Description: Remember database passwords permanently in debconf? # When you configure, upgrade, or remove applications with dbconfig-common, # administrator-level database passwords are needed. By default, these # passwords are not stored, so you will be prompted for them each time. # . # Alternatively the passwords can be permanently remembered in the debconf # database (which is protected by Unix file permissions), though this is # less secure and thus not the default setting. # . # If you would rather not be bothered for an administrative password # every time you upgrade a database application with dbconfig-common, # you should choose this option. Otherwise, you should refuse this option. # d-i dbconfig-common/remember-admin-pass boolean false ### Description: Configure database for ${pkg} with dbconfig-common? # The ${pkg} package must have a database installed and configured before # it can be used. This can be optionally handled with dbconfig-common. # . # If you are an advanced database administrator and know that you want # to perform this configuration manually, or if your database has already # been installed and configured, you should refuse this option. Details on what # needs to be done should most likely be provided in /usr/share/doc/${pkg}. # . # Otherwise, you should probably choose this option. # d-i dbconfig-common/dbconfig-install boolean true ### Description: Reinstall database for ${pkg}? # Since you are reconfiguring ${pkg}, you may also want to reinstall the # database which it uses. # . # If you wish to reinstall the database for ${pkg}, you should select # this option. If you do not wish to do so (if you are reconfiguring # the package for unrelated reasons), you should not select this option. # . # Warning: if you opt to reinstall the database and install it under a # name that already exists, the old database will be dropped without # further questions. In that case a backup of the original database is # made in /var/tmp/. # . # Warning: if you change the name of the database, the old database will # not be removed. If you change the name of the user that connects to # the database, the privileges of the original user will not be revoked. # d-i dbconfig-common/dbconfig-reinstall boolean false ### Description: Perform upgrade on database for ${pkg} with dbconfig-common? # According to the maintainer for this package, database upgrade # operations need to be performed on ${pkg}. Typically, this is due to # changes in how a new upstream version of the package needs to store # its data. # . # If you want to handle this process manually, you should # refuse this option. Otherwise, you should choose this option. # During the upgrade, a backup of the database will be made in # /var/cache/dbconfig-common/backups, from which the database can # be restored in the case of problems. # d-i dbconfig-common/dbconfig-upgrade boolean true ### Description: Deconfigure database for ${pkg} with dbconfig-common? # Since you are removing ${pkg}, it's possible that you no longer # want the underlying database and the privileges for the user # associated with this package. # . # Please choose whether database removal and privilege revocation should be # handled with dbconfig-common. # . # If you choose this option, dbconfig-common will check if ${pkg} provided # scripts and database commands to undo package specific operations and run them # if they exist. Then it will ask if you want to delete the ${pkg} database and # revoke the standard privileges for the user of ${pkg}. If you don't want any # of this, or if you want to handle this manually, you should refuse this # option. # d-i dbconfig-common/dbconfig-remove boolean true ### Description: Database type to be used by ${pkg}: # The ${pkg} package can be configured to use one of several database types. # Below, you will be presented with the available choices. # . # If other database types are supported by ${pkg} but not shown here, the reason # for their omission is that the corresponding dbconfig- packages # are not installed. If you know that you want the package to use another # supported database type, your best option is to back out of the # dbconfig-common questions and opt out of dbconfig-common assistance for this # package for now. Install your preferred dbconfig- option from # the list in the package dependencies, and then "dpkg-reconfigure ${pkg}" to # select it. # d-i dbconfig-common/database-type select # Possible choices: ${database_types} ### Description: Delete the database for ${pkg}? # If you no longer need the database for ${pkg} and the privileges of # the database user of ${pkg}, you can choose to delete the database and # revoke the privileges now. # . # If you no longer have need of the data being stored by ${pkg}, you # should choose this option. If you want to keep this data, # or if you would rather handle this process manually, you should # refuse this option. Either way, it won't affect your other databases. # d-i dbconfig-common/purge boolean false ### Description: Back up the database for ${pkg} before upgrading? # The underlying database for ${pkg} needs to be upgraded as part of the # installation process. Just in case, the database can be backed up # before this is done, so that if something goes wrong, you can revert # to the previous package version and repopulate the database. # d-i dbconfig-common/upgrade-backup boolean true ### Description: Password confirmation: # d-i dbconfig-common/password-confirm password ### Description: Password confirmation: # d-i dbconfig-common/app-password-confirm password ### Description: Next step for database upgrade: # An error occurred while upgrading the database: # . # ${error} # . # Fortunately, ${dbfile} should hold a backup of the database, made just before # the upgrade (unless the error occurred during backup creation, in which case # no changes will have been applied yet). Your options are: # * abort - Causes the operation to fail; you will need to downgrade, # reinstall, reconfigure this package, or otherwise manually intervene # to continue using it. This will usually also impact your ability to # install other packages until the installation failure is resolved. # * retry - Prompts once more with all the configuration questions # (including ones you may have missed due to the debconf priority # setting) and makes another attempt at performing the operation. # * retry (skip questions) - Immediately attempts the operation again, # skipping all questions. This is normally useful only if you have # solved the underlying problem since the time the error occurred. # * ignore - Continues the operation ignoring dbconfig-common errors. # This will usually leave this package without a functional database. # d-i dbconfig-common/upgrade-error select abort # Possible choices: abort, retry, retry (skip questions), ignore ### Description: Next step for database installation: # An error occurred while installing the database: # . # ${error} # . # Your options are: # * abort - Causes the operation to fail; you will need to downgrade, # reinstall, reconfigure this package, or otherwise manually intervene # to continue using it. This will usually also impact your ability to # install other packages until the installation failure is resolved. # * retry - Prompts once more with all the configuration questions # (including ones you may have missed due to the debconf priority # setting) and makes another attempt at performing the operation. # * retry (skip questions) - Immediately attempts the operation again, # skipping all questions. This is normally useful only if you have # solved the underlying problem since the time the error occurred. # * ignore - Continues the operation ignoring dbconfig-common errors. # This will usually leave this package without a functional database. # d-i dbconfig-common/install-error select abort # Possible choices: abort, retry, retry (skip questions), ignore ### Description: Next step for database removal: # An error occurred while removing the database: # . # ${error} # . # As a result it was not possible to remove the database for ${pkg}. Your # options are: # * abort - Causes the operation to fail; you will need to downgrade, # reinstall, reconfigure this package, or otherwise manually intervene # to continue using it. This will usually also impact your ability to # install other packages until the installation failure is resolved. # * retry - Prompts once more with all the configuration questions # (including ones you may have missed due to the debconf priority # setting) and makes another attempt at performing the operation. # * retry (skip questions) - Immediately attempts the operation again, # skipping all questions. This is normally useful only if you have # solved the underlying problem since the time the error occurred. # * ignore - Continues the operation ignoring dbconfig-common errors. # This will usually leave the database and user privileges in place. # d-i dbconfig-common/remove-error select abort # Possible choices: abort, retry, retry (skip questions), ignore ### Description: Next step: # Configuring the database for ${pkg} requires the package ${dbpackage} # to be installed and configured first, which is not something that can be # checked for automatically. # . # Your options are: # * abort - Choose this when in doubt and install ${dbpackage} before # continuing with the configuration of this package. This causes the # installation of ${pkg} to fail for now. # * retry - Prompts once more with all the configuration questions # (including ones you may have missed due to the debconf priority # setting) and makes another attempt at performing the operation. # Choose this if you chose the wrong database type by mistake. # * ignore - Continues the operation ignoring dbconfig-common errors. # This will usually leave this package without a functional database. # d-i dbconfig-common/missing-db-package-error select abort # Possible choices: abort, retry, ignore ### Description: Host name of the ${dbvendor} database server for ${pkg}: # Please select the remote hostname to use, or select "new host" to # enter a new host. # d-i dbconfig-common/remote/host select localhost # Possible choices: ${hosts} ### Description: Port number for the ${dbvendor} service: # Please specify the port the ${dbvendor} database on the remote host is # running on. To use the default port, leave this field blank. # d-i dbconfig-common/remote/port string ### Description: Host running the ${dbvendor} server for ${pkg}: # Please provide the hostname of a remote ${dbvendor} server. # . # You must have already arranged for the administrative # account to be able to remotely create databases and grant # privileges. # d-i dbconfig-common/remote/newhost string ### Description: ${dbvendor} database name for ${pkg}: # Please provide a name for the ${dbvendor} database to be used by ${pkg}. # d-i dbconfig-common/db/dbname string ### Description: ${dbvendor} username for ${pkg}: # Please provide a ${dbvendor} username for ${pkg} to register with the # database server. A ${dbvendor} user is not necessarily the same as a # system login, especially if the database is on a remote server. # . # This is the user which will own the database, tables, and other # objects to be created by this installation. This user will have # complete freedom to insert, change, or delete data in the database. # . # If your username contains an @, you need to specify the domain as well # (see below). # . # Advanced usage: if you need to define the domain that the user will log # in from, you can write "username@domain". # d-i dbconfig-common/db/app-user string ### Description: ${dbvendor} storage directory for ${pkg}: # Please provide a path where the ${dbvendor} database file for ${pkg} # should be installed into. # . # The permissions for this directory will be set to match the permissions # for the generated database file. # d-i dbconfig-common/db/basepath string ### Description: Connection method for MySQL database of ${pkg}: # By default, ${pkg} will be configured to use a MySQL server # through a local Unix socket (this provides the best performance). # To connect with a different method, or to a different server entirely, # select the appropriate option from the choices here. # d-i dbconfig-common/mysql/method select Unix socket # Possible choices: Unix socket, TCP/IP ### Description: MySQL application password for ${pkg}: # Please provide a password for ${pkg} to register with the # database server. If left blank, a random password will be # generated. # d-i dbconfig-common/mysql/app-pass password ### Description: Name of the database's administrative user: # Please provide the name of the account with which this package should perform # administrative actions. This user is the one with the power to create new # database users. # . # For MySQL, this is almost always "root". Note that this is not the # same as the Unix login "root". # d-i dbconfig-common/mysql/admin-user string ### Description: Password of the database's administrative user: # Please provide the password for the administrative account "${dbadmin}" with # which this package should create its MySQL database and user. # d-i dbconfig-common/mysql/admin-pass password ### Description: Authentication plugin for MySQL database: # Database user accounts can be configured to use a variety of plugins # for authentication with MySQL. If the server default won't work with # this application, it is necessary to specify one that will. Please # select one from the list of available plugins. Leaving the selection # set to its original value should work unless a remote server is using # unpredictable defaults, but other options may not be supported by # ${pkg}. If problems arise, the package's documentation should give # hints; see /usr/share/doc/${pkg}/. # . # Your options are: # * default - use the default determined by the server. # * mysql_native_password - no MySQL authentication plugin is used. # * sha256_password - a more secure password encryption algorithm. # * caching_sha2_password - SHA2 plus an in-memory authentication cache. # d-i dbconfig-common/mysql/authplugin select default # Possible choices: default, mysql_native_password, sha256_password, caching_sha2_password ### Description: Connection method for PostgreSQL database of ${pkg}: # By default, ${pkg} will be configured to use a PostgreSQL server through # TCP/IP because that method works in most circumstances. To connect with a # different method, select the appropriate option from the choices here. # d-i dbconfig-common/pgsql/method select TCP/IP # Possible choices: Unix socket, TCP/IP, TCP/IP + SSL ### Description: PostgreSQL application password for ${pkg}: # Please provide a password for ${pkg} to register with the database # server. If left blank, a random password will be generated. # . # If you are using "ident" authentication, the supplied password will not # be used and can be left blank. Otherwise, PostgreSQL access may need to # be reconfigured to allow password-authenticated access. # d-i dbconfig-common/pgsql/app-pass password ### Description: Name of the database's administrative user: # Please provide the name of the account with which this package should perform # administrative actions. This user is the one with the power to create new # database users. # d-i dbconfig-common/pgsql/admin-user string postgres ### Description: Password of your database's administrative user: # Please provide the password for the ${dbadmin} account with which this package # should perform administrative actions. # . # For a standard PostgreSQL installation, a database password is not # required, since authentication is done at the system level. # d-i dbconfig-common/pgsql/admin-pass password ### Description: Method for authenticating the PostgreSQL administrator: # PostgreSQL servers provide several different mechanisms for authenticating # connections. Please select what method the administrative user should use # when connecting to the server. # . # With "ident" authentication on the local machine, the server will # check that the owner of the Unix socket is allowed to connect. # PostgreSQL itself calls this peer authentication. # . # With "ident" authentication to remote hosts, RFC-1413-based ident is # used (which can be considered a security risk). # . # With "password" authentication, a password will be passed to the server # for use with some authentication backend (such as "MD5" or "PAM"). Note # that the password is still passed in the clear across network # connections if your connection is not configured to use SSL. # . # For a standard PostgreSQL installation running on the same host, # "ident" is recommended. # d-i dbconfig-common/pgsql/authmethod-admin select ident # Possible choices: ident, password ### Description: Method for authenticating PostgreSQL user: # PostgreSQL servers provide several different mechanisms for authenticating # connections. Please select what method the database user should use # when connecting to the server. # . # With "ident" authentication on the local machine, the server will # check that the owner of the Unix socket is allowed to connect. # PostgreSQL itself calls this peer authentication. # . # With "ident" authentication to remote hosts, RFC-1413-based ident is # used (which can be considered a security risk). # . # With "password" authentication, a password will be passed to the server # for use with some authentication backend (such as "MD5" or "PAM"). Note # that the password is still passed in the clear across network # connections if your connection is not configured to use SSL. # . # For a standard PostgreSQL installation running on the same host, # "password" is recommended, because typically the system username # doesn't match the database username. # d-i dbconfig-common/pgsql/authmethod-user select password # Possible choices: ident, password ### Description: Change PostgreSQL configuration automatically? # It has been determined that the database installation for ${pkg} # cannot be automatically accomplished without making changes to # the PostgreSQL server's access controls. It is suggested that this # be done by dbconfig-common when the package is installed. If # instead you would prefer to do it manually, the following line needs # to be added to your pg_hba.conf: # . # ${pghbaline} # d-i dbconfig-common/pgsql/changeconf boolean false ### Description: Revert PostgreSQL configuration automatically? # As ${pkg} is now being removed, it may no longer be necessary to # have an access control entry in the PostgreSQL server's configuration. # While keeping such an entry will not break any software on the # system, it may be seen as a potential security concern. It is suggested # that this be done by dbconfig-common when the package is removed. # If instead you would prefer to do it manually, the following line # needs to be removed from your pg_hba.conf: # . # ${pghbaline} # d-i dbconfig-common/pgsql/revertconf boolean false ### Description: for internal use. # d-i dbconfig-common/internal/reconfiguring boolean false ### Description: for internal use. # d-i dbconfig-common/internal/skip-preseed boolean false ############################ #### ddclient_3.10.0-2_all.deb ############################ ### Description: Dynamic DNS service provider: # Dynamic DNS service you are using. If the service you use is not # listed, choose "other". # d-i ddclient/service select no-ip.com # Possible choices: ${choices}, other ### Description: Dynamic DNS server (blank for default): # Server providing the dynamic DNS service (example: # members.dyndns.org). Leave blank to use the default for the # "${protocol}" protocol. # d-i ddclient/server string ### Description: Dynamic DNS update protocol: # Dynamic DNS update protocol used by your dynamic DNS service # provider. If the protocol your service uses is not listed, select # "other". # d-i ddclient/protocol select dyndns2 # Possible choices: 1984, changeip, cloudflare, cloudns, dinahosting, dnsexit, dnsmadeeasy, dondominio, dslreports1, duckdns, dyndns1, dyndns2, easydns, freedns, freemyip, gandi, godaddy, googledomains, hetzner, keysystems, namecheap, nfsn, njalla, noip, nsupdate, ovh, sitelutions, woima, yandex, zoneedit1, other ### Description: Dynamic DNS update protocol: # The name of the dynamic DNS update protocol used by your dynamic DNS # service provider. # d-i ddclient/protocol-other string ### Description: Optional HTTP proxy: # HTTP proxy in the form http://proxy.example.com or # https://proxy.example.com. Proxy authentication is not supported. # Leave blank if you do not use an HTTP proxy. # d-i ddclient/proxy string ### Description: Hosts to update (comma-separated): # Comma-separated list of fully qualified domain names to update (for # instance, "myname.dyndns.org" with only one host, or # "myname1.dyndns.org,myname2.dyndns.org" for two hosts). # d-i ddclient/names string ### Description: Username: # Username (or other type of account identifer) to use with the dynamic # DNS service. # d-i ddclient/username string ### Description: Password: # Password, API key, or token to use with the dynamic DNS service. # d-i ddclient/password password ### Description: Re-enter password: # Password, API key, or token entered again to ensure it was entered # correctly. # d-i ddclient/password-repeat password ### Description: IP address discovery method: # The method ddclient uses to determine your current IP address. # Your options: # . # Web-based IP discovery service: Periodically visit a web page that # shows your IP address. You probably want this option if your computer # is connected to the Internet via a Network Address Translation (NAT) # device such as a typical consumer router. # . # Network interface: Use the IP address assigned to your computer's # network interface (such as an Ethernet adapter or PPP connection). # You probably want this option if your computer connects directly to # the Internet (your connection does not go through a NAT device). # d-i ddclient/method select Web-based IP discovery service # Possible choices: Web-based IP discovery service, Network interface ### Description: IP discovery service: # The web-based IP discovery service you would like ddclient to use to # determine your current IP address. # d-i ddclient/web select # Possible choices: ${choices}, other ### Description: IP discovery service URL: # URL to a web page that returns your IP address. # d-i ddclient/web-url string ### Description: Network interface: # The name of the network interface (e.g., eth0, wlan0, ppp0) that # ddclient will look at to determine the current IP address. # d-i ddclient/interface string ### Description: How to run ddclient: # The ddclient run mode. Your options: # . # As a daemon: ddclient runs in the background periodically checking to # see if the IP address has changed. # . # On PPP connect: Each time you connect via PPP ddclient will start, # update the IP address, and exit. # d-i ddclient/run_mode select As a daemon # Possible choices: As a daemon, On PPP connect ### Description: Time between address checks: # How long ddclient should wait between IP address checks. Values may # be given in seconds (e.g., "300s"), in minutes (e.g., "5m"), in hours # (e.g., "7h") or in days (e.g., "1d"). # d-i ddclient/daemon_interval string 5m ### Description: How to enter host names: # How to prompt you for the host name(s) that ddclient will update. # . # If you choose "From list", this program will attempt to look up the # host names that are registered with your DynDNS account. You will # then select hosts from that list. # . # If you choose "Manually", you will have to type in the host name(s). # d-i ddclient/fetchhosts select From list # Possible choices: From list, Manually ### Description: Hosts to update: # The host name(s) to keep updated with your current IP address. (This # list of host names was downloaded from your DynDNS account.) # d-i ddclient/hostslist multiselect # Possible choices: ${choices} ############################ #### debconf_1.5.82_all.deb ############################ ### Description: Interface to use: # Packages that use debconf for configuration share a common look and feel. # You can select the type of user interface they use. # . # The dialog frontend is a full-screen, character based interface, while the # readline frontend uses a more traditional plain text interface, and both the # gnome and kde frontends are modern X interfaces, fitting the respective # desktops (but may be used in any X environment). The editor frontend lets you # configure things using your favorite text editor. The noninteractive # frontend never asks you any questions. # d-i debconf/frontend select Dialog # Possible choices: Dialog, Readline, Gnome, Kde, Editor, Noninteractive ### Description: Ignore questions with a priority less than: # Debconf prioritizes the questions it asks you. Pick the lowest priority of # question you want to see: # - 'critical' only prompts you if the system might break. # Pick it if you are a newbie, or in a hurry. # - 'high' is for rather important questions # - 'medium' is for normal questions # - 'low' is for control freaks who want to see everything # . # Note that no matter what level you pick here, you will be able to see # every question if you reconfigure a package with dpkg-reconfigure. # d-i debconf/priority select high # Possible choices: critical, high, medium, low ############################ #### debian-edu-config_2.12.44~deb12u1_all.deb ############################ ### Description: Should the init.d/update-hostname script run at boot time? # d-i debian-edu-config/update-hostname boolean false ### Description: Do you want to run enable-nat on your system? # The enable-nat script activates NAT for your Thin-Clients and overwrites # your iptables rules. # d-i debian-edu-config/enable-nat boolean false ### Description: Enter the Kerberos KDC master key: # A password is needed as Kerberos master key and for all default principals. # You can use your root password or type something else. Make sure you remember # the password. # . # Note that you will not be able to see the password as you type it. # d-i debian-edu-config/kdc-password password ### Description: Re-enter password to verify: # Please enter the same password again to verify that you have typed it # correctly. # d-i debian-edu-config/kdc-password-again password ### Description: Enter the LDAP super-admin password: # A password is used as initial password for the super-admin user of GOsa². # You can use your root password or type something else. Make sure you remember # the password. # . # Note that you will not be able to see the password as you type it. # d-i debian-edu-config/ldap-password password ### Description: Re-enter password to verify: # Please enter the same password again to verify that you have typed it # correctly. # d-i debian-edu-config/ldap-password-again password ### Description: for internal use: The username of the first user in LDAP: # This is the username of the administrative user created in LDAP on # the Main-Server # d-i debian-edu-config/first-user-name string ### Description: for internal use: The full name of the first user in LDAP: # This is the full name of the administrative user created in LDAP on # the Main-Server # d-i debian-edu-config/first-user-fullname string ### Description: for internal use: The password of the initial user: # This password is used as the initial password for the first user in # LDAP. You can use your root password or type something else. Make # sure you remember the password. # . # Note that you will not be able to see the password as you type it. # d-i debian-edu-config/first-user-password password ############################ #### debian-edu-install_2.12.10~deb12u1_all.deb ############################ ### Description: for internal use # Preseed this during installation to insert the firstboot init.d script # into the boot sequence. # d-i debian-edu-install/run-firstboot boolean false ############################ #### debian-edu-router-config_2.12.8~deb12u1_all.deb ############################ ### Description: Do you want to skip Debian Edu Router networking configuration? # ERROR: Not enough usable network interfaces available for setting up the # router! # d-i debian-edu-router-config/skip-networking-if-not-enough-ifaces-available boolean ### Description: Do you want to skip Debian Edu Router networking configuration? # ERROR: Not enough unconfigured network interfaces available for setting # up the router! # . # The following interfaces were found already configured in files not # managed by Debian Edu Router: # . # ${non_d_e_r_ifaces} # . # Please consider unconfiguring these interfaces and re-try again. # d-i debian-edu-router-config/skip-networking-if-not-enough-ifaces-non-configured boolean ### Description: Do you want to enable IP packet forwarding? # The routing part of 'Debian Edu Router' requires IP packets to be # forwarded back and forth between network interfaces by the kernel. This # is mandatory and without it the router simply won't work. If you select # 'Abort' this package will be left unconfigured. To undo its # half-installed state, remove/purge it again. # . # IPv4 / IPv6 forwarding will only be enabled if the specific IP protocol # version is configured and enabled. # d-i debian-edu-router-config/ip-forwarding-consent select # Possible choices: Yes, Abort ### Description: The network interface assignment method: # You need to assign this host's network interfaces to network types # supported by Debian Edu Router. The network interface assignments can be # done in three ways (plus a bail-out method). # . # (1) ALL-CONNECTED - All network interfaces are already connected and you # know which interface you want to use for what network type. # . # (2) STEP-BY-STEP - Connect and assign network interfaces one by one. # This will add dialogs between each interface assignment requesting to # connect the network cable of the to-be-assigned network interface. # . # (3) OFFLINE-SETUP - No network interface is currently connected, allow # configuration of network interfaces that currently don't have a network # carrier. You also know which interface you want to use for what network # type. # . # (4) SKIP-NETWORK-SETUP - Don't configure networking via this package, at # all. Skip network configuration. # d-i debian-edu-router-config/net-setup-mode select # Possible choices: ALL-CONNECTED - all network cables are already connected (I know what I am doing), STEP-BY-STEP - connect network cables step-by-step and automatically assign network interfaces this way, OFFLINE-SETUP - network cables are not connected (this is an offline installation\, and yes\, I know what I am doing), SKIP-NETWORK-SETUP - don't configure network interface assignments for now\, at all ### Description: Which NIC shall be used as the 'Uplink' network interface? # The following network interfaces on this system are connected to a # network. # . # ${extended} # d-i debian-edu-router-config/net-ext-iface-uplink select # Possible choices: ${choices} ### Description: Supported internal school networks types: # d-i debian-edu-router-config/net-int-supportednetworks multiselect # Possible choices: OpenLAN, Education, Mgmt, School-Administration, WiFi-Students, WiFi-Teachers, WiFi-Guests, Printers ### Description: Shall VLANs be used on the internal network? # d-i debian-edu-router-config/net-int-with-vlans boolean false ### Description: Which NIC shall be used as VLAN interface? # The following network interfaces on this system are connected to a # network. # . # ${extended} # d-i debian-edu-router-config/net-int-iface-vlan select # Possible choices: ${choices} ### Description: Supported network types provided as VLANs: # d-i debian-edu-router-config/net-int-supportednetworks-via-vlan multiselect # Possible choices: ${choices} ### Description: VLAN-ID for the 'OpenLAN' VLAN: # d-i debian-edu-router-config/net-int-vlanid-openlan string 1 ### Description: VLAN-ID for the 'Education' VLAN: # d-i debian-edu-router-config/net-int-vlanid-education string 2 ### Description: VLAN-ID for the 'Mgmt' VLAN: # d-i debian-edu-router-config/net-int-vlanid-mgmt string 3 ### Description: VLAN-ID for the 'School-Administration' VLAN: # d-i debian-edu-router-config/net-int-vlanid-schooladministration string 4 ### Description: VLAN-ID for the 'WiFi-Students' VLAN: # d-i debian-edu-router-config/net-int-vlanid-wifistudents string 21 ### Description: VLAN-ID for the 'WiFi-Teachers' VLAN: # d-i debian-edu-router-config/net-int-vlanid-wifiteachers string 22 ### Description: VLAN-ID for the 'WiFi-Guests' VLAN: # d-i debian-edu-router-config/net-int-vlanid-wifiguests string 24 ### Description: VLAN-ID for the 'Printers' VLAN: # d-i debian-edu-router-config/net-int-vlanid-printers string 40 ### Description: Physical NIC for the internal 'OpenLAN' network: # The following network interfaces on this system are connected to a # network. # . # ${extended} # d-i debian-edu-router-config/net-int-iface-openlan select # Possible choices: ${choices} ### Description: Physical NIC for the internal 'Education' network: # The following network interfaces on this system are connected to a # network. # . # ${extended} # d-i debian-edu-router-config/net-int-iface-education select # Possible choices: ${choices} ### Description: Physical NIC for the internal 'Mgmt' network: # The following network interfaces on this system are connected to a # network. # . # ${extended} # d-i debian-edu-router-config/net-int-iface-mgmt select # Possible choices: ${choices} ### Description: Physical NIC for the internal 'School-Administration' network: # The following network interfaces on this system are connected to a # network. # . # ${extended} # d-i debian-edu-router-config/net-int-iface-schooladministration select # Possible choices: ${choices} ### Description: Physical NIC for the internal 'WiFi-Students' network: # The following network interfaces on this system are connected to a # network. # . # ${extended} # d-i debian-edu-router-config/net-int-iface-wifistudents select # Possible choices: ${choices} ### Description: Physical NIC for the internal 'WiFi-Teachers' network: # The following network interfaces on this system are connected to a # network. # . # ${extended} # d-i debian-edu-router-config/net-int-iface-wifiteachers select # Possible choices: ${choices} ### Description: Physical NIC for the internal 'WiFi-Guests' network: # The following network interfaces on this system are connected to a # network. # . # ${extended} # d-i debian-edu-router-config/net-int-iface-wifiguests select # Possible choices: ${choices} ### Description: Physical NIC for the internal 'Printers' network: # The following network interfaces on this system are connected to a # network. # . # ${extended} # d-i debian-edu-router-config/net-int-iface-printers select # Possible choices: ${choices} ### Description: Which IP versions are to be supported during configuration of the networks? # . # Questions regarding a specific IP version won't be asked if its not # selected here. # d-i debian-edu-router-config/net-ip-versions-enabled multiselect IPv4 # Possible choices: IPv4, IPv6 ### Description: Networks for which this host will have a static IPv4 address: # d-i debian-edu-router-config/net-networks-staticip-v4 multiselect # Possible choices: ${choices} ### Description: Networks for which this host will have a static IPv6 address: # d-i debian-edu-router-config/net-networks-staticip-v6 multiselect # Possible choices: ${choices} ### Description: Networks for which this host's IPv4 address will be configured via DHCPv4: # d-i debian-edu-router-config/net-networks-dhcpclient-v4 multiselect # Possible choices: ${choices} ### Description: Networks for which this host's IPv6 address will be configured via RA: # d-i debian-edu-router-config/net-networks-auto-v6 multiselect # Possible choices: ${choices} ### Description: Networks with IPv6 parameters configured via DHCPv6: # d-i debian-edu-router-config/net-networks-dhcpclient-v6 multiselect # Possible choices: ${choices} ### Description: Networks for which this host will have no configured IPv4 address: # d-i debian-edu-router-config/net-networks-manual-v4 multiselect # Possible choices: ${choices} ### Description: Networks for which this host will have no configured IPv6 address: # d-i debian-edu-router-config/net-networks-manual-v6 multiselect # Possible choices: ${choices} ### Description: IPv4 address/netmask of the external 'Uplink' NIC: # An IPv4 address is mandatory for the static IP configuration of the # 'Uplink' interface. # . # Make sure to use proper IPv4 address/netmask syntax. # . # Examples: 192.168.1.1/24, 172.16.0.1/255.255.255.0 # d-i debian-edu-router-config/net-ext-address-v4-uplink string ### Description: IPv6 address/netmask of the external 'Uplink' NIC: # IPv6 support is optional. Please leave empty if you want to skip static # IPv6 address configuration on the 'Uplink' interface now and do this # later. # d-i debian-edu-router-config/net-ext-address-v6-uplink string ### Description: IPv4 address of the 'Uplink' network's gateway: # When configuring a static IPv4 address on the 'Uplink' network # interface, it is required to provide an IPv4 gateway address. The # gateway address needs to be reachable within the 'Uplink' network's IPv4 # subnet. # . # Make sure to use proper IPv4 address syntax. # . # Examples: 192.168.1.253, 172.16.0.254 # d-i debian-edu-router-config/net-ext-gateway-v4-uplink string ### Description: IPv6 address of the 'Uplink' network's gateway: # When configuring a static IPv6 address on the 'Uplink' network # interface, it is required to provide an IPv6 gateway address. The # gateway address needs to be reachable within the 'Uplink' network's IPv6 # subnet or via the interface's IPv6 link-local address. # . # Make sure to use proper IPv6 address syntax. # . # Examples: 2001:0425:2ca1::1, fe80::1 # d-i debian-edu-router-config/net-ext-gateway-v6-uplink string ### Description: Upstream DNS servers: # You can provide a list of explicit DNS upstream servers to be used by # this system. If you have configured your 'Uplink' network interface's IP # address(es) statically, providing at least one DNS server address here # will be mandatory. # . # If you use DHCPv4/DHCPv6 for 'Uplink' network interface configuration, # you may leave this empty. # . # If DNS upstream servers are provided here, they will also be used for # forwarding DNS queries to from the internal networks if selected so in a # later configuration query. # . # Make sure to use proper IPv4/IPv6 address syntax for DNS server # addresses. Mutiple IP addresses can be separated by blanks and/or # commas. Please note that /etc/resolv.conf only supports a maximum of # three nameserver entries. # . # Example: 192.168.1.253, 2001:0425:2ca1::1, fe80::1 # d-i debian-edu-router-config/net-ext-nameservers-uplink string ### Description: IPv4 address/netmask of the internal 'OpenLAN' NIC: # An IPv4 address is mandatory for the static IP configuration of the # 'OpenLAN' interface . # . # Make sure to use proper IPv4 address/netmask syntax. # . # Examples: 192.168.100.253/24, 192.168.100.253/255.255.255.0 # d-i debian-edu-router-config/net-int-address-v4-openlan string ### Description: IPv6 address/netmask of the internal 'OpenLAN' NIC: # IPv6 support is optional. Please leave empty if you want to skip static # IPv6 address configuration on the 'OpenLAN' interface now and do this # later. # . # Make sure to use proper IPv6 address/netmask syntax. # . # Example: 2345:0425:2ca1::0567:5673:23b5/64 # d-i debian-edu-router-config/net-int-address-v6-openlan string ### Description: IPv4 address/netmask of the internal 'Education' NIC: # An IPv4 address is mandatory for the static IP configuration of the # 'Education' interface . # . # Make sure to use proper IPv4 address/netmask syntax. # . # Examples: 10.0.0.1/8, 10.0.0.1/255.0.0.0 # d-i debian-edu-router-config/net-int-address-v4-education string ### Description: IPv6 address/netmask of the internal 'Education' NIC: # IPv6 support is optional. Please leave empty if you want to skip static # IPv6 address configuration on the 'Education' interface now and do this # later. # . # Make sure to use proper IPv6 address/netmask syntax. # . # Example: 2345:0425:2ca1::0567:5673:23b5/64 # d-i debian-edu-router-config/net-int-address-v6-education string ### Description: IPv4 address/netmask of the internal 'Mgmt' NIC: # An IPv4 address is mandatory for the static IP configuration of the # 'Mgmt' interface . # . # Make sure to use proper IPv4 address/netmask syntax. # . # Examples: 172.16.0.253/24, 172.16.0.253/255.255.255.0 # d-i debian-edu-router-config/net-int-address-v4-mgmt string ### Description: IPv6 address/netmask of the internal 'Mgmt' NIC: # IPv6 support is optional. Please leave empty if you want to skip static # IPv6 address configuration on the 'Mgmt' interface now and do this # later. # . # Make sure to use proper IPv6 address/netmask syntax. # . # Example: 2345:0425:2ca1::0567:5673:23b5/64 # d-i debian-edu-router-config/net-int-address-v6-mgmt string ### Description: IPv4 address/netmask of the internal 'School-Administration' NIC: # An IPv4 address is mandatory for the static IP configuration of the # 'School-Administration' interface . # . # Make sure to use proper IPv4 address/netmask syntax. # . # Examples: 172.16.8.253/24, 172.16.8.253/255.255.255.0 # d-i debian-edu-router-config/net-int-address-v4-schooladministration string ### Description: IPv6 address/netmask of the internal 'School-Administration' NIC: # IPv6 support is optional. Please leave empty if you want to skip static # IPv6 address configuration on the 'School-Administration' interface now # and do this later. # . # Make sure to use proper IPv6 address/netmask syntax. # . # Example: 2345:0425:2ca1::0567:5673:23b5/64 # d-i debian-edu-router-config/net-int-address-v6-schooladministration string ### Description: IPv4 address/netmask of the internal 'WiFi-Students' NIC: # An IPv4 address is mandatory for the static IP configuration of the # 'WiFi-Students' interface . # . # Make sure to use proper IPv4 address/netmask syntax. # . # Examples: 172.21.0.0/21, 172.21.0.0/255.255.248.0 # d-i debian-edu-router-config/net-int-address-v4-wifistudents string ### Description: IPv6 address/netmask of the internal 'WiFi-Students' NIC: # IPv6 support is optional. Please leave empty if you want to skip static # IPv6 address configuration on the 'WiFi-Students' interface now and do # this later. # . # Make sure to use proper IPv6 address/netmask syntax. # . # Example: 2345:0425:2ca1::0567:5673:23b5/64 # d-i debian-edu-router-config/net-int-address-v6-wifistudents string ### Description: IPv4 address/netmask of the internal 'WiFi-Teachers' NIC: # An IPv4 address is mandatory for the static IP configuration of the # 'WiFi-Teachers' interface . # . # Make sure to use proper IPv4 address/netmask syntax. # . # Examples: 172.21.8.0/21, 172.21.8.0/255.255.248.0 # d-i debian-edu-router-config/net-int-address-v4-wifiteachers string ### Description: IPv6 address/netmask of the internal 'WiFi-Teachers' NIC: # IPv6 support is optional. Please leave empty if you want to skip static # IPv6 address configuration on the 'WiFi-Teachers' interface now and do # this later. # . # Make sure to use proper IPv6 address/netmask syntax. # . # Example: 2345:0425:2ca1::0567:5673:23b5/64 # d-i debian-edu-router-config/net-int-address-v6-wifiteachers string ### Description: IPv4 address/netmask of the internal 'WiFi-Guests' NIC: # An IPv4 address is mandatory for the static IP configuration of the # 'WiFi-Guests' interface . # . # Make sure to use proper IPv4 address/netmask syntax. # . # Examples: 172.21.16.0/21, 172.21.16.0/255.255.248.0 # d-i debian-edu-router-config/net-int-address-v4-wifiguests string ### Description: IPv6 address/netmask of the internal 'WiFi-Guests' NIC: # IPv6 support is optional. Please leave empty if you want to skip static # IPv6 address configuration on the 'WiFi-Guests' interface now and do # this later. # . # Make sure to use proper IPv6 address/netmask syntax. # . # Example: 2345:0425:2ca1::0567:5673:23b5/64 # d-i debian-edu-router-config/net-int-address-v6-wifiguests string ### Description: IPv4 address/netmask of the internal 'Printers' NIC: # An IPv4 address is mandatory for the static IP configuration of the # 'Printers' interface . # . # Make sure to use proper IPv4 address/netmask syntax. # . # Examples: 172.16.1.253/24, 172.16.1.253/255.255.255.0 # d-i debian-edu-router-config/net-int-address-v4-printers string ### Description: IPv6 address/netmask of the internal 'Printers' NIC: # IPv6 support is optional. Please leave empty if you want to skip static # IPv6 address configuration on the 'Printers' interface now and do this # later. # . # Make sure to use proper IPv6 address/netmask syntax. # . # Example: 2345:0425:2ca1::0567:5673:23b5/64 # d-i debian-edu-router-config/net-int-address-v6-printers string ### Description: Networks that are NAT'ed (and hidden) behind the 'Uplink' address: # Computers on networks selected here will connect to the internet via # IPv4 and NAT (network address translation). Hosts on the internet will # only "see" this system's external IPv4 address, whereas individual # computers on the internal network stay "hidden". # d-i debian-edu-router-config/service-firewall-networks-nat multiselect # Possible choices: ${choices} ### Description: Networks that are directly routed into the 'Uplink' network: # Computers on networks selected here will be directly routed to the # 'Uplink' network via IPv4. Hosts on the 'Uplink' network will "see" each # individual computer on the internal network. # . # Important: When enabling routing of internal networks directly into the # internet, you must make sure that hosts on the internal networks will # get assigned publicly addressable IPv4 addresses. Otherwise, you'd need # another NAT gateway between this system's 'Uplink' network and the # internet. # d-i debian-edu-router-config/service-firewall-networks-routed multiselect # Possible choices: ${choices} ### Description: Networks that are host-only, i.e. neither routed nor NAT'ed: # d-i debian-edu-router-config/service-firewall-networks-hostonly multiselect # Possible choices: ${choices} ### Description: Networks that are allowed to access the internet, directly: # For computers on internal networks you can choose between two default # policies regarding internet access: all allowed and all blocked. # . # Networks selected here will be allowed to access the internet, directly. # Networks not selected here will be blocked from direct internet access. # . # For blocked internal networks, you will later be provided with a # configuration dialog that allows you to define host based and port based # exceptions from this default network rule. # d-i debian-edu-router-config/service-firewall-networks-allow-internet multiselect # Possible choices: ${choices} ### Description: Networks that are blocked from internet access: # d-i debian-edu-router-config/service-firewall-networks-block-internet multiselect # Possible choices: ${choices} ### Description: Trustworthy internal IPs and networks: # Internal addresses/networks which are declared trustworthy can directly # connect to the internet even if its network is configured to block # direct internet access. # . # The matching of addresses/networks to configured internal networks happens # automatically. # . # You can enter IPv4/IPv6 single addresses or entire networks using the # address/netmask CIDR syntax. # . # Example: 10.0.0.0/8 10.0.2.2 192.168.0.1/24 # 2345:0425:2ca1::0567:5673:23b5/64 fdce:4879:a1e9:e351:1a01:be9:4d9a:157d # d-i debian-edu-router-config/service-firewall-trustworthy-ips string ### Description: Reverse NAT configuration: # Syntax: [tcp:/udp:]:[:internal_port] # . # Here, you can configure services that shall be reachable from the # internet (via your 'Uplink' IPv4 address). Multiple configurations are # possible and should be seperated by spaces. # . # As make sure you only specify IPv4 addresses that # match any of the internal networks' IP subnet configurations. Also, you # can only reverse-NAT into an internal network if it has been configured # as a NAT network. # . # Providing the protocol (udp/tcp) is optional. If not provided, the setup # will default to tcp+udp. By prepending either 'udp:' or 'tcp:' one can # limit the reverse NAT to only one of the protocols. # . # Specifying the is also optional. It will be # automatically set to if empty. and # may differ. # d-i debian-edu-router-config/service-firewall-reverse-nat-configs string ### Description: Incoming SSH connections: # Internal/external network interfaces via which it is permitted to log # into this host via SSH. # . # If you are installing this device from remote, please make sure to # include the Uplink interface into the list of allowed network interfaces. # . # NOTE: To fully make incoming SSH connections operational, make sure the # SSH service is installed and enabled. # d-i debian-edu-router-config/service-firewall-ssh-incoming multiselect # Possible choices: ${choices} ### Description: Enable DHCPv4 service on this host for the following networks: # This host can act as DHCPv4 server for all or some of the enabled # internal networks. Please select for which internal network the DHCPv4 # service shall be enabled. # . # Note for Debian Edu system administrators: Don't enable DHCPv4 on the # Education network. DHCPv4 is normally provided by Debian Edu's main # server (aka TJENER). # d-i debian-edu-router-config/service-dhcp-networks-v4 multiselect # Possible choices: ${choices} ### Description: Enable DHCPv6 service on this host for the following networks: # This host can act as DHCPv6 network parameter server for all or some of # the enabled internal networks. Please select for which internal network # the DHCPv6 service shall be enabled. # . # Networks selected here will also be provided with IPv6 router # advertisement support via this host. # d-i debian-edu-router-config/service-dhcp-networks-v6 multiselect # Possible choices: ${choices} ### Description: Free IPv4 address leases offered by DHCP on network 'OpenLAN': # The DHCPv4 service offers IPv4 addresses to requesting DHCPv4 clients. # Provide a start address, an end address and a lease duration time in the # format shown in below example. # . # Leave empty for disabling support for free DHCPv4 leases. # . # Example: 192.168.100.20,192.168.100.252,12h # d-i debian-edu-router-config/service-dhcp-range-v4-openlan string ### Description: Free IPv4 address leases offered by DHCP on network 'Education': # The DHCPv4 service offers IPv4 addresses to requesting DHCPv4 clients. # Provide a start address, an end address and a lease duration time in the # format shown in below example. # . # Leave empty for disabling support for free DHCPv4 leases. # . # Example: 10.16.0.0,10.31.255.255,12h # d-i debian-edu-router-config/service-dhcp-range-v4-education string ### Description: Free IPv4 address leases offered by DHCP on network 'Mgmt': # The DHCPv4 service offers IPv4 addresses to requesting DHCPv4 clients. # Provide a start address, an end address and a lease duration time in the # format shown in below example. # . # Leave empty for disabling support for free DHCPv4 leases. # . # Example: 172.16.0.20,172.16.0.252,12h # d-i debian-edu-router-config/service-dhcp-range-v4-mgmt string ### Description: Free IPv4 addr. leases offered by DHCP on network 'School-Administration': # The DHCPv4 service offers IPv4 addresses to requesting DHCPv4 clients. # Provide a start address, an end address and a lease duration time in the # format shown in below example. # . # Leave empty for disabling support for free DHCPv4 leases. # . # Example: 172.16.8.20,172.16.8.252,12h # d-i debian-edu-router-config/service-dhcp-range-v4-schooladministration string ### Description: Free IPv4 address leases offered by DHCP on network 'WiFi-Students': # The DHCPv4 service offers IPv4 addresses to requesting DHCPv4 clients. # Provide a start address, an end address and a lease duration time in the # format shown in below example. # . # Leave empty for disabling support for free DHCPv4 leases. # . # Example: 172.21.0.2,172.21.7.254,12h # d-i debian-edu-router-config/service-dhcp-range-v4-wifistudents string ### Description: Free IPv4 address leases offered by DHCP on network 'WiFi-Teachers': # The DHCPv4 service offers IPv4 addresses to requesting DHCPv4 clients. # Provide a start address, an end address and a lease duration time in the # format shown in below example. # . # Leave empty for disabling support for free DHCPv4 leases. # . # Example: 172.21.8.2,172.21.15.254,12h # d-i debian-edu-router-config/service-dhcp-range-v4-wifiteachers string ### Description: Free IPv4 address leases offered by DHCP on network 'WiFi-Guests': # The DHCPv4 service offers IPv4 addresses to requesting DHCPv4 clients. # Provide a start address, an end address and a lease duration time in the # format shown in below example. # . # Leave empty for disabling support for free DHCPv4 leases. # . # Example: 172.21.16.2,172.21.23.254,12h # d-i debian-edu-router-config/service-dhcp-range-v4-wifiguests string ### Description: Free IPv4 address leases offered by DHCP on network 'Printers': # The DHCPv4 service offers IPv4 addresses to requesting DHCPv4 clients. # Provide a start address, an end address and a lease duration time in the # format shown in below example. # . # Leave empty for disabling support for free DHCPv4 leases. # . # Example: 172.16.1.21,172.16.1.80,12h # d-i debian-edu-router-config/service-dhcp-range-v4-printers string ### Description: Port for incomming SSH connections (empty if disabled): # The default port for incomming SSH connections is 22. # If you want to disable the sshd service entirely then enter 0 or just # leave the input field empty. # . # Please make sure you still have a way of accessing this machine, if # you are about to disable the SSH service. # d-i debian-edu-router-config/service-ssh-custom-port string 22 ############################ #### debian-installer-launcher_39_all.deb ############################ ############################ #### junior-config_1.30_all.deb ############################ ### Description: Debian Junior users: # Please select, among the whole system user list, users who should get # a Debian Junior user menu. # d-i junior-config/group multiselect # Possible choices: ${users} ### Description: Build user menus at: # The metapackages of the Debian Junior Debian Pure Blend # contain extra menus that will be auto generated from existing packages. # If the role based user menu option was choosen these menus will be built # when a user who is registered to a given role uses the "update-menus" # utility. This can be done automatically for all users who are registered # for Debian Junior after installation of each single metapackage, # at the end of the whole installation process to save time in case # of installing more than one metapackage or just leave the call of # "update-menus" to the users themselves. # * Each package installation : Call "update-menus" after each metapackage # (time consuming); # * End of installation : Call "update-menus" only once at the end of # the whole installation/upgrading process; # * Never : Do not call "update-menus" at all. # d-i shared/junior-config/usermenus select never # Possible choices: Each package installation, End of installation, Never ### Description: Do you want user menus? # The menus for the Debian Junior Debian Pure Blend could be # implemented as user menus which means they are visible only for those # users that will be selected explicitely. Be warned that selecting # the users from a large list does not scale very well so it makes no # real sense to activate this feature if there are more than 50 users # on this machine. # d-i shared/junior-config/useusermenus boolean ############################ #### med-config_3.8.1_all.deb ############################ ### Description: Debian Med users: # Please select, among the whole system user list, users who should get # a Debian Med user menu. # d-i med-config/group multiselect # Possible choices: ${users} ### Description: Build user menus at: # The metapackages of the Debian Med Debian Pure Blend # contain extra menus that will be auto generated from existing packages. # If the role based user menu option was chosen these menus will be built # when a user who is registered to a given role uses the "update-menus" # utility. This can be done automatically for all users who are registered # for Debian Med after installation of each single metapackage, # at the end of the whole installation process to save time in case # of installing more than one metapackage or just leave the call of # "update-menus" to the users themselves. # * Each package installation : Call "update-menus" after each metapackage # (time consuming); # * End of installation : Call "update-menus" only once at the end of # the whole installation/upgrading process; # * Never : Do not call "update-menus" at all. # d-i shared/med-config/usermenus select never # Possible choices: Each package installation, End of installation, Never ### Description: Do you want user menus? # The menus for the Debian Med Debian Pure Blend could be # implemented as user menus which means they are visible only for those # users that will be selected explicitly. Be warned that selecting # the users from a large list does not scale very well so it makes no # real sense to activate this feature if there are more than 50 users # on this machine. # d-i shared/med-config/useusermenus boolean ############################ #### pan-config_0.4_all.deb ############################ ### Description: PAN Blend users: # Please select, among the whole system user list, users who should get # a PAN Blend user menu. # d-i pan-config/group multiselect # Possible choices: ${users} ### Description: Build user menus at: # The metapackages of the PAN Blend Debian Pure Blend # contain extra menus that will be auto generated from existing packages. # If the role based user menu option was chosen these menus will be built # when a user who is registered to a given role uses the "update-menus" # utility. This can be done automatically for all users who are registered # for PAN Blend after installation of each single metapackage, # at the end of the whole installation process to save time in case # of installing more than one metapackage or just leave the call of # "update-menus" to the users themselves. # * Each package installation : Call "update-menus" after each metapackage # (time consuming); # * End of installation : Call "update-menus" only once at the end of # the whole installation/upgrading process; # * Never : Do not call "update-menus" at all. # d-i shared/pan-config/usermenus select never # Possible choices: Each package installation, End of installation, Never ### Description: Do you want user menus? # The menus for the PAN Blend Debian Pure Blend could be # implemented as user menus which means they are visible only for those # users that will be selected explicitly. Be warned that selecting # the users from a large list does not scale very well so it makes no # real sense to activate this feature if there are more than 50 users # on this machine. # d-i shared/pan-config/useusermenus boolean ############################ #### science-config_1.14.5_all.deb ############################ ### Description: Debian Science users: # Please select, among the whole system user list, users who should get # a Debian Science user menu. # d-i science-config/group multiselect # Possible choices: ${users} ### Description: Build user menus at: # The metapackages of the Debian Science Debian Pure Blend # contain extra menus that will be auto generated from existing packages. # If the role based user menu option was chosen these menus will be built # when a user who is registered to a given role uses the "update-menus" # utility. This can be done automatically for all users who are registered # for Debian Science after installation of each single metapackage, # at the end of the whole installation process to save time in case # of installing more than one metapackage or just leave the call of # "update-menus" to the users themselves. # * Each package installation : Call "update-menus" after each metapackage # (time consuming); # * End of installation : Call "update-menus" only once at the end of # the whole installation/upgrading process; # * Never : Do not call "update-menus" at all. # d-i shared/science-config/usermenus select never # Possible choices: Each package installation, End of installation, Never ### Description: Do you want user menus? # The menus for the Debian Science Debian Pure Blend could be # implemented as user menus which means they are visible only for those # users that will be selected explicitly. Be warned that selecting # the users from a large list does not scale very well so it makes no # real sense to activate this feature if there are more than 50 users # on this machine. # d-i shared/science-config/useusermenus boolean ############################ #### debian-security-support_12+2023.05.12_all.deb ############################ ############################ #### debsecan_0.4.20.1_all.deb ############################ ### Description: Do you want debsecan to send daily reports? # debsecan can check the security status of the host # once per day, and notify you of any changes by email. # . # If you choose this option, debsecan will download a small file # once a day. Your package list will not be transmitted to # the server. # d-i debsecan/report boolean true ### Description: Email address to which daily reports should be sent: # d-i debsecan/mailto string root ### Description: Main suite from which packages are installed: # To present more useful data, debsecan needs to know # the Debian release from which you usually install packages. # . # If you specify "GENERIC" (the default), only basic debsecan # functionality is available. If you specify the suite # matching your sources.list configuration, information about # fixed and obsolete packages will be included in email reports. # d-i debsecan/suite select GENERIC # Possible choices: GENERIC, jessie, stretch, buster, bullseye, sid ### Description: URL of vulnerability information: # debsecan fetches vulnerability information from the network. # If your system is not connected to the Internet, you can enter # the URL of a local mirror here. If you leave this option # empty, the built-in default URL is used. # d-i debsecan/source string ############################ #### designate-api_15.0.0-4_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i designate/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i designate/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i designate/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i designate/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i designate/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i designate/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i designate/api-endpoint-address string ### Description: This service endpoint protocol: # d-i designate/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i designate/api-endpoint-region-name string regionOne ############################ #### designate-common_15.0.0-4_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i designate/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i designate/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i designate/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i designate/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i designate/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i designate/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i designate/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i designate/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i designate/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i designate/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i designate/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i designate/ksat-admin-password password ### Description: Auth server service username: # d-i designate/ksat-service-username string ### Description: Auth server service project name: # d-i designate/ksat-service-project-name string service ### Description: Auth server service password: # d-i designate/ksat-service-password password ############################ #### dhis-client_5.5-6_amd64.deb ############################ ############################ #### dibbler-client_1.0.1-1.1_amd64.deb ############################ ### Description: Should the Dibbler client be launched when the system starts? # The Dibbler client can be configured to be launched when the system # is started. If you choose this option, this host will have a correct # IPv6 setup after booting. Please ensure that a DHCPv6 server is # available on the network. # d-i dibbler-client/start boolean true ### Description: Interfaces to be configured: # Dibbler can configure any or all of a computer's network interfaces. # . # More than one interface may be specified by separating the interface names # with spaces. # d-i dibbler-client/interfaces string eth0 ### Description: Additional parameters to obtain: # The Dibbler client can request that the DHCPv6 server supplies additional # configuration parameters. # d-i dibbler-client/options multiselect dns # Possible choices: dns, domain ############################ #### dibbler-relay_1.0.1-1.1_amd64.deb ############################ ### Description: Should the Dibbler relay be launched when the system starts? # The Dibbler relay can be configured to be launched when the system is # started. If you choose this option, this node will forward # DHCPv6 messages between clients, servers and other relays. # d-i dibbler-relay/start boolean true ############################ #### dibbler-server_1.0.1-1.1_amd64.deb ############################ ### Description: Should the Dibbler server be launched when the system starts? # The Dibbler server can be configured to be launched when the system # is started. If you choose this option, this node will act as a # DHCPv6 server. It will provide IPv6 addresses and additional # configuration options to other nodes in the network. # d-i dibbler-server/start boolean true ############################ #### dictd_1.13.0+dfsg-1_amd64.deb ############################ ### Description: Method for running dictd: # The dictd server can be run either as a stand-alone daemon or from inetd. You can also # disable it entirely. # . # It is recommended to run it as a daemon. # d-i dictd/run_mode select daemon # Possible choices: daemon, inetd, disabled ############################ #### dictionaries-common_1.29.5_all.deb ############################ ### Description: System default ispell dictionary: # Please indicate which dictionary ispell should use as system-wide # default when no other spell-checking dictionary is specified. # . # This sets up the /usr/lib/ispell/default.aff and # /usr/lib/ispell/default.hash symlinks, as well as ispell's global # ispell-wrapper and Emacs defaults. # . # Use "Manual symlink setting" if you want to handle the symlinks # yourself. In this case ispell will have no global ispell-wrapper or # Emacs defaults. # . # The default ispell dictionary can be changed at any time by running # "select-default-ispell". # d-i dictionaries-common/default-ispell select # Possible choices: ${echoices}, Manual symlink setting ### Description: System default wordlist: # Please indicate which wordlist the "/usr/share/dict/words" symlink # should point to. This will provide a simple list of dictionary words # for basic spell-checking and word searches. Use "Manual symlink # setting" if you want to handle this symlink yourself. # . # The default wordlist can be changed at any time by running # "select-default-wordlist". # d-i dictionaries-common/default-wordlist select # Possible choices: ${echoices}, Manual symlink setting ### Description: Remove obsolete /etc/dictionary link? # This system has an obsolete symlink "/etc/dictionary". This is no # longer meaningful, and should be removed. # . # You will be asked to explicitly select the default wordlist during # installation of wordlist packages. You can change your selection at any # time by running "select-default-wordlist". # d-i dictionaries-common/old_wordlist_link boolean true ############################ #### discover_2.1.2-10_amd64.deb ############################ ### Description: Packages to install: # Some packages were found to be useful with your hardware. # Please select those you want to install. # d-i discover/install_hw_packages multiselect # Possible choices: ${PACKAGES} ############################ #### dist_3.5-236-1_all.deb ############################ ### Description: Name of your organization: # You don't seem to have an /etc/news/organization file. Usually that # contains the name of your organization as you want it to appear on the # Organization line of outgoing articles/mail/patches. Please supply the # name of your organization as you want it to appear on the Organization # line of outgoing articles/patches. (It is nice if this also specifies # your location. Your city name is probably sufficient if well known.) For # example: # . # University of Southern North Dakota, Hoople # . # Type in "--none--" if you do not want to specify one. # d-i shared/news/organization string --none-- ############################ #### distcc_3.4+really3.4-3_amd64.deb ############################ ### Description: Start the distcc daemon on startup? # distcc can be run as a daemon, listening on port 3632 for incoming # connections. # . # You have the option of starting the distcc daemon automatically on the # computer startup. If in doubt, it's advised not to start it automatically # on startup. If you later change your mind, you can run: 'dpkg-reconfigure # distcc'. # d-i distcc/daemon boolean false ### Description: Allowed client networks: # The distcc daemon implements access control based on the IP address of the # client, that is trying to connect. Only the hosts or networks listed # here are allowed to connect. # . # You can list multiple hosts and/or networks, separated by spaces. Hosts are # represented by their IP address, networks have to be in CIDR notation, # e.g. "192.168.1.0/24". # . # To change the list at a later point, you can run: 'dpkg-reconfigure distcc'. # d-i distcc/daemon-allow string 127.0.0.1 ### Description: Listen interfaces: # The distcc daemon can be bound to a specific network interface. # . # You probably want to choose the interface of your local network by entering # its IP address. If distccd should listen on all interfaces, just enter # nothing. # . # Be sure to protect distccd from unauthorized access, by being careful in # your choice of the listen interface and allowed networks. distccd should # never be accessible from untrusted networks. If that is needed, secureshell # should be used instead of the daemon. # . # To change the address at a later point, you can run: 'dpkg-reconfigure distcc'. # d-i distcc/daemon-listen string 127.0.0.1 ### Description: Nice level: # You can start the distcc daemon with a nice level, to give it a low priority # compared to other processes. The start script will only accept values between # 0 and 20. # . # To change this value at a later point, you can run: 'dpkg-reconfigure distcc'. # d-i distcc/daemon-nice string 10 ### Description: Maximum number of concurrent jobs: # You can tell the distcc daemon to accept a maximum number of jobs at a time. # This can be useful on systems that should stay interactive while they serve # as a distcc server. Usually, you will want to set this to a value matching # or doubling the number of cores on this system. # . # To change this value at a later point, you can run: 'dpkg-reconfigure distcc'. # d-i distcc/daemon-jobs string ### Description: Enable Zeroconf support? # distcc has Zeroconf support. # . # If you enable it here, please read /usr/share/doc/distcc/README.Debian to # learn how clients must be configured to make use of it. Also note, that # you need to install the dbus package, if you're going to use Zeroconf. # . # To change this value at a later point, you can run: 'dpkg-reconfigure distcc'. # d-i distcc/daemon-zeroconf boolean false ############################ #### dma_0.13-1+b1_amd64.deb ############################ ### Description: System mail name: # The 'mail name' is the domain name used to 'qualify' mail addresses # without a domain name. # . # This name will also be used by other programs. It should be the # single, fully qualified domain name (FQDN). # . # Thus, if a mail address on the local host is foo@example.org, # the correct value for this option would be example.org. # d-i dma/mailname string ### Description: Smarthost: # Please enter the IP address or the host name of a mail server that # this system should use as outgoing smarthost. If no smarthost is # specified, dma will try to deliver all messages by itself. # d-i dma/relayhost string ############################ #### dokuwiki_0.0.20220731.a-2_all.deb ############################ ### Description: Web server(s) to configure automatically: # DokuWiki runs on any web server supporting PHP, but only listed # web servers can be configured automatically. # . # Please select the web server(s) that should be configured # automatically for DokuWiki. # d-i dokuwiki/system/configure-webserver multiselect apache2 # Possible choices: apache2, lighttpd ### Description: Should the web server(s) be restarted now? # In order to activate the new configuration, the reconfigured web # server(s) have to be restarted. # d-i dokuwiki/system/restart-webserver boolean true ### Description: Wiki location: # Specify the directory below the server's document root from which # DokuWiki should be accessible. # d-i dokuwiki/system/documentroot string /dokuwiki ### Description: Authorized network: # Wikis normally provide open access to their content, allowing anyone # to modify it. Alternatively, access can be restricted by IP address. # . # If you select "localhost only", only people on the local host (the machine # the wiki is running on) will be able to connect. "local network" will # allow people on machines in a local network (which you will need to # specify) to talk to the wiki. "global" will allow anyone, anywhere, to # connect to the wiki. # . # The default is for site security, but more permissive settings should # be safe unless you have a particular need for privacy. # d-i dokuwiki/system/accessible select localhost only # Possible choices: localhost only, local network, global ### Description: Local network: # The specification of your local network should either be # an IP network in CIDR format (x.x.x.x/y) or a domain specification (like # .example.com). # . # Anyone who matches this specification will be given full and complete # access to DokuWiki's content. # d-i dokuwiki/system/localnet string 10.0.0.0/24 ### Description: Purge pages on package removal? # By default, DokuWiki stores all its pages in a file database in # /var/lib/dokuwiki. # . # Accepting this option will leave you with a tidier system when the # DokuWiki package is removed, but may cause information loss if you have an # operational wiki that gets removed. # d-i dokuwiki/system/purgepages boolean false ### Description: Make the configuration web-writeable? # DokuWiki includes a web-based configuration interface. To be usable, it # requires the web server to have write permission to the configuration # directory. # . # Accepting this option will give the web server write permissions on the # configuration directory and files. # . # The configuration files will still be readable and editable by hand # regardless of whether or not you accept this option. # d-i dokuwiki/system/writeconf boolean false ### Description: Make the plugins directory web-writeable? # DokuWiki includes a web-based plugin installation interface. To be usable, # it requires the web server to have write permission to the plugins directory. # . # Accepting this option will give the web server write permissions to the # plugins directory. # . # Plugins can still be installed by hand regardless of whether or not you # accept this option. # d-i dokuwiki/system/writeplugins boolean false ### Description: Wiki title: # The wiki title will be displayed in the upper right corner of the default # template and on the browser window title. # d-i dokuwiki/wiki/title string Debian DokuWiki ### Description: Wiki license: # Please choose the license you want to apply to your wiki content. If none of # these licenses suits your needs, you will be able to add your own to the file # /etc/dokuwiki/license.php and to refer it in the main configuration file # /etc/dokuwiki/local.php when the installation is finished. # . # Creative Commons "No Rights Reserved" is designed to waive as many rights as # legally possible. # . # CC Attribution is a permissive license that only requires licensees to # give credit to the author. # . # CC Attribution-ShareAlike and GNU Free Documentation License are # copyleft-based free licenses (requiring modifications to be released under # similar terms). # . # CC Attribution-NonCommercial and CC Attribution-Noncommercial-ShareAlike # are non-free licenses, in that they forbid commercial use. # d-i dokuwiki/wiki/license select cc-by-sa # Possible choices: CC0 "No Rights Reserved", CC Attribution, CC Attribution-ShareAlike, GNU Free Documentation Licence, CC Attribution-NonCommercial, CC Attribution-NonCommercial-ShareAlike ### Description: Enable ACL? # Enable this to use an Access Control List for restricting what the users of # your wiki may do. # . # This is a recommended setting because without ACL support you will not have # access to the administration features of DokuWiki. # d-i dokuwiki/wiki/acl boolean true ### Description: Administrator username: # Please enter a name for the administrator account, which will be able to # manage DokuWiki's configuration and create new wiki users. The username # should be composed of lowercase ASCII letters only. # . # If this field is left blank, no administrator account will be created now. # d-i dokuwiki/wiki/superuser string admin ### Description: Administrator real name: # Please enter the full name associated with the wiki administrator account. # This name will be stored in the wiki password file as an informative # field, and will be displayed with the wiki page changes made by the # administrator account. # d-i dokuwiki/wiki/fullname string DokuWiki Administrator ### Description: Administrator email address: # Please enter the email address associated with the wiki administrator account. # This address will be stored in the wiki password file, and may be used # to get a new administrator password if you lose the original. # d-i dokuwiki/wiki/email string webmaster@localhost ### Description: Administrator password: # Please choose a password for the wiki administrator. # d-i dokuwiki/wiki/password password ### Description: Re-enter password to verify: # Please enter the same "admin" password again to verify # you have typed it correctly. # d-i dokuwiki/wiki/confirm password ### Description: Initial ACL policy: # Please select what initial ACL configuration should be set up to match # the intended usage of this wiki: # "open": both readable and writeable for anonymous users; # "public": readable for anonymous users, writeable for registered users; # "closed": readable and writeable for registered users only. # . # This is only an initial setup; you will be able to adjust the ACL rules later. # d-i dokuwiki/wiki/policy select public # Possible choices: open, public, closed ############################ #### idanish_1.6.36-14_all.deb ############################ ############################ #### wdanish_1.6.36-14_all.deb ############################ ############################ #### dump1090-mutability_1.15~20180310.4a16df3+dfsg-8.1_amd64.deb ############################ ### Description: Start dump1090 automatically? # dump1090 can be started automatically via an init-script. # Otherwise, the init-script does nothing; you must run dump1090 by hand. # . # You can modify the options used when automatically starting # dump1090 by running "dpkg-reconfigure dump1090-mutability" as root, # or by editing /etc/default/dump1090-mutability. # d-i dump1090-mutability/auto-start boolean true ### Description: User to run dump1090 as: # When started automatically, dump1090 runs as an unprivileged system user. # This user will be created if it does not yet exist. # d-i dump1090-mutability/run-as-user string dump1090 ### Description: Path to log to: # When started automatically, dump1090 will log its output somewhere. This # log will contain any startup errors, and periodic statistics reports. # d-i dump1090-mutability/log-file string /var/log/dump1090-mutability.log ### Description: RTL-SDR dongle to use: # If you have only one dongle connected, you can leave this blank. # . # Otherwise, you can provide the serial number (more reliable) or device # index (first device = 0, but the ordering is unpredictable) to choose # a particular dongle to use. # . # To run dump1090 in "net only" mode, specify the literal word "none". # d-i dump1090-mutability/rtlsdr-device string ### Description: RTL-SDR gain, in dB: # The tuner gain used by dump1090 can be provided as a value in dB, or # "max" to use the maximum gain available, or "agc" to use the tuner's AGC to # control the gain. If unsure, choose "max". # d-i dump1090-mutability/rtlsdr-gain string max ### Description: RTL-SDR frequency correction, in PPM: # The oscillator in each RTL-SDL dongle is not perfectly accurate. You can # choose a correction factor, in parts-per-million, to correct for this. The # correction factor varies from dongle to dongle, and also varies with operating # temperature. You can find a suitable value with "rtl_test -p" or "kalibrate". # If you don't know the value for your dongle, choose 0. # d-i dump1090-mutability/rtlsdr-ppm string 0 ### Description: Fix detected CRC errors? # dump1090 can fix unambiguous single-bit CRC errors detected in received # messages. This allows weaker messages to be decoded. It can slightly increase # the rate of undetected errors, but this is not usually significant. # d-i dump1090-mutability/decode-fixcrc boolean true ### Description: Latitude of receiver, in decimal degrees: # If the location of the receiver is provided, dump1090 can do # local position decoding in cases where insufficient position messages are # received for unambiguous global position decoding. # d-i dump1090-mutability/decode-lat string ### Description: Longitude of receiver, in decimal degrees: # If the location of the receiver is provided, dump1090 can do # local position decoding in cases where insufficient position messages are # received for unambiguous global position decoding. # d-i dump1090-mutability/decode-lon string ### Description: Absolute maximum range of receiver, in nautical miles: # If the maximum range of the receiver is provided, dump1090 can filter # out impossible position reports that are due to aircraft that transmit # bad data. # . # Additionally, if the maximum range is larger than 180NM, when local # position decoding is used (when insufficient position messages # have been received for global position decoding), it is limited to # only those positions that would unambiguously decode to a single # position within the given receiver range. # . # This range should be the absolute maximum range - any position data # from further away will be entirely discarded! # d-i dump1090-mutability/decode-max-range string 300 ### Description: Portsfor AVR-format input connections (0 disables): # dump1090 can accept connections to receive data from other sources in # several formats. This setting controls the port dump1090 will listen # on for AVR ("raw") format input connections. # d-i dump1090-mutability/net-ri-port string 30001 ### Description: Ports for AVR-format output connections (0 disables): # dump1090 can forward ADS-B messages to other software in several formats. # This setting controls the port dump1090 will listen on for AVR ("raw") # format output connections. # d-i dump1090-mutability/net-ro-port string 30002 ### Description: Ports for Beast-format input connections (0 disables): # dump1090 can accept connections to receive data from other sources in # several formats. This setting controls the port dump1090 will listen # on for Beast ("binary") format input connections. # d-i dump1090-mutability/net-bi-port string 30004,30104 ### Description: Ports for Beast-format output connections (0 disables): # dump1090 can forward ADS-B messages to other software in several formats. # This setting controls the port dump1090 will listen on for Beast ("binary") # format output connections. # d-i dump1090-mutability/net-bo-port string 30005 ### Description: Ports for SBS-format output connections (0 disables): # dump1090 can forward ADS-B messages to other software in several formats. # This setting controls the port dump1090 will listen on for SBS BaseStation # format output connections. # d-i dump1090-mutability/net-sbs-port string 30003 ### Description: Seconds between heartbeat messages (0 disables): # If there is no other data sent on a network connection, dump1090 can # periodically send an empty heartbeat message to ensure that the # connection stays established. This setting controls the interval # betweeen heartbeat messages. # d-i dump1090-mutability/net-heartbeat string 60 ### Description: Minimum output message size: # To avoid sending many small network messages, output connections will # accumulate data waiting to be sent until either a minimum size is reached # or a maximum delay is reached. This setting controls the minimum size, # in bytes. # d-i dump1090-mutability/net-out-size string 500 ### Description: Maximum output buffering time: # To avoid sending many small network messages, output connections will # buffer data waiting to be sent until either a minimum size is reached # or a maximum delay is reached. This setting controls the maximum delay, # in seconds. # d-i dump1090-mutability/net-out-interval string 1 ### Description: SO_SNDBUF size: # Here you can specify the TCP send buffer size to use on network connections. # d-i dump1090-mutability/net-buffer select 262144 # Possible choices: 65536, 131072, 262144 ### Description: Interface address to bind to (blank for all interfaces): # If you want to limit incoming connections to a particular interface, # specify the interface address here. A blank value will bind to the wildcard # address, allowing connections on all interfaces. # . # The default value of 127.0.0.1 will allow connections only on localhost, # i.e. only connections that originate on the same machine. # d-i dump1090-mutability/net-bind-address string 127.0.0.1 ### Description: Interval between logging stats, in seconds: # dump1090 will periodically log message reception stats to its logfile. # This setting controls how often that is done. # d-i dump1090-mutability/stats-interval string 3600 ### Description: Enable the lighttpd integration? # dump1090 can serve a virtual radar map via a separate webserver. # This package includes a configuration for lighttpd that does this. # To use that configuration, enable this option. # d-i dump1090-mutability/use-lighttpd boolean true ### Description: Directory to write JSON aircraft state to: # As this can be written frequently, you should select a location # that is not on a sdcard. The default path under /run is on tmpfs # and will not write to the sdcard. # . # A blank path disables writing JSON state. This will also disable # the virtual radar map. # d-i dump1090-mutability/json-dir string /run/dump1090-mutability ### Description: Interval between writing JSON aircraft state, in seconds: # dump1090 periodically write a list of aircraft, in JSON format, for use # by the virtual radar view when using an external webserver. This setting # controls the directory to write to. # . # Here you can control how often the JSON state is updated, which determines # how frequently the virtual radar view updates. # d-i dump1090-mutability/json-interval string 1 ### Description: Receiver location accuracy to show in the web interface: # dump1090 can provide the configured receiver location to the web map, # so that the map can show distances from the receiver. # . # For privacy reasons, if you are making the map publicly available you # may not want to show the exact location of the receiver. There are three # options available to control what is shown: # . # approximate: dump1090 will provide the receiver location rounded to the # nearest 0.01 degree of latitude and longitude. This gives a location # that is accurate to within about 0.5 - 1km. # . # exact: dump1090 will provide the exact receiver location. # . # none: dump1090 will not provide the receiver location at all; distance # display will be disabled. # d-i dump1090-mutability/json-location-accuracy select approximate # Possible choices: approximate, exact, none ### Description: Log all decoded messages? # dump1090 can log all decoded messages as text to the logfile. # This can result in a very large logfile! Usually you don't need this. # d-i dump1090-mutability/log-decoded-messages boolean false ### Description: Extra arguments to pass to dump1090: # Here you can add any extra arguments you want to pass to dump1090. # d-i dump1090-mutability/extra-args string ############################ #### durep_0.9-3.1_all.deb ############################ ### Description: HTTP directory for supplementary files: # If this package shall provide disk usage information through a HTTP # CGI-service, it needs a public web directory containing additional files like # style sheet and images. This directory should be visible as '/durep' on the # web site where the durep.cgi page is located. # . # Due to FHS policy these files are not automatically installed to system # directories. To make them accessible, they can either be copied into a # location inside the HTTP root directory, or the web server needs to be # configured accordingly. # . # To configure the Apache webserver (for example), the following directive # creates the needed directory alias: # . # Alias /durep /usr/share/durep/www # . # To install supplementary files into another root directory please specify its # path here. The directory must already exist. A typical answer would be # '/var/www'. The subdirectory '/durep' with files will be created # automatically, the files will be installed from '/usr/share/durep/www' unless # they already exist. # d-i durep/httpfileroot string ### Description: Do you want to enable daily report generation? # If you wish, a daily script will create disk usage statistics of chosen # filesystems. They will be kept for seven days. # . # WARNING: with the default configuration, the statistics are stored in the # public httpd directory, /var/www/durep. This may breach the privacy of the # users. # d-i durep/makereports boolean false ### Description: List of filesystems for durep reports: # To specify single filesystems to report on, enter their mount points # separated by spaces (eg. "/data /var"). A single dot (".") means scanning # of the whole UNIX filesystem tree. # d-i durep/filesystems string . ############################ #### idutch_2.20.19-2_all.deb ############################ ############################ #### wdutch_2.20.19-2_all.deb ############################ ############################ #### dvi2ps_5.1j-1.5_amd64.deb ############################ ############################ #### dwww_1.15_amd64.deb ############################ ### Description: Location of web server's document root: # dwww needs to know the path of the directory which contains your web server's # document root. The web standard suggests /var/www. # d-i dwww/docrootdir string /var/www ### Description: Location of web server's cgi directory: # dwww needs to know the path of the directory which contains your web server's # CGI scripts. The web standard suggests /usr/lib/cgi-bin, but your web server # may already be configured for a different location. # d-i dwww/cgidir string /usr/lib/cgi-bin ### Description: Name of CGI user: # dwww needs to know what user will be running the dwww CGI script, as the cache # directory must be owned by that user. # d-i dwww/cgiuser string www-data ### Description: Host name of the web server: # dwww needs to know the host name of your web server. # d-i dwww/servername string localhost ### Description: Web server's port: # dwww needs to know what port your web server is running on. Normally web # servers run on port 80. # d-i dwww/serverport string 80 ### Description: Should post-installation script index your documentation files? # dwww-index++(8) program will be run once a week to index your documentation files # registered with doc-base package. # . # The index can also be generated (in the background) by the post-installation script. # This process needs quite a lot of computer resources, and can take several minutes # so you can choose now if you would like to do this. # d-i dwww/index_docs boolean false ############################ #### efingerd_1.6.7-1+b1_amd64.deb ############################ ### Description: Permit users to have their own configurable finger replies? # You can decide if efingerd honours users' ~/.efingerd files. # . # If someone from network fingers given user, and the user has ~/.efingerd # file readable and executable for efingerd daemon, this file will be # executed and its output will be sent to the fingerer. # . # This can be either desired or not, depending on your system policy. In # particular, allowing .efingerd files allows users to cheat about their # real identity. However, efingerd can be configured to display users' full # names (from passwd) as the first line of the reply, so they cannot hide # themselves completely. # . # There is however a slight security concern: if you allow .efingerd files, # these files will be executed under efingerd UID, so malicious users gain # access to all files owned by efingerd - this becomes important when you # make efingerd to log into some files writable by the daemon, unless you # take appropriate precautions. # . # If you are the only user, or you trust your users, there is no reason to # disable .efingerd files (and this is probably a reason you want to install # efingerd for). However, if you expect your users to be nasty, you should # better think about protecting from them - in particular, if you enable # logging, make sure they cannot fiddle with the logfile - this is UP TO # YOU. # d-i efingerd/allow_files boolean true ### Description: Display users' real names? # By default, efingerd displays users real names (from passwd) as the first # line of finger reply. You may want to suppress it, but if you allow the # use of .efingerd files at the same time, be aware that users can hide # their identity for the fingerer. # . # If in doubt, select this option. # d-i efingerd/show_names boolean true ############################ #### ejabberd_23.01-1_amd64.deb ############################ ### Description: Hostname for this Jabber server: # Please enter a hostname for this Jabber server. # . # If you would like to configure multiple hostnames for this server, you will # have to do so manually in /etc/ejabberd/ejabberd.yml after installation. # d-i ejabberd/hostname string localhost ### Description: Jabber server administrator username: # Please provide the name of an account to administrate the ejabberd server. # After the installation of ejabberd, you can log in to this account using # either any Jabber client or a web browser pointed at the administrative # https://${hostname}:5280/admin/ interface. # . # You only need to enter the username part here (such as ${user}), but # the full Jabber ID (such as ${user}@${hostname}) is required to # access the ejabberd web interface. # . # Please leave this field empty if you don't want to create an # administrator account automatically. # d-i ejabberd/user string ### Description: Jabber server administrator password: # Please enter the password for the administrative user. # d-i ejabberd/password password ### Description: Re-enter password to verify: # Please enter the same administrator password again to verify that you have typed it # correctly. # d-i ejabberd/verify password ### Description: ERL_OPTIONS for this ejabberd server: # To run the ejabberd server with customized Erlang options, enter them here. # It is also possible to set them by editing /etc/ejabberd/ejabberdctl.cfg. # See the erl(1) man page for more information. # d-i ejabberd/erlangopts string -env ERL_CRASH_DUMP_BYTES 0 ############################ #### libdebuginfod-common_0.188-2.1_all.deb ############################ ### Description: Connect to Debian's debuginfod server to download debug symbols? # While debugging programs (with GDB, for example) or using # debuginfo-consumer applications, it is possible to connect to # Debian's debuginfod server and download the necessary debug # information for the program you are debugging on-the-fly, without the # need to configure the debian-debug apt repository nor installing # any dbgsym packages. This service is maintained by Debian, and the # only information you will have to send to it is the Build-ID hash of # the program(s)/library(ies) being debugged. # d-i libdebuginfod/usedebiandebuginfod boolean false ############################ #### emacspeak_53.0+dfsg-2_all.deb ############################ ### Description: for internal use # This template is never shown to the user and does not require # translation. # d-i shared/emacspeak/fake select # Possible choices: ${choices} ### Description: Default speech server: # The /etc/emacspeak.conf file will be configured so that the command # '/usr/bin/emacspeak' will start Emacs with emacspeak support using # this server. # . # You may change the selection later by running # 'dpkg-reconfigure emacspeak' as root, or temporarily override the # selection by setting the environment variable DTK_PROGRAM. # d-i shared/emacspeak/device select espeak # Possible choices: ${choices} ### Description: Hardware port of the speech generation device: # If a hardware device is used to generate speech, please enter the # Unix device file associated with it, such as '/dev/ttyS0' or # '/dev/ttyUSB0'. # . # If you use a software method to generate speech, please enter 'none'. # d-i shared/emacspeak/port string none ### Description: Users of speech server: # Users must be members of group ${group} to access the speech server # connected to ${port}. Please review the space-separated list of # current members of that group, and add or remove usernames if needed. # . # If you later add users to the system, you can either reconfigure # the emacspeak package afterwards, or enroll the user in ${group} # with 'adduser ${group} '. # . # Group membership is checked at login time, so new members must log # out and log in again before using the speech server. # d-i shared/emacspeak/groupies string ### Description: for internal use # This template is never shown to the user and does not require # translation. This variable holds the path to the speech server, # relative to /usr/share//site-lisp/emacspeak/servers. # d-i shared/emacspeak/program string ### Description: for internal use # This template is never shown to the user and does not require # translation. This variable holds the path to the interpreter if any # used to run the speech server. # d-i shared/emacspeak/tcl string ### Description: for internal use # This template is never shown to the user and does not require # translation. This variable holds all the available choices for # speech servers, and the corresponding values of "program", "tcl", and # "device" for the above variables. # d-i shared/emacspeak/database select # Possible choices: ${choices} ############################ #### emacspeak-ss_1.12.1-9_amd64.deb ############################ ### Description: for internal use # This template is never shown to the user and does not require # translation. # d-i shared/emacspeak/fake select # Possible choices: ${choices} ### Description: Default speech server: # The /etc/emacspeak.conf file will be configured so that the command # '/usr/bin/emacspeak' will start Emacs with emacspeak support using # this server. # . # You may change the selection later by running # 'dpkg-reconfigure emacspeak' as root, or temporarily override the # selection by setting the environment variable DTK_PROGRAM. # d-i shared/emacspeak/device select DECtalk Express # Possible choices: ${choices} ### Description: Hardware port of the speech generation device: # If a hardware device is used to generate speech, please enter the # Unix device file associated with it, such as '/dev/ttyS0' or # '/dev/ttyUSB0'. # . # If you use a software method to generate speech, please enter 'none'. # d-i shared/emacspeak/port string none ### Description: Users of speech server: # Users must be members of group ${group} to access the speech server # connected to ${port}. Please review the space-separated list of # current members of that group, and add or remove usernames if needed. # . # If you later add users to the system, you can either reconfigure # the emacspeak package afterwards, or enroll the user in ${group} # with 'adduser ${group} '. # . # Group membership is checked at login time, so new members must log # out and log in again before using the speech server. # d-i shared/emacspeak/groupies string ### Description: for internal use # This template is never shown to the user and does not require # translation. This variable holds the path to the speech server, # relative to /usr/share//site-lisp/emacspeak/servers. # d-i shared/emacspeak/program string ### Description: for internal use # This template is never shown to the user and does not require # translation. This variable holds the path to the interpreter if any # used to run the speech server. # d-i shared/emacspeak/tcl string ### Description: for internal use # This template is never shown to the user and does not require # translation. This variable holds all the available choices for # speech servers, and the corresponding values of "program", "tcl", and # "device" for the above variables. # d-i shared/emacspeak/database select # Possible choices: ${choices} ############################ #### email-reminder_0.8.2-2_all.deb ############################ ### Description: Run daily email-reminder cronjob? # By default, email-reminder checks once a day for reminders that need # to be sent out. # d-i email-reminder/send_reminders boolean true ### Description: SMTP server: # Specify the address of the outgoing mail server that email-reminder # should use to send its emails. # d-i email-reminder/smtp_server string localhost ### Description: SMTP username: # If the outgoing mail server requires a username, enter it here. # . # Leave this blank if the SMTP server doesn't require authentication. # d-i email-reminder/smtp_username string ### Description: SMTP password: # If the outgoing mail server requires a password, enter it here. # . # Leave this blank if the SMTP server doesn't require authentication. # d-i email-reminder/smtp_password password ### Description: Connect to the SMTP server using SSL? # If the SMTP server supports SSL and you choose this option, data # exchanged with it will be encrypted. # d-i email-reminder/smtp_ssl boolean false ### Description: Reminder mails originating address: # Reminder emails will appear to come from this address. The default # should work unless the SMTP server requires routable domains in # source addresses. # d-i email-reminder/mail_from string root@localhost ############################ #### encfs_1.9.5-2_amd64.deb ############################ ############################ #### iesperanto_2.1.2000.02.25-61_all.deb ############################ ############################ #### wesperanto_2.1.2000.02.25-61_all.deb ############################ ############################ #### esmtp_1.2-18+b1_amd64.deb ############################ ### Description: Automatically overwrite configuration files? # The mail configuration file /etc/esmtprc can be automatically updated on # each upgrade with the information supplied to the debconf database. If you # do not want this to happen (i.e., you want to maintain control of this file # yourself) then unset this option to prevent the program touching this file. # d-i esmtp/overwriteconfig boolean false ### Description: SMTP server hostname: # d-i esmtp/hostname string localdomain ### Description: SMTP server port number: # d-i esmtp/hostport string 25 ### Description: Authentication username: # This is the username to be given to the mailhub if authentication is # required by the SMTP server. # . # Do NOT set the username and password on the system configuration file # unless you are the sole user of this machine. Esmtp is not run with suid # privileges therefore the system configuration file must be readable by # everyone. If your SMTP server requires authorization and you are not the # only user then accept the default options in the system configuration file # for local delivery and specify your personal SMTP account details in the # user configuration file. # d-i esmtp/username string ### Description: Authentication password: # This is the password to be given to the mailhub if authentication is # required by the SMTP server. # d-i esmtp/password password ### Description: Whether to use the Starttls extension # d-i esmtp/starttls select disabled # Possible choices: enabled, disabled, required ### Description: Certificate passphrase: # This is the certificate passphrase for the StartTLS extension. # d-i esmtp/certificate_passphrase password ### Description: Mail Delivery Agent # This is the Mail Delivery Agent used for local mail delivery. # d-i esmtp/mda select # Possible choices: none, procmail, maildrop ############################ #### ispanish_1.11-20_all.deb ############################ ############################ #### etckeeper_1.18.20-1_all.deb ############################ ### Description: Remove etckeeper ${VCS} repository and associated files? # Etckeeper is being purged from the system, and was used to # store /etc in a ${VCS} repository. If you choose to remove the # repository, this will DESTROY all history etckeeper has recorded # for /etc. # d-i etckeeper/purge boolean true ############################ #### eviacam_2.1.4-2.1_amd64.deb ############################ ### Description: Should eviacamloader be installed "setuid root"? # Installing eviacamloader with the set-user-ID bit set enables all # users who have been added to the group "eviacam" to launch eviacam # with a modified scheduling priority for better responsiveness. # . # Since this setting allows eviacamloader to be run with superuser # privileges, it may have security implications in the case of # vulnerabilities in eviacamloader's code. # d-i eviacamloader/eviacamloader_setuid boolean false ############################ #### exim4_4.96-15+deb12u4_all.deb ############################ ############################ #### exim4-base_4.96-15+deb12u4_amd64.deb ############################ ### Description: Remove undelivered messages in spool directory? # There are e-mail messages in the Exim spool directory # /var/spool/exim4/input/ which have not yet been delivered. Removing # Exim will cause them to remain undelivered until Exim is re-installed. # . # If this option is not chosen, the spool directory is kept, allowing # the messages in the queue to be delivered at a later date after # Exim is re-installed. # d-i exim4/purge_spool boolean false ############################ #### exim4-config_4.96-15+deb12u4_all.deb ############################ ### Description: General type of mail configuration: # Please select the mail server configuration type that best meets your needs. # . # Systems with dynamic IP addresses, including dialup systems, should generally # be configured to send outgoing mail to another machine, called a 'smarthost' # for delivery because many receiving systems on the Internet block # incoming mail from dynamic IP addresses as spam protection. # . # A system with a dynamic IP address can receive its own mail, or local # delivery can be disabled entirely (except mail for root and postmaster). # d-i exim4/dc_eximconfig_configtype select local delivery only; not on a network # Possible choices: internet site; mail is sent and received directly using SMTP, mail sent by smarthost; received via SMTP or fetchmail, mail sent by smarthost; no local mail, local delivery only; not on a network, no configuration at this time ### Description: Really leave the mail system unconfigured? # Until the mail system is configured, it will be broken and cannot be # used. Configuration at a later time can be done either by hand or by # running 'dpkg-reconfigure exim4-config' as root. # d-i exim4/no_config boolean true ### Description: System mail name: # The 'mail name' is the domain name used to 'qualify' mail addresses # without a domain name. # . # This name will also be used by other programs. It should be the # single, fully qualified domain name (FQDN). # . # Thus, if a mail address on the local host is foo@example.org, # the correct value for this option would be example.org. # . # This name won't appear on From: lines of outgoing messages if rewriting # is enabled. # d-i exim4/mailname string ### Description: Other destinations for which mail is accepted: # Please enter a semicolon-separated list of recipient domains for # which this machine should consider itself the final destination. # These domains are commonly called 'local domains'. The local hostname # (${fqdn}) and 'localhost' are always added to the list given here. # . # By default all local domains will be treated identically. If both # a.example and b.example are local domains, acc@a.example and # acc@b.example will be delivered to the same final destination. If # different domain names should be treated differently, it is # necessary to edit the config files afterwards. # d-i exim4/dc_other_hostnames string ### Description: Domains to relay mail for: # Please enter a semicolon-separated list of recipient domains for # which this system will relay mail, for example as a fallback MX or # mail gateway. This means that this system will accept mail for these # domains from anywhere on the Internet and deliver them according to # local delivery rules. # . # Do not mention local domains here. Wildcards may be used. # d-i exim4/dc_relay_domains string ### Description: Machines to relay mail for: # Please enter a semicolon-separated list of IP address ranges for # which this system will unconditionally relay mail, functioning as a # smarthost. # . # You should use the standard address/prefix format (e.g. 194.222.242.0/24 # or 5f03:1200:836f::/48). # . # If this system should not be a smarthost for any other host, leave # this list blank. # d-i exim4/dc_relay_nets string ### Description: Visible domain name for local users: # The option to hide the local mail name in outgoing mail was enabled. # It is therefore necessary to specify the domain name this system # should use for the domain part of local users' sender addresses. # d-i exim4/dc_readhost string ### Description: IP address or host name of the outgoing smarthost: # Please enter the IP address or the host name of a mail server that # this system should use as outgoing smarthost. If the smarthost only # accepts your mail on a port different from TCP/25, append two colons # and the port number (for example smarthost.example::587 or # 192.168.254.254::2525). Colons in IPv6 addresses need to be doubled. # . # If the smarthost requires authentication, please refer to # the Debian-specific README files in /usr/share/doc/exim4-base for # notes about setting up SMTP authentication. # d-i exim4/dc_smarthost string ### Description: Root and postmaster mail recipient: # Mail for the 'postmaster', 'root', and other system accounts needs to # be redirected to the user account of the actual system administrator. # . # If this value is left empty, such mail will be saved in /var/mail/mail, # which is not recommended. # . # Note that postmaster's mail should be read on the system to which it is # directed, rather than being forwarded elsewhere, so (at least one of) # the users listed here should not redirect their mail off this machine. # A 'real-' prefix can be used to force local delivery. # . # Multiple user names need to be separated by spaces. # d-i exim4/dc_postmaster string ### Description: IP-addresses to listen on for incoming SMTP connections: # Please enter a semicolon-separated list of IP addresses. The Exim SMTP # listener daemon will listen on all IP addresses listed here. # . # An empty value will cause Exim to listen for connections on all # available network interfaces. # . # If this system only receives mail directly from local services # (and not from other hosts), it is suggested to prohibit external # connections to the local Exim daemon. Such services include e-mail # programs (MUAs) which talk to localhost only as well as fetchmail. # External connections are impossible when 127.0.0.1 is entered here, # as this will disable listening on public network interfaces. # d-i exim4/dc_local_interfaces string notset ### Description: Keep number of DNS-queries minimal (Dial-on-Demand)? # In normal mode of operation Exim does DNS lookups at startup, and when # receiving or delivering messages. This is for logging purposes and # allows keeping down the number of hard-coded values in the # configuration. # . # If this system does not have a DNS full service resolver available at # all times (for example if its Internet access is a dial-up line using # dial-on-demand), this might have unwanted consequences. For example, # starting up Exim or running the queue (even with no messages waiting) # might trigger a costly dial-up-event. # . # This option should be selected if this system is using Dial-on-Demand. # If it has always-on Internet access, this option should be disabled. # d-i exim4/dc_minimaldns boolean false ### Description: Split configuration into small files? # The Debian exim4 packages can either use 'unsplit configuration', a # single monolithic file (/etc/exim4/exim4.conf.template) or 'split # configuration', where the actual Exim configuration files are built # from about 50 smaller files in /etc/exim4/conf.d/. # . # Unsplit configuration is better suited for large modifications and is # generally more stable, whereas split configuration offers a comfortable # way to make smaller modifications but is more fragile and might break # if modified carelessly. # . # A more detailed discussion of split and unsplit configuration can be # found in the Debian-specific README files in /usr/share/doc/exim4-base. # d-i exim4/use_split_config boolean ### Description: Hide local mail name in outgoing mail? # The headers of outgoing mail can be rewritten to make it appear to have been # generated on a different system. If this option is chosen, # '${mailname}', 'localhost' and '${dc_other_hostnames}' in From, Reply-To, # Sender and Return-Path are rewritten. # d-i exim4/hide_mailname boolean ### Description: Delivery method for local mail: # Exim is able to store locally delivered email in different formats. # The most commonly used ones are mbox and Maildir. mbox uses a single # file for the complete mail folder stored in /var/mail/. With Maildir # format every single message is stored in a separate file in ~/Maildir/. # . # Please note that most mail tools in Debian expect the local delivery # method to be mbox in their default. # d-i exim4/dc_localdelivery select mbox format in /var/mail/ # Possible choices: mbox format in /var/mail/, Maildir format in home directory ############################ #### exim4-daemon-heavy_4.96-15+deb12u4_amd64.deb ############################ ############################ #### exim4-daemon-light_4.96-15+deb12u4_amd64.deb ############################ ############################ #### expeyes-web_5.3.0+repack-3_all.deb ############################ ### Description: List of web servers to reconfigure automatically: # Expeyes-Web currently supports Apache2. # . # If no web service is installed, choose "none". # d-i expeyes-web/reconfigure-webserver select apache2 # Possible choices: apache2, none ### Description: This should be the URL of the Expeyes service: # Choose some fully qualified domain name, and make sure that this name # will be resolved by DNS servers to your server's IP address. # d-i expeyes-web/expeyes-site string expeyes.example.com ### Description: This should be the URL reachable by the "Home" link: # The main page featured by the Expeyes service has a few active buttons # in its top. The "Home" button can be a link to a schools welcome page. # . # Choose some fully qualified domain name, and make sure that this name # will be resolved by DNS servers to your school server's IP address. # d-i expeyes-web/school-site string school.example.com ############################ #### fdutils_5.6-4_amd64.deb ############################ ### Description: Should fdmount be installed 'setuid root'? # In order to enable ordinary users to mount a floppy disk, # the fdmount program can be installed with the set-user-ID bit set, so # that it will run with the permissions of the superuser. # . # Such a setting may have security implications in the case of # vulnerabilities in fdmount's code. # d-i fdutils/fdmount_setuid boolean false ############################ #### ferm_2.5.1-1.1_all.deb ############################ ### Description: Enable ferm on bootup? # Ferm can load firewall rules on every bootup from /etc/ferm/ferm.conf. # . # The default configuration allows SSH login on port 22; if you are # installing this package remotely on another port, you should not # choose this option, and later edit /etc/default/ferm to enable ferm. # d-i ferm/enable boolean true ############################ #### firebird3.0-server_3.0.11.33637.ds4-2+b1_amd64.deb ############################ ### Description: Password for SYSDBA: # Firebird has a special user named SYSDBA, which is the user that has # access to all databases. SYSDBA can also create new databases and users. # Because of this, it is necessary to secure SYSDBA with a password. # . # The password is stored in /etc/firebird/${FB_VER}/SYSDBA.password # (readable only by root). You may modify it there (don't forget to update # the security database too, using the gsec utility), or you may use # dpkg-reconfigure to update both. # . # If you don't enter a password, a random one will be used (and stored in # SYSDBA.password). # d-i shared/firebird/sysdba_password/first_install password ### Description: Password for SYSDBA: # Firebird has a special user named SYSDBA, which is the user that has # access to all databases. SYSDBA can also create new databases and users. # Because of this, it is necessary to secure SYSDBA with a password. # . # The password is stored in /etc/firebird/${FB_VER}/SYSDBA.password # (readable only by root). You may modify it there (don't forget to update # the security database too, using the gsec utility), or you may use # dpkg-reconfigure to update both. # . # To keep your existing password, leave this blank. # d-i shared/firebird/sysdba_password/upgrade_reconfigure password ### Description: New password for SYSDBA (for internal use) # *DO NOT TRANSLATE* # This is an internal, hidden template # d-i shared/firebird/sysdba_password/new_password password ############################ #### libfltk1.1-dev_1.1.10-30_amd64.deb ############################ ### Description: Make .h links to ? # For compatibility with some older code, FLTK used to make its C++-specific # headers available as as well as . However, the # lowercase-h names are deprecated and should be eliminated from # source code. # . # Please choose whether such compatibility symlinks should be created. # d-i libfltk1.1-dev/header-links boolean false ############################ #### fontconfig-config_2.14.1-4_amd64.deb ############################ ### Description: Font tuning method for screen (system default): # Please select the preferred method for tuning fonts for screen rendering. # . # Select 'Native' if you mostly use DejaVu (the default in Debian) or # any of the Microsoft fonts. Select 'Autohinter' if you mostly use other # TrueType fonts. Select 'None' if you want blurry text. # d-i fontconfig/hinting_type select Native # Possible choices: Native, Autohinter, None ### Description: Automatic font hinting style: # Please select the preferred automatic font hinting style to be used as # the system default. # . # The hinting style is the amount of font reshaping done to line up to the grid. # "Slight" will make the font more fuzzy to line up to the grid but will be better # in retaining font shape, while "Full" will be a crisp font that aligns well to # the pixel grid but will lose a greater amount of font shape. "Slight" is the # default setting. # . # To revert to the pre-2.12 behavior, select "Full". # d-i fontconfig/hinting_style select hintslight # Possible choices: None, Slight, Medium, Full ### Description: Enable subpixel rendering for screen: # Rendering text at a subpixel level generally makes it look a bit better # on flat (LCD) screens, but can show color artifacts on CRT screens. The # "Automatic" choice will enable it only if a LCD screen is detected. # d-i fontconfig/subpixel_rendering select Automatic # Possible choices: Automatic, Always, Never ### Description: Enable bitmapped fonts by default? # By default, only outline fonts are used by applications which support # fontconfig. # . # Outline fonts are fonts which scale well to various sizes. In # contrast, bitmapped fonts are often lower quality. Enabling this # option will affect the systemwide default; this and many other # fontconfig options may be enabled or disabled on a per-user basis. # d-i fontconfig/enable_bitmaps boolean false ############################ #### foomatic-filters_4.0.17-16_amd64.deb ############################ ### Description: Enable logging debug output into a log file (INSECURE)? # If you choose this option, the log file will be named /tmp/foomatic-rip.log. # . # This option is a potential security issue and should not be used # in production. However, if you are having trouble printing, you should # enable it and include the log file in bug reports. # d-i foomatic-filters/filter_debug boolean false ### Description: Command for converting text files to PostScript: # If you select 'Automagic', Foomatic will search for one of a2ps, # mpage, and enscript (in that order) each time the filter script is executed. # . # Please make sure that the selected command is actually available; otherwise # print jobs may get lost. # . # This setting is ignored when foomatic-filters is used with CUPS; # instead, the texttops program included in the cups package is # always used to convert jobs submitted as plain text to PostScript for # printing to raster devices. # d-i foomatic-filters/textfilter select Automagic # Possible choices: Automagic, a2ps, mpage, enscript, Custom ### Description: Command to convert standard input to PostScript: # Please enter the full command line of a command that converts text from # standard input to PostScript on standard output. # . # Please note that entering an invalid command line here may result in lost # print jobs. # d-i foomatic-filters/custom_textfilter string ### Description: Enable PostScript accounting for CUPS? # You should choose this option if you want to insert PostScript code # for accounting into each print job. This is currently only useful # with CUPS. # d-i foomatic-filters/ps_accounting boolean true ### Description: Printer spooler backend for Foomatic: # Foomatic normally requires a printer spooler (like CUPS or LPRng) to # handle communication with the printer and manage print jobs. If # no spooler is installed, you can use the 'direct' backend, but # this is only recommended for single-user systems. # . # The installation process may have already detected the correct # spooler; however, if this is the initial installation of this system, # or if more than one spooler is installed, # the detected spooler may be incorrect. # d-i foomatic-filters/spooler select direct # Possible choices: cups, lpd, lprng, pdq, ppr, direct ### Description: (for internal use only) # d-i foomatic-filters/config_parsed boolean false ############################ #### fortunes-de_0.35-1_all.deb ############################ ### Description: Fortunes to use: # You can choose fortunes packages to be used by fortune. # . # If you later change your mind, you can run: 'dpkg-reconfigure # ${pkg}'. # d-i fortunes-de/fortunes_to_install multiselect Anekdoten, ASCIIart, Bahnhof, Bauernregeln, Computer, Debian Tips, Elefanten, Fußball, Gedichte, Holenlassen, Huhn, Kinder, Letzte Worte, Lieber als, Löwe, Mathematiker, MS, Murphy, Namen, Quiz, Sicherheitshinweise, Sprichworte, Sprüche, Stilblüten, Tips, Translations, Unfug, Vornamen, Warmduscher, Witze, Wörterbuch, Wußten Sie, Zitate # Possible choices: Anekdoten, ASCIIart, Bahnhof, Bauernregeln, Channel Debian, Computer, Debian Tips, Elefanten, Fußball, Gedichte, Holenlassen, Huhn, Infodrom, Kinder, Letzte Worte, Lieber als, Linuxtag, Löwe, Mathematiker, MS, Murphy, Namen, Rezepte, Quiz, Sicherheitshinweise, Sprichworte, Sprüche, Stilblüten, Tips, Translations, Unfug, Vornamen, Warmduscher, Witze, Wörterbuch, Wußten Sie, Zitate ############################ #### fp-compiler-3.2.2_3.2.2+dfsg-20_amd64.deb ############################ ### Description: Rename "/etc/fpc.cfg" to "/etc/fpc.cfg.bak"? # FPC now supports having multiple versions installed on the same system. # The update-alternatives command can be used to set a default version for # * fpc (the compiler); # * fpc.cfg (the configuration file); # * fp-utils (the helper tools). # . # Whatever version you may choose as default, the configuration files are # always backward compatible, so it should always be safe to use the latest # version. # . # In order to use the alternatives system on the system wide FPC configuration # file you must accept renaming "/etc/fpc.cfg"; otherwise you will need to # manage this manually by yourself. # d-i fp-compiler/rename_cfg boolean true ### Description: Default MS Windows .rc resource compiler: # FPC supports compiling programs that embed resources as MS Windows # .rc-format files on all platforms where the MinGW windres tool is available. # . # In order to be able to compile projects using .rc files, you need first to # manually install the package mingw32-binutils. mingw32-binutils is suggested # by fp-compiler but not pulled in automatically. # . # If you want to enter a custom .rc file compiler that does not appear in this # list or if you simply want to disable this feature, please select # "Select manually". # d-i fp-compiler/windres-select select Select manually # Possible choices: ${choices}, Select manually ### Description: Default MS Windows .rc resource compiler: # FPC supports compiling programs that embed resources as MS Windows # .rc-format files on all platforms where the MinGW windres tool is available. # . # In order to be able to compile projects using .rc files, you need first to # manually install the package mingw32-binutils. mingw32-binutils is suggested # by fp-compiler but not pulled in automatically. # . # If you don't want to use a default .rc file compiler, leave this blank. # d-i fp-compiler/windres string ############################ #### fprobe_1.1-8_amd64.deb ############################ ### Description: Interface to capture: # fprobe will listen on this interface and send the traffic to the collector. # d-i fprobe/interface string eth0 ### Description: Collector address: # Please enter the collector's IP address and port number, separated by a colon. # d-i fprobe/collector string localhost:555 ############################ #### freedombox_23.6.2+deb12u1_all.deb ############################ ############################ #### tdsodbc_1.3.17+ds-2_amd64.deb ############################ ### Description: Do you want FreeTDS to be registered as an ODBC driver? # You appear to have an ODBC manager (unixodbc or iODBC) installed on your # system. FreeTDS now provides an Open Database Connectivity driver that # can be registered with the manager using the /usr/bin/odbcinst utility. # . # If you wish, FreeTDS will be automatically added as an ODBC driver now and # will be automatically deleted from the list when you remove the freetds # package. # d-i freetds/addtoodbc boolean true ############################ #### freezer-scheduler_13.0.0-2_all.deb ############################ ### Description: Manage freezer-scheduler config through debconf? # Freezer-scheduler service must contact Freezer-api, and this is configured through # the [DEFAULT] section of the configuration. Specify if you wish # to handle this configuration through debconf. # d-i freezer-scheduler/configure boolean false ### Description: Freezer-api server region name: # Freezer-scheduler needs to be able to communicate with Freezer-api through Keystone. Therefore # Freezer-scheduler needs to know the freezer tenant name, username, password and region. # d-i freezer-scheduler/region string regionOne ### Description: Keystone endpoint version: # d-i freezer-scheduler/api-version select 3 # Possible choices: 2, 3 ### Description: Auth server endpoint URL: # Specify the URL of your Keystone authentication server endpoint. This # value will be set in os_auth_url. # d-i freezer-scheduler/auth-url string http://localhost:5000/v3 ### Description: Freezer api backup endpoint URL: # Specify the URL of your Freezer-api endpoint. This # value will be set in backup_url. # d-i freezer-scheduler/backup-url string http://localhost:9090 ### Description: Auth server username: # d-i freezer-scheduler/ksat-username string user ### Description: Auth server project name: # d-i freezer-scheduler/ksat-project-name string project ### Description: Auth server password: # d-i freezer-scheduler/ksat-password password ############################ #### freezer-api_13.0.0-2_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i freezer-api/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i freezer-api/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i freezer-api/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i freezer-api/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i freezer-api/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i freezer-api/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i freezer-api/api-endpoint-address string ### Description: This service endpoint protocol: # d-i freezer-api/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i freezer-api/api-endpoint-region-name string regionOne ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i freezer-api/configure_db boolean false ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i freezer-api/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i freezer-api/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i freezer-api/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i freezer-api/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i freezer-api/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i freezer-api/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i freezer-api/ksat-admin-password password ### Description: Auth server service username: # d-i freezer-api/ksat-service-username string ### Description: Auth server service project name: # d-i freezer-api/ksat-service-project-name string service ### Description: Auth server service password: # d-i freezer-api/ksat-service-password password ############################ #### fwanalog_0.6.9-10_all.deb ############################ ### Description: Output language: # Please select the language you would like the reports to be generated in. # If you want your own custom language, please look in # /usr/share/doc/fwanalog/support - there are a few scripts to convert # analog .lng files to other languages. If you make a custom # translation, please submit it to the author. # d-i fwanalog/language select English # Possible choices: English, German, French, Italian ### Description: Do you wish to run fwanalog from cron daily ? # Enabling this option a daily cron-job will be set up to start fwanalog, # thereby producing fresh reports every day. # d-i fwanalog/cron boolean true ### Description: User who will receive the report via e-mail: # Enter the email-address of the person who should receive the log created # by the cron-job. Just enter a blank line, and no mail will be sent. # d-i fwanalog/mailto string root ############################ #### fwlogwatch_1.4-4_amd64.deb ############################ ### Description: Would you like fwlogwatch as a daemon (realtime mode)? # Running fwlogwatch as a daemon will let fwlogwatch act (i.e. adding new # firewall rules) against active 'attacks', or warn you (i.e. sending email) # about them. It could also run a web server to access fwlogwatch's current # status. # d-i fwlogwatch/realtime boolean false ### Description: Add new firewall rules (or take another action) in case of alert? # Don't use this option unless you know what you're doing. Doing so could # expose your system to a Denial of Service attack. i.e. spoofed packets # could be made to look like coming from your DNS. Adding a rule to block # packets from your DNS won't be good ;-) # . # In case of choosing 'other', you'll have to edit # '/etc/fwlogwatch/fwlw_respond' to meet your requirements. # d-i fwlogwatch/respond select no # Possible choices: no, yes (iptables), yes (ipchains), yes (other) ### Description: Send alerts by mail or other ways? # This option will make fwlogwatch send you alerts by email or other ways. # You may wish to adjust 'alert_threshold' in # '/etc/fwlogwatch/fwlogwatch.config' to avoid getting too many warnings. # . # In case of choosing 'other', you'll have to edit # '/etc/fwlogwatch/fwlw_notify' to meet your requirements. # d-i fwlogwatch/notify select no # Possible choices: no, yes (mail), yes (other) ### Description: Email address to send the alerts to: # d-i fwlogwatch/email string root@localhost ### Description: Email address to send daily reports on firewall events: # If you want a daily cron job to send you an email with a report of the # day's log entries, just type the address where you want the email to be # sent. # . # If you don't want these emails, just set the field to 'none' (without # quotes). # d-i fwlogwatch/cron_email string none ### Description: fwlogwatch parameters to use in the cron job: # If you do not know what these mean, it's safe to leave the defaults. # d-i fwlogwatch/cron_parameters string -p -d -O ta -t -e -l 1d ### Description: Rebuild configuration file from debconf's values? # d-i fwlogwatch/buildconfig boolean true ############################ #### fwsnort_1.6.8-1_all.deb ############################ ### Description: Download the rules? # The latest Snort rules can be downloaded from http://www.emergingthreats.net # in order to keep fwsnort up-to-date. # d-i fwsnort/download boolean false ############################ #### ganeti-3.0_3.0.2-3_all.deb ############################ ### Description: Abort ${package} removal? # You are attempting to remove ${package}, but it seems that the running Ganeti # version is still ${version}. # . # This can happen if you upgrade the ganeti package to a new minor version, but # have not run "gnt-cluster upgrade" yet. Removing ${package} will cause Ganeti to # stop functioning correctly. # . # It is highly recommended to abort the removal now and upgrade the cluster before # removing ${package}. # d-i ganeti-3.0/abort-removal boolean true ############################ #### ganeti-haskell-3.0_3.0.2-3_amd64.deb ############################ ### Description: Abort ${package} removal? # You are attempting to remove ${package}, but it seems that the running Ganeti # version is still ${version}. # . # This can happen if you upgrade the ganeti package to a new minor version, but # have not run "gnt-cluster upgrade" yet. Removing ${package} will cause Ganeti to # stop functioning correctly. # . # It is highly recommended to abort the removal now and upgrade the cluster before # removing ${package}. # d-i ganeti-haskell-3.0/abort-removal boolean true ############################ #### ganeti-htools-3.0_3.0.2-3_amd64.deb ############################ ### Description: Abort ${package} removal? # You are attempting to remove ${package}, but it seems that the running Ganeti # version is still ${version}. # . # This can happen if you upgrade the ganeti package to a new minor version, but # have not run "gnt-cluster upgrade" yet. Removing ${package} will cause Ganeti to # stop functioning correctly. # . # It is highly recommended to abort the removal now and upgrade the cluster before # removing ${package}. # d-i ganeti-htools-3.0/abort-removal boolean true ############################ #### gcl_2.6.14-4_amd64.deb ############################ ### Description: Use the work-in-progress ANSI build by default? # GCL is in the process of providing an ANSI compliant image in addition to # its traditional CLtL1 image still in production use. # . # Please see the README.Debian file for a brief description of these terms. # Choosing this option will determine which image will be used by default # when executing 'gcl'. # . # This setting may be overridden by setting the GCL_ANSI # environment variable to any non-empty string for the ANSI build, and to # the empty string for the CLtL1 build, e.g. GCL_ANSI=t gcl. The # currently enforced build flavor will be reported in the initial startup # banner. # d-i gcl/default_gcl_ansi boolean ### Description: Use the profiling build by default? # GCL has optional support for profiling via gprof. # . # Please see the documentation for si::gprof-start and si::gprof-quit # for details. As this build is slower than builds without gprof # support, it is not recommended for final production use. # . # Set the GCL_PROF environment variable to the empty string for more # optimized builds, or any non-empty string for profiling support; e.g. # GCL_PROF=t gcl. If profiling is enabled, this will be reported # in the initial startup banner. # d-i gcl/default_gcl_prof boolean ############################ #### gdm3_43.0-3_amd64.deb ############################ ### Description: for internal use only # d-i gdm3/daemon_name string /usr/sbin/gdm3 ### Description: Default display manager: # A display manager is a program that provides graphical login capabilities for # the X Window System. # . # Only one display manager can manage a given X server, but multiple display # manager packages are installed. Please select which display manager should # run by default. # . # Multiple display managers can run simultaneously if they are configured to # manage different servers; to achieve this, configure the display managers # accordingly, edit each of their init scripts in /etc/init.d, and disable the # check for a default display manager. # d-i shared/default-x-display-manager select # Possible choices: ${choices} ############################ #### gitolite3_3.6.12-1_all.deb ############################ ### Description: System username for gitolite: # Please enter the name for the system user which should be used by # gitolite to access repositories. It will be created if necessary. # d-i gitolite3/gituser string gitolite3 ### Description: Repository path: # Please enter the path in which gitolite should store the repositories. # This will become the gitolite system user's home directory. # d-i gitolite3/gitdir string /var/lib/gitolite3 ### Description: Administrator's SSH key: # Please specify the key of the user that will administer the access # configuration of gitolite. # . # This can be either the SSH public key itself, or the path to a file # containing it. If it is blank, gitolite will be left unconfigured and # must be set up manually. # . # If migrating from gitolite version 2.x, leave this blank. # d-i gitolite3/adminkey string ############################ #### glance-api_25.1.0-2_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i glance/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i glance/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i glance/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i glance/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i glance/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i glance/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i glance/api-endpoint-address string ### Description: This service endpoint protocol: # d-i glance/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i glance/api-endpoint-region-name string regionOne ############################ #### glance-common_25.1.0-2_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i glance/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i glance/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i glance/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i glance/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i glance/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i glance/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i glance/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i glance/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i glance/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i glance/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i glance/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i glance/ksat-admin-password password ### Description: Auth server service username: # d-i glance/ksat-service-username string ### Description: Auth server service project name: # d-i glance/ksat-service-project-name string service ### Description: Auth server service password: # d-i glance/ksat-service-password password ############################ #### glewlwyd_2.7.5-3_amd64.deb ############################ ### Description: Glewlwyd setup # You can configure it later if needed # d-i glewlwyd/config_type select Personalized # Possible choices: Personalized, No configuration ### Description: External address to access Glewlwyd: # d-i glewlwyd/config_external_url string http://localhost:4593/ ############################ #### libc6_2.36-9+deb12u4_amd64.deb ############################ ### Description: Do you want to upgrade glibc now? # Running services and programs that are using NSS need to be restarted, # otherwise they might not be able to do lookup or authentication any more. # The installation process is able to restart some services (such as ssh or # telnetd), but other programs cannot be restarted automatically. One such # program that needs manual stopping and restart after the glibc upgrade by # yourself is xdm - because automatic restart might disconnect your active # X11 sessions. # . # This script detected the following installed services which must be # stopped before the upgrade: ${services} # . # If you want to interrupt the upgrade now and continue later, please # answer No to the question below. # d-i glibc/upgrade boolean true ### Description: Services to restart for GNU libc library upgrade: # Running services and programs that are using NSS need to be restarted, # otherwise they might not be able to do lookup or authentication any more # (for services such as ssh, this can affect your ability to login). # Please review the following space-separated list of init.d scripts for # services to be restarted now, and correct it if needed. # . # Note: restarting sshd/telnetd should not affect any existing connections. # d-i glibc/restart-services string ### Description: Restart services during package upgrades without asking? # There are services installed on your system which need to be restarted # when certain libraries, such as libpam, libc, and libssl, are upgraded. # Since these restarts may cause interruptions of service for the system, # you will normally be prompted on each upgrade for the list of services # you wish to restart. You can choose this option to avoid being prompted; # instead, all necessary restarts will be done for you automatically so you # can avoid being asked questions on each library upgrade. # d-i libraries/restart-without-asking boolean false ############################ #### locales_2.36-9+deb12u4_all.deb ############################ ### Description: Locales to be generated: # Locales are a framework to switch between multiple languages and # allow users to use their language, country, characters, collation # order, etc. # . # Please choose which locales to generate. UTF-8 locales should be # chosen by default, particularly for new installations. Other # character sets may be useful for backwards compatibility with older # systems and software. # d-i locales/locales_to_be_generated multiselect # Possible choices: All locales, ${locales} ### Description: Default locale for the system environment: # Many packages in Debian use locales to display text in the correct # language for the user. You can choose a default locale for the system # from the generated locales. # . # This will select the default language for the entire system. If this # system is a multi-user system where not all users are able to speak # the default language, they will experience difficulties. # d-i locales/default_environment_locale select None # Possible choices: None, C.UTF-8, ${locales} ############################ #### libglide3_2002.04.10ds1-21_amd64.deb ############################ ### Description: Manually select driver for 3Dfx card? # No 3Dfx card that is supported by glide3 was found. This package # supports cards based on the following 3Dfx chipsets: Voodoo # Banshee, Voodoo 3, Voodoo 4, and Voodoo 5. # . # If the graphics card in this computer does not use one of these # chipsets, and you are not compiling programs against glide, # this package will not be useful. # . # If the graphics card is based on one of these chipsets, you # should file a bug report against this package, including the output from the # "lspci -vm" command. # . # Please choose whether you want to manually select the driver to use for now. # d-i libglide3/no_card boolean false ### Description: Driver for 3D acceleration: # Please select the driver you would like to use for 3D acceleration: # * h3: Voodoo Banshee and Voodoo 3; # * h5: Voodoo 4 and Voodoo 5. # d-i libglide3/driver select ${default} # Possible choices: h3, h5 ### Description: Card to use for 3D acceleration: # Multiple 3Dfx-based cards were detected based on one of the # following 3Dfx chipsets: Voodoo 2, Voodoo Banshee, Voodoo 3, Voodoo 4, and Voodoo 5. # . # Please select the card you would like to use for 3D acceleration. # d-i libglide3/card select # Possible choices: ${choices} ############################ #### gnarwl_3.6.dfsg-13+b1_amd64.deb ############################ ### Description: Name/address of the LDAP server: # Gnarwl contacts a LDAP server in order to get information about # vacation messages and accounts. Please specify the server, # optionally with the port to be used. # . # Example: ldap.yourdomain.local:389 # d-i gnarwl/server string ### Description: Base DN of the LDAP server: # In order to access the LDAP server, please specify the base gnarwl # should use for LDAP queries. # . # Example: dc=yourdomain,dc=somewhere # d-i gnarwl/base string ############################ #### gnocchi-api_4.4.2-2_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i gnocchi/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i gnocchi/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i gnocchi/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i gnocchi/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i gnocchi/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i gnocchi/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i gnocchi/api-endpoint-address string ### Description: This service endpoint protocol: # d-i gnocchi/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i gnocchi/api-endpoint-region-name string regionOne ############################ #### gnocchi-common_4.4.2-2_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i gnocchi/configure_db boolean false ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i gnocchi/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i gnocchi/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i gnocchi/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i gnocchi/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i gnocchi/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i gnocchi/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i gnocchi/ksat-admin-password password ### Description: Auth server service username: # d-i gnocchi/ksat-service-username string ### Description: Auth server service project name: # d-i gnocchi/ksat-service-project-name string service ### Description: Auth server service password: # d-i gnocchi/ksat-service-password password ############################ #### gnubg_1.07.001-1+b1_amd64.deb ############################ ### Description: Build bearoff database? # For maximum strength, GNU Backgammon needs a two-sided bearoff database, # used to evaluate positions in the end-game. This database takes up # 6.6MB of disk space and requires several minutes to generate on a # reasonably fast computer. GNU Backgammon is fully playable without this # database, but will use weaker heuristics for the end of the game. # d-i gnubg/build-bearoffs boolean true ############################ #### gnumeric_1.12.55-1_amd64.deb ############################ ### Description: Really upgrade gnumeric? # An instance of gnumeric is currently running. If you # upgrade now, it may no longer be able to save its data. # . # You should close the running instances of gnumeric # before upgrading this package. # d-i gnumeric/existing-process boolean false ############################ #### gnunet_0.19.3-2_amd64.deb ############################ ### Description: GNUnet user: # Please choose the user that the GNUnet server process will run as. # . # This should be a dedicated account. If the specified account does not # already exist, it will automatically be created, with no login shell. # d-i gnunet/user string gnunet ### Description: GNUnet group: # Please choose the group that the GNUnet server process will run as. # . # This should be a dedicated group, not one that already owns data. Only the # members of this group will have access to GNUnet data, and be allowed to # start and stop the GNUnet server. # d-i gnunet/group string gnunet ### Description: Should the GNUnet server be launched on boot? # If you choose this option, a GNUnet server will be launched each time the # system is started. Otherwise, you will need to launch GNUnet each time you # want to use it. # d-i gnunet/autostart boolean true ############################ #### gom_0.30.4-1_amd64.deb ############################ ### Description: Initialize mixer on system startup? # If you choose this option, "/etc/init.d/gom start" (on system # startup, or if run manually) will set mixer settings to your saved # configuration. # . # You may use upstream's "gomconfig" script as root later to fine-tune # the settings. # d-i gom/auto_init boolean false ### Description: Space-separated list of valid sound devices: # If none of these device names exists in /proc/devices, # /etc/init.d/gom will exit silently (so it does not produce errors if # the system has no sound at all). # . # You would usually not touch the default value ("sound" is OSS, "alsa" # is ALSA). # d-i gom/valid_sound_devices string sound alsa ### Description: Remove /etc/gom completely? # The /etc/gom directory seems to contain additional local # customization files. Please choose whether you want to remove it # entirely. # d-i gom/purge_etc_gom boolean true ### Description: Remove obsoleted /etc/rc.boot/gom? # The /etc/rc.boot/gom file is obsoleted but might contain local # customizations. # d-i gom/remove_obsolete_rcboot boolean true ############################ #### gosa-desktop_2.8~git20230203.10abe45+dfsg-1+deb12u2_all.deb ############################ ### Description: URL to your GOsa installation: # The gosa start script can automatically point your # browser to a system wide default location of your # GOsa instance. # . # Enter the URL in order to set this default. # d-i gosa-desktop/url string http://localhost/gosa ############################ #### gpm_1.20.7-10+b1_amd64.deb ############################ ### Description: Do you want to (re)start GPM while X is running? # Usually, GPM should be started or restarted when it is installed or # upgraded. However, when X is running and trying to use the same mouse # device, this can sometimes cause a problem with the X mouse cursor. # Switching to the console and then back to X will usually fix it. # d-i gpm/restart boolean false ### Description: Mouse device for GPM: # Please enter the mouse device name. # . # Common mouse devices names: # - PS/2 mouse: /dev/psaux # - Serial mouse: /dev/ttySx # - USB mouse: /dev/input/mice # - Sun mouse: /dev/sunmouse # - M68k Mac mouse: /dev/mouse # d-i gpm/device string ### Description: Mouse type: # Available mouse types are: # . # Name Description # . # PS/2 mice: round 6-pin connector # autops2 Most PS/2 mice; specific protocol will be auto-detected. # Also use this for USB and ADB mice. # ps2 Standard PS/2 mice, 2 or 3 buttons # imps2 Microsoft IntelliMouse and compatibles; PS/2 mice with # 3 buttons and a scroll wheel # exps2 Newer Microsoft IntelliMouse and compatible, may have # more than 3 buttons. Most newer PS/2 mice are this type. # synps2 Synaptics PS/2 TouchPad, found on many laptops # netmouse Genius NetMouse, 2 normal buttons plus an "Up/Down" button # fups2 Same as "ps2" but may be needed for certain broken # mice or KVM switches # fuimps2 Same as "imps2" but may be needed for certain broken # mice or KVM switches # . # Serial mice: 9-pin or 25-pin serial connector # msc The MouseSystems protocol. Most 3-button serial mice. # mman The MouseMan protocol used by newer Logitech serial mice # ms3 Microsoft IntelliMouse, 3 buttons plus scroll wheel # ms Microsoft serial mice, 2 or 3 buttons, no wheel # ms+ Like 'ms', but allows dragging with the middle button # ms+lr 'ms+', but you can reset m by pressing lr (see man page) # pnp Microsoft's "plug and play" serial mouse standard # bare 2-button Microsoft serial mice. Use this one if the 'ms' # protocol seems to produce spurious middle-button events. # mm MM series. Probably an old protocol. # logi Old serial Logitech mice # logim Old Logitech serial mice in MouseSystems mode (3 buttons) # syn Synaptics TouchPad, serial version # brw Fellowes Browser - 4 buttons and a wheel # . # Other mice # bm Some Microsoft and Logitech bus mice: 8-pin round connector # vsxxxaa The DEC VSXXX-AA/GA serial mouse on DEC workstations # sun Sparc mice # . # Non-mice # js Mouse emulation with a joystick # cal Calcomp UltraSlate in absolute mode # calr Calcomp UltraSlate in relative mode # twid Handykey Twiddler keyboard # ncr Ncr3125pen, found on some laptops # wacom Wacom Protocol IV Tablets: Pen+Mouse, # relative+absolute mode # genitizer Genitizer tablet, in relative mode # summa Summa/Genius tablet in absolute mode # (906, 1212B, EasyPainter...) # mtouch MicroTouch touch-screens (only button-1 events reported) # gunze Gunze touch-screens (only button-1 events reported) # acecad Acecad tablet in absolute mode (Summagraphics MM-Series mode) # wp Genius WizardPad tablet # d-i gpm/type string ### Description: Mouse responsiveness: # The responsiveness defines how often the cursor responds to mouse # movement, and is expressed as a number. If the mouse seems to # move too slowly, try setting this to 15. # d-i gpm/responsiveness string ### Description: Protocol to use for repeating mouse events: # GPM can act as a repeater via /dev/gpmdata, and give both GPM and X access # to the mouse data in configurations where it would otherwise only be available # to only X or GPM. # . # Enter 'none' to turn repeating off. # d-i gpm/repeat_type string ms3 ### Description: Mouse sample rate: # The sample rate defines how often GPM polls the mouse device for new # position data. Tweaking it can make the mouse appear to move more # smoothly, but this option is for experts only. # d-i gpm/sample_rate string ### Description: Additional arguments for the GPM daemon: # Please enter any additional arguments that the GPM daemon should use. # d-i gpm/append string ############################ #### gpr_0.15deb-2+b2_amd64.deb ############################ ### Description: divert lpr with a wrapper that points to gpr? # gpr can install a wrapper in place of the command lpr. The wrapper will # call the real lpr command if: either it is called from a terminal, or # there is no access to an X DISPLAY; otherwise it will call gpr. This # wrapper can be useful when printing from graphical programs (such as # mozilla or openoffice), so that the users will be able to choose the # printer and other printer-related settings. # d-i gpr/divert_lpr boolean false ############################ #### graphite-carbon_1.1.7-1.1_all.deb ############################ ### Description: Remove database files when purging graphite-carbon? # The /var/lib/graphite/whisper directory contains the whisper database # files. # . # You may want to keep these database files even if you completely # remove graphite-carbon, in case you plan to reinstall it later. # d-i graphite-carbon/postrm_remove_databases boolean false ############################ #### greylistd_0.9.0.2+nmu1_all.deb ############################ ### Description: Restart Exim after adding it to the greylist group? # You are using Exim 4 as your Mail Transport Agent (MTA). Great! # . # The "Debian-exim" user will be added to the "greylist" group, so that the # Exim daemon process can talk to greylistd. However, for this change to # take effect, the process must also be restarted. # d-i greylistd/restartexim boolean true ############################ #### gridengine-client_8.1.9+dfsg-10+b1_amd64.deb ############################ ### Description: Configure SGE automatically? # Please choose whether you wish to configure SGE automatically (with # debconf). If you do not configure it automatically, the daemons or client # programs will not work until a manual configuration is performed. # d-i shared/gridengineconfig boolean true ### Description: SGE cell name: # Please provide the SGE cell name for use by client programs and the # execution daemon. # d-i shared/gridenginecell string default ### Description: SGE master hostname: # The execution daemon and the client programs need to know where the cluster # master is in order to run. # . # Please enter the fully qualified domain name of the grid master. # d-i shared/gridenginemaster string ############################ #### gridengine-common_8.1.9+dfsg-10_all.deb ############################ ### Description: Configure SGE automatically? # Please choose whether you wish to configure SGE automatically (with # debconf). If you do not configure it automatically, the daemons or client # programs will not work until a manual configuration is performed. # d-i shared/gridengineconfig boolean true ### Description: SGE cell name: # Please provide the SGE cell name for use by client programs and the # execution daemon. # d-i shared/gridenginecell string default ### Description: SGE master hostname: # The execution daemon and the client programs need to know where the cluster # master is in order to run. # . # Please enter the fully qualified domain name of the grid master. # d-i shared/gridenginemaster string ############################ #### gridengine-exec_8.1.9+dfsg-10+b1_amd64.deb ############################ ### Description: Configure SGE automatically? # Please choose whether you wish to configure SGE automatically (with # debconf). If you do not configure it automatically, the daemons or client # programs will not work until a manual configuration is performed. # d-i shared/gridengineconfig boolean true ### Description: SGE cell name: # Please provide the SGE cell name for use by client programs and the # execution daemon. # d-i shared/gridenginecell string default ### Description: SGE master hostname: # The execution daemon and the client programs need to know where the cluster # master is in order to run. # . # Please enter the fully qualified domain name of the grid master. # d-i shared/gridenginemaster string ############################ #### gridengine-master_8.1.9+dfsg-10+b1_amd64.deb ############################ ### Description: Configure SGE automatically? # Please choose whether you wish to configure SGE automatically (with # debconf). If you do not configure it automatically, the daemons or client # programs will not work until a manual configuration is performed. # d-i shared/gridengineconfig boolean true ### Description: SGE cell name: # Please provide the SGE cell name for use by client programs and the # execution daemon. # d-i shared/gridenginecell string default ### Description: SGE master hostname: # The execution daemon and the client programs need to know where the cluster # master is in order to run. # . # Please enter the fully qualified domain name of the grid master. # d-i shared/gridenginemaster string ############################ #### gridengine-qmon_8.1.9+dfsg-10+b1_amd64.deb ############################ ### Description: Configure SGE automatically? # Please choose whether you wish to configure SGE automatically (with # debconf). If you do not configure it automatically, the daemons or client # programs will not work until a manual configuration is performed. # d-i shared/gridengineconfig boolean true ### Description: SGE cell name: # Please provide the SGE cell name for use by client programs and the # execution daemon. # d-i shared/gridenginecell string default ### Description: SGE master hostname: # The execution daemon and the client programs need to know where the cluster # master is in order to run. # . # Please enter the fully qualified domain name of the grid master. # d-i shared/gridenginemaster string ############################ #### grub-coreboot_2.06-13+deb12u1_amd64.deb ############################ ### Description: Linux command line: # The following Linux command line was extracted from /etc/default/grub or the # `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, # and modify it if necessary. The command line is allowed to be empty. # d-i grub2/linux_cmdline string ### Description: Linux default command line: # The following string will be used as Linux parameters for the default menu # entry but not for the recovery mode. # d-i grub2/linux_cmdline_default string quiet ### Description: Force extra installation to the EFI removable media path? # Some EFI-based systems are buggy and do not handle new bootloaders correctly. # If you force an extra installation of GRUB to the EFI removable media path, # this should ensure that this system will boot Debian correctly despite such a # problem. However, it may remove the ability to boot any other operating # systems that also depend on this path. If so, you will need to make sure that # GRUB is configured successfully to be able to boot any other OS installations # correctly. # d-i grub2/force_efi_extra_removable boolean false ### Description: Update NVRAM variables to automatically boot into Debian? # GRUB can configure your platform's NVRAM variables so that it boots into # Debian automatically when powered on. However, you may prefer to disable # this behavior and avoid changes to your boot configuration. For example, # if your NVRAM variables have been set up such that your system contacts a # PXE server on every boot, this would preserve that behavior. # d-i grub2/update_nvram boolean true ### Description: Run os-prober automatically to detect and boot other OSes? # GRUB can use the os-prober tool to attempt to detect other # operating systems on your computer and add them to its list of boot # options automatically. # . # If your computer has multiple operating systems installed, then this # is probably what you want. However, if your computer is a host for # guest OSes installed via LVM or raw disk devices, running os-prober # can cause damage to those guest OSes as it mounts filesystems to look # for things. # d-i grub2/enable_os_prober boolean false ### Description: kFreeBSD command line: # The following kFreeBSD command line was extracted from /etc/default/grub or the # `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, # and modify it if necessary. The command line is allowed to be empty. # d-i grub2/kfreebsd_cmdline string ### Description: kFreeBSD default command line: # The following string will be used as kFreeBSD parameters for the default menu # entry but not for the recovery mode. # d-i grub2/kfreebsd_cmdline_default string quiet ############################ #### grub-efi-amd64_2.06-13+deb12u1_amd64.deb ############################ ### Description: Linux command line: # The following Linux command line was extracted from /etc/default/grub or the # `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, # and modify it if necessary. The command line is allowed to be empty. # d-i grub2/linux_cmdline string ### Description: Linux default command line: # The following string will be used as Linux parameters for the default menu # entry but not for the recovery mode. # d-i grub2/linux_cmdline_default string quiet ### Description: Force extra installation to the EFI removable media path? # Some EFI-based systems are buggy and do not handle new bootloaders correctly. # If you force an extra installation of GRUB to the EFI removable media path, # this should ensure that this system will boot Debian correctly despite such a # problem. However, it may remove the ability to boot any other operating # systems that also depend on this path. If so, you will need to make sure that # GRUB is configured successfully to be able to boot any other OS installations # correctly. # d-i grub2/force_efi_extra_removable boolean false ### Description: Update NVRAM variables to automatically boot into Debian? # GRUB can configure your platform's NVRAM variables so that it boots into # Debian automatically when powered on. However, you may prefer to disable # this behavior and avoid changes to your boot configuration. For example, # if your NVRAM variables have been set up such that your system contacts a # PXE server on every boot, this would preserve that behavior. # d-i grub2/update_nvram boolean true ### Description: Run os-prober automatically to detect and boot other OSes? # GRUB can use the os-prober tool to attempt to detect other # operating systems on your computer and add them to its list of boot # options automatically. # . # If your computer has multiple operating systems installed, then this # is probably what you want. However, if your computer is a host for # guest OSes installed via LVM or raw disk devices, running os-prober # can cause damage to those guest OSes as it mounts filesystems to look # for things. # d-i grub2/enable_os_prober boolean false ### Description: kFreeBSD command line: # The following kFreeBSD command line was extracted from /etc/default/grub or the # `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, # and modify it if necessary. The command line is allowed to be empty. # d-i grub2/kfreebsd_cmdline string ### Description: kFreeBSD default command line: # The following string will be used as kFreeBSD parameters for the default menu # entry but not for the recovery mode. # d-i grub2/kfreebsd_cmdline_default string quiet ############################ #### grub-efi-ia32_2.06-13+deb12u1_amd64.deb ############################ ### Description: Linux command line: # The following Linux command line was extracted from /etc/default/grub or the # `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, # and modify it if necessary. The command line is allowed to be empty. # d-i grub2/linux_cmdline string ### Description: Linux default command line: # The following string will be used as Linux parameters for the default menu # entry but not for the recovery mode. # d-i grub2/linux_cmdline_default string quiet ### Description: Force extra installation to the EFI removable media path? # Some EFI-based systems are buggy and do not handle new bootloaders correctly. # If you force an extra installation of GRUB to the EFI removable media path, # this should ensure that this system will boot Debian correctly despite such a # problem. However, it may remove the ability to boot any other operating # systems that also depend on this path. If so, you will need to make sure that # GRUB is configured successfully to be able to boot any other OS installations # correctly. # d-i grub2/force_efi_extra_removable boolean false ### Description: Update NVRAM variables to automatically boot into Debian? # GRUB can configure your platform's NVRAM variables so that it boots into # Debian automatically when powered on. However, you may prefer to disable # this behavior and avoid changes to your boot configuration. For example, # if your NVRAM variables have been set up such that your system contacts a # PXE server on every boot, this would preserve that behavior. # d-i grub2/update_nvram boolean true ### Description: Run os-prober automatically to detect and boot other OSes? # GRUB can use the os-prober tool to attempt to detect other # operating systems on your computer and add them to its list of boot # options automatically. # . # If your computer has multiple operating systems installed, then this # is probably what you want. However, if your computer is a host for # guest OSes installed via LVM or raw disk devices, running os-prober # can cause damage to those guest OSes as it mounts filesystems to look # for things. # d-i grub2/enable_os_prober boolean false ### Description: kFreeBSD command line: # The following kFreeBSD command line was extracted from /etc/default/grub or the # `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, # and modify it if necessary. The command line is allowed to be empty. # d-i grub2/kfreebsd_cmdline string ### Description: kFreeBSD default command line: # The following string will be used as kFreeBSD parameters for the default menu # entry but not for the recovery mode. # d-i grub2/kfreebsd_cmdline_default string quiet ############################ #### grub-ieee1275_2.06-13+deb12u1_amd64.deb ############################ ### Description: Linux command line: # The following Linux command line was extracted from /etc/default/grub or the # `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, # and modify it if necessary. The command line is allowed to be empty. # d-i grub2/linux_cmdline string ### Description: Linux default command line: # The following string will be used as Linux parameters for the default menu # entry but not for the recovery mode. # d-i grub2/linux_cmdline_default string quiet ### Description: Force extra installation to the EFI removable media path? # Some EFI-based systems are buggy and do not handle new bootloaders correctly. # If you force an extra installation of GRUB to the EFI removable media path, # this should ensure that this system will boot Debian correctly despite such a # problem. However, it may remove the ability to boot any other operating # systems that also depend on this path. If so, you will need to make sure that # GRUB is configured successfully to be able to boot any other OS installations # correctly. # d-i grub2/force_efi_extra_removable boolean false ### Description: Update NVRAM variables to automatically boot into Debian? # GRUB can configure your platform's NVRAM variables so that it boots into # Debian automatically when powered on. However, you may prefer to disable # this behavior and avoid changes to your boot configuration. For example, # if your NVRAM variables have been set up such that your system contacts a # PXE server on every boot, this would preserve that behavior. # d-i grub2/update_nvram boolean true ### Description: Run os-prober automatically to detect and boot other OSes? # GRUB can use the os-prober tool to attempt to detect other # operating systems on your computer and add them to its list of boot # options automatically. # . # If your computer has multiple operating systems installed, then this # is probably what you want. However, if your computer is a host for # guest OSes installed via LVM or raw disk devices, running os-prober # can cause damage to those guest OSes as it mounts filesystems to look # for things. # d-i grub2/enable_os_prober boolean false ### Description: kFreeBSD command line: # The following kFreeBSD command line was extracted from /etc/default/grub or the # `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, # and modify it if necessary. The command line is allowed to be empty. # d-i grub2/kfreebsd_cmdline string ### Description: kFreeBSD default command line: # The following string will be used as kFreeBSD parameters for the default menu # entry but not for the recovery mode. # d-i grub2/kfreebsd_cmdline_default string quiet ############################ #### grub-pc_2.06-13+deb12u1_amd64.deb ############################ ### Description: Linux command line: # The following Linux command line was extracted from /etc/default/grub or the # `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, # and modify it if necessary. The command line is allowed to be empty. # d-i grub2/linux_cmdline string ### Description: Linux default command line: # The following string will be used as Linux parameters for the default menu # entry but not for the recovery mode. # d-i grub2/linux_cmdline_default string quiet ### Description: Force extra installation to the EFI removable media path? # Some EFI-based systems are buggy and do not handle new bootloaders correctly. # If you force an extra installation of GRUB to the EFI removable media path, # this should ensure that this system will boot Debian correctly despite such a # problem. However, it may remove the ability to boot any other operating # systems that also depend on this path. If so, you will need to make sure that # GRUB is configured successfully to be able to boot any other OS installations # correctly. # d-i grub2/force_efi_extra_removable boolean false ### Description: Update NVRAM variables to automatically boot into Debian? # GRUB can configure your platform's NVRAM variables so that it boots into # Debian automatically when powered on. However, you may prefer to disable # this behavior and avoid changes to your boot configuration. For example, # if your NVRAM variables have been set up such that your system contacts a # PXE server on every boot, this would preserve that behavior. # d-i grub2/update_nvram boolean true ### Description: Run os-prober automatically to detect and boot other OSes? # GRUB can use the os-prober tool to attempt to detect other # operating systems on your computer and add them to its list of boot # options automatically. # . # If your computer has multiple operating systems installed, then this # is probably what you want. However, if your computer is a host for # guest OSes installed via LVM or raw disk devices, running os-prober # can cause damage to those guest OSes as it mounts filesystems to look # for things. # d-i grub2/enable_os_prober boolean false ### Description: kFreeBSD command line: # The following kFreeBSD command line was extracted from /etc/default/grub or the # `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, # and modify it if necessary. The command line is allowed to be empty. # d-i grub2/kfreebsd_cmdline string ### Description: kFreeBSD default command line: # The following string will be used as kFreeBSD parameters for the default menu # entry but not for the recovery mode. # d-i grub2/kfreebsd_cmdline_default string quiet ### Description: Chainload from menu.lst? # GRUB upgrade scripts have detected a GRUB Legacy setup in /boot/grub. # . # In order to replace the Legacy version of GRUB in your system, it is # recommended that /boot/grub/menu.lst is adjusted to load a GRUB 2 boot # image from your existing GRUB Legacy setup. This step can be automatically # performed now. # . # It's recommended that you accept chainloading GRUB 2 from menu.lst, and # verify that the new GRUB 2 setup works before it is written to the MBR # (Master Boot Record). # . # Whatever your decision, you can replace the old MBR image with GRUB 2 # later by issuing the following command as root: # . # upgrade-from-grub-legacy # d-i grub-pc/chainload_from_menu.lst boolean true ### Description: GRUB install devices: # The grub-pc package is being upgraded. This menu allows you to select which # devices you'd like grub-install to be automatically run for, if any. # . # Running grub-install automatically is recommended in most situations, to # prevent the installed GRUB core image from getting out of sync with GRUB # modules or grub.cfg. # . # If you're unsure which drive is designated as boot drive by your BIOS, it is # often a good idea to install GRUB to all of them. # . # Note: it is possible to install GRUB to partition boot records as well, and # some appropriate partitions are offered here. However, this forces GRUB to # use the blocklist mechanism, which makes it less reliable, and therefore is # not recommended. # d-i grub-pc/install_devices multiselect # Possible choices: ${CHOICES} ### Description: GRUB install devices: # The GRUB boot loader was previously installed to a disk that is no longer # present, or whose unique identifier has changed for some reason. It is # important to make sure that the installed GRUB core image stays in sync # with GRUB modules and grub.cfg. Please check again to make sure that GRUB # is written to the appropriate boot devices. # . # If you're unsure which drive is designated as boot drive by your BIOS, it is # often a good idea to install GRUB to all of them. # . # Note: it is possible to install GRUB to partition boot records as well, and # some appropriate partitions are offered here. However, this forces GRUB to # use the blocklist mechanism, which makes it less reliable, and therefore is # not recommended. # d-i grub-pc/install_devices_disks_changed multiselect # Possible choices: ${CHOICES} ### Description: Writing GRUB to boot device failed - continue? # GRUB failed to install to the following devices: # . # ${FAILED_DEVICES} # . # Do you want to continue anyway? If you do, your computer may not start up # properly. # d-i grub-pc/install_devices_failed boolean false ### Description: Writing GRUB to boot device failed - try again? # GRUB failed to install to the following devices: # . # ${FAILED_DEVICES} # . # You may be able to install GRUB to some other device, although you should # check that your system will boot from that device. Otherwise, the upgrade # from GRUB Legacy will be canceled. # d-i grub-pc/install_devices_failed_upgrade boolean true ### Description: Continue without installing GRUB? # You chose not to install GRUB to any devices. If you continue, the boot # loader may not be properly configured, and when this computer next starts # up it will use whatever was previously in the boot sector. If there is an # earlier version of GRUB 2 in the boot sector, it may be unable to load # modules or handle the current configuration file. # . # If you are already using a different boot loader and want to carry on # doing so, or if this is a special environment where you do not need a boot # loader, then you should continue anyway. Otherwise, you should install # GRUB somewhere. # d-i grub-pc/install_devices_empty boolean false ### Description: Remove GRUB 2 from /boot/grub? # Do you want to have all GRUB 2 files removed from /boot/grub? # . # This will make the system unbootable unless another boot loader is # installed. # d-i grub-pc/postrm_purge_boot_grub boolean false ### Description: Finish conversion to GRUB 2 now? # This system still has files from the GRUB Legacy boot loader installed, but # it now also has GRUB 2 boot records installed on these disks: # . # ${DISKS} # . # It seems likely that GRUB Legacy is no longer in use, and that you should # instead upgrade the GRUB 2 images on these disks and finish the conversion # to GRUB 2 by removing old GRUB Legacy files. If you do not upgrade these # GRUB 2 images, then they may be incompatible with the new packages and # cause your system to stop booting properly. # . # You should generally finish the conversion to GRUB 2 unless these boot # records were created by a GRUB 2 installation on some other operating # system. # d-i grub-pc/mixed_legacy_and_grub2 boolean true ### Description: for internal use # d-i grub-pc/kopt_extracted boolean false ### Description: GRUB timeout; for internal use # d-i grub-pc/timeout string 5 ### Description: Hide the GRUB timeout; for internal use # d-i grub-pc/hidden_timeout boolean false ############################ #### grub-xen_2.06-13+deb12u1_amd64.deb ############################ ### Description: Linux command line: # The following Linux command line was extracted from /etc/default/grub or the # `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, # and modify it if necessary. The command line is allowed to be empty. # d-i grub2/linux_cmdline string ### Description: Linux default command line: # The following string will be used as Linux parameters for the default menu # entry but not for the recovery mode. # d-i grub2/linux_cmdline_default string quiet ### Description: Force extra installation to the EFI removable media path? # Some EFI-based systems are buggy and do not handle new bootloaders correctly. # If you force an extra installation of GRUB to the EFI removable media path, # this should ensure that this system will boot Debian correctly despite such a # problem. However, it may remove the ability to boot any other operating # systems that also depend on this path. If so, you will need to make sure that # GRUB is configured successfully to be able to boot any other OS installations # correctly. # d-i grub2/force_efi_extra_removable boolean false ### Description: Update NVRAM variables to automatically boot into Debian? # GRUB can configure your platform's NVRAM variables so that it boots into # Debian automatically when powered on. However, you may prefer to disable # this behavior and avoid changes to your boot configuration. For example, # if your NVRAM variables have been set up such that your system contacts a # PXE server on every boot, this would preserve that behavior. # d-i grub2/update_nvram boolean true ### Description: Run os-prober automatically to detect and boot other OSes? # GRUB can use the os-prober tool to attempt to detect other # operating systems on your computer and add them to its list of boot # options automatically. # . # If your computer has multiple operating systems installed, then this # is probably what you want. However, if your computer is a host for # guest OSes installed via LVM or raw disk devices, running os-prober # can cause damage to those guest OSes as it mounts filesystems to look # for things. # d-i grub2/enable_os_prober boolean false ### Description: kFreeBSD command line: # The following kFreeBSD command line was extracted from /etc/default/grub or the # `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, # and modify it if necessary. The command line is allowed to be empty. # d-i grub2/kfreebsd_cmdline string ### Description: kFreeBSD default command line: # The following string will be used as kFreeBSD parameters for the default menu # entry but not for the recovery mode. # d-i grub2/kfreebsd_cmdline_default string quiet ############################ #### gwhois_20120626.0-1_all.deb ############################ ### Description: Install gwhois as a whois proxy server? # If gwhois is installed as a whois proxy server (using inetd) it # will listen on the standard whois port (43) allowing normal # whois clients to query it. # . # This can be interesting for example if you want to setup a generic whois # server for your company or coworkers which can then use their standard # whois-client (e.g. a windows client) and still make use of the intelligent # features of gwhois. # d-i gwhois/inetd boolean false ############################ #### haserl_0.9.36-1_amd64.deb ############################ ### Description: Install haserl binary with suid root permissions? # When haserl is installed with suid root permissions, it will automatically set # its UID and GID to match the owner and group of the script. # . # This is a potential security vulnerability, as scripts that are owned # by root will be run as root, even when they do not have the suid root bit. # d-i haserl/setuid boolean false ############################ #### hearse_1.5+debian1-2_all.deb ############################ ### Description: Email address to submit to the Hearse server: # The Hearse server requires that you supply an email address before # you can exchange bones files. If you supply an address here it will # be submitted to the server for you. If you don't supply an address, # hearse will be installed but it won't run automatically until you # create an account yourself. # . # The server operator states that your email address will only be used # to contact you about Hearse, and will never be given to any third # party. If you enter an invalid address, the server won't be able to # support you if you download a bad bones file, and will be forced to # ban you if any of your uploaded files are bad. # d-i hearse/user-email string ############################ #### heat-api_19.0.0-3_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i heat/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i heat/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i heat/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i heat/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i heat/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i heat/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i heat/api-endpoint-address string ### Description: This service endpoint protocol: # d-i heat/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i heat/api-endpoint-region-name string regionOne ############################ #### heat-api-cfn_19.0.0-3_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i heat-api-cfn/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i heat-api-cfn/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i heat-api-cfn/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i heat-api-cfn/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i heat-api-cfn/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i heat-api-cfn/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i heat-api-cfn/api-endpoint-address string ### Description: This service endpoint protocol: # d-i heat-api-cfn/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i heat-api-cfn/api-endpoint-region-name string regionOne ############################ #### heat-common_19.0.0-3_all.deb ############################ ### Description: Configure Heat domain with debconf? # Heat domain must be configured to connect to Keystone. Specify this should be # configured through debconf. # d-i heat/configure_with_debconf boolean false ### Description: Heat domain administrator username: # Please enter the username of the Heat domain administrator. # d-i heat/heat_domain_admin_username string heat_domain_admin ### Description: Heat domain administrator password: # Please enter the password of the Heat domain administrator. # d-i heat/heat_domain_admin_password password ### Description: Heat domain: # Please enter domain name which will be used as heat domain. # d-i heat/heat_domain_name string heat ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i heat/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i heat/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i heat/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i heat/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i heat/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i heat/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i heat/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i heat/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i heat/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i heat/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i heat/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i heat/ksat-admin-password password ### Description: Auth server service username: # d-i heat/ksat-service-username string ### Description: Auth server service project name: # d-i heat/ksat-service-project-name string service ### Description: Auth server service password: # d-i heat/ksat-service-password password ############################ #### heimdal-kdc_7.8.git20221117.28daf24+dfsg-2_amd64.deb ############################ ### Description: Local realm name: # Please enter the name of the local Kerberos realm. # . # Using the uppercase domain name is common. For instance, if the host # name is host.example.org, then the realm will become EXAMPLE.ORG. The # default for this host is ${default_realm}. # d-i heimdal/realm string ### Description: KDC password: # Heimdal can encrypt the key distribution center (KDC) data with # a password. A hashed representation of this password will be stored # in /var/lib/heimdal-kdc/m-key. # d-i heimdal-kdc/password password ############################ #### libhesiod0_3.2.1-4_amd64.deb ############################ ### Description: Hesiod domain for searches: # Please enter the Hesiod RHS (right hand-side) to do searches in. # . # If the Hesiod server is 'ns.example.org' then the LHS will be '.ns', the # RHS will be '.example.org' (note leading periods) and directory lookups # will be performed as DNS requests to (e.g.) 'sam.passwd.ns.example.org'. # d-i hesiod/rhs string .athena.mit.edu ### Description: Hesiod prefix for searches: # Please enter the Hesiod LHS (left hand-side) to do searches in. # . # If the Hesiod server is 'ns.example.org' then the LHS will be '.ns', the # RHS will be '.example.org' (note leading periods) and directory lookups # will be performed as DNS requests to (e.g.) 'sam.passwd.ns.example.org'. # d-i hesiod/lhs string .ns ### Description: DNS class search order: # Hesiod looks up names using DNS TXT records. In addition to using the # standard IN DNS class for Internet names, it also uses by default the # special HS class. # . # Please enter the class search order (the default value is suitable for # most sites). There should be no spaces in this search order value. # . # Sites using # older Hesiod installations may need to use the 'HS,IN' search order. # d-i hesiod/classes string IN,HS ############################ #### iogerman_2-38_all.deb ############################ ############################ #### wogerman_2-38_all.deb ############################ ############################ #### openstack-dashboard_23.0.0-5+deb12u1_all.deb ############################ ### Description: Allowed hostname(s): # Please enter the list of hostnames that can be used to reach your OpenStack # Dashboard server. This is a security measure to prevent HTTP Host header attacks, # which are possible even under many seemingly-safe web server configurations. # . # Enter values separated by commas. Any space will be removed, so you can add # some to make it more readable. # . # Values in this list can be fully qualified names like "www.example.com", in # which case they will be matched against the request's Host header exactly # (case-insensitive, not including port). A value beginning with a period can be # used as a subdomain wildcard: ".example.com" will match example.com, # www.example.com, and any other subdomain of example.com. A value of "*" will # match anything; in this case you are responsible for providing your own # validation of the Host header (perhaps in middleware; if so this middleware # must be listed first in MIDDLEWARE). # d-i horizon/allowed-hosts string ############################ #### openstack-dashboard-apache_23.0.0-5+deb12u1_all.deb ############################ ### Description: Activate Dashboard and disable default VirtualHost? # The Apache package sets up a default web site and a default page, configured # in /etc/apache2/sites-available/000-default.conf. # . # If this option is not selected, Horizon will be installed using /horizon # instead of the webroot. # . # Choose this option to replace that default with the OpenStack Dashboard # configuration. # d-i horizon/activate_vhost boolean false ### Description: Should the Dashboard use HTTPS? # Select this option if you would like Horizon to be served over HTTPS only, # with a redirection to HTTPS if HTTP is in use. # d-i horizon/use_ssl boolean true ############################ #### hoteldruid_3.0.4-1_all.deb ############################ ### Description: Automatically configure the Apache web server for HotelDruid? # HotelDruid runs on any web server supporting PHP, but automatic # configuration can only be performed for Apache. # . # Once configured, HotelDruid can be accessed locally at # "http://localhost/hoteldruid". # . # Please choose whether automatic configuration should be performed now. # d-i hoteldruid/configure-apache boolean true ### Description: Restrict HotelDruid access to localhost? # The Apache web server can be configured to forbid HotelDruid # connections from other machines. # . # It is recommended to activate this setting if HotelDruid is # going to be used only from this machine. # d-i hoteldruid/restrict-localhost boolean true ### Description: Reload the web server configuration for HotelDruid? # In order to activate the new configuration for HotelDruid, # the web server has to reload its configuration files. # d-i hoteldruid/restart-webserver boolean true ### Description: HotelDruid administrator username: # Please enter a name for the administrator user, which will be able to # manage HotelDruid's configuration and create new users. The # username should be composed of ASCII letters and numbers only. # . # You can later change the administrator username and password from # the "User management" page in HotelDruid. If this field is left blank, # no user login will be required to access HotelDruid. # d-i hoteldruid/administrator-username string admin ### Description: HotelDruid administrator password: # Please choose a password for the HotelDruid administrator. # d-i hoteldruid/administrator-password password ### Description: Re-enter password to verify: # Please enter the same "admin" password again to verify # you have typed it correctly. # d-i hoteldruid/confirm-password password ### Description: Erase HotelDruid data when purging the package? # The hoteldruid package is about to be purged from this system. # . # HotelDruid stores its data in "/var/lib/hoteldruid". # If you choose this option, these data files will be erased now. # . # Refuse this option if there is operational information which should be # kept after HotelDruid is purged. # d-i hoteldruid/purgedata boolean false ############################ #### htdig_3.2.0b6-19+b1_amd64.deb ############################ ### Description: Generate ht://Dig endings database now? # The ht://Dig search engine requires an endings database which has to be # generated before the first start. Generating the database will take a # short while. It can be done either now or later by calling the # '/usr/sbin/htdigconfig' script. # d-i htdig/generate-databases boolean true ### Description: Schedule a daily execution of the 'rundig' script? # On-line content must be indexed by the 'rundig' script before # ht://Dig can be used to search data. That script indexes the # web content defined in /etc/htdig/htdig.conf. # . # If you choose this option, a daily run of the script will be scheduled. # You may choose to not use this option if ht://Dig is used another # way (for instance by KDE, to # perform local indexing). If in doubt, do not choose this option. # d-i htdig/run-rundig boolean false ############################ #### hylafax-server_6.0.7-5_amd64.deb ############################ ### Description: Start the HylaFAX daemon now? # Hylafax is already configured and may be started now. If you specify to # start it later manually, remember to change the value of RUN_HYLAFAX # in /etc/default/hylafax. # d-i hylafax-server/start_now boolean true ############################ #### libhyperscan5_5.4.0-2_amd64.deb ############################ ### Description: Really install package? # This CPU lacks support for the Supplemental Streaming SIMD Extensions # 3 (SSSE3) instruction set that is required to execute programs linked # against hyperscan. # d-i libhyperscan/cpu-ssse3 boolean false ############################ #### icecast2_2.4.4-4+b1_amd64.deb ############################ ### Description: Configure Icecast2? # Choose this option to set up passwords for Icecast2. Until these are # configured the server will not be activated. # . # You should not use this option if you have already manually tweaked # the configuration of Icecast2. # d-i icecast2/icecast-setup boolean false ### Description: Icecast2 hostname: # Please specify the fully qualified domain name that should be used # as prefix to all streams. # d-i icecast2/hostname string localhost ### Description: Icecast2 source password: # Please specify the password that should be used to control access to # Icecast2's media sources. # d-i icecast2/sourcepassword string hackme ### Description: Icecast2 relay password: # Please specify the password that should be used to control access to # Icecast2's stream relays. # d-i icecast2/relaypassword string hackme ### Description: Icecast2 administration password: # Please specify the password that should be used for Icecast2 # administration. # . # The administration web interface, at http://localhost:8000, can be # used to monitor connections or to block users from streaming. # d-i icecast2/adminpassword string hackme ############################ #### icinga2-ido-mysql_2.13.6-2_amd64.deb ############################ ### Description: Enable Icinga 2's ido-mysql feature? # Please specify whether Icinga 2 should use MySQL. # . # You may later disable the feature by using the # "icinga2 feature disable ido-mysql" command. # d-i icinga2-ido-mysql/enable boolean true ############################ #### icinga2-ido-pgsql_2.13.6-2_amd64.deb ############################ ### Description: Enable Icinga 2's ido-pgsql feature? # Please specify whether Icinga 2 should use PostgreSQL. # . # You may later disable the feature by using the # "icinga2 feature disable ido-pgsql" command. # d-i icinga2-ido-pgsql/enable boolean true ############################ #### libgempc410_1.0.8-7_amd64.deb ############################ ### Description: Communication port to use with the smart card reader: # The driver needs to know to which serial port the GemPC410 reader is # connected. # d-i libgempc410/port select # Possible choices: ttyS0, ttyS1, ttyS2, ttyS3, None ############################ #### ifetch-tools_0.18.5-1_all.deb ############################ ### Description: Remove all ifetch-tools data, logs, and settings files? # The /var/lib/ifetch-tools, /var/log/ifetch-tools, and /etc/ifetch-tools # directories which contain the ifetch-tools data, logs, and settings files # are about to be removed. # . # If you're removing the ifetch-tools package in order to later install a # more recent version or if a different ifetch-tools package is already # using the data, logs, and settings, they should be kept. # d-i ifetch-tools/remove boolean false ############################ #### ifplugd_0.28-19.5_amd64.deb ############################ ### Description: static interfaces to be watched by ifplugd: # Specify the interfaces to control here, separated by spaces. Ifplugd # processes will be started for each of these interfaces when the ifplugd # initscript is called with the "start" argument. You may use the magic # string "auto" to make the initscript start or stop ifplugd processes for # ALL eth and wlan interfaces that are available according to # /proc/net/dev. Note that the list of interfaces appearing in # /proc/net/dev may depend on which kernel modules you have loaded. # . # You should not add interfaces that are hotplugged (USB or PCMCIA) here, # you will be asked for those in the next question. # d-i ifplugd/interfaces string ### Description: hotplugged interfaces to be watched by ifplugd: # Specify the hotplugged interfaces to control here, separated by spaces. # . # You may use the magic string "all" to make the hotplug script start an # ifplugd process for any hotplugged interface. # . # Hotplugged interfaces are usually interfaces on PCMCIA or WLAN adapters. # d-i ifplugd/hotplug_interfaces string ### Description: arguments to ifplugd: # You can give arguments to the ifplug daemon here. Relevant options are: # . # -q Don't run script on daemon quit # -f Ignore detection failure and retry # -u Specify delay for configuring interface # -d Specify delay for deconfiguring interface # -w Wait until daemon fork finished # -I Don't exit on nonzero return value of program executed # . # -a Do not enable interface automatically # -s Use stderr instead of syslog for debugging # -b Do not beep (-U/-D Do not beep on interface up/down) # -t Specify poll time in seconds (default: 1) # -p Don't run script on daemon startup # -l Run "down" script on startup if no cable is detected # -W Wait until the daemon died when running daemon is killed # -M Use interface monitoring # d-i ifplugd/args string -q -f -u0 -d10 -w -I ### Description: suspend behaviour: # When you put your notebook into suspend mode, you can choose between three # actions: # . # none: no action # . # suspend: this puts ifplugd into suspend mode. In this mode, ifplugd does # not check the link status. This is necessary for some broken network # drivers. # . # stop: this stops ifplugd. If the -q option is not given, ifplugd will stop # the interface. After resume, it will be restarted. This makes sense if you # use some mechanism (eg. guessnet or whereami) to detect your network # environment, which may have changed while suspending. # d-i ifplugd/suspend_action select stop # Possible choices: none, suspend, stop ############################ #### ifrench_1.4-30_all.deb ############################ ############################ #### ifrench-gut_1.0-32.2_amd64.deb ############################ ############################ #### wgaelic_0.50-13.1_all.deb ############################ ############################ #### ingerman_20161207-11_all.deb ############################ ############################ #### iswiss_20161207-11_all.deb ############################ ############################ #### wngerman_20161207-11_all.deb ############################ ############################ #### wswiss_20161207-11_all.deb ############################ ############################ #### igtf-policy-classic_1.118-1_all.deb ############################ ### Description: Trust IGTF classic CAs by default? # Trusted IGTF Certification Authority certificates are installed in # ${location}. # . # Accept this option to have certificates included by default unless they # are explicitly excluded. Reject it to choose the reverse policy, # excluding them unless explicitly included. # . # You will then have the opportunity to define the list of exceptions. # d-i igtf-policy-classic/install_profile boolean true ### Description: Certificates to explicitly exclude: # Please select which certificates should not be installed in # ${location}. # d-i igtf-policy-classic/exclude_ca multiselect # Possible choices: ${exclude_ca} ### Description: Certificates to explicitly include: # Please select which certificates should be installed in # ${location}. # d-i igtf-policy-classic/include_ca multiselect # Possible choices: ${include_ca} ### Description: Installation directory of the certificates: # The default location /etc/grid-security/certificates should # work fine in most cases. # . # An alternative location can be given here if needed. # d-i igtf-policy/location string /etc/grid-security/certificates ### Description: for internal use # This setting is for internal use by the configure script # and users should never see this question. It exists to ensure # proper cleanup if the location changes. # d-i igtf-policy/old-location string ############################ #### igtf-policy-iota_1.118-1_all.deb ############################ ### Description: Trust IGTF iota CAs by default? # Trusted IGTF Certification Authority certificates are installed in # ${location}. # . # Accept this option to have certificates included by default unless they # are explicitly excluded. Reject it to choose the reverse policy, # excluding them unless explicitly included. # . # You will then have the opportunity to define the list of exceptions. # d-i igtf-policy-iota/install_profile boolean true ### Description: Certificates to explicitly exclude: # Please select which certificates should not be installed in # ${location}. # d-i igtf-policy-iota/exclude_ca multiselect # Possible choices: ${exclude_ca} ### Description: Certificates to explicitly include: # Please select which certificates should be installed in # ${location}. # d-i igtf-policy-iota/include_ca multiselect # Possible choices: ${include_ca} ### Description: Installation directory of the certificates: # The default location /etc/grid-security/certificates should # work fine in most cases. # . # An alternative location can be given here if needed. # d-i igtf-policy/location string /etc/grid-security/certificates ### Description: for internal use # This setting is for internal use by the configure script # and users should never see this question. It exists to ensure # proper cleanup if the location changes. # d-i igtf-policy/old-location string ############################ #### igtf-policy-mics_1.118-1_all.deb ############################ ### Description: Trust IGTF mics CAs by default? # Trusted IGTF Certification Authority certificates are installed in # ${location}. # . # Accept this option to have certificates included by default unless they # are explicitly excluded. Reject it to choose the reverse policy, # excluding them unless explicitly included. # . # You will then have the opportunity to define the list of exceptions. # d-i igtf-policy-mics/install_profile boolean true ### Description: Certificates to explicitly exclude: # Please select which certificates should not be installed in # ${location}. # d-i igtf-policy-mics/exclude_ca multiselect # Possible choices: ${exclude_ca} ### Description: Certificates to explicitly include: # Please select which certificates should be installed in # ${location}. # d-i igtf-policy-mics/include_ca multiselect # Possible choices: ${include_ca} ### Description: Installation directory of the certificates: # The default location /etc/grid-security/certificates should # work fine in most cases. # . # An alternative location can be given here if needed. # d-i igtf-policy/location string /etc/grid-security/certificates ### Description: for internal use # This setting is for internal use by the configure script # and users should never see this question. It exists to ensure # proper cleanup if the location changes. # d-i igtf-policy/old-location string ############################ #### igtf-policy-slcs_1.118-1_all.deb ############################ ### Description: Trust IGTF slcs CAs by default? # Trusted IGTF Certification Authority certificates are installed in # ${location}. # . # Accept this option to have certificates included by default unless they # are explicitly excluded. Reject it to choose the reverse policy, # excluding them unless explicitly included. # . # You will then have the opportunity to define the list of exceptions. # d-i igtf-policy-slcs/install_profile boolean true ### Description: Certificates to explicitly exclude: # Please select which certificates should not be installed in # ${location}. # d-i igtf-policy-slcs/exclude_ca multiselect # Possible choices: ${exclude_ca} ### Description: Certificates to explicitly include: # Please select which certificates should be installed in # ${location}. # d-i igtf-policy-slcs/include_ca multiselect # Possible choices: ${include_ca} ### Description: Installation directory of the certificates: # The default location /etc/grid-security/certificates should # work fine in most cases. # . # An alternative location can be given here if needed. # d-i igtf-policy/location string /etc/grid-security/certificates ### Description: for internal use # This setting is for internal use by the configure script # and users should never see this question. It exists to ensure # proper cleanup if the location changes. # d-i igtf-policy/old-location string ############################ #### wirish_2.0-27.1_all.deb ############################ ############################ #### iitalian_2.3-3.1_amd64.deb ############################ ############################ #### im_153-4_all.deb ############################ ### Description: Use setuid imget for RPOP? # The RPOP feature is disabled by default. It is an obsolete feature (The # RPOP command was used instead of the PASS command to authenticate access # to a maildrop. It was removed in RFC 1460). If you prefer, you can use RPOP # by setuid imget. # d-i im/rpop boolean false ### Description: Generate /etc/im/SiteConfig by hand? # This package normally generates /etc/im/SiteConfig. If you prefer, you can # generate /etc/im/SiteConfig by hand. # d-i im/siteconfig_by_hand boolean false ### Description: Default From: domain: # In a mail/news header, if a From: field does not have a domain part, imput # will add this domain automatically. # . # If unsure, you can ignore this. # d-i im/fromdomain string ### Description: Default To: domain: # In a mail header, if a To: field does not have a domain part, imput will # add this domain automatically. # . # If unsure, you can ignore this. # d-i im/todomain string ### Description: Organization: # In a news header, imput will add an Organization: field automatically. # . # If unsure, you can ignore this. # d-i im/organization string ### Description: Use imget with maildir? # A maildir is not used by default. If you prefer, imget can retrieve mails # from ~/Maildir/{new,cur}. # d-i im/use_maildir boolean false ############################ #### wmanx_0.50-16.1_all.deb ############################ ############################ #### iodine_0.7.0-10+b1_amd64.deb ############################ ### Description: Should iodined (server) start on boot? # If you want iodined to be started at boot time you can set this behaviour here. # d-i iodine/start_daemon boolean false ### Description: Options to iodined (server): # You need to give the necessary arguments to iodined; see iodined(8) for help. # Example: 10.0.0.1 tunnel.mydomain.example # d-i iodine/daemon_options string ### Description: Password for iodined (server): # Enter the password iodined uses at startup. It has to be used by clients # when connecting. # This password will be stored in plain text in /etc/default/iodine. # d-i iodine/daemon_password password ############################ #### iog_1.03-6_all.deb ############################ ### Description: Migrate old install out of /var/www/iog/? # A previous package release has left data installed in the # /var/www/iog/ directory. Current versions of the IOG package now use # /var/lib/iog/ for IOG data files. # . # If you choose this option, all existing network data will be moved # to the new location. # . # Consequently, directory settings in the IOG configuration file # (/etc/iog.cfg) will be changed to /var/lib/iog and a web server # alias declaration will be added so that old network statistics # are still published. # d-i iog/migrate boolean false ############################ #### iperf3_3.12-1+deb12u1_amd64.deb ############################ ### Description: Start Iperf3 as a daemon automatically? # Choose this option if Iperf3 should start automatically as a daemon, # now and at boot time. # d-i iperf3/start_daemon boolean false ############################ #### ipolish_20220301-1_all.deb ############################ ############################ #### wpolish_20220301-1_all.deb ############################ ############################ #### iproute2_6.1.0-3_amd64.deb ############################ ### Description: Allow ordinary users to run ip vrf exec using capabilities? # iproute2 can be used to configure and use Virtual Routing and Forwarding (VRF) # functionality in the kernel. # This normally requires root permissions, but sometimes it's useful to allow # ordinary users to execute commands from inside a virtual routing and forwarding # domain. E.g. ip vrf exec examplevrf ping 10.0.0.1 # . # The ip command supports dropping capabilities, making an exception for ip vrf exec. # The drawback of setting the permissions is that if in the unlikely case of a # security critical bug being found before the ip command has dropped capabilities # then it could be used by an attacker to gain root permissions. # It's up to you to decide about the trade-offs and select the best setting for your # system. # This will give cap_dac_override, cap_net_admin and cap_sys_admin to /bin/ip. # . # More information about VRF can be found at: # https://www.kernel.org/doc/Documentation/networking/vrf.txt # d-i iproute2/setcaps boolean false ############################ #### ipset-persistent_1.0.20_all.deb ############################ ### Description: Save current ipsets? # Current ipsets can be saved to the configuration # file /etc/ipset/ipsets. These ipsets will then be loaded automatically # during system startup. # . # Sets are only saved automatically during package installation. See the # manual page of ip6tables-save(8) for instructions on keeping the rules file # up-to-date. # d-i ipset-persistent/autosave boolean true ############################ #### iptables-persistent_1.0.20_all.deb ############################ ### Description: Save current IPv4 rules? # Current iptables rules can be saved to the configuration # file /etc/iptables/rules.v4. These rules will then be loaded automatically # during system startup. # . # Rules are only saved automatically during package installation. See the # manual page of iptables-save(8) for instructions on keeping the rules file # up-to-date. # d-i iptables-persistent/autosave_v4 boolean true ### Description: Save current IPv6 rules? # Current iptables rules can be saved to the configuration # file /etc/iptables/rules.v6. These rules will then be loaded automatically # during system startup. # . # Rules are only saved automatically during package installation. See the # manual page of ip6tables-save(8) for instructions on keeping the rules file # up-to-date. # d-i iptables-persistent/autosave_v6 boolean true ############################ #### ircd-hybrid_8.2.43+dfsg.1-1_amd64.deb ############################ ### Description: Restart ircd-hybrid on each upgrade? # Please choose whether the ircd-hybrid daemon should be restarted # every time a new version of this package is installed. # . # Automatic restarts may be problematic if, for instance, the server is # running with manually loaded modules, which will need to be reloaded # after the restart. # . # If you reject this option, you will have to restart ircd-hybrid via # "service ircd-hybrid restart" when needed. # d-i ircd-hybrid/restart_on_upgrade boolean true ### Description: Automatically fix references to obsolete config options? # Several ssl configuration variables have been renamed to tls-like ones in # version 8.2.30, with some further changes to rename network_desc and # max_watch in 8.2.36, and dots_in_ident in 8.2.38. If enabled, the # post-installation script will attempt to automatically fix them before the # server is restarted. If not, and you have these options specified, the # configuration will become invalid, and server restart will fail. # d-i ircd-hybrid/automatically_fix_config boolean false ############################ #### ironic-api_21.1.0-3_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i ironic/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i ironic/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i ironic/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i ironic/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i ironic/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i ironic/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i ironic/api-endpoint-address string ### Description: This service endpoint protocol: # d-i ironic/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i ironic/api-endpoint-region-name string regionOne ############################ #### ironic-common_21.1.0-3_all.deb ############################ ### Description: Please select a list of Ironic drivers for this conductor to enable: # It is possible to activate multiple drivers per Ironic conductor node to # manage deployment and power. It is not mandatory to use the same list of # activated drivers across all of your ironic-conductor nodes. # d-i ironic/enabled_drivers multiselect pxe_ipmitool # Possible choices: pxe_ipmitool, pxe_ipminative, pxe_ssh, pxe_seamicro, pxe_iboot, pxe_ilo, pxe_drac, pxe_snmp ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i ironic/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i ironic/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i ironic/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i ironic/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i ironic/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i ironic/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i ironic/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i ironic/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i ironic/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i ironic/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i ironic/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i ironic/ksat-admin-password password ### Description: Auth server service username: # d-i ironic/ksat-service-username string ### Description: Auth server service project name: # d-i ironic/ksat-service-project-name string service ### Description: Auth server service password: # d-i ironic/ksat-service-password password ############################ #### ironic-inspector_11.1.0-2_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i ironic-inspector/configure_db boolean false ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i ironic-inspector/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i ironic-inspector/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i ironic-inspector/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i ironic-inspector/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i ironic-inspector/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i ironic-inspector/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i ironic-inspector/ksat-admin-password password ### Description: Auth server service username: # d-i ironic-inspector/ksat-service-username string ### Description: Auth server service project name: # d-i ironic-inspector/ksat-service-project-name string service ### Description: Auth server service password: # d-i ironic-inspector/ksat-service-password password ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i ironic-inspector/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i ironic-inspector/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i ironic-inspector/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i ironic-inspector/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i ironic-inspector/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i ironic-inspector/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i ironic-inspector/api-endpoint-address string ### Description: This service endpoint protocol: # d-i ironic-inspector/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i ironic-inspector/api-endpoint-region-name string regionOne ############################ #### sse3-support_15.1_amd64.deb ############################ ############################ #### sse4.1-support_15.1_amd64.deb ############################ ############################ #### sse4.2-support_15.1_amd64.deb ############################ ############################ #### isc-dhcp-relay_4.4.3-P1-2_amd64.deb ############################ ### Description: Servers the DHCP relay should forward requests to: # Please enter the hostname or IP address of at least one DHCP server # to which DHCP and BOOTP requests should be relayed. # . # You can specify multiple server names or IP addresses (in a # space-separated list). # d-i isc-dhcp-relay/servers string ### Description: Interfaces the DHCP relay should listen on: # Please specify which network interface(s) the DHCP relay should # attempt to configure. Multiple interface names should be entered as a # space-separated list. # . # Leave this field blank to allow for automatic detection and # configuration of network interfaces by the DHCP relay, in which case # only broadcast interfaces will be used (if possible). # d-i isc-dhcp-relay/interfaces string ### Description: Additional options for the DHCP relay daemon: # Please specify any additional options for the DHCP relay daemon. # . # For example: '-m replace' or '-a -D'. # d-i isc-dhcp-relay/options string ############################ #### isc-dhcp-server_4.4.3-P1-2_amd64.deb ############################ ### Description: Network interfaces on which the DHCP server should listen: # Please specify on which network interface(s) the DHCP server should # listen for DHCP requests. Multiple interface names should be entered # as a space-separated list. # . # The interfaces will be automatically detected if this field is left # blank. # d-i isc-dhcp-server/interfaces string ############################ #### isenkram-cli_0.51_all.deb ############################ ### Description: Packages to install: # Some packages were found to be useful with your hardware. # Please select those you want to install. # d-i isenkram/install_hw_packages multiselect # Possible choices: ${PACKAGES} ############################ #### isoqlog_2.2.1-9.1_amd64.deb ############################ ### Description: MTA log type: # Isoqlog has multi-mta support. You must select the logformat which is used by # your mail server. # d-i isoqlog/main_logtype select exim # Possible choices: qmail-multilog, qmail-syslog, postfix, sendmail, exim ### Description: Directory to use for HTML outputs: # Please choose the directory where isoqlog should write its output. It # must be in "WebRoot" of your webserver. # d-i isoqlog/main_outputdir string /var/www/isoqlog ### Description: Local host name: # d-i isoqlog/main_hostname string localhost ### Description: Language to use for outputs: # Isoqlog has multi language support on reports. You can select the # preferred language for outputs. # d-i isoqlog/main_langfile select English # Possible choices: Bulgarian, Czech, Danish, Dutch, English, Finnish, French, German, Italian, Norwegian, Polish, Portuguese, Romanian, Russian, Spanish, Swedish, Turkish ### Description: Domains for which you want to make reports: # Isoqlog can display Top incoming, outgoing, total, and byte based # statistics for each domain. Please enter the domains separated by spaces. # d-i isoqlog/main_domains string ############################ #### iamerican_3.4.05-1_all.deb ############################ ############################ #### iamerican-huge_3.4.05-1_all.deb ############################ ############################ #### iamerican-insane_3.4.05-1_all.deb ############################ ############################ #### iamerican-large_3.4.05-1_all.deb ############################ ############################ #### iamerican-small_3.4.05-1_all.deb ############################ ############################ #### ibritish_3.4.05-1_all.deb ############################ ############################ #### ibritish-huge_3.4.05-1_all.deb ############################ ############################ #### ibritish-insane_3.4.05-1_all.deb ############################ ############################ #### ibritish-large_3.4.05-1_all.deb ############################ ############################ #### ibritish-small_3.4.05-1_all.deb ############################ ############################ #### iczech_20040229-5.3_amd64.deb ############################ ############################ #### iestonian_20030606-32_all.deb ############################ ############################ #### ifaroese_0.4.2+repack1-4_all.deb ############################ ############################ #### wfaroese_0.4.2+repack1-4_all.deb ############################ ############################ #### igalician-minimos_0.5-48_all.deb ############################ ############################ #### wgalician-minimos_0.5-48_all.deb ############################ ############################ #### ilithuanian_1.3.2-3_all.deb ############################ ############################ #### itagalog_0.3.1-10_all.deb ############################ ############################ #### wukrainian_1.8.0+dfsg-1_all.deb ############################ ############################ #### iportuguese_20220621-1_all.deb ############################ ############################ #### wportuguese_20220621-1_all.deb ############################ ############################ #### jackd1_0.126.0-2_amd64.deb ############################ ### Description: Enable realtime process priority? # If you want to run jackd with realtime priorities, the user starting jackd # needs realtime permissions. Accept this option to create the # file /etc/security/limits.d/audio.conf, granting realtime # priority and memlock privileges to the audio group. # . # Running jackd with realtime priority minimizes latency, but # may lead to complete system lock-ups by requesting # all the available physical system memory, which is unacceptable in # multi-user environments. # d-i jackd/tweak_rt_limits boolean false ############################ #### jackd2_1.9.21~dfsg-3_amd64.deb ############################ ### Description: Enable realtime process priority? # If you want to run jackd with realtime priorities, the user starting jackd # needs realtime permissions. Accept this option to create the # file /etc/security/limits.d/audio.conf, granting realtime # priority and memlock privileges to the audio group. # . # Running jackd with realtime priority minimizes latency, but # may lead to complete system lock-ups by requesting # all the available physical system memory, which is unacceptable in # multi-user environments. # d-i jackd/tweak_rt_limits boolean false ############################ #### jalview_2.11.2.5+dfsg-3_all.deb ############################ ### Description: Automatically download identifiers from jalview.org? # Jalview can automatically download a list of identifiers.org URL templates # for viewing accessions from various biological databases. # . # This is a convenience for users but can be deactivated as it causes an # automatic ping to www.jalview.org/services/identifiers, which records usage # statistics. # . # Individual users can override this setting in their configuration file. # d-i jalview/identifiersservice boolean true ### Description: Automatically display news from jalview.org? # Jalview can automatically show updates from # https://www.jalview.org/feeds/desktop/rss in a popup window. # . # The news feed is informative to users but its retrieval pings www.jalview.org, # which records usage statistics. # . # If this is disabled, users may still manually open the news reader. # Users can also override this preference in the Preferences window or from their # own configuration file. # d-i jalview/news boolean true ### Description: Automatically check for questionnaires from jalview.org? # User questionnaires are posted from time to time on www.jalview.org, and # Jalview can automatically query the site to look for them on startup, in order # to prompt users to complete them. # . # Logs for the questionnaire service are used to record usage statistics, and # anonymised cookies are stored in the user's preferences to track whether they # have completed the latest questionnaire. # . # Users can enable or disable this query from their own configuration file, or # from the Preferences window in the application. # d-i jalview/questionnaire boolean true ### Description: Automatically discover JABA Web Services? # The JABAWS system (www.compbio.dundee.ac.uk/jabaws) provides access to a range # of third party multiple sequence alignment and analysis tools as web services. # . # Jalview can automatically query the public (or any other configured) JABAWS # services on startup. Otherwise, users will need to initiate discovery with a # menu option. # . # Users can enable or disable startup discovery from their own configuration # file or from the Preferences window in the application. # d-i jalview/jws2services boolean true ### Description: Automatically download HTML templates from Github? # Jalview can automatically download the latest "BioJS" HTML export template # from https://github.com/jalview/exporter-templates on startup. # . # This is a convenience for users but can be deactivated as it causes an # automatic ping to Github. # . # Individual users can override this setting in their configuration file. # d-i jalview/htmltemplates boolean true ############################ #### jove_4.17.5.1-2_amd64.deb ############################ ############################ #### kdump-tools_1.8.1_amd64.deb ############################ ### Description: Should kdump-tools be enabled by default? # If you choose this option, the kdump-tools mechanism will be # enabled. A reboot is still required in order to enable the # crashkernel kernel parameter. # d-i kdump-tools/use_kdump boolean true ############################ #### krb5-config_2.7_all.deb ############################ ### Description: Default Kerberos version 5 realm: # When users attempt to use Kerberos and specify a principal or user name # without specifying what administrative Kerberos realm that principal # belongs to, the system appends the default realm. The default realm # may also be used as the realm of a Kerberos service running on the # local machine. Often, the default # realm is the uppercase version of the local DNS domain. # d-i krb5-config/default_realm string ### Description: For internal use only # We want to try and capture user changes when they edit a config file # manually. To do this, we look in the config script to read the file. # However, in the case of preconfigure, the config script is run twice # before the postinst is run. Thus, we may read the wrong value before the # edited value is written out in postinst. If this is false, we skip # reading config files until postinst runs. # d-i krb5-config/read_conf boolean true ### Description: for internal use # d-i krb5-config/add_servers_realm string ### Description: Add locations of default Kerberos servers to /etc/krb5.conf? # Typically, clients find Kerberos servers for their default realm in # the domain-name system. ${dns} # d-i krb5-config/add_servers boolean false ### Description: Kerberos servers for your realm: # Enter the hostnames of Kerberos servers in the ${realm} Kerberos realm # separated by spaces. # d-i krb5-config/kerberos_servers string ### Description: Administrative server for your Kerberos realm: # Enter the hostname of the administrative (password changing) server for # the ${realm} Kerberos realm. # d-i krb5-config/admin_server string ############################ #### kexec-tools_2.0.25-3+b1_amd64.deb ############################ ### Description: Should kexec-tools handle reboots? # If you choose this option, a system reboot will trigger a restart # into a kernel loaded by kexec instead of going through the full # system boot loader process. # d-i kexec-tools/load_kexec boolean true ### Description: Read GRUB configuration file to load the kernel? # If you choose this option, kexec will read the GRUB configuration file to # determine which kernel and options to load for kexec reboot, as opposed # to what is in /etc/default/kexec. # d-i kexec-tools/use_grub_config boolean false ############################ #### keystone_22.0.0-2_all.deb ############################ ### Description: Set up a database for Keystone? # No database has been set up for Keystone to use. Before # continuing, you should make sure you have the following information: # . # * the type of database that you want to use; # * the database server host name (that server must allow TCP connections from this # machine); # * a username and password to access the database. # . # If some of these requirements are missing, do not choose this option and run with # regular SQLite support. # . # You can change this setting later on by running "dpkg-reconfigure -plow # keystone". # d-i keystone/configure_db boolean false ### Description: Register administration tenants? # For OpenStack to work, you need a basic tenant configuration. The # creation of these administration tenants can be done automatically. # d-i keystone/create-admin-tenant boolean false ### Description: Username of the administrative user: # Please enter a username for the administrative user. # d-i keystone/admin-user string admin ### Description: Email address of the administrative user: # Please enter the email address of the administrative user. # d-i keystone/admin-email string root@localhost ### Description: Password of the administrative user: # Please enter a password for the administrative user. # d-i keystone/admin-password password ### Description: Re-enter password to verify: # Please enter the same administrative password again to verify that you have typed it # correctly. # d-i keystone/admin-password-confirm password ### Description: Name of the administrative role: # Please enter the name of the administrative role. # d-i keystone/admin-role-name string admin ### Description: Name of the administrative tenant: # Please enter the name of the administrative tenant. # d-i keystone/admin-tenant-name string admin ### Description: Register Keystone endpoint? # Each OpenStack service (each API) should be registered in order to be # accessible. This is done using "keystone service-create" and "keystone # endpoint-create". This can be done automatically now. # d-i keystone/register-endpoint boolean false ### Description: Keystone endpoint IP address: # Please enter the IP address or hostname that will be used to contact Keystone. # d-i keystone/endpoint-ip string ### Description: Endpoint protocol: # d-i keystone/endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using availability zones, with each region representing # a location. Please enter the zone that you wish to use when registering the # endpoint. # d-i keystone/region-name string regionOne ############################ #### kinput2-canna-wnn_3.1-14_amd64.deb ############################ ### Description: Default system keybindings of Kinput2 for Wnn # Debian prepackaged version of Kinput2 provides a functionality to select # default keybindings of Kinput2 for Wnn from "Kinput2" and "Egg". Although # the former is the original keybindings of Kinput2, Egg on Emacs users may # prefer the latter. # d-i shared/kinput2/wnn/keybindings select Egg # Possible choices: Kinput2, Egg ############################ #### kinput2-wnn_3.1-14_amd64.deb ############################ ### Description: Default system keybindings of Kinput2 for Wnn # Debian prepackaged version of Kinput2 provides a functionality to select # default keybindings of Kinput2 for Wnn from "Kinput2" and "Egg". Although # the former is the original keybindings of Kinput2, Egg on Emacs users may # prefer the latter. # d-i shared/kinput2/wnn/keybindings select Egg # Possible choices: Kinput2, Egg ############################ #### knews_1.0b.1-35_amd64.deb ############################ ### Description: What news server should be used for reading and posting news? # knews is configured to read news via an NNTP connection, and needs to know # the fully-qualified host name of the server (such as news.example.com). If # you have a local news spool, you should consider installing some NNTP # server like inn2; in that case, enter "localhost" as your news server. # d-i shared/news/server string ### Description: What is your system's mail name? # Please enter the 'mail name' of your system. This is the hostname portion # of the address to be shown on outgoing news and mail messages, and is used # by many packages. # d-i knews/mail-name string ############################ #### knot-resolver_5.6.0-1_amd64.deb ############################ ############################ #### krb5-admin-server_1.20.1-2+deb12u1_amd64.deb ############################ ############################ #### krb5-kdc_1.20.1-2+deb12u1_amd64.deb ############################ ### Description: Create the Kerberos KDC configuration automatically? # The Kerberos Key Distribution Center (KDC) configuration files, in # /etc/krb5kdc, may be created automatically. # . # By default, an example template will be copied into this directory # with local parameters filled in. # . # Administrators who already have infrastructure to manage their # Kerberos configuration may wish to disable these automatic # configuration changes. # d-i krb5-kdc/debconf boolean true ### Description: Should the KDC database be deleted? # By default, removing this package will not delete the KDC database in # /var/lib/krb5kdc/principal since this database cannot be recovered once # it is deleted. # . # Choose this option if you wish to delete the KDC database now, deleting # all of the user accounts and passwords in the KDC. # d-i krb5-kdc/purge_data_too boolean false ############################ #### kwartz-client_2.1-2_all.deb ############################ ### Description: URI ("Uniform Resource Identifier") of the LDAP server: # Please enter the URI of the LDAP server provided by your Kwartz machine. # You can use a numeric IP address rather than a symbolic one, in order to # minimize failure possibilities when the name service is down. # . # It is possible to specify multiple LDAP URIS, separated by spaces. # d-i kwartz/ldapuri string ldap://serveur.lycee.jb/ ### Description: LDAP's Base DN ("Distinguished Name"): # Please enter the DN ("Distinguished Name") used as the base of the LDAP # service. Many systems use the elements of their domain name for this purpose. # For example, the domain "example.net" would use "dc=example, dc=net". # d-i kwartz/ldapbase string dc=lycee,dc=jb ### Description: DN ("Distinguished Name") of one user: # Please enter the DN ("Distinguished Name") of one unprivileged user # already existing in the LDAP directory. Kwartz requires that requests come # from an existing user before replying anything. # d-i kwartz/user string cn=personne,cn=Users,dc=lycee,dc=jb ### Description: Password of the unprivileged user: # Please enter the password of the unprivileged user. Kwartz requires # that requests come from an existing user before replying anything. # This password should not be disclosed, and should be fairly strong. # d-i kwartz/userpassword password ### Description: The Samba name of the kwartz server: # Please enter the Samba name of the kwartz server; this is the name of # the server, as seen in Windows' neighborhood. # d-i kwartz/servername string SERVEUR ### Description: The IP address of the Cloud service, if any: # Please enter the IP address of the Cloud server. It may be the address of the # main server, as seen from the Internet (not the address in the local network). # If there is no such service, you can safely keep the default. # d-i kwartz/cloud_ip string kwartz.lyceejeanbart.fr ### Description: The IP address of the kwartz server, in the LAN: # A kwartz server has at least two networks connections, one for the # Internet, and the other one for the local network. Here you can type # the name as it appears in the directory service in use; i.e. if the # LDAP URI of the directory service is "ldap://serveur.lycee.jb/" you # can type: "serveur.lycee.jb" or an equivalent numeric IP address. # d-i kwartz/alt_ip string serveur.lycee.jb ### Description: The port used to access https services of the Cloud: # https services are usually bound to the port number 443. However the # Cloud service may be bound to some other port number. If there is no # cloud service, you can safely keep the default value. # d-i kwartz/tls_port string 8443 ### Description: The path used to get the DAVS service: # this is the end of the URL used to access the DAVS service featured by the # Cloud. If the cloud is powered by Owncloud, the default value is probably # good. If there is no cloud service, you can safely keep the default value. # d-i kwartz/davpath string owncloud/remote.php/webdav ############################ #### lava-server_2023.01-2_all.deb ############################ ### Description: Remove V1 data from database? # If you continue this upgrade, all V1 test data will be # permanently DELETED. # . # V2 test data will not be affected. If you have remaining # V1 test data that you care about, make sure it is backed # up before you continue here. # d-i lava-server/removev1 boolean true ############################ #### lcl-utils-2.2_2.2.6+dfsg2-2_amd64.deb ############################ ### Description: Rename "/etc/lazarus" to "/etc/lazarus.bak"? # The Lazarus suite now supports keeping multiple versions installed # at the same time and using the alternatives system to set proper # defaults. Normally, the latest version of any component is used. # . # To use the alternatives system on the system-wide configuration # of the Lazarus suite, /etc/lazarus needs to be under control of the # alternatives system. Currently there is a real directory at # /etc/lazarus, probably from a previous installation. In order to # start using the alternatives system on the configuration you must # accept renaming "/etc/lazarus". If you don't, you will need to # review the configuration on every version update of Lazarus as, # unfortunately, the configuration files are not always # backward-compatible. Also switching between different versions # might need more intervention. # . # If you have made changes to your configuration files, you will # probably need to review them and apply them to all versioned # configurations, as they will not automatically propagate. # d-i lcl-utils-2.2/rename_cfg boolean true ############################ #### lcdproc_0.5.9-6+b2_amd64.deb ############################ ### Description: Perform automatic configuration upgrade ? # lcdproc configuration can be merged automatically by cme # during package upgrade. This process will keep your # configuration customization, apply maintainer's changes and write back # the configuration files. # . # You can later edit lcdproc configuration with the command # 'sudo cme edit lcdproc'. # . # If you decline this option, you must then copy the original configuration # file(s) from /usr/share/doc/lcdproc to /etc. This file will # not be managed by Debian package manager. # d-i lcdproc/auto-upgrade-config boolean true ############################ #### ldap-account-manager_8.3-1_all.deb ############################ ### Description: Web server configuration: # LDAP Account Manager supports any webserver that supports PHP, but this # automatic configuration process only supports Apache2. # If you choose to configure Apache2 then LAM can be accessed at http(s)://localhost/lam # d-i ldap-account-manager/config-webserver multiselect apache2 # Possible choices: apache2 ### Description: Alias name: # LAM will add an alias to your httpd.conf which allows you to # access LAM at http(s)://localhost/lam. You may select an alias other than # "lam". # d-i ldap-account-manager/alias string lam ### Description: Would you like to restart your webserver(s) now? # Your webserver(s) need to be restarted in order to apply the changes. # d-i ldap-account-manager/restart-webserver boolean true ############################ #### ldh-gui-suite_0.1~20200908-6_all.deb ############################ ### Description: Liberty Deckplan Host: # The "Liberty Deckplan Host" (LDH) is a single domain # implementing the concrete configuration plan # defined at . # . # This name will also be used by other programs. # It should be the single, fully qualified domain name (FQDN). # . # Leave blank to use a default value (currently "${defaultvalue}"), # and to permit eventual automatic change of that value without asking. # d-i one.liberty/domain string ### Description: Descriptive name for Liberty Deckplan Host service Hub: # "Hub" is a service to manage your Liberty Deckplan Host account. # . # This descriptive name will also be used by other programs. # It should be a short string usable within a longer description sentence. # . # Leave blank to use a default value (currently "${defaultvalue}"), # and to permit eventual automatic change of that value without asking. # d-i one.liberty/hub/name string ### Description: URI for Liberty Deckplan Host service Hub: # "Hub" is a service to manage your Liberty Deckplan Host account, # online accessible at this URI. # . # This URI will also be used by other programs. # It should be the single Uniform Resource Identifier (URI). # . # Leave blank to use a default value (currently "${defaultvalue}"), # and to permit eventual automatic change of that value without asking. # d-i one.liberty/hub/uri string ### Description: URI for Liberty Deckplan Host service Chat: # "Chat" is a microblogging service part of Liberty Deckplan Host. # . # This URI will also be used by other programs. # It should be the single Uniform Resource Identifier (URI). # . # Leave blank to use a default value (currently "${defaultvalue}"), # and to permit eventual automatic change of that value without asking. # d-i one.liberty/chat/uri string ### Description: URI for Liberty Deckplan Host service Social: # "Social" is a microblogging service part of Liberty Deckplan Host. # . # This URI will also be used by other programs. # It should be the single Uniform Resource Identifier (URI). # . # Leave blank to use a default value (currently "${defaultvalue}"), # and to permit eventual automatic change of that value without asking. # d-i one.liberty/social/uri string ############################ #### leafnode_1.12.0-2_amd64.deb ############################ ### Description: Server to download news from: # The name of the news server should be provided by the organization # providing you with network access, such as your Internet Service # Provider. # . # This server is generally called "news." or "nntp." # where is the local domain name. # d-i leafnode/server string news ### Description: Enable access controls for Leafnode? # If you do not enable some access controls for Leafnode, people everywhere # will be able to use the news server which opens opportunities # for spamming or resource abuse. # . # Access controls will prevent computers other than the news server # itself reading or posting to newsgroups using the server. If required # access can be granted to other computers by editing /etc/hosts.allow. # d-i leafnode/tcpd boolean true ### Description: Network connection type: # The Leafnode package can automatically download news. # . # The method used for this depends on the network connection type. # Scripts provided with the package support two network connection types: # - permanent: hourly news downloads; # - PPP : news downloads triggered by dialouts. # . # Either option will work for a dial-on-demand network connection. # . # Choosing 'none' will disable automatic news downloads. News # can be downloaded manually by running 'fetchnews'. # d-i leafnode/network select PPP # Possible choices: PPP, permanent, none ### Description: Update the list of available groups? # Leafnode updates the list of available newsgroups when # it checks for new news. No newsgroups will be available until this has # happened at least once. # . # If you choose to update the list of groups immediately, # newsgroups will be available to clients as soon as Leafnode has been # set up. # d-i leafnode/update-groups boolean true ### Description: Remove news groups and articles when purging the package? # The /var/spool/news directory holds the database of news articles # downloaded by Leafnode. Many other news servers also use this # directory to store their news database and you may wish to keep it # even when removing the leafnode package. # d-i leafnode/purge boolean false ############################ #### ledgersmb_1.6.33+ds-2.1_all.deb ############################ ### Description: Database administrative user login: # Please enter the login of the LedgerSMB database administrative user. This # login is needed for the administrative web user interface, typically at # http://localhost:5762/setup.pl. # d-i ledgersmb/admin_login string lsmb_dbadmin ### Description: Database administrative user password: # Please enter the password of the LedgerSMB database administrative user. This # password is needed for the administrative web user interface, typically at # http://localhost:5762/setup.pl. # d-i ledgersmb/admin_password password LEDGERSMBINITIAL ### Description: Web Reverse Proxy to configure? # The LedgerSMB application now defaults to being made available on port 5762, # and being run directly by Starman. If other access is needed, a Reverse Proxy # can be configured using Apache or Nginx or Lighttpd or Varnish, or you can # leave the choice as None if it is not needed or if the web proxy will be set # up remotely. # . # For more details, please see the Web Proxy section that can be found in the # /usr/share/doc/ledgersmb/README.Debian file. # d-i ledgersmb/lsmb_proxy select None # Possible choices: ${lsmbproxy}, None, Apache, Lighttpd, Nginx, Varnish ############################ #### liblemonldap-ng-common-perl_2.16.1+ds-deb12u2_all.deb ############################ ### Description: LDAP server: # Set here name or IP address of the LDAP server that has to be used by # Lemonldap::NG. # You can modify this value later using the Lemonldap::NG manager. # d-i liblemonldap-ng-common-perl/ldapServer string localhost ### Description: Lemonldap::NG DNS domain: # Set here the main domain protected by Lemonldap::NG. # You can modify this value later using the Lemonldap::NG manager. # d-i liblemonldap-ng-common-perl/domain string example.com ### Description: Lemonldap::NG portal: # Set here the Lemonldap::NG portal URL. # You can modify this value later using the Lemonldap::NG manager. # d-i liblemonldap-ng-common-perl/portal string http://auth.example.com/ ### Description: LDAP server port: # Set here the port used by the LDAP server. # You can modify this value later using the Lemonldap::NG manager. # d-i liblemonldap-ng-common-perl/ldapPort string 389 ### Description: LDAP search base: # Set here the search base to use in LDAP queries. # You can modify this value later using the Lemonldap::NG manager. # d-i liblemonldap-ng-common-perl/ldapBase string dc=example,dc=com ### Description: LDAP account: # Set here the account that Lemonldap::NG has to use for its LDAP requests. # Leaving it blank causes Lemonldap::NG to use anonymous connections. # You can modify this value later using the Lemonldap::NG manager. # d-i liblemonldap-ng-common-perl/managerDn string ### Description: LDAP password: # Set here the password for the Lemonldap::NG LDAP account. # You can modify this value later using the Lemonldap::NG manager. # d-i liblemonldap-ng-common-perl/managerPassword string ### Description: Lemonldap::NG configuration files have changed, try to migrate your files? # d-i liblemonldap-ng-common-perl/migrate boolean ############################ #### libapache-sessionx-perl_2.01-5_all.deb ############################ ### Description: for internal use only # Keys used to find configured stores. # d-i libapache-sessionx-perl/priv_keys string ### Description: Action: # Choose "Add New" to add a new session storage method, or choose an already # configured store to modify or delete it. # . # Choose "Finished" when done. # d-i libapache-sessionx-perl/action select Finished # Possible choices: Finished, Add New, ${stores} ### Description: Action to perform on ${store}: # d-i libapache-sessionx-perl/store_action select Modify # Possible choices: Modify, Delete ### Description: Session storage method: # Please select the storage method you wish to use: # File: File-based, using semaphores for locking. # FileFile: File-based, using lockfiles. # DB_File: DBM file storage, using lockfiles. # Mysql: MySQL storage, using semaphores for locking. # MysqlMysql: MySQL storage, using MySQL for locking. # Oracle: Oracle storage and locking. # Sybase: Sybase storage and locking. # Postgres: PostgreSQL storage and locking. # . # The file-based methods are the simplest to configure, but don't scale to # the needs of a high-volume site. # . # Semaphore locking is faster than file-based locking, but cannot be shared # between multiple hosts; in such a situation, you probably should be using # one of the database backends anyway. # d-i libapache-sessionx-perl/store_type select # Possible choices: File, FileFile, DB_File, Mysql, MysqlMysql, Oracle, Sybase, Postgres ### Description: Store name: # Please choose the name you will use when referring to this storage method. # d-i libapache-sessionx-perl/store_name string ### Description: File storage directory: # Please choose the directory in which to store session data. Each # session will be a new file in this directory. # d-i libapache-sessionx-perl/store_file_directory string ### Description: Lockfile storage directory: # Please choose the directory in which to store session locks. Each # lock is a new file in this directory. # . # The filenames are chosen such that they will not conflict with session # data, so you may repeat a file storage directory here. # d-i libapache-sessionx-perl/store_file_lockdirectory string ### Description: Database file: # Please enter the DBM file used to store sessions. # d-i libapache-sessionx-perl/store_dbfile_filename string ### Description: MySQL data source: # Please choose the MySQL data source used for storing session data, in # the form of a Perl DBI DSN (see the DBI manpage). # . # The general form is "dbi:mysql:". See the DBD::mysql manpage for # more details. # d-i libapache-sessionx-perl/store_mysql_datasource string dbi:mysql:sessions ### Description: MySQL username: # Please enter the username used to access the session database. If # left blank, the current user's login will be used. # d-i libapache-sessionx-perl/store_mysql_username string ### Description: MySQL password: # Please enter the password used to access the session database. May be # left blank if no password is needed. # d-i libapache-sessionx-perl/store_mysql_password password ### Description: MySQL lock data source: # Please enter the MySQL data source used for locking, in the form of a # Perl DBI DSN (see the DBI manpage). Locking is performed using # MySQL's GET_LOCK and RELEASE_LOCK functions. # . # The general form is "dbi:mysql:". See the DBD::mysql manpage for # more details. # . # You will almost certainly want to use the same value you used for the # session data. # d-i libapache-sessionx-perl/store_mysql_lockdatasource string dbi:mysql:sessions ### Description: MySQL username for locking: # Please enter the username used to access the database for locking. If # left blank, the current user's login will be used. # d-i libapache-sessionx-perl/store_mysql_lockusername string ### Description: MySQL password for locking: # Please enter the password used to access the database for # locking. May be left blank if no password is needed. # d-i libapache-sessionx-perl/store_mysql_lockpassword password ### Description: Oracle data source: # Please enter the Oracle data source used for storing session data, in # the form of a Perl DBI DSN (see the DBI manpage). The general # form is "dbi:Oracle:". See the DBD::Oracle manpage for more # details. # d-i libapache-sessionx-perl/store_oracle_datasource string dbi:Oracle:sessions ### Description: Oracle username: # Please enter the username used to access the session database. If # left blank, the current user's login will be used. # d-i libapache-sessionx-perl/store_oracle_username string ### Description: Oracle password: # Please enter the password used to access the session database. May be left blank if no # password is needed. # d-i libapache-sessionx-perl/store_oracle_password password ### Description: Sybase data source: # Please enter the Sybase data source used for storing session data, in # the form of a Perl DBI DSN (see the DBI manpage). # . # The general form is "dbi:Sybase:database=;server=". See # the DBD::Sybase manpage for more details. # d-i libapache-sessionx-perl/store_sybase_datasource string dbi:Sybase:database=sessions ### Description: Sybase username: # Please enter the username used to access the session database. If # left blank, the current user's login will be used. # d-i libapache-sessionx-perl/store_sybase_username string ### Description: Sybase password: # Please enter the password used to access the session database. May be # left blank if no password is needed. # d-i libapache-sessionx-perl/store_sybase_password password ### Description: PostgreSQL data source: # Please enter the PostgreSQL data source used for storing session # data, in the form of a Perl DBI DSN (see the DBI manpage). # . # The general form is "dbi:Pg:dbname=;host=". See the # DBD::Pg manpage for more details. # d-i libapache-sessionx-perl/store_postgres_datasource string dbi:Pg:dbname=sessions ### Description: PostgreSQL username: # Please enter the username used to access the session database. If left blank, the current # user's login will be used. # d-i libapache-sessionx-perl/store_postgres_username string ### Description: PostgreSQL password: # Please enter the password used to access the session database. May be # left blank if no password is needed. # d-i libapache-sessionx-perl/store_postgres_password password ### Description: Default storage method: # Please choose the storage method that will be used by default if you # don't specify a particular storage method at run time. # d-i libapache-sessionx-perl/default_store select # Possible choices: ${stores} ############################ #### libcifpp-data_5.0.7.1-1_all.deb ############################ ### Description: Should mmcif_pdbx files be updated automatically? # The default mmcif_pdbx.dic file may become out-of-date over time. # Using this option you can enable automatic weekly updating of this file. # d-i libcifpp/update boolean ############################ #### libgcr410_2.4.0-9.3_amd64.deb ############################ ### Description: Serial port to which the smartcard reader is connected: # The driver needs to know to which serial port the GemPlus GCR410 reader is # connected. # d-i libgcr410/port select # Possible choices: ttyS0, ttyS1, ttyS2, ttyS3 ############################ #### libpaper1_1.1.29_amd64.deb ############################ ### Description: System's default paper size: # Please select the default paper size for the system. # Various programs on the system will use this configuration option to # determine how to print output. # d-i libpaper/defaultpaper select # Possible choices: letter, a4, note, legal, executive, halfletter, halfexecutive, 11x17, statement, folio, quarto, 10x14, ledger, tabloid, a0, a1, a2, a3, a5, a6, a7, a8, a9, a10, b0, b1, b2, b3, b4, b5, c5, DL, Comm10, Monarch, archE, archD, archC, archB, archA, flsa, flse, csheet, dsheet, esheet ############################ #### libvirt-daemon-system_9.0.0-4_amd64.deb ############################ ### Description: Continue with incorrect libvirt-qemu user/group ID(s)? # The user/group ID (uid/gid) allocated for libvirt-qemu (64055) # seems to be taken by another user/group, thus it is not possible # to create the user/group with this numeric ID. # . # The migration of guests with disk image files shared over NFS # requires a static libvirt-qemu user and group ID (uid and gid) # between the source and destination host systems. # . # If guest migration over NFS is not required, you can continue # the installation. # . # In order to resolve this problem, do not continue the installation, # release the 64055 uid/gid (which might involve permission changes), # then install this package again. # d-i libvirt-daemon-system/id_warning boolean true ############################ #### libwiki-toolkit-perl_0.86-1_all.deb ############################ ### Description: Install version of Wiki::Toolkit requiring schema upgrade? # You are about to install a version of Wiki::Toolkit which requires a # database schema upgrade. Until you have run the upgrade procedure on # Wiki::Toolkit databases, this will cause applications using Wiki::Toolkit # to stop working. # . # If your Wiki::Toolkit application installed an upgrade hook, this upgrade # procedure will optionally run this hook to automatically upgrade the # database(s) belonging to this application. # d-i libwiki-toolkit-perl/schema_upgrade_warn boolean ### Description: Automatically upgrade Wiki::Toolkit databases? # Upgrade hooks provided by Wiki::Toolkit applications have been found. # They can be run after the package upgrade completes to automatically # upgrade the relevant databases. # . # It is recommended that you backup your Wiki::Toolkit databases before # upgrading them. # d-i libwiki-toolkit-perl/schema_upgrade_auto boolean ############################ #### lightdm_1.26.0-8_amd64.deb ############################ ### Description: for internal use only # d-i lightdm/daemon_name string /usr/sbin/lightdm ### Description: Default display manager: # A display manager is a program that provides graphical login capabilities for # the X Window System. # . # Only one display manager can manage a given X server, but multiple display # manager packages are installed. Please select which display manager should # run by default. # . # Multiple display managers can run simultaneously if they are configured to # manage different servers; to achieve this, configure the display managers # accordingly, edit each of their init scripts in /etc/init.d, and disable the # check for a default display manager. # d-i shared/default-x-display-manager select # Possible choices: ${choices} ############################ #### linux-base_4.9_all.deb ############################ ### Description: Abort kernel removal? # You are running a kernel (version ${running}) and attempting to remove # the same version. # . # This can make the system unbootable as it will remove # /boot/vmlinuz-${running} and all modules under the directory # /lib/modules/${running}. This can only be fixed with a copy of the # kernel image and the corresponding modules. # . # It is highly recommended to abort the kernel removal unless you are # prepared to fix the system after removal. # d-i linux-base/removing-running-kernel boolean true ############################ #### localepurge_0.7.3.10_all.deb ############################ ### Description: Locale files to keep on this system: # The localepurge package will remove all locale files from the system # except those that you select here. # . # When selecting the locale corresponding to your language and country # code (such as "de_DE", "de_CH", "it_IT", etc.) it is recommended to # choose the two-character entry ("de", "it", etc.) as well. # . # Entries from /etc/locale.gen will be preselected # if no prior configuration has been successfully completed. # d-i localepurge/nopurge multiselect # Possible choices: ${locales} ### Description: Use dpkg --path-exclude? # dpkg supports --path-exclude and --path-include options to filter files # from packages being installed. # . # Please see /usr/share/doc/localepurge/README.dpkg-path for more # information about this feature. It can be enabled (or disabled) # later by running "dpkg-reconfigure localepurge". # . # This option will become active for packages # unpacked after localepurge has been (re)configured. Packages # installed or upgraded together with localepurge may (or may not) be # subject to the previous configuration of localepurge. # d-i localepurge/use-dpkg-feature boolean true ### Description: Really remove all locales? # No locale has been chosen for being kept. This means that all locales will be # removed from this system. Please confirm whether this is really your # intent. # d-i localepurge/none_selected boolean false ### Description: Also delete localized man pages? # Based on the same locale information you chose, localepurge can also # delete localized man pages. # d-i localepurge/mandelete boolean true ### Description: Inform about new locales? # If you choose this option, you will be given the opportunity # to decide whether to keep or delete newly introduced locales. # . # If you don't choose it, newly introduced locales will be # automatically dropped from the system. # d-i localepurge/dontbothernew boolean false ### Description: Display freed disk space? # The localepurge program can display the disk space freed by each # operation, and show a final summary of saved disk space. # d-i localepurge/showfreedspace boolean true ### Description: Accurate disk space calculation? # There are two ways available to calculate freed disk space. One is # much faster than the other but far less accurate if other changes occur # on the file system during disk space calculation. The other one is more # accurate but slower. # d-i localepurge/quickndirtycalc boolean true ### Description: Display verbose output? # The localepurge program can be configured to explicitly show which # locale files it deletes. This may cause a lot of screen output. # d-i localepurge/verbose boolean false ############################ #### logtool_1.2.8-11_amd64.deb ############################ ### Description: Manual configuration of logtool's database? # Logtool needs a database with regular expressions that describe logfile # entries that should be ignored, or considered less important. You can # write this database manually, or use the very flexible database in the # package logcheck-database for this purpose. # . # If you choose to use logcheck-database and already added values to the # files in /etc/logtool, these files will be replaced by symbolic links in # the logcheck database (although backups will be preserved). Make sure this # is not unwanted behaviour. # . # Reply positively to manually write a database, or negatively to use the # database from the package "logcheck-database". # . # Note: since logtool does not depend on this database (but instead # Recommends it), the default answer to this question is to manually # configure the database. # d-i logtool/manual boolean true ### Description: Ignored template # No longer used template (although its value is read for upgrade purposes), # no need to translate it. # d-i logtool/ignore-start select paranoid # Possible choices: paranoid, server, workstation ### Description: Do you want to use the '${level}' level regular expressions? # The database in the logcheck-database package defines three levels: # paranoid, server, and workstation; and it also has a database for cracking, # violations, and ignored violations ('violations-ignore'). Logcheck allows you # to pick one of the levels, and ignores the rest. # . # Logtool, on the other hand, can use multiple databases, which either # specify lines that should be completely excluded from output # (/etc/logtool/exclude) or lines that should be given a specific color # (green, yellow, blue, magenta, cyan, brightcyan). There is also the # possibility to not create an exclude file, and use an 'include' style of # file instead; its use is not recommended. Last but not least, files that # are not excluded from output but that do not match any other regular # expression are colored red. # . # If you want to map the '${level}' level database of regular expressions to # one of the above specified options, then answer positively to this # question. # d-i logtool/use-level boolean true ### Description: What do you want the ${level} level of regular expressions to do? # Please specify what you want to do with a line if it matches at least one # of the regular expressions in the ${level} level database. You have the # following options (note that regular expressions are matched on a # line-per-line basis): # . # * exclude: discard matching lines # * include: discard all but matching lines. Not recommended. Note that # this is mutually exclusive with 'exclude'. # * green, yellow, blue, magenta, cyan, brightcyan: give matching lines # the specified color. # . # Note that each option can be specified for only one of paranoid, # server, or workstation. # d-i logtool/map-level-to-file select # Possible choices: exclude, include, green, yellow, blue, magenta, cyan, brightcyan ############################ #### lprng_3.8.B-6_amd64.deb ############################ ### Description: Make lpr, lprm and lpq setuid root? # For full RFC1179 compliance you need to make these programs setuid root. # This is mainly so they can create a socket with a low port number. The low # port number may be important if you have network printers or have adjusted # /etc/lprng/lpd.perms to restrict access to non-privledged ports. For the # typical printer connected locally to parallel port (and many other) # scenario you can leave these programs non setuid root. # d-i lprng/setuid_tools boolean false ### Description: Start lpd (Printer Daemon) at boot? # Some people for various reasons do not want to start lpd. Refusing this # option means lpd will not start. Unless you know why you want lpd # not to start, just accept the default. # d-i lprng/start_lpd boolean true ############################ #### lsh-server_2.1-13+b1_amd64.deb ############################ ### Description: lsh server port: # The default port for lshd is 22. If lshd should run on a different port, # please specify the alternative port here. If you specify 22, you will # need to manually disable any other SSH servers running on port 22, other # than OpenSSH (from the package openssh-server), which will be disabled # automatically if you choose 22 here. # d-i lsh-server/lshd_port string 22 ### Description: Enable the SFTP subsystem? # Please choose whether you want to use the EXPERIMENTAL lsh SFTP support. # . # Since it is experimental, the default is for it to be disabled, but it # can be enabled now or later by manually changing /etc/default/lsh-server. # d-i lsh-server/sftp boolean false ### Description: Remove host key on purge? # When this package is installed, a host key is generated to authenticate # your host. # . # Please choose whether you want to purge the host key when the package # is removed. # d-i lsh-server/purge_hostkey boolean true ### Description: Additional arguments to pass to lshd: # d-i lsh-server/extra_args string ############################ #### lxc_5.0.2-1+deb12u2_amd64.deb ############################ ### Description: Auto update lxc2 configuration format to lxc3? # LXC 3 comes with many changes for containers' configuration files. # It also comes with a binary `/usr/bin/lxc-update-config` that allows # one to update his configuration. # . # This job can be done either automatically now or manually later. # . # Unpriviledged containers configurations will have to be updated manually # either way via the `/usr/bin/lxc-update-config` command. # d-i lxc/auto_update_config boolean ############################ #### lxdm_0.5.3-4_amd64.deb ############################ ### Description: Default display manager: # A display manager is a program that provides graphical login capabilities for # the X Window System. # . # Only one display manager can manage a given X server, but multiple display # manager packages are installed. Please select which display manager should # run by default. # . # Multiple display managers can run simultaneously if they are configured to # manage different servers; to achieve this, configure the display managers # accordingly, edit each of their init scripts in /etc/init.d, and disable the # check for a default display manager. # d-i shared/default-x-display-manager select # Possible choices: ${choices} ############################ #### lyskom-elisp-client_0.48+git.20200923.ec349ff4-3_all.deb ############################ ### Description: Exclude non-English servers from default server list? # The LysKOM Elisp Client normally comes with a default server list that # includes one server for communication in English, one Finnish server and a # dozen Swedish servers. If you don't know Swedish (or Finnish), you # will have little or no use for those servers. # d-i lyskom-elisp-client/server-list-query boolean true ############################ #### lyskom-server_2.1.2-16+b3_amd64.deb ############################ ### Description: Language of initial database: # The LysKOM server comes with two pre-defined databases, one with English # names for conferences and the administrator account, and one in Swedish. # Please select the one you want to install on your machine. # . # The database is only installed once, and when you have installed it you # cannot switch. You can, of course, rename the conferences and accounts if # you wish. # d-i lyskom-server/language select English # Possible choices: English, Swedish ### Description: Password for the pre-defined administrator account: # Please enter the password for the initial person with full # administrative rights, "Administrator (of) LysKOM". If you leave it # blank, it will default to "gazonk". # d-i lyskom-server/admin-password password ### Description: Confirm password: # Please enter the password again to verify. # d-i lyskom-server/admin-password-repeat password ############################ #### macchanger_1.7.0-5.4_amd64.deb ############################ ### Description: Change MAC automatically? # Please specify whether macchanger should be set up to run automatically # every time a network device is brought up or down. This gives a new MAC # address whenever you attach an ethernet cable or reenable wifi. # d-i macchanger/automatically_run boolean false ############################ #### magnum-api_15.0.1-4_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i magnum/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i magnum/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i magnum/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i magnum/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i magnum/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i magnum/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i magnum/api-endpoint-address string ### Description: This service endpoint protocol: # d-i magnum/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i magnum/api-endpoint-region-name string regionOne ############################ #### magnum-common_15.0.1-4_all.deb ############################ ### Description: Configure Magnum trustee and Cinder connection with debconf? # Magnum trustee must be configured to connect to Keystone and Cinder. Specify # if you wish to handle this configuration through debconf. # d-i magnum/configure_with_debconf boolean false ### Description: Magnum domain administrator username: # Please enter the username of the Magnum domain administrator. # d-i magnum/magnum_domain_admin_username string magnum_domain_admin ### Description: Magnum domain administrator password: # Please enter the password of the Magnum domain administrator. # d-i magnum/magnum_domain_admin_password password ### Description: Magnum domain: # Please enter domain name which will be used as aagnum domain. # d-i magnum/magnum_domain_name string magnum ### Description: Keystone interface: # Select keystone_interface with either public or internal depending on your network # configuration. If your instances cannot reach internal keystone endpoint which is # often the case in production environments it should be set to public. # Default to public. # d-i magnum/keystone_interface select # Possible choices: public, internal ### Description: Cinder os region name: # Please enter the region name for cinder service. # d-i magnum/cinder_os_region_name string regionOne ### Description: Configure default volume type? # Magnum needs to have some volume type # created in cinder. Do you want to create it? # d-i magnum/create_volume_type boolean false ### Description: Default docker volume type: # Magnum needs to have some volume type # created in cinder. Therefore , please specify the name # of volume type which magnum will use: # d-i magnum/default_docker_volume_type string docker ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i magnum/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i magnum/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i magnum/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i magnum/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i magnum/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i magnum/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i magnum/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i magnum/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i magnum/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i magnum/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i magnum/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i magnum/ksat-admin-password password ### Description: Auth server service username: # d-i magnum/ksat-service-username string ### Description: Auth server service project name: # d-i magnum/ksat-service-project-name string service ### Description: Auth server service password: # d-i magnum/ksat-service-password password ############################ #### ihungarian_1.6.1-2.1_amd64.deb ############################ ############################ #### mailagent_3.1-106-1_amd64.deb ############################ ### Description: Organization name for this computer: # The /etc/news/organization file does not exist. That file contains # the name of the organization this computer belongs to. This is the # name that will appear in the Organization header field of outgoing # articles, mail, or patches. # . # Please enter the name of the organization as you want it to appear in # that header field. It is common practice to add a location, typically # a city name, to the organization's name, for instance: # University of Southern North Dakota, Hoople # . # If you enter "--none--", no organization name will be setup. # d-i shared/news/organization string --none-- ############################ #### mailfilter_0.8.9-1_amd64.deb ############################ ############################ #### mailgraph_1.14-20_all.deb ############################ ### Description: Should Mailgraph start on boot? # Mailgraph can start on boot time as a daemon. Then it will monitor # your Postfix logfile for changes. This is recommended. # . # The other method is to call mailgraph by hand with the -c parameter. # d-i mailgraph/start_on_boot boolean true ### Description: Logfile used by mailgraph: # Enter the logfile which should be used to create the databases for # mailgraph. If unsure, leave default (/var/log/mail.log). # d-i mailgraph/mail_log string /var/log/mail.log ### Description: Ignore mail to/from localhost? # When using a content filter like amavis, incoming mail is counted more # than once, which will result in wrong values. # If you use some content filter, you should choose this option. # d-i mailgraph/ignore_localhost boolean false ############################ #### python3-mailman-hyperkitty_1.2.1-1_all.deb ############################ ############################ #### mailman3-web_0+20200530-2.1_all.deb ############################ ### Description: Domain name for sender email addresses: # If the Mailman3 web interface sends emails, this domain will # be used for the sender addresses. In particular, it will be # 'postorius@' for internal authentication and # 'root@' for error messages. # d-i mailman3-web/emailname string localhost.local ### Description: Username of the Postorius superuser: # This is the username of the Postorius superuser. It will have # global administrative access to all mailinglists. # d-i mailman3-web/superuser-name string admin ### Description: Email address of the Postorius superuser: # d-i mailman3-web/superuser-mail string root@localhost ### Description: Password for the Postorius superuser: # If an empty password is given, no superuser will be created # at all. It then needs to be created manually. # d-i mailman3-web/superuser-password password ### Description: Web server(s) to configure automatically: # Mailman3-web supports any web server with uwsgi support, # however only Apache 2 and nginx can be configured # automatically. # . # Please select the web server(s) that should be configured # automatically for Mailman3-web. # d-i mailman3-web/configure-webserver select none # Possible choices: none, apache2, nginx ### Description: Should the webserver(s) be restarted now? # In order to activate the new configuration, the configured # web server(s) have to be restarted. # d-i mailman3-web/restart-webserver boolean true ############################ #### mailman3_3.3.8-2~deb12u1_all.deb ############################ ### Description: Add the HyperKitty configuration to mailman.cfg? # Mailman3 needs additional configuration in mailman.cfg in order to send # messages to the HyperKitty archiver. This configuration can be added # automatically now. # . # The content of /usr/share/mailman3/mailman_cfg_hyperkitty_snippet.cfg # will be added to /etc/mailman3/mailman.cfg. # d-i mailman3/config_hyperkitty boolean ############################ #### man-db_2.11.2-2_amd64.deb ############################ ### Description: Should man and mandb be installed 'setuid man'? # The man and mandb program can be installed with the set-user-id bit set, so # that they will run with the permissions of the 'man' user. This allows # ordinary users to benefit from the caching of preformatted manual pages # ('cat pages'), which may aid performance on slower machines. # . # Cached man pages only work if you are using an 80-column terminal, to avoid # one user causing cat pages to be saved at widths that would be inconvenient # for other users. If you use a wide terminal, you can force man pages to be # formatted to 80 columns anyway by setting MANWIDTH=80. # . # Enabling this feature may be a security risk, so it is disabled by default. # If in doubt, you should leave it disabled. # d-i man-db/install-setuid boolean false ### Description: for internal use; can be preseeded # If true, automatically rebuild man-db's database when packages containing # manual pages are installed. # d-i man-db/auto-update boolean true ############################ #### man2html_1.6g-14_amd64.deb ############################ ### Description: Should post-installation script index your man pages? # Swish++ will be run once a week to index your man pages. # . # The index can also be generated (in the background) by the post-installation script. # This process needs quite a lot of computer resources, and can take several minutes # so you can choose now if you would like to do this. # d-i man2html/index_manpages boolean true ############################ #### mandos_1.8.16-1_all.deb ############################ ############################ #### mandos-client_1.8.16-1_amd64.deb ############################ ############################ #### manila-api_15.1.0-2_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i manila/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i manila/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i manila/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i manila/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i manila/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i manila/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i manila/api-endpoint-address string ### Description: This service endpoint protocol: # d-i manila/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i manila/api-endpoint-region-name string regionOne ############################ #### manila-common_15.1.0-2_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i manila/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i manila/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i manila/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i manila/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i manila/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i manila/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i manila/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i manila/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i manila/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i manila/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i manila/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i manila/ksat-admin-password password ### Description: Auth server service username: # d-i manila/ksat-service-username string ### Description: Auth server service project name: # d-i manila/ksat-service-project-name string service ### Description: Auth server service password: # d-i manila/ksat-service-password password ############################ #### mariadb-server_10.11.6-0+deb12u1_amd64.deb ############################ ### Description: Remove all MariaDB databases? # The /var/lib/mysql directory which contains the MariaDB databases is about # to be removed. # . # If you're removing the MariaDB package in order to later install a more # recent version or if a different mariadb-server package is already # using it, the data should be kept. # d-i mariadb-server/postrm_remove_databases boolean false ############################ #### masakari-api_14.0.2-2_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i masakari/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i masakari/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i masakari/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i masakari/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i masakari/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i masakari/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i masakari/api-endpoint-address string ### Description: This service endpoint protocol: # d-i masakari/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i masakari/api-endpoint-region-name string regionOne ############################ #### masakari-common_14.0.2-2_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i masakari/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i masakari/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i masakari/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i masakari/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i masakari/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i masakari/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i masakari/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i masakari/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i masakari/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i masakari/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i masakari/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i masakari/ksat-admin-password password ### Description: Auth server service username: # d-i masakari/ksat-service-username string ### Description: Auth server service project name: # d-i masakari/ksat-service-project-name string service ### Description: Auth server service password: # d-i masakari/ksat-service-password password ############################ #### mason_1.0.0-13_all.deb ############################ ### Description: Default action for new firewall rules: # The new rule default action specifies how Mason will handle unknown packets, when the firewall is in learning mode. # . # The "accept" action will allow the packet through. "Reject" will stop the # packet with a rejection reply, while "deny" will drop the packet silently. # d-i mason/newrulepolicy select accept # Possible choices: accept, reject, deny ### Description: Default action for rulesets: # The default action specifies how Mason will handle unknown packets, when the firewall is not in learning mode. # . # Again, "accept" allows the packet through, "reject" drops the packet with # a reply, and "deny" silently drops the packet. # d-i mason/defaultpolicy select accept # Possible choices: accept, reject, deny ############################ #### mdadm_4.2-5_amd64.deb ############################ ### Description: Should mdadm run monthly redundancy checks of the MD arrays? # If the kernel supports it (versions greater than 2.6.14), mdadm can periodically check the # redundancy of MD arrays (RAIDs). This may be a resource-intensive process, # depending on the local setup, but it could help prevent rare cases of data loss. # Note that this is a read-only check unless errors are found; if errors are # found, mdadm will try to correct them, which may result in write access to # the media. # . # The default, if turned on, is to check on the first Sunday of every # month at 01:06. # d-i mdadm/autocheck boolean true ### Description: Should mdadm check once a day for degraded arrays? # mdadm can check once a day for degraded arrays and missing spares # to ensure that such events don't go unnoticed. # d-i mdadm/autoscan boolean true ### Description: Do you want to start the MD monitoring daemon? # The MD (RAID) monitor daemon sends email notifications in response to # important MD events (such as a disk failure). # . # Enabling this option is recommended. # d-i mdadm/start_daemon boolean true ### Description: Recipient for email notifications: # Please enter the email address of the user who should get the email # notifications for important MD events. # d-i mdadm/mail_to string root ############################ #### wgerman-medical_20220425-1_all.deb ############################ ############################ #### metaphlan2-data_2.6.0+ds-4_all.deb ############################ ### Description: Should the database be created right now? # This binary Debian package is using a different dataformat than it # is used by the package metaphlan2. To use the data with metaphlan2 # a conversion is needed. The conversion script takes about 20min. # If you decide to delay this conversion you need to manually call # . # /usr/sbin/metaphlan2-data-convert # . # after the installation process has finished. Otherwise metaphlan2 # is not usable. # d-i metaphlan2-data/createnow boolean true ############################ #### mgetty-fax_1.2.1-1.2_amd64.deb ############################ ### Description: Run faxrunqd during system startup? # The mgetty-fax package contains a daemon ("faxrunqd") that can # automatically take in charge the sending of the faxes spooled with # faxspool. This daemon and the faxrunq utility need # /etc/mgetty/faxrunq.config to be configured appropriately in order to run. # If you plan to use faxrunqd, please indicate so. # d-i mgetty-fax/start_faxrunqd boolean true ############################ #### mimedefang_3.3-1_amd64.deb ############################ ### Description: Should MIMEDefang use an embedded Perl interpreter? # Choosing this option is generally safe and will significantly improve # performance. However, some systems do not support it. See # mimedefang-multiplexor(8) for more details on using an embedded Perl # interpreter # d-i mimedefang/embedperl boolean true ############################ #### minissdpd_1.6.0-1_amd64.deb ############################ ### Description: Start the MiniSSDP daemon automatically? # Choose this option if the MiniSSDP daemon should start automatically, # now and at boot time. # d-i minissdpd/start_daemon boolean false ### Description: Interfaces to listen on for UPnP queries: # The MiniSSDP daemon will listen for requests on one interface, and drop # all queries that do not come from the local network. Please enter the LAN # interfaces or IP addresses of those interfaces (in CIDR notation) that it # should listen on, separated by space. # . # Interface names are highly preferred, and required if you plan to enable IPv6 # port forwarding. # d-i minissdpd/listen string ### Description: Enable IPv6 listening? # Please specify whether the MiniSSDP daemon should listen for IPv6 queries. # d-i minissdpd/ip6 boolean false ############################ #### miniupnpd_2.3.1-1_all.deb ############################ ### Description: Start the MiniUPnP daemon automatically? # Choose this option if the MiniUPnP daemon should start automatically, # now and at boot time. # d-i miniupnpd/start_daemon boolean false ### Description: Interfaces to listen on for UPnP queries: # The MiniUPnP daemon will listen for requests on the local network. Please # enter the interfaces or IP addresses it should listen on, separated by # space. # . # Interface names are preferred, and required if you plan to enable IPv6 port # forwarding. # d-i miniupnpd/listen string ### Description: External WAN network interface to open ports on: # The MiniUPnP daemon will listen on a specific IP address on the local # network, then open ports on the WAN interface. Please enter the name of # the WAN network interface on which the MiniUPnP daemon should perform # port forwarding. # d-i miniupnpd/iface string ### Description: Enable IPv6 firewall chain? # Please specify whether the MiniUPnP daemon should run its # ip6tables script on startup to initialize the IPv6 firewall chain. # . # Note: This option is useless if you don't block any IPv6 forwarded traffic. # d-i miniupnpd/ip6script boolean false ### Description: Force reporting IGDv1 in rootDesc? # Some IGD clients (most notably Microsoft® Windows® BITS) look for IGDv1 and do # not recognize IGDv2 as a valid IGD service. This option will fool them by # pretending itself to be IGDv1. # . # Of course you will lose IGDv2 functions (notably IPv6 support) by enabling # this. # d-i miniupnpd/force_igd_desc_v1 boolean false ############################ #### miscfiles_1.5+dfsg-4_all.deb ############################ ############################ #### mistral-api_15.0.0-1_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i mistral/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i mistral/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i mistral/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i mistral/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i mistral/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i mistral/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i mistral/api-endpoint-address string ### Description: This service endpoint protocol: # d-i mistral/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i mistral/api-endpoint-region-name string regionOne ############################ #### mistral-common_15.0.0-1_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i mistral/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i mistral/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i mistral/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i mistral/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i mistral/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i mistral/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i mistral/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i mistral/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i mistral/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i mistral/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i mistral/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i mistral/ksat-admin-password password ### Description: Auth server service username: # d-i mistral/ksat-service-username string ### Description: Auth server service project name: # d-i mistral/ksat-service-project-name string service ### Description: Auth server service password: # d-i mistral/ksat-service-password password ############################ #### mlmmj_1.3.0-4_amd64.deb ############################ ### Description: Remove mlmmj lists on purge? # Removing mlmmj on purge includes the removal of all subscriber lists, # archives and configuration options for all lists currently stored. # . # Accepting here basically means that everything under /var/spool/mlmmj # and /etc/mlmmj/lists will be removed when this package is purged. Also # please note that any changes you might have made to /etc/aliases will not # be unmade automatically when this package is removed. (A notice will be # displayed however, to remind you to clean up your aliases.) # d-i mlmmj/remove-on-purge boolean false ############################ #### libapache2-mod-mono_3.8-3+b2_amd64.deb ############################ ### Description: Mono server to use: # The libapache2-mod-mono module can be used with one of two different # Mono ASP.NET backends: # - mod-mono-server2: implements ASP.NET 2.0 features; # - mod-mono-server4: implements ASP.NET 4.0 features. # d-i libapache2-mod-mono/mono-server select mod-mono-server4 # Possible choices: mod-mono-server2, mod-mono-server4 ############################ #### moon-buggy_1.0.51-13_amd64.deb ############################ ############################ #### mopidy_3.4.1-1_all.deb ############################ ### Description: Start the Mopidy server at boot? # The Mopidy server can be run as a system service, automatically starting # at boot. It will be listening to MPD connections on port 6600 and HTTP # connections on port 6680. By default, it will only accept connections from # the local machine. # . # You have the option of starting the Mopidy server automatically on system # boot. If in doubt, it is suggested to not start it automatically on boot. # . # This setting can be modified later by running "dpkg-reconfigure mopidy". # d-i mopidy/daemon boolean false ############################ #### motion_4.5.1-2_amd64.deb ############################ ############################ #### mpdscribble_0.24-3_amd64.deb ############################ ### Description: Install system mpdscribble service? # You can install mpdscribble as a system daemon. The mpdscribble service will be started on boot. # Note that is not necessary to run mpd as a system service as it runs fine # when started manually using a regular user account. # d-i mpdscribble/systemwide boolean false ### Description: Last.fm username: # Enter username you use on Last.fm. # d-i mpdscribble/user string ### Description: Last.fm password: # Enter password you use on Last.fm. # d-i mpdscribble/password password ############################ #### mrtg_2.17.10-5+deb12u2_amd64.deb ############################ ### Description: Fix owner, group and permissions for /var/www/html/mrtg? # By default MRTG writes all graphs in the directory /var/www/html/mrtg/. This # directory currently exists, but it is insecure. The directory should be # owned by the user 'mrtg' and group 'www-data', with recommended permissions # of 0750. # d-i mrtg/fix_permissions boolean true ### Description: Create /var/www/html/mrtg? # By default MRTG writes all graphs in the directory /var/www/html/mrtg/. # However, this directory doesn't currently exist. The directory should be # owned by the user 'mrtg' and group 'www-data', with recommended permissions # of 0750. # . # Alternatively, you can use another path for generated graphs. Note that # keeping this directory empty when using another path is not a problem. # d-i mrtg/create_www boolean true ### Description: Remove old and conflicting file /etc/cron.d/mrtg? # MRTG no longer needs to use cron because it is started via systemd # (or init.d scripts). # . # A file /etc/cron.d/mrtg exists, left behind by an old version of MRTG. # If kept, this file will cause duplicate work because MRTG now runs as a # daemon. It is therefore strongly recommended to remove the cron file. # . # If this cron job is needed, consider renaming the file (e.g. from # /etc/cron.d/mrtg to /etc/cron.d/mrtg-custom) to avoid future warnings. # d-i mrtg/remove_cron boolean true ############################ #### msmtp_1.8.23-1_amd64.deb ############################ ### Description: Enable AppArmor support? # Apparmor is a kernel security mechanism to restrict programs capabilities # with per-program profiles. # . # The AppArmor profile for msmtp covers a lot of common usecases but there are # still corner cases with some options which breaks msmtp with incomprehensible # permissions denied errors. # d-i msmtp/apparmor boolean false ############################ #### mumble-server_1.3.4-4_amd64.deb ############################ ### Description: Password to set on SuperUser account: # Murmur has a special account called "SuperUser" which bypasses all # privilege checks. # . # If you set a password here, the password for the "SuperUser" account will # be updated. # . # If you leave this blank, the password will not be changed. # d-i mumble-server/password password ### Description: Autostart mumble-server on server boot? # Mumble-server (murmurd) can start automatically when the server is booted. # d-i mumble-server/start_daemon boolean true ### Description: Allow mumble-server to use higher priority? # Mumble-server (murmurd) can use higher process and network priority to # ensure low latency audio forwarding even on highly loaded servers. # d-i mumble-server/use_capabilities boolean false ############################ #### munin_2.0.73-1_all.deb ############################ ### Description: Remove all RRD database files? # The /var/lib/munin directory which contains the RRD files with the # data accumulated by munin is about to be removed. # . # If you want to install munin later again or if you want to use the # content of the RRD files for other purposes, the data should be kept. # d-i munin/postrm_remove_rrd_files boolean false ############################ #### murano-api_14.0.0-3_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i murano/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i murano/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i murano/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i murano/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i murano/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i murano/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i murano/api-endpoint-address string ### Description: This service endpoint protocol: # d-i murano/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i murano/api-endpoint-region-name string regionOne ############################ #### murano-common_14.0.0-3_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i murano/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i murano/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i murano/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i murano/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i murano/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i murano/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i murano/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i murano/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i murano/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i murano/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i murano/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i murano/ksat-admin-password password ### Description: Auth server service username: # d-i murano/ksat-service-username string ### Description: Auth server service project name: # d-i murano/ksat-service-project-name string service ### Description: Auth server service password: # d-i murano/ksat-service-password password ############################ #### muse_4.1.0-1_amd64.deb ############################ ### Description: Do you want MusE to run with superuser rights? # For good timing, MusE needs to set the real time clock (/dev/rtc) to a # higher clock rate, and raise its scheduling priority. Usually, only the # root user is allowed to do so. MusE can be installed "suid-root", so # that it always runs with superuser capabilities. This is convenient, but # programming errors in MusE likely present a hazard for system security in # this setup. # . # File /usr/share/doc/muse/README.Debian summarizes several more secure # methods to meet the timing requirements, but they all require manual # configuration. # . # If you intend to use MusE for timing-sensitive recordings, and security # is of no concern on this computer, opt for the suid-root installation # by giving an affirmative answer to this question. Deny if unsure. # d-i muse/muse-setuid boolean false ############################ #### mysqmail_0.4.9-10.3_all.deb ############################ ### Description: Reuse MySQL authentication information from DTC? # MySQMail can use the same MySQL credentials as DTC. # . # If you choose this option, you will not be prompted for a login # and password to configure MySQMail. # d-i mysqmail/conf_mysqlautoconfig boolean true ### Description: MySQL hostname: # Please enter the hostname or IP address of the MySQL server for MySQMail. # d-i mysqmail/conf_mysqlhost string localhost ### Description: MySQL login: # Please enter the MySQL login needed to create (and later, access) the MySQMail # database. # d-i mysqmail/conf_mysqllogin string root ### Description: MySQL password: # Please enter the MySQL password needed to create (and later, access) the MySQMail # database. # d-i mysqmail/conf_mysqlpass password ### Description: MySQL database name: # Please enter the name of the database where MySQMail will store its data. # d-i mysqmail/conf_mysqldb string dtc ############################ #### mythtv-status_1.0.1-6.1_all.deb ############################ ### Description: MythTV backend to check: # The MythTV backend to check, you only need to change this if you want to check # a different host. # d-i mythtv-status/host string localhost ### Description: Update the system MOTD? # Whether the Message of the Day should be updated on system boot and on a # regular basis. # . # To adjust how often the MOTD is updated, edit /etc/cron.d/mythtv-status. # d-i mythtv-status/enable boolean true ### Description: Send email status to: # Status emails can be sent on a daily basis. # . # By default an email is only sent if there are alerts. You must have # the MythTV Perl API installed for conflict alerts to be generated. # . # To disable set the email address to "none". To specify multiple email # addresses, seperate them with a comma. # d-i mythtv-status/email string none ############################ #### nagvis_1.9.34-1_all.deb ############################ ### Description: Monitoring suite used with NagVis: # The NagVis package supports Icinga as well as # Nagios, using the check-mk-live broker backend. # . # If you would like to use NagVis with a different backend or a different # monitoring suite, please choose "other". You'll have to configure it # manually. # d-i nagvis/monitoring_system select icinga # Possible choices: icinga2, icinga, nagios, shinken, other ### Description: Delete NagVis data when purging the package? # NagVis creates files in /var/{cache,lib}/nagvis and # /etc/nagvis (for instance background images and map files), including a small # database for authentification. If you don't need any of these files, # they can be removed now, or you may want to keep them and clean up by hand # later. # d-i nagvis/delete_on_purge boolean false ############################ #### namazu2_2.0.21-23_amd64.deb ############################ ### Description: Directories in which to copy the cgi: # Namazu package will be installed in /usr/lib/cgi-bin/namazu.cgi by # default. But for VirtualHost, you may also need copy the cgi scripts to another # location. The cgi will be copied automatically on upgrade or installation. # . # Directories should be space separated. If you don't need this feature, # please leave this option to the empty string. # d-i namazu2/install string ############################ #### nas_1.9.4-7_amd64.deb ############################ ### Description: Should nasd release /dev/dsp? # By default, the NAS server will open the configured audio device # at startup, and then keep it open until the server is stopped. This will # stop any non-NAS-aware audio clients from using the audio device. # . # The daemon can be configured to release the audio device when it is # not using it, with some delay after the # application completes before the device is available. # . # An alternative is to use the "audiooss" package to wrap any programs # that use /dev/dsp to make them use equivalent NAS calls. # d-i nas/relinquish boolean true ### Description: Should nasd change mixer settings at startup? # If you choose this option, the NAS server will change the mixer settings # at startup as follows: # . # - set PCM volume to 50%; # - change the record input device to LINE. # d-i nas/mixer boolean false ############################ #### nbd-client_3.24-1.1_amd64.deb ############################ ############################ #### nbd-server_3.24-1.1_amd64.deb ############################ ### Description: Number of nbd-server instances to run: # Multiple nbd-server processes may run to export multiple files or # block devices. Please specify how many configurations for such servers you # want to generate. # . # Note that you can always add extra servers by adding them to # /etc/nbd-server/config, or by running "dpkg-reconfigure nbd-server". # d-i nbd-server/number string 0 ### Description: Name of export ${number}: # Please specify a name for this export. # d-i nbd-server/name string ### Description: File to export (server number ${number}): # Please specify a file name or block device that should be exported # over the network. You can export a real block device (for instance # "/dev/hda1"); a normal file (such as "/export/nbd/bl1"); or a # bunch of files all at once. For the third option, you can # use "%s" in the filename, which will be expanded to the # IP-address of the connecting client. An example would be # "/export/swaps/swp%s". # . # Note that it is possible to tune the way in which the IP address will # be substituted in the file name. See "man 5 nbd-server" for details. # d-i nbd-server/filename string ############################ #### snmpd_5.9.3+dfsg-2_amd64.deb ############################ ############################ #### netdiag_1.2-1.2_amd64.deb ############################ ### Description: Start statnetd at boot time? # Please specify whether statnetd should be started as part of the boot # process. This can be changed later by editing /etc/default/netdiag. # d-i netdiag/run_statnetd boolean true ############################ #### nethack-common_3.6.6-3+b2_amd64.deb ############################ ### Description: Use setgid bit with NetHack's recover utility? # The "recover" program in the package nethack-common is traditionally # installed with the "setgid" bit set, so that all users can use it to # recover their own save files after a crash (with "games" group # privileges). This is a potential source of security problems. # . # This package includes a script that runs during system boot, invoking # recover on any broken save files it finds. This makes it less likely # that users will need to run it themselves, so the default is to install # recover without the special permission bits required for that. # . # If you choose this option, unprivileged users will be able to run "recover". # d-i nethack-common/recover-setgid boolean true ############################ #### netselect_0.3.ds1-30.1_amd64.deb ############################ ### Description: Should netselect be installed setuid root? # Netselect can be installed with the set-user-id bit set, so that it will # run with the permissions of the "root" user. Since netselect needs these # permissions to work properly, unprivileged users cannot run it unless it is # installed this way. # . # Enabling this feature may be a security risk. If in doubt, it is # suggested to leave it disabled. # d-i netselect/install-setuid boolean false ############################ #### neurodebian_0.41.2+nmu1_all.deb ############################ ### Description: Enable the NeuroDebian package repository? # The NeuroDebian project provides a separate APT repository with # software that is not available in Debian, including datasets and # backported new releases. # . # If you choose this option, these packages will be available for # installation and upgrades. # . # Even though these packages are closely maintained # by the NeuroDebian team, enabling this additional archive # may compromise the integrity of the system. # d-i neurodebian/enable boolean false ### Description: Release name of the base system: # Please specify the appropriate Debian or Ubuntu release codename # (for instance "stretch" or "trusty"). # . # If this is set to "automatic"', the release name is chosen according # to the output of "apt-cache policy". If the release name for this # system is not "${release}", you should choose the specific one which # matches best. # d-i neurodebian/release select auto # Possible choices: automatic, ${releases} ### Description: NeuroDebian mirror to use: # The NeuroDebian project has a number of community-maintained mirrors # around the globe. # . # If you do not know which mirror URL to choose, select one of: # . # * origin: the original NeuroDebian repository; # * best: will try to use netselect to select the "closest" mirror. # This may fail depending on the current mirror setup and the # configuration of the firewall. If netselect is not available, the # default mirror will be used. # d-i neurodebian/mirror select best # Possible choices: origin, best, custom, ${mirrors} ### Description: NeuroDebian flavor to use: # The NeuroDebian project adheres to the Debian Free Software Guidelines, # and offers three packages areas, classified by license, for all # suites/releases: # . # libre # DFSG-compliant material only # full # all three areas (main, contrib, non-free) # auto # picked from the output of "apt-cache policy" # (for this machine: "${flavor}"). # d-i neurodebian/flavor select auto # Possible choices: auto, libre, full ### Description: NeuroDebian repository components to enable: # NeuroDebian repository provides three different sets of packages: # . # software # Packages containing software, often backports of stable software # releases for previous Debian/Ubuntu releases; # devel # Additional "bleeding edge" software packages (like those in Debian # experimental), which it may not be safe to enable by default. # data # Packages containing data (such as atlases or sample datasets), often # required by other packages. This should usually be enabled. # d-i neurodebian/components multiselect software, data # Possible choices: software, data, devel ### Description: Overwrite the existing NeuroDebian APT file? # If an APT sources.list file already exists for NeuroDebian, this # package will fail to configure unless given permission to overwrite it. # d-i neurodebian/overwrite boolean true ### Description: Additional suffix for the NeuroDebian APT file name: # Adding a suffix makes it possible to enable an additional repository # (such as NeuroDebian devel) or release, without interfering with the # main NeuroDebian sources list. # . # It should usually be left empty. # d-i neurodebian/suffix string ############################ #### neutron-api_21.0.0-7_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i neutron/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i neutron/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i neutron/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i neutron/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i neutron/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i neutron/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i neutron/api-endpoint-address string ### Description: This service endpoint protocol: # d-i neutron/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i neutron/api-endpoint-region-name string regionOne ############################ #### neutron-common_21.0.0-7_all.deb ############################ ### Description: Manage nova config through debconf? # Neutron service must contact Nova, and this is configured through # the [nova] section of the configuration. Specify if you wish # to handle this configuration through debconf. # d-i neutron/configure_nova boolean false ### Description: Nova keystone auth URL: # Neutron needs to be able to communicate with Nova through Keystone. Therefore # Neutron needs to know the Nova admin tenant name, username, password and region. # . # Please enter the URL of keystone auth_url for Nova. # d-i neutron/nova_auth_url string http://127.0.0.1:5000 ### Description: Nova server region name: # Neutron needs to be able to communicate with Nova through Keystone. Therefore # Neutron needs to know the Nova admin tenant name, username, password and region. # . # Please enter the region of the admin tenant for Nova. # d-i neutron/nova_region string regionOne ### Description: Nova admin tenant name: # Neutron needs to be able to communicate with Nova through Keystone. Therefore # Neutron needs to know the Nova admin tenant name, username, password and region. # . # Please enter the name of the admin tenant for Nova. # d-i neutron/nova_service_project_name string service ### Description: Nova service username: # Neutron needs to be able to communicate with Nova through Keystone. Therefore # Neutron needs to know the Nova admin tenant name, username, password and region. # . # Please enter the username of the admin tenant for Nova. # d-i neutron/nova_service_username string nova ### Description: Nova administrator password: # Neutron needs to be able to communicate with Nova through Keystone. Therefore # Neutron needs to know the Nova admin tenant name, username, password and region. # . # Please enter the password of the admin tenat for Nova. # d-i neutron/nova_service_password password ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i neutron/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i neutron/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i neutron/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i neutron/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i neutron/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i neutron/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i neutron/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i neutron/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i neutron/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i neutron/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i neutron/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i neutron/ksat-admin-password password ### Description: Auth server service username: # d-i neutron/ksat-service-username string ### Description: Auth server service project name: # d-i neutron/ksat-service-project-name string service ### Description: Auth server service password: # d-i neutron/ksat-service-password password ############################ #### neutron-metadata-agent_21.0.0-7_all.deb ############################ ### Description: Manage Neutron metadata config through debconf? # Neutron Metadata service must be configured to contact Nova. # Specify if you wish to handle this configuration through debconf. # d-i neutron-metadata/configure boolean false ### Description: Metadata proxy shared secret: # VM instances using Neutron to handle networking retrieve their metadata # through the Neutron metadata agent, which serves as a proxy to the Nova # metadata REST API server. # . # Please enter the password that should be used to protect communications # between the Neutron metadata proxy agent and the Nova metadata server. The # same shared password should be used when setting up the nova-common # package. # d-i neutron-metadata/metadata_secret password ### Description: Nova metadata host: # VM instances using Neutron to handle networking retrieve their metadata # through the Neutron metadata agent, which serves as a proxy to the Nova # metadata REST API server. # . # Please enter the host of Nova metadata server. # d-i neutron-metadata/nova_metadata_host string 127.0.0.1 ############################ #### neutron-openvswitch-agent_21.0.0-7_all.deb ############################ ### Description: Neutron overlay interface ip address: # Neutron overlay interface ip address. # d-i neutron-openvswitch-agent/overlay-int-ip-address string 127.0.0.1 ############################ #### neutron-dynamic-routing-common_21.0.0-1.1_all.deb ############################ ### Description: Run default configuration for neutron-dynamic-routing ? # If you want to run now, please make sure you have configured # database.connection in neutron.conf. Database migrations will be executed. # . # If you don't choose this option, no database migration will be run # and no plugin will be enabled, these things you have to do manually. # . # You can change this setting later on by running "dpkg-reconfigure # -plow python3-neutron-fwaas". # d-i neutron-dynamic-routing/configure-dynamic-routing boolean false ### Description: Neutron-dynamic-routing router-id: # Neutron-dynamic-routing needs to be able to communicate with remote BGP system. Therefore # Neutron-dynamic-routing needs to know local BGP router id. Please fill router id with # a suitable unique 32-bit number, typically an IPv4 address on the host running the agent. # For example, 192.168.0.2. # . # Please enter the local BGP router id. # d-i neutron-dynamic-routing/router-id string 192.168.0.2 ############################ #### neutron-vpnaas-common_21.0.0-2_all.deb ############################ ### Description: Run default configuration for neutron-vpnaas ? # Neutron-vpnaas will be configured to use strongswan and vpnaas l3 extension. # If you want to run now, please make sure you have configured # database.connection in neutron.conf: # . # If you don't choose this option, no database migration will be run # and no plugin will be enabled, these things you have to do manually. # . # You can change this setting later on by running "dpkg-reconfigure # -plow neutron-vpnaas-common". # d-i neutron-vpnaas/configure-vpnaas boolean false ############################ #### nginx-common_1.22.1-9_all.deb ############################ ############################ #### nn_6.7.3-15_amd64.deb ############################ ### Description: NNTP server to use: # Enter the fully qualified host name of the news server to use for reading. # d-i nn/ask-newsserver string news ############################ #### nodm_0.13-6_amd64.deb ############################ ### Description: Enable nodm? # Designed for embedded or kiosk systems, nodm starts an X session # for a user without asking for authentication. On regular # machines, this has security implications and is therefore disabled # by default. # . # You should enable nodm only if you need autologin on this machine. # d-i nodm/enabled boolean true ### Description: User to start a session for: # Please enter the login name of the user that will automatically be logged into X by nodm. # d-i nodm/user string root ### Description: Lowest numbered vt on which X may start: # nodm needs to find a free virtual terminal on which to start the X server. # . # Since X and getty get to conflict, this parameter will specify the lowest # numbered virtual terminal on which to start the search. # . # This value should be set to one higher than the highest numbered virtual # terminal on which a getty may start. # d-i nodm/first_vt string 7 ### Description: Options for the X server: # Please enter the options to pass to the X server when starting it. # . # Format: [/usr/bin/] [:] # . # The Xserver executable and the display name can be omitted, but should # be placed in front, if nodm's defaults shall be overridden. # . # If no vtN option is used, nodm will perform automatic vt allocation. # d-i nodm/x_options string -nolisten tcp ### Description: Minimum time (in seconds) for a session to be considered OK: # If an X session will run for less than this time in seconds, nodm will wait an # amount of time before restarting the session. The waiting time will grow # until a session lasts longer than this amount. # d-i nodm/min_session_time string 60 ### Description: Maximum time (in seconds) to wait for X to start: # Timeout (in seconds) to wait for X to be ready to accept connections. If X is # not ready before this timeout, it is killed and restarted. # d-i nodm/x_timeout string 300 ### Description: X session to use: # Please choose the name of the X session script to use with nodm. # d-i nodm/xsession string /etc/X11/Xsession ### Description: for internal use only # d-i nodm/daemon_name string /usr/sbin/nodm ### Description: Default display manager: # A display manager is a program that provides graphical login capabilities for # the X Window System. # . # Only one display manager can manage a given X server, but multiple display # manager packages are installed. Please select which display manager should # run by default. # . # Multiple display managers can run simultaneously if they are configured to # manage different servers; to achieve this, configure the display managers # accordingly, edit each of their init scripts in /etc/init.d, and disable the # check for a default display manager. # d-i shared/default-x-display-manager select # Possible choices: ${choices} ############################ #### aspell-no_2.2-4_all.deb ############################ ### Description: Norwegian language variant: # Norwegian has two different written forms: bokmaal and nynorsk. # . # Please choose the one you wish to use. # d-i aspell-no/whichvariant select bokmaal # Possible choices: nynorsk, bokmaal ############################ #### inorwegian_2.2-4_amd64.deb ############################ ### Description: Norwegian language variant: # Norwegian has two different written forms: bokmaal and nynorsk. # . # Please choose the one you wish to use. # d-i inorwegian/whichvariant select bokmaal # Possible choices: nynorsk, bokmaal ############################ #### wnorwegian_2.2-4_all.deb ############################ ### Description: Norwegian language variant: # Norwegian has two different written forms: bokmaal and nynorsk. # . # Please choose the one you wish to use. # d-i wnorwegian/whichvariant select bokmaal # Possible choices: nynorsk, bokmaal ############################ #### nova-api_26.1.0-4_all.deb ############################ ### Description: Set up a database for Nova API? # No database has been set up for Nova to use. If you want # to set one up now, please make sure you have all needed # information: # . # * the host name of the database server (which must allow TCP # connections from this machine); # * a username and password to access the database; # * the type of database management software you want to use. # . # If you don't choose this option, no database will be set up and Nova # will use regular SQLite support. # . # You can change this setting later on by running "dpkg-reconfigure # -plow nova-api". # d-i novaapi/configure_db boolean false ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i nova/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i nova/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i nova/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i nova/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i nova/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i nova/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i nova/api-endpoint-address string ### Description: This service endpoint protocol: # d-i nova/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i nova/api-endpoint-region-name string regionOne ############################ #### nova-common_26.1.0-4_all.deb ############################ ### Description: Value for my_ip: # This value will be stored in the my_ip directive of nova.conf. # d-i nova/my-ip string ### Description: Neutron server URL: # Please enter the URL of the Neutron server. # d-i nova/neutron_url string http://127.0.0.1:9696 ### Description: Neutron admin tenant name: # Nova needs to be able to communicate with Neutron through Keystone. Therefore # Nova needs to know the Neutron admin tenant, username and password. # . # Please enter the name of the admin tenant for Neutron. # d-i nova/neutron_admin_tenant_name string admin ### Description: Neutron administrator username: # Please enter the username of the Neutron administrator. # d-i nova/neutron_admin_username string admin ### Description: Neutron administrator password: # Please enter the password of the Neutron administrator. # d-i nova/neutron_admin_password password ### Description: Metadata proxy shared secret: # VM instances using Neutron to handle networking retrieve their metadata # through the Neutron metadata agent, which serves as a proxy to the Nova # metadata REST API server. # . # Please enter the password that should be used to protect communications # between the Neutron metadata proxy agent and the Nova metadata server. The # same shared password should be used when setting up the neutron-metadata-agent # package. # d-i nova/metadata_secret password ### Description: Cinder os region name: # Please enter the region name for cinder service. # d-i nova/cinder_os_region_name string regionOne ### Description: Placement admin tenant name: # Nova needs to be able to communicate with Placement through Keystone. Therefore # Nova needs to know the Placement admin tenant, username and password. # . # Please enter the name of the admin tenant for Placement. # d-i nova/placement_admin_tenant_name string service ### Description: Placement administrator username: # Please enter the username of the Placement administrator. # d-i nova/placement_admin_username string placement ### Description: Placement administrator password: # Please enter the password of the Placement administrator. # d-i nova/placement_admin_password password ### Description: Placement os region name: # Please enter the region name for Placement service. # d-i nova/placement_os_region_name string regionOne ### Description: Manage neutron config through debconf? # Nova service must contact Neutron, and this is configured through # the [neutron] section of the configuration. Specify if you wish # to handle this configuration through debconf. # d-i nova/configure_neutron boolean false ### Description: Manage placement config through debconf? # Nova service must contact Placement, and this is configured through # the [placement] section of the configuration. Specify if you wish # to handle this configuration through debconf. # d-i nova/configure_placement boolean false ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i nova/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i nova/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i nova/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i nova/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i nova/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i nova/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i nova/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i nova/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i nova/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i nova/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i nova/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i nova/ksat-admin-password password ### Description: Auth server service username: # d-i nova/ksat-service-username string ### Description: Auth server service project name: # d-i nova/ksat-service-project-name string service ### Description: Auth server service password: # d-i nova/ksat-service-password password ############################ #### nova-consoleproxy_26.1.0-4_all.deb ############################ ### Description: Type of console daemon to start at boot time: # Nova Console supports 3 types of consoles. One is specific to Xen, called # XVP (Xen VNC Proxy), and the other daemon supports KVM. While the SPICE # protocol is normally faster than VNC, it also requires support for web # sockets in your browser, and that is a feature only very modern browsers # have support for. # . # This can later be edited in /etc/default/nova-consoleproxy. # d-i nova-consoleproxy/daemon_type select spicehtml5 # Possible choices: spicehtml5, novnc ############################ #### nsca_2.10.2-2_amd64.deb ############################ ### Description: Should the nsca daemon be enabled by default? # The nsca daemon is the process that handles results service checks sent # via send_nsca on remote hosts. Typically the nsca daemon is only needed # on hosts that run the nagios daemon. # . # If the system on which you are installing nsca also runs the nagios # daemon, you should most likely choose this option. If you are installing # nsca on a remote "satellite" system for the purpose of sending service # checks to a central nagios host, you should not choose this option. If # you wish to run nsca as a service through inetd/xinetd, you should # also not choose this option. # d-i nsca/run-nsca-daemon boolean ############################ #### libnss-ldapd_0.9.12-4_amd64.deb ############################ ### Description: Name services to configure: # For this package to work, you need to modify the /etc/nsswitch.conf file to use # the ldap datasource. # . # You can select the services that should have LDAP lookups enabled. The # new LDAP lookups will be added as the last datasource. Be sure to review # these changes. # d-i libnss-ldapd/nsswitch multiselect # Possible choices: passwd, group, shadow, hosts, networks, ethers, protocols, services, rpc, netgroup, aliases ### Description: Remove LDAP from nsswitch.conf now? # The following services are still configured to use LDAP for lookups: # ${services} # but the libnss-ldapd package is about to be removed. # . # You are advised to remove the entries if you don't plan on using LDAP for # name resolution any more. Not removing ldap from nsswitch.conf should, for # most services, not cause problems, but host name resolution could be affected # in subtle ways. # . # You can edit /etc/nsswitch.conf by hand or choose to remove the entries # automatically now. Be sure to review the changes to /etc/nsswitch.conf if you # choose to remove the entries now. # d-i libnss-ldapd/clean_nsswitch boolean false ############################ #### nslcd_0.9.12-4_amd64.deb ############################ ### Description: LDAP server URI: # Please enter the Uniform Resource Identifier of the LDAP server. The format # is "ldap://:/". Alternatively, "ldaps://" or # "ldapi://" can be used. The port number is optional. # . # When using an ldap or ldaps scheme it is recommended to use an IP address to # avoid failures when domain name services are unavailable. # . # Multiple URIs can be separated by spaces. # d-i nslcd/ldap-uris string ### Description: LDAP server search base: # Please enter the distinguished name of the LDAP search base. Many sites use # the components of their domain names for this purpose. For example, the # domain "example.net" would use "dc=example,dc=net" as the distinguished name # of the search base. # d-i nslcd/ldap-base string ### Description: LDAP authentication to use: # Please choose what type of authentication the LDAP database should # require (if any): # . # * none: no authentication; # * simple: simple bind DN and password authentication; # * SASL: any Simple Authentication and Security Layer mechanism. # d-i nslcd/ldap-auth-type select # Possible choices: none, simple, SASL ### Description: LDAP database user: # Please enter the name of the account that will be used to log in to the LDAP # database. This value should be specified as a DN (distinguished name). # d-i nslcd/ldap-binddn string ### Description: LDAP user password: # Please enter the password that will be used to log in to the LDAP database. # d-i nslcd/ldap-bindpw password ### Description: SASL mechanism to use: # Please choose the SASL mechanism that will be used to authenticate to the LDAP # database: # . # * auto: auto-negotiation; # * LOGIN: deprecated in favor of PLAIN; # * PLAIN: simple cleartext password mechanism; # * NTLM: NT LAN Manager authentication mechanism; # * CRAM-MD5: challenge-response scheme based on HMAC-MD5; # * DIGEST-MD5: HTTP Digest compatible challenge-response scheme; # * SCRAM: salted challenge-response mechanism; # * GSSAPI: used for Kerberos; # * SKEY: S/KEY mechanism (obsoleted by OTP); # * OTP: One Time Password mechanism; # * EXTERNAL: authentication is implicit in the context. # d-i nslcd/ldap-sasl-mech select # Possible choices: auto, LOGIN, PLAIN, NTLM, CRAM-MD5, DIGEST-MD5, SCRAM, GSSAPI, SKEY, OTP, EXTERNAL ### Description: SASL realm: # Please enter the SASL realm that will be used to authenticate to the LDAP # database. # . # The realm is appended to authentication and authorization identities. # . # For GSSAPI, this can be left blank to use information from the Kerberos # credentials cache. # d-i nslcd/ldap-sasl-realm string ### Description: SASL authentication identity: # Please enter the SASL authentication identity that will be used to authenticate to # the LDAP database. # . # This is the login used in LOGIN, PLAIN, CRAM-MD5, and DIGEST-MD5 mechanisms. # d-i nslcd/ldap-sasl-authcid string ### Description: SASL proxy authorization identity: # Please enter the proxy authorization identity that will be used to authenticate to # the LDAP database. # . # This is the object in the name of which the LDAP request is done. # This value should be specified as a DN (distinguished name). # d-i nslcd/ldap-sasl-authzid string ### Description: Cyrus SASL security properties: # Please enter the Cyrus SASL security properties. # . # Allowed values are described in the ldap.conf(5) manual page # in the SASL OPTIONS section. # d-i nslcd/ldap-sasl-secprops string ### Description: Kerberos credential cache file path: # Please enter the GSSAPI/Kerberos credential cache file name that will be used. # d-i nslcd/ldap-sasl-krb5-ccname string /run/nslcd/nslcd.tkt ### Description: Use StartTLS? # Please choose whether the connection to the LDAP server should use # StartTLS to encrypt the connection. # d-i nslcd/ldap-starttls boolean ### Description: Check server's SSL certificate: # When an encrypted connection is used, a server certificate can be requested # and checked. Please choose whether lookups should be configured to require # a certificate, and whether certificates should be checked for validity: # . # * never: no certificate will be requested or checked; # * allow: a certificate will be requested, but it is not # required or checked; # * try: a certificate will be requested and checked, but if no # certificate is provided, it is ignored; # * demand: a certificate will be requested, required, and checked. # d-i nslcd/ldap-reqcert select # Possible choices: never, allow, try, demand ### Description: Certificate authority certificate: # When certificate checking is enabled this file contains the X.509 # certificate that is used to check the certificate provided by the server. # d-i nslcd/ldap-cacertfile string /etc/ssl/certs/ca-certificates.crt ############################ #### pynslcd_0.9.12-4_all.deb ############################ ### Description: LDAP server URI: # Please enter the Uniform Resource Identifier of the LDAP server. The format # is "ldap://:/". Alternatively, "ldaps://" or # "ldapi://" can be used. The port number is optional. # . # When using an ldap or ldaps scheme it is recommended to use an IP address to # avoid failures when domain name services are unavailable. # . # Multiple URIs can be separated by spaces. # d-i nslcd/ldap-uris string ### Description: LDAP server search base: # Please enter the distinguished name of the LDAP search base. Many sites use # the components of their domain names for this purpose. For example, the # domain "example.net" would use "dc=example,dc=net" as the distinguished name # of the search base. # d-i nslcd/ldap-base string ### Description: LDAP authentication to use: # Please choose what type of authentication the LDAP database should # require (if any): # . # * none: no authentication; # * simple: simple bind DN and password authentication; # * SASL: any Simple Authentication and Security Layer mechanism. # d-i nslcd/ldap-auth-type select # Possible choices: none, simple, SASL ### Description: LDAP database user: # Please enter the name of the account that will be used to log in to the LDAP # database. This value should be specified as a DN (distinguished name). # d-i nslcd/ldap-binddn string ### Description: LDAP user password: # Please enter the password that will be used to log in to the LDAP database. # d-i nslcd/ldap-bindpw password ### Description: SASL mechanism to use: # Please choose the SASL mechanism that will be used to authenticate to the LDAP # database: # . # * auto: auto-negotiation; # * LOGIN: deprecated in favor of PLAIN; # * PLAIN: simple cleartext password mechanism; # * NTLM: NT LAN Manager authentication mechanism; # * CRAM-MD5: challenge-response scheme based on HMAC-MD5; # * DIGEST-MD5: HTTP Digest compatible challenge-response scheme; # * SCRAM: salted challenge-response mechanism; # * GSSAPI: used for Kerberos; # * SKEY: S/KEY mechanism (obsoleted by OTP); # * OTP: One Time Password mechanism; # * EXTERNAL: authentication is implicit in the context. # d-i nslcd/ldap-sasl-mech select # Possible choices: auto, LOGIN, PLAIN, NTLM, CRAM-MD5, DIGEST-MD5, SCRAM, GSSAPI, SKEY, OTP, EXTERNAL ### Description: SASL realm: # Please enter the SASL realm that will be used to authenticate to the LDAP # database. # . # The realm is appended to authentication and authorization identities. # . # For GSSAPI, this can be left blank to use information from the Kerberos # credentials cache. # d-i nslcd/ldap-sasl-realm string ### Description: SASL authentication identity: # Please enter the SASL authentication identity that will be used to authenticate to # the LDAP database. # . # This is the login used in LOGIN, PLAIN, CRAM-MD5, and DIGEST-MD5 mechanisms. # d-i nslcd/ldap-sasl-authcid string ### Description: SASL proxy authorization identity: # Please enter the proxy authorization identity that will be used to authenticate to # the LDAP database. # . # This is the object in the name of which the LDAP request is done. # This value should be specified as a DN (distinguished name). # d-i nslcd/ldap-sasl-authzid string ### Description: Cyrus SASL security properties: # Please enter the Cyrus SASL security properties. # . # Allowed values are described in the ldap.conf(5) manual page # in the SASL OPTIONS section. # d-i nslcd/ldap-sasl-secprops string ### Description: Kerberos credential cache file path: # Please enter the GSSAPI/Kerberos credential cache file name that will be used. # d-i nslcd/ldap-sasl-krb5-ccname string /run/nslcd/nslcd.tkt ### Description: Use StartTLS? # Please choose whether the connection to the LDAP server should use # StartTLS to encrypt the connection. # d-i nslcd/ldap-starttls boolean ### Description: Check server's SSL certificate: # When an encrypted connection is used, a server certificate can be requested # and checked. Please choose whether lookups should be configured to require # a certificate, and whether certificates should be checked for validity: # . # * never: no certificate will be requested or checked; # * allow: a certificate will be requested, but it is not # required or checked; # * try: a certificate will be requested and checked, but if no # certificate is provided, it is ignored; # * demand: a certificate will be requested, required, and checked. # d-i nslcd/ldap-reqcert select # Possible choices: never, allow, try, demand ### Description: Certificate authority certificate: # When certificate checking is enabled this file contains the X.509 # certificate that is used to check the certificate provided by the server. # d-i nslcd/ldap-cacertfile string /etc/ssl/certs/ca-certificates.crt ############################ #### nullmailer_2.2-4_amd64.deb ############################ ### Description: Mailname of your system: # This is the fully-qualified host name of the computer running nullmailer. # It defaults to the literal name 'me'. # d-i shared/mailname string ### Description: The domain name to be appended to hostnames: # This is the domain name which will be added to any hostnames that don't # contain a dot (that is to say, which aren't already qualified by a domain). # d-i nullmailer/defaultdomain string ### Description: Smarthosts: # This is a colon-separated list of remote servers to which to send each # message. Each entry contains a remote host name or address followed by # an optional protocol string 'host protocol'. The protocol name defaults # to smtp, and may be followed by command-line arguments for that module. # . # Examples: # . # smarthost # smarthost smtp --port=10025 # mail.example.com smtp --user=foo --pass=bar # 192.168.1.254 qmqp # [fe80::5054:ff:fef4:ef81] smtp # d-i nullmailer/relayhost string ### Description: Where to send local emails (optional): # If not empty, all recipients to users at either 'localhost' (the literal # string) or the canonical host name (from /etc/mailname) are remapped to # this address. This is provided to allow local daemons to be able to send # email to 'somebody@localhost' and have it go somewhere sensible instead of # being bounced by your relay host. # d-i nullmailer/adminaddr string ############################ #### ocfs2-tools_1.8.7-1+b1_amd64.deb ############################ ### Description: Would you like to start an OCFS2 cluster (O2CB) at boot time? # d-i ocfs2-tools/init boolean false ### Description: Name of the cluster to start at boot time: # d-i ocfs2-tools/clustername string ocfs2 ### Description: O2CB heartbeat threshold: # The O2CB heartbeat threshold sets up the maximum time in seconds that a # node awaits for an I/O operation. After it, the node "fences" itself, # and you will probably see a crash. # . # It is calculated as the result of: (threshold - 1) x 2. # . # Its default value is 31 (60 seconds). # . # Raise it if you have slow disks and/or crashes with kernel messages # like: # . # o2hb_write_timeout: 164 ERROR: heartbeat write timeout to device XXXX # after NNNN milliseconds # d-i ocfs2-tools/heartbeat_threshold string 31 ### Description: O2CB idle timeout: # The O2CB idle timeout (expressed in milliseconds) is the time before # a network connection is considered dead. # . # Its default value is 30000 (30 seconds) and the minimum recommended value # is 5000 (5 seconds). # d-i ocfs2-tools/idle_timeout string 30000 ### Description: O2CB keepalive delay: # The O2CB keepalive delay (expressed in milliseconds) is the maximum time before # a keepalive packet is sent. # . # Its default value is 2000 (2 seconds) and the minimum recommended value # is 1000 (1 second). # d-i ocfs2-tools/keepalive_delay string 2000 ### Description: O2CB reconnect delay: # The O2CB reconnect delay (expressed in milliseconds) is the minimum time between # connection attempts. # . # Its default and recommended minimum value is 2000 (2 seconds). # d-i ocfs2-tools/reconnect_delay string 2000 ############################ #### ocsinventory-agent_2.10.0-3_amd64.deb ############################ ### Description: Method used to generate the inventory: # Choose the 'local' method if you do not have a network connection. # . # Choose the 'http' method if an OCS Inventory server is set up. # d-i ocsinventory-agent/method select local # Possible choices: local, http ### Description: OCS Inventory server URL: # Please enter the URL of the OCS inventory server. # d-i ocsinventory-agent/server string ### Description: Tag for the generated inventory: # Each inventory can have an associated tag. Please enter the tag you would # like for the new inventory. # . # This field can be left blank to continue without setting a new tag for the # inventory. # d-i ocsinventory-agent/tag string ############################ #### octavia-api_11.0.0-2_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i octavia/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i octavia/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i octavia/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i octavia/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i octavia/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i octavia/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i octavia/api-endpoint-address string ### Description: This service endpoint protocol: # d-i octavia/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i octavia/api-endpoint-region-name string regionOne ############################ #### octavia-common_11.0.0-2_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i octavia/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i octavia/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i octavia/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i octavia/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i octavia/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i octavia/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i octavia/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i octavia/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i octavia/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i octavia/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i octavia/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i octavia/ksat-admin-password password ### Description: Auth server service username: # d-i octavia/ksat-service-username string ### Description: Auth server service project name: # d-i octavia/ksat-service-project-name string service ### Description: Auth server service password: # d-i octavia/ksat-service-password password ############################ #### octavia-health-manager_11.0.0-2_all.deb ############################ ### Description: Configure health-manager with debconf ? # Octavia health-manager needs to have bind_ip, # bind_port and heartbeat_key configured. # This can be configured via debconf. # d-i octavia/configure_health_manager boolean false ### Description: Value for health_manager bind_ip: # IP address of Octavia health_manager on which will listen for heart beats. # This IP has to be in external octavia LB network to be able communicate # with amphora instances. # This value will be set in config block health_manager bind_ip. # d-i octavia/health_manager_bind_ip string 127.0.0.1 ### Description: Value for health_manager bind_port: # IP port of Octavia health_manager on which will listen for heart beats. # This value will be set in config block health_manager bind_port. # d-i octavia/health_manager_bind_port string 5555 ### Description: Octavia's hearthbeat_key: # Key used to validate amphora sending the message. # This value will be set in config block health_manager, heartbeat_key. # d-i octavia/hearthbeat_key string insecure ############################ #### oneliner-el_0.3.6-9.2_all.deb ############################ ### Description: Should oneliner-el be auto-loaded by default at your site? # If you want to auto-load oneliner-el at your site, you should accept here. # . # If you accept here, oneliner-el are loaded globally, i.e. all people in # your site can use oneliner-el without special settings in their # "~/.emacs". If your site is a single user site and you want to use # oneliner-el, you should accept here without hesitating. # . # If you refuse here, people who desire to use it will have to put the # string "(require 'oneliner)" in their "~/.emacs" to load it. # d-i oneliner-el/default boolean true ############################ #### open-infrastructure-compute-tools_20221223-3_all.deb ############################ ### Description: machines directory: # Please specify the directory that will be used to store the containers. # . # If unsure, use /var/lib/machines (default) or /srv/container/system when # using shared storage. # d-i open-infrastructure-compute-tools/machines-directory string /var/lib/machines ### Description: config directory: # Please specify the directory that will be used to store the container # configuration files. # . # If unsure, use /etc/compute-tools/config (default) or # /srv/container/config when using shared storage. # d-i open-infrastructure-compute-tools/config-directory string /etc/compute-tools/config ### Description: debconf directory: # Please specify the directory that will be used to store the container # preseed files. # . # If unsure, use /etc/compute-tools/debconf (default) or # /srv/container/debconf when using shared storage. # d-i open-infrastructure-compute-tools/debconf-directory string /etc/compute-tools/debconf ### Description: hooks directory: # Please specify the directory that will be used to store the container # hooks. # . # If unsure, use /etc/compute-tools/hooks (default) or /srv/container/hooks # when using shared storage. # d-i open-infrastructure-compute-tools/hooks-directory string /etc/compute-tools/hooks ### Description: keys directory: # Please specify the directory that will be used to store the container keys # for verifying container image downloads. # . # If unsure, use /etc/compute-tools/keys (default) or /srv/container/keys # when using shared storage. # d-i open-infrastructure-compute-tools/keys-directory string /etc/compute-tools/keys ### Description: cache directory: # Please specify the directory that will be used to cache files during # creation of containers. # . # If unsure, use /var/cache/container (default) or /srv/container/cache when # using shared storage. # d-i open-infrastructure-compute-tools/cache-directory string /var/cache/container ### Description: Do you want system-wide readable container directories? # By default, the machines directory (and a few non-critical additional # directories such as 'cache' and 'config') is only readable by the root # user. If you want any user to be able to see what machines are available, # you can select read-only instead of root-only (default). # . # If unsure, leave at root-only (default). # d-i open-infrastructure-compute-tools/directory-permissions select root-only # Possible choices: root-only, read-only ### Description: default build script: # Please select the script that will be used by default to create # containers. # . # If unsure, use debian (default). # d-i open-infrastructure-compute-tools/build-script select debian # Possible choices: ${SCRIPT_CHOICES} ### Description: IRC notifications: # The container command can send IRC notifications via irker to one or more # (whitespace separated) IRC channels. # . # The following example will send IRC notifications to the # open-infrastructure channel on irc.oftc.net: # . # irc://irc.oftc.net:6668/open-infrastructure # . # If unsure, leave empty (default). # d-i open-infrastructure-compute-tools/irc string ############################ #### open-infrastructure-storage-tools_20190301-lts1-5_all.deb ############################ ### Description: ceph-log: # ceph-log stores Ceph cluster log as a logfile, see ceph-log(1). # . # Should ceph-log be enabled? # d-i open-infrastructure-storage-tools/ceph-log boolean false ### Description: ceph-info: # ceph-info shows Ceph cluster information as a HTML page, see ceph-info(1). # . # Should ceph-info be enabled? # d-i open-infrastructure-storage-tools/ceph-info boolean false ### Description: cephfs-snap: # cephfs-snap creates CephFS snapshots periodically, see cephfs-snap(1). # . # Should cephfs-snap be enabled? # d-i open-infrastructure-storage-tools/cephfs-snap boolean false ### Description: cephfs-snap directories: # Please specify the directories (space separated) where CephFS are mounted # that should be snapshoted. # . # If unsure, leave empty. # d-i open-infrastructure-storage-tools/cephfs-snap-directories string ### Description: cephfs-snap hourly: # Please specify the number of hourly snapshots that should be kept. # . # Depending on the use case a reasonable default might be to keep hourly # snapshots for 1 week, means: (24 * 7) + 1 = 169 # . # If unsure, leave empty (no automatic hourly snapshot rotation). # d-i open-infrastructure-storage-tools/cephfs-snap-hourly string 169 ### Description: cephfs-snap daily: # Please specify the number of daily snapshots that should be kept. # . # Depending on the use case a reasonable default might be to keep daily # snapshots for 1 month, means: (31 * 1) + 1 = 32 # . # If unsure, leave empty (no automatic daily snapshot rotation). # d-i open-infrastructure-storage-tools/cephfs-snap-daily string 32 ### Description: cephfs-snap weekly: # Please specify the number of weekly snapshots that should be kept. # . # Depending on the use case a reasonable default might be to keep weekly # snapshots for 6 months, means: (6 * 4) + 1 = 25 # . # If unsure, leave empty (no automatic weekly snapshot rotation). # d-i open-infrastructure-storage-tools/cephfs-snap-weekly string 25 ### Description: cephfs-snap monthly: # Please specify the number of monthly snapshots that should be kept. # . # Depending on the use case a reasonable default might be to keep monthly # snapshots for 1 year, means: (12 * 1) + 1 = 13 # . # If unsure, leave empty (no automatic monthly snapshot rotation). # d-i open-infrastructure-storage-tools/cephfs-snap-monthly string 13 ### Description: cephfs-snap yearly: # Please specify the number of yearly snapshots that should be kept. # . # Depending on the use case a reasonable default might be to keep yearly # snapshots for 10 years, means: (10 * 1) + 1 = 11 # . # If unsure, leave empty (no automatic yearly snapshot rotation). # d-i open-infrastructure-storage-tools/cephfs-snap-yearly string 11 ### Description: IRC notifications: # The cephfs-snap command can send IRC notifications via irker to one or # more (whitespace separated) IRC channels. # . # The following example will send IRC notifications to the # open-infrastructure channel on irc.oftc.net: # . # irc://irc.oftc.net:6668/open-infrastructure # . # If unsure, leave empty (default). # d-i open-infrastructure-storage-tools/irc string ############################ #### open-iscsi_2.1.8-1_amd64.deb ############################ ### Description: Proceed with removing open-iscsi? # There are currently active iSCSI sessions. If you remove open-iscsi # now this may lead to data loss and/or hang the system at shutdown. # . # Do not do this if this system's root filesystem is on iSCSI. # . # If you do proceed, open-iscsi will try to unmount all filesystems on # iSCSI and log out from current sessions. If that fails (because a # filesystem is still in use), the kernel will keep the current # iSCSI sessions open, but will not perform any recovery if there is an # interruption of the network connection (or if the target is rebooted). # . # If you really intend to remove open-iscsi, you should abort here and # then stop open-iscsi: # . # service open-iscsi stop # . # If that did not clean up everything, manually umount all filesystems # that are on iSCSI, manually dismantle the storage stack, and only then # log out from all iSCSI sessions: # . # iscsiadm -m node --logoutall=all # . # At that point, it should be safe to remove this package. # d-i open-iscsi/remove_even_with_active_sessions boolean ### Description: Proceed with upgrading open-iscsi? # There are currently failed iSCSI sessions. Upgrading open-iscsi may # cause data loss. # . # If you do not proceed, the preinstallation script will be aborted and # you will have the option to manually recover the iSCSI sessions. (Note # that aborting an upgrade is problematic if you are dist-upgrading your # entire system.) You may also recover the iSCSI sessions manually while # keeping this prompt open and then choose to proceed. Or you may choose # to proceed directly, after which iscsid will be restarted and session # recovery will be attempted once more. # d-i open-iscsi/upgrade_even_with_failed_sessions boolean ### Description: Proceed with downgrading open-iscsi? # You are trying to downgrade open-iscsi. Because of changes between the # version you are downgrading to and the version currently installed, # this downgrade will break the system. # . # If you really intend to downgrade, please follow the following procedure # instead: umount all iSCSI file systems, log out of all iSCSI sessions, # back up /etc/iscsi, purge open-iscsi, and reinstall the older version. # d-i open-iscsi/downgrade_and_break_system boolean ############################ #### open-isns-discoveryd_0.101-0.2+b1_amd64.deb ############################ ### Description: iSNS server name: # The iSNS discovery daemon will connect to an iSNS server at startup. # . # If left blank, the discovery daemon will not be started after # package installation, and you will have an opportunity to modify # the configuration file, /etc/isns/isnsdd.conf. # d-i open-isns-discoveryd/isns-server string ### Description: iSNS server public key file: # When authentication is enabled, the iSNS discovery daemon needs to # know the public key of the iSNS server. Please provide a file name # that contains the public key. It will then be copied to # /etc/isns/server_key.pub. # . # Alternatively, you may copy the server's public key to that location # yourself. # . # If left blank and /etc/isns/server_key.pub does not exist, # authentication will remain disabled. # d-i open-isns-discoveryd/server-pubkey string ### Description: iSNS discovery daemon private key file: # When authentication is enabled, the iSNS discovery daemon needs to # have a private key, where the corresponding public key is enrolled # with the iSNS server. Please provide a file name that contains the # private key. It will then be copied to /etc/isns/auth_key. # . # Alternatively, you may copy the discovery daemon's private key to that # location yourself. # . # If left blank and /etc/isns/auth_key does not exist, authentication # will remain disabled. # d-i open-isns-discoveryd/own-key string ### Description: Remove /etc/isns/auth_key? # The private authentication key /etc/isns/auth_key was likely copied # there during the installation of the open-isns-discoveryd package. If # you are using other iSNS-related utilities (such as the iSNS server or # isnsadm) that require this authentication key, you should not remove # it. # . # Otherwise, it is safe to remove it. # d-i open-isns-discoveryd/purge-auth-key boolean true ### Description: Remove /etc/isns/server_key.pub? # The iSNS server's public key /etc/isns/server_key.pub was likely # copied there during the installation of the open-isns-discoveryd # package. If you are using other iSNS-related utilities (such as # isnsadm) that require this public key, you should not remove it. # . # Otherwise, it is safe to remove it. # d-i open-isns-discoveryd/purge-server-key-pub boolean true ### Description: for internal use # Whether the postinst script should override the ServerAddress setting # in isnsdd.conf. Will be set by the config script. # d-i open-isns-discoveryd/isns-server-override boolean false ############################ #### open-isns-server_0.101-0.2+b1_amd64.deb ############################ ### Description: Remove /etc/isns/auth_key? # The private authentication key /etc/isns/auth_key was likely generated # during the installation of the open-isns-server package. If you are # using other iSNS-related utilities (such as the disocvery daemon or # isnsadm) that require this authentication key, you should not remove # it. # . # Otherwise, it is safe to remove it. # d-i open-isns-server/purge-auth-key boolean true ############################ #### openafs-client_1.8.9-1_amd64.deb ############################ ### Description: DB server host names for your home cell: # AFS uses the file /etc/openafs/CellServDB to hold the list of servers that # should be contacted to find parts of a cell. The cell you claim this # workstation belongs to is not in that file. Enter the host names of the # database servers separated by spaces. IMPORTANT: If you are creating a new # cell and this machine is to be a database server in that cell, only enter # this machine's name; add the other servers later after they are # functioning. Also, do not enable the AFS client to start at boot on this # server until the cell is configured. When you are ready you can edit # /etc/openafs/afs.conf.client to enable the client. # d-i openafs-client/cell-info string ### Description: AFS cell this workstation belongs to: # AFS filespace is organized into cells or administrative domains. # Each workstation belongs to one cell. Usually the cell is the DNS # domain name of the site. # d-i openafs-client/thiscell string ### Description: Size of AFS cache in kB: # AFS uses an area of the disk to cache remote files for faster # access. This cache will be mounted on /var/cache/openafs. It is # important that the cache not overfill the partition it is located # on. Often, people find it useful to dedicate a partition to their # AFS cache. # d-i openafs-client/cachesize string 50000 ### Description: Run Openafs client now and at boot? # Normally, most users who install the openafs-client package expect AFS to # be mounted automatically at boot. However, if you are planning on # setting up a new cell or are on a laptop, you may not want it started at # boot time. If you choose not to start AFS at boot, run # service openafs-client force-start to start the client when you wish # to run it. # d-i openafs-client/run-client boolean true ### Description: Look up AFS cells in DNS? # In order to contact an AFS cell, you need the IP addresses of the cell's # database servers. Normally, this information is read from # /etc/openafs/CellServDB. However, if Openafs cannot find a cell in that # file, it can use DNS to look for AFSDB records that contain the # information. # d-i openafs-client/afsdb boolean true ### Description: Encrypt authenticated traffic with AFS fileserver? # AFS provides a weak form of encryption that can optionally be used between # a client and the fileservers. While this encryption is weaker than DES # and thus is not sufficient for highly confidential data, it does provide # some confidentiality and is likely to make the job of a casual attacker # significantly more difficult. # d-i openafs-client/crypt boolean true ### Description: Dynamically generate the contents of /afs? # /afs generally contains an entry for each cell that a client can talk to. # Traditionally, these entries were generated by servers in the client's # home cell. However, OpenAFS clients can generate the contents of /afs # dynamically based on the contents of /etc/openafs/CellServDB and DNS. # . # If you generate /afs dynamically, you may need to create # /etc/openafs/CellAlias to include aliases for common cells. (The syntax # of this file is one line per alias, with the cell name, a space, and then # the alias for that cell.) # . # The Sparse option is the same as Yes except that, rather than populating # /afs from /etc/openafs/CellServDB immediately, cells other than the local # cell will not appear until they are accessed. Cell aliases as set in the # CellAlias file are shown as normal, although they may appear to be # dangling links until traversed. # d-i openafs-client/dynroot select Yes # Possible choices: Yes, Sparse, No ### Description: Use fakestat to avoid hangs when listing /afs? # Because AFS is a global file space, operations on the /afs directory can # generate significant network traffic. If some AFS cells are unavailable # then looking at /afs using ls or a graphical file browser may hang your # machine for minutes. AFS has an option to simulate answers to these # operations locally to avoid these hangs. You want this option under most # circumstances. # d-i openafs-client/fakestat boolean true ############################ #### openafs-fileserver_1.8.9-1_amd64.deb ############################ ### Description: Cell this server serves files for: # AFS fileservers belong to a cell. They have the key for that cell's # Kerberos service and serve volumes into that cell. Normally, this cell is # the same cell as the workstation's client belongs to. # d-i openafs-fileserver/thiscell string ############################ #### opendmarc_1.4.2-2+b1_amd64.deb ############################ ### Description: Configure database for OpenDMARC with dbconfig-common? # To generate aggregate feedback reports a database is needed. This can # be optionally handled with dbconfig-common. # . # If you are an advanced database administrator and know that you want to # perform this configuration manually, or if your database has already # been installed and configured, you should refuse this option. Details # on what needs to be done are provided in # /usr/share/doc/opendmarc/README.Debian. # . # Otherwise, you should probably choose this option. # d-i opendmarc/dbconfig-install boolean true ############################ #### opendnssec-common_2.1.12-2_all.deb ############################ ############################ #### openguides_0.84-1_all.deb ############################ ### Description: Okay to proceed with upgrade? # You are trying to upgrade from a version of OpenGuides that used an old # database schema. The migration is somewhat risky and so it is strongly # recommended that you backup your OpenGuides databases before proceeding. # d-i openguides/check_old_upgrade boolean ############################ #### slapd_2.5.13+dfsg-5_amd64.deb ############################ ### Description: Omit OpenLDAP server configuration? # If you enable this option, no initial configuration or database will be # created for you. # d-i slapd/no_configuration boolean false ### Description: Dump databases to file on upgrade: # Before upgrading to a new version of the OpenLDAP server, the data from # your LDAP directories can be dumped into plain text files in the # standard LDAP Data Interchange Format. # . # Selecting "always" will cause the databases to be dumped # unconditionally before an upgrade. Selecting "when needed" will only # dump the database if the new version is incompatible with the old # database format and it needs to be reimported. If you select "never", # no dump will be done. # d-i slapd/dump_database select when needed # Possible choices: always, when needed, never ### Description: Directory to use for dumped databases: # Please specify the directory where the LDAP databases will be exported. # In this directory, several LDIF files will be created which correspond # to the search bases located on the server. Make sure you have enough # free space on the partition where the directory is located. The first # occurrence of the string "VERSION" is replaced with the server version # you are upgrading from. # d-i slapd/dump_database_destdir string /var/backups/slapd-VERSION ### Description: Move old database? # There are still files in /var/lib/ldap which will probably break # the configuration process. If you enable this option, the maintainer # scripts will move the old database files out of the way before # creating a new database. # d-i slapd/move_old_database boolean true ### Description: Retry configuration? # The configuration you entered is invalid. Make sure that the DNS domain name # is syntactically valid, the field for the organization is not left empty and # the admin passwords match. If you decide not to retry the configuration the # LDAP server will not be set up. Run 'dpkg-reconfigure slapd' if you want to # retry later. # d-i slapd/invalid_config boolean true ### Description: DNS domain name: # The DNS domain name is used to construct the base DN of the LDAP directory. # For example, 'foo.example.org' will create the directory with # 'dc=foo, dc=example, dc=org' as base DN. # d-i slapd/domain string ### Description: Organization name: # Please enter the name of the organization to use in the base DN of your # LDAP directory. # d-i shared/organization string ### Description: Administrator password: # Please enter the password for the admin entry in your LDAP directory. # d-i slapd/password1 password ### Description: Confirm password: # Please enter the admin password for your LDAP directory again to verify # that you have typed it correctly. # d-i slapd/password2 password ### Description: Do you want the database to be removed when slapd is purged? # d-i slapd/purge_database boolean false ### Description: Encrypted admin password: # Internal template, should never be displayed to users. # d-i slapd/internal/adminpw password ### Description: Generated admin password: # Internal template, should never be displayed to users. # d-i slapd/internal/generated_adminpw password ############################ #### opensmtpd_6.8.0p2-4+b4_amd64.deb ############################ ### Description: System mail name: # The "mail name" is used as the domain name in the email address for # messages that only have a "local part" (such as or # ). It should be a fully qualified domain name (FQDN) that you are # entitled to use. # . # For instance, to allow the local host to generate mail with addresses # such as , set the system mail name to # "example.org". # . # This mail name is used as the hostname in the SMTP greeting banner, and # will also be used by other programs. # d-i opensmtpd/mailname string ### Description: Root and postmaster mail recipient: # Mail for the "postmaster", "root", and other system accounts should be # redirected to the user account(s) of the actual system administrator(s). # . # Please enter a comma-separated list of the usernames of the intended # recipients. Leave this field blank to not create an alias for "root"; # in this case, the root account will receive mail addressed to # "postmaster" and other system accounts, assuming aliases for these # accounts do not already exist. # d-i opensmtpd/root_address string ############################ #### openssh-server_9.2p1-2+deb12u2_amd64.deb ############################ ### Description: Disable SSH password authentication for root? # Previous versions of openssh-server permitted logging in as root over SSH # using password authentication. The default for new installations is now # "PermitRootLogin prohibit-password", which disables password authentication # for root without breaking systems that have explicitly configured SSH # public key authentication for root. # . # This change makes systems more secure against brute-force password # dictionary attacks on the root user (a very common target for such # attacks). However, it may break systems that are set up with the # expectation of being able to SSH as root using password authentication. You # should only make this change if you do not need to do that. # d-i openssh-server/permit-root-login boolean true ### Description: Allow password authentication? # By default, the SSH server will allow authenticating using a password. # You may want to change this if all users on this system authenticate using # a stronger authentication method, such as public keys. # d-i openssh-server/password-authentication boolean true ############################ #### openstack-cluster-installer_42.2.5_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i openstack-cluster-installer/configure_db boolean false ############################ #### trove-api_18.0.0-2_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i trove/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i trove/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i trove/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i trove/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i trove/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i trove/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i trove/api-endpoint-address string ### Description: This service endpoint protocol: # d-i trove/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i trove/api-endpoint-region-name string regionOne ############################ #### trove-common_18.0.0-2_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i trove/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i trove/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i trove/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i trove/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i trove/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i trove/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i trove/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i trove/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i trove/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i trove/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i trove/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i trove/ksat-admin-password password ### Description: Auth server service username: # d-i trove/ksat-service-username string ### Description: Auth server service project name: # d-i trove/ksat-service-project-name string service ### Description: Auth server service password: # d-i trove/ksat-service-password password ############################ #### openstreetmap-carto_5.7.0-1_all.deb ############################ ### Description: PostgreSQL database name: # The openstreetmap-carto stylesheet uses a PostgreSQL database to # store OpenStreetMap data. # . # Please choose the name for this database. # d-i openstreetmap-carto/database-name string gis ############################ #### openstreetmap-carto-common_5.7.0-1_all.deb ############################ ### Description: Download OpenStreetMap data files from the Internet? # The openstreetmap-carto stylesheet uses several data files that must # be downloaded from the Internet. # . # If you choose not to do this now, it can be done manually later # by running the "get-external-data.py" script in the /usr/share/openstreetmap-carto-common # directory. # d-i openstreetmap-carto/fetch-data boolean ############################ #### openvpn_2.6.3-1+deb12u2_amd64.deb ############################ ### Description: Create the TUN/TAP device? # If you choose this option, the /dev/net/tun device # needed by OpenVPN will be created. # . # You should not choose this option if you're using devfs. # d-i openvpn/create_tun boolean false ############################ #### osk-sdl_0.67.1-2_amd64.deb ############################ ### Description: Automatically clean crypttab? # Selecting this will result in instances of 'osk-sdl-keyscript' # being removed from /etc/crypttab on package removal. # d-i osk-sdl/prerm-config boolean ############################ #### libpam-modules_1.5.2-6+deb12u1_amd64.deb ############################ ############################ #### libpam-runtime_1.5.2-6+deb12u1_all.deb ############################ ### Description: PAM profiles to enable: # Pluggable Authentication Modules (PAM) determine how authentication, # authorization, and password changing are handled on the system, as well # as allowing configuration of additional actions to take when starting # user sessions. # . # Some PAM module packages provide profiles that can be used to # automatically adjust the behavior of all PAM-using applications on the # system. Please indicate which of these behaviors you wish to enable. # d-i libpam-runtime/profiles multiselect # Possible choices: ${profiles} ### Description: Override local changes to /etc/pam.d/common-*? # One or more of the files /etc/pam.d/common-{auth,account,password,session} # have been locally modified. Please indicate whether these local changes # should be overridden using the system-provided configuration. If you # decline this option, you will need to manage your system's # authentication configuration by hand. # d-i libpam-runtime/override boolean false ############################ #### libpam0g_1.5.2-6+deb12u1_amd64.deb ############################ ### Description: Services to restart for PAM library upgrade: # Most services that use PAM need to be restarted to use modules built for # this new version of libpam. Please review the following space-separated # list of services to be restarted now, and correct it # if needed. # d-i libpam0g/restart-services string ### Description: Restart services during package upgrades without asking? # There are services installed on your system which need to be restarted # when certain libraries, such as libpam, libc, and libssl, are upgraded. # Since these restarts may cause interruptions of service for the system, # you will normally be prompted on each upgrade for the list of services # you wish to restart. You can choose this option to avoid being prompted; # instead, all necessary restarts will be done for you automatically so you # can avoid being asked questions on each library upgrade. # d-i libraries/restart-without-asking boolean false ############################ #### pbuilder_0.231_all.deb ############################ ### Description: Default mirror site: # Please enter the default mirror you want to be used by pbuilder. # . # If you leave this field blank, there will be one attempt to autodetect # this information. If this attempt fails, you will be prompted again # to insert some valid mirror information. # . # Here is a valid mirror example: http://deb.debian.org/debian # d-i pbuilder/mirrorsite string ### Description: Overwrite current configuration? # Your system seems to have already pbuilder configuration. # Proceeding might discard or overwrite part or the entire # pbuilder's configuration. # d-i pbuilder/rewrite boolean false ############################ #### pconsole_1.2.0-1_amd64.deb ############################ ### Description: Do you want /usr/bin/pconsole to be installed SUID root? # You are strongly encouraged to leave pconsole without the SUID bit on. # . # If you are using a multiuser system, setting the SUID bit on pconsole will # be a major risk for a breach, since normal users will be able to attach # their consoles to a root PTY/TTY and send commands as root. # . # However, on a single-user system, setting the SUID bit might be a good # idea to avoid logging as root user. # . # If in doubt, you should install it without SUID. If it causes problems # you can change your mind later by running: dpkg-reconfigure pconsole # d-i pconsole/setuid boolean false ############################ #### pdsh_2.34-0.2_amd64.deb ############################ ### Description: Should the pdsh binary be installed setuid root? # The pdsh program can be installed setuid root, so that it will run with # the permissions of the 'root' user. # . # This is required for non-root accounts to use the rsh remote-command method # of pdsh. However, enabling this could be a security risk. # . # In short, unless you know what you are doing or have a very controlled # user base, you should not enable this feature. If you choose not to enable # setuid root, then you can still use pdsh through tools like sudo or with # the ssh remote-command module. # d-i pdsh/setuidroot boolean false ############################ #### perlindex_1.606-4_all.deb ############################ ### Description: Remove the index when purging the package? # perlindex creates some index files under /var/cache/perlindex/. # d-i perlindex/removeindexonpurge boolean true ############################ #### arcanist_0~git20220903-2_all.deb ############################ ############################ #### phalanx_25-1_amd64.deb ############################ ### Description: Learning file size (1-999999): # The learning file may improve Phalanx strength. Each item in this # file uses 8 bytes. # . # Please specify a number in the range 1-999999. The size may be # changed later by reconfiguring the package but this will erase any # data the file may then contain. # d-i phalanx/learning_file_size string 32768 ### Description: Really change the size of the learning file and erase its data? # You chose to change the size of the learning file used by phalanx # for improving its strength. This will erase all the learned data. # d-i phalanx/learning_file_erase boolean false ############################ #### phonon4qt5_4.11.1-4_amd64.deb ############################ ############################ #### phonon4qt5-backend-null_4.11.1-4_amd64.deb ############################ ############################ #### phpldapadmin_1.2.6.3-0.3_all.deb ############################ ### Description: LDAP server host address: # Please enter the host name or the address of the LDAP server you want to # connect to. # d-i phpldapadmin/ldap-server string 127.0.0.1 ### Description: Enable support for ldaps protocol? # If your LDAP server supports TLS (Transport Security Layer), you can use # the ldaps protocol to connect to it. # d-i phpldapadmin/ldap-tls boolean false ### Description: Distinguished name of the search base: # Please enter the distinguished name of the LDAP search base. Many sites # use the components of their domain names for this purpose. For example, # the domain "example.com" would use "dc=example,dc=com" as the # distinguished name of the search base. # d-i phpldapadmin/ldap-basedn string dc=example,dc=com ### Description: Type of authentication # session : You will be prompted for a login dn and a password everytime # you connect to phpLDAPadmin, and a session variable on the # web server will store them. It is more secure so this is the # default. # . # cookie : You will be prompted for a login dn and a password everytime # you connect to phpLDAPadmin, and a cookie on your client will # store them. # . # config : login dn and password are stored in the configuration file, # so you have not to specify them when you connect to # phpLDAPadmin. # d-i phpldapadmin/ldap-authtype select session # Possible choices: session, cookie, config ### Description: Login dn for the LDAP server: # Enter the name of the account that will be used to log in to the LDAP # server. If you chose a form based authentication this will be the # default login dn. In this case you can also leave it empty, if you do # not want a default one. # d-i phpldapadmin/ldap-binddn string cn=admin,dc=example,dc=com ### Description: Login password for the LDAP server: # Enter the password that will be used to log in to the LDAP server. Note: # the password will be stored in clear text in config.php, which is not # world-readable. # d-i phpldapadmin/ldap-bindpw string secret ### Description: Web server(s) which will be reconfigured automatically: # phpLDAPadmin supports any web server that PHP does, but this automatic # configuration process only supports Apache2. # d-i phpldapadmin/reconfigure-webserver multiselect apache2 # Possible choices: apache2 ### Description: Should your webserver(s) be restarted? # Remember that in order to apply the changes your webserver(s) has/have to # be restarted. # d-i phpldapadmin/restart-webserver boolean true ############################ #### phpmyadmin_5.2.1+dfsg-1_all.deb ############################ ### Description: Web server to reconfigure automatically: # Please choose the web server that should be automatically configured # to run phpMyAdmin. # d-i phpmyadmin/reconfigure-webserver multiselect # Possible choices: apache2, lighttpd ############################ #### phpsysinfo_3.4.2-3_all.deb ############################ ### Description: Web server to reconfigure automatically: # Please choose the web server that should be automatically configured # to run phpSysInfo. # d-i phpsysinfo/reconfigure-webserver multiselect # Possible choices: apache2, nginx, lighttpd ### Description: Do you want to restart the webservers now if needed? # Remember that in order to activate the new configuration # the webservers have to be restarted. # d-i phpsysinfo/restart-webserver boolean true ############################ #### pinto_0.14000-2_all.deb ############################ ### Description: Pinto web administration password: # Please choose the password for the "pintoadmin" user. # . # This username/password combination is needed, after installation, to log # in to Pinto through its web interface. # . # If this is left empty, you will have to manually configure # accounts for Pinto. # d-i pinto/adminpassword password ### Description: Re-enter password to verify: # Please enter the same user password again to verify you have typed it # correctly. # d-i pinto/adminpassword-repeat password ############################ #### pioneers-metaserver_15.6-1+b1_amd64.deb ############################ ### Description: Port range for creating new games on the metaserver: # The metaserver can create new games, so players don't need to install and # run the pioneers server. The ports which are used for these games can be # specified. If this field is left empty, the metaserver will disable its # game creation functionality. # . # If the value is not empty, it must be two port numbers, separated by a minus # sign. # d-i pioneers-metaserver/ports string 5560-5569 ### Description: Server name for created games: # In some cases, the name the metaserver uses for itself when creating new # games is incorrect. If this field is not left empty, it is used to override # the detected hostname. # d-i pioneers-metaserver/name string ### Description: Extra arguments to pass to the metaserver: # These arguments are passed to the metaserver. # * --redirect: Redirect clients to another metaserver # d-i pioneers-metaserver/arguments string ############################ #### placement-api_8.0.0-2_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i placement/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i placement/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i placement/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i placement/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i placement/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i placement/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i placement/api-endpoint-address string ### Description: This service endpoint protocol: # d-i placement/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i placement/api-endpoint-region-name string regionOne ############################ #### placement-common_8.0.0-2_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i placement/configure_db boolean false ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i placement/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i placement/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i placement/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i placement/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i placement/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i placement/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i placement/ksat-admin-password password ### Description: Auth server service username: # d-i placement/ksat-service-username string ### Description: Auth server service project name: # d-i placement/ksat-service-project-name string service ### Description: Auth server service password: # d-i placement/ksat-service-password password ############################ #### playmidi_2.4debian-13_amd64.deb ############################ ### Description: Options for playmidi when invoked through MIME: # The playmidi package sets up a MIME entry which allows mail user agents # and other applications to play MIDI files. # . # In order for playmidi to work properly, you may need to set # hardware-specific options: # . # '-a': Sound Blaster AWE32; # '-e': external MIDI device, Ensoniq SoundScape, Turtle # Beach WaveFront or WaveBlaster sound card; # '-g': Gravis Ultrasound. # . # Most other cards require no specific options and will work with this # field left blank. This setting is kept in # /etc/playmidi/playmidi.conf. # d-i playmidi/options string ############################ #### plptools_1.0.13-2_amd64.deb ############################ ### Description: Should ncpd be started during boot? # Normally, ncpd - the daemon which handles the serial connection to a # Psion - is started on boot-up. If you intend to connect your Psion to # another machine on the net and NEVER will use it locally, you can # disable this here. # d-i plptools/ncpd/start boolean true ### Description: Serial line to use: # By default, the Psion is expected to be connected to the first serial # line (COM1:) of your machine. You can change this here. # d-i plptools/ncpd/serial string /dev/ttyS0 ### Description: IP address and port for ncpd: # If you intend to use the plptools front-ends from other machines, you # can specify 0.0.0.0 or the IP address of your machine here. Normal # users should keep the default 127.0.0.1! # . # Note, that THIS IS A SECURITY THREAT as no authentication and no # encryption is used! DO NOT USE THIS on machines which are accessible # from the Internet! # d-i plptools/ncpd/listenat string 127.0.0.1 ### Description: Should plpfuse be started during boot? # If plpfuse is started during boot-up, it will wait for a Psion being # connected and then automatically mount that Psion. Since this is # done as root, non-privileged users will not have access to the # mounted directory. If you have a single-user machine, you probably # want to start plpfuse manually when you need it. # d-i plptools/plpfuse/start boolean false ### Description: Should plpprintd be started during boot? # If you intend to use the Psion's "Print via PC" feature, you can # enable this option. You must have a working print queue which # is capable of printing Postscript in order to use this feature. # d-i plptools/plpprintd/start boolean false ### Description: Print queue to use: # Please enter the name of the print queue you want to use for # printing from the Psion. # d-i plptools/plpprintd/printqueue string psion ### Description: Remote host to be contacted: # Since you have ncpd either disabled or listening on a non-standard # address, you should specify the address for the frontends again. # d-i plptools/frontends/remoteaddr string ############################ #### printer-driver-pnm2ppa_1.13-13+b1_amd64.deb ############################ ### Description: Would you like debconf to configure pnm2ppa? # You can have debconf perform some simple configuration steps for your # default pnm2ppa setup (edited in your /etc/pnm2ppa.conf file). # d-i pnm2ppa/use_debconf boolean true ### Description: What model of HP Deskjet printer do you use? # The pnm2ppa printer filter behaves differently depending upon which HP # DeskJet model you use. Choose your model of printer for the default # configuration file /etc/pnm2ppa.conf. # d-i pnm2ppa/printer_model select 710 # Possible choices: 710, 712, 720, 722, 820, 1000 ### Description: Would you like debconf to create magicfilter filters? # Magicfilter is a customizable, extensible automatic printer filter. It # uses its own magic database (a la file(1)) to decide how to print out a # given print job. Debconf can run the custom pnm2ppa script called # "update-magicfilter" to generate a default set of filters for color and # black-and-white printing. # . # The template filter is found in /usr/share/pnm2ppa/ as # "pnm2ppa-magicfilter.in". update-magicfilter uses sed to replace # @OPTIONS@ from the template and place the resulting filters in # /etc/magicfilter. Additionally, symbolic links are created from the # generated pnm2ppa filters to pbm2ppa filters (the deprecated # predecessor to pnm2ppa). # . # The only thing left for you to do is run magicfilterconfig to # generate your /etc/printcap. # d-i pnm2ppa/create_magicfilter boolean false ############################ #### popa3d_1.0.3-1.1_amd64.deb ############################ ### Description: Run popa3d in standalone mode? # In standalone mode, popa3d will become a daemon, accepting connections on # the pop3 port (110/tcp) and forking child processes to handle them. This # has lower overhead than starting popa3d from an inetd equivalent and is # thus useful on busy servers to reduce load. See popa3d(8) for more # details. # d-i popa3d/standalone boolean true ############################ #### popularity-contest_1.76_all.deb ############################ ### Description: Participate in the package usage survey? # The system may anonymously supply the distribution developers with # statistics about the most used packages on this system. This # information influences decisions such as which packages should go on # the first distribution CD. # . # If you choose to participate, the automatic submission script will # run once every week, sending statistics to the distribution developers. # The collected statistics can be viewed on https://popcon.debian.org/. # . # This choice can be later modified by running "dpkg-reconfigure # popularity-contest". # d-i popularity-contest/participate boolean false ### Description: for internal use # Preseed this during installation to replace the URL used for # submitting reports. # d-i popularity-contest/submiturls string ############################ #### portsentry_1.2-14+b1_amd64.deb ############################ ############################ #### posh_0.14.1_amd64.deb ############################ ### Description: Install posh as /bin/sh? # dash is the default /bin/sh on a Debian system. However, since our policy # requires all shell scripts using /bin/sh to be POSIX-compliant, any shell # that conforms to POSIX can serve as /bin/sh. Since posh is # POSIX-compliant, it can be used as /bin/sh. # d-i posh/sh boolean false ############################ #### postfix_3.7.10-0+deb12u1_amd64.deb ############################ ### Description: Ignore incorrect hostname entry? # The string '${enteredstring}' does not follow RFC 1035 and does not # appear to be a valid IP address. # . # RFC 1035 states that 'each component must start with an alphanum, end with # an alphanum and contain only alphanums and hyphens. Components must be # separated by full stops.' # . # Please check and confirm if you want to keep your entry. # d-i postfix/rfc1035_violation boolean false ### Description: General mail configuration type: # Please select the mail server configuration type that best meets your needs. # . # No configuration: # Should be chosen to leave the current configuration unchanged. # Internet site: # Mail is sent and received directly using SMTP. # Internet with smarthost: # Mail is received directly using SMTP or by running a utility such # as fetchmail. Outgoing mail is sent using a smarthost. # Satellite system: # All mail is sent to another machine, called a 'smarthost', for # delivery. # Local only: # The only delivered mail is the mail for local users. There is no # network. # d-i postfix/main_mailer_type select Internet Site # Possible choices: No configuration, Internet Site, Internet with smarthost, Satellite system, Local only ### Description: System mail name: # The 'mail name' is the domain name used to 'qualify' _ALL_ mail addresses # without a domain name. This includes mail to and from : please do not # make your machine send out mail from root@example.org unless root@example.org # has told you to. # . # This name will also be used by other programs. It should be the # single, fully qualified domain name (FQDN). # . # Thus, if a mail address on the local host is foo@example.org, # the correct value for this option would be example.org. # . # d-i postfix/mailname string /etc/mailname ### Description: Other destinations to accept mail for (blank for none): # Please give a comma-separated list of domains for which this machine # should consider itself the final destination. If this is a mail # domain gateway, you probably want to include the top-level domain. # d-i postfix/destinations string ### Description: SMTP relay host (blank for none): # Please specify a domain, host, host:port, [address] or # [address]:port. Use the form [destination] to turn off MX lookups. # Leave this blank for no relay host. # . # Do not specify more than one host. # . # The relayhost parameter specifies the default external host to send mail to # when no entry is matched in the optional transport(5) table. When no relay # host is given, mail is routed directly to the destination. # d-i postfix/relayhost string ### Description: Use procmail for local delivery? # Please choose whether you want to use procmail to deliver local mail. # . # Note that if you use procmail to deliver mail system-wide, you should set # up an alias that forwards mail for root to a real user. # d-i postfix/procmail boolean ### Description: Internet protocols to use: # By default, whichever Internet protocols are enabled on the system at # installation time will be used. You may override this default with any # of the following: # . # all : use both IPv4 and IPv6 addresses; # ipv6: listen only on IPv6 addresses; # ipv4: listen only on IPv4 addresses. # d-i postfix/protocols select # Possible choices: all, ipv6, ipv4 ### Description: Local address extension character: # Please choose a character used as recipient delimiter that will indicate # a local address extension. # . # To not use address extensions, leave the string blank. # d-i postfix/recipient_delim string + ### Description: Force synchronous updates on mail queue? # If synchronous updates are forced, then mail is processed more slowly. # If not forced, then there is a remote chance of losing some mail if # the system crashes at an inopportune time, and you are not using a # journaled filesystem (such as ext3). # d-i postfix/chattr boolean false ### Description: Local networks: # Please specify the network blocks for which this host should relay mail. # The default is just the local host, which is needed by some mail user agents. # The default includes local host for both IPv4 and IPv6. If just connecting # via one IP version, the unused value(s) may be removed. # . # If this host is a smarthost for a block of machines, you need to specify the # netblocks here, or mail will be rejected rather than relayed. # . # To use the Postfix default (which is based on the connected subnets), leave # this blank. # d-i postfix/mynetworks string 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 ### Description: Mailbox size limit (bytes): # Please specify the limit that Postfix should place on mailbox files to # constrain file system usage by a single file (potentially due to abusive mail # or software errors). A value of zero (0) means no limit. The upstream default # is 51200000. # d-i postfix/mailbox_limit string 0 ### Description: Recipient for root and postmaster mail: # Mail for the 'postmaster', 'root', and other system accounts needs to # be redirected to the user account of the actual system administrator. # . # If this value is left empty, such mail will be saved in /var/mail/nobody, # which is not recommended. # . # Mail is not delivered to external delivery agents as root. # . # If you already have a /etc/aliases file and it does not have an entry # for root, then you should add this entry. Leave this blank to not add one. # d-i postfix/root_address string ### Description: Run newaliases command? # d-i postfix/newaliases boolean false ############################ #### postgresql-15_15.5-0+deb12u1_amd64.deb ############################ ### Description: Remove PostgreSQL directories when package is purged? # Removing the PostgreSQL server package will leave existing database clusters # intact, i.e. their configuration, data, and log directories will not be # removed. On purging the package, the directories can optionally be removed. # d-i postgresql-15/postrm_purge_data boolean true ############################ #### postgresql-common_248_all.deb ############################ ### Description: Enable SSL by default in new PostgreSQL clusters? # PostgreSQL supports SSL-encrypted connections. This is usually a good thing. # However, if the database is solely accessed using TCP connections on # localhost, SSL can be turned off without introducing security issues. # . # UNIX domain socket connections (called "local" in pg_hba.conf) are not # affected by this setting. This setting concerns new PostgreSQL clusters # created during package install, or by using the pg_createcluster command. It # does not reconfigure existing clusters. # . # If unsure, enable SSL. # d-i postgresql-common/ssl boolean true ############################ #### postsrsd_1.10-2+b1_amd64.deb ############################ ### Description: Local domain name to use as origin: # Please enter the domain name to use in rewritten addresses of # forwarded mail. The SPF policy for that domain should allow this # mail server to send mail. # . # Without a configured local domain name, postsrsd will not start. # d-i postsrsd/domain string ############################ #### powerline_2.8.3-4_amd64.deb ############################ ### Description: Enable powerline globally? # powerline can be enabled globally for all users of certain applications on this system. # d-i powerline/enable multiselect # Possible choices: Bash ############################ #### privoxy_3.0.34-1_amd64.deb ############################ ### Description: Adresses on with Privoxy listens: # Please enter a space separated list of address:port combinations on # which Privoxy will listen for client requests. # d-i privoxy/listen-address string 127.0.0.1:8118 [::1]:8118 ############################ #### progress-linux_20221212-3_all.deb ############################ ### Description: setup apt archives: # Please select the apt archives to setup. # d-i progress-linux/archives multiselect # Possible choices: ${CHOICES} ### Description: setup apt archive areas: # Please select the apt archive areas to setup. # d-i progress-linux/archive-areas multiselect # Possible choices: ${CHOICES} ### Description: enter apt mirror: # Please specify the mirror to download packages from. # . # If unsure, leave empty which will use the default mirror # (https://deb.progress-linux.org/packages). # d-i progress-linux/mirror string https://deb.progress-linux.org/packages ############################ #### prometheus-blackbox-exporter_0.23.0-4+b4_amd64.deb ############################ ### Description: Enable additional network privileges for ICMP probing? # /usr/bin/prometheus-blackbox-exporter requires the CAP_NET_RAW capability to # be able to send out crafted packets to targets for ICMP probing. # . # ICMP probing will not work unless this option is enabled, or # prometheus-blackbox-exporter runs as root. # d-i prometheus-blackbox-exporter/want_cap_net_raw boolean false ############################ #### prometheus-homeplug-exporter_0.3.0-4+b5_amd64.deb ############################ ### Description: Enable additional network privileges for PLC communication? # prometheus-homeplug-exporter requires CAP_NET_RAW capabilities to be able to # send out raw Ethernet packets to the HomePlug/PLC devices. # . # prometheus-homeplug-exporter will not work at all unless this option is # enabled, or it runs as root. # d-i prometheus-homeplug-exporter/want_cap_net_raw boolean true ############################ #### prometheus-nextcloud-exporter_0.6.0-1+b3_amd64.deb ############################ ### Description: URL to Nextcloud server: # d-i prometheus-nextcloud-exporter/server string cloud.example.org ### Description: Username for connecting to Nextcloud: # This user needs admin privileges in order to have access to the metrics. # d-i prometheus-nextcloud-exporter/username string admin ### Description: Password for connecting to Nextcloud: # It's highly recommended to generate an application password without # filesystem access. # d-i prometheus-nextcloud-exporter/password password ############################ #### prometheus-smokeping-prober_0.6.1-3+b5_amd64.deb ############################ ### Description: Enable additional network privileges for ICMP probing? # /usr/bin/prometheus-smokeping-prober requires the CAP_NET_RAW capability to # be able to send out crafted packets to targets for ICMP probing. # . # ICMP probing will not work unless this option is enabled, or # prometheus-smokeping-prober runs as root. # d-i prometheus-smokeping-prober/want_cap_net_raw boolean true ############################ #### puppet-agent_7.23.0-1_all.deb ############################ ### Description: Remove Puppet configuration and data when package is purged? # The directories containing Puppet code, environments, configuration, ssl # certificates, logs and other data are about to be removed. # . # If you're purging the puppet-agent package in order to replace it with a more # recent or custom version or if you want to keep the data for further analysis, # the data should be kept. # . # If puppet.conf was modified from its default configuration, some data may # still remain. # d-i puppet-agent/postrm_purge_data boolean true ############################ #### pure-ftpd-common_1.0.50-2.1_all.deb ############################ ### Description: Run pure-ftpd from inetd or as a standalone server: # Pure-ftpd can be run from inetd or as a standalone daemon. Using inetd is # a suitable option for small ftp servers because the inetd super-server # will only launch pure-ftpd to handle incoming connections. Standalone # operation is more efficient for busy ftp sites. # . # Keep in mind that a few options only work in standalone mode, such as # limiting connections per-IP and binding the server to a specific IP # address. # d-i pure-ftpd/standalone-or-inetd select standalone # Possible choices: inetd, standalone ### Description: Do you want pure-ftpwho to be installed setuid root? # The pure-ftpwho program only works with root privileges. Since it's a # fairly trivial program, this poses little security risk. Still, it is only # recommended that you install any program setuid root if you need it. # . # You can always change your mind later by reconfiguring this package with # "dpkg-reconfigure pure-ftpd-common". # d-i pure-ftpd/ftpwho-setuid boolean false ### Description: Enable virtual chroots ? # Chrooted users are usually restricted to their home directory. # With virtual chroots symbolic links are always followed, even if they are # pointing to directories not located in the user's home directory. # This is useful for having shared directories like a symbolic link # to /var/incoming in every home directory. # d-i pure-ftpd/virtualchroot boolean false ############################ #### put-dns_0.0.2-7_all.deb ############################ ### Description: Automatically update domain in put-dns.conf? # If enabled put-dns will, on configuration, try to detect a # valid external domain name on the current system and update # the put-dns.conf configuration file to use it. If disabled # then the configuration will not be automatically updated. # d-i put-dns/update-domain boolean false ############################ #### pwman3_0.12.2-2_all.deb ############################ ### Description: Old database format detected # It seems that you are trying to upgrade Pwman3 from version 0.5.x or older. # The database is not compatible with the new database format. Before # upgrading you need to export your database to a CSV with: # . # pwman> export # . # That will create a CSV file located in $HOME/pwman-export.csv. Once exported, # you will have to rename your old database to keep a backup of it: # . # mv $HOME/pwman/pwman.db $HOME/pwman/pwman-old.db # . # Then you can restart the package upgrade. # Once the upgrade will be finished, you will be able to import the CSV file # previously generated: # . # pwman3 -i $HOME/pwman-export.csv \; # . # Don't forget to remove the CSV file when the import succeeded (the passwords # are stored in clear text in this file). # d-i pwman/old_db_format select abort # Possible choices: abort, continue ############################ #### certbot_2.1.0-4_all.deb ############################ ### Description: You have unexpired certs; do you still want to purge? # The certbot configuration directory /etc/letsencrypt still contains # unexpired certificates that may be live on your system. If you # choose this option, the purge will continue and delete those # certificates, potentially breaking services which depend on them. # . # If you have already installed different certificates in your # services, or you have confirmed you don't have any services depending # on these certificates, you should choose this option. To cancel and # manually delete the /etc/letsencrypt directory, you should refuse # this option. # d-i certbot/remove_live_certs boolean true ############################ #### qcumber_2.3.0-2_all.deb ############################ ### Description: Installation directory of the minikraken database: # QCumber is using kraken which needs a database. To simplyfy the process # of creating the database which requires a lot of computing power there is # the option to download this database (see # https://ccb.jhu.edu/software/kraken/). If you want to run QCumber the # directory of the kraken database needs to be known to the program. Please # input the directory the database is installed or should the database be # installed by the script /usr/share/doc/qcumber/get-minikrakendb. # d-i qcumber/krakendb string /var/lib/kraken/minikraken_20141208 ############################ #### qpsmtpd_0.94-5_all.deb ############################ ### Description: Enable qpsmtpd startup at boot time? # Because most MTAs in Debian listen on one or all network interfaces by # default, when first installed qpsmtpd cannot normally be started. # . # Before enabling qpsmtpd, you must first configure your local MTA not to # bind to the SMTP TCP port on at least one interface. The most common # approach is to leave your MTA listening on the loopback interface # (127.0.0.1), with qpsmtpd listening on the external interface. # Instructions for configuring common MTAs to work with qpsmtpd can be found # after installation in /usr/share/doc/qpsmtpd/README.Debian. # . # Once you have adjusted your MTA configuration, you can enable qpsmtpd by # restarting this configuration, by running 'dpkg-reconfigure qpsmtpd'. # d-i qpsmtpd/startup_enabled boolean false ### Description: Qpsmtpd server type: # Qpsmtpd supports two process models for handling connections. The # 'forkserver' model uses a single process when idle, and forks new processes # to handle connections. This uses less memory but slightly reduces # server throughput. The 'prefork' model keeps a pool of idle processes # available to handle new connections, offering slightly better performance # at the cost of more memory. # d-i qpsmtpd/server_type select forkserver # Possible choices: forkserver, prefork ### Description: Addresses on which to listen for incoming SMTP connections: # Enter one or more of your local IP addresses, separated by spaces, on # which qpsmtpd should listen for incoming SMTP connections. If you leave # this setting empty, qpsmtpd will listen on all interfaces available at # startup time. # . # If you intend to use qpsmtpd to spool deliveries from remote hosts into a # local MTA, you may wish to have qpsmtpd listen on all external interfaces, # while leaving your local MTA listening on the loopback device (127.0.0.1). # . # For each interface you may optionally specify a port to listen on instead # of the default port 25; do this by appending : to the interface, as # in "127.0.0.1:2526". # d-i qpsmtpd/listen_interfaces string unset ### Description: Queueing method for accepted mail: # Select the method for queueing mail once it's been delivered via SMTP. If # you deliver your mail locally, choose the method corresponding to the # installed MTA (the installer will try to pick the correct default.) # . # Select "proxy" if you'd like qpsmtpd to act as an SMTP proxy for another # MTA (local or remote). You will then be prompted to enter a destination # host. # . # Select "maildir" to have qpsmtpd deliver into a local maildir-format spool # instead of queueing it for delivery (e.g. if you're setting up a # spamtrap.) # . # If you select "none," no queueing will be done at all, unless you manually # configure it yourself by editing /etc/qpsmtpd/plugins. # d-i qpsmtpd/queue_plugin select # Possible choices: exim, postfix, qmail, proxy, maildir, none ### Description: Destination host/port for SMTP proxy delivery: # To have qpsmtpd act as an SMTP proxy for another host, supply the hostname # or IP address of that host here. You can optionally add a port number # after a colon, such as "localhost:25". # d-i qpsmtpd/queue_smtp_proxy_destination string localhost ### Description: Destination Maildir for maildir-type delivery: # To have qpsmtpd deliver received mail into a local maildir-format spool, # enter a location for that maildir. A maildir will be created in that # location if it does not exist already. # d-i qpsmtpd/queue_maildir_destination string /var/spool/qpsmtpd/Maildir ### Description: Proceed without a queueing plugin selected? # By selecting "none" as a queueing plugin, you have disabled local queueing # of inbound mail. This will prevent any mail being spooled by qpsmtpd # until you manually configure a queueing method. Any hosts attempting to # deliver mail to you will receive 4xx soft-failure messages until then, at # the potential cost of wasted bandwidth and eventual bouncing of possibly # legitimate mail. # . # To configure queueing manually, edit /etc/qpsmtpd/plugins and select one # of the queueing methods listed there. If you didn't see your installed # MTA in the list and aren't sure what to do, pick "Cancel" here and # select the SMTP proxy method instead, configuring it to proxy into your # MTA on a suitable local address/port. # d-i qpsmtpd/queue_none_confirm boolean ### Description: Destination domain(s) to accept mail for (blank for none): # Enter a list of domain name(s) for which qpsmtpd should accept mail, # separated by spaces. This list should include any hostname or domain name # for which you intend to accept delivery locally, as well as any recipient # domains for which you intend to act as a mail relay. In general, if you # intend to spool received mail into a local MTA, this list should be the # same as used for that MTA (the installer will attempt to extract that # setting as a default.) # . # If you prefer to manage this list manually, leave the entry blank and edit # the file /etc/qpsmtpd/rcpthosts. # d-i qpsmtpd/rcpthosts string unset ############################ #### quota_4.06-1+b2_amd64.deb ############################ ### Description: Send daily reminders to users over quota? # Enable this option if you want the warnquota utility to be run daily to # alert users when they are over quota. # d-i quota/run_warnquota boolean false ### Description: Phone support number of the admin: # Enter the phone number a user can call if he needs assistance with his # "over quota" emails. You do not have to enter anything here if you specify # a signature later. # d-i quota/supportphone string ### Description: Support email of the admin: # Enter the email address a user can write to if he needs assistance with # his "over quota" emails. You do not have to enter anything here if you # specify a signature later. # d-i quota/supportemail string ### Description: From header of warnquota emails: # The email address you specify here is used as the "From:" field of any # mail sent by the warnquota utility. # d-i quota/mailfrom string ### Description: Message of warnquota emails: # The text you specify here is used as message in any mail sent by the # warnquota utility. Use "|" to specify a line break. Leave empty if you # want the default message. # d-i quota/message string ### Description: Signature of warnquota emails: # The text you specify here is used as signature in any mail sent by the # warnquota utility. Use "|" to specify a line break. Leave empty if you # want the default signature. # d-i quota/signature string ### Description: Message of warnquota group emails: # The text you specify here is used as message in any mail sent by the # warnquota utility for groups that are over quota. Use "|" to specify a # line break. Leave empty if you want the default message. # d-i quota/group_message string ### Description: Subject header of warnquota emails: # The text you specify here is used as the "Subject:" field of any # mail sent by the warnquota utility. # d-i quota/subject string ### Description: CC header of warnquota emails: # The text you specify here is used as the "CC:" field of any # mail sent by the warnquota utility. # d-i quota/cc string ### Description: Character set in which the e-mail is sent: # The text you specify here is used as the "charset:" field in the MIME header # of any mail sent by the warnquota utility. # d-i quota/charset string ### Description: Time slot in which admin gets email: # During this time slot before the end of the grace period admin # will be CCed on all generated emails. # Leave empty to get the whole grace period. # d-i quota/cc_before string ### Description: Signature of warnquota group emails: # The text you specify here is used as signature in any mail sent by the # warnquota utility for groups that are over quota. Use "|" to specify a # line break. Leave empty if you want the default message. # d-i quota/group_signature string ############################ #### radioclk_1.0.pristine-3+b1_amd64.deb ############################ ### Description: Serial port the radio receiver is connected to: # Your time signal receiver should be connected to a serial port. # Please enter the device name of the serial port, without the /dev/ # part. # . # Example: for the second serial port, /dev/ttyS1, enter ttyS1. # d-i radioclk/serialport string ttyS0 ############################ #### rally_3.3.0-2_all.deb ############################ ### Description: Set up a database for Rally? # No database has been set up for rally to use. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use; # * the database server hostname (that server must allow TCP # connections from this machine); # * a username and password to access the database. # . # If some of these requirements are missing, do not choose this option and run with # regular SQLite support. # . # You can change this setting later on by running "dpkg-reconfigure -plow # rally". # d-i rally/configure_db boolean false ############################ #### rancid_3.13-2+b1_amd64.deb ############################ ### Description: Really continue? # Please check, whether you made a backup copy of your rancid data. If # it's your first installation of rancid accept here, otherwise # decline, perform the backup and then run "dpkg-reconfigure rancid" # d-i rancid/go_on boolean false ############################ #### redmine_5.0.4-5_all.deb ############################ ### Description: Redmine instances to be configured or upgraded: # Space-separated list of instances identifiers. # . # Each instance has its configuration files in /etc/redmine// # . # To deconfigure an instance, remove its identifier from this list. # Configuration files and data from removed instances will not be deleted until # the package is purged, but they will be no longer managed automatically. # d-i redmine/current-instances string default ### Description: Default redmine language: # d-i redmine/default-language select en # Possible choices: ar, az, bg, bs, ca, cs, da, de, el, en, en-gb, es, es-pa, et, eu, fa, fi, fr, gl, he, hr, hu, id, it, ja, ko, lt, lv, mk, mn, nl, no, pl, pt, pt-br, ro, ru, sk, sl, sq, sr, sr-yu, sv, th, tr, uk, vi, zh, zh-tw ############################ #### refind_0.13.2-1+b1_amd64.deb ############################ ### Description: Automatically install rEFInd to the ESP? # It is necessary to install rEFInd to the EFI System Partition (ESP) for # it to control the boot process. # . # Not installing the new rEFInd binary on the ESP may leave the system in an # unbootable state. Alternatives to automatically installing rEFInd include # running /usr/sbin/refind-install by hand or installing the rEFInd binaries # manually by copying them from subdirectories of /usr/share/refind-{version}. # d-i refind/install_to_esp boolean true ############################ #### request-tracker4_4.4.6+dfsg-1.1+deb12u1_all.deb ############################ ### Description: Name for this Request Tracker (RT) instance: # Every installation of Request Tracker must have a unique name. # The domain name or an abbreviation of the organization name are # usually good candidates. # . # Please note that once you start using a name, you should probably never # change it. Otherwise, mail for existing tickets won't get put in the right # place. # . # This setting corresponds to the $rtname configuration variable. # d-i request-tracker4/rtname string ### Description: Identifier for this RT instance: # In addition to its name, every installation of Request Tracker must also have # a unique identifier. It is used when linking between RT installations. # . # It should be a persistent DNS domain relating to your installation, for # example example.org, or perhaps rt.example.org. It should not be changed # during the lifetime of the RT database, so it is recommended not to use the # default value of the system hostname. Therefore, if you plan to restore # an existing database to this installation, you should use the same value # as previous installations using the same database. # . # This setting corresponds to the $Organization configuration variable. # d-i request-tracker4/organization string ### Description: Default email address for RT correspondence: # Please choose the address that will be listed in From: and Reply-To: headers of # emails tracked by RT, unless overridden by a queue-specific # address. # . # This setting corresponds to the $CorrespondAddress configuration variable. # d-i request-tracker4/correspondaddress string ### Description: Default email address for RT comments: # Please choose the address that will be listed in From: and Reply-To: headers of comment # emails, unless overridden by a queue-specific address. Comments can be # used for adding ticket information that is not visible to the client. # . # This setting corresponds to the $CommentAddress configuration variable. # d-i request-tracker4/commentaddress string ### Description: Base URL for the RT web interface: # Please specify the scheme, server and (optionally) port for constructing # RT web interface URLs. # . # The value should not have a trailing slash (/). # . # This setting corresponds to the $WebBaseURL configuration variable. # d-i request-tracker4/webbaseurl string ### Description: Path to the RT web interface: # If the RT web interface is going to be installed somewhere other than at # the documents root of the web server, you should specify the path to it here. # . # The value requires a leading slash (/) but not a trailing one. # . # This setting corresponds to the $WebPath configuration variable. # d-i request-tracker4/webpath string ### Description: Handle RT_SiteConfig.pm permissions? # The RT web interface needs access to the database password, stored in the # main RT configuration file. Because of this, the file is made readable by # the www-data group in normal setups. This may have security implications. # . # If you reject this option, the file will be readable only by root, and # you will have to set up appropriate access controls yourself. # . # With the SQLite backend, this choice will also affect the # permissions of automatically-generated local database files. # d-i request-tracker4/handle-siteconfig-permissions boolean ### Description: Install cron jobs? # Some features of RT depend on cron jobs, and they can be set up for you # by this package. You should normally accept this option unless you are # working on a snapshot of data (and would like to avoid events which send # out email to users) or this system will be part of a cluster (in which # case only one system should have cron jobs enabled). # d-i request-tracker4/install-cronjobs boolean ### Description: Initial root password for RT system: # The RT system will be populated with an initial superuser, named 'root', # and the password you provide here will be used as the initial password # of this superuser. It should be five characters or more. # d-i request-tracker4/initial-root-password password ############################ #### rt4-db-mysql_4.4.6+dfsg-1.1+deb12u1_all.deb ############################ ### Description: for internal use only # The package stores information about its availability here for the # interval between the config script is run and the package is unpacked. # d-i rt4-db-mysql/available boolean ############################ #### rt4-db-postgresql_4.4.6+dfsg-1.1+deb12u1_all.deb ############################ ### Description: for internal use only # The package stores information about its availability here for the # interval between the config script is run and the package is unpacked. # d-i rt4-db-postgresql/available boolean ############################ #### rt4-db-sqlite_4.4.6+dfsg-1.1+deb12u1_all.deb ############################ ### Description: for internal use only # The package stores information about its availability here for the # interval between the config script is run and the package is unpacked. # d-i rt4-db-sqlite/available boolean ############################ #### request-tracker5_5.0.3+dfsg-3~deb12u2_all.deb ############################ ### Description: Name for this Request Tracker (RT) instance: # Every installation of Request Tracker must have a unique name. # The domain name or an abbreviation of the organization name are # usually good candidates. # . # Please note that once you start using a name, you should probably never # change it. Otherwise, mail for existing tickets won't get put in the right # place. # . # This setting corresponds to the $rtname configuration variable. # d-i request-tracker5/rtname string ### Description: Identifier for this RT instance: # In addition to its name, every installation of Request Tracker must also have # a unique identifier. It is used when linking between RT installations. # . # It should be a persistent DNS domain relating to your installation, for # example example.org, or perhaps rt.example.org. It should not be changed # during the lifetime of the RT database, so it is recommended not to use the # default value of the system hostname. Therefore, if you plan to restore # an existing database to this installation, you should use the same value # as previous installations using the same database. # . # This setting corresponds to the $Organization configuration variable. # d-i request-tracker5/organization string ### Description: Default email address for RT correspondence: # Please choose the address that will be listed in From: and Reply-To: headers of # emails tracked by RT, unless overridden by a queue-specific # address. # . # This setting corresponds to the $CorrespondAddress configuration variable. # d-i request-tracker5/correspondaddress string ### Description: Default email address for RT comments: # Please choose the address that will be listed in From: and Reply-To: headers of comment # emails, unless overridden by a queue-specific address. Comments can be # used for adding ticket information that is not visible to the client. # . # This setting corresponds to the $CommentAddress configuration variable. # d-i request-tracker5/commentaddress string ### Description: Base URL for the RT web interface: # Please specify the scheme, server and (optionally) port for constructing # RT web interface URLs. # . # The value should not have a trailing slash (/). # . # This setting corresponds to the $WebBaseURL configuration variable. # d-i request-tracker5/webbaseurl string ### Description: Path to the RT web interface: # If the RT web interface is going to be installed somewhere other than at # the documents root of the web server, you should specify the path to it here. # . # The value requires a leading slash (/) but not a trailing one. # . # This setting corresponds to the $WebPath configuration variable. # d-i request-tracker5/webpath string ### Description: Handle RT_SiteConfig.pm permissions? # The RT web interface needs access to the database password, stored in the # main RT configuration file. Because of this, the file is made readable by # the www-data group in normal setups. This may have security implications. # . # If you reject this option, the file will be readable only by root, and # you will have to set up appropriate access controls yourself. # . # With the SQLite backend, this choice will also affect the # permissions of automatically-generated local database files. # d-i request-tracker5/handle-siteconfig-permissions boolean ### Description: Install cron jobs? # Some features of RT depend on cron jobs, and they can be set up for you # by this package. You should normally accept this option unless you are # working on a snapshot of data (and would like to avoid events which send # out email to users) or this system will be part of a cluster (in which # case only one system should have cron jobs enabled). # d-i request-tracker5/install-cronjobs boolean ### Description: Initial root password for RT system: # The RT system will be populated with an initial superuser, named 'root', # and the password you provide here will be used as the initial password # of this superuser. It should be five characters or more. # d-i request-tracker5/initial-root-password password ############################ #### rt5-db-mysql_5.0.3+dfsg-3~deb12u2_all.deb ############################ ### Description: for internal use only # The package stores information about its availability here for the # interval between the config script is run and the package is unpacked. # d-i rt5-db-mysql/available boolean ############################ #### rt5-db-postgresql_5.0.3+dfsg-3~deb12u2_all.deb ############################ ### Description: for internal use only # The package stores information about its availability here for the # interval between the config script is run and the package is unpacked. # d-i rt5-db-postgresql/available boolean ############################ #### rt5-db-sqlite_5.0.3+dfsg-3~deb12u2_all.deb ############################ ### Description: for internal use only # The package stores information about its availability here for the # interval between the config script is run and the package is unpacked. # d-i rt5-db-sqlite/available boolean ############################ #### resolvconf_1.91+nmu1_all.deb ############################ ### Description: Prepare /etc/resolv.conf for dynamic updates? # The resolvconf package contains the infrastructure required for # dynamic updating of the resolver configuration file. Part of the # necessary infrastructure is a symbolic link from /etc/resolv.conf to # /run/resolvconf/resolv.conf. If you choose this option then this # link will be created; the existing /etc/resolv.conf file will be # preserved as /etc/resolvconf/resolv.conf.d/original, and will be # restored if this package is removed. # . # Declining this option will prevent future installations from # recreating the symbolic link and therefore the resolver configuration # file will not be dynamically updated. Dynamic updating can then be # activated following instructions in the README file. # . # The presence of resolvconf can affect the behavior of other programs, # so it should not be left installed if unconfigured. # d-i resolvconf/linkify-resolvconf boolean true ### Description: Append original file to dynamic file? # If the original static resolver configuration file (/etc/resolv.conf) # contains name server addresses, those addresses should be listed on # "dns-nameservers" lines in /etc/network/interfaces. For more # information, please consult the resolvconf(8) man page and the # README file. # . # Until /etc/network/interfaces has been edited and the affected # interfaces brought down and up again, the name server addresses will # not be included in the dynamically generated resolver configuration # file. # . # If you choose this option, a temporary workaround will be put in # place: a symbolic link will be created (if it does not already exist) # from /etc/resolvconf/resolv.conf.d/tail to # /etc/resolvconf/resolv.conf.d/original. This will cause the whole of # that original resolver configuration file to be appended to the # dynamically generated file. # . # After the required "dns-nameservers" lines have been added to # /etc/network/interfaces, the /etc/resolvconf/resolv.conf.d/tail link # should be replaced by one to /dev/null. # d-i resolvconf/link-tail-to-original boolean false ############################ #### rkhunter_1.4.6-11_all.deb ############################ ### Description: Activate daily run of rkhunter? # If you choose this option, rkhunter will be run automatically # by a daily cron job. # d-i rkhunter/cron_daily_run boolean ### Description: Activate weekly update of rkhunter's databases? # If you choose this option, rkhunter databases will be # updated automatically by a weekly cron job. # d-i rkhunter/cron_db_update boolean ### Description: Automatically update rkhunter's file properties database? # The file properties database can be updated automatically # by the package management system. # . # This feature is not enabled by default as # database updates may be slow on low-end machines. # Even if it is enabled, the database won't be updated if the # 'hashes' test is disabled in rkhunter configuration. # d-i rkhunter/apt_autogen boolean false ############################ #### rlinetd_0.9.3-1_amd64.deb ############################ ### Description: Convert inetd's configuration file to rlinetd's? # Currently, there are no services defined in your rlinetd's configuration # files. You can import services from /etc/inetd.conf by using inetd2rlinetd # program. # d-i rlinetd/convert_from_inetd boolean true ############################ #### roundcube-core_1.6.5+dfsg-1~deb12u1_all.deb ############################ ### Description: Web server(s) to configure automatically: # RoundCube supports any web server supported by PHP, however only # Apache 2 and lighttpd can be configured automatically. # . # Please select the web server(s) that should be configured # automatically for RoundCube. # d-i roundcube/reconfigure-webserver multiselect apache2, lighttpd # Possible choices: apache2, lighttpd ### Description: Should the webserver(s) be restarted now? # In order to activate the new configuration, the reconfigured web # server(s) have to be restarted. # d-i roundcube/restart-webserver boolean true ### Description: IMAP server(s) used with RoundCube: # Please select the IMAP server(s) that should be used with RoundCube. # . # If this is left blank, a text box will be displayed at # login. Entering a space-separated list of hosts will display a # pull-down menu. Entering a single host will enforce using this # host. # . # To use SSL connections, please enter host names as 'ssl://hostname:993'. # d-i roundcube/hosts string localhost:143 ### Description: Default language: # Please choose the default language for RoundCube. # . # This choice can be overridden by individual users in their preferences. # . # However, the default language will be used for the login screen and # the first connection of users. # d-i roundcube/language select # Possible choices: ${languages} ############################ #### rpki-trust-anchors_20210817-2_all.deb ############################ ### Description: Do you accept the ARIN Relying Party Agreement (RPA)? # ARIN forbids third parties from distributing the Trust Anchor Locator (TAL) # for their RPKI repository, hence this package can download it only if # you will agree to ARIN's conditions. # . # If you want that this package automatically download and installs the ARIN # TAL, then you need to accept the ARIN Relying Party Agreement (RPA): # https://www.arin.net/resources/manage/rpki/rpa.pdf . # d-i rpki-trust-anchors/get_arin_tal boolean ############################ #### irussian_0.99g5-29_all.deb ############################ ############################ #### s-nail_14.9.24-2_amd64.deb ############################ ### Description: Should the dotlock helper be installed ‘setgid mail’? # S-nail protects mbox files via fcntl(2) file-region locks during # file operations in order to avoid inconsistencies due to concurrent # modifications. By default system mbox files are also locked using # traditional dotlock files. # . # On Debian system users normally lack the permissions to create files in # the directory containing the system mailboxes (/var/mail/). In this case # a dedicated privileged (setgid mail) dotlock helper is needed, however # this may be a security concern. # d-i s-nail/setgid-dotlock boolean true ############################ #### sa-exim_4.2.1-20+b1_amd64.deb ############################ ### Description: Remove saved mails in sa-exim's spool directory? # There are some saved mails in subdirectories of /var/spool/sa-exim. # Depending on the configuration, sa-exim may save mails matching specific # criteria (such as "an error occurred", "rejected as spam", or "passed # through although recognized as spam") in these directories. # . # Please choose whether you want to keep these mails for further analysis # or delete them now. # d-i sa-exim/purge_spool boolean false ############################ #### sahara-api_16.0.0-2_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i sahara/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i sahara/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i sahara/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i sahara/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i sahara/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i sahara/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i sahara/api-endpoint-address string ### Description: This service endpoint protocol: # d-i sahara/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i sahara/api-endpoint-region-name string regionOne ############################ #### sahara-common_16.0.0-2_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i sahara/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i sahara/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i sahara/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i sahara/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i sahara/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i sahara/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i sahara/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i sahara/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i sahara/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i sahara/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i sahara/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i sahara/ksat-admin-password password ### Description: Auth server service username: # d-i sahara/ksat-service-username string ### Description: Auth server service project name: # d-i sahara/ksat-service-project-name string service ### Description: Auth server service password: # d-i sahara/ksat-service-password password ############################ #### samba-common_4.17.12+dfsg-0+deb12u1_all.deb ############################ ### Description: Modify smb.conf to use WINS settings from DHCP? # If your computer gets IP address information from a DHCP server on the # network, the DHCP server may also provide information about WINS servers # ("NetBIOS name servers") present on the network. This requires a # change to your smb.conf file so that DHCP-provided WINS settings will # automatically be read from /var/lib/samba/dhcp.conf. # . # The dhcp-client package must be installed to take advantage of this # feature. # d-i samba-common/dhcp boolean false ### Description: Configure smb.conf automatically? # The rest of the configuration of Samba deals with questions that # affect parameters in /etc/samba/smb.conf, which is the file used to # configure the Samba programs (nmbd and smbd). Your current smb.conf # contains an "include" line or an option that spans multiple lines, # which could confuse the automated configuration process and require # you to edit your smb.conf by hand to get it working again. # . # If you do not choose this option, you will have to handle # any configuration changes yourself, and will not be able to take # advantage of periodic configuration enhancements. # d-i samba-common/do_debconf boolean true ### Description: Workgroup/Domain Name: # Please specify the workgroup for this system. This setting controls which # workgroup the system will appear in when used as a server, the default # workgroup to be used when browsing with various frontends, and the domain # name used with the "security=domain" setting. # d-i samba-common/workgroup string WORKGROUP ############################ #### samhain_4.1.4-2+b2_amd64.deb ############################ ############################ #### sane-utils_1.2.1-2_amd64.deb ############################ ### Description: Enable saned as a standalone server? # The saned server, when enabled, makes scanners available over the network. # . # There are two ways of running saned: # - as an inetd service, started by the inetd superserver. In this mode, # saned is started on demand when a client connects to the server; # - as a standalone daemon, started at system boot. In this mode, saned # runs in the background all by itself and listens for client connections. # . # When run in standalone mode, saned advertises itself on the network and # can be detected automatically by the SANE clients with no configuration # on the client side. You still need to configure the server to accept # connections from your clients. This feature is experimental and requires # a running Avahi daemon. # . # Accept this option if you want to make use of this feature. # d-i sane-utils/saned_run boolean false ### Description: Add saned user to the scanner group? # The saned server, when enabled, makes scanners available over the network. # By applying different permissions to the different scanners connected to # your machine, you can control which ones will be made available over the # network. # . # Read /usr/share/doc/sane-utils/README.Debian for details on how to manage # permissions for saned. By default, saned is run under the saned user and # group. # . # Accept this option if you want to make all your scanners available over # the network without restriction. # d-i sane-utils/saned_scanner_group boolean true ############################ #### sash_3.8-5+b21_amd64.deb ############################ ############################ #### sbox-dtc_1.11.7-1.1_amd64.deb ############################ ### Description: Use dtc:dtcgrp for the sbox binary? # Under Debian, apache runs under www-data:www-data. This is ok if running only # apache, but if using sbox-dtc together with the DTC control panel, you need to # have sbox chown to dtc:dtcgrp. In that case, you want create the dtc user and # dtcgrp group, and chown the sbox binary to dtc:dtcgrp, otherwise you don't. # d-i sbox-dtc/conf_use_dtc_dtcgrp boolean true ############################ #### schroot_1.6.13-3+b2_amd64.deb ############################ ############################ #### wamerican_2020.12.07-2_all.deb ############################ ############################ #### wamerican-huge_2020.12.07-2_all.deb ############################ ############################ #### wamerican-insane_2020.12.07-2_all.deb ############################ ############################ #### wamerican-large_2020.12.07-2_all.deb ############################ ############################ #### wamerican-small_2020.12.07-2_all.deb ############################ ############################ #### wbritish_2020.12.07-2_all.deb ############################ ############################ #### wbritish-huge_2020.12.07-2_all.deb ############################ ############################ #### wbritish-insane_2020.12.07-2_all.deb ############################ ############################ #### wbritish-large_2020.12.07-2_all.deb ############################ ############################ #### wbritish-small_2020.12.07-2_all.deb ############################ ############################ #### wcanadian_2020.12.07-2_all.deb ############################ ############################ #### wcanadian-huge_2020.12.07-2_all.deb ############################ ############################ #### wcanadian-insane_2020.12.07-2_all.deb ############################ ############################ #### wcanadian-large_2020.12.07-2_all.deb ############################ ############################ #### wcanadian-small_2020.12.07-2_all.deb ############################ ############################ #### sddm_0.19.0-5_amd64.deb ############################ ### Description: for internal use only # d-i sddm/daemon_name string /usr/bin/sddm ### Description: Default display manager: # A display manager is a program that provides graphical login capabilities for # the X Window System. # . # Only one display manager can manage a given X server, but multiple display # manager packages are installed. Please select which display manager should # run by default. # . # Multiple display managers can run simultaneously if they are configured to # manage different servers; to achieve this, configure the display managers # accordingly, edit each of their init scripts in /etc/init.d, and disable the # check for a default display manager. # d-i shared/default-x-display-manager select # Possible choices: ${choices} ############################ #### senlin-api_14.0.0-1_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i senlin/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i senlin/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i senlin/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i senlin/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i senlin/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i senlin/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i senlin/api-endpoint-address string ### Description: This service endpoint protocol: # d-i senlin/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i senlin/api-endpoint-region-name string regionOne ############################ #### senlin-common_14.0.0-1_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i senlin/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i senlin/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i senlin/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i senlin/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i senlin/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i senlin/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i senlin/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i senlin/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i senlin/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i senlin/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i senlin/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i senlin/ksat-admin-password password ### Description: Auth server service username: # d-i senlin/ksat-service-username string ### Description: Auth server service project name: # d-i senlin/ksat-service-project-name string service ### Description: Auth server service password: # d-i senlin/ksat-service-password password ############################ #### setserial_2.17-53+b1_amd64.deb ############################ ### Description: Automatically configure the serial port parameters? # It is recommended that the serial port parameters should be # configured automatically. It is also possible to configure them # manually by editing the file /etc/serial.conf. # . # PCMCIA serial-type devices should be configured with pcmciautils. See # /usr/share/doc/setserial/README.Debian.gz for details. # d-i setserial/autosave boolean true ### Description: Type of automatic serial port configuration: # Setserial allows saving the current serial configuration in various ways: # . # autosave once : save only once, now; # manual : never save the configuration automatically; # autosave always: save on every system shutdown (risks overwriting the # serial.conf file with errors); # kernel : do not use the serial.conf file and use the kernel settings # at bootup. # d-i setserial/autosave-types select autosave once # Possible choices: autosave once, manual, autosave always, kernel ############################ #### seyon_2.20c-34_amd64.deb ############################ ### Description: Modem device # Please choose the device file corresponding to the port the modem is # connected to. This may be /dev/ttyS1 or any other device file. # . # /dev/modem is usually a symbolic link to the appropriate device file. # This configuration program will not setup this link. If you choose # "/dev/modem", the link should already exist. # d-i seyon/device string /dev/modem ############################ #### shim-signed-common_1.39+15.7-1_all.deb ############################ ### Description: Disable UEFI Secure Boot? # If Secure Boot remains enabled on your system, your system may still boot but # any hardware that requires third-party drivers to work correctly may not be # usable. # d-i shim/disable_secureboot boolean true ### Description: Enable UEFI Secure Boot? # If Secure Boot is enabled on your system, your system may still boot but # any hardware that requires third-party drivers to work correctly may not be # usable. # d-i shim/enable_secureboot boolean false ### Description: UEFI Secure Boot password: # Please enter a password for configuring UEFI Secure Boot. # . # This password will be used after a reboot to confirm authorization for a # change to Secure Boot state. # d-i shim/secureboot_key password ### Description: Re-enter password to verify: # Please enter the same password again to verify that you have typed it # correctly. # d-i shim/secureboot_key_again password ############################ #### sinfo_0.0.48-2.1+b1_amd64.deb ############################ ### Description: Enable the sinfo CGI script? # A CGI script is included, to provide a web interface for sinfo. It is # disabled by default as it might publish information about the computer not # intended to be public. # d-i sinfo/cgi boolean false ############################ #### sitesummary_0.1.56~deb12u2_all.deb ############################ ### Description: for internal use # Activate the munin config replacement feature? # This is an internal (hidden) debconf question. It should not be translated. # d-i sitesummary/replace-munin-config boolean false ### Description: for internal use # Activate the Nagios autoconfig feature? # This is an internal (hidden) debconf question. It should not be translated. # d-i sitesummary/enable-nagios-config boolean false ############################ #### sitesummary-client_0.1.56~deb12u2_all.deb ############################ ### Description: URL: # Insert the URL to the sitesummary collector, where should the # sitesummary information be submitted. Several URLs can be specified # separated by space. # . # The default URL is http://localhost/cgi-bin/sitesummary-collector.cgi # d-i sitesummary-client/collector_url string ### Description: Site: # Insert a string identifying the site where this machine is located. # d-i sitesummary-client/site string ### Description: Sitegroup: # Insert a string identifying the subgroup within the site where this # machine is located. # d-i sitesummary-client/sitegroup string ### Description: Host class: # Insert string identifying the host class, like workstation, server, # laptop, thin client etc. # d-i sitesummary-client/hostclass string ### Description: for internal use # Activate the Nagios NRPE config feature? # This is an internal (hidden) debconf question. It should not be translated. # d-i sitesummary-client/enable-nagios-nrpe-config boolean false ### Description: for internal use # Host name of nagios server allowed to contact NRPE: # This is an internal (hidden) debconf question. It should not be translated. # d-i db_get sitesummary-client/nagios-server string ############################ #### slashem-common_0.0.7E7F3-10+b3_amd64.deb ############################ ### Description: Should Slash'em back up your old, incompatible save files? # You are upgrading from a version of Slashe'em whose save files are not # compatible with the version you are upgrading to. You may either have them # backed up into /tmp, purge them, ignore this problem completely, or abort # this installation and manually handle Slashem's save files. # . # If you choose to back up, the files will be backed up into a # gzip-compressed tar archive in /tmp with a random name starting with # 'slash' and ending in '.tar.gz'. # d-i slashem-common/backup-incompatible select backup # Possible choices: abort, backup, purge, ignore ### Description: Should Slash'em back up your old, incompatible save files? # You are upgrading from a version of Slashe'em whose save files are not # compatible with the version you are upgrading to. You may either have them # backed up into /tmp, purge them, ignore this problem completely, or abort # this installation and manually handle Slashem's save files. # . # If you choose to back up, the files will be backed up into a # gzip-compressed tar archive in /tmp with a random name starting with # 'slash' and ending in '.tar.gz'. # d-i slashem-common/do-backup select backup # Possible choices: abort, backup, purge, ignore ############################ #### slay_3.0.2_all.deb ############################ ### Description: Shall slay punish users? # Normally slay will punish ordinary users trying to run it by slaying # themselves. This is The Right Thing(TM), as users should not mess with # administrative commands like slay, but some administrators find it # inconvenient. Therefore slay can be configured to punish users or just to # display error message. # d-i slay/punish boolean false ### Description: Shall slay use `Butt-head' mode by default? # Slay has two sets of messages: a standard set and an alternative set that # is more informal. The alternative set is named after "Butt-head" from # MTV's "Beavis & Butt-head" cartoon show, a character who uses the sort of # language you'll find in the alternative set. In most cases, the standard # set of messages is more appropriate. # d-i slay/butthead boolean false ############################ #### slbackup_0.0.12-13_all.deb ############################ ### Description: Configure the backup system now? # Select this if you want to configure the backup system now. # . # If you choose to do so, you will get the opportunity to configure one # client and the backup server, and a cron job will be configured to start # the backup session once a day, on a moment of time of your choice. # . # To configure more than one backup client, you could either use the # Webmin-module provided by the webmin-slbackup package, or you can do this # manually in the file /etc/slbackup/slbackup.conf. # . # If you choose to not configure slbackup now, an example configuration file # will be installed, but cron will not be configured to start any backup # sessions. To activate backup, you can reconfigure the system by running # 'dpkg-reconfigure slbackup' (as root) or manually by editing the # /etc/slbackup/slbackup.conf and /etc/cron.d/slbackup files. # d-i slbackup/enable boolean false ### Description: Start time of the backup session: # By default slbackup starts one backup session each day, and here you can # choose when to start this session. Enter the time in a HH:MM-format. # d-i slbackup/backuptime string 01:00 ### Description: Name of your client: # In slbackup each client has a unique name which identifies it. This name # does not necessarily have anything to do with the hostname. Please enter # the unique name of the client you want to configure. # d-i slbackup/client_name string localhost ### Description: Type of client to configure: # This determines what type of client that will be configured now. # . # If you choose local, the server will back up data from this computer. If # you choose extern, the server will back up data from another computer # using a SSH connection (this choice assumes that you install SSH and # provide a passwordless connection between the user running the backup # software on this computer (probably root) and the user running the backup # software on the client). # d-i slbackup/client_type select local # Possible choices: local, extern ### Description: Client hostname or IP address: # You have choosen to configure an external client. Please enter the # client's hostname or IP address. # d-i slbackup/client_address string localhost ### Description: User running the backup software on the client: # The backup software (rdiff-backup) will also run on the client, and the # user that runs it has to have access to all the files that shall be # backed up. Enter the username of the user that shall run the backup # software on the client. # d-i slbackup/client_user string root ### Description: Files and directories to back up: # Enter the location of the files and/or directories that you want to back # up on the client. Use a whitespace as a delimiter. # . # Example: /etc /home /var/backups # d-i slbackup/client_location string /etc /home /var/backups ### Description: Time life of backups (in days): # slbackup is doing a kind of maintenance before each backup session, where # backups that are older than a certain number of days will be deleted. In # this dialog you can specify the number of days that you want to keep the # backups for this client on the backup server. The default is 185 days # (approximately six months). # . # If you want to keep the backups for this client forever, or want to do the # maintenance yourself, 0 days will be treated as infinite. # d-i slbackup/client_keep string 185 ### Description: Type of server to configure / connect to: # This determines what type of server slbackup will configure. # . # If you choose local, the backup will be stored on this computer. If you # choose extern, the backup will be stored on another computer using a SSH # connection (this choice assumes that you install SSH and provide a # passwordless connection between the user running the backup software on # this computer (probably root) and the user running the backup software on # the backup server). # d-i slbackup/server_type select local # Possible choices: local, extern ### Description: Server's hostname or IP address: # You have chosen to configure an external backup server. Please enter the # backup server's hostname or IP address. # d-i slbackup/server_address string localhost ### Description: Backup location on the server: # Enter the location where you want the backups to be stored. slbackup will # not create this directory for you. When you create this directory, make # sure that you have enough disk space to store all the backups you define. # d-i slbackup/server_destdir string /var/lib/slbackup ### Description: User running the backup software on the server: # The backup software (rdiff-backup) will also run on the server, and the # user that runs it has to have access to the location where the files are # going to be stored. Enter the username that shall run the backup software # on the backup server. # d-i slbackup/server_user string root ############################ #### slbackup-php_0.4.5-4+deb12u1_all.deb ############################ ### Description: Activate SSL support in slbackup-php? # Please note that SSL is needed to connect to the slbackup-php server. # Activating it is therefore strongly recommended. # . # However, SSL should also be activated in the web server which will not # be done by choosing this option. # d-i slbackup-php/use-ssl boolean false ############################ #### slim_1.3.6-5.3_amd64.deb ############################ ### Description: for internal use only # d-i slim/daemon_name string /usr/bin/slim ### Description: Default display manager: # A display manager is a program that provides graphical login capabilities for # the X Window System. # . # Only one display manager can manage a given X server, but multiple display # manager packages are installed. Please select which display manager should # run by default. # . # Multiple display managers can run simultaneously if they are configured to # manage different servers; to achieve this, configure the display managers # accordingly, edit each of their init scripts in /etc/init.d, and disable the # check for a default display manager. # d-i shared/default-x-display-manager select # Possible choices: ${choices} ############################ #### slrn_1.0.3+dfsg-6+b1_amd64.deb ############################ ### Description: News server for reading and posting news: # Enter the fully qualified domain name of the news server (NNTP server) that # should be used by default for reading and posting news. # d-i shared/news/server string ### Description: Please enter the mail name of your system: # The "mail name" is the hostname portion of the address to be shown on # outgoing news and mail messages. # d-i shared/mailname string ### Description: How should newsgroup descriptions be refreshed? # Slrn needs to periodically connect to the network to download new # descriptions of newsgroups. This can be handled in a variety of ways. # . # A cron job that is run weekly can be used. This works well if you have a # permanent network connection, or if you are using diald or a similar # program that connects to the network on demand. # . # The ip-up script will make slrn refresh the descriptions when you connect # to the network via ppp. The new descriptions will still only be retrieved # once a week if you choose this method, no matter how often you connect to # the network. # . # Or you can choose to handle this manually and run as root the command # /usr/sbin/slrn_getdescs every week or so while you're online. # d-i slrn/getdescs select cron job # Possible choices: cron job, ip-up, manually ### Description: Download newsgroup descriptions now? # This appears to be a new install of slrn; no newsgroup descriptions have # been downloaded so far. If you are online now, you should download the # newsgroup descriptions. (It will take a few minutes, depending on the speed # of your network connection.) # d-i slrn/getdescs_now boolean false ############################ #### slrnpull_1.0.3+dfsg-6+b1_amd64.deb ############################ ### Description: News server for reading and posting news: # Enter the fully qualified domain name of the news server (NNTP server) that # should be used by default for reading and posting news. # d-i shared/news/server string ### Description: When should slrnpull be run? # Slrnpull needs to run periodically to download news. This can be # accomplished in a variety of ways. # . # A cron job that is run daily can be used. This works well if you have a # permanent network connection, or if you are using diald or a similar # program that connects to the network on demand. # . # The ip-up script will make slrnpull download news when you connect to the # network via ppp. # . # Or you can choose to handle this manually and run as root the command # slrnpull -h `cat /etc/news/server` as you like it. # d-i slrnpull/run_from select cron job # Possible choices: cron job, ip-up, manually ############################ #### smb2www_980804-45_all.deb ############################ ### Description: Do you want to enable smb2www? # d-i smb2www/set_link boolean false ### Description: Master browser server: # Please enter the name of the server which will be used by smb2www as a master # browser. # d-i smb2www/master_browser string localhost ### Description: Language for smb2www pages: # Smb2www can generate its HTML pages in several languages. # . # Please choose the language you want to use on generated pages. # d-i smb2www/language select English # Possible choices: English, Czech, Dutch, German, Finnish, French, Polish, Spanish, Swedish, Vietnamese ### Description: for internal use # This is an INTERNAL option. If you see it while configuring the package, # please file a bug report against smb2www. # d-i smb2www/need_reconfigure boolean false ############################ #### smstools_3.1.21-4+b1_amd64.deb ############################ ### Description: Manage smsd configuration automatically? # Reject this option if you want to configure smsd manually. # d-i smstools/configure boolean true ### Description: Global event-handler: # Please specify an external program or script that will execute, # whenever a message is sent or received, or on failures. # This is useful for instance when running an email2sms gateway. # . # Examples of event-handlers are detailed in /usr/share/doc/smstools/examples. # d-i smstools/eventhandler string ### Description: Modem name: # Please specify the short name for the modem device. This is a mandatory # setting. # d-i smstools/devicename string GSM1 ### Description: Modem device: # Please specify the modem device. Usually the modem device is # /dev/ttyS0 (the first serial port), but your setup may differ; # e.g. for a USB device, choose 'Other' and specify the full path of # the appropriate device node. # d-i smstools/devicenode select # Possible choices: /dev/ttyS0, /dev/ttyS1, /dev/ttyS2, /dev/ttyS3, /dev/ttyS4, Other ### Description: Modem device: # Please specify an optional extra device for the modem. # d-i smstools/devicenodeother string ### Description: Modem device speed (bps): # Most modems work well with a speed of 19200bps, but some modems may # require 9600 bps. If your modem does not support any of the baud # rates in the list, select 'Other'. # d-i smstools/devicebaudrate select 19200 # Possible choices: 9600, 19200, 28800, 38400, 115200, Other ### Description: Modem device speed (bps): # d-i smstools/devicebaudrateother string ### Description: Receive SMS with this device? # Please choose whether the device should be used to receive incoming SMS. # d-i smstools/deviceincoming boolean true ### Description: Modem initialization string: # Please specify the modem initialization command. That may be left empty # for most modems. Please consult your modem's manual for more details # about its supported commands. # d-i smstools/deviceinit string ### Description: SIM device PIN code: # If the device's SIM needs a PIN to be unlocked, please enter it here. # d-i smstools/devicepin password ### Description: Configure another modem? # d-i smstools/configureanothermodem boolean false ############################ #### sn_0.3.8-12_amd64.deb ############################ ### Description: sn should run from: # The scripts provided with the package support several ways to run snget # (the program to fetch new news): # . # cron -- The program will be executed daily by cron -- useful e.g # for permanent connections; # ip-up -- The program will called from ip-up, that is, when your # computer makes a connection -- useful for e.g. dialup # connections; # manually -- The program will never be called, you have to call it # manually to get new news (just type snget as root). # d-i sn/runfrom select cron # Possible choices: cron, ip-up, manually ### Description: Should sn only accept connections from localhost? # sn is a small newsserver, intended mainly to be run for single user # systems. On such systems, it's better to have sn only answer connections # from localhost. If you intend to use sn from multiple machines, refuse # here. # d-i sn/onlylocal boolean true ############################ #### snoopy_2.5.1-1_amd64.deb ############################ ### Description: Install snoopy library to /etc/ld.so.preload? # snoopy is a library that can only reliably do its work if it is # mandatorily preloaded via /etc/ld.so.preload. Since this can potentially # do harm to the system, your consent is needed. # d-i snoopy/install-ld-preload boolean false ############################ #### icatalan_0.20111230b-14_all.deb ############################ ############################ #### wcatalan_0.20111230b-14_all.deb ############################ ############################ #### solaar_1.1.8+dfsg-2_all.deb ############################ ### Description: Use plugdev group? # Please specify how non-root users should be given access to the Logitech # receiver devices. # . # If systemd or consolekit are in use, they can apply ACLs to make them # accessible via Solaar for the user logged in on the current seat. Right # now, ${SEAT_DAEMON_STATUS} daemon is running. # . # If neither of these daemons is in use, or if the receiver should also be # accessible for remotely logged in users, it is possible to grant access # for members of the "plugdev" system group. # . # If you do use the "plugdev" group, don't forget to make sure all the # appropriate users are members of that group. You can add new members to # the group by running, as root: # adduser plugdev # For the group membership to take effect, the affected users need to log # out and back in again. # d-i solaar/use_plugdev_group boolean false ############################ #### solid-pop3d_0.15-31_amd64.deb ############################ ### Description: How do you want to run solid-pop3d? # The solid-pop3d POP server can run as a standalone daemon or from inetd. # Running from inetd is the recommended approach. # d-i solid-pop3d/run_mode select inetd # Possible choices: inetd, daemon ############################ #### spamprobe_1.4d-16+deb12u1_amd64.deb ############################ ############################ #### squidguard_1.6.0-4_amd64.deb ############################ ### Description: Rebuild Squidguard blacklist database during postinst? # Rebuilding the blacklist databases is time consuming and under some # circumstances could cause problems. With the breakout of individual # blacklist section packages the time it takes for each package to rebuild # will be extensive. Also it may not be desireable to rebuild these # databases on production servers. You can manually perform a rebuild by # running /usr/sbin/update-squidguard. # d-i squidguard/dbreload boolean true ############################ #### ssl-cert_1.1.2_all.deb ############################ ### Description: Host name: # Please enter the host name to use in the SSL certificate. # . # It will become the 'commonName' field of the generated SSL certificate. # d-i make-ssl-cert/hostname string localhost ### Description: Alternative name(s): # Please enter any additional names to use in the SSL certificate. # . # It will become the 'subjectAltName' field of the generated SSL certificate. # . # Multiple alternative names should be delimited with comma and no spaces. # For a web server with multiple DNS names this could look like: # . # DNS:www.example.com,DNS:images.example.com # . # A more complex example including a hostname, a WebID, an email address, and # an IPv4 address: # . # DNS:example.com,URI:http://example.com/joe#me,email:me@example.com,IP:192.168.7.3 # d-i make-ssl-cert/altname string ############################ #### sslh_1.20-1+b2_amd64.deb ############################ ### Description: Run sslh: # sslh can be run either as a service from inetd, or as a standalone # server. Each choice has its own benefits. With only a few connection # per day, it is probably better to run sslh from inetd in # order to save resources. # . # On the other hand, with many connections, # sslh should run as a standalone server to avoid spawning a new # process for each incoming connection. # d-i sslh/inetd_or_standalone select standalone # Possible choices: from inetd, standalone ############################ #### ssmtp_2.64-11_amd64.deb ############################ ### Description: Automatically overwrite config files? # The mail configuration file /etc/ssmtp/ssmtp.conf can be automatically # updated on each upgrade with the information supplied to the debconf # database. If you do not want this to happen (ie/ you want to maintain # control of this file yourself) then set this option to have the program # never touch this file. # d-i ssmtp/overwriteconfig boolean true ### Description: Username who gets mail for userids < 1000: # Mail sent to a local user whose UID is less than 1000 will instead be # sent here. This is useful for daemons which mail reports to root and # other system UIDs. # Make this empty to disable rewriting. # d-i ssmtp/root string postmaster ### Description: Name of your mailhub: # This sets the host to which mail is delivered. The actual machine # name is required; no MX records are consulted. Commonly, mailhosts # are named "mail.domain.com". # d-i ssmtp/mailhub string mail ### Description: Remote SMTP port number: # If your remote SMTP server listens on a port other than 25 (Standard/RFC) # then set it here. # d-i ssmtp/port string 25 ### Description: Domain to masquerade as: # ssmtp will use "username@REWRITEDOMAIN" as the default From: address # for outgoing mail which contains only a local username. # d-i ssmtp/rewritedomain string ### Description: Name to store in /etc/mailname: # This is the portion of the address after the '@' sign to be shown on # outgoing news and mail messages. # d-i ssmtp/mailname string ### Description: Fully qualified hostname: # This should specify the real hostname of this machine, and will be # sent to the mailhub when delivering mail. # d-i ssmtp/hostname string ### Description: Allow override of From: line in email header? # A "positive" response will permit local users to enter any From: line # in their messages without it being mangled, and cause ssmtp to rewrite # the envelope header with that address. A "negative" response will # disallow this, and use only the default address or addresses set in # /etc/ssmtp/revaliases. # d-i ssmtp/fromoverride boolean false ############################ #### strongswan-starter_5.9.8-5+deb12u1_amd64.deb ############################ ### Description: Restart strongSwan now? # Restarting strongSwan is recommended, since if there is a security fix, it # will not be applied until the daemon restarts. Most people expect the daemon # to restart, so this is generally a good idea. However, this might take down # existing connections and then bring them back up, so if you are using such # a strongSwan tunnel to connect for this update, restarting is not recommended. # d-i strongswan/restart boolean true ### Description: Use an X.509 certificate for this host? # An X.509 certificate for this host can be automatically created or imported. # It can be used to authenticate IPsec connections to other hosts # and is the preferred way of building up secure IPsec connections. The other # possibility would be to use shared secrets (passwords that are the same on # both sides of the tunnel) for authenticating a connection, but for a larger # number of connections, key based authentication is easier to administer and # more secure. # . # Alternatively you can reject this option and later use the command # "dpkg-reconfigure strongswan" to come back. # d-i strongswan/install_x509_certificate boolean false ### Description: Methods for using a X.509 certificate to authenticate this host: # It is possible to create a new X.509 certificate with user-defined settings # or to import an existing public and private key stored in PEM file(s) for # authenticating IPsec connections. # . # If you choose to create a new X.509 certificate you will first be asked # a number of questions which must be answered before the creation can start. # Please keep in mind that if you want the public key to get signed by # an existing Certificate Authority you should not select to create a # self-signed certificate and all the answers given must match exactly the # requirements of the CA, otherwise the certificate request may be rejected. # . # If you want to import an existing public and private key you will be # prompted for their filenames (which may be identical if both parts are stored # together in one file). Optionally you may also specify a filename where the # public key(s) of the Certificate Authority are kept, but this file cannot # be the same as the former ones. Please also be aware that the format for the # X.509 certificates has to be PEM and that the private key must not be encrypted # or the import procedure will fail. # d-i strongswan/how_to_get_x509_certificate select create # Possible choices: create, import ### Description: File name of your PEM format X.509 certificate: # Please enter the location of the file containing your X.509 certificate in # PEM format. # d-i strongswan/existing_x509_certificate_filename string ### Description: File name of your PEM format X.509 private key: # Please enter the location of the file containing the private RSA key # matching your X.509 certificate in PEM format. This can be the same file # that contains the X.509 certificate. # d-i strongswan/existing_x509_key_filename string ### Description: File name of your PEM format X.509 RootCA: # Optionally you can now enter the location of the file containing the X.509 # Certificate Authority root used to sign your certificate in PEM format. If you # do not have one or do not want to use it please leave the field empty. Please # note that it's not possible to store the RootCA in the same file as your X.509 # certificate or private key. # d-i strongswan/existing_x509_rootca_filename string ### Description: Please enter which length the created RSA key should have: # Please enter the length of the created RSA key. It should not be less than # 1024 bits because this should be considered unsecure and you will probably # not need anything more than 4096 bits because it only slows the # authentication process down and is not needed at the moment. # d-i strongswan/rsa_key_length string 2048 ### Description: Create a self-signed X.509 certificate? # Only self-signed X.509 certificates can be created # automatically, because otherwise a Certificate Authority is needed to sign # the certificate request. If you choose to create a self-signed certificate, # you can use it immediately to connect to other IPsec hosts that support # X.509 certificate for authentication of IPsec connections. However, using # strongSwan's PKI features requires all certificates to be signed by a single # Certificate Authority to create a trust path. # . # If you do not choose to create a self-signed certificate, only the RSA # private key and the certificate request will be created, and you will # have to sign the certificate request with your Certificate Authority. # d-i strongswan/x509_self_signed boolean true ### Description: Country code for the X.509 certificate request: # Please enter the two-letter code for the country the server resides in # (such as "AT" for Austria). # . # OpenSSL will refuse to generate a certificate unless this is a valid # ISO-3166 country code; an empty field is allowed elsewhere in the X.509 # certificate, but not here. # d-i strongswan/x509_country_code string AT ### Description: State or province name for the X.509 certificate request: # Please enter the full name of the state or province the server resides in # (such as "Upper Austria"). # d-i strongswan/x509_state_name string ### Description: Locality name for the X.509 certificate request: # Please enter the locality the server resides in (often a city, such # as "Vienna"). # d-i strongswan/x509_locality_name string ### Description: Organization name for the X.509 certificate request: # Please enter the organization the server belongs to (such as "Debian"). # d-i strongswan/x509_organization_name string ### Description: Organizational unit for the X.509 certificate request: # Please enter the organizational unit the server belongs to (such as # "security group"). # d-i strongswan/x509_organizational_unit string ### Description: Common Name for the X.509 certificate request: # Please enter the Common Name for this host (such as # "gateway.example.org"). # d-i strongswan/x509_common_name string ### Description: Email address for the X.509 certificate request: # Please enter the email address of the person or organization # responsible for the X.509 certificate. # d-i strongswan/x509_email_address string ### Description: Enable opportunistic encryption? # This version of strongSwan supports opportunistic encryption (OE), which stores # IPSec authentication information in # DNS records. Until this is widely deployed, activating it will # cause a significant delay for every new outgoing connection. # . # You should only enable opportunistic encryption if you are sure you want it. # It may break the Internet connection (default route) as the daemon starts. # d-i strongswan/enable-oe boolean false ############################ #### iswedish_1.4.5-3_amd64.deb ############################ ############################ #### wswedish_1.4.5-3_all.deb ############################ ############################ #### swish-e_2.4.7-6.1+b2_amd64.deb ############################ ############################ #### sympa_6.2.70~dfsg-2_amd64.deb ############################ ### Description: Default language for Sympa: # d-i sympa/language select en # Possible choices: ${supported_langs} ### Description: Sympa hostname: # This is the name of the machine or the alias you will use to reach sympa. # . # Example: # . # listhost.cru.fr # . # Then, you will send your sympa commands to: # . # sympa@listhost.cru.fr # d-i sympa/hostname string ### Description: Listmaster email address(es): # Listmasters are privileged people who administrate mailing lists (mailing # list superusers). # . # Please give listmasters email addresses separated by commas. # . # Example: # . # postmaster@cru.fr, root@home.cru.fr # d-i sympa/listmaster string ### Description: Should lists home and spool directories be removed? # The lists home directory (/var/lib/sympa) contains the mailing lists # configurations, mailing list archives and S/MIME user certificates # (when sympa is configured for using S/MIME encryption and authentication). # The spool directory (/var/spool/sympa) contains various queue directories. # . # Note that if those directories are empty, they will be automatically # removed. # . # Please choose whether you want to remove lists home and spool directories. # d-i sympa/remove_spool boolean false ### Description: URL to access WWSympa: # d-i wwsympa/wwsympa_url string ### Description: Which Web Server(s) are you running? # d-i wwsympa/webserver_type select Apache 2 # Possible choices: Apache 2, Other ### Description: Do you want the sympa SOAP server to be used? # Sympa SOAP server allows to access a Sympa service from within another # program, written in any programming language and on any computer. The SOAP # server provides a limited set of high level functions including login, # which, lists, subscribe, signoff. # . # The SOAP server uses libsoap-lite-perl package and a webserver like apache. # d-i sympa/use_soap boolean false ### Description: Should the web archives and the bounce directory be removed? # If you used the default configuration, WWSympa web archives are located in # /var/lib/sympa/wwsarchive. The WWSympa bounce directory contains bounces # (non-delivery reports) and is set to /var/spool/sympa/wwsbounce by # default. # . # Please choose whether you want to remove the web archives and the bounce # directory. # d-i wwsympa/remove_spool boolean false ### Description: Should sympa_newaliases-wrapper be setuid root? # Program 'sympa_newaliases-wrapper' is run with root privileges to # allow sympa to update email aliases when creating or deleting lists, # but this can lead to security issues (see CVE-2020-26880). # . # In most email environments (exim, postfix) sympa doesn't need root # privileges (see also the 'aliases_program' parameter in sympa.conf). # . # Please choose whether you want to install this program with the # setuid bit set (u+s). # d-i sympa/sympa_newaliases-wrapper-setuid-root boolean false ############################ #### python-sympy-doc_1.11.1-1_all.deb ############################ ### Description: Activate live.sympy.org service # One can activate the service provided by https://live.sympy.org, # which can improve one's experience by providing the "Sympy Live # Shell" inside documentation pages. # . # However one must know that even if the button "Sympy Live Shell" is # not triggered, when one is browsing enabled documentation pages, HTTP # requests are sent to the website https://live.sympy.org, so there is # a privacy breach. # . # When the parameter python-sympy-doc/live-sympy is true, links to # https://live.sympy.org are active. When this parameter is false, # those links are replaced by links to http://localhost, so there is # no privacy breach. # . # You can safely keep the default 'false' value for this parameter. # d-i python-sympy-doc/live-sympy boolean false ############################ #### sysstat_12.6.1-1_amd64.deb ############################ ### Description: Remove old format statistics data files? # The format of daily data statistics files has changed in version ${s_version} # of sysstat and is not compatible with the previous one. # . # If you choose this option, all existing data files in the /var/log/sysstat/ # directory will be deleted. # . # If you don't choose this option, the sar(1) command will not work properly # until you remove the files manually. # d-i sysstat/remove_files boolean true ### Description: Activate sysstat's cron job? # If this option is enabled the sysstat package will monitor system # activities and store the data in log files within /var/log/sysstat/. # . # This data allows the sar(1) command to display system statistics for the # whole day. # . # If you don't enable this option, the sar(1) command will only show the # current statistics. # d-i sysstat/enable boolean false ############################ #### sysvinit-core_3.06-4_amd64.deb ############################ ### Description: Update getty pathnames and add hurd-console? # Your /etc/inittab seems to use /libexec/getty as getty and/or to miss # hurd-console entry. The default inittab has been changed, however your # /etc/inittab has been modified. Note that sysvinit has not been used # to boot an Hurd system for long, so any errors in that file would not # have shown up earlier. # . # If you allow this change, a backup will be stored in /etc/inittab.dpkg-old. # . # If you don't allow this change, an updated inittab will be written to # /etc/inittab.dpkg-new. Please review the changes and update your # /etc/inittab accordingly. # d-i sysvinit/hurd-fix-inittab boolean ############################ #### t-prot_3.4-4.1_all.deb ############################ ### Description: Do you want to enable t-prot system wide for mutt? # The t-prot package provides a config file /etc/t-prot/Muttrc -- to use the # script from mutt you have to enable it. You can do this either by creating a # symlink in /etc/Muttrc.d/ for systemwide usage (rather, this can be done # automatically for you), or let the users decide to add a "source" line for it # in their ~/.muttrc or ~/.mutt/muttrc. If you acknowledge this question the # systemwide usage will be enabled. # d-i t-prot/muttrc.d boolean true ############################ #### tango-common_9.3.4+dfsg1-2_all.deb ############################ ### Description: TANGO host: # Please specify the name of the host where the TANGO database server is running. # d-i tango-common/tango-host string localhost:10000 ############################ #### tasksel_3.73_all.deb ############################ ### Description: Choose software to install: # At the moment, only the core of the system is installed. To tune the # system to your needs, you can choose to install one or more of the # following predefined collections of software. # d-i tasksel/first multiselect # Possible choices: ${CHOICES} ### Description: Choose software to install: # You can choose to install one or more of the following predefined # collections of software. # d-i tasksel/tasks multiselect # Possible choices: ${CHOICES} ### Description: This can be preseeded to override the default desktop. # d-i tasksel/desktop multiselect # Possible choices: gnome, kde, xfce, lxde, gnome-flashback, cinnamon, mate, lxqt ############################ #### terminatorx_4.2.0-1_amd64.deb ############################ ### Description: Install terminatorX SUID root so it can use realtime scheduling? # TerminatorX now supports installation of its binary SUID root. This # allows it to run in a realtime scheduled priority thereby greatly # improving performance. However, it is generally a good idea to minimize # the number of SUID programs on your machine to avoid security risks. # . # If you are installing this on your personal desktop with only 1 user, it # should be fairly safe to accept here. If in doubt, refuse. # d-i terminatorx/suid_bin boolean false ############################ #### texlive-base_2022.20230122-3_all.deb ############################ ### Description: TeX binaries that should use the system paper size: # This system's TeX binaries currently use different default paper # sizes. Please choose which of them should get the system paper size # (${libpaperPaper}) as their default. # d-i texlive-base/binary_chooser multiselect pdftex, dvips, dvipdfmx, xdvi # Possible choices: pdftex, dvips, dvipdfmx, xdvi ############################ #### tftpd-hpa_5.2+20150808-1.4_amd64.deb ############################ ### Description: Dedicated system account for the tftpd-hpa TFTP daemon: # The TFTP server must use a dedicated account for its operation so that # the system's security is not compromised by running it with superuser # privileges. # . # Please choose that account's username. # d-i tftpd-hpa/username string tftp ### Description: TFTP root directory: # Please specify the directory that will be used as root for the # TFTP server. # d-i tftpd-hpa/directory string /srv/tftp ### Description: TFTP server address and port: # Please specify an address and port to listen to in the form of # [address][:port]. # . # By default, the TFTP server listens to port 69 on all addresses and all # interfaces. If no port is specified, it defaults to 69. # . # Please note that numeric IPv6 addresses must be enclosed in square brackets # to avoid ambiguity with the optional port information. # d-i tftpd-hpa/address string :69 ### Description: TFTP server additional options: # Additional options can be passed to the TFTP server with this mechanism, # please consult the tftpd(8) manpage for more information about available # options. # . # Options other than the recommended '--secure' are rarely needed and only # for special situations. If unsure, leave it at the recommended default value. # d-i tftpd-hpa/options string --secure ############################ #### tgif_4.2.5-1.3+b2_amd64.deb ############################ ### Description: Paper size to be used: # Please select the size of paper to be used by Tgif. This # selection will be appended to the global Tgif initialization file. # d-i tgif/papersize select A4 # Possible choices: A4, Letter ### Description: Units to use for the grid: # Please select the units to be used by Tgif when rendering the grid. This will also # determine the scaling when the snap-to-grid option is enabled. # d-i tgif/gridunits select Metric # Possible choices: Centimeters, Inches ############################ #### tiger_3.2.4~rc1-3.2_amd64.deb ############################ ### Description: Recipient of the daily mails: # The user you enter below will receive all the emails that 'tiger' sends # during the day when running the cron jobs. This does not mean that when # executing the 'tiger' program standalone this user will receive the # reports. Also note that any administrator will be able to access the # reports since they are available in the /var/log/tiger/ directory. # d-i tiger/mail_rcpt string root ############################ #### tin_2.6.2-1_amd64.deb ############################ ### Description: Enter the fully qualified domain name of your news server # What news server (NNTP server) should be used for reading and posting # news? # d-i shared/news/server string ############################ #### tmpreaper_1.6.17_amd64.deb ############################ ############################ #### tpb_0.6.4-11_amd64.deb ############################ ### Description: Start tpb automatically? # tpb can be started automatically after X has been started for a user. # That can be either after startx from console or after login with a display manager. # d-i tpb/autostart boolean true ############################ #### tripwire_2.4.3.7-4+b7_amd64.deb ############################ ### Description: Do you wish to upgrade? # The format of the Tripwire database and configuration files have changed # substantially between previous versions and this release. # . # To ensure your system remains secure, the upgrade process keeps a copy of # the old version of Tripwire and the old configuration file along with any # old databases that may exist. You will find a detailed explanation for # using the old version of Tripwire in # /usr/share/doc/tripwire/README.Debian. # . # However, as no conversion of the old configuration file and database is # attempted, you may prefer not to upgrade. # . # Due to the way Debian handles configuration files, if you choose to # upgrade you must accept the new version of /etc/cron.daily/tripwire for # regular reporting to occur. The cron job associated with the previous # version will continue to run regardless. # d-i tripwire/upgrade boolean true ### Description: Do you wish to create/use your site key passphrase during installation? # Tripwire uses a pair of keys to sign various files, thus ensuring their # unaltered state. By accepting here, you will be prompted for the # passphrase for the first of those keys, the site key, during the # installation. You are also agreeing to create a site key if one # doesn't exist already. Tripwire uses the site key to sign files that may # be common to multiple systems, e.g. the configuration & policy files. See # twfiles(5) for more information. # . # Unfortunately, due to the Debian installation process, there is a period # of time where this passphrase exists in a unencrypted format. Were an # attacker to have access to your machine during this period, he could # possibly retrieve your passphrase and use it at some later point. # . # If you would rather not have this exposure, decline here. You will then # need to create a site key, configuration file & policy file by hand. See # twadmin(8) for more information. # d-i tripwire/use-sitekey boolean true ### Description: Do you wish to create/use your local key passphrase during installation? # Tripwire uses a pair of keys to sign various files, thus ensuring their # unaltered state. By accepting here, you will be prompted for the # passphrase for the second of those keys, the local key, during the # installation. You are also agreeing to create a local key if one # doesn't exist already. Tripwire uses the local key to sign files that are # specific to this system, e.g. the tripwire database. See twfiles(5) for # more information. # . # Unfortunately, due to the Debian installation process, there is a period # of time where this passphrase exists in a unencrypted format. Were an # attacker to have access to your machine during this period, he could # possibly retrieve your passphrase and use it at some later point. # . # If you would rather not have this exposure, decline here. You will then # need to create a local key file by hand. See twadmin(8) for more # information. # d-i tripwire/use-localkey boolean true ### Description: Enter site-key passphrase: # Tripwire uses two different keys for authentication and encryption of # files. The site key is used to protect files that could be used across # several systems. This includes the policy and configuration files. # . # You are being prompted for this passphrase either because no site key # exists at this time or because you have requested the rebuilding of the # policy or configuration files. # . # Remember this passphrase; it is not stored anywhere! # d-i tripwire/site-passphrase password ### Description: Repeat the site-key passphrase: # Please repeat the site pass phrase to be sure you didn't mistype. # d-i tripwire/site-passphrase-again password ### Description: Your site passphrase is incorrect. Retry operation? # The site passphrase you entered is incorrect. If you think you mistyped # it and would like to retry the current operation accept below. If # you can't remember the passphrase, decline below and the tripwire # installation process will terminate gracefully. When you remember the # site passphrase continue the installation process by running # . # dpkg-reconfigure tripwire # . # as root. # . # If you have completely forgotten your site passphrase, generate a new # site key with a new passphrase by running # . # twadmin -m G -S /etc/tripwire/site.key # . # as root. # d-i tripwire/site-passphrase-incorrect boolean false ### Description: Enter local key passphrase: # Tripwire uses two different keys for authentication and encryption of # files. The local key is used to protect files specific to the local # machine, such as the Tripwire database. The local key may also be used # for signing integrity check reports. # . # You are being prompted for this passphrase because no local key file # currently exists. # . # Remember this passphrase; it is not stored anywhere! # d-i tripwire/local-passphrase password ### Description: Repeat the local key passphrase: # Please repeat the local pass phrase to be sure you didn't mistype. # d-i tripwire/local-passphrase-again password ### Description: Your local passphrase is incorrect. Retry operation? # The local passphrase you entered is incorrect. If you think you mistyped # it and would like to retry the current operation accept below. If # you can't remember the passphrase, decline below and the tripwire # installation process will terminate gracefully. When you remember the # local passphrase continue the installation process by running # . # dpkg-reconfigure tripwire # . # as root. # . # If you have completely forgotten your local passphrase, generate a new # local key with a new passphrase by running # . # twadmin -m G -L /etc/tripwire/${hostname}-local.key # . # as root. # d-i tripwire/local-passphrase-incorrect boolean false ### Description: Rebuild Tripwire configuration file? # Tripwire keeps its configuration in a encrypted database that is # generated, by default, from /etc/tripwire/twcfg.txt # . # Any changes to /etc/tripwire/twcfg.txt, either as a result of a change in # this package or due to administrator activity, require the regeneration of # the encrypted database before they will take effect. # . # Selecting this action will result in your being prompted for the site key # passphrase during the post-installation process of this package. # d-i tripwire/rebuild-config boolean true ### Description: Rebuild Tripwire policy file? # Tripwire keeps its policies on what attributes of which files should be # monitored in a encrypted database that is generated, by default, from # /etc/tripwire/twpol.txt # . # Any changes to /etc/tripwire/twpol.txt, either as a result of a change in # this package or due to administrator activity, require the regeneration of # the encrypted database before they will take effect. # . # Selecting this action will result in your being prompted for the site key # passphrase during the post-installation process of this package. # d-i tripwire/rebuild-policy boolean true ############################ #### tryton-server-all-in-one_6.0.29-2+deb12u1_all.deb ############################ ### Description: Postal codes # Please select all countries for which postal codes should be imported. # This allows the address management system to offer automatic completion # features. # . # Note: The availability of codes depends on their existence on geonames.org. # d-i tryton-server-all-in-one/postal-code-countries multiselect # Possible choices: Afghanistan - AF, Albania - AL, Algeria - DZ, American Samoa - AS, Andorra - AD, Angola - AO, Anguilla - AI, Antarctica - AQ, Antigua and Barbuda - AG, Argentina - AR, Armenia - AM, Aruba - AW, Australia - AU, Austria - AT, Azerbaijan - AZ, Bahamas - BS, Bahrain - BH, Bangladesh - BD, Barbados - BB, Belarus - BY, Belgium - BE, Belize - BZ, Benin - BJ, Bermuda - BM, Bhutan - BT, Bolivia Plurinational State of - BO, Bonaire Sint Eustatius and Saba - BQ, Bosnia and Herzegovina - BA, Botswana - BW, Bouvet Island - BV, Brazil - BR, British Indian Ocean Territory - IO, Brunei Darussalam - BN, Bulgaria - BG, Burkina Faso - BF, Burundi - BI, Cabo Verde - CV, Cambodia - KH, Cameroon - CM, Canada - CA, Cayman Islands - KY, Central African Republic - CF, Chad - TD, Chile - CL, China - CN, Christmas Island - CX, Cocos (Keeling) Islands - CC, Colombia - CO, Comoros - KM, Congo The Democratic Republic of the - CD, Congo - CG, Cook Islands - CK, Costa Rica - CR, Croatia - HR, Cuba - CU, Curaçao - CW, Cyprus - CY, Czechia - CZ, Côte dIvoire - CI, Denmark - DK, Djibouti - DJ, Dominica - DM, Dominican Republic - DO, Ecuador - EC, Egypt - EG, El Salvador - SV, Equatorial Guinea - GQ, Eritrea - ER, Estonia - EE, Eswatini - SZ, Ethiopia - ET, Falkland Islands (Malvinas) - FK, Faroe Islands - FO, Fiji - FJ, Finland - FI, France - FR, French Guiana - GF, French Polynesia - PF, French Southern Territories - TF, Gabon - GA, Gambia - GM, Georgia - GE, Germany - DE, Ghana - GH, Gibraltar - GI, Greece - GR, Greenland - GL, Grenada - GD, Guadeloupe - GP, Guam - GU, Guatemala - GT, Guernsey - GG, Guinea - GN, Guinea-Bissau - GW, Guyana - GY, Haiti - HT, Heard Island and McDonald Islands - HM, Holy See (Vatican City State) - VA, Honduras - HN, Hong Kong - HK, Hungary - HU, Iceland - IS, India - IN, Indonesia - ID, Iran Islamic Republic of - IR, Iraq - IQ, Ireland - IE, Isle of Man - IM, Israel - IL, Italy - IT, Jamaica - JM, Japan - JP, Jersey - JE, Jordan - JO, Kazakhstan - KZ, Kenya - KE, Kiribati - KI, Korea Democratic Peoples Republic of - KP, Korea Republic of - KR, Kuwait - KW, Kyrgyzstan - KG, Lao Peoples Democratic Republic - LA, Latvia - LV, Lebanon - LB, Lesotho - LS, Liberia - LR, Libya - LY, Liechtenstein - LI, Lithuania - LT, Luxembourg - LU, Macao - MO, Madagascar - MG, Malawi - MW, Malaysia - MY, Maldives - MV, Mali - ML, Malta - MT, Marshall Islands - MH, Martinique - MQ, Mauritania - MR, Mauritius - MU, Mayotte - YT, Mexico - MX, Micronesia Federated States of - FM, Moldova Republic of - MD, Monaco - MC, Mongolia - MN, Montenegro - ME, Montserrat - MS, Morocco - MA, Mozambique - MZ, Myanmar - MM, Namibia - NA, Nauru - NR, Nepal - NP, Netherlands - NL, New Caledonia - NC, New Zealand - NZ, Nicaragua - NI, Niger - NE, Nigeria - NG, Niue - NU, Norfolk Island - NF, North Macedonia - MK, Northern Mariana Islands - MP, Norway - NO, Oman - OM, Pakistan - PK, Palau - PW, Palestine State of - PS, Panama - PA, Papua New Guinea - PG, Paraguay - PY, Peru - PE, Philippines - PH, Pitcairn - PN, Poland - PL, Portugal - PT, Puerto Rico - PR, Qatar - QA, Romania - RO, Russian Federation - RU, Rwanda - RW, Réunion - RE, Saint Barthélemy - BL, Saint Helena Ascension and Tristan da Cunha - SH, Saint Kitts and Nevis - KN, Saint Lucia - LC, Saint Martin (French part) - MF, Saint Pierre and Miquelon - PM, Saint Vincent and the Grenadines - VC, Samoa - WS, San Marino - SM, Sao Tome and Principe - ST, Saudi Arabia - SA, Senegal - SN, Serbia - RS, Seychelles - SC, Sierra Leone - SL, Singapore - SG, Sint Maarten (Dutch part) - SX, Slovakia - SK, Slovenia - SI, Solomon Islands - SB, Somalia - SO, South Africa - ZA, South Georgia and the South Sandwich Islands - GS, South Sudan - SS, Spain - ES, Sri Lanka - LK, Sudan - SD, Suriname - SR, Svalbard and Jan Mayen - SJ, Sweden - SE, Switzerland - CH, Syrian Arab Republic - SY, Taiwan Province of China - TW, Tajikistan - TJ, Tanzania United Republic of - TZ, Thailand - TH, Timor-Leste - TL, Togo - TG, Tokelau - TK, Tonga - TO, Trinidad and Tobago - TT, Tunisia - TN, Turkey - TR, Turkmenistan - TM, Turks and Caicos Islands - TC, Tuvalu - TV, Uganda - UG, Ukraine - UA, United Arab Emirates - AE, United Kingdom - GB, United States - US, United States Minor Outlying Islands - UM, Uruguay - UY, Uzbekistan - UZ, Vanuatu - VU, Venezuela Bolivarian Republic of - VE, Viet Nam - VN, Virgin Islands British - VG, Virgin Islands U.S. - VI, Wallis and Futuna - WF, Western Sahara - EH, Yemen - YE, Zambia - ZM, Zimbabwe - ZW, Åland Islands - AX ############################ #### tryton-server-nginx_6.0.29-2+deb12u1_all.deb ############################ ### Description: Domain for the Tryton website: # This will be the domain under which the Tryton server will be exposed via # http (and/or https with Letsencrypt certificates when using the # python3-certbot-nginx package). # . # The value should be a FQDN (Full Qualified Domain Name). Typically it is # something like "mycompany.com" or "tryton.mysite.eu". # . # If you leave the value empty the hostname of this machine will be used # as domain. # d-i tryton-server-nginx/website-uri string ### Description: Perform Letsencrypt registration and configuration? # When the python3-certbot-nginx package is installed (default configuration) # the automatic registration with Letsencrypt can be performed. # The domain as configured in the previous question will be registered. # . # Note: For this to work you need # - a fully registered domain name # - working DNS records for this domain name # - accessibility to this server via Internet on port 80/443 # . # In case you want to register several (sub-)domains with this nginx frontend # you should opt out and perform the registration manually. # You can perform this configuration manually at any time later (please refer # to the necessary steps in /usr/share/doc/certbot/README.rst.gz). # . # When registering with Letsencrypt you agree with the Terms of Service at # https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must # agree in order to register with the ACME server. # d-i tryton-server-nginx/run-certbot boolean false ### Description: Letsencrypt E-Mail: # Enter an email address (used for urgent renewal and security notices) # d-i tryton-server-nginx/certbot-email string ############################ #### tryton-server-postgresql_6.0.29-2+deb12u1_all.deb ############################ ### Description: Initial admin password for Tryton: # A superuser account named "admin" will be created for the Tryton database. # Please specify the password that this account should require for the initial # login. # . # If it is left empty a random password will be used. You can reset this # password from the command line with # . # $ sudo -u tryton trytond-admin -c /etc/tryton/trytond.conf --password -d # . # Note: The initialization of the database may take some time; please be patient. # d-i tryton-server-postgresql/db-admin-password string ### Description: Email address for the admin user: # Please specify a valid email address that should receive administrative # messages from the Tryton server. # d-i tryton-server-postgresql/db-admin-email string root@localhost ############################ #### tryton-server-uwsgi_6.0.29-2+deb12u1_all.deb ############################ ### Description: Set up Tryton server workers? # Some Tryton server tasks can be performed asynchronously in the # background by workers in a task queue. # . # If enabled, the workers can automatically perform tasks such as the # processing of sales, invoices, or purchases removing the need to execute # particular workflow steps manually in the clients and wait for them # to finish. # d-i tryton-server-uwsgi/enable-workers boolean false ### Description: Set up a Tryton scheduler? # Tryton server has its own internal "cron" scheduler which can run # periodic database-maintenance tasks (configured using the Tryton clients). # Please specify whether it should be enabled. # . # Note: Only one cron server should be enabled per database. # d-i tryton-server-uwsgi/enable-cron boolean false ############################ #### tt-rss_21~git20210204.b4cbc79+dfsg-1.2_all.deb ############################ ### Description: Web server to reconfigure automatically: # Please choose the web server that should be automatically configured # to run Tiny Tiny RSS. # d-i tt-rss/reconfigure-webserver multiselect # Possible choices: apache2, lighttpd ### Description: Full URL of the tt-rss installation: # Please enter the URL that should be used to access tt-rss # with a web browser. # . # This should include the location of the tt-rss directory - for # instance http://example.org/tt-rss/. # If this is not set correctly, several features, # including PUSH, bookmarklets, and browser integration, will not # work properly. # d-i tt-rss/self_url_path string http://example.org/tt-rss/ ############################ #### tvtime_1.0.11-7_amd64.deb ############################ ### Description: TV standard: # Please choose the TV standard to use. NTSC is used in North America, # much of South America, and Japan; SECAM in France, the former USSR, # and parts of Africa and the Middle East; and PAL elsewhere. # d-i tvtime/norm select # Possible choices: NTSC, PAL, SECAM, PAL-Nc, PAL-M, PAL-N, NTSC-JP, PAL-60 ### Description: Default frequency table: # Please choose the frequency table to use. It specifies which frequencies correspond to the familiar # channel numbers. You should select "Broadcast" if you use an antenna for over-the-air # signals. # d-i tvtime/frequencies-ntsc select # Possible choices: Cable, Broadcast, Cable including channels 100+ ### Description: Default frequency table: # Please choose the frequency table to use. It specifies which # frequencies correspond to the familiar channel numbers. # . # You should select "Broadcast" if you use an antenna for over-the-air # signals. # d-i tvtime/frequencies-jp select # Possible choices: Cable, Broadcast ### Description: Default frequency table: # Please choose the frequency table to use. It specifies which # frequencies correspond to the familiar channel numbers. # . # If you are a user of a cable company that does not use standard # frequencies, you should select "Custom" and run # the tvtime-scanner application before using tvtime. # d-i tvtime/frequencies-pal select # Possible choices: Europe, France, Russia, Australia, New Zealand, China Broadcast, Australia Optus, Custom (must run tvtime-scanner first) ### Description: Default television capture device: # Please choose the video4linux device which corresponds to your capture # card. # d-i tvtime/v4ldevice string /dev/video0 ### Description: Device to use for VBI decoding: # Please choose the device that will be used in NTSC areas for decoding closed captions and XDS # channel information. # d-i tvtime/vbidevice string /dev/vbi0 ### Description: Allow tvtime to run with root privileges? # Please choose whether tvtime should be "setuid root", therefore getting # root privileges when running. # . # This allows tvtime to run at a high priority to ensure smooth video and # should be used for high quality video output even during high CPU load. # d-i tvtime/setuid boolean false ### Description: Process priority for the tvtime binary: # This setting controls the priority of the tvtime process relative to other # processes on the system. # . # Allowed values are integers between -20 and 19. Lower # values indicate higher priority, and a value of 0 would give tvtime the # same priority as a normal process. # d-i tvtime/processpriority string -10 ############################ #### tzdata_2024a-0+deb12u1_all.deb ############################ ### Description: Geographic area: # Please select the geographic area in which you live. Subsequent # configuration questions will narrow this down by presenting a list of # cities, representing the time zones in which they are located. # d-i tzdata/Areas select # Possible choices: Africa, America, Antarctica, Arctic, Asia, Atlantic, Australia, Europe, Indian, Pacific, US, Etc ### Description: Time zone: # Please select the city or region corresponding to your time zone. # d-i tzdata/Zones/Africa select # Possible choices: Abidjan, Accra, Addis_Ababa, Algiers, Asmara, Bamako, Bangui, Banjul, Bissau, Blantyre, Brazzaville, Bujumbura, Cairo, Casablanca, Ceuta, Conakry, Dakar, Dar_es_Salaam, Djibouti, Douala, El_Aaiun, Freetown, Gaborone, Harare, Johannesburg, Juba, Kampala, Khartoum, Kigali, Kinshasa, Lagos, Libreville, Lome, Luanda, Lubumbashi, Lusaka, Malabo, Maputo, Maseru, Mbabane, Mogadishu, Monrovia, Nairobi, Ndjamena, Niamey, Nouakchott, Ouagadougou, Porto-Novo, Sao_Tome, Timbuktu, Tripoli, Tunis, Windhoek ### Description: Time zone: # Please select the city or region corresponding to your time zone. # d-i tzdata/Zones/America select # Possible choices: Adak, Anchorage, Anguilla, Antigua, Araguaina, Argentina/Buenos_Aires, Argentina/Catamarca, Argentina/Cordoba, Argentina/Jujuy, Argentina/La_Rioja, Argentina/Mendoza, Argentina/Rio_Gallegos, Argentina/Salta, Argentina/San_Juan, Argentina/San_Luis, Argentina/Tucuman, Argentina/Ushuaia, Aruba, Asuncion, Atikokan, Atka, Bahia, Bahia_Banderas, Barbados, Belem, Belize, Blanc-Sablon, Boa_Vista, Bogota, Boise, Cambridge_Bay, Campo_Grande, Cancun, Caracas, Cayenne, Cayman, Chicago, Chihuahua, Ciudad_Juarez, Coral_Harbour, Costa_Rica, Creston, Cuiaba, Curacao, Danmarkshavn, Dawson, Dawson_Creek, Denver, Detroit, Dominica, Edmonton, Eirunepe, El_Salvador, Ensenada, Fort_Nelson, Fortaleza, Glace_Bay, Godthab, Goose_Bay, Grand_Turk, Grenada, Guadeloupe, Guatemala, Guayaquil, Guyana, Halifax, Havana, Hermosillo, Indiana/Indianapolis, Indiana/Knox, Indiana/Marengo, Indiana/Petersburg, Indiana/Tell_City, Indiana/Vevay, Indiana/Vincennes, Indiana/Winamac, Inuvik, Iqaluit, Jamaica, Juneau, Kentucky/Louisville, Kentucky/Monticello, Kralendijk, La_Paz, Lima, Los_Angeles, Lower_Princes, Maceio, Managua, Manaus, Marigot, Martinique, Matamoros, Mazatlan, Menominee, Merida, Metlakatla, Mexico_City, Miquelon, Moncton, Monterrey, Montevideo, Montreal, Montserrat, Nassau, New_York, Nipigon, Nome, Noronha, North_Dakota/Beulah, North_Dakota/Center, North_Dakota/New_Salem, Nuuk, Ojinaga, Panama, Pangnirtung, Paramaribo, Phoenix, Port-au-Prince, Port_of_Spain, Porto_Acre, Porto_Velho, Puerto_Rico, Punta_Arenas, Rainy_River, Rankin_Inlet, Recife, Regina, Resolute, Rio_Branco, Santa_Isabel, Santarem, Santiago, Santo_Domingo, Sao_Paulo, Scoresbysund, Shiprock, Sitka, St_Barthelemy, St_Johns, St_Kitts, St_Lucia, St_Thomas, St_Vincent, Swift_Current, Tegucigalpa, Thule, Thunder_Bay, Tijuana, Toronto, Tortola, Vancouver, Virgin, Whitehorse, Winnipeg, Yakutat, Yellowknife ### Description: Time zone: # Please select the city or region corresponding to your time zone. # d-i tzdata/Zones/Antarctica select # Possible choices: Casey, Davis, DumontDUrville, Macquarie, Mawson, McMurdo, Palmer, Rothera, Syowa, Troll, Vostok ### Description: Time zone: # Please select the city or region corresponding to your time zone. # d-i tzdata/Zones/Arctic select # Possible choices: Longyearbyen ### Description: Time zone: # Please select the city or region corresponding to your time zone. # d-i tzdata/Zones/Asia select # Possible choices: Aden, Almaty, Amman, Anadyr, Aqtau, Aqtobe, Ashgabat, Atyrau, Baghdad, Bahrain, Baku, Bangkok, Barnaul, Beirut, Bishkek, Brunei, Chita, Choibalsan, Chongqing, Colombo, Damascus, Dhaka, Dili, Dubai, Dushanbe, Famagusta, Gaza, Harbin, Hebron, Ho_Chi_Minh, Hong_Kong, Hovd, Irkutsk, Istanbul, Jakarta, Jayapura, Jerusalem, Kabul, Kamchatka, Karachi, Kashgar, Kathmandu, Khandyga, Kolkata, Krasnoyarsk, Kuala_Lumpur, Kuching, Kuwait, Macau, Magadan, Makassar, Manila, Muscat, Nicosia, Novokuznetsk, Novosibirsk, Omsk, Oral, Phnom_Penh, Pontianak, Pyongyang, Qatar, Qostanay, Qyzylorda, Riyadh, Sakhalin, Samarkand, Seoul, Shanghai, Singapore, Srednekolymsk, Taipei, Tashkent, Tbilisi, Tehran, Tel_Aviv, Thimphu, Tokyo, Tomsk, Ulaanbaatar, Urumqi, Ust-Nera, Vientiane, Vladivostok, Yakutsk, Yangon, Yekaterinburg, Yerevan ### Description: Time zone: # Please select the city or region corresponding to your time zone. # d-i tzdata/Zones/Atlantic select # Possible choices: Azores, Bermuda, Canary, Cape_Verde, Faroe, Jan_Mayen, Madeira, Reykjavik, South_Georgia, St_Helena, Stanley ### Description: Time zone: # Please select the city or region corresponding to your time zone. # d-i tzdata/Zones/Australia select # Possible choices: Adelaide, Brisbane, Broken_Hill, Canberra, Currie, Darwin, Eucla, Hobart, Lindeman, Lord_Howe, Melbourne, Perth, Sydney, Yancowinna ### Description: Time zone: # Please select the city or region corresponding to your time zone. # d-i tzdata/Zones/Europe select # Possible choices: Amsterdam, Andorra, Astrakhan, Athens, Belfast, Belgrade, Berlin, Bratislava, Brussels, Bucharest, Budapest, Busingen, Chisinau, Copenhagen, Dublin, Gibraltar, Guernsey, Helsinki, Isle_of_Man, Istanbul, Jersey, Kaliningrad, Kirov, Kyiv, Lisbon, Ljubljana, London, Luxembourg, Madrid, Malta, Mariehamn, Minsk, Monaco, Moscow, Nicosia, Oslo, Paris, Podgorica, Prague, Riga, Rome, Samara, San_Marino, Sarajevo, Saratov, Simferopol, Skopje, Sofia, Stockholm, Tallinn, Tirane, Tiraspol, Ulyanovsk, Vaduz, Vatican, Vienna, Vilnius, Volgograd, Warsaw, Zagreb, Zurich ### Description: Time zone: # Please select the city or region corresponding to your time zone. # d-i tzdata/Zones/Indian select # Possible choices: Antananarivo, Chagos, Christmas, Cocos, Comoro, Kerguelen, Mahe, Maldives, Mauritius, Mayotte, Reunion ### Description: Time zone: # Please select the city or region corresponding to your time zone. # d-i tzdata/Zones/Pacific select # Possible choices: Apia, Auckland, Bougainville, Chatham, Chuuk, Easter, Efate, Fakaofo, Fiji, Funafuti, Galapagos, Gambier, Guadalcanal, Guam, Honolulu, Johnston, Kanton, Kiritimati, Kosrae, Kwajalein, Majuro, Marquesas, Midway, Nauru, Niue, Norfolk, Noumea, Pago_Pago, Palau, Pitcairn, Pohnpei, Port_Moresby, Rarotonga, Saipan, Samoa, Tahiti, Tarawa, Tongatapu, Wake, Wallis, Yap ### Description: Time zone: # Please select the city or region corresponding to your time zone. # d-i tzdata/Zones/US select # Possible choices: Alaska, Aleutian, Arizona, Central, Eastern, Hawaii, Indiana-Starke, Michigan, Mountain, Pacific, Samoa ### Description: Time zone: # Please select your time zone. Contrary to modern conventions, these POSIX-compatible zones use positive values to refer to zones west of Greenwich and negative values for those east of Greenwich (e.g., 'Etc/GMT+6' refers to 6 hours west of Greenwich, commonly called 'UTC-6'). # d-i tzdata/Zones/Etc select # Possible choices: GMT, GMT0, GMT+0, GMT+1, GMT+2, GMT+3, GMT+4, GMT+5, GMT+6, GMT+7, GMT+8, GMT+9, GMT+10, GMT+11, GMT+12, GMT-0, GMT-1, GMT-2, GMT-3, GMT-4, GMT-5, GMT-6, GMT-7, GMT-8, GMT-9, GMT-10, GMT-11, GMT-12, GMT-13, GMT-14, Greenwich, UCT, UTC, Universal, Zulu ############################ #### ucf_3.0043+nmu1_all.deb ############################ ### Description: What do you want to do about modified configuration file ${BASENAME}? # A new version (${NEW}) of configuration file ${FILE} is available, but the version installed # currently has been locally modified. # d-i ucf/changeprompt_threeway select keep_current # Possible choices: install the package maintainer's version, keep the local version currently installed, show the differences between the versions, show a side-by-side difference between the versions, show a 3-way difference between available versions, do a 3-way merge between available versions, start a new shell to examine the situation ### Description: What do you want to do about modified configuration file ${BASENAME}? # ${BASENAME}: A new version (${NEW}) of configuration file ${FILE} is available, but the version installed # currently has been locally modified. # d-i ucf/changeprompt select keep_current # Possible choices: install the package maintainer's version, keep the local version currently installed, show the differences between the versions, show a side-by-side difference between the versions, start a new shell to examine the situation ############################ #### uftp_4.10.2-1.1+b2_amd64.deb ############################ ### Description: Destination directories for received files: # When an incoming file specifies an absolute path, it must match one of the # destination directories, otherwise the file will be rejected. Incoming files # that don't specify an absolute path will be received into the first # destination directory in the list. # . # Default is '/tmp'. # d-i uftp/dest_dir string /tmp ### Description: Extra arguments passed to uftpd: # Commonly used arguments: # . # '-t' for writing the received data into the destination directory. # '-k ' can be used to specify key-files for encrypted transfers. # '-I ' can be used to specify the network interface to listen on. # . # See 'man 1 uftpd' for details. # d-i uftp/arguments string -t ### Description: for internal use # d-i uftp/generate_config boolean true ############################ #### ufw_0.36.2-1_all.deb ############################ ### Description: Start ufw automatically? # If you choose this option, the rules you are about to set # will be enabled during system startup so that this host is protected # as early as possible. # . # To protect this host immediately, you must start ufw manually. # d-i ufw/enable boolean false ### Description: Authorized services: # Please choose the services that should be available for incoming connections. # . # Other services may be specified in the next configuration step. # d-i ufw/allow_known_ports multiselect # Possible choices: CUPS, DNS, IMAPS, POP3S, SSH, CIFS (Samba), SMTP, HTTP, HTTPS ### Description: Additional authorized services: # Please enter a space separated list of any additional ports you would like to # open. You may use a service name (as found in /etc/services), a # port number, or a port number with protocol. # . # Example: to allow a web server, port 53 # and tcp port 22, you should enter "www 53 22/tcp". # d-i ufw/allow_custom_ports string ############################ #### uif_1.99.0-4.1_all.deb ############################ ### Description: Firewall configuration method # Please choose whether the firewall should be configured now with a # simple "workstation" setup, given a specialized Debian Edu Router # configuration, or left unconfigured so that you can manually edit # /etc/uif/uif.conf. # d-i uif/conf_method select don't touch # Possible choices: don't touch, workstation, debian-edu-router ### Description: Trusted DNS hostnames: # In workstation mode, you can specify some DNS hostnames to be # globally trusted. All incoming traffic coming from these will be # allowed. Multiple entries must be separated with spaces. # . # Hostnames provided here must be resolvable to both IPv4 and IPv6 # addresses. # . # Example: trusted-host-v4-and-v6.mydomain.com # d-i uif/trusted-hostnames string ### Description: Trusted IPv4 hosts and/or networks: # In workstation mode, you can specify some IPv4 hosts or networks to be # globally trusted. All incoming traffic coming from these will be # allowed. Multiple entries must be separated with spaces. # . # If you want to trust DNS hostnames that only resolve to # an IPv4 address, please enter them here. # . # Example: 10.1.0.0/16 trusted-host-v4-only.mydomain.com 192.168.1.55 # d-i uif/trusted string ### Description: Trusted IPv6 hosts and/or networks: # In workstation mode, you can specify some IPv6 hosts or networks to be # globally trusted. All incoming traffic coming from these will be # allowed. Multiple entries must be separated with spaces. # . # If you want to trust DNS hostnames that only resolve with # an IPv6 address, please enter them here. # . # Example: 2001:1234:ab::1 fe80::1 # d-i uif/trusted-v6 string ### Description: Allow ping? # Normally an Internet host should be reachable with "pings" (ICMP Echo # requests). Rejecting this option will disable this, which might be # somewhat confusing when analyzing network problems. # d-i uif/pings boolean true ### Description: Allow traceroute? # Normally an Internet host should react to traceroute test packets. # Rejecting this option will disable this, which might be somewhat # confusing when analyzing network problems. # d-i uif/traceroute boolean true ### Description: Really set up up a simple workstation firewall? # Warning: This configuration only provides a very simple firewall setup, # specifying certain hosts as trusted and configuring responses to ping # and traceroute. # . # If you need a more complex setup, use /etc/uif/uif.conf as a template and # choose "don't touch" next time. # d-i uif/really-setup-workstation boolean ### Description: Really set up the firewall for Debian Edu Router? # Warning: This configuration provides a base setup for the Debian Edu # Router, which basically blocks all incoming/outgoing traffic. # . # Don't use this setup unless you know what you are doing. # d-i uif/really-setup-debianedurouter boolean ############################ #### unattended-upgrades_2.9.1+nmu3_all.deb ############################ ### Description: Automatically download and install stable updates? # Applying updates on a frequent basis is an important part of keeping # systems secure. By default, updates need to be applied manually using package # management tools. Alternatively, you can choose to have this system # automatically download and install important updates. # d-i unattended-upgrades/enable_auto_updates boolean true ############################ #### unclutter-startup_8-25_all.deb ############################ ### Description: Start unclutter automatically? # unclutter can be started automatically after X has been started for a # user. That can be either after startx from console or after login with a # display manager. # d-i unclutter/autostart boolean true ############################ #### cw_3.6.0-5+b1_amd64.deb ############################ ### Description: Run cw with root privileges? # If it is run with elevated privileges (which is not recommended), cw # can produce sounds using the console buzzer. # . # Please choose whether this should be achieved by giving the # executable the "setuid" attribute. # . # Alternatives include running the program with sudo or eliminating this # issue completely by using output via a sound card instead of the # buzzer. # d-i cw/suid_bit boolean false ############################ #### cwcp_3.6.0-5+b1_amd64.deb ############################ ### Description: Run cwcp with root privileges? # If it is run with elevated privileges (which is not recommended), cwcp # can produce sounds using the console buzzer. # . # Please choose whether this should be achieved by giving the # executable the "setuid" attribute. # . # Alternatives include running the program with sudo or eliminating this # issue completely by using output via a sound card instead of the # buzzer. # d-i cwcp/suid_bit boolean false ############################ #### xcwcp_3.6.0-5+b1_amd64.deb ############################ ### Description: Make xcwcp setuid root? # xcwcp can produce sounds using console buzzer, but this feature # is available only if xcwcp is run by root user. # You can achieve this by setting setuid bit here (not recommended) # or by running xcwcp with sudo (also not recommended). You can also # use soundcard output instead of console buzzer output and # eliminate this problem completely. # d-i xcwcp/suid_bit boolean false ############################ #### imapproxy_1.2.8~svn20171105-2+b2_amd64.deb ############################ ### Description: IMAP server to connect to: # Please enter the hostname or address of the IMAP server IMAP Proxy will # connect to. # d-i imapproxy/imap-server string localhost ############################ #### update-inetd_4.53_all.deb ############################ ### Description: Ignore multiple entries and continue without changes? # There are multiple entries in ${inetdcf} for the '${service}' service. # d-i update-inetd/ask-several-entries boolean true ### Description: Leave existing entry and continue without changes? # An unrecognized entry for ${sservice} was found in ${inetdcf} while # trying to add the following entry: # . # ${newentry} # . # The unrecognized entry is: # . # ${lookslike} # d-i update-inetd/ask-entry-present boolean true ### Description: Remove inetd entries? # There are multiple entries in ${inetdcf} for the '${service}' service. # . # Please confirm that you agree to remove these entries. # d-i update-inetd/ask-remove-entries boolean false ### Description: Disable inetd entries? # There are multiple entries in ${inetdcf} for the '${service}' service. # . # Please confirm that you agree to disable these entries. # d-i update-inetd/ask-disable-entries boolean false ############################ #### uptimed_0.4.6-3+b1_amd64.deb ############################ ### Description: Delay between database updates (seconds): # Uptimed will update its database regularly so that the uptime # doesn't get lost in case of a system crash. You can set how frequently # this will happen (use higher values if you want to avoid disk activity, # for instance on a laptop). # d-i uptimed/interval string 3600 ### Description: Number of records that should be kept: # Uptimed can limit the number of records to be kept to the highest n, # to keep an unlimited number of records set this value to 0 # . # Be aware that uptime data will be lost if the limit has been reached and/or the number records is reduced. # d-i uptimed/maxrecords string 500 ### Description: Send mails if a milestone or record is reached: # Uptimed can be configured to send a mail each time a record is broken or a # "milestone" is reached. You can choose whether you: # . # * never want to receive these mails; # * want to be notified only when a record is broken; # * would like to know about milestones; # * are interested in both. # d-i uptimed/mail/do_mail select Never # Possible choices: Never, Record, Milestone, Both ### Description: Uptimed email recipient: # Since you have chosen to be sent emails, you should specify where to send # these mails. # d-i uptimed/mail/address string root ############################ #### user-setup_1.95_all.deb ############################ ### Description: for internal use only # d-i passwd/root-password-crypted password ### Description: for internal use only # d-i passwd/user-password-crypted password ### Description: for internal use only # d-i passwd/user-uid string ### Description: for internal use only # d-i passwd/user-default-groups string audio cdrom dip floppy video plugdev netdev scanner bluetooth debian-tor lpadmin ### Description: Allow login as root? # If you choose not to allow root to log in, then a user account will be # created and given the power to become root using the 'sudo' command. # d-i passwd/root-login boolean true ### Description: Root password: # You need to set a password for 'root', the system administrative # account. A malicious or unqualified user with root access can have # disastrous results, so you should take care to choose a root password # that is not easy to guess. It should not be a word found in dictionaries, # or a word that could be easily associated with you. # . # A good password will contain a mixture of letters, numbers and punctuation # and should be changed at regular intervals. # . # The root user should not have an empty password. If you leave this # empty, the root account will be disabled and the system's initial user # account will be given the power to become root using the "sudo" # command. # . # Note that you will not be able to see the password as you type it. # d-i passwd/root-password password ### Description: Re-enter password to verify: # Please enter the same root password again to verify that you have typed it # correctly. # d-i passwd/root-password-again password ### Description: Create a normal user account now? # It's a bad idea to use the root account for normal day-to-day activities, # such as the reading of electronic mail, because even a small mistake can # result in disaster. You should create a normal user account to use for # those day-to-day tasks. # . # Note that you may create it later (as well as any additional account) by # typing 'adduser ' as root, where is an username, # like 'imurdock' or 'rms'. # d-i passwd/make-user boolean true ### Description: Full name for the new user: # A user account will be created for you to use instead of the root # account for non-administrative activities. # . # Please enter the real name of this user. This information will be used # for instance as default origin for emails sent by this user as well as # any program which displays or uses the user's real name. Your full # name is a reasonable choice. # d-i passwd/user-fullname string ### Description: Username for your account: # Select a username for the new account. Your first name is a reasonable choice. # The username should start with a lower-case letter, which can be # followed by any combination of numbers and more lower-case letters. # d-i passwd/username string ### Description: Choose a password for the new user: # A good password will contain a mixture of letters, numbers and punctuation # and should be changed at regular intervals. # d-i passwd/user-password password ### Description: Re-enter password to verify: # Please enter the same user password again to verify you have typed it # correctly. # d-i passwd/user-password-again password ############################ #### vdr_2.6.0-1.1_amd64.deb ############################ ### Description: DVB card type: # VDR needs to know your DVB card type to work correctly. # Using your selection, a channels.conf file will be installed to /var/lib/vdr. # You may have to change this file depending on your setup. # d-i vdr/select_dvb_card select Satellite # Possible choices: Satellite, Terrestrial, Cable ### Description: Create /var/lib/video? # By default VDR is configured to use /var/lib/video to store recordings. # You can either create this directory now, or change this behavior later # by modifying the config file /etc/vdr/conf.d/00-vdr.conf. # d-i vdr/create_video_dir boolean false ############################ #### libvirtodbc0_7.2.5.1+dfsg1-0.3_amd64.deb ############################ ### Description: Register the Virtuoso ODBC driver? # An ODBC manager (unixodbc or iODBC) is already installed on this system. # . # The Virtuoso ODBC driver can be automatically added to the list of # available ODBC drivers (and automatically deleted from the list # when this package is removed). # d-i libvirtodbc0/register-odbc-driver boolean false ############################ #### virtuoso-opensource-7_7.2.5.1+dfsg1-0.3_amd64.deb ############################ ### Description: Password for DBA and DAV users: # Following installation, users and passwords in Virtuoso can be managed # using the command line tools (see the full documentation) or via # the Conductor web application which is installed by default at # http://localhost:8890/conductor. # . # Two users ("dba" and "dav") are created by default, with administrative # access to Virtuoso. Secure passwords must be chosen for these users # in order to complete the installation. # . # If you leave this blank, the daemon will be disabled # unless a non-default password already exists. # d-i virtuoso-opensource-7/dba-password password ### Description: Administrative users password confirmation: # d-i virtuoso-opensource-7/dba-password-again password ### Description: Remove all Virtuoso databases? # The /var/lib/virtuoso-opensource-7 directory which contains the Virtuoso # databases is about to be removed. # . # If you're removing the Virtuoso package in order to later install a more # recent version, or if a different Virtuoso package is already using it, # you can choose to keep databases. # d-i virtuoso-opensource-7/check-remove-databases boolean false ### Description: HTTP server port: # Virtuoso provides a web server capable of hosting HTML and VSP pages # (with optional support for other languages). If you are installing this # instance as a public web server directly on the Internet, you probably want # to choose 80 as web server port. # . # Please note that the default web server root directory is # /var/lib/virtuoso-opensource-7/vsp and will be empty unless you also # install the package containing the standard Virtuoso start page. # d-i virtuoso-opensource-7/http-server-port string 8890 ### Description: Database server port: # You may change here the port on which the Virtuoso database server will # listen for connections. # . # Modifying this default value can improve security on servers that # might be targets for unauthorized intrusion. # d-i virtuoso-opensource-7/db-server-port string 1111 ### Description: Register an ODBC system DSN for Virtuoso? # An ODBC manager (unixodbc or iODBC) is already installed on this system, # and the Virtuoso ODBC driver is installed. # . # The default Virtuoso instance can be automatically added to the list of # available System Data Sources (and automatically deleted from the list # when this package is removed). # . # If you choose this option, the DSN will be named "VOS". User and # password details are omitted from the DSN for security reasons. # d-i virtuoso-opensource-7/register-odbc-dsn boolean false ### Description: Default Virtuoso server package: # Please choose the version of virtuoso-server that will be linked to by the # default (unversioned) names, for init scripts and client tools. # d-i virtuoso-opensource/primary-server select # Possible choices: ${choices} ############################ #### vitrage-api_9.0.0-3.1_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i vitrage/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i vitrage/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i vitrage/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i vitrage/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i vitrage/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i vitrage/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i vitrage/api-endpoint-address string ### Description: This service endpoint protocol: # d-i vitrage/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i vitrage/api-endpoint-region-name string regionOne ############################ #### vitrage-common_9.0.0-3.1_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i vitrage/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i vitrage/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i vitrage/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i vitrage/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i vitrage/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i vitrage/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i vitrage/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i vitrage/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i vitrage/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i vitrage/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i vitrage/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i vitrage/ksat-admin-password password ### Description: Auth server service username: # d-i vitrage/ksat-service-username string ### Description: Auth server service project name: # d-i vitrage/ksat-service-project-name string service ### Description: Auth server service password: # d-i vitrage/ksat-service-password password ############################ #### libvpb1_4.2.61-1.4_amd64.deb ############################ ### Description: ITU-T telephone code: # This is the numeric code for the region your phone system will be operating in # (eg. 61 for Australia or 33 for France). It is used to configure the default # regional standards that Voicetronix telephony hardware should comply with. # d-i libvpb1/countrycode string 61 ############################ #### vsftpd_3.0.3-13+b2_amd64.deb ############################ ### Description: Dedicated system account for the vsftpd FTP daemon: # The FTP server must use a dedicated account for its operation so that # the system's security is not compromised by running it with superuser # privileges. # . # Please choose that account's username. # d-i vsftpd/username string ftp ### Description: FTP root directory: # Please specify the directory that will be used as root for the # FTP server. # d-i vsftpd/directory string /srv/ftp ############################ #### w3c-linkchecker_5.0.0-2_all.deb ############################ ### Description: Host name for W3C LinkChecker service: # Please specify the fully qualified domain name that the w3c-linkchecker # service should be remotely accessible on, if any. By default it will only be # available on localhost. # d-i w3c-linkchecker/hostname string localhost ### Description: Allow private IP addresses? # Please specify whether w3c-linkchecker should permit validation of websites # on private networks. By default it will only permit public IP addresses. # d-i w3c-linkchecker/private_ips boolean false ############################ #### watchdog_5.16-1+b2_amd64.deb ############################ ### Description: Start watchdog at boot time? # Please specify whether watchdog should be started as part of the boot # process. This can be changed later by editing /etc/default/watchdog. # d-i watchdog/run boolean true ### Description: Start wd_keepalive after stopping watchdog? # Please specify whether stopping watchdog should start wd_keepalive to keep on # triggering the watchdog device. This can be changed later by editing # /etc/default/watchdog. # d-i watchdog/run_keepalive boolean true ### Description: Restart watchdog on upgrades? # If the kernel is configured with the CONFIG_WATCHDOG_NOWAYOUT option # (which is not the default setting), restarting watchdog will cause a # spurious reboot (the kernel will assume that the watchdog daemon # crashed). # d-i watchdog/restart boolean false ### Description: Watchdog module to preload: # Please choose which watchdog module should be preloaded before # starting watchdog. The 'softdog' module should be suited for all # installations. Enter 'none' if you don't want the script to load # a module. # d-i watchdog/module string none ############################ #### watcher-api_9.0.0-2_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i watcher/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i watcher/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i watcher/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i watcher/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i watcher/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i watcher/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i watcher/api-endpoint-address string ### Description: This service endpoint protocol: # d-i watcher/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i watcher/api-endpoint-region-name string regionOne ############################ #### watcher-common_9.0.0-2_all.deb ############################ ### Description: Set up a database for this package? # No database has been set up for this package. Before continuing, you should # make sure you have the following information: # . # * the type of database that you want to use - generally the MySQL backend # (which is compatible with MariaDB) is a good choice, and other # implementations like PostgreSQL or SQLite are often problematic with # OpenStack (this depends on the service); # * the database server hostname (that server must allow TCP connections from # this machine); # * a username and password to access the database. # . # Note that if you plan on using a remote database server, you must first # configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), # and the remote database server needs to be configured with adequate # credentials. # . # If some of these requirements are missing, do not choose this option. Run # with regular SQLite support instead. # . # You can change this setting later on by running "dpkg-reconfigure -plow". # d-i watcher/configure_db boolean false ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i watcher/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i watcher/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i watcher/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i watcher/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i watcher/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i watcher/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i watcher/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i watcher/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i watcher/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i watcher/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i watcher/ksat-admin-password password ### Description: Auth server service username: # d-i watcher/ksat-service-username string ### Description: Auth server service project name: # d-i watcher/ksat-service-project-name string service ### Description: Auth server service password: # d-i watcher/ksat-service-password password ############################ #### wdm_1.28-26+b1_amd64.deb ############################ ### Description: Desired default display manager. # A display manager is a program that provides graphical login capabilities # for the X Window System. # . # Only one display manager can manage a given X server, but multiple display # manager packages are installed. Please select which display manager # should run by default. # . # (Multiple display managers can run simultaneously if they are configured # to manage different servers; to achieve this, configure the display # managers accordingly, edit each of their init scripts in /etc/init.d, and # disable the check for a default display manager.) # d-i shared/default-x-display-manager select # Possible choices: ${choices} ### Description: for internal use # This template is never shown to the user and does not require translation. # d-i wdm/daemon_name string /usr/bin/wdm ############################ #### webalizer_2.23.08-3.3_amd64.deb ############################ ### Description: Directory to put the output in: # d-i webalizer/directory string /var/www/webalizer ### Description: Generate a default configuration file ? # Note that webalizer always parses the default configuration, so if you plan # on using more than one configuration or using the -c parameter, you probably # want to say No here. # d-i webalizer/create_conf boolean true ### Description: Title of the reports webalizer will generate: # (your system's hostname will be appended to it) # d-i webalizer/doc_title string Usage Statistics for ### Description: Webserver's rotated log filename: # d-i webalizer/logfile string /var/log/apache/access.log.1 ### Description: Enable DNSCache Option? # Speed up name resolving with the DNSCache option enabled. See # /usr/share/doc/webalizer/DNS.README.gz for more information. # d-i webalizer/dnscache boolean false ############################ #### webfs_1.21+ds1-12+b1_amd64.deb ############################ ### Description: IP address webfsd should listen to: # On a system with multiple IP addresses, webfsd can be configured to # listen to only one of them. # . # If you leave this empty, webfsd will listen to all IP addresses. # d-i webfsd/web_ip string ### Description: Timeout for network connections: # d-i webfsd/web_timeout string ### Description: for internal use only # d-i webfsd/pending string no ### Description: Number of parallel network connections: # For small private networks, the default number of parallel network # connections should be fine. This can be increased for larger networks. # d-i webfsd/web_conn string ### Description: Directory cache size: # Directory listings can be cached by webfsd. By default, the size of # the cache is limited to 128 entries. If the web server has # very big directory trees, you might want to raise this value. # d-i webfsd/web_dircache string ### Description: Incoming port number for webfsd: # Please enter the port number for webfsd to listen to. If you leave # this blank, the default port (8000) will be used. # d-i webfsd/web_port string ### Description: Enable virtual hosts? # This option allows webfsd to support name-based virtual hosts, taking # the directories immediately below the document root as host names. # d-i webfsd/web_virtual boolean false ### Description: Document root for webfsd: # Webfsd is a lightweight HTTP server for mostly static content. Its # most obvious use is to provide HTTP access to an anonymous FTP server. # . # Please specify the document root for the webfs daemon. # . # If you leave this field blank, webfsd will not be started at boot time. # d-i webfsd/web_root string /var/www/html ### Description: Host name for webfsd: # By default, webfsd uses the machine name as host name. # . # You can specify an alternate host name to be used as an external # alias name (for instance "ftp.example.org") instead of the machine's # fully qualified domain name. # d-i webfsd/web_host string ### Description: User running the webfsd daemon: # d-i webfsd/web_user string www-data ### Description: Log webfsd events (start, stop, etc.) to syslog? # d-i webfsd/web_syslog boolean false ### Description: Access log file: # Access to webfsd is logged in common log format. # . # If this field is left empty, no logging of incoming connections will # be done. # d-i webfsd/web_accesslog string ### Description: Should logging be buffered? # With buffered logging, entries will be written in chunks, not as soon # as they are accepted as client calls. # d-i webfsd/web_logbuffering boolean true ### Description: Group running the webfsd daemon: # d-i webfsd/web_group string www-data ### Description: Directory index filename: # If webfsd receives a request for a directory, it can optionally look for # an index file to send to the client. Common names are "index.html" and # "default.html". If you leave this field empty, webfsd will never treat # any file as index of a directory. # . # In the absence of an index, webfsd will normally construct a listing for # any requested directory. However, if you consider a generated directory # listing to present a security risk, then the listing can be disabled by # running the server with the "-j" option. This option can be added to the # variable "web_extras" in "/etc/webfsd.conf", either manually or by way # of a following dialog ("Extra options to include"). # d-i webfsd/web_index string ### Description: CGI script catalog: # Please specify the location for CGI scripts to be served by webfsd. This # path should be located immediately below the document root. # . # Please specify the full path name, not a relative path. If this # field is left empty, CGI scripts will be disabled. # d-i webfsd/web_cgipath string ### Description: Extra options to include: # Please specify any webfsd options you want to use with the main # daemon. # . # For instance, webfsd can run chrooted, provide timed expiration of # files, and bind either IPv4 or IPv6 addresses. # . # In particular, this is the right time to insert the option "-j", # preventing all generation of directory listings. # . # See webfsd's manual page for further options and details. # d-i webfsd/web_extras string ############################ #### wfrench_1.2.7-2_all.deb ############################ ############################ #### whatmaps_0.0.13-1_all.deb ############################ ### Description: Automatically restart services after library security updates? # Services need to be restarted to benefit from updates of shared libraries they # depend on. Otherwise they remain vulnerable to security bugs fixed in these # updates. # . # Automatic service restarts are only done if APT fetched the library from a # source providing security updates. This also affects packages installed # via "unattended-upgrades". # d-i whatmaps/enable_service_restarts boolean false ############################ #### wide-dhcpv6-client_20080615-23_amd64.deb ############################ ### Description: Interfaces on which the DHCPv6 client sends requests: # Network interfaces on which the DHCPv6 client sends requests should be # specified here. Multiple interfaces are separated with spaces. An empty # line temporarily disables dhcp6c. # d-i wide-dhcpv6-client/interfaces string eth0 ############################ #### wide-dhcpv6-relay_20080615-23_amd64.deb ############################ ### Description: Interfaces on which the DHCPv6 relay operates: # Network interfaces on which the DHCPv6 relay handles requests should be # specified here. Multiple interfaces are separated with spaces. An empty # line temporarily disables dhcp6relay. # d-i wide-dhcpv6-relay/interfaces string eth0 ############################ #### wide-dhcpv6-server_20080615-23_amd64.deb ############################ ### Description: Interfaces on which the DHCPv6 server listens to requests: # Network interfaces on which the DHCPv6 server listens to requests should be # specified here. Multiple interfaces are separated with spaces. An empty # line temporarily disables dhcp6s. # d-i wide-dhcpv6-server/interfaces string eth0 ############################ #### wims-lti_0.4.4.1-12_all.deb ############################ ### Description: hostname for the service: # When you use Apache2 + WSGI to deploy the service, it can be implemented # as a virtual host. In the example below, the service administration's # webpage should be at http://wims-lti.example.com/admin/ # . # If unsure, you can keep the default value. # d-i wims-lti/virtualHost string wims-lti.example.com ### Description: email for django's service admin: # Choose a valid email string. # d-i wims-lti/adminEmail string admin@example.com ### Description: password for django's service admin: # Choose a strong enough password. # d-i wims-lti/adminPassword password ### Description: how long to wait for a response from WIMS adm/raw module: # Choose an integer value (in seconds). The default value is generally fine. # When a server has many active classes, this time should be increased. # d-i wims-lti/timeout string 5 ############################ #### wireshark-common_4.0.11-1~deb12u1_amd64.deb ############################ ### Description: Should non-superusers be able to capture packets? # Dumpcap can be installed in a way that allows members of the "wireshark" # system group to capture packets. This is recommended over the # alternative of running Wireshark/Tshark directly as root, because # less of the code will run with elevated privileges. # . # For more detailed information please see # /usr/share/doc/wireshark-common/README.Debian.gz once the package # is installed. # . # Enabling this feature may be a security risk, so it is disabled by # default. If in doubt, it is suggested to leave it disabled. # d-i wireshark-common/install-setuid boolean false ############################ #### witalian_1.10_all.deb ############################ ############################ #### wspanish_1.0.30_all.deb ############################ ############################ #### wvdial_1.61-6_amd64.deb ############################ ### Description: Automatically detect and configure the modem? # WvDial can automatically detect the modem and create its configuration # file. This detection may cause problems with some computers. # . # You may reconfigure WvDial by running a program called wvdialconf which # will write these settings into the /etc/wvdial.conf file. # d-i wvdial/wvdialconf boolean true ### Description: ISP's telephone number: # Please enter the telephone number that should be used to connect to the # Internet Service Provider (ISP). # d-i wvdial/phone string ### Description: Account username: # Please enter the username or login for an account issued by the ISP. # d-i wvdial/login string ### Description: Account passphrase: # Please enter the password or passphrase that corresponds with the account # username. # d-i wvdial/passphrase password ### Description: Confirm passphrase: # Please enter the password or passphrase again for verification. # d-i wvdial/passphrase2 password ############################ #### x2gobroker-ssh_0.0.4.3-4_amd64.deb ############################ ### Description: for internal use # d-i x2gobroker-ssh/last-group-x2gobroker-users string ### Description: Create group for X2Go Broker SSH access now? # In X2Go Session Broker, SSH-based broker access is controlled via the # broker users' membership in a dedicated group (default: x2gobroker-users). # . # If this group is not created now, you will be asked to assign this # privilege to an existing group instead. # d-i x2gobroker-ssh/create-group boolean true ### Description: Use an already existing group for X2Go Session Broker SSH access? # If there already exists a group (e.g. in an LDAP database) that you # would like to use for controlling X2Go Session Broker SSH access with, # then you can specify this group name with the next step. # d-i x2gobroker-ssh/use-existing-group boolean true ### Description: Set up X2Go Session Broker SSH access later? # Without an existing group for X2Go Session Broker SSH access, the SSH # broker will not be usable by users. You have to set up things later, # either manually or via this configuration helper. # . # A manual setup is only recommended, if you really know what have # to do for this. # . # Alternatively, the setup questions can be asked once more... # d-i x2gobroker-ssh/manual-setup-required boolean false ### Description: X2Go Session Broker SSH access group: # Please specify the group name for users with full X2Go Session Broker # access via SSH now. # d-i x2gobroker-ssh/group-x2gobroker-users string x2gobroker-users ### Description: Delete the group that was formerly used for X2Go Session Broker SSH access? # The group for X2Go Session Broker SSH access has been modified. # . # Please specify whether the old group should be deleted from your system. # If unsure, keep the formerly used group and manually investigate later. # d-i x2gobroker-ssh/del-last-group-x2gobroker-users boolean false ############################ #### x2goserver_4.1.0.3-7+deb12u1_amd64.deb ############################ ############################ #### x2goserver-desktopsharing_4.1.0.3-7+deb12u1_all.deb ############################ ### Description: Create x2godesktopsharing group? # X2Go Desktop Sharing grants users the privileges to share X2Go/X11 # desktop session with one another via membership of a common POSIX # group. The group being used for this can be configured system-wide and # on a per-user basis (in X2Go Desktop Sharing's user configuration). # . # Please specify whether X2Go Desktop Sharing should set up the group # "x2godesktopsharing" as the system-wide default group used for this # purpose. # . # Alternatively, if you reject this option, you will be asked to assign # the role to some already existing group. # . # With no such group users will not be able to share X2Go/X11 desktop # sessions. # d-i x2goserver-desktopsharing/create-group-for-sharing boolean true ### Description: Use existing group for X2Go Desktop Sharing? # If X2Go Desktop Sharing can use an existing group (possibly from an LDAP # database) then you can specify this group name on the next screen. # d-i x2goserver-desktopsharing/use-existing-group-for-sharing boolean false ### Description: Group to use for X2Go Desktop Sharing: # Please specify the name of the existing POSIX group that you want to # assign X2Go Desktop Sharing privileges to. # . # An empty string will be replaced by the "root" group. # d-i x2goserver-desktopsharing/group-sharing string x2godesktopsharing ### Description: Auto-start X2Go Desktop Sharing applet? # For an X2Go/X11 desktop session to be accessible via X2Go Desktop # Sharing, the X2Go Desktop Sharing applet needs to be running. It # advertises the user's X2Go/X11 session through an access controlled # socket to X2Go client applications. # . # The applet can be configured to start automatically on desktop session # startup, but for security reasons this is not the default. # d-i x2goserver-desktopsharing/auto-start-on-logon boolean false ### Description: Auto-activate X2Go Desktop Sharing? # The X2Go Desktop Sharing applet normally starts in non-sharing mode # (users that request to share the running desktop session get # auto-rejected). The user normally has to choose to activate the sharing # mode in the applet's GUI. # . # If the auto-start option is active, you can additionally choose here # whether desktop sharing should be activated when the X2Go Desktop # Sharing applet is auto-started at session logon. # . # For security and data protection reasons, this is not the default. Use # this auto-activation feature only in appropriate environments, such as # for classroom computers. # d-i x2goserver-desktopsharing/auto-activate-on-logon boolean false ############################ #### x2gothinclient-displaymanager_1.5.0.1-10_all.deb ############################ ### Description: Default display manager: # On X2Go thin clients X2Go Client is sort of used as a display manager. For # this, X2Go Client gets started in TCE mode. The TCE acronym stands for # thin client environment. In TCE mode, X2Go Client manages the default # display of the X Window System. # . # Generally, a display manager is a program that provides graphical login # capabilities for the X Window System. Other display managers for example # are GDM, KDM, etc. Login is--in most cases--granted to the local system. # . # However, X2Go Client in TCE mode does appear like a display manager, but # it will log you onto pre-defined X2Go sessions on remote servers. # . # As you are about to install X2Go Client in TCE mode on this machine and as # you already have other display managers installed on this machine, please # explicitly select which display manager is supposed to be the default for # your system. # d-i shared/default-x-display-manager select # Possible choices: ${choices} ############################ #### xastir_2.1.8-1+b1_amd64.deb ############################ ### Description: Should non-superusers be able to use native AX.25 interfaces? # Xastir can be installed in a way that allows members of the "xastir-ax25" # system group to use a native Linux AX.25 interface from within Xastir. # Where available this configuration uses Linux capabilities in order to # limit the process's privileges to only those required, falling back on # installing the binary setuid where Linux capabilities are not available. # . # This is recommended over the alternative of running Xastir directly as # root, but enabling it may be a security risk, so it is disabled by # default. If in doubt, or if you do not intend to use native AX.25 # interfaces (using a serial TNC or Internet connection instead), it is # suggested to leave it disabled. # . # For more detailed information please see # /usr/share/doc/xastir/README.Debian. # d-i xastir/install-setuid boolean false ############################ #### xawtv_3.107-1.1_amd64.deb ############################ ### Description: Scan for TV stations? # A list of TV stations found by scanning can be included in the # configuration file. # . # This requires a working bttv driver. If bttv isn't configured correctly, TV # stations will not be found. # . # Channel names will be retrieved from teletext information, which # will only work for PAL channels. # d-i xawtv/channel-scan boolean false ### Description: TV standard: # d-i xawtv/tvnorm select # Possible choices: PAL, SECAM, NTSC ### Description: Create a default configuration for xawtv? # A system-wide configuration file for xawtv can be created with reasonable # default values for the local country. # . # That file is not required but will simplify software configuration # for users. # d-i xawtv/build-config boolean false ### Description: Frequency table to use: # A frequency table is a list of TV channel names and numbers with # their broadcast frequencies. # d-i xawtv/freqtab select # Possible choices: us-bcast, us-cable, us-cable-hrc, japan-bcast, japan-cable, europe-west, europe-east, italy, newzealand, australia, ireland, france, china-bcast ############################ #### xdm_1.1.11-3+b2_amd64.deb ############################ ### Description: Default display manager: # A display manager is a program that provides graphical login capabilities for # the X Window System. # . # Only one display manager can manage a given X server, but multiple display # manager packages are installed. Please select which display manager should # run by default. # . # Multiple display managers can run simultaneously if they are configured to # manage different servers; to achieve this, configure the display managers # accordingly, edit each of their init scripts in /etc/init.d, and disable the # check for a default display manager. # d-i shared/default-x-display-manager select # Possible choices: ${choices} ### Description: internal use only # This template is never shown to the user and does not require translation. # d-i xdm/daemon_name string /usr/bin/xdm ### Description: Stop the xdm daemon? # The X display manager (xdm) daemon is typically stopped on package upgrade # and removal, but it appears to be managing at least one running X session. # . # If xdm is stopped now, any X sessions it manages will be terminated. # Otherwise, the new version will take effect the next time the daemon # is restarted. # d-i xdm/stop_running_server_with_children boolean false ############################ #### xfonts-traditional_1.8.0+nmu1_all.deb ############################ ### Description: Generate traditional versions of fonts? # xfonts-traditional can automatically generate traditional versions # (with foundry "Trad" instead of "Misc") of all fonts for which it has # an idea about the glyphs. (Currently this is versions of 6x13, aka # "fixed".) # . # But you may prefer not to do this automatically, and would rather # just have the tool installed. # d-i xfonts-traditional/generate boolean true ### Description: Configure xterm to use traditional fonts? # You can have the xterm default UTF-8 font changed to the traditional # version. # . # If you approve, I will edit /etc/X11/app-default/XTerm for you, and # save your old file as XTerm.backup.not-trad. (Note that this is a # conffile so you may get prompts from dpkg about it in the future.) # . # Alternatively, if you do not want me to change the default, I will # generate the file XTerm.trad, but it will not be used. # . # To revert the change, simply change the key "*VT100.utf8Fonts.font" # back from "-trad-..." to "-misc-...", or rename the old file back # into place. # d-i xfonts-traditional/reconfigure-xterm boolean false ### Description: Configure system to use traditional "fixed"? # I can remap the font alias "fixed" to the traditional version. # . # If you approve, I will edit /etc/X11/fonts/misc/xfonts-base.alias for # you, and save your old file as xfonts-base.alias.backup.not-trad. # (Note that this is a conffile, so you may get prompts from dpkg about # it in the future.) # . # Alternatively, if you do not want me to change the default, I will # generate xfonts-base-alias.trad for you to do what you like with. # . # To revert this change, simply change the alias "fixed" back from # "-trad-..." to "-misc-...", or rename the old file back into place. # d-i xfonts-traditional/remap-fixed boolean false ### Description: Remove xfonts-traditional, breaking "fixed" and your X server? # Removing xfonts-traditional would break your X server by removing "fixed". # . # You should not remove xfonts-traditional while "fixed" refers to one # of its fonts. You probably want to check the differences between the # various /etc/X11/fonts/misc/xfonts-base.alias*, reconcile any changes, # and then run "update-fonts-alias misc". After that you can retry the # removal. # d-i xfonts-traditional/confirm-break-remove boolean false ############################ #### xfonts-wqy_1.0.0~rc1-7_all.deb ############################ ### Description: Enable WenQuanYi font in fontconfig? # By default, bitmapped fonts are disabled in fontconfig setting because # they are often lower quality. Enabling this option will bypass the # system wide fontconfig setting and allow applications to use WenQuanYi # font without affecting other bitmapped fonts. # d-i xfonts-wqy/enable_wqy boolean true ############################ #### xserver-xorg-legacy_21.1.7-3+deb12u5_amd64.deb ############################ ### Description: Users allowed to start the X server: # Because the X server runs with superuser privileges, it may be unwise to # permit any user to start it, for security reasons. On the other hand, it is # even more unwise to run general-purpose X client programs as root, which is # what may happen if only root is permitted to start the X server. A good # compromise is to permit the X server to be started only by users logged in to # one of the virtual consoles. # d-i xserver-xorg-legacy/xwrapper/allowed_users select Console Users Only # Possible choices: Root Only, Console Users Only, Anybody ### Description: for internal use # This template is never shown to the user and does not require translation. # d-i xserver-xorg-legacy/xwrapper/actual_allowed_users string ############################ #### xringd_1.20-27+b1_amd64.deb ############################ ### Description: Modem device: # Please enter the name of the device the modem is connected to. # . # Xringd needs to poll a modem attached via a serial port. Please # specify which serial port the modem uses (usually /dev/ttyS[0-4]). # d-i xringd/modem-device string /dev/ttyS0 ############################ #### mono-apache-server4_4.2-2.4_all.deb ############################ ### Description: Let mono-apache-server4 restart Apache? # The Debian version of mono-apache-server4 includes a # mono-server4-update script that creates a configuration file for # Apache to start the ASP.NET applications, and mono-server4-update can # restart Apache if there's a new configuration file # (/etc/mono-server4/mono-server-hosts.conf). If this is true, then # Apache will be restarted when there is a new mono-server4-hosts.conf file. # d-i monoserver4/monoserver4_restartapache boolean true ############################ #### mono-xsp4_4.2-2.4_all.deb ############################ ### Description: Start on boot? # If this is true, then XSP4 will automatically start when the computer # is turned on. # d-i xsp4/xsp4_autostart boolean true ### Description: Bind to address: # To function properly, XSP4 needs to be bound to an IP address. The # default ("0.0.0.0") binds to all addresses of the server, but a # specific port can be selected. To use XSP4 only locally, use # "127.0.0.1" for the address. # d-i xsp4/xsp4_bind string 0.0.0.0 ### Description: Bind to port: # XSP is bound to a specific port on the server. Common values are 80, # 8080, or 8081. # d-i xsp4/xsp4_port string 8084 ############################ #### xymon_4.3.30-1+b2_amd64.deb ############################ ### Description: Automatically migrate old hobbit files to xymon? # The operating system user was renamed from "hobbit" to "xymon", and all # configuration, state, log directories and files have been renamed as well. # The package postinst scripts can do the migration automatically. This is # usually a good idea, but might not work so well if your config differs # substantially from the default. # d-i hobbit-client/automatic-xymon-migration boolean true ############################ #### xymon-client_4.3.30-1+b2_amd64.deb ############################ ### Description: Xymon server: # Please enter the network address used to access the Xymon # server(s). If you use multiple servers, use a space-separated list of # addresses. # . # Using host names instead of IP addresses is discouraged in case the # network experiences DNS failures. # d-i hobbit-client/HOBBITSERVERS string 127.0.0.1 ### Description: Client hostname: # Please enter the host name used by the Xymon client when sending # reports to the Xymon server. This name must match # the name used in the hosts.cfg file on the Xymon # server. # d-i hobbit-client/CLIENTHOSTNAME string ### Description: Automatically migrate old hobbit files to xymon? # The operating system user was renamed from "hobbit" to "xymon", and all # configuration, state, log directories and files have been renamed as well. # The package postinst scripts can do the migration automatically. This is # usually a good idea, but might not work so well if your config differs # substantially from the default. # d-i hobbit-client/automatic-xymon-migration boolean true ############################ #### libpam-yubico_2.26-1.1+b1_amd64.deb ############################ ### Description: Parameters for Yubico PAM: # The Yubico PAM module supports two modes of operation: online # validation of YubiKey OTPs or offline validation of YubiKey HMAC-SHA-1 # responses to challenges. # . # The default is online validation, and for that to work you need to get # a free API key at https://upgrade.yubico.com/getapikey/ and # enter the key id as "id=NNNN" and the base64 secret as "key=...". # . # All the available parameters for the Yubico PAM module are described # in /usr/share/doc/libpam-yubico/README.gz. To avoid accidental # lock-outs the module will not be active until it is enabled with the # "pam-auth-update" command. # d-i libpam-yubico/module_args string mode=client try_first_pass id=N key=K ############################ #### zaqar-common_15.0.0-1_all.deb ############################ ### Description: Configure RabbitMQ access with debconf? # OpenStack services need access to a message queue server, defined by the # transport_url directive. Please specify whether configuring this should be # handled through debconf. # . # Only access to RabbitMQ is handled, and the RabbitMQ user creation isn't # performed. A new RabbitMQ user can be created with the commands:" # . # - rabbitmqctl add_user openstack PASSWORD # - rabbitmqctl set_permissions -p / openstack ".*" ".*" ".*" # . # Note that the default RabbitMQ guest account cannot be used for remote # connections. # d-i zaqar/configure_rabbit boolean false ### Description: IP address of your RabbitMQ host: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the IP address of that server. # d-i zaqar/rabbit-host string localhost ### Description: Username for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the username used to connect to that RabbitMQ server. # d-i zaqar/rabbit-userid string guest ### Description: Password for connection to the RabbitMQ server: # In order to interoperate with other components of OpenStack, this package # needs to connect to a central RabbitMQ server. # . # Please specify the password used to connect to that RabbitMQ server. # d-i zaqar/rabbit-password password ### Description: Manage keystone_authtoken with debconf? # Every OpenStack service must contact Keystone, and this is configured through # the [keystone_authtoken] section of the configuration. Specify if you wish to # handle this configuration through debconf. # d-i zaqar/configure_ksat boolean false ### Description: Auth server public endpoint URL: # Specify the URL of your Keystone authentication server public endpoint. This # value will be set in the www_authenticate_uri directive. # d-i zaqar/ksat-public-url string http://localhost:5000 ### Description: Keystone region: # Specify the Keystone region to use. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # d-i zaqar/ksat-region string regionOne ### Description: Create service user? # This package can reuse an already existing username, or create one right now. # If you wish to create one, then you will be prompted for the admin credentials. # d-i zaqar/ksat-create-service-user boolean true ### Description: Auth server admin username: # d-i zaqar/ksat-admin-username string admin ### Description: Auth server admin project name: # d-i zaqar/ksat-admin-project-name string admin ### Description: Auth server admin password: # d-i zaqar/ksat-admin-password password ### Description: Auth server service username: # d-i zaqar/ksat-service-username string ### Description: Auth server service project name: # d-i zaqar/ksat-service-project-name string service ### Description: Auth server service password: # d-i zaqar/ksat-service-password password ############################ #### zaqar-server_15.0.0-1_all.deb ############################ ### Description: Register this service in the Keystone endpoint catalog? # Each OpenStack service (each API) must be registered in the Keystone catalog # in order to be accessible. This is done using "openstack service create" and # "openstack endpoint create". This can be done automatically now. # . # Note that you will need to have an up and running Keystone server on which to # connect using a known admin project name, admin username and password. The # admin auth token is not used anymore. # . # Also, if a service with a matching name is already present in the Keystone # catalog, endpoint registration will be aborted. # d-i zaqar/configure_api-endpoint boolean false ### Description: Keystone server address: # Please enter the address (IP or resolvable address) of the Keystone server, # for creating the new service and endpoints. # . # Any non-valid ipv4, ipv6 or host address string will abort the endpoint # registration. # d-i zaqar/api-keystone-address string ### Description: Keystone endpoint protocol: # d-i zaqar/api-keystone-proto select http # Possible choices: http, https ### Description: Keystone admin username: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i zaqar/api-keystone-admin-username string admin ### Description: Keystone admin project name: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i zaqar/api-keystone-admin-project-name string admin ### Description: Keystone admin password: # To create the service endpoint, this package needs to know the Admin # username, project name, and password, so it can issue commands through the # Keystone API. # d-i zaqar/api-keystone-admin-password password ### Description: This service endpoint address: # Please enter the endpoint address that will be used to contact this service. # You can specify either a Fully Qualified Domain Name (FQDN) or an IP address. # d-i zaqar/api-endpoint-address string ### Description: This service endpoint protocol: # d-i zaqar/api-endpoint-proto select http # Possible choices: http, https ### Description: Name of the region to register: # OpenStack supports using regions, with each region representing a different # location (usually a different data center). Please enter the region name that # you wish to use when registering the endpoint. # . # The region name is usually a string containing only ASCII alphanumerics, # dots, and dashes. # . # A non-valid string will abort the API endpoint registration. # d-i zaqar/api-endpoint-region-name string regionOne ############################ #### zephyr-clients_3.1.2-1.1+b1_amd64.deb ############################ ### Description: Zephyr servers: # Please specify the full names of the Zephyr servers, as a # space-separated list. # . # The list configured on clients can be a subset of the list configured # on servers. # . # This can be left empty if Hesiod is used to advertise Zephyr servers. # d-i zephyr-clients/servers string ### Description: for internal use # We want to try and capture user changes when they edit a config file # manually. To do this we look at the file in the config script. However, # in the case of preconfigure, the config script is run twice before the # postinst is run. Thus we may read the wrong value before the edited value # is written out in postinst. If this is false we skip reading config files # until postinst runs. # d-i zephyr-clients/read_conf boolean true ############################ #### zephyr-server_3.1.2-1.1+b1_amd64.deb ############################ ### Description: Zephyr servers: # Please specify the full names of the Zephyr servers, as a # space-separated list. # . # The list configured on clients can be a subset of the list configured # on servers. # d-i zephyr-server/servers string ### Description: for internal use # We want to try and capture user changes when they edit a config file # manually. To do this we look at the file in the config script. However, # in the case of preconfigure, the config script is run twice before the # postinst is run. Thus we may read the wrong value before the edited value # is written out in postinst. If this is false we skip reading config files # until postinst runs. # d-i zephyr-server/read_conf boolean true ############################ #### zephyr-server-krb5_3.1.2-1.1+b1_amd64.deb ############################ ### Description: Zephyr servers: # Please specify the full names of the Zephyr servers, as a # space-separated list. # . # The list configured on clients can be a subset of the list configured # on servers. # d-i zephyr-server/servers string ### Description: for internal use # We want to try and capture user changes when they edit a config file # manually. To do this we look at the file in the config script. However, # in the case of preconfigure, the config script is run twice before the # postinst is run. Thus we may read the wrong value before the edited value # is written out in postinst. If this is false we skip reading config files # until postinst runs. # d-i zephyr-server/read_conf boolean true ############################ #### zoph_1.0.1-3_all.deb ############################ ### Description: Remove image files (photos) you uploaded? # Zoph imports files into, by default, /var/lib/zoph. # If you decide to remove the zoph package, but wish to # keep the photos you uploaded answer yes. # To have the files removed, answer no. # To be asked at package removal time answer ask. # d-i zoph/rm_images select ask # Possible choices: yes, no, ask ### Description: Keep uploaded image files after removal? # You have imported some photos into /var/lib/zoph, and # are removing the zoph package. # d-i zoph/keep_images boolean true