686 lines
20 KiB
Text
686 lines
20 KiB
Text
# ChangeLog for www-client/google-chrome-unstable
|
|
# Copyright 1999-2016 Gentoo Foundation; Distributed under the GPL v2
|
|
# (auto-generated from git log)
|
|
|
|
*google-chrome-unstable-46.0.2471.2_p1 (09 Aug 2015)
|
|
|
|
09 Aug 2015; Robin H. Johnson <robbat2@gentoo.org>
|
|
+google-chrome-unstable-46.0.2471.2_p1.ebuild, +metadata.xml:
|
|
proj/gentoo: Initial commit
|
|
|
|
This commit represents a new era for Gentoo:
|
|
Storing the gentoo-x86 tree in Git, as converted from CVS.
|
|
|
|
This commit is the start of the NEW history.
|
|
Any historical data is intended to be grafted onto this point.
|
|
|
|
Creation process:
|
|
1. Take final CVS checkout snapshot
|
|
2. Remove ALL ChangeLog* files
|
|
3. Transform all Manifests to thin
|
|
4. Remove empty Manifests
|
|
5. Convert all stale $Header$/$Id$ CVS keywords to non-expanded Git $Id$
|
|
5.1. Do not touch files with -kb/-ko keyword flags.
|
|
|
|
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
|
|
X-Thanks: Alec Warner <antarus@gentoo.org> - did the GSoC 2006 migration
|
|
tests
|
|
X-Thanks: Robin H. Johnson <robbat2@gentoo.org> - infra guy, herding this
|
|
project
|
|
X-Thanks: Nguyen Thai Ngoc Duy <pclouds@gentoo.org> - Former Gentoo
|
|
developer, wrote Git features for the migration
|
|
X-Thanks: Brian Harring <ferringb@gentoo.org> - wrote much python to improve
|
|
cvs2svn
|
|
X-Thanks: Rich Freeman <rich0@gentoo.org> - validation scripts
|
|
X-Thanks: Patrick Lauer <patrick@gentoo.org> - Gentoo dev, running new 2014
|
|
work in migration
|
|
X-Thanks: Michał Górny <mgorny@gentoo.org> - scripts, QA, nagging
|
|
X-Thanks: All of other Gentoo developers - many ideas and lots of paint on
|
|
the bikeshed
|
|
|
|
*google-chrome-unstable-46.0.2478.0_p1 (11 Aug 2015)
|
|
|
|
11 Aug 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-46.0.2471.2_p1.ebuild,
|
|
+google-chrome-unstable-46.0.2478.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.20
|
|
|
|
*google-chrome-unstable-46.0.2486.0_p1 (19 Aug 2015)
|
|
|
|
19 Aug 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-46.0.2478.0_p1.ebuild,
|
|
+google-chrome-unstable-46.0.2486.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.20_p134
|
|
|
|
24 Aug 2015; Justin Lecher <jlec@gentoo.org> metadata.xml:
|
|
Use https by default
|
|
|
|
Convert all URLs for sites supporting encrypted connections from http to
|
|
https
|
|
|
|
Signed-off-by: Justin Lecher <jlec@gentoo.org>
|
|
|
|
24 Aug 2015; Justin Lecher <jlec@gentoo.org>
|
|
google-chrome-unstable-46.0.2486.0_p1.ebuild:
|
|
Enable https for all google URIs
|
|
|
|
Signed-off-by: Justin Lecher <jlec@gentoo.org>
|
|
|
|
24 Aug 2015; Mike Gilbert <floppym@gentoo.org> metadata.xml:
|
|
Revert DOCTYPE SYSTEM https changes in metadata.xml
|
|
|
|
repoman does not yet accept the https version.
|
|
This partially reverts eaaface92ee81f30a6ac66fe7acbcc42c00dc450.
|
|
|
|
Bug: https://bugs.gentoo.org/552720
|
|
|
|
*google-chrome-unstable-46.0.2490.4_p1 (25 Aug 2015)
|
|
|
|
25 Aug 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-46.0.2486.0_p1.ebuild,
|
|
+google-chrome-unstable-46.0.2490.4_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.20
|
|
|
|
*google-chrome-unstable-46.0.2490.6_p1 (27 Aug 2015)
|
|
|
|
27 Aug 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-46.0.2490.4_p1.ebuild,
|
|
+google-chrome-unstable-46.0.2490.6_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.20
|
|
|
|
*google-chrome-unstable-47.0.2498.0_p1 (02 Sep 2015)
|
|
|
|
02 Sep 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-46.0.2490.6_p1.ebuild,
|
|
+google-chrome-unstable-47.0.2498.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.20
|
|
|
|
*google-chrome-unstable-47.0.2503.0_p1 (08 Sep 2015)
|
|
|
|
08 Sep 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-47.0.2498.0_p1.ebuild,
|
|
+google-chrome-unstable-47.0.2503.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.20
|
|
|
|
*google-chrome-unstable-47.0.2508.0_p1 (16 Sep 2015)
|
|
|
|
16 Sep 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-47.0.2503.0_p1.ebuild,
|
|
+google-chrome-unstable-47.0.2508.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.20
|
|
|
|
*google-chrome-unstable-47.0.2516.0_p1 (22 Sep 2015)
|
|
|
|
22 Sep 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-47.0.2508.0_p1.ebuild,
|
|
+google-chrome-unstable-47.0.2516.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.20_p164
|
|
|
|
*google-chrome-unstable-47.0.2522.1_p1 (01 Oct 2015)
|
|
|
|
01 Oct 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-47.0.2516.0_p1.ebuild,
|
|
+google-chrome-unstable-47.0.2522.1_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.22_p5
|
|
|
|
*google-chrome-unstable-47.0.2526.6_p1 (07 Oct 2015)
|
|
|
|
07 Oct 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-47.0.2522.1_p1.ebuild,
|
|
+google-chrome-unstable-47.0.2526.6_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.22_p11
|
|
|
|
*google-chrome-unstable-47.0.2526.8_p1 (09 Oct 2015)
|
|
|
|
09 Oct 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-47.0.2526.6_p1.ebuild,
|
|
+google-chrome-unstable-47.0.2526.8_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.22_p13
|
|
|
|
*google-chrome-unstable-47.0.2526.16_p1 (14 Oct 2015)
|
|
|
|
14 Oct 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-47.0.2526.8_p1.ebuild,
|
|
+google-chrome-unstable-47.0.2526.16_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.22_p20
|
|
|
|
*google-chrome-unstable-48.0.2535.0_p1 (19 Oct 2015)
|
|
|
|
19 Oct 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-47.0.2526.16_p1.ebuild,
|
|
+google-chrome-unstable-48.0.2535.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.23_p4
|
|
|
|
*google-chrome-unstable-48.0.2541.0_p1 (22 Oct 2015)
|
|
|
|
22 Oct 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-48.0.2535.0_p1.ebuild,
|
|
+google-chrome-unstable-48.0.2541.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.23_p4
|
|
|
|
*google-chrome-unstable-48.0.2547.0_p1 (30 Oct 2015)
|
|
|
|
30 Oct 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-48.0.2541.0_p1.ebuild,
|
|
+google-chrome-unstable-48.0.2547.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.23_p10
|
|
|
|
*google-chrome-unstable-48.0.2552.0_p1 (05 Nov 2015)
|
|
|
|
05 Nov 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-48.0.2547.0_p1.ebuild,
|
|
+google-chrome-unstable-48.0.2552.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.23_p18
|
|
|
|
*google-chrome-unstable-48.0.2560.0_p1 (11 Nov 2015)
|
|
|
|
11 Nov 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-48.0.2552.0_p1.ebuild,
|
|
+google-chrome-unstable-48.0.2560.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.23_p26
|
|
|
|
13 Nov 2015; Michael Palimaka <kensington@gentoo.org>
|
|
google-chrome-unstable-48.0.2560.0_p1.ebuild:
|
|
kde-apps/oxygen-icons: pkgmove to kde-frameworks/oxygen-icons
|
|
|
|
kde4-base.eclass: Recognize KDEBASE in kde-frameworks
|
|
kde4-functions.eclass: Change RDEPEND
|
|
chromium.eclass: Minor change
|
|
Various ebuilds: kde-apps/oxygen-icons -> kde-frameworks/oxygen-icons
|
|
|
|
Package-Manager: portage-2.2.23
|
|
|
|
*google-chrome-unstable-48.0.2564.8_p1 (17 Nov 2015)
|
|
|
|
17 Nov 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-48.0.2560.0_p1.ebuild,
|
|
+google-chrome-unstable-48.0.2564.8_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.25
|
|
|
|
19 Nov 2015; Mike Gilbert <floppym@gentoo.org>
|
|
google-chrome-unstable-48.0.2564.8_p1.ebuild:
|
|
Remove RPATH from chrome-sandbox
|
|
|
|
Package-Manager: portage-2.2.25
|
|
|
|
*google-chrome-unstable-48.0.2564.10_p1 (20 Nov 2015)
|
|
|
|
20 Nov 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-48.0.2564.8_p1.ebuild,
|
|
+google-chrome-unstable-48.0.2564.10_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.25
|
|
|
|
*google-chrome-unstable-48.0.2564.22_p1 (04 Dec 2015)
|
|
|
|
04 Dec 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-48.0.2564.10_p1.ebuild,
|
|
+google-chrome-unstable-48.0.2564.22_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.26_p10
|
|
|
|
*google-chrome-unstable-49.0.2587.3_p1 (16 Dec 2015)
|
|
|
|
16 Dec 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-48.0.2564.22_p1.ebuild,
|
|
+google-chrome-unstable-49.0.2587.3_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.26_p32
|
|
|
|
*google-chrome-unstable-49.0.2593.0_p1 (17 Dec 2015)
|
|
|
|
17 Dec 2015; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-49.0.2587.3_p1.ebuild,
|
|
+google-chrome-unstable-49.0.2593.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.26_p32
|
|
|
|
17 Dec 2015; Mike Gilbert <floppym@gentoo.org>
|
|
google-chrome-unstable-49.0.2593.0_p1.ebuild, metadata.xml:
|
|
Add fake-bidi to CHROMIUM_LINGUAS
|
|
|
|
Package-Manager: portage-2.2.26_p32
|
|
|
|
*google-chrome-unstable-49.0.2612.0_p1 (06 Jan 2016)
|
|
|
|
06 Jan 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-49.0.2593.0_p1.ebuild,
|
|
+google-chrome-unstable-49.0.2612.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.26_p125
|
|
|
|
*google-chrome-unstable-49.0.2618.8_p1 (13 Jan 2016)
|
|
|
|
13 Jan 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-49.0.2612.0_p1.ebuild,
|
|
+google-chrome-unstable-49.0.2618.8_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.26_p106
|
|
|
|
*google-chrome-unstable-49.0.2623.13_p1 (21 Jan 2016)
|
|
|
|
21 Jan 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-49.0.2618.8_p1.ebuild,
|
|
+google-chrome-unstable-49.0.2623.13_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.27_p46_p1251
|
|
|
|
22 Jan 2016; Mike Gilbert <floppym@gentoo.org>
|
|
google-chrome-unstable-49.0.2623.13_p1.ebuild:
|
|
Remove RPATH workaround
|
|
|
|
Package-Manager: portage-2.2.27_p47
|
|
|
|
24 Jan 2016; Michał Górny <mgorny@gentoo.org> metadata.xml:
|
|
Replace all herds with appropriate projects (GLEP 67)
|
|
|
|
Replace all uses of herd with appropriate project maintainers, or no
|
|
maintainers in case of herds requested to be disbanded.
|
|
|
|
24 Jan 2016; Michał Górny <mgorny@gentoo.org> metadata.xml:
|
|
Set appropriate maintainer types in metadata.xml (GLEP 67)
|
|
|
|
*google-chrome-unstable-49.0.2623.23_p1 (27 Jan 2016)
|
|
|
|
27 Jan 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-49.0.2623.13_p1.ebuild,
|
|
+google-chrome-unstable-49.0.2623.23_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.27_p49
|
|
|
|
*google-chrome-unstable-50.0.2633.3_p1 (01 Feb 2016)
|
|
|
|
01 Feb 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-49.0.2623.23_p1.ebuild,
|
|
+google-chrome-unstable-50.0.2633.3_p1.ebuild:
|
|
Bump, drops x86 support
|
|
|
|
Package-Manager: portage-2.2.27_p57
|
|
|
|
*google-chrome-unstable-50.0.2638.0_p1 (02 Feb 2016)
|
|
|
|
02 Feb 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-50.0.2633.3_p1.ebuild,
|
|
+google-chrome-unstable-50.0.2638.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.27_p14
|
|
|
|
*google-chrome-unstable-50.0.2645.4_p1 (16 Feb 2016)
|
|
|
|
16 Feb 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-50.0.2638.0_p1.ebuild,
|
|
+google-chrome-unstable-50.0.2645.4_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.27_p57
|
|
|
|
*google-chrome-unstable-50.0.2652.0_p1 (18 Feb 2016)
|
|
|
|
18 Feb 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-50.0.2645.4_p1.ebuild,
|
|
+google-chrome-unstable-50.0.2652.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.27_p64
|
|
|
|
*google-chrome-unstable-50.0.2657.0_p1 (25 Feb 2016)
|
|
|
|
25 Feb 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-50.0.2652.0_p1.ebuild,
|
|
+google-chrome-unstable-50.0.2657.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.27_p64
|
|
|
|
03 Mar 2016; Mike Gilbert <floppym@gentoo.org>
|
|
google-chrome-unstable-50.0.2657.0_p1.ebuild:
|
|
Use gentoo.readme-r1
|
|
|
|
Package-Manager: portage-2.2.27_p64
|
|
|
|
*google-chrome-unstable-50.0.2661.11_p1 (07 Mar 2016)
|
|
|
|
07 Mar 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-50.0.2657.0_p1.ebuild,
|
|
+google-chrome-unstable-50.0.2661.11_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.27_p64
|
|
|
|
*google-chrome-unstable-50.0.2661.18_p1 (09 Mar 2016)
|
|
|
|
09 Mar 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-50.0.2661.11_p1.ebuild,
|
|
+google-chrome-unstable-50.0.2661.18_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.27_p81
|
|
|
|
*google-chrome-unstable-51.0.2679.0_p1 (16 Mar 2016)
|
|
|
|
16 Mar 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-50.0.2661.18_p1.ebuild,
|
|
+google-chrome-unstable-51.0.2679.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.28_p60
|
|
|
|
18 Mar 2016; Mike Gilbert <floppym@gentoo.org>
|
|
google-chrome-unstable-51.0.2679.0_p1.ebuild:
|
|
www-client/google-chrome: Add REQUIRED_USE="abi_x86_64"
|
|
|
|
This should prevent people from accidentatlly trying to install this
|
|
package on x86 due to portage's autounmask feature.
|
|
|
|
Bug: https://bugs.gentoo.org/577678
|
|
|
|
21 Mar 2016; Mike Gilbert <floppym@gentoo.org>
|
|
google-chrome-unstable-51.0.2679.0_p1.ebuild:
|
|
Revert "www-client/google-chrome: Add REQUIRED_USE="abi_x86_64""
|
|
|
|
This reverts commit 8e336a3b9265100c300094900f4601296e317333.
|
|
|
|
Adding this REQUIRED_USE constraint is pretty hacky and users will
|
|
quickly figure out that the ebuild doesn't work anyway.
|
|
|
|
*google-chrome-unstable-51.0.2687.0_p1 (23 Mar 2016)
|
|
|
|
23 Mar 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-51.0.2679.0_p1.ebuild,
|
|
+google-chrome-unstable-51.0.2687.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.28_p64
|
|
|
|
23 Mar 2016; Mike Gilbert <floppym@gentoo.org>
|
|
google-chrome-unstable-51.0.2687.0_p1.ebuild:
|
|
www-client/google-chrome: Misc cleanup
|
|
|
|
EAPI=6
|
|
Remove stale code that is no longer useful with x86 gone.
|
|
Die in pkg_pretend if not on amd64.
|
|
|
|
*google-chrome-unstable-51.0.2693.2_p1 (29 Mar 2016)
|
|
|
|
29 Mar 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-51.0.2687.0_p1.ebuild,
|
|
+google-chrome-unstable-51.0.2693.2_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.28_p64
|
|
|
|
*google-chrome-unstable-51.0.2700.0_p1 (06 Apr 2016)
|
|
|
|
06 Apr 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-51.0.2693.2_p1.ebuild,
|
|
+google-chrome-unstable-51.0.2700.0_p1.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.28_p64
|
|
|
|
*google-chrome-unstable-51.0.2704.4 (13 Apr 2016)
|
|
|
|
13 Apr 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-51.0.2700.0_p1.ebuild,
|
|
+google-chrome-unstable-51.0.2704.4.ebuild:
|
|
bump
|
|
|
|
Package-Manager: portage-2.2.28_p64
|
|
|
|
*google-chrome-unstable-51.0.2704.7 (15 Apr 2016)
|
|
|
|
15 Apr 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-51.0.2704.4.ebuild,
|
|
+google-chrome-unstable-51.0.2704.7.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.28_p64
|
|
|
|
*google-chrome-unstable-51.0.2704.19 (20 Apr 2016)
|
|
|
|
20 Apr 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-51.0.2704.7.ebuild,
|
|
+google-chrome-unstable-51.0.2704.19.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.28_p3
|
|
|
|
*google-chrome-unstable-52.0.2716.0 (27 Apr 2016)
|
|
|
|
27 Apr 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-51.0.2704.19.ebuild,
|
|
+google-chrome-unstable-52.0.2716.0.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.28_p79
|
|
|
|
*google-chrome-unstable-52.0.2723.2 (06 May 2016)
|
|
|
|
06 May 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-52.0.2716.0.ebuild,
|
|
+google-chrome-unstable-52.0.2723.2.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.28_p97
|
|
|
|
*google-chrome-unstable-52.0.2729.3 (11 May 2016)
|
|
|
|
11 May 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-52.0.2723.2.ebuild,
|
|
+google-chrome-unstable-52.0.2729.3.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.28_p105
|
|
|
|
*google-chrome-unstable-52.0.2739.0 (18 May 2016)
|
|
|
|
18 May 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-52.0.2729.3.ebuild,
|
|
+google-chrome-unstable-52.0.2739.0.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.2.28_p107_p545449
|
|
|
|
21 May 2016; Mike Gilbert <floppym@gentoo.org>
|
|
google-chrome-unstable-52.0.2739.0.ebuild:
|
|
www-client/google-chrome: replace es_LA with es_419
|
|
|
|
*google-chrome-unstable-52.0.2743.10 (27 May 2016)
|
|
|
|
27 May 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-52.0.2739.0.ebuild,
|
|
+google-chrome-unstable-52.0.2743.10.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.3.0_rc1_p12
|
|
|
|
*google-chrome-unstable-52.0.2743.19 (31 May 2016)
|
|
|
|
31 May 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-52.0.2743.10.ebuild,
|
|
+google-chrome-unstable-52.0.2743.19.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.3.0_rc1_p14
|
|
|
|
*google-chrome-unstable-53.0.2756.0 (04 Jun 2016)
|
|
|
|
04 Jun 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-52.0.2743.19.ebuild,
|
|
+google-chrome-unstable-53.0.2756.0.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.3.0_rc1_p14
|
|
|
|
*google-chrome-unstable-53.0.2763.0 (10 Jun 2016)
|
|
|
|
10 Jun 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-53.0.2756.0.ebuild,
|
|
+google-chrome-unstable-53.0.2763.0.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.3.0_rc1_p20
|
|
|
|
*google-chrome-unstable-53.0.2767.4 (16 Jun 2016)
|
|
|
|
16 Jun 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-53.0.2763.0.ebuild,
|
|
+google-chrome-unstable-53.0.2767.4.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.3.0_rc1_p20
|
|
|
|
*google-chrome-unstable-53.0.2774.3 (25 Jun 2016)
|
|
|
|
25 Jun 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-53.0.2767.4.ebuild,
|
|
+google-chrome-unstable-53.0.2774.3.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-portage_p2.3.0
|
|
|
|
28 Jun 2016; Mike Gilbert <floppym@gentoo.org>
|
|
google-chrome-unstable-53.0.2774.3.ebuild, metadata.xml:
|
|
use chromium-2.eclass
|
|
|
|
Package-Manager: portage-portage_p2.3.0
|
|
|
|
*google-chrome-unstable-53.0.2783.2 (29 Jun 2016)
|
|
|
|
29 Jun 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-53.0.2774.3.ebuild,
|
|
+google-chrome-unstable-53.0.2783.2.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.3.0_p7
|
|
|
|
07 Jul 2016; Mike Gilbert <floppym@gentoo.org>
|
|
google-chrome-unstable-53.0.2783.2.ebuild, metadata.xml:
|
|
drop l10n_fake-bidi
|
|
|
|
Bug: https://bugs.gentoo.org/588198
|
|
|
|
Package-Manager: portage-2.3.0_p11
|
|
|
|
*google-chrome-unstable-53.0.2785.8 (08 Jul 2016)
|
|
|
|
08 Jul 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-53.0.2783.2.ebuild,
|
|
+google-chrome-unstable-53.0.2785.8.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.3.0_p11
|
|
|
|
*google-chrome-unstable-53.0.2785.8-r1 (10 Jul 2016)
|
|
|
|
10 Jul 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-53.0.2785.8.ebuild,
|
|
+google-chrome-unstable-53.0.2785.8-r1.ebuild:
|
|
create /usr/bin/${PN} symlink
|
|
|
|
It appears this is no longer included in the data.tar archive; instead, the
|
|
postinst script creates it when installed using dpkg.
|
|
|
|
https://bugs.gentoo.org/588318
|
|
|
|
Package-Manager: portage-2.3.0_p11
|
|
|
|
*google-chrome-unstable-53.0.2785.21 (20 Jul 2016)
|
|
|
|
20 Jul 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-53.0.2785.8-r1.ebuild,
|
|
+google-chrome-unstable-53.0.2785.21.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.3.0_p15
|
|
|
|
*google-chrome-unstable-53.0.2785.30 (27 Jul 2016)
|
|
|
|
27 Jul 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-53.0.2785.21.ebuild,
|
|
+google-chrome-unstable-53.0.2785.30.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.3.0_p16
|
|
|
|
*google-chrome-unstable-54.0.2810.2 (29 Jul 2016)
|
|
|
|
29 Jul 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-53.0.2785.30.ebuild,
|
|
+google-chrome-unstable-54.0.2810.2.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.3.0_p16
|
|
|
|
*google-chrome-unstable-54.0.2816.0 (03 Aug 2016)
|
|
|
|
03 Aug 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-54.0.2810.2.ebuild,
|
|
+google-chrome-unstable-54.0.2816.0.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.3.0_p16
|
|
|
|
*google-chrome-unstable-54.0.2824.0 (10 Aug 2016)
|
|
|
|
10 Aug 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-54.0.2816.0.ebuild,
|
|
+google-chrome-unstable-54.0.2824.0.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.3.0_p16
|
|
|
|
*google-chrome-unstable-54.0.2832.2 (20 Aug 2016)
|
|
|
|
20 Aug 2016; Mike Gilbert <floppym@gentoo.org>
|
|
-google-chrome-unstable-54.0.2824.0.ebuild,
|
|
+google-chrome-unstable-54.0.2832.2.ebuild:
|
|
automated update
|
|
|
|
Package-Manager: portage-2.3.0_p16
|
|
|