I am sorry, I copied the wrong bug number and inadvertently closed
this bug by mistake.
My apologies!
It has now been reopened.
Thanks,
Anthony
On 21 August 2017 at 14:11, Michael Hudson-Doyle
wrote:
> On 22 August 2017 at 01:17, Paul R. Tagliamonte wrote:
>> Why not use the import path I so lovingly put in the generated control
>> file for times like these?
>
> That's still missing from heaps of packages, isn't it? I know someone who
>
On 22 August 2017 at 01:17, Paul R. Tagliamonte wrote:
> Why not use the import path I so lovingly put in the generated control
> file for times like these?
>
That's still missing from heaps of packages, isn't it? I know someone who
likes writing scripts to fix lots of golang packages at once...
Hi Paul,
On Mon, Aug 21, 2017 at 3:17 PM, Paul R. Tagliamonte wrote:
> Why not use the import path I so lovingly put in the generated control file
> for times like these?
This would probably be even better, indeed:
$ grep-dctrl -X -FGo-Import-Path github.com/onsi/ginkgo -sBinary
/var/lib/apt/lis
Why not use the import path I so lovingly put in the generated control file
for times like these?
On Aug 21, 2017 9:12 AM, "Balint Reczey"
wrote:
> Package: dh-make-golang
> Version: 0.0~git20170703.0.5eaf198-2
> Severity: wishlist
>
> Dead Maintainer,
>
> When looking for packaged build-depende
Package: dh-make-golang
Version: 0.0~git20170703.0.5eaf198-2
Severity: wishlist
Dead Maintainer,
When looking for packaged build-dependencies the vendor's path
(github.com/onsi/ginkgo) is converted using the default go library
naming scheme
(to golang-github-onsi-ginkgo-dev) which package may not
6 matches
Mail list logo
