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

Vincent Bernat bernat at debian.org
Sat Oct 18 09:36:57 UTC 2014

 ❦ 18 octobre 2014 18:12 +0900, Osamu Aoki <osamu at debian.org> :

> We are reaching closer to freeze.  This -2 package is missing APIKEY
> still and pushed almost immediately to testing archive breaking not just
> unstable but *tesing* systems.
> I have no idea why urgency=medium package takes only one day to migrate
> to testing.  I have no idea why the same trick of immediate push to
> testing is not used to fix this situation since fix seems to be known
> for 5 days. https://bugs.debian.org/748867#117

This is because the release team bypassed the regular delay (due to CVE
fixed in -1 and I suppose because of the importance of the bugs fixed by

> I guess something much more urgent is holding Mike to fix this.  Can
> someone NMU this package after applying and checking this patch, if Mike
> is not available?

I think that Mike is the only member of the Chromium team now. I also
think that your patch is the right way to move forward.

> At least adding this key fixed my system.  (I have removed old
> ~/.chromium directory before adding the API key.  If removal of this is
> required for upgrade, please consider adding entry to  debian/NEWS)

It is not needed. I have kept my .chromium without any issue (segfaulted
with -1 but worked unmodified with -2).
printk("Illegal format on cdrom.  Pester manufacturer.\n"); 
	2.2.16 /usr/src/linux/fs/isofs/inode.c
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-chromium-maint/attachments/20141018/218f0c13/attachment.sig>

More information about the Pkg-chromium-maint mailing list