[EPEL-devel] Fedora EPEL 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 949 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5620/bugzilla-3.4.14-2.el6 168 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1616/puppet-2.7.26-1.el6 39 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3434/pylint-1.3.1-1.el6,python-astroid-1.2.1-2.el6,python-logilab-common-0.62.1-2.el6 14 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4005/nginx-1.0.15-11.el6 14 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4008/cross-binutils-2.23.51.0.3-1.el6.1 12 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4057/moodle-2.5.9-1.el6 8 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4151/lsyncd-2.1.4-4.el6.1.1 8 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4144/nodejs-0.10.33-1.el6,libuv-0.10.29-1.el6 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4165/python-eyed3-0.7.4-5.el6 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4176/clamav-0.98.5-1.el6 5 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4237/drupal7-7.34-1.el6 5 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4192/wordpress-4.0.1-1.el6 5 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4233/drupal6-6.34-1.el6 2 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4242/facter-1.6.18-8.el6 2 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4243/asterisk-1.8.32.1-1.el6 2 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2069/php-channel-phpseclib-1.3-1.el6,php-sabredav-Sabre_VObject-2.1.4-2.el6,php-sabredav-Sabre_HTTP-1.7.11-1.el6,php-sabredav-Sabre_DAVACL-1.7.9-1.el6,php-sabredav-Sabre_DAV-1.7.13-1.el6,php-sabredav-Sabre_CardDAV-1.7.9-2.el6,php-sabredav-Sabre_CalDAV-1.7.9-1.el6,php-irodsphp-3.3.0-0.4.beta1.el6,php-phpseclib-net-ssh2-0.3.9-1.el6,php-phpseclib-net-sftp-0.3.9-1.el6,php-phpseclib-crypt-twofish-0.3.9-2.el6,php-phpseclib-crypt-tripledes-0.3.9-2.el6,php-phpseclib-crypt-rsa-0.3.9-1.el6,php-phpseclib-crypt-rijndael-0.3.9-2.el6,php-phpseclib-crypt-rc4-0.3.9-2.el6,php-phpseclib-crypt-random-0.3.9-1.el6,php-phpseclib-crypt-hash-0.3.9-1.el6,php-phpseclib-crypt-des-0.3.9-2.el6,php-phpseclib-crypt-blowfish-0.3.9-2.el6,php-phpseclib-crypt-aes-0.3.9-1.el6,php-phpseclib-math-biginteger-0.3.9-1.el6,php-phpseclib-crypt-base-0.3.9-1.el6,owncloud-6.0.6-1.el6 1 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4281/docker-io-1.3.2-2.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing ansible-1.8-1.el6 debootstrap-1.0.66-1.el6 fts-3.2.30-1.el6 fts-monitoring-3.2.30-1.el6 fts-mysql-3.2.30-1.el6 mom-0.4.3-1.el6 py3status-1.6-1.el6 Details about builds: ansible-1.8-1.el6 (FEDORA-EPEL-2014-4299) SSH-based configuration management, deployment, and task execution system Update Information: Update to 1.8 ChangeLog: * Tue Nov 25 2014 Kevin Fenzi ke...@scrye.com 1.8-1 - Update to 1.8 debootstrap-1.0.66-1.el6 (FEDORA-EPEL-2014-4295) Debian GNU/Linux bootstrapper Update Information: new upstream release ChangeLog: * Tue Nov 25 2014 Jan Vcelak jvce...@fedoraproject.org 1.0.66-1 - new upstream release: + add support for 'stretch' + specify gzip for deboostrap, xz for debootstrap-udeb + better portability on non-Debian platforms References: [ 1 ] Bug #1163119 - debootstrap-1.0.66 is available https://bugzilla.redhat.com/show_bug.cgi?id=1163119 fts-3.2.30-1.el6 (FEDORA-EPEL-2014-4309) File Transfer Service V3 Update Information: New upstream release 3.2.30 ChangeLog: * Wed Nov 26 2014 Alejandro Alvarez Ayllon aalva...@cern.ch - 3.2.30-1 - Update for new upstream release * Thu Sep 4 2014 Orion Poplawski or...@cora.nwra.com - 3.2.26.2-4 - Rebuild for pugixml 1.4 * Sat Aug 16 2014 Fedora Release Engineering rel-...@lists.fedoraproject.org - 3.2.26.2-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_22_Mass_Rebuild
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 30 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3621/php-Smarty-3.1.21-1.el7 14 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3989/cross-binutils-2.23.88.0.1-2.el7.1 13 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4045/libvncserver-0.9.9-0.9.el7.1 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4113/kwebkitpart-1.3.4-5.el7 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4100/erlang-R16B-03.9.el7 8 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4152/lsyncd-2.1.5-6.el7 8 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4154/nodejs-0.10.33-1.el7,libuv-0.10.29-1.el7 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4174/python-eyed3-0.7.4-4.el7 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4170/clamav-0.98.5-1.el7 5 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4208/drupal7-7.34-1.el7 5 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4197/wordpress-4.0.1-1.el7 2 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4252/phpMyAdmin-4.2.12-1.el7 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4302/hexchat-2.10.2-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing ansible-1.8-1.el7 bmon-3.6-1.el7 debootstrap-1.0.66-1.el7 fts-3.2.30-1.el7 fts-monitoring-3.2.30-1.el7 fts-mysql-3.2.30-1.el7 gtkdialog-0.8.3-8.el7 hexchat-2.10.2-1.el7 hgsvn-0.2.3-3.el7 kbibtex-0.5.1-5.el7 mom-0.4.3-1.el7 nodejs-codemirror-4.8.0-1.el7 nodejs-handlebars-2.0.0-2.el7 owncloud-7.0.3-3.el7 perl-Plack-Middleware-FixMissingBodyInRedirect-0.12-1.el7 perl-Plack-Middleware-RemoveRedundantBody-0.05-1.el7 perl-Tangerine-0.11-1.el7 php-channel-dropbox-php-1.3-5.el7 php-channel-phpseclib-1.3-1.el7 php-dropbox-php-Dropbox-1.0.0-6.el7 php-pear-Crypt-Blowfish-1.1.0-0.10.rc2.el7 php-phpseclib-crypt-aes-0.3.9-1.el7 php-phpseclib-crypt-base-0.3.9-1.el7 php-phpseclib-crypt-blowfish-0.3.9-2.el7 php-phpseclib-crypt-des-0.3.9-2.el7 php-phpseclib-crypt-hash-0.3.9-1.el7 php-phpseclib-crypt-random-0.3.9-1.el7 php-phpseclib-crypt-rc4-0.3.9-2.el7 php-phpseclib-crypt-rijndael-0.3.9-2.el7 php-phpseclib-crypt-rsa-0.3.9-1.el7 php-phpseclib-crypt-tripledes-0.3.9-2.el7 php-phpseclib-crypt-twofish-0.3.9-2.el7 php-phpseclib-math-biginteger-0.3.9-1.el7 php-phpseclib-net-sftp-0.3.9-1.el7 php-phpseclib-net-ssh2-0.3.9-1.el7 spacecmd-2.3.2-1.el7 varnish-4.0.2-1.el7 Details about builds: ansible-1.8-1.el7 (FEDORA-EPEL-2014-4298) SSH-based configuration management, deployment, and task execution system Update Information: Update to 1.8 ChangeLog: * Tue Nov 25 2014 Kevin Fenzi ke...@scrye.com 1.8-1 - Update to 1.8 * Thu Oct 9 2014 Toshio Kuratomi tos...@fedoraproject.org - 1.7.2-2 - Add /usr/bin/ansible to the rhel6 newer pycrypto patch bmon-3.6-1.el7 (FEDORA-EPEL-2014-4301) Bandwidth monitor and rate estimator Update Information: Update to 3.6 release References: [ 1 ] Bug #1141182 - Please build bmon for epel7 https://bugzilla.redhat.com/show_bug.cgi?id=1141182 debootstrap-1.0.66-1.el7 (FEDORA-EPEL-2014-4289) Debian GNU/Linux bootstrapper Update Information: new upstream release ChangeLog: * Tue Nov 25 2014 Jan Vcelak jvce...@fedoraproject.org 1.0.66-1 - new upstream release: + add support for 'stretch' + specify gzip for deboostrap, xz for debootstrap-udeb + better portability on non-Debian platforms References: [ 1 ] Bug #1163119 - debootstrap-1.0.66 is available https://bugzilla.redhat.com/show_bug.cgi?id=1163119 fts-3.2.30-1.el7 (FEDORA-EPEL-2014-4292) File Transfer Service V3
Re: Abotu setting 'PermitRootLogin=no' in sshd_config
- Original Message - On Wed, Nov 26, 2014 at 11:48 AM, Scott Schmit i.g...@comcast.net wrote: On Tue, Nov 25, 2014 at 09:56:59AM -0500, Simo Sorce wrote: On Sat, 22 Nov 2014 08:24:32 + (UTC) P J P wrote: On Saturday, 22 November 2014 1:39 AM, Richard W.M. Jones wrote: On Fri, Nov 21, 2014 at 09:11:51AM +0100, Florian Weimer wrote: The latter. We have to install authorized_keys inside the VM anyway, so we can touch sshd_config, too. Virt-builder has a new '--ssh-inject' feature (in F22 only). $ virt-builder fedora-20 --ssh-inject root would inject your current ssh key into the root account of the new VM. There are other variations, including ways to create a non-root user account, see: http://libguestfs.org/virt-builder.1.html Excellent! :) So far the consensus seem that it is okay to reverse the current default and set PermitRootLogin=no. I'll talk to the upstream maintainer - plautrba(https://fedoraproject.org/wiki/User:Plautrba). Thank you. We can install machine w/o user accounts, removing the ability to log in as root via ssh means those machines will not be accessible. If you want to remove root access that should be conditionally done at firstboot only if a user account was created. It seems to me that we could tweak this somewhat: only if a user account was created OR remote users have been configured And in months that start with the letter q, but not odd numbed weekdays, and if I ate a tuna fish sandwich for lunch, but not if I'm wearing white socks, and only on alternate years with a prime number, etc, etc., etc. Look, this is a basic system configuration. It's not Cripple Mr. Onion. Pick *one* setting, and let people know from that whether they'll need to manipulate their local environments for their particular subtle needs. And for those who don't read Terry Pratchett stories, http://discworld.wikia.com/wiki/Cripple_Mr_Onion Exactly! The more I think about this Change the more I am having an opinion that we should reject it altogether. In fact this change does not really bring any real security improvement because for the Workstation the sshd is already disabled completely by default and for the other products the people who are installing them can be expected to know what they are doing. Also disabling root access does not improve security against targeted attacks because in such cases the user name can be quite easily inferred. So basically this feature is just a 'marketing' improvement and not worth the hassle. Tomas Mraz -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Best way to use zram in Fedora 21?
On Wed, 2014-11-26 at 16:27 -0500, Corey Sheldon wrote: Juan no needinst.zram=on on install on first boot modprobe zram ; systemctl start zramvoila I use the default one in f21b no issues For now. But the anaconda's zram.service is tailored to provide zram swap for the installation process. Future changes in it may make it unusable for general purpose usage on an installed system. So packaging something general-purpose it definitely the right way to go. Reindl's scripts look good to me, I'd just suggest adding a configuration option for setting the maximum RAM for the zram swap being created. It doesn't make much sense to use it on systems with e.g. 32 GiB of RAM. That's by the way one of the tweaks the anaconda's version of the scripts+service has (hardcoded, though). -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Best way to use zram in Fedora 21?
On Wed, 2014-11-26 at 23:46 +0100, Nicolas Chauvet wrote: 2014-11-26 22:27 GMT+01:00 Corey Sheldon sheldon.co...@gmail.com: Juan no needinst.zram=on on install on first boot modprobe zram ; systemctl start zramvoila I use the default one in f21b no issues Corey, Why this service is part of anaconda-core ? and not with the base systemd or else ? Because it is not a general-purpose service. It is a tailored version of service+scripts for use in the installation process. -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Best way to use zram in Fedora 21?
Am 27.11.2014 um 11:15 schrieb Vratislav Podzimek: On Wed, 2014-11-26 at 16:27 -0500, Corey Sheldon wrote: Juan no needinst.zram=on on install on first boot modprobe zram ; systemctl start zramvoila I use the default one in f21b no issues For now. But the anaconda's zram.service is tailored to provide zram swap for the installation process. Future changes in it may make it unusable for general purpose usage on an installed system. So packaging something general-purpose it definitely the right way to go. Reindl's scripts look good to me, I'd just suggest adding a configuration option for setting the maximum RAM for the zram swap being created. It doesn't make much sense to use it on systems with e.g. 32 GiB of RAM. That's by the way one of the tweaks the anaconda's version of the scripts+service has (hardcoded, though) my script supports a percent of total RAM config which i don't ship with the RPM because it's meant for internal usage (it's BTW a result of Google around after face the zram module with new kernels, took existing snippets from several sources, made them easier, fixed some bugs and introduced the systemd-unit) [root@mail-gw:~]$ cat /etc/sysconfig/zram FACTOR=15 It doesn't make much sense to use it on systems with e.g. 32 GiB of RAM depends on the context - on a host mostly used for a lot of virtual machines it makes sense even with 64 GB or more - depends on the total count of guests and how much RAM they have assigend instead have zram on all of the guests and to prevent danger of OOM events they may have all 2-3 GB RAM and while overcommit the host that way it can swap out most unsed guest memory without fall back to slow disk swapping VMware ESXi does something similar for years to overcommit hosts http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.resourcemanagement.doc_41/managing_memory_resources/c_memory_compression.html signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: timedatex replacing systemd-timedated for NTP packages
On Tue, 2014-11-25 at 18:26 +0100, Lennart Poettering wrote: On Tue, 25.11.14 11:08, Michael Catanzaro (mcatanz...@gnome.org) wrote: On Tue, 2014-11-25 at 17:15 +0100, Lennart Poettering wrote: I am sorry, but timedated is really not the place to control NTP *server* software. It's simply, desktopy stuff, for controlling NTP clients. Of course, but the desktopy NTP client in Fedora Workstation is chrony, as you know full well. Unless that changes, we need timedatex. Even if we decide to drop chrony, we still need timedatex to ensure NTP is not broken for users who upgrade from F21 to F22. (Unless you have another plan for handling such an upgrade?) Drop the NTP checkbox. Enable chrony by default. Done. That would be quite a big security issue. -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
F-21 Branched report: 20141127 changes
Compose started at Thu Nov 27 07:15:02 UTC 2014 Broken deps for armhfp -- [avro] avro-mapred-1.7.5-9.fc21.noarch requires hadoop-mapreduce avro-mapred-1.7.5-9.fc21.noarch requires hadoop-client [gofer] ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) = 0:0.16.0 [openstack-nova] openstack-nova-compute-2014.1.2-1.fc21.noarch requires libvirt-daemon-xen [ostree] ostree-grub2-2014.11-1.fc21.armv7hl requires grub2 [spring-maps-default] spring-maps-default-0.1-12.fc21.noarch requires spring [syntastic] syntastic-d-3.5.0-1.fc21.noarch requires ldc Broken deps for i386 -- [gofer] ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) = 0:0.16.0 Broken deps for x86_64 -- [gofer] ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) = 0:0.16.0 Removed package: python3-configobj-4.7.2-6.20131004hg10adc6e7d759.fc21 Summary: Added Packages: 0 Removed Packages: 1 Modified Packages: 0 Size of added packages: 0 (0 ) Size change of modified packages: 0 (0 ) Size of removed packages: 104275 (102 k) Size change: -104275 (-102 k) Compose finished at Thu Nov 27 10:43:22 UTC 2014 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
rawhide report: 20141127 changes
Compose started at Thu Nov 27 05:15:03 UTC 2014 Broken deps for i386 -- [3Depict] 3Depict-0.0.16-3.fc22.i686 requires libmgl.so.7.2.0 [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [cab] cab-0.1.9-12.fc22.i686 requires cabal-dev [cinepaint] cinepaint-libs-1.4-7.fc22.i686 requires libImath-2_1.so.11 cinepaint-libs-1.4-7.fc22.i686 requires libIlmThread-2_1.so.11 cinepaint-libs-1.4-7.fc22.i686 requires libIlmImf-Imf_2_1.so.21 cinepaint-libs-1.4-7.fc22.i686 requires libIexMath-2_1.so.11 cinepaint-libs-1.4-7.fc22.i686 requires libIex-2_1.so.11 cinepaint-libs-1.4-7.fc22.i686 requires libHalf.so.11 [dnssec-check] dnssec-check-1.14.0.1-4.fc20.i686 requires libval-threads.so.14 dnssec-check-1.14.0.1-4.fc20.i686 requires libsres.so.14 [gegl] gegl-0.2.0-20.fc22.i686 requires libImath-2_1.so.11 gegl-0.2.0-20.fc22.i686 requires libIlmThread-2_1.so.11 gegl-0.2.0-20.fc22.i686 requires libIlmImf-Imf_2_1.so.21 gegl-0.2.0-20.fc22.i686 requires libIexMath-2_1.so.11 gegl-0.2.0-20.fc22.i686 requires libIex-2_1.so.11 gegl-0.2.0-20.fc22.i686 requires libHalf.so.11 [glances] glances-2.1.2-2.fc22.noarch requires python-psutil = 0:2.0.0 [nwchem] nwchem-openmpi-6.3.2-11.fc21.i686 requires libmpi_usempi.so.1 [python-selenium] python3-selenium-2.43.0-1.fc22.noarch requires python3-rdflib [rubygem-wirb] rubygem-wirb-1.0.3-2.fc21.noarch requires rubygem(paint) 0:0.9 [shogun] shogun-doc-3.2.0.1-0.27.git20140804.96f3cf3.fc22.noarch requires shogun-data = 0:0.8.1-0.18.git20140804.48a1abb.fc22 [uwsgi] uwsgi-plugin-gridfs-2.0.7-2.fc22.i686 requires libmongoclient.so uwsgi-stats-pusher-mongodb-2.0.7-2.fc22.i686 requires libmongoclient.so [vfrnav] vfrnav-20140510-2.fc22.i686 requires libpolyclipping.so.16 vfrnav-utils-20140510-2.fc22.i686 requires libpolyclipping.so.16 Broken deps for x86_64 -- [3Depict] 3Depict-0.0.16-3.fc22.x86_64 requires libmgl.so.7.2.0()(64bit) [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [cab] cab-0.1.9-12.fc22.x86_64 requires cabal-dev [cinepaint] cinepaint-libs-1.4-7.fc22.i686 requires libImath-2_1.so.11 cinepaint-libs-1.4-7.fc22.i686 requires libIlmThread-2_1.so.11 cinepaint-libs-1.4-7.fc22.i686 requires libIlmImf-Imf_2_1.so.21 cinepaint-libs-1.4-7.fc22.i686 requires libIexMath-2_1.so.11 cinepaint-libs-1.4-7.fc22.i686 requires libIex-2_1.so.11 cinepaint-libs-1.4-7.fc22.i686 requires libHalf.so.11 cinepaint-libs-1.4-7.fc22.x86_64 requires libImath-2_1.so.11()(64bit) cinepaint-libs-1.4-7.fc22.x86_64 requires libIlmThread-2_1.so.11()(64bit) cinepaint-libs-1.4-7.fc22.x86_64 requires libIlmImf-Imf_2_1.so.21()(64bit) cinepaint-libs-1.4-7.fc22.x86_64 requires libIexMath-2_1.so.11()(64bit) cinepaint-libs-1.4-7.fc22.x86_64 requires libIex-2_1.so.11()(64bit) cinepaint-libs-1.4-7.fc22.x86_64 requires libHalf.so.11()(64bit) [dnssec-check] dnssec-check-1.14.0.1-4.fc20.x86_64 requires libval-threads.so.14()(64bit) dnssec-check-1.14.0.1-4.fc20.x86_64 requires libsres.so.14()(64bit) [gegl] gegl-0.2.0-20.fc22.i686 requires libImath-2_1.so.11 gegl-0.2.0-20.fc22.i686 requires libIlmThread-2_1.so.11 gegl-0.2.0-20.fc22.i686 requires libIlmImf-Imf_2_1.so.21 gegl-0.2.0-20.fc22.i686 requires libIexMath-2_1.so.11 gegl-0.2.0-20.fc22.i686 requires libIex-2_1.so.11 gegl-0.2.0-20.fc22.i686 requires libHalf.so.11 gegl-0.2.0-20.fc22.x86_64 requires libImath-2_1.so.11()(64bit) gegl-0.2.0-20.fc22.x86_64 requires libIlmThread-2_1.so.11()(64bit) gegl-0.2.0-20.fc22.x86_64 requires libIlmImf-Imf_2_1.so.21()(64bit) gegl-0.2.0-20.fc22.x86_64 requires libIexMath-2_1.so.11()(64bit) gegl-0.2.0-20.fc22.x86_64 requires libIex-2_1.so.11()(64bit) gegl-0.2.0-20.fc22.x86_64 requires libHalf.so.11()(64bit) [glances] glances-2.1.2-2.fc22.noarch requires python-psutil = 0:2.0.0 [nwchem] nwchem-openmpi-6.3.2-11.fc21.x86_64 requires libmpi_usempi.so.1()(64bit) [python-selenium] python3-selenium-2.43.0-1.fc22.noarch requires python3-rdflib [rubygem-wirb] rubygem-wirb-1.0.3-2.fc21.noarch requires rubygem(paint) 0:0.9 [shogun] shogun-doc-3.2.0.1-0.27.git20140804.96f3cf3.fc22.noarch requires shogun-data = 0:0.8.1-0.18.git20140804.48a1abb.fc22 [uwsgi] uwsgi-plugin-gridfs-2.0.7-2.fc22.x86_64 requires libmongoclient.so()(64bit) uwsgi-stats-pusher-mongodb-2.0.7-2.fc22.x86_64 requires libmongoclient.so()(64bit) [vfrnav] vfrnav-20140510-2.fc22.i686 requires libpolyclipping.so.16
Re: Abotu setting 'PermitRootLogin=no' in sshd_config
Hello Tomas, On Thursday, 27 November 2014 3:05 PM, Tomas Mraz wrote: - Original Message - On Wed, Nov 26, 2014 at 11:48 AM, Scott Schmit wrote: Look, this is a basic system configuration. It's not Cripple Mr. Onion. Pick *one* setting, and let people know from that whether they'll need to manipulate their local environments for their particular subtle needs. Exactly! The more I think about this Change the more I am having an opinion that we should reject it altogether. In fact this change does not really bring any real security improvement because for the Workstation the sshd is already disabled completely by default and for the other products the people who are installing them can be expected to know what they are doing. That's not a prudent expectation. Also disabling root access does not improve security against targeted attacks because in such cases the user name can be quite easily inferred. So basically this feature is just a 'marketing' improvement and not worth the hassle. I disagree. Just because it is easy to infer non-root user names does not mean we tell people it is 'root'. Secondly, it might be easy for you to infer such names, not for everyone. The increased difficulty level that is added by not allowing remote root login could help to thwart lot of real automated attacks.[1] Thirdly, it need not have to be entirely about security, it's also about picking the right default configuration. Same as disabling sshd(8) in Workstation by default. As Scott wrote above ...Pick *one* setting, and let people know from that... This feature, like any other, requires users to tweak their current practices to suite the new defaults. That is no reason to not do it; Because in the longer run it is only beneficial. [1] https://lists.fedoraproject.org/pipermail/security/2014-November/002031.html --- Regards -Prasad http://feedmug.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Abotu setting 'PermitRootLogin=no' in sshd_config
Am 27.11.2014 um 12:13 schrieb P J P: Just because it is easy to infer non-root user names does not mean we tell people it is 'root'. Secondly, it might be easy for you to infer such names, not for everyone. The increased difficulty level that is added by not allowing remote root login could help to thwart lot of real automated attacks.[1] Thirdly, it need not have to be entirely about security, it's also about picking the right default configuration. Same as disabling sshd(8) in Workstation by default. As Scott wrote above so why not consider disable sshd at all and make a checkbox in Anaconda ssh support yes/no because after somebody says yes it's his clearly decision and he is responsible to secure it with key-only auth i guess the answer will be because too many options in the installer will harm which i can't support - to less options IMHO harm forcing the user to look what is setup and how signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: libmusicbrainz5 soname bump
Done. Cheers, H. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[PkgDB] psabata:perl-Regexp-Assemble commit set to Approved
user: psabata set for pghmcfc acl: commit of package: perl-Regexp-Assemble from: Awaiting Review to: Approved on branch: master To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Regexp-Assemble -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Abotu setting 'PermitRootLogin=no' in sshd_config
On Thursday, 27 November 2014 4:49 PM, Reindl Harald wrote: so why not consider disable sshd at all and make a checkbox in Anaconda ssh support yes/no because after somebody says yes it's his clearly decision and he is responsible to secure it with key-only auth Sure these are options, which need to be evaluated against their pros and cons. For the 'Disable remote root login' option, this evaluation has been more positive than negative. Cases wherein it is negative, is mostly due to the tweaking that users would have to incorporate in their workflow, ex. explicitly enable remote root login after creating a new VM. This is easily doable because these users are fairly experienced ones. Idea is not to punish them for it, but to depend on their expertise rather than to expect that unknown users would/should know how to safe guard their systems. Overall this feature adds more value to Fedora, than its perceived short term cost. --- Regards -Prasad http://feedmug.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[PkgDB] jplesnik:perl-POE-Component-Client-DNS approveacls set to Approved
user: jplesnik set for jehane acl: approveacls of package: perl-POE-Component-Client-DNS from: Awaiting Review to: Approved on branch: f20 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-POE-Component-Client-DNS -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Best way to use zram in Fedora 21?
El 2014-11-27 11:24, Reindl Harald escribió: Am 27.11.2014 um 11:15 schrieb Vratislav Podzimek: On Wed, 2014-11-26 at 16:27 -0500, Corey Sheldon wrote: Juan no needinst.zram=on on install on first boot modprobe zram ; systemctl start zramvoila I use the default one in f21b no issues For now. But the anaconda's zram.service is tailored to provide zram swap for the installation process. Future changes in it may make it unusable for general purpose usage on an installed system. So packaging something general-purpose it definitely the right way to go. Reindl's scripts look good to me, I'd just suggest adding a configuration option for setting the maximum RAM for the zram swap being created. It doesn't make much sense to use it on systems with e.g. 32 GiB of RAM. That's by the way one of the tweaks the anaconda's version of the scripts+service has (hardcoded, though) my script supports a percent of total RAM config which i don't ship with the RPM because it's meant for internal usage (it's BTW a result of Google around after face the zram module with new kernels, took existing snippets from several sources, made them easier, fixed some bugs and introduced the systemd-unit) [root@mail-gw:~]$ cat /etc/sysconfig/zram FACTOR=15 sion.html Reindl, I'm of the opinion you should upload your scripts to some git repository and package them to be part of the distribution. I can co-maintain if you wish. -- Juan Orti https://miceliux.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[PkgDB] psabata:perl-Unix-Statgrab commit set to Approved
user: psabata set for cicku acl: commit of package: perl-Unix-Statgrab from: Awaiting Review to: Approved on branch: master To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Unix-Statgrab -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Module-Loaded watchbugzilla set to Approved
user: psabata set for iburrell acl: watchbugzilla of package: perl-Module-Loaded from: Awaiting Review to: Approved on branch: el5 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Module-Loaded -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Class-ErrorHandler watchcommits set to Approved
user: psabata set for xavierb acl: watchcommits of package: perl-Class-ErrorHandler from: Awaiting Review to: Approved on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Class-ErrorHandler -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Mail-SPF commit set to Approved
user: psabata set for nb acl: commit of package: perl-Mail-SPF from: Awaiting Review to: Approved on branch: epel7 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Mail-SPF -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Convert-ASCII-Armour watchcommits set to Approved
user: psabata set for xavierb acl: watchcommits of package: perl-Convert-ASCII-Armour from: Awaiting Review to: Approved on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Convert-ASCII-Armour -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Object-Accessor set point of contact to: orphan
user: psabata changed point of contact of package: perl-Object-Accessor from: psabata to: orphan on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Object-Accessor -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Module-Loaded watchcommits set to Approved
user: psabata set for iburrell acl: watchcommits of package: perl-Module-Loaded from: Awaiting Review to: Approved on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Module-Loaded -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Mail-SPF approveacls set to Approved
user: psabata set for nb acl: approveacls of package: perl-Mail-SPF from: Awaiting Review to: Approved on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Mail-SPF -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Term-UI set point of contact to: orphan
user: psabata changed point of contact of package: perl-Term-UI from: psabata to: orphan on branch: el5 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Term-UI -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Mail-SPF commit set to Approved
user: psabata set for nb acl: commit of package: perl-Mail-SPF from: Awaiting Review to: Approved on branch: f19 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Mail-SPF -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Mail-SPF commit set to Approved
user: psabata set for nb acl: commit of package: perl-Mail-SPF from: Awaiting Review to: Approved on branch: f21 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Mail-SPF -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Mail-SPF approveacls set to Approved
user: psabata set for nb acl: approveacls of package: perl-Mail-SPF from: Awaiting Review to: Approved on branch: f20 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Mail-SPF -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Unix-Statgrab commit set to Approved
user: psabata set for cicku acl: commit of package: perl-Unix-Statgrab from: Awaiting Review to: Approved on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Unix-Statgrab -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Net-SFTP commit set to Approved
user: psabata set for xavierb acl: commit of package: perl-Net-SFTP from: Awaiting Review to: Approved on branch: el5 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Net-SFTP -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Net-SFTP watchbugzilla set to Approved
user: psabata set for xavierb acl: watchbugzilla of package: perl-Net-SFTP from: Awaiting Review to: Approved on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Net-SFTP -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Module-Loaded watchcommits set to Approved
user: psabata set for iburrell acl: watchcommits of package: perl-Module-Loaded from: Awaiting Review to: Approved on branch: el5 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Module-Loaded -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Mail-SPF approveacls set to Approved
user: psabata set for nb acl: approveacls of package: perl-Mail-SPF from: Awaiting Review to: Approved on branch: master To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Mail-SPF -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Unix-Statgrab commit set to Approved
user: psabata set for cicku acl: commit of package: perl-Unix-Statgrab from: Awaiting Review to: Approved on branch: f20 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Unix-Statgrab -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Crypt-DES_EDE3 watchcommits set to Approved
user: psabata set for xavierb acl: watchcommits of package: perl-Crypt-DES_EDE3 from: Awaiting Review to: Approved on branch: el5 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Crypt-DES_EDE3 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Unix-Statgrab commit set to Approved
user: psabata set for cicku acl: commit of package: perl-Unix-Statgrab from: Awaiting Review to: Approved on branch: f21 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Unix-Statgrab -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Crypt-DES_EDE3 watchcommits set to Approved
user: psabata set for xavierb acl: watchcommits of package: perl-Crypt-DES_EDE3 from: Awaiting Review to: Approved on branch: epel7 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Crypt-DES_EDE3 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Crypt-DES_EDE3 watchbugzilla set to Approved
user: psabata set for xavierb acl: watchbugzilla of package: perl-Crypt-DES_EDE3 from: Awaiting Review to: Approved on branch: el5 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Crypt-DES_EDE3 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Object-Accessor set point of contact to: orphan
user: psabata changed point of contact of package: perl-Object-Accessor from: psabata to: orphan on branch: el5 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Object-Accessor -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Crypt-DES_EDE3 watchcommits set to Approved
user: psabata set for xavierb acl: watchcommits of package: perl-Crypt-DES_EDE3 from: Awaiting Review to: Approved on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Crypt-DES_EDE3 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Unix-Statgrab commit set to Approved
user: psabata set for cicku acl: commit of package: perl-Unix-Statgrab from: Awaiting Review to: Approved on branch: f19 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Unix-Statgrab -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Convert-ASCII-Armour commit set to Approved
user: psabata set for xavierb acl: commit of package: perl-Convert-ASCII-Armour from: Awaiting Review to: Approved on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Convert-ASCII-Armour -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Unix-Statgrab commit set to Approved
user: psabata set for cicku acl: commit of package: perl-Unix-Statgrab from: to: Approved on branch: el5 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Unix-Statgrab -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Best way to use zram in Fedora 21?
Am 27.11.2014 um 14:25 schrieb Juan Orti: El 2014-11-27 11:24, Reindl Harald escribió: Am 27.11.2014 um 11:15 schrieb Vratislav Podzimek: On Wed, 2014-11-26 at 16:27 -0500, Corey Sheldon wrote: Juan no needinst.zram=on on install on first boot modprobe zram ; systemctl start zramvoila I use the default one in f21b no issues For now. But the anaconda's zram.service is tailored to provide zram swap for the installation process. Future changes in it may make it unusable for general purpose usage on an installed system. So packaging something general-purpose it definitely the right way to go. Reindl's scripts look good to me, I'd just suggest adding a configuration option for setting the maximum RAM for the zram swap being created. It doesn't make much sense to use it on systems with e.g. 32 GiB of RAM. That's by the way one of the tweaks the anaconda's version of the scripts+service has (hardcoded, though) my script supports a percent of total RAM config which i don't ship with the RPM because it's meant for internal usage (it's BTW a result of Google around after face the zram module with new kernels, took existing snippets from several sources, made them easier, fixed some bugs and introduced the systemd-unit) [root@mail-gw:~]$ cat /etc/sysconfig/zram FACTOR=15 Reindl, I'm of the opinion you should upload your scripts to some git repository and package them to be part of the distribution. I can co-maintain if you wish feel free to package it! that's why i attached it as i saw the topic i am not a active packager on the Fedora infrastrcuture signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Abotu setting 'PermitRootLogin=no' in sshd_config
On Thu, Nov 27, 2014 at 8:06 AM, P J P pj.pan...@yahoo.co.in wrote: On Thursday, 27 November 2014 4:49 PM, Reindl Harald wrote: so why not consider disable sshd at all and make a checkbox in Anaconda ssh support yes/no because after somebody says yes it's his clearly decision and he is responsible to secure it with key-only auth Sure these are options, which need to be evaluated against their pros and cons. For the 'Disable remote root login' option, this evaluation has been more positive than negative. Cases wherein it is negative, is mostly due to the tweaking that users would have to incorporate in their workflow, ex. explicitly enable remote root login after creating a new VM. This is easily doable because these users are fairly experienced ones. Idea is not to punish them for it, but to depend on their expertise rather than to expect that unknown users would/should know how to safe guard their systems. Overall this feature adds more value to Fedora, than its perceived short term cost. I agree, from a basic security standpoint, that it's the simplest change with the largest return on investment. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Entire process's environment attached to bugzillas by ABRT
Hello, As you might know ABRT attaches 'environ' file to its Bugzilla bugs. The file contains a full copy of /proc/[pid]/environ. Even though ABRT highlights black-listed words and encourages users to review the data before submitting them, it may happen that the reporter misses something and publishes his secrete data in 'environ' file. Do you find 'environ' attachment valuable or is ABRT just publishing personal information? Regards, Jakub -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Best way to use zram in Fedora 21?
El 2014-11-27 14:48, Reindl Harald escribió: Am 27.11.2014 um 14:25 schrieb Juan Orti: Reindl, I'm of the opinion you should upload your scripts to some git repository and package them to be part of the distribution. I can co-maintain if you wish feel free to package it! that's why i attached it as i saw the topic i am not a active packager on the Fedora infrastrcuture Ok, I've uploaded the scripts to GitHub and submitted a review request: https://github.com/jorti/zram-swap https://bugzilla.redhat.com/show_bug.cgi?id=1168692 -- Juan Orti https://miceliux.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: libmusicbrainz5 soname bump
On Thu, Nov 27, 2014 at 01:58:23PM +0100, Haïkel wrote: Done. Thanks a lot Haïkel! Christophe pgpCDHfLqen0I.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Entire process's environment attached to bugzillas by ABRT
On Thu, 27 Nov 2014 16:23:57 +0100, Jakub Filak wrote: Do you find 'environ' attachment valuable or is ABRT just publishing personal information? No but I can imagine in some cases it may be useful. Couldn't there be a way to send additional information upon bug assignee's request? That would be typically useful with the core files but reporters always said they cannot find the core file anywhere. Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: timedatex replacing systemd-timedated for NTP packages
- Original Message - If we want to have this working correctly with chronyd/ntpd, at this point it seems the only reasonable option is to replace systemd-timedated. timedatex is a new implementation of the timedate interface that was recently added to Fedora. It reads the list of NTP units from a directory as systemd-timedated used to do. When installed, systemd will start it for the timedate bus name instead of systemd-timedated. The timedate clients should work as expected, please report bugs if not. One suggestion was to install it as a dependency of the NTP packages. Is this a good idea? Should this first go through the Fedora change process or at least be documented somewhere? I think having a package that “takes over” a D-Bus service name, and installing it by default but not in all possible installations, is surprising enough that it would benefit from a FESCo sanity check, yes. (I don’t at this moment have any specific objections to this but this does seem a little dangerous. The flip side is that it is probably impossible for FESCo to discuss the technical risk of timedatex without also discussing the underlying conflict about time synchronization clients.) (*Sigh* It would be so much better if people could come to a consensus on a single design and implementation instead of “show me the code“-like writing software that bypasses some other software… I suppose at least it is good that several people care about time synchronization. Oh, and I also want world peace, and ponies. Don’t forget ponies.) Mirek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: timedatex replacing systemd-timedated for NTP packages
On Wed, Nov 26, 2014 at 3:10 PM, Chris Adams li...@cmadams.net wrote: Once upon a time, Tomasz Torcz to...@pipebreaker.pl said: On Wed, Nov 26, 2014 at 08:01:37AM -0600, Chris Adams wrote: Once upon a time, Florian Weimer fwei...@redhat.com said: Do we even use the DHCP NTP server assignment? I believe it is used for chrony and ntpd, don't know about sysmted's new implementation. systemd-timesyncd uses DHCP-provided NTP servers only if systemd-networkd is used as DHCP client. That should be a bug (and block it from use). There's no excuse for that other than not invented here. There are technical reasons for this choice, not merely NIH. Cheers, Tom -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: timedatex replacing systemd-timedated for NTP packages
On Thu, Nov 27, 2014 at 12:51 PM, Tom Gundersen t...@jklm.no wrote: On Wed, Nov 26, 2014 at 3:10 PM, Chris Adams li...@cmadams.net wrote: Once upon a time, Tomasz Torcz to...@pipebreaker.pl said: On Wed, Nov 26, 2014 at 08:01:37AM -0600, Chris Adams wrote: Once upon a time, Florian Weimer fwei...@redhat.com said: Do we even use the DHCP NTP server assignment? I believe it is used for chrony and ntpd, don't know about sysmted's new implementation. systemd-timesyncd uses DHCP-provided NTP servers only if systemd-networkd is used as DHCP client. That should be a bug (and block it from use). There's no excuse for that other than not invented here. There are technical reasons for this choice, not merely NIH. And those technical reasons are? I realize that the shell-script-fu that most DHCP clients seem to require is a bit messy, but it does work, and it should be more than flexible enough to plug in some systemd-timesyncd controls. As a counterexample, I run some production servers with rather complicated network configurations. NetworkManager is a nonstarter, and I suspect that systemd-networkd will never work for them either. This isn't a complaint about either package -- I don't really expect them to understand my configuration. I use a Python script that reads a rather large hand-curated config file and outputs Debian interfaces(5) rules with a liberal sprinking of up and down directives. (Yes, this is an Ubuntu system, not Fedora. If I were doing it over, I'd be using Fedora or CentOS, and I'd grumble at the fact that interfaces(5) is IMO much better than the Fedora equivalent.) The upshot is that I won't be using systemd-networkd any time soon. Again, this is in no way a criticism of systemd-networkd. I do use NTP, and I don't really care much which implementation I'm using, but if systemd-timesyncd refuses to be reasonably configurable unless systemd-networkd is installed, I won't be using *that* any time soon either. And if Fedora becomes dependent on services that aren't configurable, then the next time I reconsider what distro I use, Fedora's going to have a big mark against it. --Andy -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: timedatex replacing systemd-timedated for NTP packages
Hi Andrew, On Thu, Nov 27, 2014 at 10:00 PM, Andrew Lutomirski l...@mit.edu wrote: On Thu, Nov 27, 2014 at 12:51 PM, Tom Gundersen t...@jklm.no wrote: On Wed, Nov 26, 2014 at 3:10 PM, Chris Adams li...@cmadams.net wrote: Once upon a time, Tomasz Torcz to...@pipebreaker.pl said: On Wed, Nov 26, 2014 at 08:01:37AM -0600, Chris Adams wrote: Once upon a time, Florian Weimer fwei...@redhat.com said: Do we even use the DHCP NTP server assignment? I believe it is used for chrony and ntpd, don't know about sysmted's new implementation. systemd-timesyncd uses DHCP-provided NTP servers only if systemd-networkd is used as DHCP client. That should be a bug (and block it from use). There's no excuse for that other than not invented here. There are technical reasons for this choice, not merely NIH. And those technical reasons are? I realize that the shell-script-fu that most DHCP clients seem to require is a bit messy, but it does work, and it should be more than flexible enough to plug in some systemd-timesyncd controls. The whole model is just the wrong way around for how networkd/timesyncd works, so this is not simply a case of if (!networkd) return -EINVAL. networkd allows consumers of network information (such as NTP servers, DNS resolvers, HTTP proxy brokers,...) to subscribe to this information (currently only via a C API [0], but could just as well have been dbus) and be notified of changes to it. Other DHCP clients will typically instead call a bunch of hooks (with env vars set) on every configuration change (and it is then presumably the job of the hook to instruct the NTP client, or whatever else, to change its config). So basically the systemd model is one where the consumer pulls the information from the producer, where the traditional DHCP model the producer pushes the information to the consumer. It follows from this that anyone can be a consumer of any sort of information (so you can come along and implement your alternative NTP clients hooking into networkd just fine), but making a drop-in replacement for a producer of information is not necessarily that straightforward (you basically have to go out of your way to make sure you mimic all the interfaces etc). I guess this is how our stack works most of the time anyway, replacing things higher in the stack is always easier than replacing things lower in the stack (because the kernel does not have hooks to call into your browser, your browser calls into the kernel...). Now that's just the design, you can of course make whatever bash scripts do whatever briding in either direction to make things behave in any way you want. As a counterexample, I run some production servers with rather complicated network configurations. NetworkManager is a nonstarter, and I suspect that systemd-networkd will never work for them either. There are certainly still usecases we don't cover, but a-priori we are interested in making anything work, so feel free to give us ping over at the systemd ML if we lack some features you need. This isn't a complaint about either package -- I don't really expect them to understand my configuration. I use a Python script that reads a rather large hand-curated config file and outputs Debian interfaces(5) rules with a liberal sprinking of up and down directives. Yikes... I do use NTP, and I don't really care much which implementation I'm using, but if systemd-timesyncd refuses to be reasonably configurable unless systemd-networkd is installed, I won't be using *that* any time soon either. You can of course still configure systemd-timesyncd to use a set of statically configured NTP servers, it is only the DHCP integration that currently requires networkd. That said, timesyncd is supposed to be this simple client that just works in the 99% of simple setups. If you have something fancy going on, it may very well be that you'll be better served by some other client (and that's just fine IMHO). And if Fedora becomes dependent on services that aren't configurable, My understanding is that timesyncd is meant to be a good enough default that just works, but not the one true NTP client. It is (or may at least one day be) a reasonable default, but it should clearly still be possible to exchange it with something else. Cheers, Tom [0]: http://cgit.freedesktop.org/systemd/systemd/tree/src/systemd/sd-network.h -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: timedatex replacing systemd-timedated for NTP packages
On Thu, Nov 27, 2014 at 10:53:45PM +0100, Tom Gundersen wrote: On Thu, Nov 27, 2014 at 10:00 PM, Andrew Lutomirski l...@mit.edu wrote: On Thu, Nov 27, 2014 at 12:51 PM, Tom Gundersen t...@jklm.no wrote: On Wed, Nov 26, 2014 at 3:10 PM, Chris Adams li...@cmadams.net wrote: Once upon a time, Tomasz Torcz to...@pipebreaker.pl said: On Wed, Nov 26, 2014 at 08:01:37AM -0600, Chris Adams wrote: Once upon a time, Florian Weimer fwei...@redhat.com said: Do we even use the DHCP NTP server assignment? I believe it is used for chrony and ntpd, don't know about sysmted's new implementation. systemd-timesyncd uses DHCP-provided NTP servers only if systemd-networkd is used as DHCP client. There are technical reasons for this choice, not merely NIH. And those technical reasons are? I realize that the shell-script-fu that most DHCP clients seem to require is a bit messy, but it does work, and it should be more than flexible enough to plug in some systemd-timesyncd controls. networkd allows consumers of network information (such as NTP servers, DNS resolvers, HTTP proxy brokers,...) to subscribe to this information (currently only via a C API [0], but could just as well have been dbus) and be notified of changes to it. Other DHCP clients will typically instead call a bunch of hooks (with env vars set) on every configuration change (and it is then presumably the job of the hook to instruct the NTP client, or whatever else, to change its config). Nb. chronyd's unit in Fedora has: ExecStartPost=/usr/libexec/chrony-helper add-dhclient-servers This is a script which gets NTP servers names from dhclient and feeds them to chronyd. Nothing prevents extending this script to get data from networkd, too. (sorry about slight offtopic). -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: timedatex replacing systemd-timedated for NTP packages
On Thu, Nov 27, 2014 at 1:53 PM, Tom Gundersen t...@jklm.no wrote: Hi Andrew, On Thu, Nov 27, 2014 at 10:00 PM, Andrew Lutomirski l...@mit.edu wrote: On Thu, Nov 27, 2014 at 12:51 PM, Tom Gundersen t...@jklm.no wrote: On Wed, Nov 26, 2014 at 3:10 PM, Chris Adams li...@cmadams.net wrote: Once upon a time, Tomasz Torcz to...@pipebreaker.pl said: On Wed, Nov 26, 2014 at 08:01:37AM -0600, Chris Adams wrote: Once upon a time, Florian Weimer fwei...@redhat.com said: Do we even use the DHCP NTP server assignment? I believe it is used for chrony and ntpd, don't know about sysmted's new implementation. systemd-timesyncd uses DHCP-provided NTP servers only if systemd-networkd is used as DHCP client. That should be a bug (and block it from use). There's no excuse for that other than not invented here. There are technical reasons for this choice, not merely NIH. And those technical reasons are? I realize that the shell-script-fu that most DHCP clients seem to require is a bit messy, but it does work, and it should be more than flexible enough to plug in some systemd-timesyncd controls. The whole model is just the wrong way around for how networkd/timesyncd works, so this is not simply a case of if (!networkd) return -EINVAL. networkd allows consumers of network information (such as NTP servers, DNS resolvers, HTTP proxy brokers,...) to subscribe to this information (currently only via a C API [0], but could just as well have been dbus) and be notified of changes to it. Other DHCP clients will typically instead call a bunch of hooks (with env vars set) on every configuration change (and it is then presumably the job of the hook to instruct the NTP client, or whatever else, to change its config). So basically the systemd model is one where the consumer pulls the information from the producer, where the traditional DHCP model the producer pushes the information to the consumer. It follows from this that anyone can be a consumer of any sort of information (so you can come along and implement your alternative NTP clients hooking into networkd just fine), but making a drop-in replacement for a producer of information is not necessarily that straightforward (you basically have to go out of your way to make sure you mimic all the interfaces etc). I guess this is how our stack works most of the time anyway, replacing things higher in the stack is always easier than replacing things lower in the stack (because the kernel does not have hooks to call into your browser, your browser calls into the kernel...). Now that's just the design, you can of course make whatever bash scripts do whatever briding in either direction to make things behave in any way you want. Should be straightforward to wire up timesyncd (maybe with a networkd configured to not do anything) to any shell-based dhclient, then, if anyone cared to do that. As a counterexample, I run some production servers with rather complicated network configurations. NetworkManager is a nonstarter, and I suspect that systemd-networkd will never work for them either. There are certainly still usecases we don't cover, but a-priori we are interested in making anything work, so feel free to give us ping over at the systemd ML if we lack some features you need. This isn't a complaint about either package -- I don't really expect them to understand my configuration. I use a Python script that reads a rather large hand-curated config file and outputs Debian interfaces(5) rules with a liberal sprinking of up and down directives. Yikes... We used to do it by hand, but there were too many things to configure... Anyway, I probably won't even try to make it work with systemd-networkd until I'm on a distro that uses systemd in the first place. Ubuntu is still using upstart (grumble). --Andy I do use NTP, and I don't really care much which implementation I'm using, but if systemd-timesyncd refuses to be reasonably configurable unless systemd-networkd is installed, I won't be using *that* any time soon either. You can of course still configure systemd-timesyncd to use a set of statically configured NTP servers, it is only the DHCP integration that currently requires networkd. That said, timesyncd is supposed to be this simple client that just works in the 99% of simple setups. If you have something fancy going on, it may very well be that you'll be better served by some other client (and that's just fine IMHO). And if Fedora becomes dependent on services that aren't configurable, My understanding is that timesyncd is meant to be a good enough default that just works, but not the one true NTP client. It is (or may at least one day be) a reasonable default, but it should clearly still be possible to exchange it with something else. Cheers, Tom [0]: http://cgit.freedesktop.org/systemd/systemd/tree/src/systemd/sd-network.h -- devel mailing list devel@lists.fedoraproject.org
Re: Entire process's environment attached to bugzillas by ABRT
On Thu, Nov 27, 2014 at 07:02:00PM +0100, Jan Kratochvil wrote: On Thu, 27 Nov 2014 16:23:57 +0100, Jakub Filak wrote: Do you find 'environ' attachment valuable or is ABRT just publishing personal information? No but I can imagine in some cases it may be useful. Is this a problem in practice? I don't recall ever seeing anything private in the hundreds of abrt traces I looked at. I checked the enironment of my shell, nothing interesting there, and I'm not aware of any services using environment variables to pass authentication data. If anything, the cwd and open fds reveal the most information, but they are also one of the most useful parts (in my experience, that is version strings and backtrace followed by open fds). Couldn't there be a way to send additional information upon bug assignee's request? That would be typically useful with the core files but reporters always said they cannot find the core file anywhere. Actually if the scheme that Jakub is working on is adopted and coredumps are stored by systemd, they will be available for longer, and it should often be possible to request a coredump after the fact. But in general depending on user help after the fact is most often futile. I wouldn't go there unless actual complaints about exposed data appear. Zbyszek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Best way to use zram in Fedora 21?
On Thu, Nov 27, 2014 at 04:42:36PM +0100, Juan Orti wrote: El 2014-11-27 14:48, Reindl Harald escribió: Am 27.11.2014 um 14:25 schrieb Juan Orti: Reindl, I'm of the opinion you should upload your scripts to some git repository and package them to be part of the distribution. I can co-maintain if you wish feel free to package it! that's why i attached it as i saw the topic i am not a active packager on the Fedora infrastrcuture Ok, I've uploaded the scripts to GitHub and submitted a review request: https://github.com/jorti/zram-swap https://bugzilla.redhat.com/show_bug.cgi?id=1168692 I have a question about the code: why are multiple swap devices needed? /sys/block/zram0/max_comp_streams can be set to whatever number is wanted. While it might be useful to have additional zram devices for different purposes, I don't think more than one zram swap is useful. If you only have one device, then reloading the module is no longer necessary to change the parameters, since everything else seems to be configurable through sysfs. Zbyszek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Best way to use zram in Fedora 21?
Am 28.11.2014 um 01:21 schrieb Zbigniew Jędrzejewski-Szmek: On Thu, Nov 27, 2014 at 04:42:36PM +0100, Juan Orti wrote: El 2014-11-27 14:48, Reindl Harald escribió: Am 27.11.2014 um 14:25 schrieb Juan Orti: Reindl, I'm of the opinion you should upload your scripts to some git repository and package them to be part of the distribution. I can co-maintain if you wish feel free to package it! that's why i attached it as i saw the topic i am not a active packager on the Fedora infrastrcuture Ok, I've uploaded the scripts to GitHub and submitted a review request: https://github.com/jorti/zram-swap https://bugzilla.redhat.com/show_bug.cgi?id=1168692 I have a question about the code: why are multiple swap devices needed? /sys/block/zram0/max_comp_streams can be set to whatever number is wanted. While it might be useful to have additional zram devices for different purposes, I don't think more than one zram swap is useful. If you only have one device, then reloading the module is no longer necessary to change the parameters, since everything else seems to be configurable through sysfs i admit that i am not really sure, that part found by Google around and maybe that's a relict of zram before it made it to the upstream kernel i guess /sys/block/zram0/max_comp_streams should be set to the number of CPU's and i ask my self why the default is 1 instead number of cores signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Best way to use zram in Fedora 21?
On Fri, Nov 28, 2014 at 01:21:26AM +0100, Zbigniew Jędrzejewski-Szmek wrote: On Thu, Nov 27, 2014 at 04:42:36PM +0100, Juan Orti wrote: El 2014-11-27 14:48, Reindl Harald escribió: Am 27.11.2014 um 14:25 schrieb Juan Orti: Reindl, I'm of the opinion you should upload your scripts to some git repository and package them to be part of the distribution. I can co-maintain if you wish feel free to package it! that's why i attached it as i saw the topic i am not a active packager on the Fedora infrastrcuture Ok, I've uploaded the scripts to GitHub and submitted a review request: https://github.com/jorti/zram-swap https://bugzilla.redhat.com/show_bug.cgi?id=1168692 I have a question about the code: why are multiple swap devices needed? /sys/block/zram0/max_comp_streams can be set to whatever number is wanted. While it might be useful to have additional zram devices for different purposes, I don't think more than one zram swap is useful. If you only have one device, then reloading the module is no longer necessary to change the parameters, since everything else seems to be configurable through sysfs. And another question (sorry, I never used compressed swap before): why not zswap? It seems to be a better fit for the desktop/server environments that Fedora is used for. IIUC, zswap is better because it overflows automatically into the backing swap device. Zbyszek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Best way to use zram in Fedora 21?
Am 28.11.2014 um 01:34 schrieb Zbigniew Jędrzejewski-Szmek: On Fri, Nov 28, 2014 at 01:21:26AM +0100, Zbigniew Jędrzejewski-Szmek wrote: On Thu, Nov 27, 2014 at 04:42:36PM +0100, Juan Orti wrote: El 2014-11-27 14:48, Reindl Harald escribió: Am 27.11.2014 um 14:25 schrieb Juan Orti: Reindl, I'm of the opinion you should upload your scripts to some git repository and package them to be part of the distribution. I can co-maintain if you wish feel free to package it! that's why i attached it as i saw the topic i am not a active packager on the Fedora infrastrcuture Ok, I've uploaded the scripts to GitHub and submitted a review request: https://github.com/jorti/zram-swap https://bugzilla.redhat.com/show_bug.cgi?id=1168692 I have a question about the code: why are multiple swap devices needed? /sys/block/zram0/max_comp_streams can be set to whatever number is wanted. While it might be useful to have additional zram devices for different purposes, I don't think more than one zram swap is useful. If you only have one device, then reloading the module is no longer necessary to change the parameters, since everything else seems to be configurable through sysfs. And another question (sorry, I never used compressed swap before): why not zswap? It seems to be a better fit for the desktop/server environments that Fedora is used for. IIUC, zswap is better because it overflows automatically into the backing swap device on machines with plenty RAM i prefer not have a swap partition or a swap file at all - especially on virtual machines it's a waste of (possible expensive SAN) disk storage on virtual servers currently i prefer zram inside the guest to avoid OOM conditions in the guest while the memory compression of the hypervisor steps in too late and is more for overcommit the host signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Trig functions from math.h
Les Howell wrote: I have some older code that used to compile, which I wish to reuse and maybe redesign. However the code is C and uses the sinf function, which seems to have disappeared from math.h. Can anyone tell me where this has gone? The man pages no longer return the sinf function, Info pages say that it should be in either math.h or complex.h, but it is not. The either math.h needs some modification (dated Sep 26 this year), and the man pages need updating, or the new function needs to be named, supported and the information on the Info pages needs to be updated. But in the interim, what is a work around? Please don't tell me I have to code a trig function. #define _DEFAULT_SOURCE or pass -D_DEFAULT_SOURCE to gcc. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Best way to use zram in Fedora 21?
ok to the naming and multi zram devices questions: 1) one single large space is wasteful if you have your machine up for longer than a single (or series ) of heavy lifting operations --say you are rendering a video and then back to the usual grind stuff would you want all that extra space just wasted ? also say a follow up process is in need of more would you wanna be stuck on previous values? zram is dynamic in nature smaller more numerous /dev/zram$i allows for that and in a dynamic manner... 2) it the RAM its based off not swap and the z is known as dynamic Corey W Sheldon Freelance IT Consultant, Multi-Discipline Tutor 310.909.7672 www.facebook.com/1stclassmobileshine On Thu, Nov 27, 2014 at 7:39 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 28.11.2014 um 01:34 schrieb Zbigniew Jędrzejewski-Szmek: On Fri, Nov 28, 2014 at 01:21:26AM +0100, Zbigniew Jędrzejewski-Szmek wrote: On Thu, Nov 27, 2014 at 04:42:36PM +0100, Juan Orti wrote: El 2014-11-27 14:48, Reindl Harald escribió: Am 27.11.2014 um 14:25 schrieb Juan Orti: Reindl, I'm of the opinion you should upload your scripts to some git repository and package them to be part of the distribution. I can co-maintain if you wish feel free to package it! that's why i attached it as i saw the topic i am not a active packager on the Fedora infrastrcuture Ok, I've uploaded the scripts to GitHub and submitted a review request: https://github.com/jorti/zram-swap https://bugzilla.redhat.com/show_bug.cgi?id=1168692 I have a question about the code: why are multiple swap devices needed? /sys/block/zram0/max_comp_streams can be set to whatever number is wanted. While it might be useful to have additional zram devices for different purposes, I don't think more than one zram swap is useful. If you only have one device, then reloading the module is no longer necessary to change the parameters, since everything else seems to be configurable through sysfs. And another question (sorry, I never used compressed swap before): why not zswap? It seems to be a better fit for the desktop/server environments that Fedora is used for. IIUC, zswap is better because it overflows automatically into the backing swap device on machines with plenty RAM i prefer not have a swap partition or a swap file at all - especially on virtual machines it's a waste of (possible expensive SAN) disk storage on virtual servers currently i prefer zram inside the guest to avoid OOM conditions in the guest while the memory compression of the hypervisor steps in too late and is more for overcommit the host -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Best way to use zram in Fedora 21?
I recall that multiple zram devices are due to the way the device is handled - there's some need for multiple devices to allow multiple cores to operate concurrently against it. zswap looks interesting. compcache/zram used to be able to setup a backing store that worked like zswap, but was poor performing. I think that if you wanted to eventually persist to disk, then zswap might be the way to go. If you don't want (or don't have) hard swap, then zram. On Fri Nov 28 2014 at 13:41:42 Corey Sheldon sheldon.co...@gmail.com wrote: ok to the naming and multi zram devices questions: 1) one single large space is wasteful if you have your machine up for longer than a single (or series ) of heavy lifting operations --say you are rendering a video and then back to the usual grind stuff would you want all that extra space just wasted ? also say a follow up process is in need of more would you wanna be stuck on previous values? zram is dynamic in nature smaller more numerous /dev/zram$i allows for that and in a dynamic manner... 2) it the RAM its based off not swap and the z is known as dynamic Corey W Sheldon Freelance IT Consultant, Multi-Discipline Tutor 310.909.7672 www.facebook.com/1stclassmobileshine On Thu, Nov 27, 2014 at 7:39 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 28.11.2014 um 01:34 schrieb Zbigniew Jędrzejewski-Szmek: On Fri, Nov 28, 2014 at 01:21:26AM +0100, Zbigniew Jędrzejewski-Szmek wrote: On Thu, Nov 27, 2014 at 04:42:36PM +0100, Juan Orti wrote: El 2014-11-27 14:48, Reindl Harald escribió: Am 27.11.2014 um 14:25 schrieb Juan Orti: Reindl, I'm of the opinion you should upload your scripts to some git repository and package them to be part of the distribution. I can co-maintain if you wish feel free to package it! that's why i attached it as i saw the topic i am not a active packager on the Fedora infrastrcuture Ok, I've uploaded the scripts to GitHub and submitted a review request: https://github.com/jorti/zram-swap https://bugzilla.redhat.com/show_bug.cgi?id=1168692 I have a question about the code: why are multiple swap devices needed? /sys/block/zram0/max_comp_streams can be set to whatever number is wanted. While it might be useful to have additional zram devices for different purposes, I don't think more than one zram swap is useful. If you only have one device, then reloading the module is no longer necessary to change the parameters, since everything else seems to be configurable through sysfs. And another question (sorry, I never used compressed swap before): why not zswap? It seems to be a better fit for the desktop/server environments that Fedora is used for. IIUC, zswap is better because it overflows automatically into the backing swap device on machines with plenty RAM i prefer not have a swap partition or a swap file at all - especially on virtual machines it's a waste of (possible expensive SAN) disk storage on virtual servers currently i prefer zram inside the guest to avoid OOM conditions in the guest while the memory compression of the hypervisor steps in too late and is more for overcommit the host -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Entire process's environment attached to bugzillas by ABRT
On Thu, 2014-11-27 at 19:02 +0100, Jan Kratochvil wrote: On Thu, 27 Nov 2014 16:23:57 +0100, Jakub Filak wrote: Do you find 'environ' attachment valuable or is ABRT just publishing personal information? No but I can imagine in some cases it may be useful. Couldn't there be a way to send additional information upon bug assignee's request? That would be typically useful with the core files but reporters always said they cannot find the core file anywhere. Yes, but it is not trivial to implement. I did the first step and opened the following pull request: https://github.com/abrt/gnome-abrt/pull/95 The patch enables users to filter problems by Bugzilla ID in gnome-abrt. So you can ask the report to write Bugzilla ID to the search field in gnome-abrt and it should show him the original ABRT problem. 'coredump' is stored in $DATA_DIRECTORY and the path to $DATA_DIRECTORY can be found under Details (bottom-right corner). Jakub -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Entire process's environment attached to bugzillas by ABRT
On Fri, 2014-11-28 at 00:28 +0100, Zbigniew Jędrzejewski-Szmek wrote: On Thu, Nov 27, 2014 at 07:02:00PM +0100, Jan Kratochvil wrote: On Thu, 27 Nov 2014 16:23:57 +0100, Jakub Filak wrote: Do you find 'environ' attachment valuable or is ABRT just publishing personal information? No but I can imagine in some cases it may be useful. Is this a problem in practice? Unfortunately yes, I started this thread after participating in a discussion about leaking personal information in 'environment'. I don't recall ever seeing anything private in the hundreds of abrt traces I looked at. I checked the enironment of my shell, nothing interesting there, and I'm not aware of any services using environment variables to pass authentication data. The discussion I mentioned above was primarily about OpenStack (but the participants also expressed concerns about sending 'environ' to Bugzilla at all), where people are regularly storing their passwords and tokens as environment variables. If anything, the cwd and open fds reveal the most information, but they are also one of the most useful parts (in my experience, that is version strings and backtrace followed by open fds). Couldn't there be a way to send additional information upon bug assignee's request? That would be typically useful with the core files but reporters always said they cannot find the core file anywhere. Actually if the scheme that Jakub is working on is adopted and coredumps are stored by systemd, they will be available for longer, and it should often be possible to request a coredump after the fact. But in general depending on user help after the fact is most often futile. I wouldn't go there unless actual complaints about exposed data appear. I opened the following bugzilla bug for those who store private data as environment variables: https://bugzilla.redhat.com/show_bug.cgi?id=1168494 Regards, Jakub -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Heads up CouchDB and RabbitMQ users!
Hello All! I've finally found time to fix a very long-standing issue with Erlang applications pulling in a lot of X11-related rpms during the installation. See these two Bugzilla tickets for the details: * https://bugzilla.redhat.com/784693 (Fedora) * https://bugzilla.redhat.com/1161922 (EPEL 7) Now fresh headless Fedora 21+ (and even EPEL7 is you live dangerously enough to use epel-testing) installations of CouchDB or RabbitMQ won't pull a long tail of packages related to GUI, which is great. Now you'll get a more slim and tiny containers with CouchDB or RabbitMQ inside. Some of the out-of-the-box Erlang/OTP functionality was intentionally cut off. Namely the ability to remotely connect to debugger on the headless node or running dialyzer there - if you try to install the packages necessary for the remote debugging they will install all the X11 stuff again. I believe this isn't a serious issue though (nevertheless I'll try to address it as time permits). However I'd love to gather some unusual user experience - if you're using debugger, dialyzer, observer, applications remotely on a production node then please talk to me. I believe that the only application which needs to be de-X11-ied further is observer since my experience tells me than nobody runs dialyzer (static Erlang code checker) on the production node remotely (unlike running observer which is necessary in some cases). Prove me wrong if you can! if you're just a casual CouchDB or RabbitMQ user then I believe you won't notice anything (except of more slim and tiny containers with Erlang applications inside). However if you see something strange then file a Bugzilla ticket ASAP! -- With best regards, Peter Lemenkov. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1163257] perl-Mixin-ExtraFields-0.140002 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1163257 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #5 from Fedora Update System upda...@fedoraproject.org --- Package perl-Mixin-ExtraFields-0.140002-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing perl-Mixin-ExtraFields-0.140002-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-15797/perl-Mixin-ExtraFields-0.140002-1.fc19 then log in and leave karma (feedback). -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=d4TvS7rbgCa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1167717] perl-MooX-Options-4.013 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1167717 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System upda...@fedoraproject.org --- Package perl-MooX-Options-4.013-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing perl-MooX-Options-4.013-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-15806/perl-MooX-Options-4.013-1.fc20 then log in and leave karma (feedback). -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=sgxXYZHR7Ja=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Object-InsideOut] Bootstrapping done
commit 5dc37b50321d2e471ac5410d1d1531b78c9512cb
Author: Paul Howarth p...@city-fan.org
Date: Thu Nov 27 09:18:41 2014 +
Bootstrapping done
perl-Object-InsideOut.spec |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
---
diff --git a/perl-Object-InsideOut.spec b/perl-Object-InsideOut.spec
index 80d16c7..2606e55 100644
--- a/perl-Object-InsideOut.spec
+++ b/perl-Object-InsideOut.spec
@@ -1,8 +1,6 @@
-%global perl_bootstrap 1
-
Name: perl-Object-InsideOut
Version:3.98
-Release:5%{?dist}
+Release:6%{?dist}
Summary:Comprehensive inside-out object support module
Group: Development/Libraries
License:GPL+ or Artistic
@@ -84,6 +82,9 @@ make test
%changelog
+* Thu Nov 27 2014 Paul Howarth p...@city-fan.org - 3.98-6
+- Bootstrapping done
+
* Tue Nov 18 2014 Paul Howarth p...@city-fan.org - 3.98-5
- Bootstrap build for Math::Random::MT::Auto on arm
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1163246] perl-Inline-C-0.66 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1163246 Petr Šabata psab...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-Inline-C-0.67-1.fc22 Resolution|--- |RAWHIDE Last Closed||2014-11-27 04:25:37 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=9ANKkyYfy4a=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Object-InsideOut] Created tag perl-Object-InsideOut-3.98-6.fc22
The lightweight tag 'perl-Object-InsideOut-3.98-6.fc22' was created pointing to: 5dc37b5... Bootstrapping done -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] ddick:perl-Net-Pcap set point of contact to: ddick
user: ddick changed point of contact of package: perl-Net-Pcap from: orphan to: ddick on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Net-Pcap -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] ddick:perl-Net-Pcap commit set to Approved
user: ddick set for ddick acl: commit of package: perl-Net-Pcap from: Approved to: Approved on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Net-Pcap -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] ddick:perl-Net-Pcap watchbugzilla set to Approved
user: ddick set for ddick acl: watchbugzilla of package: perl-Net-Pcap from: Approved to: Approved on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Net-Pcap -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] ddick:perl-Net-Pcap approveacls set to Approved
user: ddick set for ddick acl: approveacls of package: perl-Net-Pcap from: Approved to: Approved on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Net-Pcap -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] ddick:perl-Net-Pcap watchcommits set to Approved
user: ddick set for ddick acl: watchcommits of package: perl-Net-Pcap from: Approved to: Approved on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Net-Pcap -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File IO-Socket-SSL-2.007.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-IO-Socket-SSL: 0eedd741976b913323acebdd692e6a26 IO-Socket-SSL-2.007.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Socket-SSL] Update to 2.007
commit bc89e9047697a3d6ed821dd13a299ccdc41f636a
Author: Paul Howarth p...@city-fan.org
Date: Thu Nov 27 10:52:47 2014 +
Update to 2.007
- New upstream release 2.007
- Make getline/readline fall back to super class if class is not sslified
yet, i.e. behave the same as sysread, syswrite etc. (CPAN RT#100529)
...-SSL-2.007-use-system-default-SSL-version.patch |2 +-
perl-IO-Socket-SSL.spec|9 +++--
sources|2 +-
3 files changed, 9 insertions(+), 4 deletions(-)
---
diff --git a/IO-Socket-SSL-2.006-use-system-default-SSL-version.patch
b/IO-Socket-SSL-2.007-use-system-default-SSL-version.patch
similarity index 98%
rename from IO-Socket-SSL-2.006-use-system-default-SSL-version.patch
rename to IO-Socket-SSL-2.007-use-system-default-SSL-version.patch
index 460b0d1..f39023e 100644
--- a/IO-Socket-SSL-2.006-use-system-default-SSL-version.patch
+++ b/IO-Socket-SSL-2.007-use-system-default-SSL-version.patch
@@ -9,7 +9,7 @@
SSL_verify_callback = undef,
SSL_verifycn_scheme = undef, # fallback cn verification
SSL_verifycn_publicsuffix = undef, # fallback default list verification
-@@ -2068,7 +2068,7 @@ WARN
+@@ -2069,7 +2069,7 @@ WARN
$ssl_op |= Net::SSLeay::OP_SINGLE_DH_USE;
$ssl_op |= Net::SSLeay::OP_SINGLE_ECDH_USE if $can_ecdh;
diff --git a/perl-IO-Socket-SSL.spec b/perl-IO-Socket-SSL.spec
index 3fefe35..b89542c 100644
--- a/perl-IO-Socket-SSL.spec
+++ b/perl-IO-Socket-SSL.spec
@@ -1,5 +1,5 @@
Name: perl-IO-Socket-SSL
-Version: 2.006
+Version: 2.007
Release: 1%{?dist}
Summary: Perl library for transparent SSL
Group: Development/Libraries
@@ -7,7 +7,7 @@ License:GPL+ or Artistic
URL: http://search.cpan.org/dist/IO-Socket-SSL/
Source0:
http://search.cpan.org/CPAN/authors/id/S/SU/SULLR/IO-Socket-SSL-%{version}.tar.gz
Patch0:IO-Socket-SSL-2.006-use-system-default-cipher-list.patch
-Patch1:IO-Socket-SSL-2.006-use-system-default-SSL-version.patch
+Patch1:IO-Socket-SSL-2.007-use-system-default-SSL-version.patch
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(id -nu)
BuildArch: noarch
# Module Build
@@ -112,6 +112,11 @@ rm -rf %{buildroot}
%{_mandir}/man3/IO::Socket::SSL::Utils.3*
%changelog
+* Thu Nov 27 2014 Paul Howarth p...@city-fan.org - 2.007-1
+- Update to 2.007
+ - Make getline/readline fall back to super class if class is not sslified
+yet, i.e. behave the same as sysread, syswrite etc. (CPAN RT#100529)
+
* Sun Nov 23 2014 Paul Howarth p...@city-fan.org - 2.006-1
- Update to 2.006
- Make SSLv3 available even if the SSL library disables it by default in
diff --git a/sources b/sources
index 3e584ca..f634d95 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-cbb09143c0d697fc44dac1226641eb41 IO-Socket-SSL-2.006.tar.gz
+0eedd741976b913323acebdd692e6a26 IO-Socket-SSL-2.007.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Socket-SSL] Created tag perl-IO-Socket-SSL-2.007-1.fc22
The lightweight tag 'perl-IO-Socket-SSL-2.007-1.fc22' was created pointing to: bc89e90... Update to 2.007 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File Algorithm-Diff-1.1903.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-Algorithm-Diff: 0e8add21a641b8d66436df0c2024bf3b Algorithm-Diff-1.1903.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Algorithm-Diff] Update to 1.1903
commit af25f4aabb14e0443db63d201f6e2ccc7c63122e
Author: Paul Howarth p...@city-fan.org
Date: Thu Nov 27 12:13:12 2014 +
Update to 1.1903
- New upstream release 1.1903
- Fix documentation typos (CPAN RT#84981)
- Add -w and -i switches to diffnew.pl (CPAN RT#69945)
- Remove Algorithm::DiffOld from the index; the module is still
distributed
with Algorithm::Diff, but is not indexed on CPAN because this is an
***UNAUTHORIZED*** release of Algorithm::DiffOld
- Add patch to generate provide for perl(Algorithm::DiffOld)
- Drop %defattr, redundant since rpm 4.4
- General spec tidy-up
.gitignore |2 +-
Algorithm-Diff-1.1903-provides.patch | 12 ++
perl-Algorithm-Diff.spec | 68 +-
sources |2 +-
4 files changed, 56 insertions(+), 28 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index aa2d248..7578227 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1 @@
-Algorithm-Diff-1.1902.tar.gz
+/Algorithm-Diff-[0-9.]*.tar.gz
diff --git a/Algorithm-Diff-1.1903-provides.patch
b/Algorithm-Diff-1.1903-provides.patch
new file mode 100644
index 000..959961e
--- /dev/null
+++ b/Algorithm-Diff-1.1903-provides.patch
@@ -0,0 +1,12 @@
+--- lib/Algorithm/DiffOld.pm
lib/Algorithm/DiffOld.pm
+@@ -2,8 +2,7 @@
+ # like versions = 0.59 used to.
+ # $Revision: 1.3 $
+
+-package # don't index
+-Algorithm::DiffOld;
++package Algorithm::DiffOld;
+ use strict;
+ use vars qw($VERSION @EXPORT_OK @ISA @EXPORT);
+ use integer; # see below in _replaceNextLargerWith() for mod to make
diff --git a/perl-Algorithm-Diff.spec b/perl-Algorithm-Diff.spec
index 9152f57..b64a840 100644
--- a/perl-Algorithm-Diff.spec
+++ b/perl-Algorithm-Diff.spec
@@ -1,64 +1,80 @@
Name: perl-Algorithm-Diff
-Version:1.1902
-Release:21%{?dist}
-Summary:Algorithm::Diff Perl module
+Version:1.1903
+Release:1%{?dist}
+Summary:Compute `intelligent' differences between two files/lists
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/Algorithm-Diff/
Source0:
http://www.cpan.org/authors/id/T/TY/TYEMQ/Algorithm-Diff-%{version}.tar.gz
-BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
+Patch0: Algorithm-Diff-1.1903-provides.patch
+BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(id -nu)
BuildArch: noarch
+# Build:
+BuildRequires: perl
BuildRequires: perl(ExtUtils::MakeMaker)
# Run-time:
BuildRequires: perl(Carp)
BuildRequires: perl(Exporter)
+BuildRequires: perl(integer)
+BuildRequires: perl(strict)
+BuildRequires: perl(vars)
# Tests:
BuildRequires: perl(Data::Dumper)
BuildRequires: perl(lib)
BuildRequires: perl(Test)
-Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+# Explicit requirements:
+Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
Requires: perl(Carp)
%description
-This is a module for computing the difference between two files, two
-strings, or any other two lists of things. It uses an intelligent
-algorithm similar to (or identical to) the one used by the Unix diff
-program. It is guaranteed to find the *smallest possible* set of
-differences.
+This is a module for computing the difference between two files, two strings,
+or any other two lists of things. It uses an intelligent algorithm similar to
+(or identical to) the one used by the Unix diff program. It is guaranteed to
+find the *smallest possible* set of differences.
%prep
%setup -q -n Algorithm-Diff-%{version}
-chmod 644 *.pl
+
+# Generate provide for perl(Algorithm::DiffOld)
+%patch0
%build
-%{__perl} Makefile.PL INSTALLDIRS=vendor
+perl Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
-rm -rf $RPM_BUILD_ROOT
-
-make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
-
-find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \;
-find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2/dev/null \;
+rm -rf %{buildroot}
+make pure_install DESTDIR=%{buildroot}
+find %{buildroot} -type f -name .packlist -exec rm -f {} \;
+%{_fixperms} %{buildroot}
-%{_fixperms} $RPM_BUILD_ROOT/*
-
-rm -f $RPM_BUILD_ROOT%{perl_vendorlib}/Algorithm/*.pl
+# Remove example scripts we're shipping as documentation
+rm -f %{buildroot}%{perl_vendorlib}/Algorithm/*.pl
%check
make test
%clean
-rm -rf $RPM_BUILD_ROOT
+rm -rf %{buildroot}
%files
-%defattr(-,root,root,-)
%doc Changes README *.pl
-%{perl_vendorlib}/*
-%{_mandir}/man3/*
+%{perl_vendorlib}/Algorithm/
+%{_mandir}/man3/Algorithm::Diff.3*
+%{_mandir}/man3/Algorithm::DiffOld.3*
%changelog
+* Thu Nov 27 2014 Paul Howarth p...@city-fan.org - 1.1903-1
+- Update to 1.1903
+ - Fix documentation typos (CPAN RT#84981)
+ - Add -w and -i switches to diffnew.pl (CPAN
[Bug 1163236] perl-Git-CPAN-Patch-2.0.3 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1163236 --- Comment #1 from Petr Šabata psab...@redhat.com --- This requires a number of modules not yet packaged for Fedora. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=tVXVT4fRFda=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1163236] perl-Git-CPAN-Patch-2.0.3 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1163236 Petr Šabata psab...@redhat.com changed: What|Removed |Added Depends On||1168612 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1168612 [Bug 1168612] Review Request: perl-List-Pairwise - Map/grep arrays and hashes pairwise -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=aveKkbK89pa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Algorithm-Diff] Created tag perl-Algorithm-Diff-1.1903-1.fc22
The lightweight tag 'perl-Algorithm-Diff-1.1903-1.fc22' was created pointing to: af25f4a... Update to 1.1903 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Apache-Session approveacls set to Approved
user: psabata set for pghmcfc acl: approveacls of package: perl-Apache-Session from: Awaiting Review to: Approved on branch: master To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Apache-Session -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Apache-Session approveacls set to Approved
user: psabata set for pghmcfc acl: approveacls of package: perl-Apache-Session from: Awaiting Review to: Approved on branch: f21 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Apache-Session -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Apache-Session approveacls set to Approved
user: psabata set for pghmcfc acl: approveacls of package: perl-Apache-Session from: Awaiting Review to: Approved on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Apache-Session -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Apache-Session approveacls set to Approved
user: psabata set for pghmcfc acl: approveacls of package: perl-Apache-Session from: Awaiting Review to: Approved on branch: f20 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Apache-Session -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Apache-Session approveacls set to Approved
user: psabata set for pghmcfc acl: approveacls of package: perl-Apache-Session from: Awaiting Review to: Approved on branch: f19 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Apache-Session -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Apache-Session approveacls set to Approved
user: psabata set for pghmcfc acl: approveacls of package: perl-Apache-Session from: Awaiting Review to: Approved on branch: el5 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Apache-Session -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Regexp-Assemble commit set to Approved
user: psabata set for pghmcfc acl: commit of package: perl-Regexp-Assemble from: Awaiting Review to: Approved on branch: f19 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Regexp-Assemble -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Regexp-Assemble commit set to Approved
user: psabata set for pghmcfc acl: commit of package: perl-Regexp-Assemble from: Awaiting Review to: Approved on branch: f21 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Regexp-Assemble -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Regexp-Assemble commit set to Approved
user: psabata set for pghmcfc acl: commit of package: perl-Regexp-Assemble from: Awaiting Review to: Approved on branch: f20 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Regexp-Assemble -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Algorithm-Diff commit set to Approved
user: psabata set for pghmcfc acl: commit of package: perl-Algorithm-Diff from: Awaiting Review to: Approved on branch: el5 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Algorithm-Diff -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Algorithm-Diff commit set to Approved
user: psabata set for pghmcfc acl: commit of package: perl-Algorithm-Diff from: Awaiting Review to: Approved on branch: f19 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Algorithm-Diff -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Algorithm-Diff commit set to Approved
user: psabata set for pghmcfc acl: commit of package: perl-Algorithm-Diff from: Awaiting Review to: Approved on branch: master To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Algorithm-Diff -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Algorithm-Diff commit set to Approved
user: psabata set for pghmcfc acl: commit of package: perl-Algorithm-Diff from: Awaiting Review to: Approved on branch: f20 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Algorithm-Diff -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Apache-Session commit set to Approved
user: psabata set for pghmcfc acl: commit of package: perl-Apache-Session from: Awaiting Review to: Approved on branch: el5 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Apache-Session -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Apache-Session commit set to Approved
user: psabata set for pghmcfc acl: commit of package: perl-Apache-Session from: Awaiting Review to: Approved on branch: master To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Apache-Session -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[PkgDB] psabata:perl-Apache-Session commit set to Approved
user: psabata set for pghmcfc acl: commit of package: perl-Apache-Session from: Awaiting Review to: Approved on branch: el6 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Apache-Session -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
