[EPEL-devel] Fedora EPEL 7 updates-testing report

2021-07-18 Thread updates
The following Fedora EPEL 7 Security updates need testing:
 Age  URL
  52  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-1f259a45ef   
openjpeg2-2.3.1-11.el7
   7  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-ddb4fcb22a   
opendmarc-1.4.1.1-3.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

proxychains-ng-4.14-1.el7

Details about builds:



 proxychains-ng-4.14-1.el7 (FEDORA-EPEL-2021-c0b3e6fc73)
 Redirect connections through proxy servers

Update Information:

Initial EPEL release

ChangeLog:


References:

  [ 1 ] Bug #1689606 - proxychains-ng-4.14 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1689606
  [ 2 ] Bug #1952807 - [epel8] [epel7] Please branch and build the 
proxychains-ng package for epel
https://bugzilla.redhat.com/show_bug.cgi?id=1952807


___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[EPEL-devel] Re: Do we need Mock supported on EL7?

2021-07-18 Thread Pavel Raiskup
On Saturday, July 17, 2021 3:18:02 PM CEST Stephen John Smoogen wrote:
> On Fri, 16 Jul 2021 at 17:59, Pavel Raiskup  wrote:
> >
> > We touched this topic several times before in our team.  Perhaps we should 
> > move
> > on and do it...  it would simplify a development (the yum/dnf hacks,
> > legacy systemd-nspawn hacks, podman requirement for building Fedora, etc.).
> >
> > I created an issue [1], can you please vote there if you are concerned?  If 
> > you
> > have a good argument for keeping the support, please write here or there (or
> > both).
> >
> > [1] https://github.com/rpm-software-management/mock/issues/755
> >
> 
> First off, what does this mean:
> 
> 1. you can't build EL7 packages anymore with mock? AKA we would need
> to stop building EPEL7

No.  E.g. Copr builders are on the latest Mock, on Fedora 34, and they build EL7
just fine.

> 2. you can't use "mock" on systems after the XYZ version?

Yes, Mock version XYZ will not be available on EL7. 

> Going from the graphs of growth, most of EL growth has been in EL7
> since last year. That said.. I expect that if there is a version which
> is 'known' to be the last working version of mock then people needing
> it can 'keep' that version on those systems as long as they need.

Exactly.
Pavel

> 
> > Thank you,
> > Pavel
> >
> >
> > ___
> > 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 on the list, report it: 
> > https://pagure.io/fedora-infrastructure
> 
> 
> 
> -- 
> Stephen J Smoogen.
> I've seen things you people wouldn't believe. Flame wars in
> sci.astro.orion. I have seen SPAM filters overload because of Godwin's
> Law. All those moments will be lost in time... like posts on  BBS...
> time to reboot.
> ___
> 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 on the list, report it: 
> https://pagure.io/fedora-infrastructure
> 



___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[EPEL-devel] Re: Do we need Mock supported on EL7?

2021-07-18 Thread Pavel Raiskup
On Saturday, July 17, 2021 9:08:48 PM CEST Nico Kadel-Garcia wrote:
> On Sat, Jul 17, 2021 at 9:19 AM Stephen John Smoogen  wrote:
> >
> > On Fri, 16 Jul 2021 at 17:59, Pavel Raiskup  wrote:
> > >
> > > We touched this topic several times before in our team.  Perhaps we 
> > > should move
> > > on and do it...  it would simplify a development (the yum/dnf hacks,
> > > legacy systemd-nspawn hacks, podman requirement for building Fedora, 
> > > etc.).
> > >
> > > I created an issue [1], can you please vote there if you are concerned?  
> > > If you
> > > have a good argument for keeping the support, please write here or there 
> > > (or
> > > both).
> > >
> > > [1] https://github.com/rpm-software-management/mock/issues/755
> > >
> >
> > First off, what does this mean:
> >
> > 1. you can't build EL7 packages anymore with mock? AKA we would need
> > to stop building EPEL7
> > 2. you can't use "mock" on systems after the XYZ version?
> >
> > Going from the graphs of growth, most of EL growth has been in EL7
> > since last year. That said.. I expect that if there is a version which
> > is 'known' to be the last working version of mock then people needing
> > it can 'keep' that version on those systems as long as they need.
> 
> I've done backports of mock for some operating systems, to get updated
> versions of mock-core-configs on Amazon Linux 2 for example.  You can
> still compile older operating systems on modern operating systems. The
> bigger problem is operating systems like Amazon Linux 2, or RHEL,
> where the basic software repositories are not publicly accessible to
> use on other systems. Either you have to use mock on those operating
> systems to build for them, or you need to set up an internal yum
> mirror with tools ike
> https://github.com/nkadel/nkadel-rsync-scripts/blob/master/reposync-rhel-6.sh
> .

We can build RHEL 7 just fine on RHEL 8 or on Fedora, without a local mirror.
https://github.com/rpm-software-management/mock/wiki/Feature-rhelchroots

If we faced with bottlenecks, going with bootstrap chroot or even bootstrap
image should help nowadays.

> EL 8 had its adoption poisoned by some very unwelcome choices by Red
> Hat. That's a long rant of its own, one I've stated before in the
> CentOS groups. But it means that EL 7 is going to be around a lot
> longer than people may wish. If we can keep mock working for EL 7 for
> longer, I'd be all on board. I especially want it for Amazon Linux 2,
> where I provided some support for the Samba developers to port current
> Samba releases to that EL 7 based but somewhat distinct environment.
> (python3 is python 3.7 there, and they have python 3.8 available:
> stuff built for RHEL 7 or CentOs 7 does not behave well there!)

The Mock on EL 7 should stay working for the extended life period.  Just
that it would not get updates with all bugfixes and new features.

Pavel


> Nico Kadel-Garcia
> ___
> devel mailing list -- de...@lists.fedoraproject.org
> To unsubscribe send an email to 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/de...@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
> 



___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[EPEL-devel] Re: gcc-gnat

2021-07-18 Thread Robert Scheck
Hello Erick,

On Mon, 13 Jul 2020, Erick Wittman wrote:
> I am using CentOS 8 and am using various packages in the EPEL
> repository. I am interested in seeing gcc-gnat added to EPEL.
> 
> I cannot find a current Fedora maintainer listed for this package, but
> it is available in Fedora (at least in version 32).  Are there any EPEL
> maintainers who are interested in creating an EPEL version of this package?

given I'm replying to an old thread, I'm not really sure if you're still
interested, but https://bugzilla.redhat.com/show_bug.cgi?id=1983416 is what
I now submitted for a package review. Yes, the package might not be perfect
because /usr/bin/gcc can not be used directly, but there are alternative
GCC frontends such as 'gnatgcc' that worked (at least for me) as expected.

As it can be seen from the RHBZ dependencies, I'm caring about Objective-C
support, but I thought it might be worth to cover all missing parts. As far
as I can tell "hello world" worked for all built languages and the gcc-epel
package can be used also for scenarios with a single compiler but multiple
programming languages, e.g. by using CC=gnatgcc (used inside the package to
achieve bootstrapping).


Regards,
  Robert


pgpydR8Y7Va4R.pgp
Description: PGP signature
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure