Bug#452215: Add a check to make sure the .diff.gz is clean when debian/patches is used
Package: lintian Version: 1.23.36 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It would be nice to have some warnings in case the modification in .diff.gz go out of the scope of debian/ despite the existence of debian/patches (altough also reporting when the package build-depends on dpatch or quilt shouldn't harm). This is based on the idea that if debian/patches is used it means the maintainer may have done something wrong (.patch left behind under some dir? what about a somedir.orig forgotten?). Regards, Raphael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHQ5QqYy49rUbZzloRAh1bAJ93uQQ5KLqWkHflBAkpXywf7VNvGgCePfop rE+UYuuGEU0QiV3jdJHHgt4= =ksKw -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452215: Add a check to make sure the .diff.gz is clean when debian/patches is used
Raphael Geissert [EMAIL PROTECTED] writes: Package: lintian Version: 1.23.36 Severity: wishlist It would be nice to have some warnings in case the modification in .diff.gz go out of the scope of debian/ despite the existence of debian/patches (altough also reporting when the package build-depends on dpatch or quilt shouldn't harm). This is based on the idea that if debian/patches is used it means the maintainer may have done something wrong (.patch left behind under some dir? what about a somedir.orig forgotten?). This is a very good idea. I'll work on including something like that in the next release. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
