EPEL Fedora 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 598 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5620/bugzilla-3.4.14-2.el6 113 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11274/ssmtp-2.61-21.el6 55 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11865/quassel-0.9.1-1.el6 28 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12079/bip-0.8.9-1.el6 13 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-1/drupal6-6.29-1.el6 10 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12238/seamonkey-2.21-2.esr1.el6 6 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12290/zabbix20-2.0.9-2.el6 6 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12301/zabbix-1.8.18-2.el6 3 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12324/munin-2.0.19-1.el6 3 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12321/munin-2.0.18-2.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing glite-lbjp-common-jp-interface-2.3.9-1.el6 glite-lbjp-common-maildir-2.3.9-1.el6 lynis-1.3.7-1.el6 perl-pmtools-1.54-2.el6 php-pecl-http-2.0.3-1.el6 php-pecl-raphf-1.0.4-1.el6 pyhoca-cli-0.4.0.1-2.el6 pyhoca-gui-0.4.0.8-1.el6 python-x2go-0.4.0.8-1.el6 python-xlib-0.15-0.9.rc1.el6 qt5-qtbase-5.2.0-0.12.rc1.el6 qt5-qtdeclarative-5.2.0-0.12.rc1.el6 qt5-qtdoc-5.2.0-0.10.rc1.el6 qt5-qtgraphicaleffects-5.2.0-0.10.rc1.el6 qt5-qtimageformats-5.2.0-0.10.rc1.el6 qt5-qtmultimedia-5.2.0-0.10.rc1.el6 qt5-qtquick1-5.2.0-0.10.rc1.el6 qt5-qtquickcontrols-5.2.0-0.10.rc1.el6 qt5-qtscript-5.2.0-0.10.rc1.el6 qt5-qtsvg-5.2.0-0.10.rc1.el6 qt5-qttools-5.2.0-0.10.rc1.el6 qt5-qttranslations-5.2.0-0.10.rc1.el6 qt5-qtwebkit-5.2.0-0.10.rc1.el6 qt5-qtxmlpatterns-5.2.0-0.10.rc1.el6 Details about builds: glite-lbjp-common-jp-interface-2.3.9-1.el6 (FEDORA-EPEL-2013-12356) Public API to JP service internal interface Update Information: Definition of interfaces required to build plugins for Job Provenance services and implementation of minimal library of support functions. References: [ 1 ] Bug #1039296 - Review Request: glite-lbjp-common-jp-interface - Public API to JP service internal interface https://bugzilla.redhat.com/show_bug.cgi?id=1039296 glite-lbjp-common-maildir-2.3.9-1.el6 (FEDORA-EPEL-2013-12354) Single-purpose implementation of maildir-like queue Update Information: Single-purpose implementation of maildir-like queue. It is used to pass data from gLite Bookkeeping server to Job Provenance. References: [ 1 ] Bug #1039293 - Review Request: glite-lbjp-common-maildir - Single-purpose implementation of maildir-like queue https://bugzilla.redhat.com/show_bug.cgi?id=1039293 lynis-1.3.7-1.el6 (FEDORA-EPEL-2013-12355) Security and system auditing tool Update Information: * 1.3.7 (2013-12-10) New: - Function FileExists() and SearchItem() Changes: - Adjusted yum-security check [PKGS-7386] - Improved check for iptables binary check - Extended report with the tests executed and skipped * 1.3.6 (2013-12-03) New: - Support for the dntpd time daemon - New Apache test for modules [HTTP-6632] - Apache test for mod_evasive [HTTP-6640] - Apache test for mod_qos [HTTP-6641] - Apache test for mod_spamhaus [HTTP-6642] - Apache test for ModSecurity [HTTP-6643] - Check for installed package audit tool [PKGS-7398] - Added initial support for new pkgng and related tools [PKGS-7381] - Check for ssh-keyscan binary - ZFS support for FreeBSD [FILE-6330] - Test for passwordless accounts [AUTH-9283] - Initial OS support for DragonFly BSD - Initial OS support for TrueOS (FreeBSD based) - Initial OS support for elementary OS (Luna) - GetHostID for DragonFly, FreeBSD, NetBSD and OpenBSD - Check for DHCP client [NETW-3030] - Initial support for OSSEC (system integrity) [FINT-4328] - New parameter --log-file to adjust log file location - New function IsRunning() to check status of processes - New function RealFilename() to determine file name - New function CheckItem() for
Re: [pkgdb2] call for testers, bug reports and RFE
On Tue, Dec 10, 2013 at 09:52:58PM +0100, Matthias Runge wrote: On 12/10/2013 02:20 PM, Pierre-Yves Chibon wrote: So please, have a look at it, play with it, break it (no seriously, do, but don't forget to report how you did it afterward) and if you have any problem/RFE feel free to note them at: Just a heads-up, christmas holidays are coming our way and our agenda is to push pkgdb2 in production as soon as possible after the release of F20. This means that if you want to poke at it, if you find bugs or have any RFE you should really do this as early as possible so that there is time to fix/improve before we release. Wow, looks great in general. Thanks I'd love to see a feature, where it's possible to search for sub-packages as well. It would make many things easier. hm, the problem here is that pkgdb per definition does not know about sub-packages. What is the idea behing? Knowing the ACL on a specific sub-package or knowing generic information about a specific sub-package? In the first case, I don't know yet how to handle it, in the second case I believe /packages might be a better application for this: https://apps.fedoraproject.org/packages (Note the link from packages to pkgdb even on a sub-package page: https://apps.fedoraproject.org/packages/qt-devel ) Pierre -- 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: [pkgdb2] call for testers, bug reports and RFE
* Dan Mashal [10/12/2013 11:29] : Can we get a my packages button? Or am I blind and not seeing one? There's a Restrict to owner: form where you can enter your FAS username. Emmanuel -- 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: [pkgdb2] call for testers, bug reports and RFE
On Wed, 2013-12-11 at 09:55 +0100, Emmanuel Seyman wrote: * Dan Mashal [10/12/2013 11:29] : Can we get a my packages button? Or am I blind and not seeing one? There's a Restrict to owner: form where you can enter your FAS username. Also works if you just click on your nick on the top right corner. Pierre -- 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-20 Branched report: 20131211 changes
Compose started at Wed Dec 11 07:15:02 UTC 2013 Broken deps for armhfp -- [avro] avro-mapred-1.7.5-1.fc20.noarch requires hadoop-mapreduce avro-mapred-1.7.5-1.fc20.noarch requires hadoop-client [blueman] blueman-1.23-7.fc20.armv7hl requires obex-data-server = 0:0.4.3 blueman-1.23-7.fc20.armv7hl requires gvfs-obexftp [cloud-init] cloud-init-0.7.2-7.fc20.noarch requires dmidecode [cobbler] cobbler-2.4.0-2.fc20.noarch requires syslinux [fts] fts-server-3.1.1-1.fc20.armv7hl requires libactivemq-cpp.so.14 [ghc-hjsmin] ghc-hjsmin-devel-0.1.4.3-2.fc20.armv7hl requires ghc-devel(language-javascript-0.5.8-28fa88554adf134b03284de53334e91d) [gofer] ruby-gofer-0.75-4.fc20.noarch requires rubygem(qpid) = 0:0.16.0 [gtkd] gtkd-geany-tags-2.0.0-29.20120815git9ae9181.fc18.noarch requires gtkd = 0:2.0.0-29.20120815git9ae9181.fc18 [kawa] 1:kawa-1.11-5.fc19.armv7hl requires servlet25 [koji] koji-vm-1.8.0-2.fc20.noarch requires python-virtinst [kyua-cli] kyua-cli-0.5-3.fc19.armv7hl requires liblutok.so.0 kyua-cli-tests-0.5-3.fc19.armv7hl requires liblutok.so.0 [msp430-libc] msp430-libc-20120224-2.fc19.noarch requires msp430-gcc = 0:4.6.3 [nifti2dicom] nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtksys.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkWidgets.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkVolumeRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkViews.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkTextAnalysis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkParallel.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkInfovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkImaging.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkIO.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkHybrid.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGraphics.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGeovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGenericFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCommon.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCharts.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libQVTK.so.5.10 [nocpulse-common] nocpulse-common-2.2.7-2.fc20.noarch requires perl(RHN::DBI) [openbox] gdm-control-3.5.2-2.fc20.armv7hl requires gnome-panel gnome-panel-control-3.5.2-2.fc20.armv7hl requires gnome-panel [openpts] openpts-0.2.6-7.fc20.armv7hl requires tboot [owncloud] owncloud-5.0.13-1.fc20.noarch requires php-pear(pear.symfony.com/Routing) [perl-Language-Expr] perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) [php-Assetic] php-Assetic-1.1.2-1.fc20.noarch requires php-pear(pear.symfony.com/Process) 0:3.0 php-Assetic-1.1.2-1.fc20.noarch requires php-pear(pear.symfony.com/Process) = 0:2.1 [php-Metadata] php-Metadata-1.5.0-1.fc20.noarch requires php-pear(pear.symfony.com/DependencyInjection) [php-SymfonyCmfRouting] php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/Routing) 0:3.0 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/Routing) = 0:2.2 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/HttpKernel) 0:3.0 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/HttpKernel) = 0:2.2 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/EventDispatcher) 0:3.0 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/EventDispatcher) = 0:2.2 [php-doctrine-DoctrineDBAL] php-doctrine-DoctrineDBAL-2.3.4-4.fc20.noarch requires php-pear(pear.symfony.com/Console) 0:3.0 php-doctrine-DoctrineDBAL-2.3.4-4.fc20.noarch requires php-pear(pear.symfony.com/Console) = 0:2.0 [php-doctrine-DoctrineORM] php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires php-pear(pear.symfony.com/Yaml) 0:3.0 php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires php-pear(pear.symfony.com/Yaml) = 0:2.0 php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires php-pear(pear.symfony.com/Console) 0:3.0 php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires php-pear(pear.symfony.com/Console) = 0:2.0 [php-guzzle-Guzzle] php-guzzle-Guzzle-3.7.4-2.fc20.noarch requires php-pear(pear.symfony.com/EventDispatcher) = 0:2.1.0 [php-phpunit-DbUnit] php-phpunit-DbUnit-1.3.0-1.fc20.noarch requires
pacemaker in Fedora and RHEL
Hi all, I wonder if there are some reasonable explanations of package pacemaker in the repo. I checked the package and the result returned is: Fedora: pacemaker-1.1.9-3.fc20 in rawhide. RHEL: pacemaker-1.1.10-14.el6. The latest version is 1.1.11RC1(1.1.10 Final stable). Why is the package in Fedora behind the one in RHEL in spite of the maintainer of these two are the same people? Thanks. -- Yours sincerely, Christopher Meng Fєdоґa ї₴ al$о a кїпd оf нaт lїкє Яёd Haт. 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: ABRT in the comps group 'standard'
On 6.12.2013 10:56, Jakub Filak wrote: I'd like to add abrt-cli package to the comps group 'standard'. Regarding the discussion, there are two main concernes about adding abrt-cli to Standard comps group: 1) There will be some notifications popping up which can confuse users. Not true. Nothing changes for desktop environments. Package abrt-desktop is already part of GNOME and Cinnamon comps groups. What we are talking about here is abrt-cli [1] - command line interface, which will let users to list, review and report crashes on their systems caught by abrt. Root is informed about crashes by email, normal users should not be affected. 2) Abrt is sending information by default without opt-in. Not true. Abrt only stores crash details localy unless user calls 'abrt-cli report' command, or enables uReports [2]. Abrt actually helps to find and solve problems [3] so we decided to add abrt-cli to Standard comps group for F21. Regards, Vaclav [1] http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/System_Administrators_Guide/sect-abrt-cli.html [2] https://github.com/abrt/faf/wiki/uReport [3] https://bugzilla.redhat.com/show_bug.cgi?id=1036959 -- 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: ABRT in the comps group 'standard'
- Original Message - From: Václav Pavlín vpav...@redhat.com To: Development discussions related to Fedora devel@lists.fedoraproject.org Cc: Bill Nottingham nott...@redhat.com Sent: Wednesday, December 11, 2013 12:54:27 PM Subject: Re: ABRT in the comps group 'standard' On 6.12.2013 10:56, Jakub Filak wrote: I'd like to add abrt-cli package to the comps group 'standard'. Regarding the discussion, there are two main concernes about adding abrt-cli to Standard comps group: 1) There will be some notifications popping up which can confuse users. Not true. Nothing changes for desktop environments. Package abrt-desktop is already part of GNOME and Cinnamon comps groups. What we are talking about here is abrt-cli [1] - command line interface, which will let users to list, review and report crashes on their systems caught by abrt. Root is informed about crashes by email, normal users should not be affected. 2) Abrt is sending information by default without opt-in. Not true. Abrt only stores crash details localy unless user calls 'abrt-cli report' command, or enables uReports [2]. Abrt actually helps to find and solve problems [3] so we decided to add abrt-cli to Standard comps group for F21. Sorry for posting more or less a +1 reply. If there is anything I like in Fedora, it is definitely its bug solving and bug reporting features. I currently view the things Fedora can do with core dumps, gdb, debuginfo, stack traces and bug reporting as maybe the only reason a developer would choose Fedora over other distribution for development apart from its very relation to Red Hat. I guess there is more than that, but this is the one I can see during my everyday use. Any improvement to those is great IMO. On the other hand, technical improvements are not everything, and ABRT is a tool that one would like to have at hand all the time when anything gets wrong. Having the CLI always installed sounds like a natural choice to me. Cheers, Pavel Regards, Vaclav [1] http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/System_Administrators_Guide/sect-abrt-cli.html [2] https://github.com/abrt/faf/wiki/uReport [3] https://bugzilla.redhat.com/show_bug.cgi?id=1036959 -- 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
Self-introduction
Hi! I've been using Fedora for about two years now, and I appreciate both its technical and political choices, among which the policy of following closely upstream (and especially GNOME -- you know what I mean... :-). Regarding to my free software activities, I've been involved in GNOME development since about 2008, and before that a little with GNUnet -- though these days my PhD does not leave me much time for that. Anyway, I thought I could make a contribution to Fedora by packaging software that is related to my professional concerns as a social scientist. So I've made a review request for a new package for the (very promising) Julia language [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1040517 And for one of its dependencies, double-conversion: https://bugzilla.redhat.com/show_bug.cgi?id=1040027 So, you know, I need review and sponsor... :-) Regards 1: http://julialang.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: [pkgdb2] call for testers, bug reports and RFE
On 12/11/2013 09:19 AM, Pierre-Yves Chibon wrote: On Tue, Dec 10, 2013 at 09:52:58PM +0100, Matthias Runge wrote: On 12/10/2013 02:20 PM, Pierre-Yves Chibon wrote: So please, have a look at it, play with it, break it (no seriously, do, but don't forget to report how you did it afterward) and if you have any problem/RFE feel free to note them at: Just a heads-up, christmas holidays are coming our way and our agenda is to push pkgdb2 in production as soon as possible after the release of F20. This means that if you want to poke at it, if you find bugs or have any RFE you should really do this as early as possible so that there is time to fix/improve before we release. Wow, looks great in general. Thanks I'd love to see a feature, where it's possible to search for sub-packages as well. It would make many things easier. hm, the problem here is that pkgdb per definition does not know about sub-packages. What is the idea behing? Knowing the ACL on a specific sub-package or knowing generic information about a specific sub-package? The idea behind is: you have some application with an issue/error. You'll do rpm -qf filename and will get a package name, not necessarily the source package name. When filing a bug against a package, you'll need to know the source package name. Since packages should know their sub-packages, this would be easiest to link them both from here. Matthias -- 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: Self-introduction
On Tue, Dec 10, 2013 at 06:56:15PM -0800, Andrew Lutomirski wrote: I've been using Fedora for quite a few years as my main desktop OS, and I think it's time I contributed back by writing some packages. (Also, there are packages I want -- I might as well create them.) Hi Andrew, and welcome to the contributor side of things. I'm not a sponsor but I'm always glad to see more people get involved. Also I would like to see these INFINITY TIMES FASTER benchmarks you mention. Maybe we can apply that technology to other parts of Fedora. :) -- Matthew Miller -- Fedora Project Architect -- mat...@fedoraproject.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
[Maniphest] [Created] T27: Irrelevant phantom updates are not purged from active update list
tflink created this task. tflink added a subscriber: tflink. tflink added a project: blockerbugs TASK DESCRIPTION Currently, there are two anaconda updates displayed in the blocker tracking app. One is current, one is a phantom update that no longer exists in bodhi. The phantom update appears to have come from the fact that updates don't get UIDs before being pushed to updates-testing. This particular update was modified after the blocker tracking app picked it up but before the update was pushed to updates-testing. This means that the title changed before we could get the UID and we detected two different updates - one valid and one invalid. Regardless of the method by which the phantom updates are showing up, the update sync algorithm should be removing any phantom or invalid updates from the list. TASK DETAIL https://phab.qadevel.cloud.fedoraproject.org/T27 To: tflink Cc: qa-devel, tflink ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: Review Request 57: Multiple builds fixing a bug show confusing status label
On Dec. 10, 2013, 5:58 p.m., Tim Flink wrote: blockerbugs/models/update.py, line 55 http://reviewboard-tflink.rhcloud.com/r/57/diff/1/?file=1607#file1607line55 Why is this sort order change an improvement? If an older update is pending while a newer update is stable, we'd want to show the newer update Martin Krizek wrote: But wouldn't the older update be marked as obsolete? It should be but for example, if you look at the tracking app right now, there are 2 anaconda/blivet updates - one of which has been deleted in bodhi but still shows up. This issue was supposed to be fixed but obviously, it's not. Filed as https://phab.qadevel.cloud.fedoraproject.org/T27 I think that the problem of phantom updates are the root cause of the problem as reported, but I'll ask in bug to be sure. - Tim --- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/57/#review118 --- On Dec. 10, 2013, 3:54 p.m., Martin Krizek wrote: --- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/57/ --- (Updated Dec. 10, 2013, 3:54 p.m.) Review request for blockerbugs. Bugs: 438 https://fedorahosted.org/fedora-qa/ticket/438 Repository: blockerbugs Description --- commit 911781af9cc06e27c0a8580f07f7673c90e7329d Author: Martin Krizek mkri...@redhat.com Date: Tue Dec 10 16:28:52 2013 +0100 Sort updates by (status.desc(), pending.desc()) This way an update label is correctly set when multiple updates fix a bug. The label is chosen by the following order (the lowest one): pending testing testing pending stable stable Fixes: #438 Note: the rest of the issues with displaying label is handled outside this ticket in https://phab.qadevel.cloud.fedoraproject.org/T21 Diffs - blockerbugs/models/update.py 89c083da5c91558d4dead118c67e4a1138b8cae1 blockerbugs/controllers/main.py 1795ed1d717bb85e0f3d9e7e7008d68c2aae36d8 blockerbugs/__init__.py dcf6c5aadb24e6d86e95d5bb3d608b81721de47f Diff: http://reviewboard-tflink.rhcloud.com/r/57/diff/ Testing --- Sorting seems to be working as expected. Thanks, Martin Krizek ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: Review Request 57: Multiple builds fixing a bug show confusing status label
On Dec. 10, 2013, 5:58 p.m., Tim Flink wrote: blockerbugs/models/update.py, line 55 http://reviewboard-tflink.rhcloud.com/r/57/diff/1/?file=1607#file1607line55 Why is this sort order change an improvement? If an older update is pending while a newer update is stable, we'd want to show the newer update Martin Krizek wrote: But wouldn't the older update be marked as obsolete? Tim Flink wrote: It should be but for example, if you look at the tracking app right now, there are 2 anaconda/blivet updates - one of which has been deleted in bodhi but still shows up. This issue was supposed to be fixed but obviously, it's not. Filed as https://phab.qadevel.cloud.fedoraproject.org/T27 I think that the problem of phantom updates are the root cause of the problem as reported, but I'll ask in bug to be sure. After re-reading the bug, I stand corrected. That was a completely different issue than I was thinking about in my head. I don't like sorting on string fields by default but I also don't see much of a way around it unless we changed the schema to use status enums instead of strings. Go ahead and push to develop. We might want to look into changing the update status field to an enum but that's well outside the scope of this fix. - Tim --- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/57/#review118 --- On Dec. 10, 2013, 3:54 p.m., Martin Krizek wrote: --- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/57/ --- (Updated Dec. 10, 2013, 3:54 p.m.) Review request for blockerbugs. Bugs: 438 https://fedorahosted.org/fedora-qa/ticket/438 Repository: blockerbugs Description --- commit 911781af9cc06e27c0a8580f07f7673c90e7329d Author: Martin Krizek mkri...@redhat.com Date: Tue Dec 10 16:28:52 2013 +0100 Sort updates by (status.desc(), pending.desc()) This way an update label is correctly set when multiple updates fix a bug. The label is chosen by the following order (the lowest one): pending testing testing pending stable stable Fixes: #438 Note: the rest of the issues with displaying label is handled outside this ticket in https://phab.qadevel.cloud.fedoraproject.org/T21 Diffs - blockerbugs/models/update.py 89c083da5c91558d4dead118c67e4a1138b8cae1 blockerbugs/controllers/main.py 1795ed1d717bb85e0f3d9e7e7008d68c2aae36d8 blockerbugs/__init__.py dcf6c5aadb24e6d86e95d5bb3d608b81721de47f Diff: http://reviewboard-tflink.rhcloud.com/r/57/diff/ Testing --- Sorting seems to be working as expected. Thanks, Martin Krizek ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: missing on bodhi: gcc-c++-4.8.2-5.fc19.x86_64
On Wed, 11 Dec 2013 17:42:16 +0100 Reindl Harald h.rei...@thelounge.net wrote: Hi http://koji.fedoraproject.org/koji/buildinfo?buildID=483733 [root@testserver:~]$ rpm -qa | grep gcc gcc-c++-4.8.2-5.fc19.x86_64 libgcc-4.8.2-5.fc19.x86_64 gcc-4.8.2-5.fc19.x86_64 are these packages are missing on bodhi? http://bodhi.fedoraproject.org/ i would like to give positive karma after build MariaDB, Apache, PHP and VMware-Workstation kernel-modules succesful with it The maintainer has not yet submitted it as an update. 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
New release of Copr
New release of Copr is available at:
http://copr.fedoraproject.org
It has:
* nicer URL - http://copr.fedoraproject.org/ which is alias for
http://copr-fe.cloud.fedoraproject.org/
* extended API. See:
http://copr.fedoraproject.org/api/
* faster builds - previously builds for various chroots was serialized; they
run in parallel now.
* monitor of builds - for better overview. See:
https://fedorahosted.org/copr/wiki/ScreenshotsTutorial#monitor
* Support for Software collections - you can specify which packages should be always present in buildroot. For software
collections you need to have there: scl-utils-build and meta package (i.e name_of_collection-build). See:
https://fedorahosted.org/copr/wiki/ScreenshotsTutorial#chroot
* you can use markdown syntax in description of project now
* use of additional repos actually works now
* you can use non standard macros %{copr_username} and %{copr_projectname} in
your spec files if you want.
* Tito have support for Copr now (man releasers.conf for more info)
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Software Engineer, #brno, #devexp, #fedora-buildsys
--
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: missing on bodhi: gcc-c++-4.8.2-5.fc19.x86_64
Am 11.12.2013 17:46, schrieb Kevin Fenzi: On Wed, 11 Dec 2013 17:42:16 +0100 Reindl Harald h.rei...@thelounge.net wrote: Hi http://koji.fedoraproject.org/koji/buildinfo?buildID=483733 [root@testserver:~]$ rpm -qa | grep gcc gcc-c++-4.8.2-5.fc19.x86_64 libgcc-4.8.2-5.fc19.x86_64 gcc-4.8.2-5.fc19.x86_64 are these packages are missing on bodhi? http://bodhi.fedoraproject.org/ i would like to give positive karma after build MariaDB, Apache, PHP and VMware-Workstation kernel-modules succesful with it The maintainer has not yet submitted it as an update ah - ok - i am too fast :-) however, smells like working fine for me 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: missing on bodhi: gcc-c++-4.8.2-5.fc19.x86_64
On Wed, Dec 11, 2013 at 05:42:16PM +0100, Reindl Harald wrote: http://koji.fedoraproject.org/koji/buildinfo?buildID=483733 [root@testserver:~]$ rpm -qa | grep gcc gcc-c++-4.8.2-5.fc19.x86_64 libgcc-4.8.2-5.fc19.x86_64 gcc-4.8.2-5.fc19.x86_64 are these packages are missing on bodhi? http://bodhi.fedoraproject.org/ i would like to give positive karma after build MariaDB, Apache, PHP and VMware-Workstation kernel-modules succesful with it Please see http://gcc.gnu.org/PR59470, gcc-4.8.2-5 shouldn't be added. I'm debugging it right now, worst case I'll revert the offending commit if there is no fix available soon. 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
Schedule for Thursday's FPC Meeting (2013-12-12 17:00 UTC)
Following is the list of topics that will be discussed in the FPC meeting Thursday at 2013-12-12 17:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. rktime): 2013-12-12 09:00 Thu US/Pacific PST 2013-12-12 12:00 Thu US/Eastern EST 2013-12-12 17:00 Thu UTC - 2013-12-12 17:00 Thu Europe/London - 2013-12-12 18:00 Thu Europe/Paris CET 2013-12-12 18:00 Thu Europe/Berlin CET 2013-12-12 22:30 Thu Asia/Calcutta IST --new day-- 2013-12-13 01:00 Fri Asia/Singapore SGT 2013-12-13 01:00 Fri Asia/Hong_Kong HKT 2013-12-13 02:00 Fri Asia/Tokyo JST 2013-12-13 03:00 Fri Australia/Brisbane EST Links to all tickets below can be found at: https://fedorahosted.org/fpc/report/12 = Followups = (approval and retirement sections already passed) #topic #339 software collections in Fedora .fpc 339 https://fedorahosted.org/fpc/ticket/339 #topic #358 Please make some autotools guidelines. .fpc 358 https://fedorahosted.org/fpc/ticket/358 #topic #369 Guidance on dealing with the bundled libev in perl-EV .fpc 369 https://fedorahosted.org/fpc/ticket/369 #topic #372 Temporary bundling exception for kernel event library .fpc 372 https://fedorahosted.org/fpc/ticket/372 = New business = #topic #362 lpf should not be allowed in Fedora .fpc NNN https://fedorahosted.org/fpc/ticket/362 #topic #371 Packages approved without satisfied dependencies .fpc 371 https://fedorahosted.org/fpc/ticket/371 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at: https://fedorahosted.org/fpc/report/12 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/fpc, 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. -- 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: missing on bodhi: gcc-c++-4.8.2-5.fc19.x86_64
Am 11.12.2013 17:50, schrieb Jakub Jelinek: On Wed, Dec 11, 2013 at 05:42:16PM +0100, Reindl Harald wrote: http://koji.fedoraproject.org/koji/buildinfo?buildID=483733 [root@testserver:~]$ rpm -qa | grep gcc gcc-c++-4.8.2-5.fc19.x86_64 libgcc-4.8.2-5.fc19.x86_64 gcc-4.8.2-5.fc19.x86_64 are these packages are missing on bodhi? http://bodhi.fedoraproject.org/ i would like to give positive karma after build MariaDB, Apache, PHP and VMware-Workstation kernel-modules succesful with it Please see http://gcc.gnu.org/PR59470, gcc-4.8.2-5 shouldn't be added. I'm debugging it right now, worst case I'll revert the offending commit if there is no fix available soon thanks for feedback you can ping me at any time to verify whatever GCC working for server-packages with -fstack-protector-strong, i maintain most of them for several reasons in a private repo for our production infrastructure which is planned to be upgraded in the scond week of 2014 to F19 [harry@srv-rhsoft:~]$ /bin/ls -1 /fileserver/yum-repo/fc19/x86_64/ | grep \.rh aespipe-2.4c-5.fc19.20131024.rh.x86_64.rpm apr-1.5.0-4.fc19.20131127.rh.x86_64.rpm apr-devel-1.5.0-4.fc19.20131127.rh.x86_64.rpm arp-scan-1.8.4-1.fc19.20131024.rh.x86_64.rpm cantata-1.1.3-3.fc19.20131024.rh.x86_64.rpm dbmail-3.1.7-5.fc19.20131211.rh.bc9456e6b4773138c04f9ec81f2b95cd15e6.x86_64.rpm dbmail-manpages-3.1.7-5.fc19.20131211.rh.bc9456e6b4773138c04f9ec81f2b95cd15e6.x86_64.rpm dbmail-postfix-policyd-2011.05.25-10.fc19.20131024.rh.noarch.rpm dovecot-2.2.9-2.fc19.20131126.rh.x86_64.rpm ffmpeg-1.2.4-5.fc19.20131024.rh.x86_64.rpm ffmpeg-devel-1.2.4-5.fc19.20131024.rh.x86_64.rpm ffmpeg-latest-2.1.1-1.fc19.20131121.rh.x86_64.rpm ffmpeg-latest-ffserver-2.1.1-1.fc19.20131121.rh.x86_64.rpm ffmpeg-latest-manpages-2.1.1-1.fc19.20131121.rh.noarch.rpm ffmpeg-libs-1.2.4-5.fc19.20131024.rh.x86_64.rpm fsync-tester-1.0-1.fc19.20130819.rh.x86_64.rpm GeoIP-1.5.1-2.fc19.20131024.rh.x86_64.rpm GeoIP-devel-1.5.1-2.fc19.20131024.rh.x86_64.rpm gmime-2.6.19-1.fc19.20131024.rh.x86_64.rpm gmime-devel-2.6.19-1.fc19.20131024.rh.x86_64.rpm hostapd-2.0-6.fc19.20131024.rh.x86_64.rpm httpd-2.4.7-4.fc19.20131127.rh.x86_64.rpm httpd-devel-2.4.7-4.fc19.20131127.rh.x86_64.rpm httpd-extras-2.4.7-4.fc19.20131127.rh.x86_64.rpm httpd-extras-auth-2.4.7-4.fc19.20131127.rh.x86_64.rpm httpd-manual-2.4.7-4.fc19.20131127.rh.noarch.rpm httpd-tools-2.4.7-4.fc19.20131127.rh.x86_64.rpm hylafax-5.5.4-3.fc19.20131024.rh.x86_64.rpm iat-0.1.7-16.fc19.20131024.rh.x86_64.rpm iaxmodem-1.2.0-9.fc19.20131024.rh.x86_64.rpm lame-3.99.5-4.fc19.20131024.rh.x86_64.rpm lame-devel-3.99.5-4.fc19.20131024.rh.x86_64.rpm lame-libs-3.99.5-4.fc19.20131024.rh.x86_64.rpm lame-mp3x-3.99.5-4.fc19.20131024.rh.x86_64.rpm libevent-2.0.21-4.fc19.20131024.rh.x86_64.rpm libevent-devel-2.0.21-4.fc19.20131024.rh.x86_64.rpm libmpdclient-2.9-2.fc19.20131106.rh.x86_64.rpm libmpdclient-devel-2.9-2.fc19.20131106.rh.x86_64.rpm libnss-mysql-1.5-19.fc19.20131024.rh.x86_64.rpm libsamplerate-0.1.8-4.fc19.20131024.rh.x86_64.rpm libsamplerate-devel-0.1.8-4.fc19.20131024.rh.x86_64.rpm libvpx-1.2.0-5.fc19.20131024.rh.x86_64.rpm libvpx-devel-1.2.0-5.fc19.20131024.rh.x86_64.rpm libvpx-utils-1.2.0-5.fc19.20131024.rh.x86_64.rpm libzdb-2.12-2.fc19.20131024.rh.x86_64.rpm libzdb-devel-2.12-2.fc19.20131024.rh.x86_64.rpm lounge-arrakis-19.0-1.fc19.20131210.rh.noarch.rpm lounge-base-19.0-1.fc19.20131210.rh.noarch.rpm lounge-build-requires-19.0-2.fc19.20131210.rh.noarch.rpm lounge-buildserver-19.0-1.fc19.20131210.rh.noarch.rpm lounge-caladan-19.0-1.fc19.20131210.rh.noarch.rpm lounge-fileserver-19.0-1.fc19.20131210.rh.noarch.rpm lounge-flow-19.0-3.fc19.20131210.rh.noarch.rpm lounge-mailserver-19.0-1.fc19.20131210.rh.noarch.rpm lounge-master-19.0-1.fc19.20131210.rh.noarch.rpm lounge-multimedia-19.0-1.fc19.20131210.rh.noarch.rpm lounge-nameserver-19.0-1.fc19.20131210.rh.noarch.rpm lounge-rhsoft-backup-19.0-1.fc19.20131210.rh.noarch.rpm lounge-rhsoft-build-requires-19.0-2.fc19.20131210.rh.noarch.rpm lounge-rhsoft-extras-19.0-1.fc19.20131210.rh.noarch.rpm lounge-rhsoft-testserver-19.0-2.fc19.20131210.rh.noarch.rpm lounge-rhsoft-workstation-19.0-1.fc19.20131210.rh.noarch.rpm lounge-router-19.0-1.fc19.20131210.rh.noarch.rpm lounge-sftp-19.0-1.fc19.20131210.rh.noarch.rpm lounge-thx1138-19.0-1.fc19.20131210.rh.noarch.rpm lounge-trafficserver-19.0-1.fc19.20131210.rh.noarch.rpm lounge-virenscanner-19.0-1.fc19.20131210.rh.noarch.rpm lounge-voip-19.0-1.fc19.20131210.rh.noarch.rpm lounge-vpn-19.0-1.fc19.20131210.rh.noarch.rpm lounge-webserver-19.0-1.fc19.20131210.rh.noarch.rpm lounge-webserver-extras-19.0-1.fc19.20131210.rh.noarch.rpm lzo-2.06-4.fc19.20131024.rh.x86_64.rpm lzo-devel-2.06-4.fc19.20131024.rh.x86_64.rpm lzo-minilzo-2.06-4.fc19.20131024.rh.x86_64.rpm mariadb-5.5.34-3.fc19.20131127.rh.x86_64.rpm mariadb-devel-5.5.34-3.fc19.20131127.rh.x86_64.rpm mariadb-libs-5.5.34-3.fc19.20131127.rh.x86_64.rpm mariadb-manpages-5.5.34-3.fc19.20131127.rh.x86_64.rpm
Re: Self-introduction
On Wed, Dec 11, 2013 at 8:33 AM, Matthew Miller mat...@fedoraproject.org wrote: On Tue, Dec 10, 2013 at 06:56:15PM -0800, Andrew Lutomirski wrote: I've been using Fedora for quite a few years as my main desktop OS, and I think it's time I contributed back by writing some packages. (Also, there are packages I want -- I might as well create them.) Hi Andrew, and welcome to the contributor side of things. I'm not a sponsor but I'm always glad to see more people get involved. Thanks! Also I would like to see these INFINITY TIMES FASTER benchmarks you mention. Maybe we can apply that technology to other parts of Fedora. :) :) It's an exaggeration, of course. In all of the other serialization formats I know of, users first compose a message in some intermediate, friendly format, and then the library serializes or deserializes that data. In Cap'n Proto, the intermediate format *is* the wire format, so the final step is unnecessary. Hence it's INFINITY TIMES FASTER! --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: [Fedora-packaging] Schedule for Thursday's FPC Meeting (2013-12-12 17:00 UTC)
On 12/11/2013 06:09 PM, James Antill wrote: Following is the list of topics that will be discussed in the FPC meeting Thursday at 2013-12-12 17:00 UTC in #fedora-meeting-1 on irc.freenode.net. Due to other obligations, I'll likely not be able to attend. Ralf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Shared System Certificates followup: Packaging Guidelines?
Last night someone asked me about a package that they were working on that had a pem file in it. Looking closer, it seems that the pem file is a cacert bundle. Looking around, there's not currently documentation on what to do with these. I did find some information on the wiki, though: https://fedoraproject.org/wiki/PackagingDrafts/Certificates https://fedoraproject.org/wiki/Features/SharedSystemCertificates https://fedoraproject.org/wiki/Talk:Features/SharedSystemCertificates I'm by no means an expert in this area but my impression is that the PackagingDraft is made obsolete by the Shared System Certificates Feature. As Killerix and Misc note on the talk page we should probably have some packaging guidelines added that tell us what the expectations are. The Guideline should answer the following questions: * Should packages that ship their own cacerts be patched to use Shared System Certificates instead? [I think the answer to this is yes] * If the package contains a cacert that is not in our bundle, should those be added? * How does a package add a cacert to our existing bundle? Is there anyone available to write a draft for this and submit it to the FPC (and answer questions that come up)? -Toshio pgpJYfjCdw6Tj.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: Shared System Certificates followup: Packaging Guidelines?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/11/2013 12:59 PM, Toshio Kuratomi wrote: * Should we allow packages to ship automatically trusted certificates? We need to be cognizant of the potential risk inherent in allowing packagers to drop new trusted CA certificates onto the system. It's worth considering whether such things should require an approval process. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKoqWcACgkQeiVVYja6o6OV4QCgo8tNx+JPvfuGUlx68CDI8iZZ hk0An3BfXv38IRNOlrYXBpv9usNZuVTa =m/HR -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: Shared System Certificates followup: Packaging Guidelines?
On Wed, Dec 11, 2013 at 6:59 PM, Toshio Kuratomi a.bad...@gmail.com wrote: I'm by no means an expert in this area but my impression is that the PackagingDraft is made obsolete by the Shared System Certificates Feature. Shared system certificates are unrelated to application-specific certificates and private keys, and to some extent even to application-specific (or specifically-per-application-configured) CA certificates. * Should packages that ship their own cacerts be patched to use Shared System Certificates instead? [I think the answer to this is yes] * If the package contains a cacert that is not in our bundle, should those be added? * How does a package add a cacert to our existing bundle? The preference I've heard earlier is to use ca-certificates as the only authority (and ca-certificates using the Mozilla CA set without making similar decisions at the Fedora level, because we don't have any resources to do CA vetting), and disallow other packages from shipping and installing any other system-wide CA certificate. I suppose setting up some kind of site-wide mechanism like freeipa could also install a CA certificate, but it would be a generated certificate not shipped by a package, and it would have to be an explicit administrator's action. This makes sense to me; if there are cases that this can't account for, please speak up. 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: Shared System Certificates followup: Packaging Guidelines?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/11/2013 01:07 PM, Miloslav Trmač wrote: On Wed, Dec 11, 2013 at 6:59 PM, Toshio Kuratomi a.bad...@gmail.com wrote: I'm by no means an expert in this area but my impression is that the PackagingDraft is made obsolete by the Shared System Certificates Feature. Shared system certificates are unrelated to application-specific certificates and private keys, and to some extent even to application-specific (or specifically-per-application-configured) CA certificates. * Should packages that ship their own cacerts be patched to use Shared System Certificates instead? [I think the answer to this is yes] * If the package contains a cacert that is not in our bundle, should those be added? * How does a package add a cacert to our existing bundle? The preference I've heard earlier is to use ca-certificates as the only authority (and ca-certificates using the Mozilla CA set without making similar decisions at the Fedora level, because we don't have any resources to do CA vetting), and disallow other packages from shipping and installing any other system-wide CA certificate. I suppose setting up some kind of site-wide mechanism like freeipa could also install a CA certificate, but it would be a generated certificate not shipped by a package, and it would have to be an explicit administrator's action. This makes sense to me; if there are cases that this can't account for, please speak up. Well, a (hacky) pattern that I am using for OpenPegasus to support OpenLMI is this: 1) Create a private key file and an x509v3 CA certificate with CA:TRUE 2) Create a new private key and signing request for the service ticket for Pegasus with a lifetime of 10 years. 3) Sign the service certificate with the CA certificate. 4) *Delete the private key file for the CA certificate* 5) Put the public CA certificate into the trusted store While this is technically adding a CA certificate into the system-wide store, by deleting the private key file, it removes the risk that the key could subsequently be used by anyone else. Granted, there's a small race condition during the signing process where the key could be stolen by root on the box doing the installation, but that's probably negligible risk. (For the record, the benefit this brings is that users can use tools like YAWN or pyWBEM against localhost without having to ignore the certificate validation). -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKoqvAACgkQeiVVYja6o6PCqACeL2RJI8q2ICGkaq4AUK/V4fi+ Vk8AniZprSeZ7NRSTs+uWfp2PHBtfS3X =Av3l -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: Schedule for Thursday's FPC Meeting (2013-12-12 17:00 UTC)
Dne 11.12.2013 18:09, James Antill napsal(a): 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/fpc, 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. Could you plese discuss https://fedorahosted.org/fpc/ticket/368 ? Thanks -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
ecryptfs alternatives
Hi, I have read in RHEL 7 beta release notes that ecryptfs will be deprecated in this release. The problem is that I've got a system on Fedora19 (which I want to move to EL7 after release) with some encrypted data. I'm looking for realiable alternative to ecryptfs that will work on EL7 out of box or will be relatively easy to build (without rebuilding kernel modules every update). Can you recommend any solutions? -- Best regards, Michal http://eventhorizon.pl/ -- 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: ecryptfs alternatives
2013/12/11 Michał Piotrowski mkkp...@gmail.com: Hi, I have read in RHEL 7 beta release notes that ecryptfs will be deprecated in this release. The problem is that I've got a system on Fedora19 (which I want to move to EL7 after release) with some encrypted data. I'm looking for realiable alternative to ecryptfs that will work on EL7 out of box or will be relatively easy to build (without rebuilding kernel modules every update). Can you recommend any solutions? dm-crypt. Also compatible with TrueCrypt (via external userspace utility - tc-play). -- 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
Summary/Minutes from today's FESCo Meeting (2013-12-11)
=== #fedora-meeting: FESCO (2013-12-11) === Meeting started by mattdm at 18:00:46 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-12-11/fesco.2013-12-11-18.00.log.html . Meeting summary --- * init process (mattdm, 18:00:59) * #1185 Enable -Werror=format-security by default (mattdm, 18:04:33) * AGREED: We add -Werror=format-security by default. (A -1 indicates that we will add -Wformat-security instead) (+7,-2) (mattdm, 18:17:29) * #1201 Enabling third party repositories (mattdm, 18:18:02) * AGREED: Proposal: Copr repos may be searched for applications to install as long as the user is explicitly asked to enable the copr before installing packages from them (See https://fedorahosted.org/fesco/ticket/1201#comment:19 for details) (+6,-,0) (mattdm, 18:36:59) * signing and unicorns for all (mattdm, 18:37:05) * AGREED: FESCo is okay with pointing to free software repositories approved by Fedora Legal in the same way as COPR repos (+8/-0/1) (mattdm, 19:13:53) * AGREED: For non-free sofware repositories, FESCo is not changing exisiting policy. If you think the policy should change, talk to the board. (+9,-0,0) (mattdm, 19:19:06) * AGREED: Revised 1a (with proposal and t8m's feedback): FESCo is okay with pointing to free software repositories in the same way as COPR repos if they are approved by FESCo and Fedora Legal. They are not limited in the criteria that they can choose to apply. (+7,-0,1) (mattdm, 19:44:49) * further discussion to ticket and lists if necessary (mattdm, 19:45:55) * #1211 F21 System Wide Change: Headless Java (mattdm, 19:46:27) * LINK: https://fedoraproject.org/wiki/Changes/HeadlessJava (mattdm, 19:46:47) * AGREED: Headless Java system wide change is approved. Please update the change page to be consistent with comment#2 in the ticket and get updated packaging guidelines to FPC soon. (+8,0,0) (mattdm, 19:53:18) * Next week's chair (mattdm, 19:53:41) * abadger1999 to chair next week. (mattdm, 19:55:27) * we're going to skip the next two meetings after next week due to the holidays (mattdm, 19:55:44) * Open Floor (mattdm, 19:56:08) * t8m to chair january 8th meetiing (mattdm, 19:59:45) Meeting ended at 20:01:35 UTC. Action Items Action Items, by person --- * **UNASSIGNED** * (none) People Present (lines said) --- * mattdm (145) * abadger1999 (75) * jwb (62) * sgallagh (56) * mitr (43) * notting (40) * pjones (33) * t8m (31) * nirik (25) * mmaslano (17) * zodbot (15) * halfie (6) * jreznik (2) * pknirsch (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Matthew Miller -- Fedora Project Architect -- mat...@fedoraproject.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: ecryptfs alternatives
Hi, 2013/12/11 Peter Lemenkov lemen...@gmail.com 2013/12/11 Michał Piotrowski mkkp...@gmail.com: Hi, I have read in RHEL 7 beta release notes that ecryptfs will be deprecated in this release. The problem is that I've got a system on Fedora19 (which I want to move to EL7 after release) with some encrypted data. I'm looking for realiable alternative to ecryptfs that will work on EL7 out of box or will be relatively easy to build (without rebuilding kernel modules every update). Can you recommend any solutions? dm-crypt. Also compatible with TrueCrypt (via external userspace utility - tc-play). The beauty of ecryptfs is that I can encrypt one dir - not whole file system. -- 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 -- Best regards, Michal http://eventhorizon.pl/ -- 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: FTBFS if -Werror=format-security flag is used
Brendan Jones wrote: What is the best way to handle this case: qWarning(QObject::tr(Client name '%1' occupied.).arg(name).toUtf8()); something like, or can I make it simpler: qWarning(%s,qPrintable(QObject::tr(Client name '%1' occupied.).arg(name).toUtf8())); Use one of: qWarning() QObject::tr(Client name '%1' occupied.).arg(name); or: qWarning(%s, QObject::tr(Client name '%1' occupied.).arg(name).toLocal8Bit().data()); Note that hardcoding toUtf8() is also a bad idea here, the right encoding to use is toLocal8Bit(), or this will print junk in non-UTF-8 locales. (In our default UTF-8 locales, it will make no difference.) 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: Shared System Certificates followup: Packaging Guidelines?
Can be also extended for Mono snk key file stored in /etc/pki. We should also let packagers to use the system shipped key file instead of using the bundled anymore. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Fedora 20 Final status report
Sorry I didn't do more of these, but mostly, the people who've had work to do have known about it, and we've just been trying to get it all done... We have an RC1 compose running at the moment. Go/No-Go is tomorrow (12-12), and RC1 is substantially different from TC5, so we really need to run through as many of the validation tests as we possibly can with RC1. I'll try and notify in #fedora-qa and by email once the key RC1 builds that come out of Koji - desktop and KDE x86 lives, and the cloud and ARM images - are done; we'll have to wait a bit longer for the DVD and netinst. The validation matrices, as always, will be available at: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Right now those redirects are still pointing to TC5, but we'll bump them to RC1 as soon as we have something to test. If as many folks as possible can pitch in and help test, that'd be great. I and other QA folks will be on hand on IRC, in #fedora-qa and other channels, if you have any questions, from now till the go/no-go. If you hit any significant issues, please report it in #fedora-qa or to the list and/or file a bug and mark it as blocking the bug FinalBlocker (or use the webapp - https://qa.fedoraproject.org/blockerbugs/propose_bug - to nominate it as blocker/FE). Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- 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 20 Final status report
On Wed, 2013-12-11 at 17:32 -0800, Adam Williamson wrote: Sorry I didn't do more of these, but mostly, the people who've had work to do have known about it, and we've just been trying to get it all done... We have an RC1 compose running at the moment. Go/No-Go is tomorrow (12-12), and RC1 is substantially different from TC5, so we really need to run through as many of the validation tests as we possibly can with RC1. I'll try and notify in #fedora-qa and by email once the key RC1 builds that come out of Koji - desktop and KDE x86 lives, and the cloud and ARM images - are done; we'll have to wait a bit longer for the DVD and netinst. The validation matrices, as always, will be available at: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test https://fedoraproject.org/wiki/Test_Results:Current_Base_Test The desktop (GNOME) and KDE lives for both Intel arches are now done: http://kojipkgs.fedoraproject.org//work/tasks/1953/6281953/Fedora-Live-Desktop-i686-20-1.iso http://kojipkgs.fedoraproject.org//work/tasks/1956/6281956/Fedora-Live-Desktop-x86_64-20-1.iso http://kojipkgs.fedoraproject.org//work/tasks/1958/6281958/Fedora-Live-KDE-i686-20-1.iso http://kojipkgs.fedoraproject.org//work/tasks/1959/6281959/Fedora-Live-KDE-x86_64-20-1.iso As are the minimal ARM builds: http://kojipkgs.fedoraproject.org//work/tasks/2005/6282005/Fedora-Minimal-armhfp-20-1-sda.raw.xz http://kojipkgs.fedoraproject.org//work/tasks/2020/6282020/Fedora-Minimal-VFAT-armhfp-20-1-sda.raw.xz the KDE ARM builds are still running, but should be done soonish. Cloud task is complete: http://koji.fedoraproject.org/koji/taskinfo?taskID=6282038 but I'm not sufficiently cloud-y to know whether you can do anything with the image file from that task, or if releng have to do stuff to it before it's usable. We'll notify once the compose is fully done, of course, but for now it'd be great if folks can get a head start on testing with those images. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- 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: [pkgdb2] call for testers, bug reports and RFE
On Wed, 2013-12-11 at 17:18 +0100, Matthias Runge wrote: The idea behind is: you have some application with an issue/error. You'll do rpm -qf filename and will get a package name, not necessarily the source package name. When filing a bug against a package, you'll need to know the source package name. rpm -qi gives you the source package. -- Mathieu -- 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: pacemaker in Fedora and RHEL
On 11/12/13 06:36, Christopher Meng wrote: Hi all, I wonder if there are some reasonable explanations of package pacemaker in the repo. I checked the package and the result returned is: Fedora: pacemaker-1.1.9-3.fc20 in rawhide. RHEL: pacemaker-1.1.10-14.el6. The latest version is 1.1.11RC1(1.1.10 Final stable). Why is the package in Fedora behind the one in RHEL in spite of the maintainer of these two are the same people? Thanks. -- Yours sincerely, Christopher Meng Hi Christopher, I can't speak authoritatively, but I am willing to bet it's a couple of things. There was a huge push to get 1.1.10 ready for rhel 6.5, there has been a lot of work on 1.1.11 and Andrew's wife just gave birth, so he's on vacation for a bit. I would guess that pacemaker on fedora just didn't get to the front of the burner yet. digimer -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Test-Announce] Fedora 20 Final Release Candidate 1 (RC1) Available Now!
NOTE: The 32-bit Install DVD is over its size limit. As per the Fedora 20 schedule [1], Fedora 20 Final Release Candidate 1 (RC1) is now available for testing. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/5808#comment:15 . Please see the following pages for download links (including delta ISOs) and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download-ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace dl with download-ib01 in the download URL. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Ideally, all Alpha, Beta, and Final priority test cases for Installation [2], Base [3], and Desktop [4] should pass in order to meet the Final Release Criteria [5]. Help is available on #fedora-qa on irc.freenode.net [6], or on the test list [7]. Create Fedora 20 Final test compose (TC) and release candidate (RC) https://fedorahosted.org/rel-eng/ticket/5808 Current Blocker and Freeze Exception bugs: http://qa.fedoraproject.org/blockerbugs/current [1] http://fedorapeople.org/groups/schedule/f-20/f-20-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Installation_validation_testing [3] https://fedoraproject.org/wiki/QA:Base_validation_testing [4] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [5] https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria [6] irc://irc.freenode.net/fedora-qa [7] https://admin.fedoraproject.org/mailman/listinfo/test signature.asc Description: OpenPGP digital signature ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-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
[Bug 1040195] perl-CPANPLUS-0.9144 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1040195 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-CPANPLUS-0.91.44-1.fc2 ||1 Resolution|--- |RAWHIDE Last Closed||2013-12-11 03:02:55 -- 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=wpVDm6Vpl0a=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
File Math-PlanePath-112.tar.gz uploaded to lookaside cache by churchyard
A file has been added to the lookaside cache for perl-Math-PlanePath: 4fda4d575dd7288511a48d2957135ce0 Math-PlanePath-112.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-Math-PlanePath] New version 112 (#1039713)
commit 674cd2bc806d8a4928d7aed2872469d69b3adcdf
Author: Miro Hrončok m...@hroncok.cz
Date: Wed Dec 11 11:12:29 2013 +0100
New version 112 (#1039713)
.gitignore |1 +
perl-Math-PlanePath.spec |5 -
sources |2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 2d13ca6..b7c6deb 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,3 +2,4 @@
/Math-PlanePath-105.tar.gz
/Math-PlanePath-110.tar.gz
/Math-PlanePath-111.tar.gz
+/Math-PlanePath-112.tar.gz
diff --git a/perl-Math-PlanePath.spec b/perl-Math-PlanePath.spec
index 5a5b14a..f0a0a90 100644
--- a/perl-Math-PlanePath.spec
+++ b/perl-Math-PlanePath.spec
@@ -1,5 +1,5 @@
Name: perl-Math-PlanePath
-Version:111
+Version:112
Release:1%{?dist}
Summary:Mathematical paths through the 2-D plane
License:GPLv3+
@@ -59,6 +59,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Wed Dec 11 2013 Miro Hrončok mhron...@redhat.com - 112-1
+- New version 112 (#1039713)
+
* Tue Nov 26 2013 Miro Hrončok mhron...@redhat.com - 111-1
- New version 111 (#1030912)
diff --git a/sources b/sources
index b51ee1f..80bdfde 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-40afd50f14dacf080213d7b59c8d421e Math-PlanePath-111.tar.gz
+4fda4d575dd7288511a48d2957135ce0 Math-PlanePath-112.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
File ExtUtils-Typemaps-Default-1.05.tar.gz uploaded to lookaside cache by churchyard
A file has been added to the lookaside cache for perl-ExtUtils-Typemaps-Default: 346c127faf7b74bc4cfc29fa3e8e6f8d ExtUtils-Typemaps-Default-1.05.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-ExtUtils-Typemaps-Default] New upstream release 1.05 (#1039710)
commit 36884546ba1711bf567b8e69c7994c65d1923c92
Author: Miro Hrončok m...@hroncok.cz
Date: Wed Dec 11 11:27:13 2013 +0100
New upstream release 1.05 (#1039710)
.gitignore |1 +
perl-ExtUtils-Typemaps-Default.spec | 14 +++---
sources |2 +-
3 files changed, 13 insertions(+), 4 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 84e4670..dec13a7 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
/ExtUtils-Typemaps-Default-1.01.tar.gz
/ExtUtils-Typemaps-Default-1.04.tar.gz
+/ExtUtils-Typemaps-Default-1.05.tar.gz
diff --git a/perl-ExtUtils-Typemaps-Default.spec
b/perl-ExtUtils-Typemaps-Default.spec
index 1b81ba4..662cd5f 100644
--- a/perl-ExtUtils-Typemaps-Default.spec
+++ b/perl-ExtUtils-Typemaps-Default.spec
@@ -1,5 +1,5 @@
Name: perl-ExtUtils-Typemaps-Default
-Version:1.04
+Version:1.05
Release:1%{?dist}
Summary:Set of useful typemaps
License:GPL+ or Artistic
@@ -7,10 +7,11 @@ Group: Development/Libraries
URL:http://search.cpan.org/dist/ExtUtils-Typemaps-Default/
Source0:
http://www.cpan.org/authors/id/S/SM/SMUELLER/ExtUtils-Typemaps-Default-%{version}.tar.gz
BuildArch: noarch
-BuildRequires: perl(ExtUtils::Typemaps) = 1.00
+# temporary fix until more recent version is available
+BuildRequires: perl(ExtUtils::Typemaps) = 3.18-292
BuildRequires: perl(Module::Build)
BuildRequires: perl(Test::More)
-Requires: perl(ExtUtils::Typemaps) = 1.00
+Requires: perl(ExtUtils::Typemaps) = 3.18-292
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
# Filtering unversioned requires
@@ -30,6 +31,9 @@ ExtUtils::Typemaps::Basic
%prep
%setup -q -n ExtUtils-Typemaps-Default-%{version}
+# this is fixed in BuildRequired version of ExtUtils::Typemap 3.18-292
+sed -i 's/3.18_03/3.18/' Build.PL
+
%build
%{__perl} Build.PL installdirs=vendor
./Build
@@ -48,6 +52,10 @@ ExtUtils::Typemaps::Basic
%{_mandir}/man3/*
%changelog
+* Wed Dec 11 2013 Miro Hrončok mhron...@redhat.com - 1.05-1
+- New upstream release 1.05 (#1039710)
+- Temporarily (build)require ExtUtils::Typemaps = 3.18-292, patch Build.PL to
accept it
+
* Wed Aug 28 2013 Miro Hrončok mhron...@redhat.com - 1.04-1
- New upstream release
diff --git a/sources b/sources
index ceba54e..2b0ad12 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-d76a8c53e38e648088b5f5f8df1b2fac ExtUtils-Typemaps-Default-1.04.tar.gz
+346c127faf7b74bc4cfc29fa3e8e6f8d ExtUtils-Typemaps-Default-1.05.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
Broken dependencies: perl-Language-Expr
perl-Language-Expr has broken dependencies in the F-20 tree: On x86_64: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) Please resolve this as soon as possible. -- 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-ExtUtils-Typemaps-Default/f20] New upstream release 1.05 (#1039710)
Summary of changes: 3688454... New upstream release 1.05 (#1039710) (*) (*) This commit already existed in another branch; no separate mail sent -- 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 1039713] perl-Math-PlanePath-112 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1039713 Miro Hrončok mhron...@redhat.com changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |RAWHIDE Last Closed||2013-12-11 05:38:07 -- 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=7OdMxPHZ00a=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 1039710] perl-ExtUtils-Typemaps-Default-1.05 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1039710 --- Comment #1 from Fedora Update System upda...@fedoraproject.org --- perl-ExtUtils-Typemaps-Default-1.05-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/perl-ExtUtils-Typemaps-Default-1.05-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=pgYtc1RUTYa=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
Broken dependencies: perl-Language-Expr
perl-Language-Expr has broken dependencies in the rawhide tree: On x86_64: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) Please resolve this as soon as possible. -- 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 1040414] New: perl-Glib-Object-Introspection-0.017 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1040414 Bug ID: 1040414 Summary: perl-Glib-Object-Introspection-0.017 is available Product: Fedora Version: rawhide Component: perl-Glib-Object-Introspection Keywords: FutureFeature, Triaged Assignee: berra...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: berra...@redhat.com, perl-devel@lists.fedoraproject.org Latest upstream release: 0.017 Current version/release in Fedora Rawhide: 0.016-1.fc21 URL: http://search.cpan.org/dist/Glib-Object-Introspection/ 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=2O0RuHWARFa=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 1040416] New: perl-Gtk2-1.249 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1040416 Bug ID: 1040416 Summary: perl-Gtk2-1.249 is available Product: Fedora Version: rawhide Component: perl-Gtk2 Keywords: FutureFeature, Triaged Assignee: tcall...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, tcall...@redhat.com Latest upstream release: 1.249 Current version/release in Fedora Rawhide: 1.248-1.fc21 URL: http://search.cpan.org/dist/Gtk2/ 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=22UV3myTnka=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
File pmtools-1.54.tar.gz uploaded to lookaside cache by jpo
A file has been added to the lookaside cache for perl-pmtools: 1a83a0209f3fde110f65647a9741c442 pmtools-1.54.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-pmtools] Update to 1.54.
commit 75727465c57368c90293ea9d128f3cd36035c10a
Author: Jose Pedro Oliveira j...@di.uminho.pt
Date: Wed Dec 11 14:57:46 2013 +
Update to 1.54.
.gitignore|1 +
perl-pmtools.spec | 12 +---
sources |2 +-
3 files changed, 11 insertions(+), 4 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 6d020fe..283fc65 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
pmtools-1.10.tar.gz
/pmtools-1.30.tar.gz
+/pmtools-1.54.tar.gz
diff --git a/perl-pmtools.spec b/perl-pmtools.spec
index 1d38cc2..bd88bec 100644
--- a/perl-pmtools.spec
+++ b/perl-pmtools.spec
@@ -1,5 +1,5 @@
Name: perl-pmtools
-Version:1.30
+Version:1.54
Release:1%{?dist}
Summary:A suite of small programs to help manage Perl modules
@@ -11,6 +11,7 @@ BuildRoot:
%{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(Test::More)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
%description
@@ -25,7 +26,7 @@ Tom Christiansen
%prep
%setup -q -n pmtools-%{version}
find . -type f -perm 755 | xargs %{__perl} -pi -e 's{^#!/usr/bin/env
perl}{#!%{__perl}}'
-chmod -c a-x Changes README TODO Devel/Loaded.pm
+chmod -c a-x Changes TODO lib/Devel/Loaded.pm
%build
@@ -51,14 +52,19 @@ rm -rf $RPM_BUILD_ROOT
%files
%defattr(-,root,root,-)
-%doc Changes README TODO
+%doc Changes LICENSE README TODO
%{_bindir}/*
%{perl_vendorlib}/Devel/
+%{perl_vendorlib}/pmtools.pm
%{_mandir}/man1/*.1*
%{_mandir}/man3/*.3*
%changelog
+* Wed Dec 11 2013 Jose Pedro Oliveira jpo at di.uminho.pt - 1.54-1
+- Update to 1.54.
+- New build requirement: perl(Test::More).
+
* Tue Dec 10 2013 Jose Pedro Oliveira jpo at di.uminho.pt - 1.30-1
- Update to 1.30.
diff --git a/sources b/sources
index 8201a81..bfb5b00 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-444187e2b9361c423b783c31d395 pmtools-1.30.tar.gz
+1a83a0209f3fde110f65647a9741c442 pmtools-1.54.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-pmtools] The test suite also needs the less command in the build root.
commit 086b402456cf375378a3a2d2dcef08c42bf0
Author: Jose Pedro Oliveira j...@di.uminho.pt
Date: Wed Dec 11 15:25:37 2013 +
The test suite also needs the less command in the build root.
perl-pmtools.spec | 14 ++
1 files changed, 6 insertions(+), 8 deletions(-)
---
diff --git a/perl-pmtools.spec b/perl-pmtools.spec
index bd88bec..995f925 100644
--- a/perl-pmtools.spec
+++ b/perl-pmtools.spec
@@ -1,6 +1,6 @@
Name: perl-pmtools
Version:1.54
-Release:1%{?dist}
+Release:2%{?dist}
Summary:A suite of small programs to help manage Perl modules
Group: Development/Libraries
@@ -10,9 +10,10 @@ Source:
http://www.cpan.org/authors/id/M/ML/MLFISHER/pmtools-%{version}.
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
+
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(Test::More)
-Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+BuildRequires: less
%description
This is pmtools -- a suite of small programs to help manage modules.
@@ -35,7 +36,6 @@ 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 -type d -depth -exec rmdir {} 2/dev/null ';'
@@ -46,12 +46,7 @@ chmod -R u+w $RPM_BUILD_ROOT/*
make test
-%clean
-rm -rf $RPM_BUILD_ROOT
-
-
%files
-%defattr(-,root,root,-)
%doc Changes LICENSE README TODO
%{_bindir}/*
%{perl_vendorlib}/Devel/
@@ -61,6 +56,9 @@ rm -rf $RPM_BUILD_ROOT
%changelog
+* Wed Dec 11 2013 Jose Pedro Oliveira jpo at di.uminho.pt - 1.54-2
+- The test suite also needs the less command in the build root (F20+).
+
* Wed Dec 11 2013 Jose Pedro Oliveira jpo at di.uminho.pt - 1.54-1
- Update to 1.54.
- New build requirement: perl(Test::More).
--
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-pmtools/f19] (5 commits) ...The test suite also needs the less command in the build root.
Summary of changes: 7f9ed28... Perl 5.18 rebuild (*) 0b77434... - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass (*) 2e0ad0a... Update to version 1.30. (*) 7572746... Update to 1.54. (*) 086b402... The test suite also needs the less command in the build roo (*) (*) This commit already existed in another branch; no separate mail sent -- 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-pmtools/f20] (3 commits) ...The test suite also needs the less command in the build root.
Summary of changes: 2e0ad0a... Update to version 1.30. (*) 7572746... Update to 1.54. (*) 086b402... The test suite also needs the less command in the build roo (*) (*) This commit already existed in another branch; no separate mail sent -- 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-pmtools/f18] (6 commits) ...The test suite also needs the less command in the build root.
Summary of changes: 0a5c0ed... - Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass (*) 7f9ed28... Perl 5.18 rebuild (*) 0b77434... - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass (*) 2e0ad0a... Update to version 1.30. (*) 7572746... Update to 1.54. (*) 086b402... The test suite also needs the less command in the build roo (*) (*) This commit already existed in another branch; no separate mail sent -- 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-pmtools/el6] Update to version 1.54.
commit fd5371f8dd298a3354b219c02b45f1eac5f2269f
Author: Jose Pedro Oliveira j...@di.uminho.pt
Date: Wed Dec 11 15:47:20 2013 +
Update to version 1.54.
.gitignore|1 +
perl-pmtools.spec | 63 +++---
pmtools-1.01-pman2pmman.patch | 189 -
sources |2 +-
4 files changed, 54 insertions(+), 201 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 6349ed1..5e4994d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,2 @@
pmtools-1.10.tar.gz
+/pmtools-1.54.tar.gz
diff --git a/perl-pmtools.spec b/perl-pmtools.spec
index fd1dbe8..995f925 100644
--- a/perl-pmtools.spec
+++ b/perl-pmtools.spec
@@ -1,6 +1,6 @@
Name: perl-pmtools
-Version:1.10
-Release:3%{?dist}
+Version:1.54
+Release:2%{?dist}
Summary:A suite of small programs to help manage Perl modules
Group: Development/Libraries
@@ -10,8 +10,10 @@ Source:
http://www.cpan.org/authors/id/M/ML/MLFISHER/pmtools-%{version}.
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
+
BuildRequires: perl(ExtUtils::MakeMaker)
-Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+BuildRequires: perl(Test::More)
+BuildRequires: less
%description
This is pmtools -- a suite of small programs to help manage modules.
@@ -25,6 +27,7 @@ Tom Christiansen
%prep
%setup -q -n pmtools-%{version}
find . -type f -perm 755 | xargs %{__perl} -pi -e 's{^#!/usr/bin/env
perl}{#!%{__perl}}'
+chmod -c a-x Changes TODO lib/Devel/Loaded.pm
%build
@@ -33,7 +36,6 @@ 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 -type d -depth -exec rmdir {} 2/dev/null ';'
@@ -44,20 +46,59 @@ chmod -R u+w $RPM_BUILD_ROOT/*
make test
-%clean
-rm -rf $RPM_BUILD_ROOT
-
-
%files
-%defattr(-,root,root,-)
-%doc Changes README TODO
+%doc Changes LICENSE README TODO
%{_bindir}/*
%{perl_vendorlib}/Devel/
+%{perl_vendorlib}/pmtools.pm
%{_mandir}/man1/*.1*
%{_mandir}/man3/*.3*
%changelog
+* Wed Dec 11 2013 Jose Pedro Oliveira jpo at di.uminho.pt - 1.54-2
+- The test suite also needs the less command in the build root (F20+).
+
+* Wed Dec 11 2013 Jose Pedro Oliveira jpo at di.uminho.pt - 1.54-1
+- Update to 1.54.
+- New build requirement: perl(Test::More).
+
+* Tue Dec 10 2013 Jose Pedro Oliveira jpo at di.uminho.pt - 1.30-1
+- Update to 1.30.
+
+* Sun Aug 04 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.10-14
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
+
+* Wed Jul 17 2013 Petr Pisar ppi...@redhat.com - 1.10-13
+- Perl 5.18 rebuild
+
+* Thu Feb 14 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.10-12
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
+
+* Fri Jul 20 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.10-11
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild
+
+* Sun Jun 10 2012 Petr Pisar ppi...@redhat.com - 1.10-10
+- Perl 5.16 rebuild
+
+* Sat Jan 14 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.10-9
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild
+
+* Fri Jun 17 2011 Marcela Mašláňová mmasl...@redhat.com - 1.10-8
+- Perl mass rebuild
+
+* Wed Feb 09 2011 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.10-7
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild
+
+* Tue Dec 21 2010 Marcela Maslanova mmasl...@redhat.com - 1.10-6
+- 661697 rebuild for fixing problems with vendorach/lib
+
+* Tue May 04 2010 Marcela Maslanova mmasl...@redhat.com - 1.10-5
+- Mass rebuild with perl-5.12.0
+
+* Mon Dec 7 2009 Stepan Kasal ska...@redhat.com - 1.10-4
+- rebuild against perl 5.10.1
+
* Sun Jul 26 2009 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.10-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild
@@ -86,7 +127,7 @@ rm -rf $RPM_BUILD_ROOT
* Thu Dec 22 2005 Jose Pedro Oliveira jpo at di.uminho.pt - 1.00-3
- Dist tag.
-* Fri Apr 7 2005 Michael Schwendt mschwendt[AT]users.sf.net - 1.00-2
+* Thu Apr 7 2005 Michael Schwendt mschwendt[AT]users.sf.net - 1.00-2
- rebuilt
* Sun Feb 06 2005 Jose Pedro Oliveira jpo at di.uminho.pt - 1.00-1
diff --git a/sources b/sources
index 143d990..bfb5b00 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-3cb192b5b241037d6b701e6e26ef2425 pmtools-1.10.tar.gz
+1a83a0209f3fde110f65647a9741c442 pmtools-1.54.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
[Bug 1032571] perl-Net-Twitter-4.01000 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1032571 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version||perl-Net-Twitter-4.01000-1. ||fc19 Resolution|--- |ERRATA Last Closed||2013-12-11 21:53:21 --- Comment #4 from Fedora Update System upda...@fedoraproject.org --- perl-Net-Twitter-4.01000-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. -- 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=F5V7zhGEnFa=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 1037520] perl-Date-Manip-6.42 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1037520 --- Comment #4 from Fedora Update System upda...@fedoraproject.org --- perl-Date-Manip-6.42-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. -- 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=9ey2WGP3U7a=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 1037520] perl-Date-Manip-6.42 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1037520 --- Comment #5 from Fedora Update System upda...@fedoraproject.org --- perl-Date-Manip-6.42-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. -- 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=aXZiKKD2ima=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
[389-devel] please review: Ticket 47627 - changelog iteration should ignore cleaned rids when getting the minCSN
https://fedorahosted.org/389/ticket/47627 https://fedorahosted.org/389/attachment/ticket/47627/0001-Ticket-47627-changelog-iteration-should-ignore-clean.patch -- Mark Reynolds 389 Development Team Red Hat, Inc mreyno...@redhat.com -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
[389-devel] please review: Ticket 47601 - Plugin library path validation prevents intentional loading of out-of-tree modules
autogen.sh still needs to be run for this patch... https://fedorahosted.org/389/ticket/47601 https://fedorahosted.org/389/attachment/ticket/47601/0001-Ticket-47601-Plugin-library-path-validation-prevents.patch -- Mark Reynolds 389 Development Team Red Hat, Inc mreyno...@redhat.com -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
[389-devel] please review: Ticket 47617 - allow configuring changelog trim interval
https://fedorahosted.org/389/ticket/47617 https://fedorahosted.org/389/attachment/ticket/47617/0001-Ticket-47617-allow-configuring-changelog-trim-interv.patch -- Mark Reynolds 389 Development Team Red Hat, Inc mreyno...@redhat.com -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: [389-devel] Please review: [389 Project] #47606: replica init/bulk import errors should be more verbose
On 12/11/2013 7:08 PM, Noriko Hosoi wrote: https://fedorahosted.org/389/ticket/47606 https://fedorahosted.org/389/attachment/ticket/47606/0001-Ticket-47606-replica-init-bulk-import-errors-should-.patch Looks good to me. Pitty about the struct definition accessibility -- presumably that's an openldap-devel limitation... The only suggestion I'd have would be to put the length extraction code in a function, in another source file, to keep connection.c slightly cleaner. -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: Python 3.4, ensurepip and wheels
On 12/12/2013 01:18 AM, Bohuslav Kabrda wrote: Well yeah, my point is that there is no upstream-acceptable way other than checking the file hashes by ensurepip, is there? If I wouldn't want to check file hashes, I'd have to query RPM for release - or is there some other way you're thinking of? I think doing it initially as a downstream only change where you query RPM will work for now (perhaps by patching the way pip handles the case where ENSUREPIP_OPTIONS is set?). By the time this approach is posted upstream, then PEP 426/440 will hopefully by Final and we can just use the metadata version field directly rather than needing to grab the release increment from the RPM repo. (I think this situation provides a good practical use case for why it's important to standardise this feature upstream, too). Cheers, Nick. -- Nick Coghlan Red Hat Hosted Shared Services Software Engineering Development, Brisbane Testing Solutions Team Lead Beaker Development Lead (http://beaker-project.org/) ___ python-devel mailing list python-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/python-devel
[AutoQA] #446: [rpmguard] preun/postun scripts change
#446: [rpmguard] preun/postun scripts change --+-- Reporter: kparal | Owner: Type: enhancement | Status: new Priority: minor| Milestone: Rpmguard Component: tests| Keywords: Blocked By: | Blocking: --+-- It would be nice to add notifications about preun/postun scripts change. -- Ticket URL: https://fedorahosted.org/autoqa/ticket/446 AutoQA http://autoqa.fedorahosted.org Automated QA project ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
[Maniphest] [Closed] T26: Display all users that are listed in needinfo flag
mkrizek closed this task as Resolved. mkrizek added a comment. Fixed in develop [[ https://git.fedorahosted.org/cgit/blockerbugs.git/commit/?h=developid=0618ae3bc89431f9d00a3cc103b19fc0376697ed | 0618ae3bc89431f9d00a3cc103b19fc0376697ed ]] TASK DETAIL https://phab.qadevel.cloud.fedoraproject.org/T26 To: mkrizek Cc: qa-devel, mkrizek ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: Review Request 57: Multiple builds fixing a bug show confusing status label
On Dec. 10, 2013, 5:58 p.m., Tim Flink wrote: blockerbugs/__init__.py, line 162 http://reviewboard-tflink.rhcloud.com/r/57/diff/1/?file=1605#file1605line162 Bah, have we really been running this whole time with unclosed span tags on the update status labels? Yes :) On Dec. 10, 2013, 5:58 p.m., Tim Flink wrote: blockerbugs/models/update.py, line 55 http://reviewboard-tflink.rhcloud.com/r/57/diff/1/?file=1607#file1607line55 Why is this sort order change an improvement? If an older update is pending while a newer update is stable, we'd want to show the newer update But wouldn't the older update be marked as obsolete? - Martin --- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/57/#review118 --- On Dec. 10, 2013, 3:54 p.m., Martin Krizek wrote: --- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/57/ --- (Updated Dec. 10, 2013, 3:54 p.m.) Review request for blockerbugs. Bugs: 438 https://fedorahosted.org/fedora-qa/ticket/438 Repository: blockerbugs Description --- commit 911781af9cc06e27c0a8580f07f7673c90e7329d Author: Martin Krizek mkri...@redhat.com Date: Tue Dec 10 16:28:52 2013 +0100 Sort updates by (status.desc(), pending.desc()) This way an update label is correctly set when multiple updates fix a bug. The label is chosen by the following order (the lowest one): pending testing testing pending stable stable Fixes: #438 Note: the rest of the issues with displaying label is handled outside this ticket in https://phab.qadevel.cloud.fedoraproject.org/T21 Diffs - blockerbugs/models/update.py 89c083da5c91558d4dead118c67e4a1138b8cae1 blockerbugs/controllers/main.py 1795ed1d717bb85e0f3d9e7e7008d68c2aae36d8 blockerbugs/__init__.py dcf6c5aadb24e6d86e95d5bb3d608b81721de47f Diff: http://reviewboard-tflink.rhcloud.com/r/57/diff/ Testing --- Sorting seems to be working as expected. Thanks, Martin Krizek ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: Review Request 57: Multiple builds fixing a bug show confusing status label
On Dec. 10, 2013, 5:58 p.m., Tim Flink wrote: blockerbugs/models/update.py, line 55 http://reviewboard-tflink.rhcloud.com/r/57/diff/1/?file=1607#file1607line55 Why is this sort order change an improvement? If an older update is pending while a newer update is stable, we'd want to show the newer update Martin Krizek wrote: But wouldn't the older update be marked as obsolete? Tim Flink wrote: It should be but for example, if you look at the tracking app right now, there are 2 anaconda/blivet updates - one of which has been deleted in bodhi but still shows up. This issue was supposed to be fixed but obviously, it's not. Filed as https://phab.qadevel.cloud.fedoraproject.org/T27 I think that the problem of phantom updates are the root cause of the problem as reported, but I'll ask in bug to be sure. Tim Flink wrote: After re-reading the bug, I stand corrected. That was a completely different issue than I was thinking about in my head. I don't like sorting on string fields by default but I also don't see much of a way around it unless we changed the schema to use status enums instead of strings. Go ahead and push to develop. We might want to look into changing the update status field to an enum but that's well outside the scope of this fix. I know. This is just a part of the fix, the rest will be in https://phab.qadevel.cloud.fedoraproject.org/T21 as I mentioned in the fix description. Should have probably done it in one review, sorry for confusion. - Martin --- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/57/#review118 --- On Dec. 10, 2013, 3:54 p.m., Martin Krizek wrote: --- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/57/ --- (Updated Dec. 10, 2013, 3:54 p.m.) Review request for blockerbugs. Bugs: 438 https://fedorahosted.org/fedora-qa/ticket/438 Repository: blockerbugs Description --- commit 911781af9cc06e27c0a8580f07f7673c90e7329d Author: Martin Krizek mkri...@redhat.com Date: Tue Dec 10 16:28:52 2013 +0100 Sort updates by (status.desc(), pending.desc()) This way an update label is correctly set when multiple updates fix a bug. The label is chosen by the following order (the lowest one): pending testing testing pending stable stable Fixes: #438 Note: the rest of the issues with displaying label is handled outside this ticket in https://phab.qadevel.cloud.fedoraproject.org/T21 Diffs - blockerbugs/models/update.py 89c083da5c91558d4dead118c67e4a1138b8cae1 blockerbugs/controllers/main.py 1795ed1d717bb85e0f3d9e7e7008d68c2aae36d8 blockerbugs/__init__.py dcf6c5aadb24e6d86e95d5bb3d608b81721de47f Diff: http://reviewboard-tflink.rhcloud.com/r/57/diff/ Testing --- Sorting seems to be working as expected. Thanks, Martin Krizek ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
[Maniphest] [Closed] T27: Irrelevant phantom updates are not purged from active update list
tflink closed this task as Invalid. tflink claimed this task. tflink added a comment. This is a duplicate of T21 - closing. TASK DETAIL https://phab.qadevel.cloud.fedoraproject.org/T27 To: tflink Cc: qa-devel, tflink ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
[Maniphest] [Changed CC] T21: Do not display obsolete and deleted updates
tflink added a subscriber: tflink. tflink added a comment. T27 was filed as a duplicate TASK DETAIL https://phab.qadevel.cloud.fedoraproject.org/T21 To: mkrizek, tflink Cc: qa-devel, mkrizek, tflink ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Fedora 20 Final Go/No-Go Meeting #2, Thursday, December 12 @ 17:00 UTC
Join us on irc.freenode.net in #fedora-meeting-2 for this important meeting, wherein we shall determine the readiness of the Fedora 20. Thursday, December 12, 2013 17:00 UTC (12 PM EST, 9 AM PST, 18:00 CET) Before each public release Development, QA and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the Go/No-Go Meeting. Verifying that the Release criteria are met is the responsibility of the QA Team. For more details about this meeting see: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime, keep an eye on the Fedora 20 Final Blocker list: http://qa.fedoraproject.org/blockerbugs/milestone/20/final/buglist This is the second attempt to release final Fedora 20 and we're really very close to holidays. Please, help us with the release by working on the bugs assigned to you - the very, very deadline to create and validate RC on time is Wednesday... Thanks everyone! Jaroslav ___ devel-announce mailing list devel-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce
