Re: What makes a .changes file source-only? [and 1 more messages]

To: Guillem Jover <guillem@debian.org>, Sean Whitton <spwhitton@spwhitton.name>, debian-dpkg@lists.debian.org
Subject: Re: What makes a .changes file source-only? [and 1 more messages]
From: Ian Jackson <ijackson@chiark.greenend.org.uk>
Date: Wed, 21 Jun 2017 16:56:23 +0100
Message-id: <[🔎] 22858.38695.124470.105740@chiark.greenend.org.uk>
In-reply-to: <[🔎] 22858.38499.851401.671229@chiark.greenend.org.uk>
References: <20170523171718.jui35r5axdhy44mz@zephyr.silentflame.com> <20170523235754.on5jnito2ss6q2wv@gaara.hadrons.org> <20170524072448.fdfwvaotr4chfk5s@zephyr.silentflame.com> <22821.24939.118527.790266@chiark.greenend.org.uk> <[🔎] 20170621041215.qgscs63frwkvqht4@gaara.hadrons.org> <[🔎] 22858.38499.851401.671229@chiark.greenend.org.uk>

Ian Jackson writes ("Re: What makes a .changes file source-only? [and 1 more messages]"):
> Certainly, actual source packages uploaded by dgit are affected by any
                                                         ^ NOT
> infelicities that may exist in the package clean target.

Ian.

Reply to:

References:
- Re: What makes a .changes file source-only? [and 1 more messages]
  - From: Guillem Jover <guillem@debian.org>
- Re: What makes a .changes file source-only? [and 1 more messages]
  - From: Ian Jackson <ijackson@chiark.greenend.org.uk>

Prev by Date: Re: What makes a .changes file source-only? [and 1 more messages]
Next by Date: Re: source-only builds and .buildinfo
Previous by thread: Re: What makes a .changes file source-only? [and 1 more messages]
Index(es):
- Date
- Thread