Hi Kevin and EPEL,
Is there any sign of EPEL 7 support for Wine 32 yet? The
lack of Wine 32 is keeping me on SL 6.6 and it is starting
to drive me nuts!
EPEL: think of the guilt you would feel if I get
stuck in an insane asylums over the lack of wine 32
support! Seriously, the guilt would haunt you to the end
of your days. Okay, maybe not, but still ...
Many thanks,
-T
Hey, I had to try. If guilt doesn't work,
I am really good at insincere compliments too.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

What's the status of EPEL7 on i686? I haven't heard anything in a few
months but last I heard EPEL was going to be trialed on antoehr alt-arch
before i686, was this done yet and what's the current hold-up?
Peter

Hello,
we are discussing in this bug
https://bugzilla.redhat.com/show_bug.cgi?id=1220138 the work that
would be required to upgrade Mono in Epel.
I am aware that this is a major upgrade, and according to [1] it
should be avoided.
But Mono is that old in Epel7 already, so the discussion currently
goes into the direction that an upgrade is better than nobody using
Mono in Epel at all.
I would like to upgrade to the latest stable Mono version, which is
4.2 at the moment. That is in rawhide already, F23 has Mono 4.0.
What do people think on this list?
Do I need to create a Fesco ticket to request permission to upgrade
Mono in Epel7, and to do a bootstrap similar to Mono 4 in Fedora [2]?
Thanks for any hints and suggestions,
Timotheus
[1] https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#A_major_version...
[2] https://fedorahosted.org/fpc/ticket/528

Hi,
A few days ago, three CVEs for Nginx and were fixed in 1.8.1. Upstream
only maintain 1.8.x and above, so they didn't release any fixes for
older versions of Nginx. I was able to backport the relevant commits to
Nginx 1.6.x on EL7.
Unfortunately, Nginx 1.0.x on EL6 is too old; I gave it a good shot but
backporting the patches reliably without creating new CVEs is beyond my
expertise. Nginx 0.8.x on EL5 is prehistoric.
This leaves the package in a bit of a pickle. Leaving things as they are
would leave web servers vulnerable. On the other hand, updating Nginx to
1.8.x on EL5/6/7 will inevitably break something for someone (eg, via
yum-cron). I had a small discussion on fedora-devel ML about the
situation [0], and the consensus was to request for an exception.
My plan:
1. Update to 1.8.x on all branches (or to as recent a version as they
can go without FTBFS)
2. Leave them in epel-testing for a prolonged period, probably until the
next point release of RHEL.
3. Include some migration notes with the RPMs, and also post these notes
to epel-devel/epel-announce.
Sound reasonable?
[0]:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
Kind regards,
Jamie

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
All,
I have built Xfce 4.12 packages for EL-7 on COPR. The link for the
repo is
https://copr.fedorainfracloud.org/coprs/nonamedotc/xfce412-epel7/
I would appreciate it if people can install the packages and give it a
spin. Please report any issues directly to me (and not in bugzilla)
as these are not official packages.
Many thanks for testing.
Mukundan.
- --
GPG Key - E5C8BC67
- -------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJWzlpcAAoJEHE/1K3lyLxniE8QALXgsIfRuGltpv+gZwvorJsu
KpOQDgif2qtJwcMik6NCxGE33o6RgK6puboEk2e4iSrjil/iWL9dFstKU9zbfq5O
pUMIeD1zx/AFaw+9XhjK90rZbOEGx+AzknBwy6xwy+hlIHt8MN4C6HKd/+t55uFb
49ik/L4MRD/09fY5cjqZE9ook8frDXmsaFKyWMZOsvBqdoEasuzmrZum1QppS0Br
cdiw0MGqGza5avfyVdoj/stpc2fcOz4OHaaRnWmfdf5lQ9ezN/eMP1xFIM1bJ9eU
8ynGSAwybZsEdxJMkkjWkrN/kvK4ZwGTtbUELJ576Ll88BbFPQagMhCn0fz8UZX4
Vo9tYzS8E0z0uGpg3Z4L1dCtf/ueback5nUFMLC55KV6wTpK2QZPbxPXzEiksNi8
WgfbcA1amOfSVBjBwXXEs5q6DmVHC4jIwO5DLEX39dmmJKFhvajIvofkgAJzUZUy
W5pYkhF6ntP2VCiaGomwAAGrQMeyopGbEJ347eeRNfJvNiWmn2yTb9AUvjqEv38t
WlV1KfEIA/SQjo2lhhC8mo8jO7PSdM9Knz2GU45BBSsZnRNp8HyoGDeoZVJ/bsHI
YLVxdfwfvHPH5LWHFpSqSs4IUZs+dH4AMwwFiMqaTZJkxHBRv+Fs2IgMy9IN2WJL
v5XR7kkMxQ2WMor34szA
=5sOk
-----END PGP SIGNATURE-----

Hey I went through my notes and I only have 1 other questioned
proposal that people asked about. I will post that later today but if
there are things people think should have been talked about please let
me know.
--
Stephen J Smoogen.