[EPEL-devel] Re: [CentOS-devel] [Messaging] RabbitMQ for EPEL 9

[Matthias Runge]

On 21/09/2022 12:49, Alfredo Moralejo Alonso wrote:



good question, and sorry to keep you waiting for this long time without
an answer. I changed roles in my job, leading to less and less time to
contribute. The messaging SIG did not attract the contributors I hoped
it would. I am looking for volunteers! Otherwise we should admit the
failure here and just close the SIG.


I'm sorry to contradict you but in the rabbitmq-server side of the SIG 
we have contributors taking care of updating rabbitmq server:


https://cbs.centos.org/koji/packageinfo?packageID=398 



You can simply:

# sudo dnf install -y centos-release-rabbitmq-38
#sudo dnf install -y rabbitmq-server

Best regards,



Thank you Alfredo. This is encouraging to hear! Thank you Peter for 
doing the build(s)!


Matthias
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Re: [Messaging] RabbitMQ for EPEL 9

[Matthias Runge]

On 03/09/2022 20:32, Robby Callicotte via epel-devel wrote:

Hello all,

I recently stumbled onto this bugzilla issue[1].  It has gone a couple of
months without a response from the assignee.  I know that the stalled package
request procedures can be started now, but I also see that RabbitMQ was built
by the Messaging SIG in the past.  So... Where should this get routed?  Is the
messaging SIG still active?  I see some info[2] saying that it is, but the
lack of response leads me to think that it may not be.


Thanks!


[1]  https://bugzilla.redhat.com/show_bug.cgi?id=2105791
[2] https://wiki.centos.org/SpecialInterestGroup/Messaging



Hi,

good question, and sorry to keep you waiting for this long time without 
an answer. I changed roles in my job, leading to less and less time to 
contribute. The messaging SIG did not attract the contributors I hoped 
it would. I am looking for volunteers! Otherwise we should admit the 
failure here and just close the SIG.


Matthias
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Re: Django stable RPMs

[Matthias Runge]

On 08/11/16 16:31, Brian Bouterse wrote:
> I believe the future of Django in EPEL is a topic that is being
> discussed on the EPSCO meetings last week and this week (18:00 UTC on
> Wednesdays in #fedora-meeting, iirc).
> 
> I'm hoping that even if a newer, 1.8 based Django package is added to
> EPEL6, that the existing one named Django14 can be kept for legacy
> usage. The Django14 package having that unconventional name would allow
> a new package to use the more conventional python-django name which is
> convenient.

I believe I can shed a light here:
- Django14 followed the old Django naming scheme in Fedora. Django was
renamed to python-django there.
- Django-1.4 was the old long term supported version and works with
pythons up to python 2.6
- Django14 should be retired IMO
- Django-1.8 (current long term supported version) requires python 2.7.
That means, we can not have a recent Django in EPEL6 with system python.
- The main reason not updating to Django-1.8 in EPEL7 is reviewboard. (I
don't know the state of askbot currently, Fedora has ask.fedoraproject.org).
- Maintaining a django version, which was retired upstream becomes more
and more a pain, esp. if it's not part of your job to keep it alive.

Matthias
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

[EPEL-devel] Re: nodejs update

[Matthias Runge]

On 23/08/16 03:48, Stephen Gallagher wrote:
>> On Mon, Aug 22, 2016 at 4:23 PM, Stephen Gallagher 
>> >
>> Let me (or open a rel-eng ticket) when you want a epel7-nodejs6 side
>> tag to build it into. Will make it easier so you don't need to deal
>> with a billion build overrides etc.
>>
> 
> I'm not sure that will be strictly necessary; we figured out during the 
> Fedora process that once we moved to the bundled NPM, we only had about a 
> dozen packages that actually needed a rebuild to support Node.js 6.x (just 
> the ones that build a native, archful module).
> 
> But yes, I'll make sure to let you know if we decide it needs a side-tag.


Nodejs 6 bundles openssl 1.0.2.h, where RHEL/CentOS have a much older
version. That hasn't been an issue in Fedora; For CentOS, there is a
build for Node.js 4 in cbs, including a patch to unbundle openssl and to
make it work with the way older lib.

Unless we have a comparable patch (if possible) for Node version 6,
maybe we should stick with version 4?

Matthias
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org

[EPEL-devel] Re: EPEL Meeting 2016-03-08

[Matthias Runge]

On 09/03/16 20:33, Kevin Fenzi wrote:

>>  -b- We re-review Django14 and put it in. However there are 4+
>> security problems which can't be fixed without a major version move.
>> Because of this , the package may not pass review.

Because it has been retired upstream, I'm not sure if anyone really
looked at that, if there are 2 or really 4 security issues. The most
recent two might have fixes to be even backportable.

For reference, the request for re-review
is here: https://bugzilla.redhat.com/show_bug.cgi?id=1316068
> 
> We actually don't need to review it... if it's been retired less than 2
> weeks, we can just unretire it. We do need someone(s) to take over
> point of contact though. 
> 
> I guess I could do it, but is anyone else willing first? :) 

Actually, I made the mistake and did not retire it in f22-f24; it
doesn't make sense there at all. Could we consider the package as not
being retired at all?

Once the EPEL6 situation is solved, I should retire it on the previously
named branches.
> 
>>  -c- We skip re-review in this case and put the package back in. We do
>> so with an explicite end of life of 180 days (or 7.3 if that is
>> sooner) with either -a- happening or a python27 is packaged AND a
>> django 1.8 AND the packages requiring 1.4 are updated to 1.8.
> 
> Yeah, a time limit might be nice, but not sure how long all the various
> projects need + how long it will take to bring up a python27 + django1.8
> 
> Are any folks willing to work on this?
> 

Bringing in python2.7 and Django-1.8 would be the safest bet (in terms
of future stability), but that requires a bit of work, and just bringing
in python2.7 and Django-1.8 is the smallest portion here.

Matthias
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org

Re: [EPEL-devel] el7 liblockfile

[Matthias Runge]

On Mon, Feb 16, 2015 at 10:25:41PM +, Peter Robinson wrote:
 On Mon, Feb 16, 2015 at 10:09 PM, Chuck Anderson c...@wpi.edu wrote:
  liblockfile is installed with CentOS 7 and it gets updated by EPEL 7.
  Is that supposed to happen?
 
 No it's not. Added the maintainer [1] who requested it to cc: so he
 can outline why but I'm not sure why our requests are just being
 approved by the process-git-requests process.
 
 Peter
 
 [1] https://bugzilla.redhat.com/show_bug.cgi?id=601577

Ugh. Good catch! It looks like liblockfile was added to EPEL7 by
accident.

I opened a ticket[1].

Since that package didn't change for a long time, I wouldn't expect any
real difference between those two.

Matthias

[1] https://fedorahosted.org/rel-eng/ticket/6107
-- 
Matthias Runge mru...@matthias-runge.de
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

Re: EPEL Deprecated Django 1.5 in

[Matthias Runge]

On Wed, Oct 01, 2014 at 01:28:04PM +0300, Dionysis Grigoropoulos wrote:
 Hello,
 
 as far as I can see, EPEL 7 currently provides packages `python-django`
 and `python-django15` being versions 1.6.5 and 1.5.6 respectively. EPEL
 6 provides `python-django15` and `Django14` being 1.5.6 and 1.4.14.
 
 According to the Django documentation [1], since version 1.7 was
 released, version 1.5 won't receive security updates anymore. Wouldn't
 it be better to remove python-django15 from both repos and add 1.4
 (current LTS which will be supported at least until March of 2015) to
 EPEL 7 and 1.6 to epel 6?

Thank you for the heads-up.

I recently retired python-django15 from Fedora 21+, and I should do the
same ASAP for EPEL6 and EPEL7 as well.

(THIS IS THE ANNOUNCEMENT ABOUT REMOVAL in about two weeks.)

About adding Django14 to EPEL7: Since there is currently Django-1.6,
which is supported until March 2015 as well, I don't see any pro to add
another Django version. The other reason is: having two versions in the
same release is just a pain; I'd try to avoid this; they need to be
installable in parallel. We had that, it didn't work very well.

Does this make any sense?
Matthias
-- 
Matthias Runge mru...@matthias-runge.de
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

Re: EPEL python26 status in 5

[Matthias Runge]

On 21/08/14 05:20, Orion Poplawski wrote:

Just trying to see what's the status of the python26 package in EPEL5.
It doesn't appear to have been updated for a while:

* Wed Nov 07 2012 Jeffrey Ness jeffrey.n...@rackspace.com - 2.6.8-2
- Patch 121 forces sys.platform to linux2
   related to issue http://bugs.python.org/issue12326

python 2.6.9 was released but not updated -
https://www.python.org/download/releases/2.6.9/

Upstream has declared it dead, although it is in RHEL6 and so presumably
receives attention from RedHat there.

There are several open CVE bugs against it.  Time to retire or try to
sync to the RHEL6 package?

https://bugzilla.redhat.com/buglist.cgi?bug_status=NEWbug_status=ASSIGNEDclassification=Fedoracomponent=python26list_id=2761524product=Fedora%20EPELquery_format=advanced


- Orion

PS - I started looking into this to see if it is worth trying to create
a python26-django14 package for EL5 to support cobbler-web.


As far as I concern, Django-1.4 will be supported until March 2015[1].

But I must admit, I haven't touched any EL5 since ages. There is no 
Django package in EPEL5 and I don't have the intention to change that.

On the other side, it should be pretty straightforward to get a build.


[1] 
https://docs.djangoproject.com/en/1.6/internals/release-process/#lts-releases


Matthias
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

Re: EPEL Status of openstack-nova

[Matthias Runge]

On Sat, Apr 12, 2014 at 10:33:50AM +0300, Anssi Johansson wrote:
 
 I'm still of the opinion that if a package in EPEL is no longer
 maintained and it has known security issues, it should be removed
 from EPEL.

That will happen, in the next few weeks, as far as I know.

Matthias
-- 
Matthias Runge mru...@matthias-runge.de
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

Re: EPEL requesting updated status of Django package

[Matthias Runge]

On 01/08/2014 01:37 AM, Jason Helfman wrote:
 Hi,
 
 I was wondering if there are any efforts being made into getting the Django 
 package updated for the epel repository?
 
 Currently it is Django14, and we are running an application that requires at 
 a minimum 15.
 
 Any update is appreciated with any eta.
 
 Thanks very much!
 
 -jgh
 
Good question.

First of all, Django is a fast moving target, with a release in about
every 6-9 months; EPEL shouldn't move at all. Version upgrades are
deprecated during a release in general.

There used to be a Django package, which was Django-1.3. That version is
deprecated and the package is retired. What you currently get is
Django14, which we should consider as deprecated, too. Still we have a
huge bunch of packages depending on that version.

Options are:
- deprecate Django in general in EPEL and remove it, because we can not
upgrade software packages; we could provide it through Software collections
- make an exception and upgrade Django packages on a regular basis; this
might (will) break depending packages, which can't keep the pace of
Django itself. We even could decide, that we drop notorious broken packages
- introduce a new package Django15 (and probably Django16, too). That is
not ideal, too. Either we need to build every depending package for each
version, or the user has to know the right version and has to install
the right Django version manually. Not ideal either :-/
yum is apparently not smart enough to solve dependencies right.

Even in Fedora, which moves way faster than EPEL, we currently have
Django-1.5.x and not Django-1.6 because depending packages don't support
latest Django versions.

tl;dr There is currently no work being done, and I don't know a good
answer to that question. In any case, it will get messy.

Matthias
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

EPEL Django deprecated

[Matthias Runge]

Hey, just a heads up

the package Django has been deprecated or EPEL5 and EPEL6.
On EPEL6, you can use Django14 as well, if you don't require Django in
version 1.3. Please note, the latter does not receive security updates
any more and contains at least one known weakness.

For EL5 it's not that simple. Django-1.1 is ways older; I don't know,
how many known security issues exist. Newer Django versions require
newer python there.
-- 
Matthias Runge mru...@matthias-runge.de
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel