On Wed, Jul 3, 2013 at 6:51 AM, Dag Wieers <[log in to unmask]> wrote:
> On Wed, 3 Jul 2013, Steven Haigh wrote:
>> On 3/07/2013 6:04 PM, Yasha Karant wrote:
>>>
>>> I thoroughly am confused about these responses. Unless I am mistaken,
>>> the chrome RPM seems to be from a standard EL6 repository. Moreover,
>>> the previous release of chrome through this same method did not produce
>>> this error, and installed and ran without obvious issues. However, as
>>> updates typically both fix bugs and security holes, we routinely update
>>> to current production. It is only the most current release of "real"
>>> chrome (not chromium) that shows this problem -- is there a repository
>>> with the necessary RPMs for a proper workaround?
>>
>> Google calls RHEL6 'too old' and 'obsolete' now. See:
>>
>> http://linux.slashdot.org/story/13/02/11/1452259/rhel-6-no-longer-supported-by-google-chrome
>>
>> Nothing in EL6 caused this break - purely internal stuff from Google.
>
> Their build-system is Ubuntu based, and Ubuntu moved on.
>
> It's pretty cynical to learn that at Google the RHEL packages have been
> build in an Ubuntu environment, rather than properly packaged on the same
> distribution. A practice that almost everyone is doing today.
>
> It's amazing that this even worked, we'd be better off if it didn't...

They must be using mock, which is available in Ubuntu.

Although the above seems weird, it looks like something people want.
There was a recent thread on fedora-devel about the opposite,
packaging debhelper and friends for Fedora in order to package .deb.

So, in a purpose-built chroot, why not? As Ubuntu and EL6 diverge with
Ubuntu's permanent next-version updates, some problems may arise.
IIRC, the Fedora builders run EL6 but they can't run EL5.

(It seems wrong nonetheless - and it must, although I'd love to see
proof, make the build and the end-result more brittle.)