Re: [gentoo-user] Can't fetch www-plugins/chrome-binary-plugins
On Wednesday, March 11, 2015 6:52:39 AM Mick wrote: On Wednesday 11 Mar 2015 06:42:35 Fernando Rodriguez wrote: On Wednesday, March 11, 2015 6:20:25 AM Mick wrote: On Tuesday 10 Mar 2015 23:33:33 Fernando Rodriguez wrote: Google only keeps the latest versions so that ebuild is usually only good for a short while after it gets marked stable. Just keyword the unstable package. So users of the stable package have to be really fast, or lucky? Right. Or put emerge www-plugins/chrome-binary-plugins --fetchonly on a cron job to fetch it as soon as it's stable. I googled for it and downloaded it from a mirror. Am I correct that if the hash is not right the ebuild will complain about it, or will I end up installing a suspect package? Yes. If you haven't found it... https://drive.google.com/file/d/0BzPt9N2PyrQGZTg5YXZYTTAzbms/view?usp=sharing -- Fernando Rodriguez
Re: [gentoo-user] Can't fetch www-plugins/chrome-binary-plugins
On Thu, Mar 12, 2015 at 7:08 PM, Mick michaelkintz...@gmail.com wrote: On Thursday 12 Mar 2015 22:46:14 Mike Gilbert wrote: On Wed, Mar 11, 2015 at 7:38 AM, Rich Freeman ri...@gentoo.org wrote: On Wed, Mar 11, 2015 at 7:05 AM, Neil Bothwick n...@digimed.co.uk wrote: On Wed, 11 Mar 2015 06:20:25 +, Mick wrote: Google only keeps the latest versions so that ebuild is usually only good for a short while after it gets marked stable. Just keyword the unstable package. So users of the stable package have to be really fast, or lucky? Gentoo should keep a copy in its mirrors for as long as a current ebuild needs it (unless the package is fetch-restricted). Chrome is mirror-restricted, because of: 9.2 Subject to section 1.2, you may not (and you may not permit anyone else to) copy, modify, create a derivative work of, reverse engineer, decompile or otherwise attempt to extract the source code of the Software or any part thereof, unless this is expressly permitted or required by law, or unless you have been specifically told that you may do so by Google, in writing. chrome-binary-plugins is not free software, or open source. There is little Gentoo can do when they keep changing the URL/hash without warning. You can file a bug to get the ebuild updated though. As the person doing the bumps, I would actually prefer that people ping me in IRC before creating a bug report. It's annoying to have to close a bug report for an issue that occurs quite frequently. Don't mind doing this if it will help - what's your nick? floppym -- same as my email address.
Re: [gentoo-user] Can't fetch www-plugins/chrome-binary-plugins
On Wed, Mar 11, 2015 at 7:38 AM, Rich Freeman ri...@gentoo.org wrote: On Wed, Mar 11, 2015 at 7:05 AM, Neil Bothwick n...@digimed.co.uk wrote: On Wed, 11 Mar 2015 06:20:25 +, Mick wrote: Google only keeps the latest versions so that ebuild is usually only good for a short while after it gets marked stable. Just keyword the unstable package. So users of the stable package have to be really fast, or lucky? Gentoo should keep a copy in its mirrors for as long as a current ebuild needs it (unless the package is fetch-restricted). Chrome is mirror-restricted, because of: 9.2 Subject to section 1.2, you may not (and you may not permit anyone else to) copy, modify, create a derivative work of, reverse engineer, decompile or otherwise attempt to extract the source code of the Software or any part thereof, unless this is expressly permitted or required by law, or unless you have been specifically told that you may do so by Google, in writing. chrome-binary-plugins is not free software, or open source. There is little Gentoo can do when they keep changing the URL/hash without warning. You can file a bug to get the ebuild updated though. As the person doing the bumps, I would actually prefer that people ping me in IRC before creating a bug report. It's annoying to have to close a bug report for an issue that occurs quite frequently.
Re: [gentoo-user] Can't fetch www-plugins/chrome-binary-plugins
On Thursday 12 Mar 2015 22:46:14 Mike Gilbert wrote: On Wed, Mar 11, 2015 at 7:38 AM, Rich Freeman ri...@gentoo.org wrote: On Wed, Mar 11, 2015 at 7:05 AM, Neil Bothwick n...@digimed.co.uk wrote: On Wed, 11 Mar 2015 06:20:25 +, Mick wrote: Google only keeps the latest versions so that ebuild is usually only good for a short while after it gets marked stable. Just keyword the unstable package. So users of the stable package have to be really fast, or lucky? Gentoo should keep a copy in its mirrors for as long as a current ebuild needs it (unless the package is fetch-restricted). Chrome is mirror-restricted, because of: 9.2 Subject to section 1.2, you may not (and you may not permit anyone else to) copy, modify, create a derivative work of, reverse engineer, decompile or otherwise attempt to extract the source code of the Software or any part thereof, unless this is expressly permitted or required by law, or unless you have been specifically told that you may do so by Google, in writing. chrome-binary-plugins is not free software, or open source. There is little Gentoo can do when they keep changing the URL/hash without warning. You can file a bug to get the ebuild updated though. As the person doing the bumps, I would actually prefer that people ping me in IRC before creating a bug report. It's annoying to have to close a bug report for an issue that occurs quite frequently. Don't mind doing this if it will help - what's your nick? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Can't fetch www-plugins/chrome-binary-plugins
On Tuesday 10 Mar 2015 23:33:33 Fernando Rodriguez wrote: On Tuesday, March 10, 2015 11:19:34 PM Mick wrote: On Tuesday 10 Mar 2015 22:45:28 Dale wrote: Mick wrote: This is the second machine I am getting a 404 in as many weeks with this package. Is it a known problem, or am I the only one suffering from this? Emerging (1 of 8) www-plugins/chrome-binary- plugins-41.0.2272.76_p1::gentoo * Fetching files in the background. To view fetch progress, run * `tail -f /var/log/emerge-fetch.log` in another terminal. Downloading 'https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stabl e/go ogle-chrome-stable_41.0.2272.76-1_amd64.deb' --2015-03-10 22:02:09-- https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable /goo gle-chrome-stable_41.0.2272.76-1_amd64.deb Resolving dl.google.com... 216.58.210.46, 2a00:1450:4009:800::200e Connecting to dl.google.com|216.58.210.46|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2015-03-10 22:02:09 ERROR 404: Not Found. !!! Couldn't download 'google-chrome-stable_41.0.2272.76-1_amd64.deb'. Aborting. * Fetch failed for 'www-plugins/chrome-binary-plugins-41.0.2272.76_p1', Log file: * '/var/tmp/portage/www-plugins/chrome-binary- plugins-41.0.2272.76_p1/temp/build.log' * Please wait 24 hours and sync your portage tree before reporting fetch failures. I don't use the package but tried to fetch it to test. Same failure here too. Can you force it to use a different mirror or is it google's and that's it? Dale :-) :-) Thanks Dale, I'm guessing google is the only repo, at least that's the SRC_URI coded in the ebuild. Google only keeps the latest versions so that ebuild is usually only good for a short while after it gets marked stable. Just keyword the unstable package. So users of the stable package have to be really fast, or lucky? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Can't fetch www-plugins/chrome-binary-plugins
On Wednesday 11 Mar 2015 06:42:35 Fernando Rodriguez wrote: On Wednesday, March 11, 2015 6:20:25 AM Mick wrote: On Tuesday 10 Mar 2015 23:33:33 Fernando Rodriguez wrote: Google only keeps the latest versions so that ebuild is usually only good for a short while after it gets marked stable. Just keyword the unstable package. So users of the stable package have to be really fast, or lucky? Right. Or put emerge www-plugins/chrome-binary-plugins --fetchonly on a cron job to fetch it as soon as it's stable. I googled for it and downloaded it from a mirror. Am I correct that if the hash is not right the ebuild will complain about it, or will I end up installing a suspect package? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Can't fetch www-plugins/chrome-binary-plugins
On Wednesday, March 11, 2015 6:20:25 AM Mick wrote: On Tuesday 10 Mar 2015 23:33:33 Fernando Rodriguez wrote: On Tuesday, March 10, 2015 11:19:34 PM Mick wrote: On Tuesday 10 Mar 2015 22:45:28 Dale wrote: Mick wrote: This is the second machine I am getting a 404 in as many weeks with this package. Is it a known problem, or am I the only one suffering from this? Emerging (1 of 8) www-plugins/chrome-binary- plugins-41.0.2272.76_p1::gentoo * Fetching files in the background. To view fetch progress, run * `tail -f /var/log/emerge-fetch.log` in another terminal. Downloading 'https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stabl e/go ogle-chrome-stable_41.0.2272.76-1_amd64.deb' --2015-03-10 22:02:09-- https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable /goo gle-chrome-stable_41.0.2272.76-1_amd64.deb Resolving dl.google.com... 216.58.210.46, 2a00:1450:4009:800::200e Connecting to dl.google.com|216.58.210.46|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2015-03-10 22:02:09 ERROR 404: Not Found. !!! Couldn't download 'google-chrome-stable_41.0.2272.76-1_amd64.deb'. Aborting. * Fetch failed for 'www-plugins/chrome-binary-plugins-41.0.2272.76_p1', Log file: * '/var/tmp/portage/www-plugins/chrome-binary- plugins-41.0.2272.76_p1/temp/build.log' * Please wait 24 hours and sync your portage tree before reporting fetch failures. I don't use the package but tried to fetch it to test. Same failure here too. Can you force it to use a different mirror or is it google's and that's it? Dale :-) :-) Thanks Dale, I'm guessing google is the only repo, at least that's the SRC_URI coded in the ebuild. Google only keeps the latest versions so that ebuild is usually only good for a short while after it gets marked stable. Just keyword the unstable package. So users of the stable package have to be really fast, or lucky? Right. Or put emerge www-plugins/chrome-binary-plugins --fetchonly on a cron job to fetch it as soon as it's stable. -- Fernando Rodriguez signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Can't fetch www-plugins/chrome-binary-plugins
On Wed, Mar 11, 2015 at 7:05 AM, Neil Bothwick n...@digimed.co.uk wrote: On Wed, 11 Mar 2015 06:20:25 +, Mick wrote: Google only keeps the latest versions so that ebuild is usually only good for a short while after it gets marked stable. Just keyword the unstable package. So users of the stable package have to be really fast, or lucky? Gentoo should keep a copy in its mirrors for as long as a current ebuild needs it (unless the package is fetch-restricted). Chrome is mirror-restricted, because of: 9.2 Subject to section 1.2, you may not (and you may not permit anyone else to) copy, modify, create a derivative work of, reverse engineer, decompile or otherwise attempt to extract the source code of the Software or any part thereof, unless this is expressly permitted or required by law, or unless you have been specifically told that you may do so by Google, in writing. chrome-binary-plugins is not free software, or open source. There is little Gentoo can do when they keep changing the URL/hash without warning. You can file a bug to get the ebuild updated though. -- Rich
Re: [gentoo-user] Can't fetch www-plugins/chrome-binary-plugins
On Wed, 11 Mar 2015 06:20:25 +, Mick wrote: Google only keeps the latest versions so that ebuild is usually only good for a short while after it gets marked stable. Just keyword the unstable package. So users of the stable package have to be really fast, or lucky? Gentoo should keep a copy in its mirrors for as long as a current ebuild needs it (unless the package is fetch-restricted). -- Neil Bothwick A TRUE Klingon warrior does not comment his code! pgpUk46ri_kVt.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Can't fetch www-plugins/chrome-binary-plugins
On Wed, 11 March 2015, at 6:52 am, Mick michaelkintz...@gmail.com wrote: ... I googled for it and downloaded it from a mirror. Am I correct that if the hash is not right the ebuild will complain about it, Yes.
Re: [gentoo-user] Can't fetch www-plugins/chrome-binary-plugins
Mick wrote: This is the second machine I am getting a 404 in as many weeks with this package. Is it a known problem, or am I the only one suffering from this? Emerging (1 of 8) www-plugins/chrome-binary- plugins-41.0.2272.76_p1::gentoo * Fetching files in the background. To view fetch progress, run * `tail -f /var/log/emerge-fetch.log` in another terminal. Downloading 'https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_41.0.2272.76-1_amd64.deb' --2015-03-10 22:02:09-- https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_41.0.2272.76-1_amd64.deb Resolving dl.google.com... 216.58.210.46, 2a00:1450:4009:800::200e Connecting to dl.google.com|216.58.210.46|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2015-03-10 22:02:09 ERROR 404: Not Found. !!! Couldn't download 'google-chrome-stable_41.0.2272.76-1_amd64.deb'. Aborting. * Fetch failed for 'www-plugins/chrome-binary-plugins-41.0.2272.76_p1', Log file: * '/var/tmp/portage/www-plugins/chrome-binary- plugins-41.0.2272.76_p1/temp/build.log' * Please wait 24 hours and sync your portage tree before reporting fetch failures. I don't use the package but tried to fetch it to test. Same failure here too. Can you force it to use a different mirror or is it google's and that's it? Dale :-) :-)
Re: [gentoo-user] Can't fetch www-plugins/chrome-binary-plugins
On Tuesday 10 Mar 2015 22:45:28 Dale wrote: Mick wrote: This is the second machine I am getting a 404 in as many weeks with this package. Is it a known problem, or am I the only one suffering from this? Emerging (1 of 8) www-plugins/chrome-binary- plugins-41.0.2272.76_p1::gentoo * Fetching files in the background. To view fetch progress, run * `tail -f /var/log/emerge-fetch.log` in another terminal. Downloading 'https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/go ogle-chrome-stable_41.0.2272.76-1_amd64.deb' --2015-03-10 22:02:09-- https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/goo gle-chrome-stable_41.0.2272.76-1_amd64.deb Resolving dl.google.com... 216.58.210.46, 2a00:1450:4009:800::200e Connecting to dl.google.com|216.58.210.46|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2015-03-10 22:02:09 ERROR 404: Not Found. !!! Couldn't download 'google-chrome-stable_41.0.2272.76-1_amd64.deb'. Aborting. * Fetch failed for 'www-plugins/chrome-binary-plugins-41.0.2272.76_p1', Log file: * '/var/tmp/portage/www-plugins/chrome-binary- plugins-41.0.2272.76_p1/temp/build.log' * Please wait 24 hours and sync your portage tree before reporting fetch failures. I don't use the package but tried to fetch it to test. Same failure here too. Can you force it to use a different mirror or is it google's and that's it? Dale :-) :-) Thanks Dale, I'm guessing google is the only repo, at least that's the SRC_URI coded in the ebuild. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Can't fetch www-plugins/chrome-binary-plugins
On Tuesday, March 10, 2015 11:19:34 PM Mick wrote: On Tuesday 10 Mar 2015 22:45:28 Dale wrote: Mick wrote: This is the second machine I am getting a 404 in as many weeks with this package. Is it a known problem, or am I the only one suffering from this? Emerging (1 of 8) www-plugins/chrome-binary- plugins-41.0.2272.76_p1::gentoo * Fetching files in the background. To view fetch progress, run * `tail -f /var/log/emerge-fetch.log` in another terminal. Downloading 'https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/go ogle-chrome-stable_41.0.2272.76-1_amd64.deb' --2015-03-10 22:02:09-- https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/goo gle-chrome-stable_41.0.2272.76-1_amd64.deb Resolving dl.google.com... 216.58.210.46, 2a00:1450:4009:800::200e Connecting to dl.google.com|216.58.210.46|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2015-03-10 22:02:09 ERROR 404: Not Found. !!! Couldn't download 'google-chrome-stable_41.0.2272.76-1_amd64.deb'. Aborting. * Fetch failed for 'www-plugins/chrome-binary-plugins-41.0.2272.76_p1', Log file: * '/var/tmp/portage/www-plugins/chrome-binary- plugins-41.0.2272.76_p1/temp/build.log' * Please wait 24 hours and sync your portage tree before reporting fetch failures. I don't use the package but tried to fetch it to test. Same failure here too. Can you force it to use a different mirror or is it google's and that's it? Dale :-) :-) Thanks Dale, I'm guessing google is the only repo, at least that's the SRC_URI coded in the ebuild. Google only keeps the latest versions so that ebuild is usually only good for a short while after it gets marked stable. Just keyword the unstable package. -- Fernando Rodriguez signature.asc Description: This is a digitally signed message part.
