Your message dated Fri, 11 Aug 2017 12:44:51 -0700
with message-id <>
and subject line Closing inactive Policy bugs
has caused the Debian Bug report #681289,
regarding changelog and copyright should be package metadata
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: debian-policy
Severity: wishlist
Usertags: changelog

Both the changelog and the copyright files are stored with a package's
normal data (within data.tar in the .deb) but they are really package
metadata (that should be part of control.tar in the .deb).

All the tools and services that currently extract both of those files
(packages.d.o, apt-listhanges, etc.) would benefit from being able to
extract them with the rest of the package metadata.

Additionnaly it also solves a problem that we have with multi-arch same
packages and bin-nmu. Such a bin-nmu means that the changelog on the
bin-nmued architecture will be different from the other arches and the
package is thus no longer co-installable.

We should thus modify the policy to say:

1/ that the changelog and copyright files ought to be installed in the
   DEBIAN directory along with the other control files

   (this will require changes in dh_installdocs and dh_installchangelogs)

2/ that programs that want to retrieve the changelog and/or copyright file
   of an installed package should try to use "dpkg-query --control-show <pkg>
   <changelog|copyrigh>" and fall back to the usual path if that fails.

   Those interfaces are available in wheezy's dpkg (>= 1.16.5).

3/ that programs that want to retrieve the changelog and/or copyright file
   of a .deb file should use dpkg-deb -I <file> <changelog|copyrigh>" (or
   look for the changelog/copyright file in the directory extracted
   with dpkg-deb -e <file>)

This should probably be included in a new major revision of the policy
(4.0 that you wanted to do shortly after wheezy's release?).

QUESTION: Shall we design some solution to ensure that
/usr/share/doc/<pkg>/{changelog.Debian.gz,copyright} are kept during the
transition period ?

If yes, we need to think of a solution that doesn't involve as much pain
as was the /usr/doc transition (i.e. we want a single tool that does it for
all packages rather than a maintainer script snippet in all packages).

-- System Information:
Debian Release: wheezy/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (150, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 3.4-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
control: user
control: usertag -1 +obsolete
control: tag -1 +wontfix

Russ Allbery and I did a round of in-person bug triage at DebConf17 and
we are closing this bug as inactive.

The reasons for closing fall into the following categories, from most
frequent to least frequent:

- issue is appropriate for Policy, there is a consensus on how to fix
  the problem, but preparing the patch is very time-consuming and no-one
  has volunteered to do it, and we do not judge the issue to be
  important enough to keep an open bug around;

- issue is appropriate for Policy but there does not yet exist a
  consensus on what should change, and no recent discussion.  A fresh
  discussion might allow us to reach consensus, and the messages in the
  old bug are unlikely to help very much; or

- issue is not appropriate for Policy.

If you feel this bug is still relevant and want to restart the
discussion, you can re-open the bug.  However, please consider instead
opening a new bug with a message that summarises and condenses the
previous discussion, updates the report for the current state of Debian,
and makes clear exactly what you think should change.

A lot of these old bugs have long side tangents and numerous messages,
and that old discussion is not necessarily helpful for figuring out what
Debian Policy should say today.

Sean Whitton

Attachment: signature.asc
Description: PGP signature

--- End Message ---

Reply via email to