Skip to content
This repository was archived by the owner on Jun 21, 2018. It is now read-only.

Conversation

@l2dy
Copy link
Contributor

@l2dy l2dy commented Apr 18, 2017

No description provided.

@l2dy l2dy changed the title Use golang from jessie-backports apt: Pull golang from jessie-backports Apr 18, 2017
@daurnimator
Copy link
Member

What about the golang package itself?

I think I'd prefer you spelled out the relevant packages rather than using a wildcard.

@l2dy
Copy link
Contributor Author

l2dy commented Apr 18, 2017

golang is not in https://github.com/hashbang/shell-etc/blob/master/packages.txt.

$ dpkg -l | grep golang
ii  golang-go                             2:1.3.3-1                            amd64        Go programming language compiler
ii  golang-go-linux-amd64                 2:1.3.3-1                            amd64        Go standard library compiled for linux_amd64
ii  golang-src                            2:1.3.3-1                            amd64        Go programming language compiler - source files

@daurnimator
Copy link
Member

I thought it might matter if some package brought in 'golang' as a dependency?

@l2dy
Copy link
Contributor Author

l2dy commented Apr 18, 2017

Updated. I still prefer using a wildcard.

@KellerFuchs
Copy link
Member

I think having the wildcard in that case makes sense; otherwise, we would potentially have an inconsistent mix of Go 1.7 and 1.3.

@KellerFuchs
Copy link
Member

KellerFuchs commented Apr 24, 2017

@l2dy Sorry this is kinda stalled right now, as I've not been available to deal with some issues related to package deployments.
I will be getting to this as soon as I can, though. :)

There is nothing you need to do, just letting you know I didn't forget about this.

@lrvick lrvick self-assigned this May 13, 2017
@lrvick lrvick self-requested a review May 13, 2017 07:42
@lrvick
Copy link
Member

lrvick commented May 13, 2017

@KellerFuchs We are good to merge this now yeah?

@KellerFuchs
Copy link
Member

@lrvick Should be.

@l2dy
Copy link
Contributor Author

l2dy commented Jun 18, 2017

Should this be closed in favor of update to Debian 9 Stretch?

@RyanSquared
Copy link
Member

Depends on when we plan on updating. I didn't even know stretch was ready until last night.

@ghost
Copy link

ghost commented Aug 11, 2017

Am I correct in assuming that any upgrade to Stretch is waiting on our local testing setup (I think the issue # is hashbang/shell-server#43?), so we should merge this now rather than waiting on local testing being ready Soon(tm)?

@RyanSquared
Copy link
Member

Am I correct in assuming that any upgrade to Stretch is waiting on our local testing setup

Pretty much everything is.

so we should merge this now rather than waiting on local testing being ready Soon(tm)?

I dunno. Some people want to wait until we're fully migrated to continue things that aren't security-critical.

@l2dy
Copy link
Contributor Author

l2dy commented Oct 10, 2017

I'll just install go in $HOME.

@l2dy l2dy closed this Oct 10, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants