On Fri, Jan 3, 2020 at 3:24 AM Felix Lechner <felix.lech...@lease-up.com> wrote: > > Hi Tong, > > On Thu, Jan 2, 2020 at 8:56 PM Tong Sun > <suntong...@users.sourceforge.net> wrote: > > > > Hold on, I just upload the source file, you meant the binary file? > > Can I do that? > > If you upload easygen_4.1.0-1_amd64.changes to mentors, I can run my > development version against it. > > Dput/Dupload will automatically include any sources or installation > packages (deb) that might have triggered the tag. According to this > commit, both debs and source must be present for the tag to trigger: > > > https://salsa.debian.org/lintian/lintian/commit/e59e44ec0d648b66b30ab52c08f3def9224c7373
Hi Felix, I didn't get what you were talking about the first time I read above, and only after I asked almost the same question again, did I fully understand it, when you replied: > You can build a full package with 'debuild -sa'. Sorry about that, I never take such "detour" before as I always build either source or the binary package. Hope that I hadn't wore your patient off. Now I don't need to upload the easygen's _amd64.changes file anymore, because when I run `lintian -EvIL +pedantic` against it myself, I don't see the `statically-linked-binary` error any more myself either. So here is the summary of the situation, - as you put before, both debs and source must be present for the tag to trigger. I.e., when only building the source AND the binary file, the `statically-linked-binary` error will not show. - if only building binary, then the error will show. I.e., feel free to close it, if you think it is no longer a problem. i.e., we can overlook the building binary case. Thanks
