Hi Tong,
On Wed, Jan 1, 2020 at 7:13 PM Tong Sun
wrote:
>
> To be honest, #947630 seems to be tough one to find a solution. . .
I could not reproduce the bug and closed it:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947630#15
> I have a feeling that it got to be the way that *I use
On Wed, Jan 1, 2020 at 7:21 PM Dmitry Smirnov wrote:
>
> On Thursday, 2 January 2020 11:07:21 AM AEDT Felix Lechner wrote:
> > Does that mean we can close #947630?
>
> Frankly I don't know... I've seen the warning on golang packages but some
> time ago it disappeared after upgrading Lintian so I r
On Thursday, 2 January 2020 11:07:21 AM AEDT Felix Lechner wrote:
> Does that mean we can close #947630?
Frankly I don't know... I've seen the warning on golang packages but some
time ago it disappeared after upgrading Lintian so I reckon the bug might
have been already fixed in which case it wo
Hi Dmitry & Tong,
On Wed, Jan 1, 2020 at 3:58 PM Dmitry Smirnov wrote:
>
> unused-override statically-linked-binary
Does that mean we can close #947630?
Kind regards
Felix Lechner
On Thursday, 2 January 2020 10:34:25 AM AEDT Tong Sun wrote:
> Could you reviewing/sponsoring this please?
Uploaded, thanks.
FYI lintian produced the following warning:
unused-override statically-linked-binary
which probably suggests that you might be using outdated lintian.
I recommend to
Hi,
I've fixed all required by Dmitry, and updated the upstream and salsa repo at:
https://salsa.debian.org/go-team/packages/ffcvt
The package was tested on both gbp and sbuild. It's also lintian-clean.
http://paste.debian.net/1123922/
Could you reviewing/sponsoring this please?
The source
Hi Tong,
On Wed, Jan 1, 2020 at 12:09 PM Tong Sun
wrote:
>
> is there any
> builtin environment variable that can help me finding them easily, and
> the method being simple and portable enough so that I can apply to any
> other of my packages?
Good question but unfortunately, I cannot help you w
On Wed, Jan 1, 2020 at 1:09 PM Felix Lechner wrote:
>
> Hi Tong,
>
> On Wed, Jan 1, 2020 at 9:28 AM Tong Sun
> wrote:
> >
> > > > ./test-all.sh: 7: ../ffcvt: not found
>
> In d/rules, you include 'test', which supplies test/test-all.sh, but
> the missing file is ./ffcvt in your base directory. Th
Hi Tong,
On Wed, Jan 1, 2020 at 9:28 AM Tong Sun
wrote:
>
> > > ./test-all.sh: 7: ../ffcvt: not found
In d/rules, you include 'test', which supplies test/test-all.sh, but
the missing file is ./ffcvt in your base directory. This command will
copy all your files into the BUILDDIR:
export DH_G
On Wed, Jan 1, 2020 at 12:08 PM Tong Sun
wrote:
>
> Hi,
>
> This is how I do self test with my go project:
>
> ( cd test; ./test-all.sh; )
>
> https://salsa.debian.org/go-team/packages/ffcvt/commit/330c42c96ef962e0d630c5420a92a7971480c5e0
>
> and in test-all.sh I call `../ffcvt` as it is where `go
On Wed, Jan 1, 2020 at 12:22 PM Felix Lechner
wrote:
>
> Hi Tong,
>
> On Wed, Jan 1, 2020 at 9:09 AM Tong Sun
> wrote:
> >
> > ./test-all.sh: 7: ../ffcvt: not found
>
> Is it the same problem? You may be better off switching in d/rules to:
>
> export DH_GOLANG_INSTALL_EXTRA := 1
No, I put it
Hi Tong,
On Wed, Jan 1, 2020 at 9:09 AM Tong Sun
wrote:
>
> ./test-all.sh: 7: ../ffcvt: not found
Is it the same problem? You may be better off switching in d/rules to:
export DH_GOLANG_INSTALL_EXTRA := 1
Kind regards
Felix Lechner
Hi,
This is how I do self test with my go project:
( cd test; ./test-all.sh; )
https://salsa.debian.org/go-team/packages/ffcvt/commit/330c42c96ef962e0d630c5420a92a7971480c5e0
and in test-all.sh I call `../ffcvt` as it is where `go build` put my
compile binary:
https://salsa.debian.org/go-team/
On Tue, Dec 31, 2019 at 9:31 PM Felix Lechner
wrote:
>
> Hi Tong,
>
> On Tue, Dec 31, 2019 at 4:11 PM Tong Sun
> wrote:
> >
> > sh: 0: Can't open ffcvt_cli.sh
>
> The file is missing from the Go workspace in BUILDDIR. You can use one
> of these statements in d/rules to copy the files:
>
> exp
14 matches
Mail list logo
