[EPEL-devel] Fedora EPEL 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 34 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-06b243cced guacamole-server-1.0.0-1.el6 14 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-b4ada0648b putty-0.71-1.el6 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-62f9745b71 drupal7-7.65-1.el6 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-13e2a65b5e wordpress-5.1.1-4.el6 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-8d5207833a ntfs-3g-2017.3.23-11.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing milter-regex-2.4-1.el6 Details about builds: milter-regex-2.4-1.el6 (FEDORA-EPEL-2019-96b606f063) Milter plug-in for regular expression filtering Update Information: This update fixes a bug where an action might not be triggered if the configuration file specifies multiple expressions (as opposed to a single complex expression) associated with that action. There are also additional command-line options for setting pipe user, group, and permissions, the default maximum log level is now LOG_INFO (i.e. excluding LOG_DEBUG) and the syslog facility can now be set using the -f option. ChangeLog: * Wed Apr 3 2019 Paul Howarth - 2.4-1 - Update to 2.4 - Bug fix: for actions followed by multiple expressions (not just one arbitrarily complex expression), when multiple expressions become defined during the same sequence point, but with different values (e.g. one true, another false), depending on the expression order, the action might not be taken, when it should be - Add -f option to set syslog facility * Sun Mar 24 2019 Paul Howarth - 2.2-3 - Fix ownership of /var/spool/milter-regex so that dac_override isn't needed (#1678040) * Fri Aug 24 2018 Paul Howarth - 2.2-1 - Update to 2.2 - Add -U, -G, and -P options to set pipe user, group, and permissions * Fri Aug 24 2018 Paul Howarth - 2.1-1 - Update to 2.1 - Default maximum log level to 6 (LOG_INFO), i.e. exclude LOG_DEBUG - Upstream switched from benezedrine.cx to bezendrine.ch * Fri Jan 26 2018 Paul Howarth - 2.0-11 - List build requirements one per line - Don't use full paths for commands in scriptlets, to improve readability - Drop legacy Group: tag - Specify all build requirements ___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing:
Age URL
232 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d
condor-8.6.11-1.el7
40 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f8311ec8a2
tor-0.3.5.8-1.el7
34 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9c2c40e3df
guacamole-server-1.0.0-1.el7
14 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-a578ca80ae
putty-0.71-1.el7
13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-317c9a2f81
drupal7-7.65-1.el7
12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-15679bf3f9
wordpress-5.1.1-4.el7
9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-114610bd18
golang-googlecode-go-crypto-0-0.15.20190324gitb7391e9.el7
8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d2c1368294
cinnamon-3.6.7-5.el7
6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f1efad2982
aria2-1.34.0-4.el7
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-7bae341677
chromium-73.0.3683.86-2.el7
4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c9cd2d9a6c
ntfs-3g-2017.3.23-11.el7
0 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-50a6a1ddfd
afflib-3.7.18-2.el7
The following builds have been pushed to Fedora EPEL 7 updates-testing
js8call-1.0.0-2.el7
milter-regex-2.4-1.el7
perl-No-Worries-1.6-1.el7
python-capturer-2.4-5.el7
python-coloredlogs-10.0-7.el7
python-enlighten-1.2.0-1.el7
python-humanfriendly-4.18-1.el7
python-pytest-repeat-0.7.0-1.el7
python-vcstool-0.1.40-1.el7
python-verboselogs-1.7-4.el7
python3-chardet-2.3.0-6.el7
zabbix40-4.0.6-1.el7
Details about builds:
js8call-1.0.0-2.el7 (FEDORA-EPEL-2019-af32367058)
Amateur Radio message passing using FT8 modulation
Update Information:
Initial release of js8call for Fedora.
References:
[ 1 ] Bug #1694735 - Review Request: js8call - Amateur Radio message passing
using FT8 modulation
https://bugzilla.redhat.com/show_bug.cgi?id=1694735
milter-regex-2.4-1.el7 (FEDORA-EPEL-2019-4e5a28e476)
Milter plug-in for regular expression filtering
Update Information:
This update fixes a bug where an action might not be triggered if the
configuration file specifies multiple expressions (as opposed to a single
complex expression) associated with that action. There are also additional
command-line options for setting pipe user, group, and permissions, the default
maximum log level is now LOG_INFO (i.e. excluding LOG_DEBUG) and the syslog
facility can now be set using the -f option.
ChangeLog:
* Wed Apr 3 2019 Paul Howarth - 2.4-1
- Update to 2.4
- Bug fix: for actions followed by multiple expressions (not just one
arbitrarily complex expression), when multiple expressions become defined
during the same sequence point, but with different values (e.g. one true,
another false), depending on the expression order, the action might not be
taken, when it should be
- Add -f option to set syslog facility
* Sun Mar 24 2019 Paul Howarth - 2.2-3
- Fix ownership of /var/spool/milter-regex so that dac_override isn't needed
(#1678040)
* Fri Feb 1 2019 Fedora Release Engineering - 2.2-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
* Fri Aug 24 2018 Paul Howarth - 2.2-1
- Update to 2.2
- Add -U, -G, and -P options to set pipe user, group, and permissions
* Fri Aug 24 2018 Paul Howarth - 2.1-1
- Update to 2.1
- Default maximum log level to 6 (LOG_INFO), i.e. exclude LOG_DEBUG
- Upstream switched from benezedrine.cx to bezendrine.ch
* Fri Jul 13 2018 Fedora Release Engineering - 2.0-13
- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
* Thu Feb 8 2018 Fedora Release Engineering - 2.0-12
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
* Fri Jan 26 2018 Paul Howarth - 2.0-11
- Drop dependencies on systemd-units and use %{?systemd_requires} instead
- Use forward-looking conditionals
- List build requirements one per line
- Don't use full paths for commands in scriptlets, to improve readability
- Drop legacy Group: tag
* Thu Aug 3 2017 Fedora Release Engineering - 2.0-10
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Binutils_Mass_Rebuild
* Wed Jul 26 2017 Fedora Release Engineering - 2.0-9
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass
[EPEL-devel] Re: Major upgrade for singularity in EPEL
Thanks very much for your reply, Stephen. I have already done scratch builds for EPEL 6 & 7 so that's not a problem. The primary reason for upgrading to singularity-3 is that development has stopped on singularity-2 and users have been asking me to upgrade because they want some of the newer features. I will go ahead and create a pagure issue. Dave On Wed, Apr 03, 2019 at 06:04:42AM -0400, Stephen John Smoogen wrote: > On Tue, 2 Apr 2019 at 18:29, David Dykstra wrote: > > singularity-3.1.1 was just released upstream, and I think it is at this > > point compatible enough with singularity-2 to upgrade it in EPEL6 and > > EPEL7. I have had singularity-3 releases in Fedora for over 3 months, > > but have been holding off on EPEL upgrades because it is a complete > > rewrite in another language (golang instead of C) and initially had some > > incompatibilities. There is no more development happening in > > singularity-2, although the startup company that supplies long term > > support for singularity-2 (Sylabs) has promised to release any security > > patches that it develops. > > > > Is there any objection, or any process that needs to be gone through, in > > order to do this type of major upgrade in EPEL? > > I would start by doing scratch builds to see if there are versions of > go which will compile the code in EPEL-6 and EPEL-7. I am expecting > EPEL-6 might be too old and is only got a 18 months of life left so > keeping it at -2 and using the security updates will be the case. > EPEL-7 might be possible but not sure. > > After that, the process for doing it in EPEL would be to email this > list with the reasons why an upgrade needs to be done, and then put in > a ticket https://pagure.io/epel/issues that we will discuss at the > next meeting. EPSCO would then probably give approval and you would > then send one more email announcing it is happening and bob's your > uncle. ___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Major upgrade for singularity in EPEL
On Tue, 2 Apr 2019 at 18:29, David Dykstra wrote: > > Hello, > > singularity-3.1.1 was just released upstream, and I think it is at this > point compatible enough with singularity-2 to upgrade it in EPEL6 and > EPEL7. I have had singularity-3 releases in Fedora for over 3 months, > but have been holding off on EPEL upgrades because it is a complete > rewrite in another language (golang instead of C) and initially had some > incompatibilities. There is no more development happening in > singularity-2, although the startup company that supplies long term > support for singularity-2 (Sylabs) has promised to release any security > patches that it develops. > > Is there any objection, or any process that needs to be gone through, in > order to do this type of major upgrade in EPEL? > I would start by doing scratch builds to see if there are versions of go which will compile the code in EPEL-6 and EPEL-7. I am expecting EPEL-6 might be too old and is only got a 18 months of life left so keeping it at -2 and using the security updates will be the case. EPEL-7 might be possible but not sure. After that, the process for doing it in EPEL would be to email this list with the reasons why an upgrade needs to be done, and then put in a ticket https://pagure.io/epel/issues that we will discuss at the next meeting. EPSCO would then probably give approval and you would then send one more email announcing it is happening and bob's your uncle. > Thanks, > > Dave > ___ > 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://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org -- Stephen J Smoogen. ___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
