Re: Dealing with 404 vendor packages

2020-03-15 Thread Shengjing Zhu
On Mon, Mar 16, 2020 at 2:21 AM Shengjing Zhu wrote: > > On Mon, Mar 16, 2020 at 2:03 AM Tong Sun wrote: > [...] > > > > I am more interested in how to move on and overcome the issue, rather > > than knowing why it stopped working. > > > > While you're going to package k8s.io/* stuff, and packagi

Re: Dealing with 404 vendor packages

2020-03-15 Thread Shengjing Zhu
On Mon, Mar 16, 2020 at 2:03 AM Tong Sun wrote: [...] > > I am more interested in how to move on and overcome the issue, rather > than knowing why it stopped working. > While you're going to package k8s.io/* stuff, and packaging k8s.io/* is not an essay task. So I think it's worth for you to figu

Re: Dealing with 404 vendor packages

2020-03-15 Thread Tong Sun
On Sun, Mar 15, 2020 at 1:46 PM Tong Sun wrote: > > On Sun, Mar 15, 2020 at 1:36 PM Shengjing Zhu wrote: > > > > On Mon, Mar 16, 2020 at 1:30 AM Tong Sun wrote: > > [...] > > > https://github.com/kubernetes/api/archive/vkubernetes-1.14.0-beta.0.tar.gz > > > 2020/03/15 13:05:42 Could not create a

Re: Dealing with 404 vendor packages

2020-03-15 Thread Tong Sun
On Sun, Mar 15, 2020 at 1:36 PM Shengjing Zhu wrote: > > On Mon, Mar 16, 2020 at 1:30 AM Tong Sun wrote: > [...] > > https://github.com/kubernetes/api/archive/vkubernetes-1.14.0-beta.0.tar.gz > > 2020/03/15 13:05:42 Could not create a tarball of the upstream source: > > 404 Not Found > > I think

Re: Dealing with 404 vendor packages

2020-03-15 Thread Shengjing Zhu
On Mon, Mar 16, 2020 at 1:30 AM Tong Sun wrote: [...] > https://github.com/kubernetes/api/archive/vkubernetes-1.14.0-beta.0.tar.gz > 2020/03/15 13:05:42 Could not create a tarball of the upstream source: > 404 Not Found I think the log is pretty clear. It has nothing to do with k8s.io/api 404, bu

Re: Dealing with 404 vendor packages

2020-03-15 Thread Tong Sun
Thanks Paul On Sun, Mar 15, 2020 at 12:59 PM Paul R. Tagliamonte wrote: > On Sun, Mar 15, 2020, 12:39 PM Tong Sun wrote: >> >> On Sun, Mar 15, 2020 at 2:24 AM Vincent Bernat wrote: >> > >> > ❦ 14 mars 2020 22:50 -04, Tong Sun : >> > >> > > How to deal with vendor packages that are 404 when ac

Re: Dealing with 404 vendor packages

2020-03-15 Thread Paul R. Tagliamonte
That url will be used by go get. A go get should determine the right path based on meta headers. It should import fine! What's the thing you're trying to do here? Paul On Sun, Mar 15, 2020, 12:39 PM Tong Sun wrote: > On Sun, Mar 15, 2020 at 2:24 AM Vincent Bernat wrote: > > > > ❦ 14 mars 20

Re: Dealing with 404 vendor packages

2020-03-15 Thread Tong Sun
On Sun, Mar 15, 2020 at 2:24 AM Vincent Bernat wrote: > > ❦ 14 mars 2020 22:50 -04, Tong Sun : > > > How to deal with vendor packages that are 404 when accessed? > > > > The docker cli has many k8s.io packages in its vendor folder that when > > I try to visit them, I'm getting 404. > > > > E.g. k

Re: Dealing with 404 vendor packages

2020-03-14 Thread Vincent Bernat
❦ 14 mars 2020 22:50 -04, Tong Sun : > How to deal with vendor packages that are 404 when accessed? > > The docker cli has many k8s.io packages in its vendor folder that when > I try to visit them, I'm getting 404. > > E.g. k8s.io/api is one of its vendor packages, but I'm getting 404 for it. >

Dealing with 404 vendor packages

2020-03-14 Thread Tong Sun
Hi, How to deal with vendor packages that are 404 when accessed? The docker cli has many k8s.io packages in its vendor folder that when I try to visit them, I'm getting 404. E.g. k8s.io/api is one of its vendor packages, but I'm getting 404 for it. (I do have found a repo: https://github.com/ku