Bug#916021: lintian: Please check for references to build directory

2018-12-20 Thread Chris Lamb
Dmitry, > > The new gitlab auto-notifier is not maintainer by me, but the source > > is indeed in Salsa if you wish to suggest improvements. > > Could you provide a link, please? https://salsa.debian.org/salsa/salsa-webhook Regards, -- ,''`. : :' : Chris Lamb `. `'`

Bug#916021: lintian: Please check for references to build directory

2018-12-20 Thread Dmitry Bogatov
[2018-12-19 20:46] Chris Lamb > Hi Dmitry, > > > PS. Any chance to configure your fine gitlab auto-notifier to send > > not only diffstat, but whole diff too? > > I used to do this manually but it was a bit annoying and sometimes far > too long. > > The new gitlab auto-notifier is not

Bug#916021: lintian: Please check for references to build directory

2018-12-19 Thread Chris Lamb
Hi Dmitry, > PS. Any chance to configure your fine gitlab auto-notifier to send > not only diffstat, but whole diff too? I used to do this manually but it was a bit annoying and sometimes far too long. The new gitlab auto-notifier is not maintainer by me, but the source is indeed in Salsa

Bug#916021: lintian: Please check for references to build directory

2018-12-15 Thread Dmitry Bogatov
[2018-12-13 16:14] Chris Lamb > Fixed in Git, pending upload: > > > https://salsa.debian.org/lintian/lintian/commit/4aaab6b1c5dd2f4e6da498d15713180e4aa68c76 Severity: wishlist Certanity: possible What about excluding some trivial build paths, like "/" or "/build", which are too short to

Bug#916021: lintian: Please check for references to build directory

2018-12-13 Thread Chris Lamb
tags 916021 + pending thanks Fixed in Git, pending upload: https://salsa.debian.org/lintian/lintian/commit/4aaab6b1c5dd2f4e6da498d15713180e4aa68c76 checks/files.desc | 12 checks/files.pm | 12 +--- debian/changelog | 2 ++ 3 files changed, 23 insertions(+), 3

Bug#916021: lintian: Please check for references to build directory

2018-12-12 Thread Dmitry Bogatov
[2018-12-11 08:26] Chris Lamb > [...] > However, we could trust the "Build-Path" field in a .buildinfo if it > exists? Would that work for you? I assume yours contains: > > Build-Path: /home/iu/devel/salsa/ucscpi-tcp"? > > (You may need to pass --buildinfo-option=--always-include-path to >

Bug#916021: [rb-general] Bug#916021: lintian: Please check for references to build directory

2018-12-11 Thread Daniel Shahaf
[fixing bug's address in Cc] Dmitry Bogatov wrote on Mon, 10 Dec 2018 19:49 +: > I believe, most of us keep repositories of git packages somewhere under > ~/. For example, for me, ucspi-tcp package is located at > /home/iu/devel/salsa/ucspi-tcp. > > So my workflow is following: > > $ cd

Bug#916021: lintian: Please check for references to build directory

2018-12-10 Thread Chris Lamb
Hi Dmitry, > $ cd /home/iu/devel/salsa/ucspi-tcp > $ dpkg-buildpackage -us -uc > $ lintian > > And here lintian could check, that generated binary packages does not > contains references to /home/iu/devel/salsa/ucspi-tcp. Alas, I don't think the output of Lintian should ever change depending

Bug#916021: lintian: Please check for references to build directory

2018-12-10 Thread Dmitry Bogatov
[2018-12-09 22:46] Chris Lamb > [Adding rb-gene...@lists.reproducible-builds.org to CC] > > > please add check, that files in binary packages do not refer to build > > directory. See (#915511) for example. ($PWD) > > Do you mean the literal string "$PWD"? No, I meant another thing. I

Bug#916021: lintian: Please check for references to build directory

2018-12-09 Thread Chris Lamb
tags 916021 + moreinfo thanks [Adding rb-gene...@lists.reproducible-builds.org to CC] > please add check, that files in binary packages do not refer to build > directory. See (#915511) for example. This seems like it would have quite the overlap with reproducible builds in that we are

Bug#916021: lintian: Please check for references to build directory

2018-12-09 Thread Dmitry Bogatov
Package: lintian Version: 2.5.116 Severity: wishlist Dear Maintainer, please add check, that files in binary packages do not refer to build directory. See (#915511) for example. I believe the following strings should raise warning: /build/{name} /build/{name}-{version} $PWD