Fixes most of the SELinux issues but as I use some non-default jails, I also get these:

type=AVC msg=audit(1623327223.709:6536): avc:  denied  { watch } for  pid=118968 comm="fail2ban-server" path="/var/log/secure" dev="dm-0" ino=662190 scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:object_r:var_log_t:s0 tclass=file permissive=0
type=AVC msg=audit(1623327223.713:6537): avc:  denied  { watch } for  pid=118968 comm="fail2ban-server" path="/var/log/httpd" dev="dm-0" ino=658553 scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:object_r:httpd_log_t:s0 tclass=dir permissive=0
type=AVC msg=audit(1623327223.713:6538): avc:  denied  { watch } for  pid=118968 comm="fail2ban-server" path="/var/log/httpd/access_log" dev="dm-0" ino=662142 scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:object_r:httpd_log_t:s0 tclass=file permissive=0

I'm going to have to downgrade my bacula server back down to 9.x because this version requires a significant database update as described in the release notes, and the database upgrade script for mysql is not working for me (I'm currently on database version 16 and the script is failing to remove index JobId on the File table).

The App-Cme issue looks like a valid warning (for a duplicate "verbose" option), which was added recently.

GLD 0.106 introduced use of Term::ReadKey to get the terminal width, so it was necessary to run tests in "expect" to get them to work. This caused a lot of problems like the ones you saw, so GLD 0.107 reverts that change.

proftpd is a server, not a client. You start it by doing:

$ sudo systemctl start proftpd

You can check its status by doing:

$ sudo systemctl status proftpd

It looks like your last attempt at starting it via sudo worked, so you may need to kill that one if it's still running.

@jpbn, I installed this on a fresh F32 box and it worked straight away for me. Have you made any changes to the way the server is started? If you run rpm -V proftpd does it report anything other than /etc/ftpusers?

What do you get from ls -lZ /etc/proftpd.conf?

Here's what I get:

[root@tycho ~]# ls -lZ /etc/proftpd.conf 
-rw-r-----. 1 root root system_u:object_r:ftpd_etc_t:s0 6485 May 31 17:35 /etc/proftpd.conf
[root@tycho ~]# rpm -V proftpd
S.5....T.  c /etc/ftpusers
[root@tycho ~]# ls -lZ /etc/proftpd.conf 
-rw-r-----. 1 root root system_u:object_r:ftpd_etc_t:s0 6485 May 31 17:35 /etc/proftpd.conf

Is there a reason this update isn't being pushed to stable?

Update details: "Rebased to version 2.5.2"? A bit of finger trouble there...

perl-Compress-Raw-Lzma records the version of the LZMA library it was built against and there can be issues if the run-time version is different, hence the versioned dependency. Rebuilding it against the new xz and having a single update for both is exactly the right thing to do.

milter-greylist itself hasn't had a release since 2016 but on the other hand it could be regarded as stable software that doesn't need to be frequently updated. It certainly still works and I'm comfortable running it on my own mail server.

I've intentionally compiled it without GeoIP support because MaxMind stopped releasing updates for the legacy GeoIP databases about a year ago and hence any GeoIP data is quite likely to be wrong. This would get worse during the long lifetime of EL8.

Updating to libmaxminddb rather than GeoIP won't help either, because MaxMind have changed the license terms for their current databases and we can no longer redistribute them.

OK so I see there is this update plus for GeoIP-GeoLite-data, both created by Morten Stevens. So it seems like the options are either that Morten pushes both updates again or Thomas bumps and rebuilds both packages and then creates a new combined update for them both.

I'm fine either way.


If you're happy to maintain it and deal with the bugs you'll get about it being broken and/or out of date, by all means push it to EPEL-8. But make an update containing both GeoIP and GeoIP-GeoLite-data, don't just push GeoIP on its own.

Hi, (I'm Paul Howarth by the way) Re: GeoIP-GeoLite-data, it should be included in the same update as GeoIP. Cheers, Paul.

If you're going to ship this package, you'll need to build GeoIP-GeoLite-data and add that to the update because otherwise GeoIP will have broken dependencies.

If you're not sure about whether you can remove a package after a year or so (I think you can, but I also think it's against the spirit of EPEL to provide something now knowing that you intend to remove it long before the end of life of EL-8), you might want to discuss it on the EPEL devel list.

Built perl-Crypt-DH successfully using this package.

Used this package to build perl-Regexp-Assemble successfully.

BZ#1761961 [RFE] EPEL-8 branch for perl-Test-File-Contents

Local build of perl-Module-CPANTS-Analyse works with this.

Built perl-Test-Vars successfully using this.

BZ#1754852 [RFE] EPEL8 branch of perl-Test-Output

Never mind, I'll do a separate update for perl-PPIx-Utilities-1.001000-35.el8 and perl-Perl-Critic-1.134-5.el8.

perl-PPIx-QuoteLike and perl-PPIx-Regexp look fine to me.

BZ#1754255 [RFE] EPEL-8 branch for perl-PPIx-QuoteLike (and perl-PPIx-Regexp)