[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#816667: www.debian.org: please make the documentation from dbconfig-common available



Package: www.debian.org
Severity: wishlist

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

As suggested by Paul Wise in a response to an e-mail to debian-admin@l.d.o, I
would like to have the content that currently lives here:
https://people.debian.org/~seanius/policy/dbapp-policy.html/
https://people.debian.org/~seanius/policy/dbconfig-common.html/
https://people.debian.org/~seanius/policy/dbconfig-common-design.html
to be extracted from the dbconfig-common binary package and made available on
https://www.debian.org/doc/devel-manuals or in the ../packaging-manuals. The
current webpages are out-dated and seanius is retired from Debian so won't
update anymore.

The documentation can be found at
/usr/share/doc/dbconfig-common/dbapp-policy.html/
/usr/share/doc/dbconfig-common/dbconfig-common.html/
/usr/share/doc/dbconfig-common/dbconfig-common-design.html
when one has installed the dbconfig-common package. There are also pdf and ps
versions available.

Thanks in advance.

Paul

- -- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (60, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJW2JPFAAoJEJxcmesFvXUKV+IH/1N4XjAzTdwtvo7c9DtormTA
1X3OKNh5/xxBCVj0T4V2LiTGultJxbcyIQ5QAd+H/iYuCFVJoFhXXg3K4JXg3V0e
nTvz637qO2/OZDQHYSuoVb24VGqCRxFhod50N19kzHV3iUbbGfJNPOHJUV4HcPK+
ZUxi1cIj3VykJBzMVneZoeP+60oLteWVTMC1c9UruEi6I960Oy6ZPqEAH/UyIOJ+
091eJqy3eSMQgYjHDEgqlJXxXZCNr1/rjuwWGZdrNy5FM3hLRzECUiIu8fc6miWc
Qwssm5eBu/774QsGQhS5Af3v+XPiujpofFCnAj2lJKTHB8WJpUQk+BqYcMg+t0M=
=FbFM
-----END PGP SIGNATURE-----


Reply to: