EPEL epel beta report: 20140701 changes
Compose started at Tue Jul 1 08:15:03 UTC 2014 New package: backupninja-1.0.1-3.el7 Lightweight, extensible backup system New package: calendar-1.28-1.20140613cvs.el7 Reminder utility New package: freecolor-0.9.2-2.el7 Display memory information graphically New package: jpeginfo-1.6.1-2.el7 Error-check and generate informative listings from JPEG files New package: jpegoptim-1.4.1-2.el7 Utility to optimize JPEG files New package: nagios-plugins-check-updates-1.6.7-1.el7 A Nagios plugin to check if Red Hat or Fedora system is up-to-date New package: nodejs-weak-map-1.0.5-1.el7 A WeakMap shim for Node.js and browsers New package: perl-Nagios-Plugin-0.36-7.el7 Family of perl modules to streamline writing Nagios plugins New package: sispmctl-3.1-1.el7 Control Gembird SIS-PM programmable power outlet strips Updated Packages: cppcheck-1.63-3.el7 --- * Mon Jun 30 2014 Matěj Cepl mc...@redhat.com - 1.63-3 - Bump release for new libtinyxml ctstream-20-1.el7 - * Mon Jun 30 2014 Petr Pisar ppi...@redhat.com - 20-1 - Version 20 bump easytag-2.2.3-1.el7 --- * Sun Jun 22 2014 David King amigad...@amigadave.com 2.2.3-1 - Update to 2.2.3 libva-1.2.1-3.el7 - * Fri Jun 20 2014 Elad Alfassa e...@fedoraproject.org - 1.2.1-3 - Apply upstream patch to fix a firefox crash (rhbz #1105890) * Sat Aug 03 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org - 1.2.1-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild mono-2.10.8-7.el7 - * Mon Jun 30 2014 Leigh Scott leigh123li...@googlemail.com - 2.10.8-7 - add some obsoletes (bz 1114673) nfs-ganesha-2.1.0-1.el7 --- * Mon Jun 30 2014 Kaleb S. KEITHLEY kkeithle at redhat.com 2.1.0-1 - nfs-ganesha-2.1.0 GA * Sat Jun 07 2014 Fedora Release Engineering rel-...@lists.fedoraproject.org - 2.0.0-10 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild ocserv-0.8.1-1.el7 -- * Mon Jun 30 2014 Nikos Mavrogiannopoulos n...@redhat.com - 0.8.1-1 - New upstream release puppet-3.6.2-2.el7 -- * Mon Jun 30 2014 Pádraig Brady pbr...@redhat.com - 3.6.2-2 - Allow yumrepo proxy attribute to be set to _none_ python-click-2.2-1.el7 -- * Mon Jun 30 2014 Robert Kuska rku...@redhat.com - 2.2-1 - Update to 2.2 python-moksha-hub-1.3.4-1.el7 - * Mon Jun 30 2014 Ralph Bean rb...@redhat.com - 1.3.4-1 - Improved exception handling in the consumer API. srcpd-2.1.2-4.el7 - * Mon Jun 30 2014 Jakub Čajka jca...@redhat.com - 2.1.2-4 - Changed exclude to exclusive arch i386 i486 i586 i686 pentium3 pentium4 athlon geode armv3l armv4b armv4l armv4tl armv5tel armv5tejl armv6l armv7l armv7hl armv7hnl x86_64 xrootd-4.0.0-1.el7 -- * Sun Jun 29 2014 Mattias Ellert mattias.ell...@fysast.uu.se - 1:4.0.0-1 - Update to version 4.0.0 - Remove the perl package - no longer part of upstream sources * Sun Jun 08 2014 Fedora Release Engineering rel-...@lists.fedoraproject.org - 1:3.3.6-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild Summary: Added Packages: 9 Removed Packages: 0 Modified Packages: 12 ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
EPEL Fedora 5 updates-testing report
The following Fedora EPEL 5 Security updates need testing: Age URL 800 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5630/bugzilla-3.2.10-5.el5 254 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11893/libguestfs-1.20.12-1.el5 135 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-0581/augeas-1.2.0-1.el5 19 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1626/puppet-2.7.26-1.el5 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1697/zabbix20-2.0.12-2.el5 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1696/perl-Email-Address-1.905-1.el5 4 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1747/mediawiki119-1.19.17-1.el5 2 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1767/cacti-0.8.8b-7.el5 1 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1780/zarafa-7.1.10-1.el5,php53-mapi-7.1.10-1.el5 The following builds have been pushed to Fedora EPEL 5 updates-testing R-qtl-1.32.10-3.el5 gfal2-python-1.5.0-1.el5 ovirt-guest-agent-1.0.10-1.el5 root-5.34.18-4.el5 srcpd-2.1.2-4.el5 Details about builds: R-qtl-1.32.10-3.el5 (FEDORA-EPEL-2014-1794) Tools for analyzing QTL experiments Update Information: - run tests also on secondary arches Version 1.32, 2014-05-28: Major changes: * None. Minor changes: * fitqtl with model=normal now returns residuals as an attribute. * Added an additional argument to plot.scanone, bgrect, for making the background of the plotting region a different color. * Revised cleanGeno to work with any cross having two possible genotypes (i.e., not just bc but also riself, risib, dh, haploid). * Revised summary.cross so that overall genotype frequencies are given separately for autosomes and the X chromosome. * Fixed typo in a warning in add.threshold. * Fixed a bug in reduce2grid, regarding format of attributes * Fixed a bug in MQM: in some circumstances, the last marker was always included as cofactor; other cleanup in MQM code. Version 1.32, 2014-05-28: Major changes: * None. Minor changes: * fitqtl with model=normal now returns residuals as an attribute. * Added an additional argument to plot.scanone, bgrect, for making the background of the plotting region a different color. * Revised cleanGeno to work with any cross having two possible genotypes (i.e., not just bc but also riself, risib, dh, haploid). * Revised summary.cross so that overall genotype frequencies are given separately for autosomes and the X chromosome. * Fixed typo in a warning in add.threshold. * Fixed a bug in reduce2grid, regarding format of attributes * Fixed a bug in MQM: in some circumstances, the last marker was always included as cofactor; other cleanup in MQM code. Version 1.32, 2014-05-28: Major changes: * None. Minor changes: * fitqtl with model=normal now returns residuals as an attribute. * Added an additional argument to plot.scanone, bgrect, for making the background of the plotting region a different color. * Revised cleanGeno to work with any cross having two possible genotypes (i.e., not just bc but also riself, risib, dh, haploid). * Revised summary.cross so that overall genotype frequencies are given separately for autosomes and the X chromosome. * Fixed typo in a warning in add.threshold. * Fixed a bug in reduce2grid, regarding format of attributes * Fixed a bug in MQM: in some circumstances, the last marker was always included as cofactor; other cleanup in MQM code. Version 1.32, 2014-05-28: Major changes: * None. Minor changes: * fitqtl with model=normal now returns residuals as an attribute. * Added an additional argument to plot.scanone, bgrect, for making the background of the plotting region a different color. * Revised cleanGeno to work with any cross having two possible genotypes (i.e., not just bc but also riself, risib, dh, haploid). * Revised summary.cross so that overall genotype frequencies are given separately for autosomes and the X chromosome. * Fixed typo in a warning in add.threshold. * Fixed a bug in reduce2grid, regarding format of attributes * Fixed a bug in MQM: in some circumstances, the last marker was always included as cofactor; other cleanup in MQM code. ChangeLog: * Tue Jul 1 2014 Jakub Čajka jca...@redhat.com - 1.32.10-3 - Changed stack limit on ppc64 and s390x to allow checks to pass * Sat Jun 28 2014 Mattias Ellert mattias.ell...@fysast.uu.se - 1.32.10-2 - Disable checks on ppc64 * Wed Jun 25 2014 Mattias Ellert mattias.ell...@fysast.uu.se - 1.32.10-1 - Update to 1.32.10 - Use R-core-devel instead of R-devel as BR - Re-enable checks * Fri Jun 6 2014 Fedora Release Engineering rel-...@lists.fedoraproject.org - 1.31.9-2 - Rebuilt for
Re: fedora-release-$PRODUCT, /etc/issue, /etc/os-release, Per-Product Configs and more!
Dne 30.6.2014 20:59, Stephen Gallagher napsal(a): 2) The fedora-release-$PRODUCT package (and possibly %post or systemd snippets therein) will be responsible for the creation and maintenance of /etc/issue, /etc/os-release and /etc/fedora-release-product (note: there is no $ there. That's the literal name. This file will be equivalent to /etc/fedora-release except that it will include the Product name. Could you please clarify, if you are going to preserve /etc/fedora-release on not? It is unclear to me from your wording ... Vít -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
free seats in Env and Stacks WG - volunteers wanted
Env and Stacks Working Group has noble plan to make development in Fedora easier and also work with new technologies, which are not in Fedora yet. The whole statement can be found here: https://fedoraproject.org/wiki/Env_and_Stacks/Product_Requirements_Document There is missing Atomic and/or Docker, because all members were mostly interested in things mentioned in the document than looking at containers. I believe we need someone who can pick what will be in Fedora base image. Details can be found in Matt statement: https://lists.fedoraproject.org/pipermail/env-and-stacks/2014-June/000431.html We don't have manpower to work on all projects, but we started to work or co-operate on these: 1/ testing additional repositories – Playground repo https://fedoraproject.org/wiki/Changes/Playground_repository Playground plugin is similar to Copr plugin http://dnf.baseurl.org/2014/03/19/copr-plugin/ 2/ automation – Automated packages review tools https://fedoraproject.org/wiki/Env_and_Stacks/Changes_Drafts/Automated_packages_review_tools 3/ automation – Taskotron tool for Fedora tests https://fedoraproject.org/wiki/User:Tflink/taskotron_development_plan 4/ Build Systems – Copr http://copr.fedoraproject.org/ 5/ Software Collections in Fedora https://fedoraproject.org/wiki/Changes/SCL 6/ DevAssistant http://devassistant.org/ 7/ Continuous Integration - prototype of few projects If you are interested in current topics or containers, then please let us know on env-and-sta...@lists.fedoraproject.org what you want to do and what you did until now. I received some private replies, but I'd like to give opportunity to wider audience. Thanks, Marcela -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Review Swap
Hi, I have a python module for review swap, hope someone can do me a favour, https://bugzilla.redhat.com/show_bug.cgi?id=689 Thanks. Thanks. Yours sincerely, Christopher Meng Noob here. http://cicku.me -- 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: Review Swap
On Tue, 2014-07-01 at 18:19 +0800, Christopher Meng wrote: Hi, Hi Christopher, I have a python module for review swap, hope someone can do me a favour, https://bugzilla.redhat.com/show_bug.cgi?id=689 I've taken it up. Can you please review vit in return? It's a really quick review too :) https://bugzilla.redhat.com/show_bug.cgi?id=1112072 -- Thanks, Warm regards, Ankur (FranciscoD) http://fedoraproject.org/wiki/User:Ankursinha Join Fedora! Come talk to us! http://fedoraproject.org/wiki/Fedora_Join_SIG signature.asc Description: This is a digitally signed message part -- 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: Review Swap
On Tue, Jul 1, 2014 at 6:32 PM, Ankur Sinha sanjay.an...@gmail.com wrote: I've taken it up. Can you please review vit in return? It's a really quick review too :) https://bugzilla.redhat.com/show_bug.cgi?id=1112072 No problem. Yours sincerely, Christopher Meng Noob here. http://cicku.me -- 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: Heads-up on rpm 4.12 coming to rawhide soon
On 06/30/2014 04:27 PM, Vít Ondruch wrote:
Dne 30.6.2014 15:14, Panu Matilainen napsal(a):
On 06/30/2014 03:48 PM, Panu Matilainen wrote:
On 06/30/2014 03:12 PM, Vít Ondruch wrote:
Interesting, it breaks Ruby build it seems:
http://koji.fedoraproject.org/koji/taskinfo?taskID=7090194
Not sure about the reason, though.
Seems the ruby macros are not expanding properly throughout the spec,
please file a bug.
I'd call this at least partially self-inflicted pain, its the %load
trickery thats failing. Call your own version of %load something else
and it'll work like before.
The syntax for the built-in macro is %{load:file} but the argument
is not macro expanded so %{SOURCEn} will get passed in literally.
Which obviously wont work.
- Panu -
Yes, that will do the trick probably.
However, now I am wondering, is there a way how to build SRPM, which is
using the new load feature from 4.12 using old 4.11 RPM? With old RPM,
I've got this error:
```
$ fedpkg srpm
error: line 94: Unknown tag:
/home/vondruch/fedora-scm/maintain/ruby/macros.ruby
error: query of specfile
/home/vondruch/fedora-scm/maintain/ruby/ruby.spec failed, can't parse
Could not execute srpm: need more than 0 values to unpack
```
I suppose the answer is NO, but I hope for some pleasant surprise ;)
For just creating an src.rpm, I suppose you can use a simple spec
conditional, eg
# permit src.rpm creation on older versions
%if %{fedora} = 21
%{load:...}
%endif
Anyway, like mentioned earlier, %{load:%{SOURCE4}} would not have worked
yesterday as %{load:} didn't macro-expand its argument, that has been
fixed in rpm-4.11.90-0.git12844.3.fc21 (just building now). So thanks
for trying to use that feature :)
- Panu -
--
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: Fedora 21 Changes Freeze in two weeks - 2014-07-08
- Original Message - Greetings! Fedora 21 Changes Freeze is currently scheduled to no earlier than 2014-07-08 [1] and we're getting closer to this date. Btw this is also Fedora 21 Branch from Rawhide date. The Fedora Changes Freeze is now set to 2014-07-08, so it's the same as that no early than. There's still a huge pile of Changes in ASSIGNED state, please take a look to update the status/let me know in case of any issues you hit. I'll start pinging you individually this week :). Jaroslav At this point, all accepted changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be so enabled at Change Freeze. Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness. [2] As Fedora 21 scope is really huge, progress at Changes Freeze will help us to think about where we are and what we can do for this release. This applies not only to change owners but to all other groups - especially from WGs and teams involved in Fedora re-design. Let us know if you're blocked, if you need any help etc. or just to say, hey, we're ready :). Jaroslav [1] https://fedoraproject.org/wiki/Releases/21/Schedule [2] http://bit.ly/f21changesfreeze -- 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: free seats in Env and Stacks WG - volunteers wanted
On Út 1. červenec 2014, 11:31:35 CEST, Marcela Maslanova wrote: Env and Stacks Working Group has noble plan to make development in Fedora easier and also work with new technologies, which are not in Fedora yet. The whole statement can be found here: https://fedoraproject.org/wiki/Env_and_Stacks/Product_Requirements_Document There is missing Atomic and/or Docker, because all members were mostly interested in things mentioned in the document than looking at containers. I believe we need someone who can pick what will be in Fedora base image. Details can be found in Matt statement: https://lists.fedoraproject.org/pipermail/env-and-stacks/2014-June/000431.html We don't have manpower to work on all projects, but we started to work or co-operate on these: 1/ testing additional repositories – Playground repo https://fedoraproject.org/wiki/Changes/Playground_repository Playground plugin is similar to Copr plugin http://dnf.baseurl.org/2014/03/19/copr-plugin/ 2/ automation – Automated packages review tools https://fedoraproject.org/wiki/Env_and_Stacks/Changes_Drafts/Automated_packages_review_tools 3/ automation – Taskotron tool for Fedora tests https://fedoraproject.org/wiki/User:Tflink/taskotron_development_plan 4/ Build Systems – Copr http://copr.fedoraproject.org/ 5/ Software Collections in Fedora https://fedoraproject.org/wiki/Changes/SCL 6/ DevAssistant http://devassistant.org/ 7/ Continuous Integration - prototype of few projects If you are interested in current topics or containers, then please let us know on env-and-sta...@lists.fedoraproject.org what you want to do and what you did until now. I received some private replies, but I'd like to give opportunity to wider audience. Thanks, Marcela ___ env-and-stacks mailing list env-and-sta...@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/env-and-stacks Hi, I would like to sign up for one of these seats. I am already working with Docker and Docker images - I define and maintain RHEL Docker base images, thus I think I could help with these tasks in Fedora as well. When base images are ready, I'd like to concentrate on building layered images in Copr, which, in my opinion, would help Fedora QA with automation of image testing. Regards, Vaclav Pavlin -- Lead Infrastructure Engineer Developer Experience 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: Heads-up on rpm 4.12 coming to rawhide soon
Dne 1.7.2014 12:56, Panu Matilainen napsal(a):
On 06/30/2014 04:27 PM, Vít Ondruch wrote:
Dne 30.6.2014 15:14, Panu Matilainen napsal(a):
On 06/30/2014 03:48 PM, Panu Matilainen wrote:
On 06/30/2014 03:12 PM, Vít Ondruch wrote:
Interesting, it breaks Ruby build it seems:
http://koji.fedoraproject.org/koji/taskinfo?taskID=7090194
Not sure about the reason, though.
Seems the ruby macros are not expanding properly throughout the spec,
please file a bug.
I'd call this at least partially self-inflicted pain, its the %load
trickery thats failing. Call your own version of %load something else
and it'll work like before.
The syntax for the built-in macro is %{load:file} but the argument
is not macro expanded so %{SOURCEn} will get passed in literally.
Which obviously wont work.
- Panu -
Yes, that will do the trick probably.
However, now I am wondering, is there a way how to build SRPM, which is
using the new load feature from 4.12 using old 4.11 RPM? With old RPM,
I've got this error:
```
$ fedpkg srpm
error: line 94: Unknown tag:
/home/vondruch/fedora-scm/maintain/ruby/macros.ruby
error: query of specfile
/home/vondruch/fedora-scm/maintain/ruby/ruby.spec failed, can't parse
Could not execute srpm: need more than 0 values to unpack
```
I suppose the answer is NO, but I hope for some pleasant surprise ;)
For just creating an src.rpm, I suppose you can use a simple spec
conditional, eg
# permit src.rpm creation on older versions
%if %{fedora} = 21
%{load:...}
%endif
That is not very interesting, since I would need to maintain the
%{fedora} 21 branch anyway and the results on F20 and F21 could differ.
So I have different question, related to building SRPM. Is it possible
to detect, that this is just SRPM build task? The macros are not needed
to evaluate to build SRPM, so I could just ignore the %{load:...} by
some condition.
Anyway, like mentioned earlier, %{load:%{SOURCE4}} would not have
worked yesterday as %{load:} didn't macro-expand its argument, that
has been fixed in rpm-4.11.90-0.git12844.3.fc21 (just building now).
So thanks for trying to use that feature :)
Thank you for implementing it :)
Vít
--
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: Review swaps
Hi Sandro, On Wednesday, 25 June 2014 at 15:50, Sandro Mani wrote: On 25.06.2014 15:33, Dominik 'Rathann' Mierzejewski wrote: Would anyone like to swap reviews? https://bugzilla.redhat.com/show_bug.cgi?id=1112864 elpa - High-performance library for parallel solution of eigenvalue problems This is an optional dependency of cp2k-2.5+ (and comes bundled in cp2k-2.4). https://bugzilla.redhat.com/show_bug.cgi?id=1082825 mozilla-lightbeam - An add-on for visualizing HTTP requests between websites in real time In other words, see who's tracking you online. I'll take it. I've got engrid [1] up for review. [1] https://bugzilla.redhat.com/show_bug.cgi?id=294 Thanks to you (and David) for elpa review. I'll review engrid soon. Regards, Dominik -- Fedora http://fedoraproject.org/wiki/User:Rathann RPMFusion http://rpmfusion.org | MPlayer http://mplayerhq.hu Faith manages. -- Delenn to Lennier in Babylon 5:Confessions and Lamentations -- 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: fedora-release-$PRODUCT, /etc/issue, /etc/os-release, Per-Product Configs and more!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/01/2014 04:26 AM, Vít Ondruch wrote: Dne 30.6.2014 20:59, Stephen Gallagher napsal(a): 2) The fedora-release-$PRODUCT package (and possibly %post or systemd snippets therein) will be responsible for the creation and maintenance of /etc/issue, /etc/os-release and /etc/fedora-release-product (note: there is no $ there. That's the literal name. This file will be equivalent to /etc/fedora-release except that it will include the Product name. Could you please clarify, if you are going to preserve /etc/fedora-release on not? It is unclear to me from your wording ... Yes, sorry. We will preserve /etc/fedora-release, these files will be supplementary, not a replacement. -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOyq58ACgkQeiVVYja6o6Pv8gCglKUrgDPu/PfqdVu5aqz5UNG2 IU0AnjYGe1hMpMegm4eJfYYqAmL1DYO9 =VL2o -END 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: fedora-release-$PRODUCT, /etc/issue, /etc/os-release, Per-Product Configs and more!
Dne 1.7.2014 14:37, Stephen Gallagher napsal(a): -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/01/2014 04:26 AM, Vít Ondruch wrote: Dne 30.6.2014 20:59, Stephen Gallagher napsal(a): 2) The fedora-release-$PRODUCT package (and possibly %post or systemd snippets therein) will be responsible for the creation and maintenance of /etc/issue, /etc/os-release and /etc/fedora-release-product (note: there is no $ there. That's the literal name. This file will be equivalent to /etc/fedora-release except that it will include the Product name. Could you please clarify, if you are going to preserve /etc/fedora-release on not? It is unclear to me from your wording ... Yes, sorry. We will preserve /etc/fedora-release, these files will be supplementary, not a replacement. Great, thanks for clarification. Vít -- 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: Non-responsive maintainer: Hubert Plociniczak (fas: hubert)
2014-06-24 13:50 GMT+04:00 Peter Lemenkov lemen...@gmail.com: Hello All! As fas as we know Hubert quit Fedora for a very long time (said in his private email). So it's time to change a poit of contact for the only package Hubert maintained - RabbitMQ server. https://admin.fedoraproject.org/pkgdb/package/rabbitmq-server/ I propose myself (FAS name: peter) and John Eckersberg (FAS name: jeckersb) as a primary maintainers. If anyone has any objections and/or suggestions, please, let us know. Ping? -- 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
Koschei - continuous rebuilds for packages
Hello, Recently I've been working on Koschei - a new continuous rebuilding tool for Fedora and I'd like to announce it publicly and get some feedback. How will it work? It will have a set of tracked packages for which it will watch dependency updates and will (scratch) rebuild packages in Koji after the dependencies change (are updated, downgraded...). It will use Hawkey library to resolve packages' dependencies in order to match resolution happening during the Koji build as closely as possible. That would also enable marking packages with unresolved build dependencies as unbuildable without needing actual rebuild in Koji. The packages will be scheduled for rebuild based on their current priority value, which will be increased with each depenendency update by a value inversely proportional to the distance between the package and the dependency in the dependency chain. The priority will also slowly increase over time and will be reset back when a new rebuild is scheduled. What will be the benefits? Currently, with each release of Fedora there are lot of packages that fail to build from source because their dependencies were updated to an incompatible version. The breakage is usually detected during the mass rebuild and fixing of the FTBFS bugs is a tedious process, because it's hard to determine the exact cause of the failure. Koschei could narrow down the set of packages that may be the cause to just one or two which could reduce the time spent on fixing such bugs. What about Koji load? It will be limiting the number of rebuilds in order to not overload Koji builders - by limiting maximum number of running builds and monitoring Koji current load. Maybe it would also be possible to get a separate Koji channel. We'll try our best to keep the overall Koji performance unaffected. Any suggestions regarding this part are welcome. What's the current status? The core part is already implemented - dependency resolution, fedmsg listening, update detection, build submitting, collecting the results, parsing buildroot differences from mock root logs. The source repository is available at [2] What packages will be there? Currently, the packages are added manually by me. Lately it will depend on the demand and how much it will be affecting Koji. Ideally, any Fedora user could add packages himself in the web interface. What is it's output? Currently there's a simple reporter generating static html report of all builds of all packages (example at [1]). The current format is of course not very practical because the number of packges and builds will both increase a lot, so I'd like to implement a dynamic web interface that will provide a way to categorize packages into user defined groups and display overview of packages in given group. In the overview only last Koschei build and last successful build if the current one fails will be displayed. Then there will be detailed per-package view showing all package's recent scratch builds, statistics, buildroot differences, likely failure reason etc. What is the plan for it? Get feedback from people. Try to get it deployed in Fedora infrastructure and see the how does it perform. If it turns out that Koji performance is lowered we'll stop it and reconsider how to avoid such a condition. Michael Simacek [1] http://msimacek.fedorapeople.org/koschei/ [2] https://github.com/msimacek/koschei -- 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: delta rpms - can we turn them off
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 27 Jun 2014 11:35:20 -0600 Kevin Fenzi ke...@scrye.com wrote: On Fri, 27 Jun 2014 19:23:04 +0200 drago01 drag...@gmail.com wrote: Why? My understanding of the process as it exists: Download drpm. Take drpm contents + old package files installed locally that were not changed and create updated rpm. yum/dnf hands off this updated new version to rpm as normal. If they didn't create the orig rpm, it would require rpm to handle drpms differently and apply them somehow on existing files and update rpmdb. If the drpms were signed, only those parts of the package that changed in that drpm could be verified, the rest of the ones from the filesystem would just be whatever was on the filesystem. additionally the drpms are created at repo creation time and are never available to the signing process. we would have to redo and rethink how we make deltarpms. which would open up a massive can of worms that would likely result in much wasted effort. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJTss+aAAoJEH7ltONmPFDRW4wP/RmPoKSW46VImnYuDdI+KPaO PQp/Mg9InbsuRr6Re+o2pk+fOlxZoDY0P8G9xuzuoi9j8CMh+nIENx7/GEQa3wh/ D8YpQRLZtNFnNRFB6aJm9hgWrjTtBG5YB+xc+ROXo65s/vqhYKbjCoxgl+u4ZL/l jwW7Z0pgtoAzxPrceLIjn5MrwTGin7oVcsHMnghP8+/svM2al9x1M6Jx1kzO0NGy h3L1ClkUXCM2lVsuib79fETMAICF40EGZQPZ5/RErJ5FYmu3ldif7crt/qydtA9u 8XaN6xIdc2EW7L2aqy2MYuKzxwwfpHcXg/W6WCjS2/Zd+UJMVpg8ZHIv4wOR+Eww LXfz2RHThn0siLti2WenH6pm+UagipvSGJesoVu/igdgoa9UCOtH/w+MePO1OoIv QcvtCzQ9zmDdzJoA/bsbwo9QIThtlCXCU7AT6JAbOVwZlkXvatjpUCjjmo5gWyuD XNMEIvvEkna975+TU8Y4atkkSRxIt3tOFdkzbV4nrS0OPclP9TSpsUt4zsJecosl +mT2ca2JihJfJkJXe0e1k+QZPaAon+VYHMGq6n/+T8zwjH2277ct3pn9jE2iUT62 WvubEOw6Q8jrEiBBEgfgG6uyucW49Q0jqSnyrOosikrfvwH4Inp3viO0zj7bB+yA bpktGNj51E6Qk8HkWzkX =QpUV -END 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: Cc: on dead packages
On 06/30/2014 07:20 PM, Bill Nottingham wrote: Bastien Nocera (bnoc...@redhat.com) said: Apparently, people can still file bugs for dead packages: https://bugzilla.redhat.com/show_bug.cgi?id=1114180 And I (and many others) get CC:ed on those bugs files, with no possibility to remove ourselves from the CC: in pkgdb. Any idea where I should be filing a bug for this bug? It's a combination of: snip - you can't disable filing against components I don't think that's true, a bugzilla component can be disabled for filing new bug reports, but it is not fully removed, so old bugs can still be referenced with the correct component. I previously filed a request against pkgdb2 asking them to handle this step for retired components: https://github.com/fedora-infra/pkgdb2/issues/59 - Cole -- 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: delta rpms - can we turn them off
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 29 Jun 2014 20:01:04 -0500 Jon jdisn...@gmail.com wrote: On Sun, Jun 29, 2014 at 7:42 PM, Stephen John Smoogen smo...@gmail.com wrote: [snip] Personally I would just say don't make delta-rpms for i386 and arm or just have deltarpm=1 on those architectures by default. Or all architectures even. This should, in my opinion, be disabled by default. The default-off setting should be self-documented in the config, so that it could be easily found and toggled on/off. While I generally disable deltarpm locally, you need to look at teh whole picture. There are many parts of the world that generally have caps on downloads. Australia is an example of such a country, using deltarpms there can save you a ton of bandwidth that goes against your download cap. now some ISP's run mirrors and if you hit their mirror it doesnt count against your cap. but thats not always a given. The sane default is what we have today. This should please the masochists, or people with very slow internet. Meanwhile, we can bikeshed on how to optimise the feature. Eventually somebody will make the changes that cause DRPMs to suck slightly less. At that future time we can reevaluate if we rewards are worth the aggravations. in the initial use case laid out that started this thread the user should be using ansible or puppet or something for config management. and then it is a trivial thing to disable deltarpm. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJTstElAAoJEH7ltONmPFDRWlAP/1fzM9cjzrQqS7Bazpe5LWD3 hy+LNbLEjACuUHVtAvxfCqHE14FzuSG9Th7KVsRfQeCIQpztOkLN4pHoWytTPv3V aj8pjnaRK719kV89g2CYQtP9ZIRmHEVJqrw+DOXgyu17H1D9+7RZdw6qULwQheT9 +uWy72qLGGZw7+l2IzPKFGoGyoPQkw1esPC9IDoZyhm1LckBwBYTs+9NMHpmiwl9 iVf/pRENOXG7uLaiGZI7B/Vll3FVbLBAcjLze1tPjyZSvRsdJq8shQXBIgeitlEm dKsfNg+9iOANRBIQJaM/dCODFRJPr0uMZlB8SoxJy+LOtQYyOrVCEKt0u2LEpAwF XPDMt8wOQTiUIyWXteGDbPbsFqpc44cvrhgko4mVVfZDjFzadr+WS3ZWasNlqSZW 9vuvNaqMGZTRitoFXZGSV4tvPrK2FZ/uEgEW8PbwEBACJk5fkBnJW4dAxei7AsvC YSRkiJztz3zzcGeXRQtq1GHQPaWAEEkPeGerjnJEFyXq3ZQaRV+L6ej0CS0wPnJh Ni1d2zL0iXdiAlN0BrIEttoKsECc9FEShHWsYkeKdmHjCMGom1E0gqFjVR2wqQkX WLH7dPcBT95/OOZnmMg2Ii9PrBwp7YXxtNM1wYB59QVSZLnfYO0cMwfmj7cSmT3G ky69yJoWC5CbZGpEf+qi =ZH83 -END 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
Summer 2014 FESCo Special Election
We have three open seats on FESCo, the Fedora Engineering Steering Committee. The policy for filling open seats states that we first check with the runners-up from the previous election; as they have declined, the policy is for FESCo to select replacements. We've decided that an open election is the best way to do that selection. Details on the election are available at http://fedoraproject.org/wiki/Elections and the schedule will be as follows: July 2 - 7: Nomination Period (closes promptly at 23:59:59 UTC on July 7) July 2 - 7: Questionnaire form open for the community to submit questions for the candidates. July 7 - 10: Candidates Questionnaire. Results will be posted to the wiki prior to the townhall July 10 - 15: Townhall July 15 - 22: Voting Period (closes promptly at 23:59:59 UTC on July 22) July 23: Announce Results Note that these elections will fill the seats for the remainder of the term, with the first two winners serving until next spring and the third until after the F21 release this fall. If you are interested in helping Fedora in this way, please add yourself to the list of nominees at http://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations. As a FESCo member, you will be part of the Fedora's technical leadership team. See https://fedoraproject.org/wiki/Fedora_Engineering_Steering_Committee for details of responsibilities. FESCo has a weekly IRC meeting to decide on open issues; you should plan to attend that regularly, and to spend some time understanding those issues before the meeting so that we can proceed efficiently. Even if you are not interested in running, you can help with the electoral process by adding some questions to the Questionnaire for this election: http://fedoraproject.org/wiki/Elections/Questionnaire Thanks to Jaroslav Reznik for coordinating this election! -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- 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: Koschei - continuous rebuilds for packages
Hi Michael, it sounds like a way how one could automatically handle library so-bumps in rawhide. Idea discussed with hhorak, jzeleny, pingou and others was to bump the library package, rebuild the dependency tree depending on this library and if some of them fail, notify it's maintainer(s) and the bumped library owner as well (email CC should be sufficient). If it doesn't fail, we can automatically immediately rebuild it in non-scratch environment. This'll save so much time and effort and also suppress the need for finding maintainers of the library and notifying them about the so-bump. So the question regarding Koschei is if one could schedule one-shot build of a library package (preferably from CLI) and if one could get the result of such run on CLI (allowing automation). The CLI tool would be just thin wrapper around remote interface (JSONRPC/XMLRPC/...). Do Koschei have such interface? Kind regards, -- Jan Pacner -- 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: [ACTION REQUIRED] Retiring packages for Fedora 21 v3
On Fri, Jun 27, 2014 at 06:28:58PM -0500, Yaakov Selkowitz wrote: alliance chitlesh, tnorth https://bugzilla.redhat.com/show_bug.cgi?id=1105945 I applied your patch but then noticed that the version is also three years behind upstream, therefore I am not convinced it is a good idea to keep the package in Fedora without a proper maintainer. Does anyone want to maintain it? Regards Till -- 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: [ACTION REQUIRED] Retiring packages for Fedora 21 v3
On Wed, Jul 2, 2014 at 12:24 AM, Till Maas opensou...@till.name wrote: On Fri, Jun 27, 2014 at 06:28:58PM -0500, Yaakov Selkowitz wrote: alliance chitlesh, tnorth https://bugzilla.redhat.com/show_bug.cgi?id=1105945 I applied your patch but then noticed that the version is also three years behind upstream, therefore I am not convinced it is a good idea to keep the package in Fedora without a proper maintainer. Does anyone want to maintain it? Hand it over to me. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
kde-4.13.x update for f20
KDE SIG has been discussing moving forward with another kde x.y+1 update for Fedora 20, largely due to it's extended lifetime (and f21's delayed release), extending the same rationale per http://fedoraproject.org/wiki/SIGs/KDE/Update_policy There have been kde-4.13.1 packages available for testing and feedback in a 3rd-party kde-unstable repo (see http://fedoraproject.org/wiki/SIGs/KDE/Testing ) for quite some time. We're currently tracking all kde-4.13 blocker-worthy issues in bugzilla, https://bugzilla.redhat.com/show_bug.cgi?id=kde-4.13 The most significant change involved will be moving to a new desktop search architecture, called baloo, which addresses a long-time pain-point and has been generally well-received. Any comments or concerns? -- Rex -- 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: Koschei - continuous rebuilds for packages
On Tue, 2014-07-01 at 10:13 -0400, Michael Simacek wrote: Hello, Recently I've been working on Koschei - a new continuous rebuilding tool for Fedora and I'd like to announce it publicly and get some feedback. How will it work? It will have a set of tracked packages for which it will watch dependency updates and will (scratch) rebuild packages in Koji after the dependencies change (are updated, downgraded...). [snip] Sounds a lot like what openSUSE's Open Build Service does. I think they automatically trigger rebuilds of dependees when a provide they depend on goes away due to a rebuild, so SONAME bumps are a breeze. I'm wondering why is the functionality built into a separate service instead of Koji, the build system itself? Regards, Lubo -- 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: kde-4.13.x update for f20
On Tue, Jul 1, 2014 at 12:17 PM, Rex Dieter rdie...@math.unl.edu wrote: KDE SIG has been discussing moving forward with another kde x.y+1 update for Fedora 20, largely due to it's extended lifetime (and f21's delayed release), extending the same rationale per http://fedoraproject.org/wiki/SIGs/KDE/Update_policy There have been kde-4.13.1 packages available for testing and feedback in a 3rd-party kde-unstable repo (see http://fedoraproject.org/wiki/SIGs/KDE/Testing ) for quite some time. We're currently tracking all kde-4.13 blocker-worthy issues in bugzilla, https://bugzilla.redhat.com/show_bug.cgi?id=kde-4.13 The most significant change involved will be moving to a new desktop search architecture, called baloo, which addresses a long-time pain-point and has been generally well-received. Any comments or concerns? For what it's worth: +1 -AdamM -- Rex -- 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: [ACTION REQUIRED] Retiring packages for Fedora 21 v3
On Wed, Jul 02, 2014 at 12:47:57AM +0800, Christopher Meng wrote: On Wed, Jul 2, 2014 at 12:24 AM, Till Maas opensou...@till.name wrote: On Fri, Jun 27, 2014 at 06:28:58PM -0500, Yaakov Selkowitz wrote: alliance chitlesh, tnorth https://bugzilla.redhat.com/show_bug.cgi?id=1105945 I applied your patch but then noticed that the version is also three years behind upstream, therefore I am not convinced it is a good idea to keep the package in Fedora without a proper maintainer. Does anyone want to maintain it? Hand it over to me. done Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[ACTION REQUIRED][FINAL NOTICE] Retiring packages for Fedora 21 v4
The following packages are orphaned or did not build for two releases and will be retired when Fedora (F21) is branched, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life According to https://fedoraproject.org/wiki/Schedule branching will occur on 2014-07-08. The packages will be retired starting 2014-07-04. If you intend to claim a package, please take it now. Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Package(co)maintainers === SOAPpy orphan, pingou SteGUI orphan, pingou aeolus-configure orphan, clalance, jeckersb, mmorsi, slinabery aleorphan, silfreed alliance chitlesh, tnorth bitbakeixs blktap ke4qqq clutter-gtkmm orphan, rhl cx18-firmware orphan, athimm drwright caillon eclipse-cmakeedorphan, swagiaal emacs-common-muse orphan emacs-identica-modeorphan, shakthimaan eqntottorphan, chitlesh espresso-aborphan, chitlesh fprint_demoorphan, pingou freetalk orphan, rishi fuse-smb szpak g-wrap laxathom gdome2 orphan, sundaram gnome-shell-theme-elementary orphan, eldermarco gnomeradio orphan, itamarjp, roma guile-lib laxathom ha-jdbcorphan hdrpreporphan, silfreed jbrout orphan jchartsorphan jdbm orphan jgroups212 orphan, arg kannel thias, cicku, linuxthomass libghemicalorphan minbar izhar, hicham mopac7 orphan mozilla-firetray hicham mule orphan, tspauld98 nagios-plugins-check_sip orphan netatalk orphan, fkocina netty31orphan nomnom orphan nvclockorphan obexfs orphan, itamarjp openstack-savanna orphan, matt perl-NOCpulse-SetIDorphan perl-NOCpulse-Utilsorphan, perl-sig piccolo2d orphan, akurtakov pidgin-rhythmbox orphan, nosnilmot pp3mmahut proxyknife rishi python-django-savanna orphan, matt python-savannaclient orphan, jruzicka, matt python-setuptools_trialorphan python-webdav-library orphan raidutils orphan, itamarjp rats smilner, rmonk
Attempting to contact unresponsive maintainer
Greetings, we've been told that the email addresses for this package maintainer is no longer valid. I'm starting the unresponsive maintainer policy to find out if they are still interested in maintaining their packages (and if so, have them update their email addresses in FAS). If they're not interested in maintaining or we can't locate them I'll have FESCo orphan the packages so that others can take them over. If you have a way to contact this maintainer, please let them know that we'd appreciate knowing what to do with their packages. Thanks! * gospo - former email address agosp...@redhat.com https://admin.fedoraproject.org/pkgdb/packager/gospo/ Point of contact: wiggle -- A tool for applying patches with conflicts ( master f20 f19 el6 el5 ) If we don't hear anything in a week, we will be removing their acls and will need to find new point of contacts, etc. Thanks, kevin signature.asc 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: Non-responsive maintainer: Hubert Plociniczak (fas: hubert)
On Tue, 1 Jul 2014 16:55:23 +0400 Peter Lemenkov lemen...@gmail.com wrote: 2014-06-24 13:50 GMT+04:00 Peter Lemenkov lemen...@gmail.com: Hello All! As fas as we know Hubert quit Fedora for a very long time (said in his private email). So it's time to change a poit of contact for the only package Hubert maintained - RabbitMQ server. https://admin.fedoraproject.org/pkgdb/package/rabbitmq-server/ I propose myself (FAS name: peter) and John Eckersberg (FAS name: jeckersb) as a primary maintainers. If anyone has any objections and/or suggestions, please, let us know. Ping? Sorry for the delay. I've assigned you as point of contact for the package. kevin signature.asc 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: Non-responsive maintainer: Hubert Plociniczak (fas: hubert)
2014-07-01 21:58 GMT+04:00 Kevin Fenzi ke...@scrye.com: On Tue, 1 Jul 2014 16:55:23 +0400 Peter Lemenkov lemen...@gmail.com wrote: 2014-06-24 13:50 GMT+04:00 Peter Lemenkov lemen...@gmail.com: Hello All! As fas as we know Hubert quit Fedora for a very long time (said in his private email). So it's time to change a poit of contact for the only package Hubert maintained - RabbitMQ server. https://admin.fedoraproject.org/pkgdb/package/rabbitmq-server/ I propose myself (FAS name: peter) and John Eckersberg (FAS name: jeckersb) as a primary maintainers. If anyone has any objections and/or suggestions, please, let us know. Ping? Sorry for the delay. I've assigned you as point of contact for the package. Thanks! -- 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
Re: Koschei - continuous rebuilds for packages
On Tue, 2014-07-01 at 19:19 +0200, Lubomir Rintel wrote: Sounds a lot like what openSUSE's Open Build Service does. I think they automatically trigger rebuilds of dependees when a provide they depend on goes away due to a rebuild, so SONAME bumps are a breeze. Yes, soname bumps are nonevents with OBS, since everything is automatically rebuilt. Sounds like Koschei is a big step towards that. signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Review swaps
The python-ZODB3 package, which I maintain, has been split into pieces. I need several package reviews to get all the new pieces into place. I am happy to swap reviews for these, but the number of reviews I need is sufficiently large that it will take me a little time to get to all of the reviews I am asked to do. If you can have a little patience with me, then this is what I need: 1. python-repoze-sphinx-autointerface https://bugzilla.redhat.com/show_bug.cgi?id=1102858 Already under review, but the review may have stalled. 2. python-persistent https://bugzilla.redhat.com/show_bug.cgi?id=1102950. Depends on #1. Ditto the comment for #1. 3. python-BTrees https://bugzilla.redhat.com/show_bug.cgi?id=1104291 Depends on #1 and #2.. 4. python-random2 https://bugzilla.redhat.com/show_bug.cgi?id=1104322 5. python-zodbpickle https://bugzilla.redhat.com/show_bug.cgi?id=1107321 6. python-ZODB https://bugzilla.redhat.com/show_bug.cgi?id=1108781 Depends on #1 through #5. 7. python-ZEO https://bugzilla.redhat.com/show_bug.cgi?id=1108813 Depends on #1 through #6. Also, a new version of python-networkx is out, with a new build dependency: 8. python-sphinx-rtd-theme https://bugzilla.redhat.com/show_bug.cgi?id=1115185 Thank you. Let me know what I can review for you in exchange. -- Jerry James http://www.jamezone.org/ -- 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: Koschei - continuous rebuilds for packages
On Tue, Jul 1, 2014, at 12:53 PM, Michael Catanzaro wrote: Yes, soname bumps are nonevents with OBS, since everything is automatically rebuilt. Sounds like Koschei is a big step towards that. I've always found it really strange how so many people talk about rebuilding for soname bumps. The *entire point* of a soname bump is to communicate that the API/ABI has *changed*, and thus it may require active human intervention to update callers for the change. In other words, actual source code has to be edited and not just package metadata and a build requeue. If the callers work after a rebuild, it calls into question whether the soname should have been bumped at all (see libffi and udev cases). It's of course good to try rebuilds to see if they work or not; but what'd be better is a system that would allow coordinated updates of groups of packages from a branch, with modified source code. In practice at least for the ABI-unstable libraries in GNOME like libgnome-desktop, all callers are ported during the development cycle, and rebuilds will happen manually via mclazy. The more challenging case is components which are part of multiple ecosystems and not coordinated on a schedule, like libpng. Of course, shielding callers from its ABI changes is major rationale for the existence of gdk-pixbuf. Anyways I'd say port for soname bumps instead of rebuild. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Retiring fuse-smb package
Hi, I plan to retire fuse-smb which allows to mount SMB/Samba shares as local directories before F21 is branched (2014-07-08). There have been no new versions since 2008 and the maintainer is not going to fix problem with crashes related to multi threading issues in libsmbclient 3.2+. There had been also building issues with Samba 4.0. Ubunty recommends [1] smbnetfs project [2] as a replacement, but I don't use this feature anymore and even I have access to Windows machines to test this use case, so I would not be able to test it carefully with all further Fedora updates. Maybe there would be someone else willing to package smbnetfs? [1] - https://help.ubuntu.com/community/FuseSmb [2] - https://sourceforge.net/projects/smbnetfs/ Marcin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Realted to Fedora Release Engineering is this OK?!!
Hi every one ,
This commit add number after %{?dist} .. is this OK !!
http://pkgs.fedoraproject.org/cgit/gnulib.git/commit/?id=c2f0d77aba7a2b745886654c42c943f6a9c1a4b7
See full package name
http://fr2.rpmfind.net//linux/RPM/fedora/devel/rawhide/src/g/gnulib-0-8.20140504git.fc21.1.src.html
Regards
Mosaab
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
5tFTW: Winning, FESCo election, Workstation To-Dos, Bugspad, and CentOS EPEL (2014-07-01)
Reposted from http://fedoramagazine.org/5tftw-2014-07-01/. Fedora is a big project, and it’s hard to follow it all. This series highlights interesting happenings in five different areas every week. It isn’t comprehensive news coverage — just quick summaries with links to each. Here are the five things for July 1st, 2014: What Does “Winning” Mean for Fedora? The Fedora Project Board is exploring the question “What is success for Fedora?”, brought to the board-discuss mailing list by Board member Josh Boyer. This is a public mailing list for all Fedora community members, and we welcome your thoughtful contributions to the discussion. * http://fedoraproject.org/wiki/Board * https://lists.fedoraproject.org/pipermail/board-discuss/2014-July/012613.html * https://admin.fedoraproject.org/mailman/listinfo/board-discuss FESCo Summer Election - We are holding an election for three open seats on FESCo, the Fedora Engineering Steering Committee. More information on Fedora Magazine, in an announcement I sent this morning, and of course directly on the Fedora Project wiki. * http://fedoramagazine.org/election-announced-for-the-fedora-engineering-steering-commitee/ * https://lists.fedoraproject.org/pipermail/devel-announce/2014-July/001413.html * http://fedoraproject.org/wiki/Elections Workstation To-Do List -- Fedora Workstation Working Group member Christian Schaller recently posted a message about the group’s new Tasklist wiki page, which details current and future tasks for the subproject, and explains how you can get involved (or simply better follow what’s currently going on). * https://lists.fedoraproject.org/pipermail/desktop/2014-June/009929.html * http://fedoraproject.org/wiki/Workstation/Tasklist Google Summer of Code Project: Bugspad -- Last week, I highlighted Google Summer of Code work in Fedora on the Waartaa chat system. This week, take a look at Fedora contributor Mayank Jha’s work on Bugspad, a new bug tracker focused on speed and aimed at replacing Bugzilla. In last Thursday’s Fedora Infrastructure meeting, Mayank notes that at test instance will be deployed on our internal private cloud and that he’s currently testing it with a million (auto-generated) bugs (the kind of load we need to handle in real-world Fedora). * http://fedoramagazine.org/5tftw-2014-06-24/ * https://www.google-melange.com/gsoc/homepage/google/gsoc2014 * https://www.waartaa.com/ * https://fedoraproject.org/wiki/User:Mjnovice * http://bugspad.org/ * http://meetbot.fedoraproject.org/fedora-meeting/2014-06-26/infrastructure.2014-06-26-18.00.log.html EPEL in CentOS 7 And finally, a quick note from our sibling project, CentOS. EPEL (“Extra Packages for Enterprise Linux”) is a long-standing Fedora subproject which targets Red Hat Enterprise Linux and CentOS, providing a wide universe of packages that aren’t provided by Red Hat. Many of these packages are very close to their Fedora equivalents, and it’s a common entry-point to Fedora for sysadmins and other folks who work in the enterprise world as their day job. CentOS developer Jim Perrin notes on the centos-devel mailing list that, as of the upcoming CentOS 7 release, the `epel-release` package will be included in the centos-extras repository (although not installed by default). That means to get Fedora-produced EPEL packages on CentOS, you’ll just have to `yum install epel-release` and then install whatever you like. * http://lists.centos.org/pipermail/centos-devel/2014-June/00.html -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Schedule for Wednesday's FESCo Meeting (2014-07-02)
Following is the list of topics that will be discussed in the FESCo meeting Wednesday at 17:00UTC in #fedora-meeting on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2014-07-02 17:00 UTC' Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9 = Followups = #topic #1178 Fedora 21 scheduling strategy .fesco 1178 https://fedorahosted.org/fesco/ticket/1178 #topic #1314 FESCo should grant product WGs the right to decide default services .fesco 1314 https://fedorahosted.org/fesco/ticket/1314 #topic #1310 Reconsidering rpcbind's exception allowing it to start by default .fesco 1310 https://fedorahosted.org/fesco/ticket/1310 #topic #1311 Disable syscall auditing by default .fesco 1311 https://fedorahosted.org/fesco/ticket/1311 = New business = #topic #1318 shared-mime-info arbitration .fesco 1318 https://fedorahosted.org/fesco/ticket/1318 #topic #1321 Can packages not approved for Fedora be placed in non-official branches of the Fedora pkgs repo? .fesco 1321 https://fedorahosted.org/fesco/ticket/1321 #topic 1320 Proposal: trivial patch policy .fesco 1320 https://fedorahosted.org/fesco/ticket/1320 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at https://fedorahosted.org/fesco/report/9 If you would like to add something to this agenda, you can reply to this e-mail, file a new ticket at https://fedorahosted.org/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. signature.asc 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: Realted to Fedora Release Engineering is this OK?!!
On Tue, Jul 1, 2014 at 5:02 PM, مصعب الزعبي moc...@hotmail.com wrote:
Hi every one ,
This commit add number after %{?dist} .. is this OK !!
http://pkgs.fedoraproject.org/cgit/gnulib.git/commit/?id=c2f0d77aba7a2b745886654c42c943f6a9c1a4b7
Yes, it's fine.
josh
--
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: Koschei - continuous rebuilds for packages
Colin Walters walt...@verbum.org writes: On Tue, Jul 1, 2014, at 12:53 PM, Michael Catanzaro wrote: Yes, soname bumps are nonevents with OBS, since everything is automatically rebuilt. Sounds like Koschei is a big step towards that. I've always found it really strange how so many people talk about rebuilding for soname bumps. The *entire point* of a soname bump is to communicate that the API/ABI has *changed*, and thus it may require active human intervention to update callers for the change. In other The soname bump reflects a change in ABI. The API could have stayed the same. (But of course, sometimes the ABI bump isn't warranted, and sometimes manual intervention is necessary.) Personally, I would welcome such service for Boost bumps. Most of the time, the rebuilds just pass. If I could get e-mails about the 10% or so of problematic packages for closer inspection, and the rest would just rebuild without me having to lift a finger, that would be great. Thanks, PM -- 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: Realted to Fedora Release Engineering is this OK?!!
Yes, it's fine.
If you want to avoid such bump you shouldn't use %tag, just fill in
the number. I couldn't see the reason of using this one-off macro.
Release: %{tag}.%{gitdate}git%{?dist}
to
Release: 8.%{gitdate}git%{?dist}
Yours sincerely,
Christopher Meng
Noob here.
http://cicku.me
--
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: Review swaps
Swap ZODB, sphinx-rtd-theme and BTrees with 1. osh - V6 Thompson Shell Port https://bugzilla.redhat.com/show_bug.cgi?id=1115121 2. zsh-lovers - A collection of tips, tricks and examples for the Z shell (This package is pretty easy as it only contains a manpage) https://bugzilla.redhat.com/show_bug.cgi?id=1115122 3. vinterm - Vintage-style terminal emulator https://bugzilla.redhat.com/show_bug.cgi?id=1098950 Thanks. Yours sincerely, Christopher Meng Noob here. http://cicku.me -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Fwd: [Bug 1114497] New: odb package missing gcc-plugin
The simple solution to this is for me to just rebuild against 4.8.3, but upstream said that in Debian they package the GCC plugins in /usr/lib/gcc/.../x.y/plugin instead of /usr/lib/gcc/.../x.y.z/plugin so that it doesn't break when there are minor version upgrades like this. Is doing something like that possible in Fedora as well? Or should I just rebuild when there's a minor version change? Thanks, Dave -- Forwarded message -- From: bugzi...@redhat.com Date: Mon, Jun 30, 2014 at 2:00 AM Subject: [Bug 1114497] New: odb package missing gcc-plugin To: davejohan...@gmail.com https://bugzilla.redhat.com/show_bug.cgi?id=1114497 Bug ID: 1114497 Summary: odb package missing gcc-plugin Product: Fedora Version: 20 Component: odb Assignee: davejohan...@gmail.com Reporter: steven.c...@gmail.com QA Contact: extras...@fedoraproject.org CC: davejohan...@gmail.com, lemen...@gmail.com Description of problem: Since the update to gcc to version 4.8.3, the gcc plugin that is packaged in odb remains in the 4.8.2 plugin directory and odb cannot be run because it is looking in the 4.8.3 plugin directory. Version-Release number of selected component (if applicable): odb 2.3.0-1 gcc 4.8.3-1 How reproducible: Run yum update This pulls in the latest gcc which breaks odb. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. -- 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 906396] Permission problems in amavis-new
https://bugzilla.redhat.com/show_bug.cgi?id=906396 lnie l...@redhat.com changed: What|Removed |Added CC||l...@redhat.com --- Comment #4 from lnie l...@redhat.com --- amavisd-new-2.9.0-2.fc20 works -- 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=c5HPJISxf9a=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 1114859] New: perl-CPAN-Meta-Check-0.009-1.fc21 fails to bootstrap
https://bugzilla.redhat.com/show_bug.cgi?id=1114859 Bug ID: 1114859 Summary: perl-CPAN-Meta-Check-0.009-1.fc21 fails to bootstrap Product: Fedora Version: rawhide Component: perl-CPAN-Meta-Check Assignee: p...@city-fan.org Reporter: ppi...@redhat.com QA Contact: extras...@fedoraproject.org CC: p...@city-fan.org, perl-devel@lists.fedoraproject.org perl-CPAN-Meta-Check-0.009-1.fc21 fails to bootstrap: + make test RELEASE_TESTING=1 PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -MTest::Harness -e undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/00-compile.t ok t/10-basics.t . ok Can't locate Test/Pod/Coverage.pm in @INC (you may need to install the Test::Pod::Coverage module) (@INC contains: /builddir/build/BUILD/CPAN-Meta-Check-0.009/blib/lib /builddir/build/BUILD/CPAN-Meta-Check-0.009/blib/arch /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at t/release-pod-coverage.t line 12. BEGIN failed--compilation aborted at t/release-pod-coverage.t line 12. t/release-pod-coverage.t .. Dubious, test returned 2 (wstat 512, 0x200) No subtests run Can't locate Test/Pod.pm in @INC (you may need to install the Test::Pod module) (@INC contains: /builddir/build/BUILD/CPAN-Meta-Check-0.009/blib/lib /builddir/build/BUILD/CPAN-Meta-Check-0.009/blib/arch /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at t/release-pod-syntax.t line 12. BEGIN failed--compilation aborted at t/release-pod-syntax.t line 12. t/release-pod-syntax.t Dubious, test returned 2 (wstat 512, 0x200) No subtests run That's because 0.009 started to use Test::Pod* without eval. I recommend to disable RELEASE_TESTING when bootstrapping. -- 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=jkHdIpxwj9a=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 1114859] perl-CPAN-Meta-Check-0.009-1.fc21 fails to bootstrap
https://bugzilla.redhat.com/show_bug.cgi?id=1114859 Paul Howarth p...@city-fan.org changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-CPAN-Meta-Check-0.009- ||2.fc21 Resolution|--- |RAWHIDE Last Closed||2014-07-01 04:52:48 --- Comment #1 from Paul Howarth p...@city-fan.org --- I believe it's safe to get rid of the perl_bootstrap conditional altogether actually, as perl-YAML-Tiny is no longer pulling in perl-CPAN-Meta-Check. I've done this for perl-CPAN-Meta-Check-0.009-2.fc21 Hopefully this won't cause a different dependency cycle! -- 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=91cf9xv8KMa=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 1115041] New: perl-DBD-CSV-0.43 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1115041 Bug ID: 1115041 Summary: perl-DBD-CSV-0.43 is available Product: Fedora Version: rawhide Component: perl-DBD-CSV Keywords: FutureFeature, Triaged Assignee: psab...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: mmasl...@redhat.com, perl-devel@lists.fedoraproject.org, psab...@redhat.com Latest upstream release: 0.43 Current version/release in Fedora Rawhide: 0.41-2.fc21 URL: http://search.cpan.org/dist/DBD-CSV/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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=QmSx8d0VQTa=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 1067003] Review Request: perl-Time-ParseDate - Date parsing both relative and absolute
https://bugzilla.redhat.com/show_bug.cgi?id=1067003 --- Comment #9 from Petr Pisar ppi...@redhat.com --- The standalone spec file and file from source RPM differ. I will use the standalone one for this review. The URL and Source0 are usable. Ok. The source archive is original (SHA-256: 14a761a45885cbff907531a0b293a7553100260ec0aa6cb51f4deef75616cdfe). Ok. Summary is Ok. Description is Ok. TODO: Wrap the description paragraph to 80 columns. License verified from lib/Time/ParseDate.pm, lib/Time/CTime.pm, lib/Time/DaysInMonth.pm, lib/Time/JulianDay.pm, lib/Time/Timezone.pm. FIX: The lib/Time/Timezone.pm is not TPDL-licensed. It is Public Domain: =head1 LICENSE David Muir Sharnoff disclaims any copyright and puts his contribution to this module in the public domain. Change the license tag from (TPDL) to (TPDL and Public Domain). No XS code presents, noarch BuildArch is Ok. Build-time dependencies are Ok. All tests pass. Ok. $ rpmlint perl-Time-ParseDate.spec ../SRPMS/perl-Time-ParseDate-2013.1113-2.fc21.src.rpm ../RPMS/noarch/perl-Time-ParseDate-2013.1113-2.fc21.noarch.rpm perl-Time-ParseDate.src: W: spelling-error %description -l en_US CTime - C Time, Crime, Clime perl-Time-ParseDate.src: W: spelling-error %description -l en_US DaysInMonth - Semimonthly perl-Time-ParseDate.src: W: spelling-error %description -l en_US JulianDay - Julian Day, Julian-Day, Julian-day perl-Time-ParseDate.src: E: description-line-too-long C There can be numerous options for controlling what is recognized and what is not. perl-Time-ParseDate.noarch: W: spelling-error %description -l en_US CTime - C Time, Crime, Clime perl-Time-ParseDate.noarch: W: spelling-error %description -l en_US DaysInMonth - Semimonthly perl-Time-ParseDate.noarch: W: spelling-error %description -l en_US JulianDay - Julian Day, Julian-Day, Julian-day perl-Time-ParseDate.noarch: E: description-line-too-long C There can be numerous options for controlling what is recognized and what is not. 2 packages and 1 specfiles checked; 2 errors, 6 warnings. rpmlint is Ok. $ rpm -q -lv -p ../RPMS/noarch/perl-Time-ParseDate-2013.1113-2.fc21.noarch.rpm drwxr-xr-x2 rootroot0 Jul 1 15:02 /usr/share/doc/perl-Time-ParseDate -rw-r--r--1 rootroot 7275 Nov 14 2013 /usr/share/doc/perl-Time-ParseDate/Changes -rw-r--r--1 rootroot 604 Nov 28 1998 /usr/share/doc/perl-Time-ParseDate/README -rw-r--r--1 rootroot 2805 Jul 1 15:02 /usr/share/man/man3/Time::CTime.3pm.gz -rw-r--r--1 rootroot 2181 Jul 1 15:02 /usr/share/man/man3/Time::DaysInMonth.3pm.gz -rw-r--r--1 rootroot 2901 Jul 1 15:02 /usr/share/man/man3/Time::JulianDay.3pm.gz -rw-r--r--1 rootroot 3674 Jul 1 15:02 /usr/share/man/man3/Time::ParseDate.3pm.gz -rw-r--r--1 rootroot 2321 Jul 1 15:02 /usr/share/man/man3/Time::Timezone.3pm.gz drwxr-xr-x2 rootroot0 Jul 1 15:02 /usr/share/perl5/vendor_perl/Time -rw-r--r--1 rootroot 5780 Sep 20 2013 /usr/share/perl5/vendor_perl/Time/CTime.pm -rw-r--r--1 rootroot 1330 Apr 1 2008 /usr/share/perl5/vendor_perl/Time/DaysInMonth.pm -rw-r--r--1 rootroot 5940 May 6 2011 /usr/share/perl5/vendor_perl/Time/JulianDay.pm -rw-r--r--1 rootroot29907 Nov 14 2013 /usr/share/perl5/vendor_perl/Time/ParseDate.pm -rw-r--r--1 rootroot 9604 Sep 20 2013 /usr/share/perl5/vendor_perl/Time/Timezone.pm File permissions and layout is Ok. $ rpm -q --requires -p ../RPMS/noarch/perl-Time-ParseDate-2013.1113-2.fc21.noarch.rpm | sort -f | uniq -c 1 perl = 0:5.000 1 perl = 0:5.002 1 perl(:MODULE_COMPAT_5.18.2) 1 perl(Carp) 1 perl(Exporter) 1 perl(integer) 1 perl(strict) 1 perl(Time::CTime) 1 perl(Time::JulianDay) 1 perl(Time::Timezone) 1 perl(vars) 1 rpmlib(CompressedFileNames) = 3.0.4-1 1 rpmlib(FileDigests) = 4.6.0-1 1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 1 rpmlib(PayloadIsXz) = 5.2-1 Binary requires are Ok. $ rpm -q --provides -p ../RPMS/noarch/perl-Time-ParseDate-2013.1113-2.fc21.noarch.rpm | sort -f | uniq -c 1 perl(Time::CTime) = 2011.0505 1 perl(Time::DaysInMonth) = 99.1117 1 perl(Time::JulianDay) = 2011.0505 1 perl(Time::ParseDate) = 2013.1113 1 perl(Time::Timezone) = 2006.0814 1 perl-Time-modules = 2013.1113-2.fc21 1 perl-Time-ParseDate = 2013.1113-2.fc21 Binary provides are Ok. This package replaces perl-Time-modules correctly. Ok. Package builds in F21 (http://koji.fedoraproject.org/koji/taskinfo?taskID=7096282). Ok. Otherwise the package is in line with Fedora and Perl packaging guidelines. Please correct all `FIX' issues, consider fixing `TODO' items, and
[Bug 1115055] New: perl-Pod-Usage-1.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1115055 Bug ID: 1115055 Summary: perl-Pod-Usage-1.64 is available Product: Fedora Version: rawhide Component: perl-Pod-Usage Keywords: FutureFeature, Triaged Assignee: ppi...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com Latest upstream release: 1.64 Current version/release in Fedora Rawhide: 1.63-5.fc21 URL: http://search.cpan.org/dist/Pod-Usage/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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=P4H1kjL3Goa=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 1115055] perl-Pod-Usage-1.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1115055 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-Pod-Usage-1.64-1.fc21 -- 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=9MqmZswn1Xa=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 1115055] perl-Pod-Usage-1.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1115055 --- Comment #1 from Fedora Update System upda...@fedoraproject.org --- perl-Pod-Usage-1.64-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/perl-Pod-Usage-1.64-1.fc20 -- 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=iLRTF2z73fa=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 1115041] perl-DBD-CSV-0.43 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1115041 Petr Šabata psab...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-DBD-CSV-0.43-1.fc21 Resolution|--- |RAWHIDE Last Closed||2014-07-01 10:31:05 -- 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=RXmFE8AqbPa=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 1088892] perl-Text-Xslate-3.2.4 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1088892 --- Comment #3 from Christopher Meng i...@cicku.me --- *** Bug 1084382 has been marked as a duplicate of this bug. *** -- 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=Glx0oWRM4Ma=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 1084382] perl-Text-Xslate-3.2.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1084382 Christopher Meng i...@cicku.me changed: What|Removed |Added Status|ASSIGNED|CLOSED Resolution|--- |DUPLICATE Last Closed||2014-07-01 11:42:28 --- Comment #1 from Christopher Meng i...@cicku.me --- *** This bug has been marked as a duplicate of bug 1088892 *** -- 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=gD8kWP16kna=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 1076569] perl-WebService-Linode-0.20 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1076569 Christopher Meng i...@cicku.me changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-WebService-Linode-0.20 ||-1.fc21 Resolution|--- |RAWHIDE Last Closed||2014-07-01 11:45:14 -- 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=cbgZ1iFzFIa=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 1076569] perl-WebService-Linode-0.20 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1076569 --- Comment #1 from Fedora Update System upda...@fedoraproject.org --- perl-WebService-Linode-0.20-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/perl-WebService-Linode-0.20-1.fc20 -- 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=w08a05AWiHa=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 1088892] perl-Text-Xslate-3.2.4 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1088892 Christopher Meng i...@cicku.me changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-Text-Xslate-3.2.4-1.fc ||21 Resolution|--- |RAWHIDE Last Closed||2014-07-01 11:57:59 -- 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=SkGskbOS3ha=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 1067003] Review Request: perl-Time-ParseDate - Date parsing both relative and absolute
https://bugzilla.redhat.com/show_bug.cgi?id=1067003 --- Comment #10 from Denis Fateyev de...@fateyev.com --- Fixed the long description and adjusted license tag. Updated version: http://www.fateyev.com/RPMS/Fedora20/testing/perl-Time-ParseDate.spec -- 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=aGtKGzDtFja=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 1029710] Amavisd fails to identify attached zipped files with .exe extensions
https://bugzilla.redhat.com/show_bug.cgi?id=1029710 Steve Tindall s10...@elrepo.org changed: What|Removed |Added Flags|needinfo?(s10...@elrepo.org | |) | --- Comment #4 from Steve Tindall s10...@elrepo.org --- The initial Description (see above) may cause some confusion as to what bug I am describing. Initially, I did not recognize the failure of amavisd to run 7za as a SELinux denial and then in Comment 1 described the avc denial issues causing the failure of 7za to list the contents of the zipped file. On a macro level, I define the bug as amavisd failing to quarantine a mail with a zipped exe attachment under SELinux Enforcing Policy. By failure to reproduce the bug, do you mean that you created a zipped exe file (as detailed above in Description), attached it to a mail, sent the mail and observed the mail being quarantined/rejected under Enforcing Policy? Also, the sender should get a rejection notice and a maillog entry containing ...Blocked BANNED (.asc,contains_zip.exe)... or similar text should be present. Yes, localamavisd is local SELinux policy described in Comment 1 that allows 7za to be called by amavisd. With localamavisd installed under Enforcing Policy, mail with a zipped exe attachment is quarantined, whereas with localamavisd removed, the mail is transmitted without being quarantined. Other info: # rpm -q amavisd-new p7zip selinux-policy selinux-policy-targeted amavisd-new-2.8.0-8.el6.noarch p7zip-9.20.1-2.el6.i686 selinux-policy-3.7.19-231.el6_5.3.noarch selinux-policy-targeted-3.7.19-231.el6_5.3.noarch # sestatus SELinux status: enabled SELinuxfs mount:/selinux Current mode: enforcing Mode from config file: enforcing Policy version: 24 Policy from config file:targeted -- 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=LPumoHKEuPa=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 1115055] perl-Pod-Usage-1.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1115055 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #2 from Fedora Update System upda...@fedoraproject.org --- Package perl-Pod-Usage-1.64-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-Pod-Usage-1.64-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-7968/perl-Pod-Usage-1.64-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=5bsz9Di7dZa=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
