dbconfig-common 2.0.20 source package in Ubuntu

Changelog

dbconfig-common (2.0.20) unstable; urgency=medium

  [ Debian Janitor ]
  * Remove constraints unnecessary since buster

  [ Guilhem Moulin ]
  * Replace `which` calls with `command -v`. (Closes: #995957)

 -- Paul Gevers <email address hidden>  Sun, 10 Oct 2021 21:48:00 +0200

Upload details

Uploaded by:
Paul Gevers
Uploaded to:
Sid
Original maintainer:
Paul Gevers
Architectures:
all
Section:
admin
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Jammy: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
dbconfig-common_2.0.20.dsc 1.8 KiB fe347c927f26ac17b085fdf4cc33c0e78b460baf5f0f64b5ff8d053895ff97aa
dbconfig-common_2.0.20.tar.xz 217.5 KiB 4b4f3acb0220668e6bb75bf8a6aecca4db1d412aa461ed702187246a403f1b6d

Available diffs

No changes file available.

Binary packages built by this source

dbconfig-common: framework that helps packages to manage databases

 This package contains the core of the dbconfig-common framework. This
 framework presents a policy and implementation for managing various databases
 used by applications included in Debian packages.
 .
 It can:
  - support MySQL/MariaDB, PostgreSQL, and SQLite3 based applications;
  - create or remove databases and database users;
  - access local or remote databases;
  - upgrade/modify databases when upstream changes database structure;
  - generate config files in many formats with the database info;
  - import configs from packages previously managing databases on their own;
  - prompt users with a set of normalized, pre-translated questions;
  - handle failures gracefully, with an option to retry;
  - do all the hard work automatically;
  - work for package maintainers with little effort on their part;
  - work for local admins with little effort on their part;
  - comply with an agreed upon set of standards for behavior;
  - do absolutely nothing if that is the whim of the local admin;
  - perform all operations from within the standard flow of
    package management (no additional skill is required of the local
    admin).

dbconfig-mysql: dbconfig-common MySQL/MariaDB support

 This package ensures MySQL/MariaDB support in the dbconfig-common framework,
 and should be in the depends list of packages that require MySQL support from
 dbconfig-common.
 .
 System administrators that don't want dbconfig-common to handle the database
 management should install dbconfig-no-thanks instead.

dbconfig-no-thanks: dbconfig-common bypass

 If a package relies on the dbconfig-common framework for database setup and
 maintenance, installing dbconfig-no-thanks instead of one of dbconfig's
 database-specific packages will block this function. It is intended for cases
 where the system administrator desires or requires full control of the
 database or where dbconfig-common makes bad choices, and typically leaves
 the depending packages non-functional until manually configured.

dbconfig-pgsql: dbconfig-common PostgreSQL support

 This package ensures PostgreSQL support in the dbconfig-common framework, and
 should be in the depends list of packages that require PostgreSQL support from
 dbconfig-common.
 .
 System administrators that don't want dbconfig-common to handle the database
 management should install dbconfig-no-thanks instead.

dbconfig-sqlite3: dbconfig-common SQLite3 support

 This package ensures SQLite3 support in the dbconfig-common framework, and
 should be in the depends list of packages that require SQLite3 support from
 dbconfig-common.
 .
 System administrators that don't want dbconfig-common to handle the database
 management should install dbconfig-no-thanks instead.