Re: Bug#658415: [BTS#658415] templates://golang-weekly/{golang-weekly-tools.templates} : Final update for English review

[Justin B Rye <jbr@edlug.org.uk>]

Ondřej Surý wrote:
> Justin B Rye <jbr@edlug.org.uk> wrote:
>> Jonathan Nieder wrote:
>>> Shouldn't this say "Go programming language compiler (weekly snapshot)"
>>> or something similar to distinguish it from the main golang package?
>>
>> That's what I thought until I discovered that the only golang packages
>> available for the golang metapackage to pull in are the -weekly ones.
> 
> No.
> 
> packages.qa.debian.org/g/golang.html

I don't see what you're pointing at there; .qa. pages don't list which
individual binary packages exist in which release, do they?  For that
I went to the packages.debian.org listings, and when I checked a
couple of weeks ago those seemed to say that the golang-weekly-*
binary packages were the only ones available to provide golang-*.  But
that's not right... I don't know what went wrong there.

Okay, in that case it's the golang packages that should have the
revised version of the boilerplate advertising the Go language; the
golang-weekly packages should have nothing but warnings, because 
people who don't already know what Go is shouldn't be going anywhere
near them.

[...]
>> Bear in mind that these packages are already in Testing; if the idea
>> is that some particular individual weekly snapshot is going to end up
>> as the only version of golang released with Wheezy, the text above
>> won't make much sense.
> 
> No, they are not in the Testing:
> http://packages.qa.debian.org/g/golang-weekly.html

Now I'm very confused; how did my search for golang-weekly on
packages.debian.org show me packages in Wheezy?  Was I just doing my
search too late at night?

Oh, wait: it did migrate into Wheezy a couple of times last year, but
it was removed.  Was I seeing leftovers in obscure architectures?

>>> By the way, why is this a separate source package instead of being
>>> called golang in experimental?
>>
>> Or to put it another way, if the upstream versions of the last three
>> golang-weekly releases are 2011.09.07, 2011.09.21, and 2012.01.27, why
>> is it called -weekly?
> 
> Because upstream do weekly releases, but I upload -weekly release when
> I have a time.  I need to automatize the process, but it goes back to
> "when I have a time".

Well, too late now, but golang-snapshot might have been less
misleading.
-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package