Bug 22144

Summary:	google-chrome-stable-63.0.3239.84-1.x86_64 can't be installed ca-certificates is non satisfied
Product:	Mageia	Reporter:	peter lawford <petlaw726>
Component:	RPM Packages	Assignee:	QA Team <qa-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	alda.cerny, cae, davidwhodgins, herman.viaene, jim, lists.jjorge, peter.semiletov, sysadmin-bugs
Version:	6	Keywords:	advisory, validated_update
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	MGA5TOO MGA5-64-OK MGA5-32-OK MGA6-64-OK MGA6-32-OK
Source RPM:	rootcerts	CVE:
Status comment:

Description peter lawford 2017-12-08 14:21:21 CET

Description of problem:I actually have google-chrome-stable-62.0.3202.94-1 in my system mageia6; if I want to upgrade it:

[root@mageia5_64 alain4]# urpmi --auto-update
le média « Google Earth 64bit » est à jour
le média « Google Talkplugin 64bit » est à jour
le média « Google Chrome 64bit » est à jour
le média « Google Miroir 64bit » est à jour
le média « Core Release (distrib1) » est à jour
le média « Core Updates (distrib3) » est à jour
le média « Nonfree Release (distrib11) » est à jour
le média « Nonfree Updates (distrib13) » est à jour
le média « Tainted Release (distrib21) » est à jour
le média « Tainted Updates (distrib23) » est à jour
le média « Core 32bit Release (distrib31) » est à jour
le média « Core 32bit Updates (distrib32) » est à jour
le média « Nonfree 32bit Release (distrib36) » est à jour
le média « Nonfree 32bit Updates (distrib37) » est à jour
le média « Tainted 32bit Release (distrib41) » est à jour
le média « Tainted 32bit Updates (distrib42) » est à jour
Le paquetage demandé ne peut pas être installé :
google-chrome-stable-63.0.3239.84-1.x86_64 (car ca-certificates est non satisfait)
Désirez-vous tout de même continuer ? (O/n) o
Certains paquets ont été installés mais d'autres ont échoué.
Le paquetage demandé ne peut pas être installé :
google-chrome-stable-63.0.3239.84-1.x86_64 (car ca-certificates est non satisfait)

how to get ca-certificates?

however I successfully installed google-chrome-stable-63.0.3239.84-1.x86_64 using the command: # rpm -ivh --nodeps --force
but I think it is not clean



Version-Release number of selected component (if applicable):


How reproducible:
1- download the package google-chrome-stable_current_x86_64.rpm or add the google chrome repository to your packages manager:
# urpmi.addmedia --update Google\ Chrome\ 64bit http://dl.google.com/linux/chrome/rpm/stable/x86_64

2- try to install it:
# urpmi google-chrome-stable_current_x86_64.rpm



Steps to Reproduce:
1.
2.
3.

Comment 1 James Kerr 2017-12-08 14:44:05 CET

This is a known issue - see bug#11398

*** This bug has been marked as a duplicate of bug 11398 ***

Status: NEW => RESOLVED
CC: (none) => jim
Resolution: (none) => DUPLICATE

Comment 2 José Jorge 2017-12-08 17:58:55 CET

This one will serve to follow the fix update in MGA6.

Resolution: DUPLICATE => (none)
Status: RESOLVED => REOPENED
CC: (none) => lists.jjorge

José Jorge 2017-12-08 17:59:04 CET

Assignee: bugsquad => lists.jjorge

Ales Cerny 2017-12-10 16:19:54 CET

CC: (none) => alda.cerny

Comment 3 David Walser 2017-12-13 03:00:51 CET

Updated packages in core/updates_testing:
----------------------------------------
rootcerts-20171122.00-1.mga5
rootcerts-java-20171122.00-1.mga5
rootcerts-20171122.00-1.mga6
rootcerts-java-20171122.00-1.mga6

from SRPMS:
rootcerts-20171122.00-1.mga5.src.rpm
rootcerts-20171122.00-1.mga6.src.rpm

Someone else can feel free to write some advisory text and assign this to QA.  The rootcerts have been updated to the latest certdata from Mozilla (November 22) and it now virtual provides ca-certificates.

BTW, I don't know who the semiletov is who first added the provides for mga6, but if they're not on this bug, please let them know to follow convention for where to put the subrel (should generally be immediately above %mkrel definition line, not randomly at the top of the SPEC).  Thanks.

Whiteboard: (none) => MGA5TOO
Source RPM: google-chrome-stable-63.0.3239.84-1.x86_64 => rootcerts

Comment 4 Peter Semiletov 2017-12-13 15:25:43 CET

Thanks, I've read this advice about "subrel" :)

CC: (none) => peter.semiletov

José Jorge 2017-12-13 15:37:53 CET

Assignee: lists.jjorge => qa-bugs

Comment 5 Herman Viaene 2017-12-14 14:57:55 CET

MGA5-32 on Dell Latitude D600 Xfce
No installation issues.
No apparent adverse issues. I cannot test the google-chrome since it is only provided for 64-bit.

Whiteboard: MGA5TOO => MGA5TOO MGA5-32-OK
CC: (none) => herman.viaene

Comment 6 Dave Hodgins 2017-12-15 00:26:51 CET

[RPM][11550]: install google-chrome-stable-63.0.3239.108-1.x86_64: success

# rpm -q --requires google-chrome-stable |grep cert
ca-certificates

Adding MGA5-64-OK. Will test Mageia 6 shortly.

Whiteboard: MGA5TOO MGA5-32-OK => MGA5TOO MGA5-32-OK MGA5-64-OK
CC: (none) => davidwhodgins

Comment 7 Dave Hodgins 2017-12-15 03:53:45 CET

Validating the update

Keywords: (none) => validated_update
Whiteboard: MGA5TOO MGA5-32-OK MGA5-64-OK => MGA5TOO MGA5-32-OK MGA5-64-OK MGA6-32-OK MGA6-64-OK
CC: (none) => sysadmin-bugs

Comment 8 peter lawford 2017-12-15 17:00:58 CET

(In reply to David Walser from comment #3)
> Updated packages in core/updates_testing:
> ----------------------------------------
> rootcerts-20171122.00-1.mga5
> rootcerts-java-20171122.00-1.mga5
> rootcerts-20171122.00-1.mga6
> rootcerts-java-20171122.00-1.mga6
> 
> from SRPMS:
> rootcerts-20171122.00-1.mga5.src.rpm
> rootcerts-20171122.00-1.mga6.src.rpm
> 
> Someone else can feel free to write some advisory text and assign this to
> QA.  The rootcerts have been updated to the latest certdata from Mozilla
> (November 22) and it now virtual provides ca-certificates.
> 
> BTW, I don't know who the semiletov is who first added the provides for
> mga6, but if they're not on this bug, please let them know to follow
> convention for where to put the subrel (should generally be immediately
> above %mkrel definition line, not randomly at the top of the SPEC).  Thanks.

sorry no rootcerts-20171122.00-1.mga6 in core/updates_testing, neither in mageia6 nore cauldron

Comment 9 peter lawford 2017-12-15 17:05:50 CET

(In reply to Dave Hodgins from comment #6)
> [RPM][11550]: install google-chrome-stable-63.0.3239.108-1.x86_64: success
> 
> # rpm -q --requires google-chrome-stable |grep cert
> ca-certificates
> 
> Adding MGA5-64-OK. Will test Mageia 6 shortly.

how have you successfully installed google-chrome, without ca-certificates? the only way is the installation by force:
# rpm -ivh --nodeps --force google-chrome-stable-63.0.3239.108-1.x86_64

Comment 10 Charles Edwards 2017-12-15 18:24:47 CET

What ever Mga6 mirror you are using must not be up-o-date.

http://mirrors.kernel.org/mageia/distrib/6/x86_64/media/core/updates_testing/rootcerts-20171122.00-1.mga6.noarch.rpm

http://mirrors.kernel.org/mageia/distrib/6/x86_64/media/core/updates_testing/rootcerts-java-20171122.00-1.mga6.noarch.rpm

CC: (none) => cae

Dave Hodgins 2017-12-15 20:56:20 CET

Keywords: (none) => advisory

Comment 11 David Walser 2017-12-15 21:25:17 CET

This can't be validated yet because nss needs to be rebuilt for the updated rootcerts.  An attempt was made to rebuild it, but the build failed.

Keywords: advisory, validated_update => feedback
Whiteboard: MGA5TOO MGA5-32-OK MGA5-64-OK MGA6-32-OK MGA6-64-OK => MGA5TOO

Comment 12 David Walser 2017-12-19 02:06:20 CET

Advisory:
----------------------------------------

The rootcerts package has been updated with the latest certdata.txt from
Mozilla.

Additionally, it has a virtual provides on ca-certificates to allow the
installation of third party packages that expect it.

Updated packages in core/updates_testing:
----------------------------------------
rootcerts-20171122.00-1.1.mga5
rootcerts-java-20171122.00-1.1.mga5
nss-3.28.6-1.2.mga5
nss-doc-3.28.6-1.2.mga5
libnss3-3.28.6-1.2.mga5
libnss-devel-3.28.6-1.2.mga5
libnss-static-devel-3.28.6-1.2.mga5
rootcerts-20171122.00-1.1.mga6
rootcerts-java-20171122.00-1.1.mga6
nss-3.28.6-1.2.mga6
nss-doc-3.28.6-1.2.mga6
libnss3-3.28.6-1.2.mga6
libnss-devel-3.28.6-1.2.mga6
libnss-static-devel-3.28.6-1.2.mga6

from SRPMS:
rootcerts-20171122.00-1.1.mga5.src.rpm
nss-3.28.6-1.2.mga5.src.rpm
rootcerts-20171122.00-1.1.mga6.src.rpm
nss-3.28.6-1.2.mga6.src.rpm

Keywords: feedback => (none)

Comment 13 Dave Hodgins 2017-12-19 05:00:27 CET

Advisory updated.

New packages tested on both arches, both releases.

Validating the update.

Keywords: (none) => advisory, validated_update
Whiteboard: MGA5TOO => MGA5TOO MGA5-64-OK MGA5-32-OK MGA6-64-OK MGA6-32-OK

Comment 14 Mageia Robot 2017-12-21 18:44:27 CET

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGASA-2017-0457.html

Resolution: (none) => FIXED
Status: REOPENED => RESOLVED