From 6e65361c03015f933a393ad8667c0fb0dd0b6adf Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Wed, 24 Jan 2018 23:45:57 +0000 Subject: [PATCH 1/1] dgit(7): Discuss file executability. Signed-off-by: Ian Jackson --- debian/changelog | 3 +++ dgit.7 | 13 +++++++++++++ 2 files changed, 16 insertions(+) diff --git a/debian/changelog b/debian/changelog index 6bac07b7..c32ba467 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,5 +1,8 @@ dgit (4.3~) unstable; urgency=medium + Documentation improvements: + * dgit(7): Discuss file executability. + Bugfixes: * dgit archive-api-query: Avoid crashing due to lack of $isuite. This breaks the infrastructure. Closes:#886592. diff --git a/dgit.7 b/dgit.7 index 70165a1b..ca115352 100644 --- a/dgit.7 +++ b/dgit.7 @@ -243,6 +243,19 @@ If you are not the maintainer, you do not need to worry about the source format of the package. You can just make changes as you like in git. If the package is a `3.0 (quilt)' package, the patch stack will usually not be represented in the git history. +.SH FILE EXECUTABILITY +Debian source package formats +do not always faithfully reproduce +changes to executability. +But dgit insists that the result of dgit clone is identical +(as far as git can represent - see Limitations, above) +to the result of dpkg-source -x. + +So files that are executable in your git tree +must be executable in the result of dpkg-source -x +(but often aren't). +If a package has such troublesome files, +they have to be non-executable in dgit-compatible git branches. .SH FORMAT 3.0 (QUILT) For a format `3.0 (quilt)' source package, dgit may have to make a commit on your current branch to contain metadata used by quilt and -- 2.30.2