Bug#288822: marked as done (developers-reference: "Bugs" control field not documented)

2019-10-09 Thread Guillem Jover
On Tue, 2019-10-08 at 10:33:46 +, Holger Levsen wrote: > On Tue, Oct 08, 2019 at 12:30:50PM +0200, Guillem Jover wrote: > > > I don't really understand "#288822: developers-reference: "Bugs" control > > > field > > > not documented" and I'm not sure it's really an issue still. > > This would

Bug#942051: debian-policy: [4.9] requirement to write only to /tmp, /var/tmp, ${TMPDIR} is too strict

2019-10-09 Thread Simon McVittie
On Wed, 09 Oct 2019 at 18:08:09 +0200, Bill Allombert wrote: > On Wed, Oct 09, 2019 at 05:51:53PM +0200, Ansgar Burchardt wrote: > > There are > > other paths that should be fine to be written to during the build > > process, for example /dev/shm > > Do you have example of packages that does that

Bug#942051: debian-policy: [4.9] requirement to write only to /tmp, /var/tmp, ${TMPDIR} is too strict

2019-10-09 Thread Bill Allombert
On Wed, Oct 09, 2019 at 05:51:53PM +0200, Ansgar Burchardt wrote: > Package: debian-policy > Version: 4.4.1.1 > Severity: minor > > While checking the upgrade checklist I noticed this new requirement: > > +--- > | 4.9 > |Required targets must not write outside of the unpacked source > |

Bug#942051: debian-policy: [4.9] requirement to write only to /tmp, /var/tmp, ${TMPDIR} is too strict

2019-10-09 Thread Ansgar Burchardt
Package: debian-policy Version: 4.4.1.1 Severity: minor While checking the upgrade checklist I noticed this new requirement: +--- | 4.9 |Required targets must not write outside of the unpacked source |package tree, except for TMPDIR, /tmp and /var/tmp. +--- The wording is a bit too