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

Debian Policy released

Hello everyone,

I just uploaded Debian Policy to sid.

Here are the normative changes from the previously announced version of
Policy (4.1.2):

    URLs given in ``VCS-*`` headers should use a scheme that provides
    confidentiality (``https``, for example) if the VCS repository
    supports it.  ``[vcs-field-uses-insecure-uri]``

    ``Built-Using`` should be used exactly when there are license or
    DFSG requirements to retain full source code in the archive.
    Previously, the description of the field implied it was needed in
    other cases too.

    ``libc`` may also install files in ``/lib64``.
    If a package's daemon should not be autostarted unless the local
    administrator has explicitly requested it, the package's
    ``postinst`` should use the new ``defaults-disabled`` option of

    The old method of including ``DISABLED=yes`` in the package's
    ``/etc/default`` file should not be used.

    Clarify that programs may invoke either ``/usr/bin/editor`` and
    ``/usr/bin/pager`` directly, or use ``editor`` and ``pager`` and
    rely on PATH.

    The Creative Commons CC0 1.0 Universal license (CC0-1.0) is now
    included in ``/usr/share/common-licenses`` and does not need to be
    copied verbatim in the package ``copyright`` file.

    [not actually included in /usr/share/common-licenses yet, pending an
    update to the base-files package]

Sean Whitton

Attachment: signature.asc
Description: PGP signature

Reply to: