Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

fetch packages from github instead of google code #1059

Closed
peterbourgon opened this issue Jul 2, 2015 · 5 comments
Closed

fetch packages from github instead of google code #1059

peterbourgon opened this issue Jul 2, 2015 · 5 comments
Assignees
@inercia
Labels
chore
Milestone
1.1.0

Comments

@peterbourgon
Copy link
Contributor

Google Code is shutting down, and http://code.google.com/p/gopacket redirects to https://github.com/google/gopacket, so it's probably a good idea to update our imports.
@rade rade added the chore label Jul 2, 2015
@rade rade changed the title gopacket has apparently moved from Google Code fetch gopacket from github instead od google code Jul 2, 2015
@rade rade changed the title fetch gopacket from github instead od google code fetch gopacket from github instead of google code Jul 2, 2015
@inercia inercia self-assigned this Jul 2, 2015
@rade rade changed the title fetch gopacket from github instead of google code fetch packages from github instead of google code Jul 2, 2015
@rade
Copy link
Member

rade commented Jul 2, 2015

Same applies to go-bit and go.crypto.

@rade
Copy link
Member

rade commented Jul 2, 2015

go.crypto gh mirror

I cannot find a gh mirror for go-bit :( though there are a bunch of alternative implementations on gh.

@rade
Copy link
Member

rade commented Jul 2, 2015

Is this the same?

Looks like it.

@inercia inercia mentioned this issue Jul 2, 2015
Merged
@inercia
Copy link
Contributor

inercia commented Jul 2, 2015

It seems we have to use the crypto from golang.org/x/crypto...

@rade rade modified the milestone: current Jul 2, 2015
paulbellamy added a commit that referenced this issue Jul 2, 2015
@paulbellamy
Merge pull request #1060 from /issues/1059-remove-google-code-refs
3fd1465 
Remove all the imports from "code.google.com"
@rade rade mentioned this issue Jul 3, 2015
Closed
@rade
Copy link
Member

rade commented Jul 3, 2015

This issue rather failed to identify the problem, namely that the gopacket move actually breaks the build. Hence we now have #1060, since we need to fix that on the 1.0 branch, not just master.

@rade rade modified the milestones: current, 1.1.0 Jul 13, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@inercia inercia

Labels
chore
Projects
None yet
Milestone
1.1.0
Development

No branches or pull requests
3 participants
@rade @peterbourgon @inercia