Summary: | www-client/chromium-9999-r1: ninja error, missing LASTCHANGE.blink needed by webkit_version.h | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Julien Sanchez <julien.sanchez> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build log
patch WIP ebuild update: failing build log patch WIP ebuild update build.log (file collisions failure) |
Description
Julien Sanchez
2013-06-24 07:48:40 UTC
LASTCHANGE.blink seems generated by export_tarball.py script and is referenced from webkit/common/user_agent/webkit_user_agent.gyp Created attachment 351940 [details, diff]
patch
While I took a look at fixing this issue, I've also updated the 9999 ebuild to use https.
Could you test the attached patch and confirm it works for you?
Created attachment 351956 [details]
WIP ebuild update: failing build log
With patch applied, it fails to update existing svn cache (failing build log attached).
Created attachment 351972 [details, diff] patch (In reply to Julien Sanchez from comment #3) > With patch applied, it fails to update existing svn cache (failing build log > attached). Oh, indeed, fails when usersandbox is used. Please test updated patch, thanks for catching this (added addwrite as in subversion.eclass). Created attachment 351992 [details]
WIP ebuild update build.log (file collisions failure)
It compiles fine now but it fails to merge due to file collisions.
Please note that I have splitdebug FEATURE enabled which could be the source of this new issue. I will try later without it.
(In reply to Julien Sanchez from comment #5) > Created attachment 351992 [details] > WIP ebuild update build.log (file collisions failure) > > It compiles fine now Excellent, closing this bug then. > but it fails to merge due to file collisions. > > Please note that I have splitdebug FEATURE enabled which could be the source > of this new issue. I will try later without it. Confirmed, I hit the same issue - could you file a new bug for it? Thanks! |