On Mon, Oct 13, 2014 at 3:40 PM, Romain Francoise wrote:
> On Mon, Oct 13, 2014 at 03:17:01PM -0400, Michael Gilbert wrote:
>> Again, that version is a rewrite package from scratch, so nothing was
>> specifically removed. Anything missing simply hasn't been implemented
>> yet.
>
> Then it was ina
On Mon, Oct 13, 2014 at 03:17:01PM -0400, Michael Gilbert wrote:
> Again, that version is a rewrite package from scratch, so nothing was
> specifically removed. Anything missing simply hasn't been implemented
> yet.
Then it was inappropriate to upload this to unstable. People who use
unstable exp
Il 13/10/2014 20:13, Michael Gilbert ha scritto:
> There will be no reason for users to generate keys. The Debian keys
> will be used.
Then I really don't understand why you removed the keys in debian/rules
in 37.0.2062.120-4...
Cheers,
Giuseppe
--
To UNSUBSCRIBE, email to debian-bugs-dist-re
On Mon, Oct 13, 2014 at 3:08 PM, Giuseppe Iuculano wrote:
> Il 13/10/2014 20:13, Michael Gilbert ha scritto:
>> There will be no reason for users to generate keys. The Debian keys
>> will be used.
>
> Then I really don't understand why you removed the keys in debian/rules
> in 37.0.2062.120-4...
On Mon, Oct 13, 2014 at 11:18 AM, Giuseppe Iuculano wrote:
> On 13/10/2014 03:09, Michael Gilbert wrote:
>> This has been the plan all along
>
> Could I ask you where it was discussed?
I had not mentioned it, but it is an one obvious motivation for the
/etc/chromium.d change (pepperflash being ano
On 13/10/2014 03:09, Michael Gilbert wrote:
> This has been the plan all along
Could I ask you where it was discussed? And why you decided to force
users to create their keys? What are wrong with the Debian keys?
Cheers,
Giuseppe
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debia
Am Montag, 13. Oktober 2014, 08:52:45 schrieb Dariusz Dwornikowski:
> > Another option is setting the Google API Keys in the environment [1].
> >
> > So, it should be enough to create a file at /etc/chromium.d that
> > exports the keys. (/usr/bin/chromium sources all files on that dir)
> >
> > Th
> Another option is setting the Google API Keys in the environment [1].
>
> So, it should be enough to create a file at /etc/chromium.d that
> exports the keys. (/usr/bin/chromium sources all files on that dir)
>
> This works for me:
>
> $ cat /etc/chromium.d/googleapikeys
> export GOOGLE_API_K
On Sun, Oct 12, 2014 at 9:05 PM, Carlos Alberto Lopez Perez wrote:
> Another option is setting the Google API Keys in the environment [1].
>
> So, it should be enough to create a file at /etc/chromium.d that
> exports the keys. (/usr/bin/chromium sources all files on that dir)
This has been the pl
Another option is setting the Google API Keys in the environment [1].
So, it should be enough to create a file at /etc/chromium.d that
exports the keys. (/usr/bin/chromium sources all files on that dir)
This works for me:
$ cat /etc/chromium.d/googleapikeys
export GOOGLE_API_KEY="AIzaSyCkfPOPZX
Hello,
The attached patch to debian/rules restores the ability to sign-in to
Chromium, by re-adding the Debian Google API keys that used to be included
in older Chromium packaging debian/rules.
The patch also resolves the crash that occurred on sign-in with Chromium
built against the system pr
11 matches
Mail list logo
