Wow, I'm not sure that package gets much from using dh-golang at all?
But I think the problem is the " --builddirectory=_build" in the
default target, somehow that needs to get funnelled into the right
place. Will have a look.

On 19 April 2016 at 09:05, Michael Stapelberg <stapelb...@debian.org> wrote:
> Michael, can you take a look at this issue please?
>
> On Mon, Apr 18, 2016 at 12:45 AM, Dmitry Smirnov <only...@debian.org> wrote:
>>
>> Package: dh-golang
>> Version: 1.15
>> Severity: serious
>>
>> Recent upload of "rkt" was rejected
>>
>>     rkt_1.4.0+dfsg-1_amd64.deb: Built-Using refers to non-existing source
>> package apt (= 1.0.9.10)
>>
>> due to rubbish in Built-Using field:
>>
>>     apt (= 1.0.9.10), apt (= 1.0.10.2), apt (= 1.2.10)
>>
>> Also invocation of dh-golang logged the following:
>>
>> ~~~~
>>    dh_golang -O--buildsystem=golang -O--builddirectory=_build
>> can't load package: package github.com/coreos/rkt/api/v1alpha: cannot find
>> package "github.com/coreos/rkt/api/v1alpha" in any of:
>>         /usr/lib/go/src/github.com/coreos/rkt/api/v1alpha (from $GOROOT)
>>
>> /build/rkt-1.4.0+dfsg/obj-x86_64-linux-gnu/src/github.com/coreos/rkt/api/v1alpha
>> (from $GOPATH)
>> can't load package: package github.com/coreos/rkt/rkt: cannot find package
>> "github.com/coreos/rkt/rkt" in any of:
>>         /usr/lib/go/src/github.com/coreos/rkt/rkt (from $GOROOT)
>>
>> /build/rkt-1.4.0+dfsg/obj-x86_64-linux-gnu/src/github.com/coreos/rkt/rkt
>> (from $GOPATH)
>> can't load package: package .: no buildable Go source files in
>> /build/rkt-1.4.0+dfsg
>> can't load package: package .: no buildable Go source files in
>> /build/rkt-1.4.0+dfsg
>> dpkg-query: error: --search needs at least one file name pattern argument
>>
>> Use --help for help about querying packages.
>> ~~~~
>>
>> This is regression from "dh-golang" v1.12.
>>
>> Please investigate.
>>
>> --
>> All the best,
>>  Dmitry Smirnov
>>  GPG key : 4096R/53968D1B
>>
>> ---
>>
>> Truth never damages a cause that is just.
>>         -- Mahatma Gandhi
>
>
>
>
> --
> Best regards,
> Michael

Reply via email to