[EPEL-devel] How to retire/delete an EPEL branch?
I received a bug[1] asking to remove EPEL7 branch, as the package LibRaw, is already in RHEL. How should I do that? Regards, 1. https://bugzilla.redhat.com/show_bug.cgi?id=1526701 -- Ding-Yi CHEN Software Engineer, Globalization Group Red Hat Asia-Pacific Pty Ltd dc...@redhat.com Twitter: @redhatway | Instagram: @redhatinc | Snapchat: @redhatsnaps ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Committee
Dear all, You are kindly invited to the meeting: EPEL Steering Committee on 2018-01-10 from 18:00:00 to 19:00:00 GMT At fedora-meet...@irc.freenode.net The meeting will be about: The EPEL Steering Committee will have a weekly meeting to cover current tasks and problems needed to keep EPEL going. Source: https://apps.fedoraproject.org/calendar/meeting/8724/ ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 1037 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-1087 dokuwiki-0-0.24.20140929c.el7 800 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-dac7ed832f mcollective-2.8.4-1.el7 382 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-04bc9dd81d libbsd-0.8.3-1.el7 279 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-d241156dfe mod_cluster-1.3.3-10.el7 111 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-e27758bd23 libmspack-0.6-0.1.alpha.el7 48 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-e64eeb6ece nagios-4.3.4-5.el7 37 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-d704442ae7 qpid-cpp-1.37.0-1.el7 18 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-957aa05f33 heketi-5.0.1-1.el7 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-8d57a2487b monit-5.25.1-1.el7 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-753e392fc4 xrdp-0.9.5-1.el7 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-2e2d08b1ff awstats-7.6-4.el7 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-49ca8440a1 gifsicle-1.90-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing easy-rsa-3.0.3-1.el7 librdkafka-0.11.3-1.el7 mint-x-icons-1.4.6-5.el7 mint-y-icons-1.1.3-2.el7 paper-icon-theme-1.4.0-2.el7 php-bartlett-php-compatinfo-db-1.28.0-1.el7 python-pymod2pkg-0.11.0-1.el7 rdopkg-0.45.0-5.el7 rho-0.0.31-1.el7 tcl-tclnagios-1.3-5.el7 Details about builds: easy-rsa-3.0.3-1.el7 (FEDORA-EPEL-2018-f3e8fb0991) Simple shell based CA utility Update Information: Update to 3.0.3 for modern openssl and ciphers. librdkafka-0.11.3-1.el7 (FEDORA-EPEL-2018-e49cc220fa) The Apache Kafka C library Update Information: Default changes Change default queue.buffering.max.kbytes and queued.max.message.kbytes to 1GB (#1304) win32: Use sasl.kerberos.service.name for broker principal, not sasl.kerberos.principal (#1502) Enhancements Default producer message offsets to OFFSET_INVALID rather than 0 new nuget package layout + debian9 librdkafka build (#1513, @mhowlett) Allow for calling rd_kafka_queue_io_event_enable() from the C++ world (#1483, @akhi3030) rdkafka_performance: allow testing latency with different size messages (#1482, @tbsaunde) Fixes Improved stability on termination (internal queues, ERR__DESTROY event) offsets_for_times() return ERR__TIMED_OUT if brokers did not respond in time Let list_groups() return ERR__PARTIAL with a partial group list (#1508) Properly handle infinite (-1) rd_timeout:s throughout the code (#1539) Fix offsets_store() return value when at least one valid partition portability: rdendian: add le64toh() alias for older glibc (#1463) Add MIPS build and fix CRC32 to work on big endian CPUs (@andoma, closes #1498) osx: fix endian checking for software crc32c Fix comparison in rd_list_remove_cmp (closes #1493) stop calling cnd_timedwait() with a timeout of 0h (#1481, @tbsaunde) Fix DNS cache logic broker.address.ttl (#1491, @dacjames) Fix broker thread "hang" in CONNECT state (#1397) Reset rkb_blocking_max_ms on broker DOWN to avoid busy-loop during CONNECT (#1397) Fix memory leak when producev() fails (#1478) Raise cmake minimum version to 3.2 (#1460) Do not assume LZ4 worst (best?) case 255x compression (#1446 by @tudor) Fix ALL_BROKERS_DOWN re-generation (fix by @ciprianpascu, #1101) rdkafka-performance: busy wait to wait short periods of time source: https://github.com/edenhill/librdkafka/releases mint-x-icons-1.4.6-5.el7 (FEDORA-EPEL-2018-5e92e7eb55) Icon theme for Linux Mint Update Information: - Use rpm filetriggers on Fedora and/or RHEL >= 8 mint-y-icons-1.1.3-2.el7 (FEDORA-EPEL-2018-d86af40c33) The Mint-Y icon theme Update Information: - Use rpm filetriggers on Fedora and/or RHEL >= 8
[EPEL-devel] Fedora EPEL 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 910 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7168 rubygem-crack-0.3.2-2.el6 800 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-e2b4b5b2fb mcollective-2.8.4-1.el6 771 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-35e240edd9 thttpd-2.25b-24.el6 382 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-e3e50897ac libbsd-0.8.3-2.el6 111 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-4c76ddcc92 libmspack-0.6-0.1.alpha.el6 30 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-6aaee32b7e optipng-0.7.6-6.el6 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-6e4ce19598 monit-5.25.1-1.el6 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-37c8dbd6f1 gifsicle-1.90-1.el6 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-8c9006d462 heimdal-7.5.0-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing easy-rsa-3.0.3-1.el6 rho-0.0.31-1.el6 Details about builds: easy-rsa-3.0.3-1.el6 (FEDORA-EPEL-2018-4a6cbdd222) Simple shell based CA utility Update Information: Update to 3.0.3 for modern openssl and ciphers. rho-0.0.31-1.el6 (FEDORA-EPEL-2018-4846ddf8ae) An SSH system profiler Update Information: # Testing Rho To set up Rho, you create profiles that control how to run each scan. - Authentication profiles contain user credentials for a user with sufficient authority to complete the scan (for example, a root user or one with root-level access obtained through -sudo privilege escalation). - Network profiles contain network identifiers (for example, a hostname, IP address, or range of IP addresses) and the authentication profiles to be used for a scan. Complete the following steps, repeating them as necessary to access all parts of your environment that you want to scan: 1. Create at least one authentication profile with root-level access to Rho: ``` rho auth add --name auth_name --username root_name(--sshkeyfile key_file | --password) ``` a. At the Rho vault password prompt, create a new Rho vault password. This password is required to access the encrypted Rho data, such as authentication and network profiles, scan data, and other information. b. If you did not use the sshkeyfile option to provide an SSH key for the username value, enter the password of the user with root-level access at the connection password prompt. For example, for an authentication profile where the authentication profile name is roothost1, the user with root-level access is root, and the SSH key for the user is in the path ~/.ssh/id_rsa, you would enter the following command: ``` rho auth add --name roothost1 --username root --sshkeyfile ~/.ssh/id_rsa ``` You can also use the sudo-password option to create an authentication profile for a user with root-level access who requires a password to obtain this privilege. You can use the sudo-password option with either the sshkeyfile or the password option. For example, for an authentication profile where the authentication profile name is sudouser1, the user with root-level access is sysadmin, and the access is obtained through the password option, you would enter the following command: ``` rho auth add --name sudouser1 --username sysadmin --password --sudo-password ``` After you enter this command, you are prompted to enter two passwords. First, you would enter the connection password for the username user, and then you would enter the password for the sudo command. 2. Create at least one network profile that specifies one or more network identifiers, such as a host name, an IP address, a list of IP addresses, or an IP range, and one or more authentication profiles to be used for the scan: ``` rho profile add --name profile_name --hosts host_name_or_file --auth auth_name ``` For example, for a network profile where the name of the network profile is mynetwork, the network to be scanned is the 192.0.2.0/24 subnet, and the authentication profiles that are used to run the scan are roothost1 and roothost2, you would enter the following command: ``` rho profile add --name mynetwork --hosts 192.0.2.[1:254] --auth roothost1 roothost2 ``` You can also use a file to pass in the network identifiers. If you use a file to enter multiple network identifiers, such as multiple individual IP addresses, enter each on a single line. For example, for a network profile where the path to this file is /home/user1/hosts_file, you would enter the following command: ``` rho profile add
