Michael Hudson-Doyle writes:
> Makes sense to me, I'd be happy to upload that change to experimental.
Great, thanks!
> What's the timeframe for gccgo-7 getting into unstable? Just waiting for
> buster development to open?
Presumably; I'm not aware of another reason to hold off. (An official
7
Makes sense to me, I'd be happy to upload that change to experimental.
What's the timeframe for gccgo-7 getting into unstable? Just waiting for
buster development to open?
On 13 May 2017 at 03:13, Aaron M. Ucko wrote:
> Package: gccgo-go
> Version: 2:1.8~1
> Severity: important
>
> Could you ple
Package: gccgo-go
Version: 2:1.8~1
Severity: important
Could you please switch gccgo-go's 1.8 series to wrap gccgo-7 rather than
gccgo-6, so code that needs Go 1.8.x user packages but not necessarily
Google's compiler can simply Build-Depend: gccgo-any (>= 2:1.8~)?
This change will be helpful for
3 matches
Mail list logo
