On Wed, Jul 17, 2019 at 04:16:39PM +0200, Enrico Weigelt, metux IT consult wrote: > > > In practice, that's not going to be a problem for most distributions. > > The traditional way Debian-derived systems have done builds is > > completely outside of git. So there will be a linux_5.2.orig.tar.gz > > and a linux_5.2-1.debian.tar.xz. dpkg_source -x will first unpackage > > the orig.tar.gz, and then the debian.tar.xz, and if the second > > overwrites the first, it's no big deal. > > ACK. IIRC they already filter out debian/ directories when generating > upstream tarballs - other upstreams already provide their debian/ > stuff, too. Well, no, actually they don't. That's because as much as possible they want the upstream tarball to be bit-for-bit identical to the one published on the official upstream distribution site. That allows them to include the detached PGP signature from the upstream maintainer, if one is provided. If there are files in the upstream debian/ directory that they don't need, they can delete in the distro's debian/rules file. Ideally, so we shouldn't include files in the Linux kernel's debian/ directory willy-nilly. But the debian/rules file will *always* be present, and so it will be overwritten by the <package>_<ver>.debian.tar.xz file, and so it's no big deal. - Ted
