[Pkg-chromium-maint] Bug#748867: patch: Let's fix this by adding APIKEY

Osamu Aoki osamu at debian.org
Sat Oct 18 13:26:34 UTC 2014


On Sat, Oct 18, 2014 at 01:13:39PM +0200, Giuseppe Iuculano wrote:
> Il 18/10/2014 11:12, Osamu Aoki ha scritto:
> > I understand Mike's (long term) plan to separate APIKEY to different
> > package.  But, at least for now, can we have functioning package in
> > testing without reading and manually tweaking the system?  Any reason
> > not to update this?  Then with next package, Mike can do whatever as
> > long as it is coordinated with ftp-master for the new package.
> Oh well, so if you understand Mike's (long term) plan, 

This refers to https://bugs.debian.org/748867#122 by Mike:
| This has been the plan all along, I just haven't gotten to it yet
| since the plan is a separate apikeys package and that's going to
| involve a trip through NEW.

NEW process takes *long time* and it is not good idea at this time for
most DDs as I understand.  But it mat\y be different for Mike.

> can you please make me understand why people should change APIKEY? 

Did I say this? I thought this patch was just following workaround
mentioned in this bug report thread and used old APIKEYs shipped with

> And so we have chromium broken for a month only for the very small
> number of people that will change APIKEY?

I have 2 systems.  One somehow survived through this package transition.
The other causing problem. I upgraded at different timing.  The system
which required this API key was the one which I removed
~/.config/chromium removed after facing the breakage.
I have not investigated much.

If I was the unfortunate few, then I am OK with the package as they are
as long as it works for people upgrading from wheezy.

(If API key removal was caused by the licensing issue, then it should be
documented somewhere.)



More information about the Pkg-chromium-maint mailing list