Sean Whitton writes:
> On Tue, Aug 01, 2017 at 04:55:33PM +0100, Ian Jackson wrote:
>> We should surely import the diagrams as-is.
> Russ -- you were the one that suggested generating them. What do you
> think about importing them as-is now?
My only concern about importing them as-is is that d
Hello Guillem,
On Wed, Aug 02, 2017 at 12:54:15AM +0200, Guillem Jover wrote:
> Except for the last dpkg which should probably be dpkg-source, I do
> like this version better.
>
> Also perhaps worth mentioning that dpkg-source will remove the value
> if there is no debian/tests/control file (and
> The problem is that the information in Uploaders is no more likely to
> be up-to-date than the team homepage/policy/docs.
I disagree: team homepage/policy/docs can go unmaintained for long,
whereas every upload triggers a lintian warning unless the uploader is
listed as such (and unless expli
Processing commands for cont...@bugs.debian.org:
> tags 822430 + pending
Bug #822430 [debian-policy] debian-policy: Please update 8.1.1 to use the
"ldconfig" trigger instead
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
822430: https://bug
On Tue, Aug 01, 2017 at 07:47:47PM +0300, Adrian Bunk wrote:
> 1. Debian does not currently have non-amd64 binary-all autobuilders
>
> Stating that binary-all packages in the archive are always being
> built on amd64 would actually document the current status quo,
> assuming source-only uploads.
Hi!
On Wed, 2014-08-20 at 09:44:45 -0300, Antonio Terceiro wrote:
> There are cases when you want to add it explicitly, e.g. when someone
> comes up with a new possible value for it that is not automatically
> added yet.
>
> Testsuite: mynewthing
>
> or even
>
> Testsuite: autopkgtest, mynewthi
On Sun, Apr 24, 2016 at 01:14:49PM +0200, Niels Thykier wrote:
>
> """
> Any package installing shared libraries in one of the default library
> directories of the dynamic linker (which are currently /usr/lib and
> /lib) or a directory that is listed in /etc/ld.so.conf[60] must use
> ldconfig to u
On Thu, Jan 05, 2017 at 03:22:44PM +1100, Stuart Prescott wrote:
> [ various comments on Ian's proposal ]
Ian, do you have an updated proposal in response to Stuart's points?
> * Deprecating patch systems should also deprecate the 'patch' target
> in debian/rules from §4.9.
Thanks for noting thi
Hello Niels,
On Sun, Apr 24, 2016 at 01:14:49PM +0200, Niels Thykier wrote:
> Possible wording could be:
>
> """
> Any package installing shared libraries in one of the default library
> directories of the dynamic linker (which are currently /usr/lib and
> /lib) or a directory that is listed in /
Processing commands for cont...@bugs.debian.org:
> user debian-pol...@packages.debian.org
Setting user to debian-pol...@packages.debian.org (was
spwhit...@spwhitton.name).
> limit package debian-policy
Limiting to bugs with field 'package' containing at least one of 'debian-policy'
Limit currentl
Hi,
On Tue, 1 Aug 2017 11:23:28 -0400
Sean Whitton wrote:
> We are hoping to migrate Policy to rST built by Sphinx. Maybe there is
> a flowchart tool that integrates particularly well with Sphinx. CCing
> Hideki in case he knows.
Maybe python-sphinxcontrib.blockdiag is the one.
$ apt show py
control: tag -1 +pending
On Tue, Aug 01, 2017 at 11:18:56PM +0200, Bill Allombert wrote:
> Please always quote what you are seconding. This avoid confusion.
Thanks for the tip, Bill.
--
Sean Whitton
signature.asc
Description: PGP signature
Processing control commands:
> tag -1 +pending
Bug #758124 [debian-policy] Documenting the Testsuite field in the Policy.
Added tag(s) pending.
--
758124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Tue, Aug 01, 2017 at 04:23:05PM -0400, Sean Whitton wrote:
> Hello,
>
> I second Charles' patch.
Please always quote what you are seconding. This avoid confusion.
Cheers,
--
Bill.
Imagine a large red swirl here.
On Tue, Aug 01, 2017 at 04:23:05PM -0400, Sean Whitton wrote:
> Hello,
>
> I second Charles' patch.
>
> I'll note that as a policy delegate I'll make the following
> purely informative changes to the patch once committed:
>
> - don't qualify with dpkg version number since it is older than the
>
Hello,
I second Charles' patch.
I'll note that as a policy delegate I'll make the following
purely informative changes to the patch once committed:
- don't qualify with dpkg version number since it is older than the
version in oldstable
- move the text out of tags since we're trying to reduc
Processing commands for cont...@bugs.debian.org:
> reassign 868496 debmake-doc
Bug #868496 [debian-policy] debian-policy: Please Clarify Need for
update-fonts-dir in postinst and postrm Scripts
Bug reassigned from package 'debian-policy' to 'debmake-doc'.
No longer marked as found in versions deb
On Tue, Aug 01, 2017 at 04:55:33PM +0100, Ian Jackson wrote:
> We should surely import the diagrams as-is.
Russ -- you were the one that suggested generating them. What do you
think about importing them as-is now?
--
Sean Whitton
signature.asc
Description: PGP signature
On Tue, Aug 01, 2017 at 10:18:24AM -0700, Russ Allbery wrote:
> I usually try to credit the person who wrote the bulk of the wording, even
> if someone else asked for seconds. I think of it as more of a credit
> thing than a process thing.
Since Bill agrees, I've reverted my change.
> Hope the s
On Tue, Aug 01, 2017 at 12:09:00PM -0400, Sean Whitton wrote:
> Hello,
>
> README.md says that "Wording:" is for the author of a change. However,
> I believe that the intention of the field is not to give credit to the
> author of a patch, but to indicate who sought seconds for the patch. So
> I
On Sat, Jul 15, 2017 at 07:18:41AM -0700, Sean Whitton wrote:
> Hello Bill,
>
> On Sat, Jul 15, 2017 at 02:48:36PM +0200, Bill Allombert wrote:
> > The problem is that the majority of such documentation is outdated and
> > obsolete to the point of being useless.
> > Most team start big and then sl
Sean Whitton writes:
> README.md says that "Wording:" is for the author of a change. However,
> I believe that the intention of the field is not to give credit to the
> author of a patch, but to indicate who sought seconds for the patch. So
> I've replaced "author" with "proposer" in README.md.
On Fri, Jul 14, 2017 at 04:33:49PM -0700, Sean Whitton wrote:
>...
> Before doing that, at the risk of achieving nothing, I'd like to suggest
> another wording:
>
> ... if the Maintainer control field names a group of people and a
> shared email address, the Uploaders field must be present
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sun, Dec 04, 2016 at 07:32:29PM +0100, Christoph Biedl wrote:
> Package: debian-policy
> Severity: normal
>
> Following a recent discussion on debian-devel[0], I'd like to
> formalize the (XS-)Build-Indep-Architecture: header mentioned there.
>
Hello,
README.md says that "Wording:" is for the author of a change. However,
I believe that the intention of the field is not to give credit to the
author of a patch, but to indicate who sought seconds for the patch. So
I've replaced "author" with "proposer" in README.md.
Please let me know if
Processing commands for cont...@bugs.debian.org:
> user debian-pol...@packages.debian.org
Setting user to debian-pol...@packages.debian.org (was
spwhit...@spwhitton.name).
> limit package debian-policy
Limiting to bugs with field 'package' containing at least one of 'debian-policy'
Limit currentl
Sean Whitton writes ("Re: Bug#485776: debian-policy: Adding graphical
flowcharts for maintainer scripts invocation would help understand the
process"):
> control: retitle -1 Incorporate maintscript flowcharts from Debian Women, or
> similar
>
> Here is an updated URI to the Debian Women flowcha
Hi,
On Mon, Jul 31, 2017 at 10:38:33PM -0700, Paul Hardy wrote:
> I am adding the maintainer of the New Maintainer's Guide and the Guide
> for Debian Maintainers, Osamu Aoki, to this discussion. I would like
> to reassign this wishlist bug to one of those packages if Osamu
> agrees.
Reassin to "
Package: debian-policy
Version: 4.0.0.4
Followup-For: Bug #678607
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> diff --git a/policy.xml b/policy.xml
> index ce5960b..725a951 100644
> --- a/policy.xml
> +++ b/policy.xml
> @@ -11777,8 +11777,12 @@ END-INFO-DIR-ENTRY
>
>
>
On Fri, Jul 14, 2017 at 04:51:51PM -0700, Sean Whitton wrote:
> I'm not sure why Jonathan thinks his patch is a strawman. It addresses
> the main issue of this bug. I don't think the explanation of what an
> upstream contact is needs to be relegated to a footnote. So I am
> seeking seconds for t
Processing commands for cont...@bugs.debian.org:
> outlook 661928 Recipe should be added as a script in devscripts, to which
> Policy can make reference.
Outlook recorded from message bug 661928 message
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
661928: htt
control: retitle -1 Incorporate maintscript flowcharts from Debian Women, or
similar
Here is an updated URI to the Debian Women flowcharts:
https://wiki.debian.org/MaintainerScripts
On Fri, Jun 27, 2008 at 07:47:21PM +0100, Ian Jackson wrote:
> OK, I'll get out xfig, which is my personal least
Processing control commands:
> retitle -1 Incorporate maintscript flowcharts from Debian Women, or similar
Bug #485776 [debian-policy] add graphical flowcharts for maintainer scripts
Changed Bug title to 'Incorporate maintscript flowcharts from Debian Women, or
similar' from 'add graphical flowch
Hello,
On Fri, May 22, 2015 at 01:34:42PM +0900, Charles Plessy wrote:
> Experiments on new fields are welcome, and it is good to open bugs to track
> them. But I think that we should first see how the proposed field gets
> traction before adding it to the specification.
codesearch.debian.net su
34 matches
Mail list logo