Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #712408

Bug#812721: gbp could filter out Files-Excluded: entries when committing to the pristine-tar branch

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Package: git-buildpackage
Version: 0.7.1
Severity: wishlist

Dear Maintainer,

When uscan is used to generate an upstream tarball, it filters out files
listed in the Files-Excluded: section of the debian/copyright file and
appends +dfsg to the tarball's version.  This can then be imported to
the packaging repository with gbp import-orig.

Nowadays, many upstreams do not ship tarballs.  When preparing the
Debian packaging for such a project, it is convenient to simply clone
upstream's git repository and add a branch to that for Debian
packaging.

Suppose that upstream tags a release 1.2.3 in the git repository.  The
Debian package maintainer must then manually delete the files listed in
Files-Excluded: and then tag a new version 1.2.3+dfsg.  gbp can then
create a tarball of this tag and commit it to the pristine-tar branch.

It would be great if gbp could produce the 1.2.3+dfsg tag itself by
reading debian/copyright and excluding the Files-Excluded: files.

-- 
Sean Whitton

Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Bug#812721: gbp could filter out Files-Excluded: entries when committing to the pristine-tar branch Sean Whitton <spwhitton@spwhitton.name> - 2016-01-26 05:10 +0100
  Bug#812721: gbp could filter out Files-Excluded: entries when committing to the pristine-tar branch Guido Günther <agx@sigxcpu.org> - 2016-01-26 07:50 +0100

csiph-web