[users] flash-plugin for 64-bit

[Dee Holtsclaw]

All of the discussion regarding yum-updatesd, etc. has reminded me of the YUM
errors I've been plagued with for the last couple of weeks.

SL 6.1 enables cron updating by default and since Adobe released 11.1.102.55,
the 32-bit and 64-bit copies are out-of-sync. Been basically ignoring the
error 'til now in the hopes it would go away but, considering these releases
usually plug massive exploits, I'm starting to get concerned. Is there any
way to trigger repackaging of this?

[Dag Wieers]

Post by Dee Holtsclaw
SL 6.1 enables cron updating by default and since Adobe released 11.1.102.55,
the 32-bit and 64-bit copies are out-of-sync. Been basically ignoring the
error 'til now in the hopes it would go away but, considering these releases
usually plug massive exploits, I'm starting to get concerned. Is there any
way to trigger repackaging of this?

I get triggered by security reports from Red Hat. Red Hat currently ships
the 32bit flash-plugin flash-plugin-10.3.183.11-1.el6.i686 in both 32bit
and 64bit repositories but the old URLs to download the 'latest' v10 do
not longer work.

So the question is whether I should replace the v10 flash-plugin on 32bit
to v11 ? And since they then replace the upstream (RHEL) flash-plugin
package they should technically move to extras :-(

And unfortunately Red Hat does not ship a 64bit flash-plugin (the reason
for this is that Adobe did not support it until recently), and as a result
I do not track 64bit flash-plugin versions (which are v11). I have it
updated to the latest v11.

[Dag Wieers]

Post by Dag Wieers

Post by Dee Holtsclaw
SL 6.1 enables cron updating by default and since Adobe released 11.1.102.55,
the 32-bit and 64-bit copies are out-of-sync. Been basically ignoring the
error 'til now in the hopes it would go away but, considering these releases
usually plug massive exploits, I'm starting to get concerned. Is there any
way to trigger repackaging of this?

I get triggered by security reports from Red Hat. Red Hat currently ships
the 32bit flash-plugin flash-plugin-10.3.183.11-1.el6.i686 in both 32bit
and 64bit repositories but the old URLs to download the 'latest' v10 do
not longer work.
So the question is whether I should replace the v10 flash-plugin on 32bit
to v11 ? And since they then replace the upstream (RHEL) flash-plugin
package they should technically move to extras :-(

Ok, no worries. I just found this link:
http://kb2.adobe.com/cps/142/tn_14266.html

They do offer a big ZIP file with all platform release of a given version.
This will do...

[Dag Wieers]

Post by Dag Wieers

Post by Dee Holtsclaw
SL 6.1 enables cron updating by default and since Adobe released 11.1.102.55,
the 32-bit and 64-bit copies are out-of-sync. Been basically ignoring the
error 'til now in the hopes it would go away but, considering these releases
usually plug massive exploits, I'm starting to get concerned. Is there any
way to trigger repackaging of this?

I get triggered by security reports from Red Hat. Red Hat currently ships
the 32bit flash-plugin flash-plugin-10.3.183.11-1.el6.i686 in both 32bit
and 64bit repositories but the old URLs to download the 'latest' v10 do
not longer work.
So the question is whether I should replace the v10 flash-plugin on 32bit
to v11 ? And since they then replace the upstream (RHEL) flash-plugin
package they should technically move to extras :-(

Ok, no worries. I just found this link:
http://kb2.adobe.com/cps/142/tn_14266.html

They do offer a big ZIP file with all platform release of a given version.
This will do...

[Dee Holtsclaw]

All of the discussion regarding yum-updatesd, etc. has reminded me of the YUM
errors I've been plagued with for the last couple of weeks.

SL 6.1 enables cron updating by default and since Adobe released 11.1.102.55,
the 32-bit and 64-bit copies are out-of-sync. Been basically ignoring the
error 'til now in the hopes it would go away but, considering these releases
usually plug massive exploits, I'm starting to get concerned. Is there any
way to trigger repackaging of this?

[Dag Wieers]

Post by Dee Holtsclaw
SL 6.1 enables cron updating by default and since Adobe released 11.1.102.55,
the 32-bit and 64-bit copies are out-of-sync. Been basically ignoring the
error 'til now in the hopes it would go away but, considering these releases
usually plug massive exploits, I'm starting to get concerned. Is there any
way to trigger repackaging of this?

I get triggered by security reports from Red Hat. Red Hat currently ships
the 32bit flash-plugin flash-plugin-10.3.183.11-1.el6.i686 in both 32bit
and 64bit repositories but the old URLs to download the 'latest' v10 do
not longer work.

So the question is whether I should replace the v10 flash-plugin on 32bit
to v11 ? And since they then replace the upstream (RHEL) flash-plugin
package they should technically move to extras :-(

And unfortunately Red Hat does not ship a 64bit flash-plugin (the reason
for this is that Adobe did not support it until recently), and as a result
I do not track 64bit flash-plugin versions (which are v11). I have it
updated to the latest v11.