fedup f18->f19 going OK?

[Daniel J Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/02/2013 07:37 PM, Ed Greshko wrote:
> On 07/03/13 07:34, Steven Stern wrote:
>> On 07/02/2013 06:23 PM, Ed Greshko wrote:
>>> On 07/03/13 06:13, Steven Stern wrote:
>>>> On 07/02/2013 04:27 PM, Ed Greshko wrote:
>>>>> On 07/03/13 04:32, Steven Stern wrote:
>>>>>> On 07/02/2013 03:23 PM, Steven Stern wrote:
>>>>>>> On 07/02/2013 08:02 AM, Neal Becker wrote:
>>>>>>>> I'm about to try fedup f18->f19.  Any reports good/bad on
>>>>>>>> this route?
>>>>>>>> 
>>>>>>> Just finished the upgrade.  Some of my XFCE settings aren't
>>>>>>> quite right, but the changes aren't anything I can't live
>>>>>>> with... or care about enough to change right away.
>>>>>>> 
>>>>>>> There doesn't seem to be an F19 Virtualbox repo yet, but the
>>>>>>> F18 version is running OK.
>>>>>>> 
>>>>>> Getting AVCs every time I start Chrome -- reported as a bug.
>>>>> Hope you reported the bug to Google as it is a Chrome bug and and a
>>>>> Fedora problem.  This was discussed on the test list a while back.
>>>>> A version of Chrome unstable had the fix....but it really was
>>>>> unstable.
>>>>> 
>>>>> 
>>>>> 
>>>> I reported it wherever the AVC bug reports go....
>>>> 
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=964651
>>>> 
>>>> As it worked in F18 and not in F19, it seems to me it's a bug in the 
>>>> F19-supplied SELinux policy.
>>>> 
>>> FWIW, I see in the report ....
>>> 
>>> Source RPM Packages
>>> google-chrome-stable-26.0.1410.63-192696.x86_64
>>> 
>>> On my F19 test system, fedup'd from F18 I have....
>>> 
>>> google-chrome-stable-28.0.1500.70-209565.x86_64 
>>> selinux-policy-3.12.1-54.fc19.noarch 
>>> selinux-policy-targeted-3.12.1-54.fc19.noarch
>>> 
>>> And I am not seeing the AVC you're seeing.  Have you considered
>>> updating your Chrome?
>>> 
>> My chrome package is google-chrome-beta-28.0.1500.70-209565.x86_64, 
>> straight from the Google repo.  I switched from stable to beta to get rid
>> of the last AVC problem.
>> 
> 
> So, you're saying that the beta of Chrome does not cause the AVC?
> 
> FWIW, my google-chrome-stable-28.0.1500.70-209565.x86_64 came directly from
> the Google repo as well.  But, I had to "yum clean metadata" before it was
> picked up.
> 
> 
That bugzilla is waiting for the AVC output.  Without the AVC we can not
understand the problem.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlHUCIsACgkQrlYvE4MpobOe5ACfSb2RAGFryYFsMS/tc7AjGIWB
dncAoJMlz4UqypGB5CBNBDuKaSm540uX
=ueJf
-----END PGP SIGNATURE-----