Package: devscripts Version: 2.18.3 Severity: normal Hi! If the upstream source includes some bad debian packaging, it's likely there'll be a watch file somewhere, usually bogus and/or stale. For this reason, source format 3.0 deletes /debian/ from inside the tarball -- and if the upstream packaging lives in a non-standard places, that's harmless as no tool has bogus ideas like searching elsewhere. Other than uscan, that is.
If there's a bad watch file, let's say source/debian/watch, uscan will randomly (based on filesystem order?) prefer that over debian/watch. Source format 3.0 (quilt) doesn't allow deleting files sanely: it ignores deletions, assuming that the clean target will delete them before build. This works for anything that calls debian/rules targets, but not for uscan. Thus, I'd need to repack the .orig tarball just to workaround this. This is similar to #895982 (uscan looking for debian/changelog in VCS) dirs. What's even the purpose of search for watch and changelog in places other than debian/ ? Meow. -- Package-specific info: --- /etc/devscripts.conf --- --- ~/.devscripts --- DEBCHANGE_RELEASE_HEURISTIC=log DEBSIGN_KEYID=FD9CE2D8D7754B78AB279BBD2C3B436FEAC68101 DSCVERIFY_KEYRINGS="~/.gnupg/pubring.gpg" -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-rc7-debug-00037-gda205b923a99 (SMP w/6 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
