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

On Wed, Oct 09, 2019 at 05:51:53PM +0200, Ansgar Burchardt wrote: > 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 wordi

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

On Wed, Oct 09, 2019 at 05:30:51PM +0100, Simon McVittie wrote: > 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,

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

On Wed, 09 Oct 2019 at 17:51:53 +0200, Ansgar Burchardt wrote: > +--- > | 4.9 > |Required targets must not write outside of the unpacked source > |package tree, except for TMPDIR, /tmp and /var/tmp. > +--- If you are interested in this sort of thing, is per

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

On Wed, Oct 09, 2019 at 08:30:03PM +0200, Guillem Jover wrote: > > thanks for that information! do you agree there's nothing to be added to > > dev-ref? > Yeah, looks like it. & thanks for confirming this too! :) -- cheers, Holger ---

developers-reference_11.0.5_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 10 Oct 2019 10:45:23 +0200 Source: developers-reference Architecture: source Version: 11.0.5 Distribution: unstable Urgency: medium Maintainer: Developers Reference Maintainers Changed-By: Holger Levsen Closes:

Bug#941274: marked as done (developers-reference: please mention the packaging-tutorial and lintian-brush packages)

Your message dated Thu, 10 Oct 2019 09:21:14 + with message-id and subject line Bug#941274: fixed in developers-reference 11.0.5 has caused the Debian Bug report #941274, regarding developers-reference: please mention the packaging-tutorial and lintian-brush packages to be marked as done. Th

Bug#754189: marked as done (developers-reference: describe maintenance workflow for developers-reference)

Your message dated Thu, 10 Oct 2019 09:21:14 + with message-id and subject line Bug#754189: fixed in developers-reference 11.0.5 has caused the Debian Bug report #754189, regarding developers-reference: describe maintenance workflow for developers-reference to be marked as done. This means t

Bug#540248: marked as done (Suggested additions for "Overview of Debian Maintainer Tools" (courtesy of NM))

Your message dated Thu, 10 Oct 2019 09:21:14 + with message-id and subject line Bug#540248: fixed in developers-reference 11.0.5 has caused the Debian Bug report #540248, regarding Suggested additions for "Overview of Debian Maintainer Tools" (courtesy of NM) to be marked as done. This means

Bug#548116: marked as done (developers-reference: Section 3.7 - insert a reminder to retire from teams)

Your message dated Thu, 10 Oct 2019 09:21:14 + with message-id and subject line Bug#548116: fixed in developers-reference 11.0.5 has caused the Debian Bug report #548116, regarding developers-reference: Section 3.7 - insert a reminder to retire from teams to be marked as done. This means tha

Bug#483235: marked as done (developers-reference: Section 8.3.2 - mention to use even tag "l10n")

Your message dated Thu, 10 Oct 2019 09:21:14 + with message-id and subject line Bug#483235: fixed in developers-reference 11.0.5 has caused the Debian Bug report #483235, regarding developers-reference: Section 8.3.2 - mention to use even tag "l10n" to be marked as done. This means that you c

Bug#541956: marked as done (Fw: t-p-u description in dev-ref)

Your message dated Thu, 10 Oct 2019 09:21:14 + with message-id and subject line Bug#541956: fixed in developers-reference 11.0.5 has caused the Debian Bug report #541956, regarding Fw: t-p-u description in dev-ref to be marked as done. This means that you claim that the problem has been dealt

Bug#750993: marked as done (developers-reference: Please mention more lint-style tools)

Your message dated Thu, 10 Oct 2019 09:21:14 + with message-id and subject line Bug#750993: fixed in developers-reference 11.0.5 has caused the Debian Bug report #750993, regarding developers-reference: Please mention more lint-style tools to be marked as done. This means that you claim that

Bug#823584: marked as done (Correct top-level directory name in repackaged tarballs)

Your message dated Thu, 10 Oct 2019 09:21:14 + with message-id and subject line Bug#470960: fixed in developers-reference 11.0.5 has caused the Debian Bug report #470960, regarding Correct top-level directory name in repackaged tarballs to be marked as done. This means that you claim that the

Bug#470960: marked as done (6.7.8.2: point 4 (use foo-ver.orig for repacked tarballs) seems backwards)

Your message dated Thu, 10 Oct 2019 09:21:14 + with message-id and subject line Bug#470960: fixed in developers-reference 11.0.5 has caused the Debian Bug report #470960, regarding 6.7.8.2: point 4 (use foo-ver.orig for repacked tarballs) seems backwards to be marked as done. This means that

Processing of developers-reference_11.0.5_source.changes

developers-reference_11.0.5_source.changes uploaded successfully to localhost along with the files: developers-reference_11.0.5.dsc developers-reference_11.0.5.tar.xz developers-reference_11.0.5_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)