1 |
On Wednesday, March 11, 2015 6:20:25 AM Mick wrote: |
2 |
> On Tuesday 10 Mar 2015 23:33:33 Fernando Rodriguez wrote: |
3 |
> > On Tuesday, March 10, 2015 11:19:34 PM Mick wrote: |
4 |
> > > On Tuesday 10 Mar 2015 22:45:28 Dale wrote: |
5 |
> > > > Mick wrote: |
6 |
> > > > > This is the second machine I am getting a 404 in as many weeks with |
7 |
> > > > > this package. Is it a known problem, or am I the only one suffering |
8 |
> > > > > from this? |
9 |
> > > > > |
10 |
> > > > >>>> Emerging (1 of 8) www-plugins/chrome-binary- |
11 |
> > > > > |
12 |
> > > > > plugins-41.0.2272.76_p1::gentoo |
13 |
> > > > > |
14 |
> > > > > * Fetching files in the background. To view fetch progress, run |
15 |
> > > > > * `tail -f /var/log/emerge-fetch.log` in another terminal. |
16 |
> > > > > |
17 |
> > > > >>>> Downloading |
18 |
> > > > |
19 |
> > > > 'https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stabl |
20 |
> > > > e/go ogle-chrome-stable_41.0.2272.76-1_amd64.deb' |
21 |
> > > > |
22 |
> > > > > --2015-03-10 22:02:09-- |
23 |
> > > > |
24 |
> > > > https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable |
25 |
> > > > /goo gle-chrome-stable_41.0.2272.76-1_amd64.deb |
26 |
> > > > |
27 |
> > > > > Resolving dl.google.com... 216.58.210.46, 2a00:1450:4009:800::200e |
28 |
> > > > > Connecting to dl.google.com|216.58.210.46|:443... connected. |
29 |
> > > > > HTTP request sent, awaiting response... 404 Not Found |
30 |
> > > > > 2015-03-10 22:02:09 ERROR 404: Not Found. |
31 |
> > > > > |
32 |
> > > > > !!! Couldn't download |
33 |
> > > > > 'google-chrome-stable_41.0.2272.76-1_amd64.deb'. Aborting. |
34 |
> > > > > |
35 |
> > > > > * Fetch failed for |
36 |
> > > > |
37 |
> > > > 'www-plugins/chrome-binary-plugins-41.0.2272.76_p1', Log |
38 |
> > > > |
39 |
> > > > > file: |
40 |
> > > > > * '/var/tmp/portage/www-plugins/chrome-binary- |
41 |
> > > > > |
42 |
> > > > > plugins-41.0.2272.76_p1/temp/build.log' |
43 |
> > > > > |
44 |
> > > > > * Please wait 24 hours and sync your portage tree before reporting |
45 |
> > |
46 |
> > fetch |
47 |
> > |
48 |
> > > > > failures. |
49 |
> > > > |
50 |
> > > > I don't use the package but tried to fetch it to test. Same failure |
51 |
> > > > here too. Can you force it to use a different mirror or is it |
52 |
> > > > google's and that's it? |
53 |
> > > > |
54 |
> > > > Dale |
55 |
> > > > |
56 |
> > > > :-) :-) |
57 |
> > > |
58 |
> > > Thanks Dale, I'm guessing google is the only repo, at least that's the |
59 |
> > |
60 |
> > SRC_URI |
61 |
> > |
62 |
> > > coded in the ebuild. |
63 |
> > |
64 |
> > Google only keeps the latest versions so that ebuild is usually only good |
65 |
> > for a short while after it gets marked stable. |
66 |
> > Just keyword the unstable package. |
67 |
> |
68 |
> So users of the stable package have to be really fast, or lucky? |
69 |
> |
70 |
> |
71 |
|
72 |
Right. Or put emerge www-plugins/chrome-binary-plugins --fetchonly on a cron |
73 |
job to fetch it as soon as it's stable. |
74 |
|
75 |
-- |
76 |
Fernando Rodriguez |