Bug 24613 - chromium synchronization not working due to missing api keys (typo in spec file causes them to be ignored)
Summary: chromium synchronization not working due to missing api keys (typo in spec fi...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Christiaan Welvaart
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-03 12:33 CEST by Christian Lohmaier
Modified: 2019-04-07 02:16 CEST (History)
1 user (show)

See Also:
Source RPM: chromium-browser-stable-73.0.3683.86-1.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Christian Lohmaier 2019-04-03 12:33:45 CEST
Description of problem:
account synchronization and other features relying on google api keys are not working in the current version of chromium-browser.

reason for that is that the api keys from the spec file are ignored/not used due to a missing line-continuation escape on the configure line:

[starts with some options....]
                  use_system_libpng=true \
                  use_custom_libcxx=false \
                  closure_compile=false
                  google_api_key="%{google_api_key}" \
                  google_default_client_id="%{google_default_client_id}" \
                  google_default_client_secret="%{google_default_client_secret}"

Note the missing \  on the closure_compile line.

Major severity as it's a regression and easy to fix.
Comment 1 Marja Van Waes 2019-04-06 10:03:35 CEST
Assigning to our registered chromium-browser-stable maintainer.

Assignee: bugsquad => cjw
CC: (none) => marja11

Comment 2 Christiaan Welvaart 2019-04-06 15:47:59 CEST
I noticed this while preparing the mga6 update, it will be fixed in 73.0.3683.103-1 (maybe in less than 24h since it's building on the old build machines this time).

Status: NEW => ASSIGNED

Comment 3 Christiaan Welvaart 2019-04-07 02:16:44 CEST
Fixed with chromium-browser-stable-73.0.3683.103-1.mga7.

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


Note You need to log in before you can comment on or make changes to this bug.