This is an automated email from the git hooks/post-receive script.
hertzog pushed a change to branch master
in repository developers-reference.
from e586826 Fix spelling, grammar, capitalisation and wording issues
new 9a9bdb9 Update section about package tracker
The 1 revision
This is an automated email from the git hooks/post-receive script.
hertzog pushed a commit to branch master
in repository developers-reference.
commit 9a9bdb951bfca5fbeec5ed6eaceced04ffe336b1
Author: Raphaël Hertzog
Date: Thu Mar 15 00:51:07 2018 +0100
Update section about package
This is an automated email from the git hooks/post-receive script.
hertzog pushed a change to branch master
in repository developers-reference.
from 66dcf83 Update the section about the package tracker
new 01aa6ab Also document List-Id header in package tracker mails.
The 1 re
This is an automated email from the git hooks/post-receive script.
hertzog pushed a commit to branch master
in repository developers-reference.
commit 01aa6abb9191354b88926a1626e92fce2a1405b2
Author: Raphaël Hertzog
Date: Thu Dec 10 09:54:46 2015 +0100
Also document List-Id header in
+EH0SOomqkXgDyYDD1+LU6eTygG477/102URJ3aaA=
=ntf3
-END PGP SIGNATURE-
Paul Wise (1):
Make it easier to update devref for a new Debian release.
Raphaël Hertzog (1):
Update the section about the package tracker
This is an automated email from the git hooks/post-receive script.
hertzog pushed a change to branch master
in repository developers-reference.
from fc56ee5 Make it easier to update devref for a new Debian release.
new 66dcf83 Update the section about the package tracker
The 1
This is an automated email from the git hooks/post-receive script.
hertzog pushed a commit to branch master
in repository developers-reference.
commit 66dcf83329873f0c531fbdb7fe88329d0e303721
Author: Raphaël Hertzog
Date: Wed Dec 9 10:46:34 2015 +0100
Update the section about the package
This is an automated email from the git hooks/post-receive script.
hertzog pushed a change to branch master
in repository developers-reference.
from b32b214 update Japanese translation
new f205dbb Drop myself from Uploaders.
The 1 revisions listed above as "new" are entirely n
Package: debian-policy
Severity: wishlist
User: debian-d...@lists.debian.org
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).
Package: debian-policy
Version: 3.9.2.0
Severity: normal
Tags: patch
With dpkg >= 1.16.1, the value of the Architecture field in the .dsc
is generated a bit differently.
The goal is to be able to always know when a source package generates an
architecture-independent package. Currently as soon as
Package: debian-policy
Version: 3.8.4.0
Severity: minor
/usr/share/doc/debian-policy/Process.html is difficult to read as the text
is grey and the background is another variant of grey.
color: DarkSlateGrey;
background-color: gainsboro;
Please stick to plain black on a white background.
Also in
Package: debian-policy
Version: 3.8.4.0
Severity: normal
The policy needs to be updated to take into account the dpkg triggers. At
the very least it needs to document the new invocations of the postinst in
chapter 6 (postinst triggered ...) see
/usr/share/doc/dpkg-dev/triggers.txt.gz
-- System In
Package: debian-policy
Version: 3.8.4.0
Severity: normal
I stumbled upon policy 7.4:
> A Conflicts entry should almost never have an "earlier than" version clause.
> This would prevent dpkg from upgrading or installing the package which
> declared
> such a conflict until the upgrade or removal of
Package: debian-policy
Version: 3.8.3.0
Severity: wishlist
We have some unwritten packaging rules and it would be good to write them
down even if some of them appear to be obvious to most of us. I think in
particular to stuff like:
- a package must at least be upgradable from one stable release t
Package: developers-reference
Version: 3.4.3
Severity: normal
Following a discussion on debian-newmaint, I think it's important to
improve the section about the duties to clearly communicate to all package
maintainers (and not DD only) that the bare minimum is what I described
in the pledge below
Package: debian-policy
Version: 3.8.2.0
Severity: normal
Since the upload of install-info to sid, packages installing info
documentation should no more call install-info in their postinst.
It is now automatically done by the file trigger provided by the
install-info package.
You should however ex
Package: debian-policy
Version: 3.8.2.0
Severity: wishlist
Tags: patch
In response to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494714 I
would like that the policy be updated to allow the Binary field in .dsc and
.changes to span over multiple lines.
Here's a suggested patch:
--- a/policy.
17 matches
Mail list logo
