How to handle a change in "Files-Excluded:" with gbp
- To: <debian-science@lists.debian.org>
- Subject: How to handle a change in "Files-Excluded:" with gbp
- From: Thomas Schiex <thomas.schiex@inra.fr>
- Date: Tue, 7 Aug 2018 18:18:29 +0200
- Message-id: <[🔎] 203b09c5-d830-ab39-8629-0cd627b63d02@inra.fr>
- In-reply-to: <20180703095921.glk4veahz5jud45s@an3as.eu>
- References: <20180629154321.GA25908@Asuna> <439c5ce2-ea9f-fc49-a085-86b518f9437f@inra.fr> <20180702143211.ts277tavxndvetvl@an3as.eu> <9c466618-d36b-4c14-1319-727ed31ed804@inra.fr> <20180703040116.dc2bqnwhmnt5gsbm@an3as.eu> <721911a9-2b69-4055-4d28-92f00afdb3a7@inra.fr> <20180703095921.glk4veahz5jud45s@an3as.eu>
Hello everyone,
I'm trying to polish the packaging for toulbar2 on salsa and I would
like to remove a file from upstream (a doc that is included there and
regenerated from source during compilation).This is to avoid a lintian
"source-contains-prebuilt-doxygen-documentation".
Some files are already excluded from upstream using "Files-Excluded:" in
debian/copyright, and I just added this file to the list.
But this means a new "tarball" needs to be generated by uscan and
committed. This would look like an upstream change, but it's a "debian"
change. As I expected
uscan --verbose --force-download
gbp import-orig --pristine-tar ../toulbar2_1.0.0+dfsg.orig.tar.xz
does not work as the upstream version number is unchanged and I get:
gbp:error: Upstream tag 'upstream/1.0.0+dfsg' already exists
What would you do?
Would it be reasonable to ignore this
"source-contains-prebuilt-doxygen-documentation" for now and wait for
the next upstream version to remove it?
Thomas
Reply to: