Bug#648271: [debian-policy] 11.8.3 "Packages providing a terminal emulator" says xterm passes -e option straight to exec

Filipus Klutiero writes: > Regarding the formulation, your suggestion does fix the issue Hendrik > identified. I would still remind that the term "command" is ambiguous > (you must be referring to simple commands here). I'm not sure how else to word it. I tried to resolve that ambiguity, but ap

Bug#621050: Document dependencies needed to use multiarch paths

Jonathan Nieder writes: > Russ Allbery wrote: >> Could you prepare an updated patch? > Here's one. Shouldn't this go into the section about shared libraries instead, though? Although I suppose that then raises the question of how to explain the whole multiarch thing there, which is the other pa

Bug#643690: perl policy unclear about the section for manpages

On Sat, 24 Dec 2011 11:06:31 -0800, Russ Allbery wrote: > Yes, this tripped me up too. Here's a proposed patch. Seconds or further > discussion? I'll copy debian-perl as well for further review. > >From f6938d47f9250f672586191cc00988e9e61cea06 Mon Sep 17 00:00:00 2001 > From: Russ Allbery >

Bug#648271: [debian-policy] 11.8.3 "Packages providing a terminal emulator" says xterm passes -e option straight to exec

Le 2011-12-24 14:16, Russ Allbery a écrit : Filipus Klutiero writes: Section 11.8.3 "Packages providing a terminal emulator" contains: To be an x-terminal-emulator, a program must: Support the command-line option -e command, which creates a new terminal window[94

Processed: user debian-pol...@packages.debian.org, limit package to debian-policy, tagging 644230

Processing commands for cont...@bugs.debian.org: > user debian-pol...@packages.debian.org Setting user to debian-pol...@packages.debian.org (was r...@debian.org). > limit package debian-policy Limiting to bugs with field 'package' containing at least one of 'debian-policy' Limit currently set to '

Bug#621050: Document dependencies needed to use multiarch paths

Russ Allbery wrote: > Could you prepare an updated patch? Here's one. --- policy.sgml |8 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/policy.sgml b/policy.sgml index 4aeae363..0ca925e0 100644 --- a/policy.sgml +++ b/policy.sgml @@ -6214,6 +6214,14 @@ install -m644

Processed: user debian-pol...@packages.debian.org, limit package to debian-policy, usertagging 623050 ...

Processing commands for cont...@bugs.debian.org: > user debian-pol...@packages.debian.org Setting user to debian-pol...@packages.debian.org (was r...@debian.org). > limit package debian-policy Limiting to bugs with field 'package' containing at least one of 'debian-policy' Limit currently set to '

Bug#640263: debian-policy: Clarify policy section 9.9 - Environment variables

Russ Allbery wrote: > I propose the attached patch to address all of those issues. Seconds or > further discussion? Looks good to me. (Well, one nit: the log message says custom environment variables (not, say, PATH) where I think the intent is something like custom environme

Bug#621050: Document dependencies needed to use multiarch paths

Jonathan Nieder writes: > Steve Langasek wrote[1]: >> Since we don't want to wait until the next release cycle before being >> able to proceed to step 5, this does mean that a transitional >> dependency is needed to ensure a multiarch-compatible ld.so is unpacked >> before libraries unpack to /li

Processed: user debian-pol...@packages.debian.org, limit package to debian-policy ..., usertagging 650974

Processing commands for cont...@bugs.debian.org: > user debian-pol...@packages.debian.org Setting user to debian-pol...@packages.debian.org (was r...@debian.org). > limit package debian-policy Limiting to bugs with field 'package' containing at least one of 'debian-policy' Limit currently set to '

Processed: user debian-pol...@packages.debian.org, limit package to debian-policy ..., usertagging 648271

Processing commands for cont...@bugs.debian.org: > user debian-pol...@packages.debian.org Setting user to debian-pol...@packages.debian.org (was r...@debian.org). > limit package debian-policy Limiting to bugs with field 'package' containing at least one of 'debian-policy' Limit currently set to '

Bug#648271: [debian-policy] 11.8.3 "Packages providing a terminal emulator" says xterm passes -e option straight to exec

Filipus Klutiero writes: > Section 11.8.3 "Packages providing a terminal emulator" contains: >> To be an x-terminal-emulator, a program must: >> >> Support the command-line option -e command, which creates a new >> terminal window[94 >>

Processed: user debian-pol...@packages.debian.org, limit package to debian-policy, tagging 643690 ...

Processing commands for cont...@bugs.debian.org: > user debian-pol...@packages.debian.org Setting user to debian-pol...@packages.debian.org (was r...@debian.org). > limit package debian-policy Limiting to bugs with field 'package' containing at least one of 'debian-policy' Limit currently set to '

Bug#643690: perl policy unclear about the section for manpages

Steve Langasek writes: > The perl policy makes confusing statements about the section that manpages > should be installed in: > 2.4. Documentation > -- > Manual pages distributed with Perl packages must be installed into the > standard directories: > [...] >

Bug#641153: document Built-Using field for binary packages

Russ Allbery writes: > One basic question about this before I dive into wording: why is the > Build-Depends field not adequate? Never mind this question; I figured it out but forgot to remove this part of my mail. -- Russ Allbery (r...@debian.org)

Bug#641153: document Built-Using field for binary packages

One basic question about this before I dive into wording: why is the Build-Depends field not adequate? Ansgar Burchardt writes: > A try at this: > Some binary packages incorporate material derived from source > or compiled code derived from other source packages. In this case > this fiel

User address for setting usertags for Policy bugs

Charles Plessy writes: > user debian-policy@lists.debian.org > usertags 641153 + normative discussion > thanks Just a quick note: for this to work, the user has to be debian-pol...@packages.debian.org, not the mailing list address. The packages.d.o address is special-cased by the BTS and used t

Processed: user debian-pol...@packages.debian.org, limit package to debian-policy, tagging 640263 ...

Processing commands for cont...@bugs.debian.org: > user debian-pol...@packages.debian.org Setting user to debian-pol...@packages.debian.org (was r...@debian.org). > limit package debian-policy Limiting to bugs with field 'package' containing at least one of 'debian-policy' Limit currently set to '

Bug#640263: debian-policy: Clarify policy section 9.9 - Environment variables

Jonathan Nieder writes: > Colin Watson wrote: >> --- a/policy.sgml >> +++ b/policy.sgml >> @@ -7449,8 +7449,8 @@ Reloading description configuration...done. >> Environment variables >> >> >> - A program must not depend on environment variables to get >> - reasonable default

Processed: user debian-pol...@packages.debian.org, limit package to debian-policy, tagging 617315 ...

Processing commands for cont...@bugs.debian.org: > user debian-pol...@packages.debian.org Setting user to debian-pol...@packages.debian.org (was r...@debian.org). > limit package debian-policy Limiting to bugs with field 'package' containing at least one of 'debian-policy' Limit currently set to '

Bug#617315: policy /usr/local edge case failure

Joey Hess writes: > Policy requires that creation/removal of directories in /usr/local > never fail, but its example does fail as seen in this bug report. > Apparently the problem is that the chown or chmod could fail. > One approach would be to guard them like this: > if [ ! -e