EPEL Fedora 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 583 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5620/bugzilla-3.4.14-2.el6 98 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11274/ssmtp-2.61-21.el6 40 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11865/quassel-0.9.1-1.el6 23 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12025/seamonkey-2.22-1.el6 18 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12064/drupal7-context-3.1-1.el6 13 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12079/bip-0.8.9-1.el6 12 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12040/python-djblets-0.7.23-1.el6,ReviewBoard-1.7.18-1.el6 12 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12102/moodle-2.4.7-1.el6 6 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12156/varnish-2.1.5-5.el6 6 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12154/mediawiki119-1.19.9-1.el6 3 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12171/drupal7-7.24-1.el6 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12199/lynis-1.3.5-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing fedora-gnat-project-common-3.8-1.el6 glacier-cli-0-8.20131113gite8a2536.el6 glite-lb-ws-interface-4.0.7-1.el6 javasqlite-20131124-1.el6 librcc-0.2.12-3.el6 lynis-1.3.5-1.el6 php-pecl-http-2.0.1-1.el6 php-pecl-raphf-1.0.4-1.el6 python-gevent-0.13.8-3.el6 Details about builds: fedora-gnat-project-common-3.8-1.el6 (FEDORA-EPEL-2013-12205) Files shared by Ada libraries Update Information: This upgrade brings support for Comfignat 1.2 to EPEL 6, and inclusion of runpaths can be controlled with GNAT_add_rpath. Additionally, some compiler flags have been added to prevent dangerous suppression of important checks and avoid unnecessary build failures, and the mapping from architectures to Libdir values has been corrected and expanded. ChangeLog: * Tue Nov 26 2013 Björn Persson bjorn@rombobjörn.se - 3.8-1 - Upgraded to version 3.8 with support for Comfignat 1.2. glacier-cli-0-8.20131113gite8a2536.el6 (FEDORA-EPEL-2013-12198) Command-line interface to Amazon Glacier Update Information: new package new package References: [ 1 ] Bug #1031019 - Review Request: glacier-cli - Command-line interface to Amazon Glacier https://bugzilla.redhat.com/show_bug.cgi?id=1031019 glite-lb-ws-interface-4.0.7-1.el6 (FEDORA-EPEL-2013-12206) gLite Logging and Bookkeeping web service interface Update Information: glite-lb-ws-interface with the LB web service interface specification (LB.wsdl and LBTypes.wsdl). References: [ 1 ] Bug #1003301 - Review Request: glite-lb-ws-interface - gLite Logging and Bookkeeping web service interface https://bugzilla.redhat.com/show_bug.cgi?id=1003301 javasqlite-20131124-1.el6 (FEDORA-EPEL-2013-12201) SQLite Java Wrapper/JDBC Driver Update Information: Update to version 20131124. http://www.ch-werner.de/javasqlite/ChangeLog ChangeLog: * Tue Nov 26 2013 Ville Skyttä ville.sky...@iki.fi - 20131124-1 - Update to 20131124. * Fri Oct 25 2013 Ville Skyttä ville.sky...@iki.fi - 20130214-3 - Depend on headless java where available. - Drop aarch64 specfile cruft, rely on %configure (#951442). * Sat Aug 3 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org - 20130214-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild References: [ 1 ] Bug #1034075 - javasqlite-20131124 is available https://bugzilla.redhat.com/show_bug.cgi?id=1034075
Agenda for today's Env-and-Stacks WG meeting (2013-11-26)
WG meeting will be today at 13:00 UTC in #fedora-meeting on Freenode. == Next Steps == - PRD - based on discussion on env-and-stacks mailing list == Open Floor == -- 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: orphan/retire gradle
25.11.2013 22:45, Mikolaj Izdebski wrote: W dniu 25.11.2013 18:16, Pavel Alexeev pisze: How groovy will be in Fedora? Is it mean it also will be retired soon? No, there are no plans of retiring groovy. (Groovy can be either with Ant or Gradle. Fedora uses the first option.) Thanks, Mikolaj. But IIRC groovy = 2.0 switched to gradle build only? Have not you either plans to update it? -- 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: debuginfo packages available in updates later than regular packages.
On 26.11.2013 03:55, Kevin Kofler wrote: Jan Kratochvil wrote: There were multiple Bugs suggesting the same, they are linked together for example from this one from 2005. But it all got WONTFIXed: Debug info RPMs do not require exact maching binary rpm https://bugzilla.redhat.com/show_bug.cgi?id=151598 The problem with those dependencies is that -debuginfo covers all the subpackages, so which one should it require? All of them? That's more often than not NOT what I want. (E.g., do we really want to force everyone to install gcc-* just because ABRT/DrKonqi/whatever wants to install the (usually unneeded) debugging information for libgcc? Getting gcc-debuginfo dragged in is bad enough!) Here is a quick and dirty spec implementing the idea I described: [1]. From what I can see it behaves correctly with any combination of packages and subpackages installed. Am I missing something? Sandro [1] http://smani.fedorapeople.org/somepackage.spec -- 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: debuginfo packages available in updates later than regular packages.
Le Mar 26 novembre 2013 03:55, Kevin Kofler a écrit : Jan Kratochvil wrote: There were multiple Bugs suggesting the same, they are linked together for example from this one from 2005. But it all got WONTFIXed: Debug info RPMs do not require exact maching binary rpm https://bugzilla.redhat.com/show_bug.cgi?id=151598 The problem with those dependencies is that -debuginfo covers all the subpackages, so which one should it require? All of them? That's more often than not NOT what I want. Just conflict with all subpackages that do not match the exact debuginfo version Regards, -- Nicolas Mailhot -- 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: debuginfo packages available in updates later than regular packages.
Isn't it should be implemented implicitly in RPM? -- 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 Workstation Desktop Environment Concept
Alex GS wrote: I'm a computer science major interested in Linux software engineering and just beginning to learn programming so I'm use-case #1 and #2. Currently out of all my peers I'm the only one using Linux as far as I know. Most students and developers even those working on Linux oriented projects either use Mac OS out of personal preference or Windows because it's the default in most organizations and institutions of learning. If users cannot naturally and effortlessly migrate to the Fedora Workstation from Mac or Windows and find a normal environment they're used to, the product will fail. So far, I follow you… The problem is that the vast majority of Linux desktops don't meet the design standards set by the established commercial leaders. Currently my favorite desktop environment is Gnome Shell and my second favorite is Mate. Gnome Shell is almost there, nearly meets the modern Mac OS level of quality end-users expect, and has an excellent technical foundation, it just needs some simple layout modifications and changes to menu behavior. … but here, I just cannot disagree more. Maybe as a curious student, you are more open than average to trying out new design paradigms, but what most users of other operating systems expect is the same type of interface they have been using all this time. And GNOME Shell does not resemble ANY of the proprietary desktop operating systems, except maybe Window$ 8 (which will take a few years to get into people's mindshare, assuming they can get used to it at all). As for MATE, while it might make sense from an interface point of view, I don't see why it would be more professional than other alternatives such as KDE Plasma Desktop, Xfce etc. It is, after all, an understaffed fork of an unmaintained old version of GNOME. Still, even MATE would be a better default than GNOME Shell! I've put together a *.pdf document outlining my suggestions and ideas outlining my suggestions in this regard, see the attached link. Hopefully this can be useful to the working group and a provide a starting point for a discussion about the default graphical user interface for the Workstation product. Document Link: http://goo.gl/0IzNgK *this is a Google Documents link Working with a proprietary office suite in a Free Software community is not that great an idea. (Though at least you didn't write it directly in Google Documents, and thus it lets me download the original PDF through File/Download.) Don't you have some webspace you can upload files to directly? Or I guess you could even have attached it to the mail, though large attachments on mailing lists are generally frowned upon. Also note that we are all using Free Software and so we can all open ODT files, you don't have to export them to hard-to-edit PDFs. (The PDF's properties say it has been generated with LibreOffice 4.1.) As for the contents of the document, your 2 suggestions start from the premise that GNOME Shell is to be used, so I'm the wrong person to comment on those. 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: python-django update to Django-1.6
On 11/25/2013 06:51 PM, Simo Sorce wrote: On Mon, 2013-11-25 at 11:24 -0500, Stephen Gallagher wrote: This is kind of why I keep coming back to: Why do we have python-django at all? I don't really see any reason why we shouldn't kill off the python-django package and just carry 'python-django15' and 'python-django16' packages with a conflict. The number of incompatibilities between releases is such that I don't think we really want to be forcing upgrades on other packages at all. We should just be carrying whichever two versions are supported by upstream at any given time. Upstream is very good about maintaining bugfixes and security fixes in both supported streams. +1 by changing version the current way, the only ting we can guarantee is a lot of broken packages all the time. I see your points here and thank you for the feedback! From my experience, it was just a pain to have python-django14 and python-django[1]. Introducing one or two other packages python-django15 and python-django16 will make it more difficult for users to update django. How should packages require Django? Just require python-django? Sadly, yum can not handle that properly[1]. When dropping python-django as provides/requires, we'd have the situation packages will require a specific version. That's rather unfortunate, because combination of packages requiring some other python-django-foo package might require a different django version. At least for OpenStack Horizon I can say, we're up to fix compatibility issues with Django-1.6 upstream. Matthias [1] https://bugzilla.redhat.com/show_bug.cgi?id=978647 -- 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: 20131126 changes
Compose started at Tue Nov 26 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) [gnome-do-plugins] gnome-do-plugins-thunderbird-0.8.4-14.fc20.armv7hl requires thunderbird [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 [mozilla-firetray] mozilla-firetray-thunderbird-0.3.6-0.5.143svn.fc18.1.armv7hl requires thunderbird = 0:11 [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 [perl-Language-Expr] perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) [pure] pure-doc-0.57-4.fc20.noarch requires pure = 0:0.57-4.fc20 [python-tag] python-tag-2013.1-1.fc20.armv7hl requires libboost_python.so.1.53.0 [rootplot] rootplot-2.2.1-7.fc19.noarch requires root-python [rubygem-audited-activerecord] rubygem-audited-activerecord-3.0.0-3.fc19.noarch requires rubygem(activerecord) 0:4 [scilab] scilab-doc-5.4.1-4.fc20.noarch requires scilab = 0:5.4.1-4.fc20 scilab-tests-5.4.1-4.fc20.noarch requires scilab = 0:5.4.1-4.fc20 [spacewalk-admin] spacewalk-admin-2.0.1-2.fc20.noarch requires spacewalk-base spacewalk-admin-2.0.1-2.fc20.noarch requires perl(RHN::SatelliteCert) [spring-maps-default] spring-maps-default-0.1-11.fc20.noarch requires spring [springlobby] springlobby-0.169-5.fc20.armv7hl requires spring [subsurface] subsurface-3.1.1-2.fc20.armv7hl requires libosmgpsmap.so.2 [syntastic] syntastic-d-2.3.0-11.20120917git72856e6.fc20.noarch requires ldc [tango] tango-doc-2-12.20120821git7b92443.fc19.noarch requires tango-devel = 0:2-12.20120821git7b92443.fc19 tango-geany-tags-2-12.20120821git7b92443.fc19.noarch requires tango = 0:2-12.20120821git7b92443.fc19 Broken deps for i386 -- [blueman] blueman-1.23-7.fc20.i686 requires obex-data-server = 0:0.4.3 blueman-1.23-7.fc20.i686 requires gvfs-obexftp [derelict] derelict-tcod-3-20.20130626gite70c293.fc20.i686 requires tcod derelict-tcod-devel-3-20.20130626gite70c293.fc20.i686 requires tcod [fts] fts-server-3.1.1-1.fc20.i686 requires libactivemq-cpp.so.14 [ghc-hjsmin] ghc-hjsmin-0.1.4.3-2.fc20.i686 requires
Re: debuginfo packages available in updates later than regular packages.
On 26.11.2013 11:50, Nicolas Mailhot wrote: Le Mar 26 novembre 2013 03:55, Kevin Kofler a écrit : Jan Kratochvil wrote: There were multiple Bugs suggesting the same, they are linked together for example from this one from 2005. But it all got WONTFIXed: Debug info RPMs do not require exact maching binary rpm https://bugzilla.redhat.com/show_bug.cgi?id=151598 The problem with those dependencies is that -debuginfo covers all the subpackages, so which one should it require? All of them? That's more often than not NOT what I want. Just conflict with all subpackages that do not match the exact debuginfo version Regards, Is there some rpm macro magic to list all the (sub)packages defined in a spec? Sandro -- 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: orphan/retire gradle
Il 26/11/2013 11:34, Pavel Alexeev ha scritto: 25.11.2013 22:45, Mikolaj Izdebski wrote: W dniu 25.11.2013 18:16, Pavel Alexeev pisze: How groovy will be in Fedora? Is it mean it also will be retired soon? No, there are no plans of retiring groovy. (Groovy can be either with Ant or Gradle. Fedora uses the first option.) Thanks, Mikolaj. But IIRC groovy = 2.0 switched to gradle build only? yes Have not you either plans to update it? dont forget this problem groovy-all 1.8.x asm3 groovy-all 2.x asm4 gradle use groovy-all 1.8.x ( with asm3) and asm4 attachment: puntogil.vcf-- 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: debuginfo packages available in updates later than regular packages.
On 26.11.2013 11:50, Christopher Meng wrote: Isn't it should be implemented implicitly in RPM? It is just a proof of concept/idea. Will hardly be implemented like this, if something similar is going to be implemented. Sandro -- 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: F21 System Wide Change: Headless Java
On 11/21/2013 08:57 PM, Miloslav Trmač wrote: These two steps make it rather non-simple; one would also determine which parts of the code base have not been exercised. If the test suite is so weak that it doesn't cover such basic issues, you will have trouble with *any* change, not just this one. -- Florian Weimer / Red Hat Product Security Team -- 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: python-django update to Django-1.6
On Tue, 2013-11-26 at 12:02 +0100, Matthias Runge wrote: On 11/25/2013 06:51 PM, Simo Sorce wrote: On Mon, 2013-11-25 at 11:24 -0500, Stephen Gallagher wrote: This is kind of why I keep coming back to: Why do we have python-django at all? I don't really see any reason why we shouldn't kill off the python-django package and just carry 'python-django15' and 'python-django16' packages with a conflict. The number of incompatibilities between releases is such that I don't think we really want to be forcing upgrades on other packages at all. We should just be carrying whichever two versions are supported by upstream at any given time. Upstream is very good about maintaining bugfixes and security fixes in both supported streams. +1 by changing version the current way, the only ting we can guarantee is a lot of broken packages all the time. I see your points here and thank you for the feedback! From my experience, it was just a pain to have python-django14 and python-django[1]. Introducing one or two other packages python-django15 and python-django16 will make it more difficult for users to update django. How should packages require Django? Just require python-django? Sadly, yum can not handle that properly[1]. When dropping python-django as provides/requires, we'd have the situation packages will require a specific version. That's rather unfortunate, because combination of packages requiring some other python-django-foo package might require a different django version. At least for OpenStack Horizon I can say, we're up to fix compatibility issues with Django-1.6 upstream. Matthias [1] https://bugzilla.redhat.com/show_bug.cgi?id=978647 Packages should require the latest version they work with. If some package is really awesome and supports multiple versions I guess it could support a generic python-django. It's ok if 2 packages become incompatible this way, they wouldn't work anyway with the wrong version of django. Simo. -- Simo Sorce * Red Hat, Inc * New York -- 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: python-django update to Django-1.6
On Mon, Nov 25, 2013 at 09:07:55AM +0100, Matthias Runge wrote:
Hey,
recently, I saw a few requests to update python-django to Django-1.6,
the corresponding bug is [1].
As there are quite a few changes, I'd expect this update to be harmful,
at least
- python-django-openstack-auth
- openstack-dashboard
will break, and won't even build any more (because they also execute
sanity checks during build).
So, the current plan is, to fix both packages upstream and then to
update python-django to Django 1.6 in rawhide. I'd expect this to happen
within the next two weeks and I'd update python-django to Django-1.6
around Dec 16th.
Because of bad timing, we won't have Django-1.6 in f20.
Just an idea, but what about providing Django 1.6 via copr for F{20,19}?
That might also help testing current apps against the new Django.
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: F21 Self Contained Change: Replace Bacula with Bareos
Hello, On 16 November 2013 02:09, Kevin Kofler kevin.kof...@chello.at wrote: Simone Caronni wrote: Bareos is currently in standby following some legal issues: https://fedoraproject.org/wiki/Forbidden_items#Bareos Can we know what the issues are? Switching would look like a no-brainer (old unmaintained crippleware vs. new community fork), but of course, if there are legal issues with the fork… :-( sorry for the delay, but some news have been posted today regarding this issue: http://www.mail-archive.com/bacula-users@lists.sourceforge.net/msg57308.html https://www.bareos.org/en/faq/items/copyright_bacula_bareos.html Regards, --Simone -- You cannot discover new oceans unless you have the courage to lose sight of the shore (R. W. Emerson). http://xkcd.com/229/ http://negativo17.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: python-django update to Django-1.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/26/2013 08:34 AM, Simo Sorce wrote: On Tue, 2013-11-26 at 12:02 +0100, Matthias Runge wrote: On 11/25/2013 06:51 PM, Simo Sorce wrote: On Mon, 2013-11-25 at 11:24 -0500, Stephen Gallagher wrote: This is kind of why I keep coming back to: Why do we have python-django at all? I don't really see any reason why we shouldn't kill off the python-django package and just carry 'python-django15' and 'python-django16' packages with a conflict. The number of incompatibilities between releases is such that I don't think we really want to be forcing upgrades on other packages at all. We should just be carrying whichever two versions are supported by upstream at any given time. Upstream is very good about maintaining bugfixes and security fixes in both supported streams. +1 by changing version the current way, the only ting we can guarantee is a lot of broken packages all the time. I see your points here and thank you for the feedback! From my experience, it was just a pain to have python-django14 and python-django[1]. Introducing one or two other packages python-django15 and python-django16 will make it more difficult for users to update django. How should packages require Django? Just require python-django? Sadly, yum can not handle that properly[1]. When dropping python-django as provides/requires, we'd have the situation packages will require a specific version. That's rather unfortunate, because combination of packages requiring some other python-django-foo package might require a different django version. At least for OpenStack Horizon I can say, we're up to fix compatibility issues with Django-1.6 upstream. Matthias [1] https://bugzilla.redhat.com/show_bug.cgi?id=978647 Packages should require the latest version they work with. If some package is really awesome and supports multiple versions I guess it could support a generic python-django. It's ok if 2 packages become incompatible this way, they wouldn't work anyway with the wrong version of django. I think Simo has the right idea here. We should drop the standard python-django package at this point and instead have python-django15 and python-django16. Each of those packages should add a virtual Provides: and Obsoletes: for python-django. Existing packages with a non-strict version will then default to upgrading to the absolute latest version (python-django16). If that's not acceptable to their project, they'll need to release a new update with 'Requires: python-django15' and things should go back to normal. In the future, if they update so they work with both currently-available versions, they can go back to 'Requires: python-django' and will then work with whichever version the user has on the system (such as for another project). Yes, it slightly increases the packager work, but it should give a better experience for the user... to a point. Since Django 1.5 and 1.6 cannot presently co-exist on the system, they'll need to have an explicit Conflicts:. This does mean that users will have an issue if they end up pulling Django 1.6 as part of an upgrade and then try to install a package that Requires: python-django15. We can't automatically remove python-django16, so the user will have to know to do this manually. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKUqVMACgkQeiVVYja6o6MizwCcCCJfRhc7M7h/pTWwwtVXKZ3d 7EMAn2fA3ktfExNZZZwp1fX2RleWK7rJ =6Nfr -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
[Maniphest] [Commented On] T16: generate specially crafted rpms to induce failure and passing in depcheck
tflink added a comment. yeah, one of them was supposed to be for upgradepath. Can you change the title of one of them depending on which task you were intending to take? TASK DETAIL https://phab.qadevel.cloud.fedoraproject.org/T16 To: jskladan, tflink Cc: qa-devel, tflink, jskladan ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Meeting minutes - today's Env-and-Stacks WG meeting (2013-11-26)
= #fedora-meeting: (2013-11-26) = Meeting started by mmaslano at 13:00:25 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-11-26/environment_and_stacks.2013-11-26-13.00.log.html . Meeting summary --- * init process (mmaslano, 13:01:15) * http://piratepad.net/PwUiH4MEPR (mmaslano, 13:09:53) * tools for setting up development environments/more automation for packaging/providing stacks (mmaslano, 13:19:58) * LINK: http://ambre.pingoured.fr/cgit/review_srv.git/ (pingou, 13:41:51) * So, my attempt at summarization: one idea regarding the automatic packaging is to help existing maintainers see the automatically updated spec file and the generated rpm, so they have less work updating the packages, and to enable the eager users to use them AS IS (mmaslano, 13:48:49) * the other idea I saw was: The other idea is to enable easier/quicker packaging of dependent RPM files by generating spec files for the packager automatically (mmaslano, 13:48:58) Meeting ended at 14:00:03 UTC. Action Items Action Items, by person --- * **UNASSIGNED** * (none) People Present (lines said) --- * mmaslano (40) * juhp_ (36) * tjanez (35) * pingou (30) * sochotni (18) * hhorak (6) * samkottler (4) * zodbot (4) * bkabrda (3) * pkovar (1) * abadger1999 (0) * juhp (0) * handsome_pirate (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot 13:00:25 mmaslano #startmeeting (2013-11-26) 13:00:25 zodbot Meeting started Tue Nov 26 13:00:25 2013 UTC. The chair is mmaslano. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:25 zodbot Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:00:47 mmaslano #meetingname Environment and Stacks 13:00:47 zodbot The meeting name has been set to 'environment_and_stacks' 13:01:03 mmaslano #chair abadger1999 pkovar tjanez samkottler bkabrda handsome_pirate hhorak juhp 13:01:03 zodbot Current chairs: abadger1999 bkabrda handsome_pirate hhorak juhp mmaslano pkovar samkottler tjanez 13:01:15 mmaslano #topic init process 13:01:21 mmaslano hi guys 13:01:29 tjanez hi 13:01:40 bkabrda hey 13:01:49 hhorak Hi all 13:02:29 juhp_ hi 13:06:25 mmaslano so, do we continue discussion from last week? 13:06:36 mmaslano I saw lot of ideas what we should be doing on mailinglist 13:06:48 mmaslano but I guess we need higher level ideas... 13:07:10 juhp_ yes 13:08:14 tjanez mmaslano: I agree that we should maybe try to define what our WG in a more general way 13:08:24 juhp_ should we try to collect ideas somewhere and then try to extract higher level goals from there perhaps? 13:08:45 mmaslano tjanez: definitely 13:09:44 tjanez juhp_: the piratepad last week was an attempt 13:09:53 mmaslano #info http://piratepad.net/PwUiH4MEPR 13:09:59 tjanez juhp_: It's been copied to https://fedoraproject.org/wiki/User:Toshio/Env_and_Stacks_Charter_Brainstorming 13:10:01 mmaslano we can continue there 13:10:31 hhorak having in mind concrete ideas from mailing list, we can ask WHY we want to do it and we should get more general ideas 13:10:59 juhp_ tjanez, thanks - I just opened the pad 13:12:02 juhp_ it looks more formal than what I had in mind at this stage but good 13:12:49 mmaslano it should be shorter 13:12:57 * pkovar is late 13:13:36 tjanez one of the high-level goals which comes to mind is to enable inclusion of all (legally acceptable) stacks in Fedora, which are not possible in today's Fedora landscape (policies, guidelines, tools, ...) 13:14:07 tjanez I'd put it in the pad, however, I don't know where to put it 13:15:15 juhp_ tjanez, yes 13:15:51 juhp_ right that is why I would prefer a more free-form wiki page for branch-storming 13:16:12 sochotni juhp_: brainstorming? 13:16:21 juhp_ ah yes thanks ;) 13:16:24 juhp_ :) 13:16:29 juhp_ lol 13:17:26 tjanez Another thing we should do is define the terms environment and stacks 13:17:32 juhp_ sochotni, also agree with your idea of a package review app - that seems totally needed - dunno if it is really in the scope of this WG per se 13:17:54 sochotni juhp_: it's probably more in line with core fedora infra 13:17:58 mmaslano tjanez: personally, I don't are what is stack and what is environment 13:17:59 juhp_ yes 13:17:59 sochotni i.e. generic tooling 13:18:24 juhp_ could we just be the Stacks WG? :) 13:18:32 mmaslano sure :) 13:19:01 juhp_ seems okay to me too 13:19:36 bkabrda so my high-level proposal: tools for setting up development environments/more automation for packaging/providing stacks (meaning python2/python3, ruby/jruby) 13:19:36 sochotni I agree it would be less confusing 13:19:40 juhp_ maybe Env is supposed to imply more than Stacks? shrug/ 13:19:47 mmaslano maybe 13:19:58 mmaslano #topic tools for setting up development environments/more automation for
Re: python-django update to Django-1.6
On Tue, 2013-11-26 at 08:59 -0500, Stephen Gallagher wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/26/2013 08:34 AM, Simo Sorce wrote: On Tue, 2013-11-26 at 12:02 +0100, Matthias Runge wrote: On 11/25/2013 06:51 PM, Simo Sorce wrote: On Mon, 2013-11-25 at 11:24 -0500, Stephen Gallagher wrote: This is kind of why I keep coming back to: Why do we have python-django at all? I don't really see any reason why we shouldn't kill off the python-django package and just carry 'python-django15' and 'python-django16' packages with a conflict. The number of incompatibilities between releases is such that I don't think we really want to be forcing upgrades on other packages at all. We should just be carrying whichever two versions are supported by upstream at any given time. Upstream is very good about maintaining bugfixes and security fixes in both supported streams. +1 by changing version the current way, the only ting we can guarantee is a lot of broken packages all the time. I see your points here and thank you for the feedback! From my experience, it was just a pain to have python-django14 and python-django[1]. Introducing one or two other packages python-django15 and python-django16 will make it more difficult for users to update django. How should packages require Django? Just require python-django? Sadly, yum can not handle that properly[1]. When dropping python-django as provides/requires, we'd have the situation packages will require a specific version. That's rather unfortunate, because combination of packages requiring some other python-django-foo package might require a different django version. At least for OpenStack Horizon I can say, we're up to fix compatibility issues with Django-1.6 upstream. Matthias [1] https://bugzilla.redhat.com/show_bug.cgi?id=978647 Packages should require the latest version they work with. If some package is really awesome and supports multiple versions I guess it could support a generic python-django. It's ok if 2 packages become incompatible this way, they wouldn't work anyway with the wrong version of django. I think Simo has the right idea here. We should drop the standard python-django package at this point and instead have python-django15 and python-django16. Each of those packages should add a virtual Provides: and Obsoletes: for python-django. Existing packages with a non-strict version will then default to upgrading to the absolute latest version (python-django16). If that's not acceptable to their project, they'll need to release a new update with 'Requires: python-django15' and things should go back to normal. In the future, if they update so they work with both currently-available versions, they can go back to 'Requires: python-django' and will then work with whichever version the user has on the system (such as for another project). Yes, it slightly increases the packager work, but it should give a better experience for the user... to a point. Since Django 1.5 and 1.6 cannot presently co-exist on the system, they'll need to have an explicit Conflicts:. This does mean that users will have an issue if they end up pulling Django 1.6 as part of an upgrade and then try to install a package that Requires: python-django15. We can't automatically remove python-django16, so the user will have to know to do this manually. One issue to resolve is how to upgrade to the next version if you have python-django15 and F22 has python-django16 and python-django17, perhaps some clever way of making python-django16 obsolete (instead of conflict) python-django15 once 1.5 is pushed out of the new distro version ? Simo. -- Simo Sorce * Red Hat, Inc * New York -- 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
Dne 24.11.2013 00:34, Dennis Gilmore napsal(a): There is pros and cons of each. Agreed. And therefore forcing someone to use one of them or cricitice someone for having Fedora project on Github is something I don't like. Unless it's a proper policy and if such policy is proposed I would be against it. -- 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
[Base] Release cycle discussion for Fedora products and specifically Fedora Base and how they interact/align
Hi everyone. As i've been having a few discussions myself and following several of them as well as plans about release cycles in the different WGs over the past weeks and after FESCO discussed this in during their meetings and in a FESCO ticket[1] i get the feeling that we should be discussing this not in committees only but on a broader scale across all committees and WGs. The FESCO ticket comes to the following result: 'If working groups want to use different cycles, they should provide us with what they want to do with rationale along with the PRD. They should be aware that even if we can okay the plan, it is unlikely to be implementable for one or more releases. Please do not make your PRD depend on an alternate release lifecycle.' Josh Boyer also started a very great discussion about this specifically for the kernel on the Fedora kernel mailing list and how he would like to go forward with the kernel itself[2]. A very informative and deep analysis of the options and the impacts of different alternatives as well. Stephen Gallagher did the same for the Server WG[3] with lots of good input and feedback about the it in that thread as well. What i'd like to do here now is to collect all information of every WG about how they envision their releases to work (generally), what release cadence they expect and what life time they expect for each of their products and last but certainly not least, how they plan to support that. And following the guidance of the FESCO ticket[1] how we can in the end align all products to follow a general cadence and life cycle while allowing products the flexibility they want and/or need. Thanks everyone! Regards, Phil [1] https://fedorahosted.org/fesco/ticket/1202 [2] https://lists.fedoraproject.org/pipermail/kernel/2013-November/004678.html [3] https://lists.fedoraproject.org/pipermail/server/2013-November/000369.html -- Philipp Knirsch | Tel.: +49-711-96437-470 Manager Core Services| Fax.: +49-711-96437-111 Red Hat GmbH | Email: Phil Knirsch pknir...@redhat.com Wankelstrasse 5 | Web: http://www.redhat.com/ D-70563 Stuttgart, Germany -- 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 QA] #438: Multiple builds fixing a bug show confusing status label
#438: Multiple builds fixing a bug show confusing status label ---+- Reporter: kparal| Owner: mkrizek Type: defect| Status: new Priority: minor | Milestone: Undetermined Future Component: Blocker bug tracker page |Version: Resolution:| Keywords: Blocked By:| Blocking: ---+- Changes (by mkrizek): * owner: tflink = mkrizek * milestone: = Undetermined Future Comment: Replying to [ticket:438 kparal]: So, if you have an ordered array ['pending testing', 'testing', 'pending stable', 'stable'], you pick the lowest index available in update XYZ statuses and show that as the label. What do you think? Correct. However, it turns out there are more issues with the update sync code that prevents this from being fixed easily (updates deleted from bodhi remain in the app's db as if they were not deleted...). I will investigate further. -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/438#comment:1 Fedora QA http://fedorahosted.org/fedora-qa Fedora Quality Assurance ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: [Base] Release cycle discussion for Fedora products and specifically Fedora Base and how they interact/align
On 11/26/2013 03:12 PM, Phil Knirsch wrote: Hi everyone. As i've been having a few discussions myself and following several of them as well as plans about release cycles in the different WGs over the past weeks and after FESCO discussed this in during their meetings and in a FESCO ticket[1] i get the feeling that we should be discussing this not in committees only but on a broader scale across all committees and WGs. Congrats being the first of and in the WG's that essentially asks the community what they would/could maintain their package for a long period of time as opposed to have any or all of the WG's dictate/decide that for them... JBG -- 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: orphan/retire gradle
26.11.2013 15:06, punto...@libero.it wrote: Il 26/11/2013 11:34, Pavel Alexeev ha scritto: 25.11.2013 22:45, Mikolaj Izdebski wrote: W dniu 25.11.2013 18:16, Pavel Alexeev pisze: How groovy will be in Fedora? Is it mean it also will be retired soon? No, there are no plans of retiring groovy. (Groovy can be either with Ant or Gradle. Fedora uses the first option.) Thanks, Mikolaj. But IIRC groovy = 2.0 switched to gradle build only? yes Have not you either plans to update it? dont forget this problem groovy-all 1.8.x asm3 groovy-all 2.x asm4 gradle use groovy-all 1.8.x ( with asm3) and asm4 Then we have circle? That problem what you discussing before (pointed in mail list previously)? So, no chance update both without exception use binary bundled version or fully maintain alternative build system (bootstrap)? -- 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: orphan/retire gradle
Il 26/11/2013 16:42, Pavel Alexeev ha scritto: 26.11.2013 15:06, punto...@libero.it wrote: Il 26/11/2013 11:34, Pavel Alexeev ha scritto: 25.11.2013 22:45, Mikolaj Izdebski wrote: W dniu 25.11.2013 18:16, Pavel Alexeev pisze: How groovy will be in Fedora? Is it mean it also will be retired soon? No, there are no plans of retiring groovy. (Groovy can be either with Ant or Gradle. Fedora uses the first option.) Thanks, Mikolaj. But IIRC groovy = 2.0 switched to gradle build only? yes Have not you either plans to update it? dont forget this problem groovy-all 1.8.x asm3 groovy-all 2.x asm4 gradle use groovy-all 1.8.x ( with asm3) and asm4 Then we have circle? yes That problem what you discussing before (pointed in mail list previously)? yes, but if you do the same type of question the answer is always the same So, no chance update both without exception use binary bundled version or fully maintain alternative build system (bootstrap)? what would change? ... own nothing ... gradle, use at runtime those libraries, and don't work with our ... attachment: puntogil.vcf-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[perl-NetPacket/f19] (2 commits) ...Update to 1.4.3
Summary of changes: 51e5db9... Update to 1.4.2. (*) b40cc69... Update to 1.4.3 (*) (*) 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-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-NetPacket/f20] Update to 1.4.3
Summary of changes: b40cc69... Update to 1.4.3 (*) (*) 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-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-NetPacket/f18] (2 commits) ...Update to 1.4.3
Summary of changes: 51e5db9... Update to 1.4.2. (*) b40cc69... Update to 1.4.3 (*) (*) 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-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Adding vagrant images to the Fedora build
Hi fedora ! Im reviving this thread about vagrant images. I'd like to use packer.io to build vagrant images as part of the fedora builds. I assume this means first we will need vagrant and packer packeged in fedora? Or does fedora allow the use of nonpackaged utilities to build side-artifacts, like vagrant-fedora images for qemu/vmware... having ready to roll vagrant images for fedora would be a huge win for rapid testing and adoption of software stacks on emerging fedora distros! On Wed, Jul 17, 2013 at 11:20:17AM -0400, Bill Nottingham wrote: It would likely push this to a system-wide change, but wouldn't it be logical for this feature to also make a vagrant-able image as well? To be an official Vagrant image, we need Chef, and while Sam Kottler is working with Opscode to make that finally happen (awesome!), I don't think we want that to be a blocker. Additionally, the conventions for a Vagrant image are significantly different from what we want for the cloud image. (Root password set to vagrant, for example.) So, the plan is to provide those semi-officially from fedorpeople.org and the Cloud SIG wiki. As we get easier technology in Koji for making images, we might revisit for F20. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
SDDMinsteadOfKDM Change pushed back to f21
At the KDE SIG meeting today, we made the hard decision to push http://fedoraproject.org/wiki/Changes/SDDMinsteadOfKDM change/feature back to f21. There were simply too many sddm-related blocker issues that would not be safely resolvable in time for f20 release. As such, effective immediately, we're implementing http://fedoraproject.org/wiki/Changes/SDDMinsteadOfKDM#Contingency_Plan to revert back to using kdm for f20 release. I just made commits to comps-f20 and spin-kickstarts/f20 branch to implement that. jreznik will send out some followup announcement(s), and relnotes poking (thanks). -- Rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[389-devel] please review: Ticket 47525 (continuation) - add rwlock for global config area
https://fedorahosted.org/389/ticket/47525 https://fedorahosted.org/389/attachment/ticket/47525/0001-Ticket-47525-Need-to-add-locking-around-config-area-.patch -- Mark Reynolds 389 Development Team Red Hat, Inc mreyno...@redhat.com -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Schedule for Wednesday's FESCo Meeting (2013-11-27)
Following is the list of topics that will be discussed in the FESCo meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '-MM-DD HH:MM UTC' Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9 = Followups = #topic #1193 reboots for all updates -- are we ready for this? .fesco 1193 https://fedorahosted.org/fesco/ticket/1193 #topic #1185 Enable -Werror=format-security by default .fesco 1185 https://fedorahosted.org/fesco/ticket/1185 #topic #1198 Possible changes to Fedora EOL bug procedure .fesco 1198 https://fedorahosted.org/fesco/ticket/1198 #topic #1140 F20 Self Contained Changes - week 2013-07-10 - 2013-07-17 .fesco 1140 https://fedorahosted.org/fesco/ticket/1140 #topic #1201 Enabling third party repositories .fesco 1201 https://fedorahosted.org/fesco/ticket/1201 = New business = #topic #1207 provenpackager request .fesco 1207 https://fedorahosted.org/fesco/ticket/1207 #topic #1208Request Proven Packager .fesco 1208 https://fedorahosted.org/fesco/ticket/1208 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at https://fedorahosted.org/fesco/report/9 If you would like to add something to this agenda, you can reply to this e-mail, file a new ticket at https://fedorahosted.org/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. -- 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 Change Freeze
Hi all, as the Fedora 20 schedule[1] states the Final change freeze is upon us. As of now only updates that fix an accepted Final Blocker bug or Freeze exception will be allowed in. we are at the post beta stage of release, so the Pre-release[3] stage of the updates policy applies. Regards kevin [1] http://fedorapeople.org/groups/schedule/f-20/f-20-devel-tasks.html [2] http://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [3] http://fedoraproject.org/wiki/Updates_Policy#Pre_release signature.asc Description: PGP signature ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [Fedora QA] #359: Create Ansible Playbooks for Deployment and Updating
#359: Create Ansible Playbooks for Deployment and Updating ---+- Reporter: tflink| Owner: tflink Type: enhancement | Status: closed Priority: major | Milestone: Undetermined Future Component: Blocker bug tracker page |Version: Resolution: fixed | Keywords: Blocked By:| Blocking: ---+- Changes (by mkrizek): * status: new = closed * resolution: = fixed Comment: tflink has done this. Closing. -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/359#comment:2 Fedora QA http://fedorahosted.org/fedora-qa Fedora Quality Assurance ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: python-django update to Django-1.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/26/2013 09:31 AM, Simo Sorce wrote: On Tue, 2013-11-26 at 08:59 -0500, Stephen Gallagher wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/26/2013 08:34 AM, Simo Sorce wrote: On Tue, 2013-11-26 at 12:02 +0100, Matthias Runge wrote: On 11/25/2013 06:51 PM, Simo Sorce wrote: On Mon, 2013-11-25 at 11:24 -0500, Stephen Gallagher wrote: This is kind of why I keep coming back to: Why do we have python-django at all? I don't really see any reason why we shouldn't kill off the python-django package and just carry 'python-django15' and 'python-django16' packages with a conflict. The number of incompatibilities between releases is such that I don't think we really want to be forcing upgrades on other packages at all. We should just be carrying whichever two versions are supported by upstream at any given time. Upstream is very good about maintaining bugfixes and security fixes in both supported streams. +1 by changing version the current way, the only ting we can guarantee is a lot of broken packages all the time. I see your points here and thank you for the feedback! From my experience, it was just a pain to have python-django14 and python-django[1]. Introducing one or two other packages python-django15 and python-django16 will make it more difficult for users to update django. How should packages require Django? Just require python-django? Sadly, yum can not handle that properly[1]. When dropping python-django as provides/requires, we'd have the situation packages will require a specific version. That's rather unfortunate, because combination of packages requiring some other python-django-foo package might require a different django version. At least for OpenStack Horizon I can say, we're up to fix compatibility issues with Django-1.6 upstream. Matthias [1] https://bugzilla.redhat.com/show_bug.cgi?id=978647 Packages should require the latest version they work with. If some package is really awesome and supports multiple versions I guess it could support a generic python-django. It's ok if 2 packages become incompatible this way, they wouldn't work anyway with the wrong version of django. I think Simo has the right idea here. We should drop the standard python-django package at this point and instead have python-django15 and python-django16. Each of those packages should add a virtual Provides: and Obsoletes: for python-django. Existing packages with a non-strict version will then default to upgrading to the absolute latest version (python-django16). If that's not acceptable to their project, they'll need to release a new update with 'Requires: python-django15' and things should go back to normal. In the future, if they update so they work with both currently-available versions, they can go back to 'Requires: python-django' and will then work with whichever version the user has on the system (such as for another project). Yes, it slightly increases the packager work, but it should give a better experience for the user... to a point. Since Django 1.5 and 1.6 cannot presently co-exist on the system, they'll need to have an explicit Conflicts:. This does mean that users will have an issue if they end up pulling Django 1.6 as part of an upgrade and then try to install a package that Requires: python-django15. We can't automatically remove python-django16, so the user will have to know to do this manually. One issue to resolve is how to upgrade to the next version if you have python-django15 and F22 has python-django16 and python-django17, perhaps some clever way of making python-django16 obsolete (instead of conflict) python-django15 once 1.5 is pushed out of the new distro version ? Obsoletes: wouldn't really be appropriate here, because that implies that it's a complete replacement of the old version. That said, it still might be the best of a bad situation... I still think that the safest approach is to require that packagers of Django apps keep their dependencies set appropriately. So if they know they support 1.5 and 1.6: Requires: python-django = 1.5 Conflicts: python-django = 1.7 And if they only support one, they should Requires: python-django15 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKU4PgACgkQeiVVYja6o6OMqACgjp4F2r0b6rrDjoIGSgolej+w EkwAn25xeG3DJ/j0i+5J04evaV5vH6u+ =QyXP -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: F21 Self Contained Change: Replace Bacula with Bareos
Simone Caronni wrote: http://www.mail-archive.com/bacula-users@lists.sourceforge.net/msg57308.html Hmmm, that guy is painting a somewhat different picture of the situation of the 2 projects than your Change page. In particular, he claims the community version is not dead. (Is that credible?) (He does admit that Bacula is using the crippleware business model though.) His vague allegations of copyright infringement in Bareos lack any kind of details required to verify them though. https://www.bareos.org/en/faq/items/copyright_bacula_bareos.html And of course the Bareos folks claim that there isn't any infringement. So, whom can Fedora believe in this dispute? What if the vague allegations are really just FUD (as Bareos is claiming)? Then we'd be blocking a project based only on FUD and encouraging more such FUD being spread to deny competitors a place in Fedora… Another thing that strikes me as very odd is that Bacula is apparently copyrighted by the FSFE, yet they use the crippleware business model. I thought the FSF (and the FSFE) were strongly against crippleware (or Open Core as they called it once in an essay)! That said, the FSFE is probably the way out of this mess. If they are the real copyright holders, we just need to contact THEM about the issue and get a statement from them, ignoring the Bacula guy entirely. 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: debuginfo packages available in updates later than regular packages.
Sandro Mani wrote: [1] http://smani.fedorapeople.org/somepackage.spec Yeah, that hack looks like it could work, sorta. If you have multiple subpackages installed, having only one subpackage of the correct version and the others of wrong versions will still be satisfying the dependency in the -debuginfo package. (And subpackages do not always require each other, so you cannot always require on the EVR-locked inter-subpackage Requires.) 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: orphan/retire gradle
26.11.2013 20:00, punto...@libero.it пишет: Il 26/11/2013 16:42, Pavel Alexeev ha scritto: 26.11.2013 15:06, punto...@libero.it wrote: Il 26/11/2013 11:34, Pavel Alexeev ha scritto: 25.11.2013 22:45, Mikolaj Izdebski wrote: W dniu 25.11.2013 18:16, Pavel Alexeev pisze: How groovy will be in Fedora? Is it mean it also will be retired soon? No, there are no plans of retiring groovy. (Groovy can be either with Ant or Gradle. Fedora uses the first option.) Thanks, Mikolaj. But IIRC groovy = 2.0 switched to gradle build only? yes Have not you either plans to update it? dont forget this problem groovy-all 1.8.x asm3 groovy-all 2.x asm4 gradle use groovy-all 1.8.x ( with asm3) and asm4 Then we have circle? yes That problem what you discussing before (pointed in mail list previously)? yes, but if you do the same type of question the answer is always the same So, no chance update both without exception use binary bundled version or fully maintain alternative build system (bootstrap)? what would change? ... own nothing ... gradle, use at runtime those libraries, and don't work with our ... Ok, sorry for the stupid questions. May be it because I can't believe in it. One more question. Did you see how other distributions handle it? Debian have groovy 2.1.0 ( http://packages.debian.org/experimental/groovy ) and gradle 1.4 ( http://packages.debian.org/search?searchon=nameskeywords=gradle ) -- 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: debuginfo packages available in updates later than regular packages.
On Tue, 26 Nov 2013 11:39:38 +0100, Sandro Mani wrote: Here is a quick and dirty spec implementing the idea I described: [1]. From what I can see it behaves correctly with any combination of packages and subpackages installed. Am I missing something? [1] http://smani.fedorapeople.org/somepackage.spec There were always intentions to allow installing multiple *-debuginfo.rpm versions at once. This would allow for example examining a core file generated from older binaries (which could be still running when they crashed while newer rpm was installed on disk). Currently it is not possible but one such open Bug with some proposals is: undesired cross-rpm elf build-id duplication due to strict content-hash handling in debugedit.c https://bugzilla.redhat.com/show_bug.cgi?id=1002341 (In ideal case for debug purposes one needs also the matching binary, not just its debuginfo. But in practice the debuginfo should be sufficient.) In reality ABRT solves the problem of multi debuginfo rpms by installing new chroot each time with the needed package versions. This is a bit expensive. Your proposal definitely blocks this multiple *-debuginfo.rpm versions idea. But the multi-version idea has never worked yet and it is not sure it will ever be. Your proposal is sure still better than what we have now. Besides that your proposal has to be implemented into rpm tool code; currently the debuginfo subpackage is implemented only as a rpm macro in /usr/lib/rpm. But that is sure OK. Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: orphan/retire gradle
Il 26/11/2013 20:57, Pavel Alexeev ha scritto: 26.11.2013 20:00, punto...@libero.it пишет: Il 26/11/2013 16:42, Pavel Alexeev ha scritto: 26.11.2013 15:06,punto...@libero.it wrote: Il 26/11/2013 11:34, Pavel Alexeev ha scritto: 25.11.2013 22:45, Mikolaj Izdebski wrote: W dniu 25.11.2013 18:16, Pavel Alexeev pisze: How groovy will be in Fedora? Is it mean it also will be retired soon? No, there are no plans of retiring groovy. (Groovy can be either with Ant or Gradle. Fedora uses the first option.) Thanks, Mikolaj. But IIRC groovy = 2.0 switched to gradle build only? yes Have not you either plans to update it? dont forget this problem groovy-all 1.8.x asm3 groovy-all 2.x asm4 gradle use groovy-all 1.8.x ( with asm3) and asm4 Then we have circle? yes That problem what you discussing before (pointed in mail list previously)? yes, but if you do the same type of question the answer is always the same So, no chance update both without exception use binary bundled version or fully maintain alternative build system (bootstrap)? what would change? ... own nothing ... gradle, use at runtime those libraries, and don't work with our ... Ok, sorry for the stupid questions. May be it because I can't believe in it. questions are never stupid, One more question. Did you see how other distributions handle it? Debian have groovy 2.1.0 ( http://packages.debian.org/experimental/groovy ) and gradle 1.4 ( http://packages.debian.org/search?searchon=nameskeywords=gradle ) Debian packaging guideline allow some things, such as, for e.g., groovy-all (with its bundled libraries asm3 commons-cli antlr 2.x) or maven-ant-tasks (with its bundled libraries ...) or maven 2.x or plexus-container-default 1.0-xxx, etc etc. and i dont know if the experimental Debian branch is usable with gradle ... but i think no about this topic it has been discussed for a long time, and now this conversation is only a repetition. and repeating the same things i broke the boxes, then do not take it amiss regards again my apologized attachment: puntogil.vcf-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Anyone know how to contact Chitlesh Goorah?
Hi, Per the unresponsive package maintainers policy, I've opened https://bugzilla.redhat.com/show_bug.cgi?id=1029728 . It has now been two weeks with no response, so I'm posting to the list to ask if anyone knows how to contact Chitlesh. Thanks. -Ben -- 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: debuginfo packages available in updates later than regular packages.
On 26.11.2013 19:55, Kevin Kofler wrote: Sandro Mani wrote: [1] http://smani.fedorapeople.org/somepackage.spec Yeah, that hack looks like it could work, sorta. If you have multiple subpackages installed, having only one subpackage of the correct version and the others of wrong versions will still be satisfying the dependency in the -debuginfo package. (And subpackages do not always require each other, so you cannot always require on the EVR-locked inter-subpackage Requires.) Kevin Kofler Right. Otherwise, I guess the Conflicts approach suggested by Nicolas could work and also handle such cases? But before all this, there is the current problem that debuginfo packages are only updated when using yum, as pointed out by Michael. If debuginfo packages are not shipped in the standard repos, some other solution is needed. I pointed out an approach which could work: - Move the debuginfo repo definitions to separate files - Have a package fedora-release-debug (or similar) install the repo file in /etc/yum.repos.d. The repos would be enabled by default when installed. - Have all debuginfo packages depend on fedora-release-debug - (ugly) Have debuginfo-install install the repo file before proceeding as before. Any thoughts on that? Sandro -- 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] 2013-11-27 @ **17:00 UTC** - F20 Final Blocker Bug Review #3
# F20 Final Blocker Review meeting #3 # Date: 2013-11-27 # Time: 17:00 UTC (12:00 EST, 09:00 PST) # Location: #fedora-blocker-review on irc.freenode.net Freeze is now upon us and tomorrow (2013-11-27) we'll be having another Blocker Review Meeting for Fedora 20. There's plenty to review this time around with a whopping 10 proposed blockers and 10 proposed freeze exceptions. The full list is located here: http://qa.fedoraproject.org/blockerbugs/current it might be worth the time to read up on them before the meeting - that way we can get through them all in the mere 3 hours we have. We'll be reviewing the bugs to ensure they meet the Final release criteria [1] as blocking final release and that the bugs are getting the attention they need. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting See you tomorrow! [1] https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria signature.asc Description: PGP 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
[Test-Announce] Fedora 20 Final Test Compose 3 (TC3) Available Now!
NOTE: The 64-bit Desktop and LXDE Lives are over their respective size limits. As per the Fedora 20 schedule [1], Fedora 20 Final Test Compose 3 (TC3) is now available for testing. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/5808#comment:8 . 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
Re: Adding vagrant images to the Fedora build
Check this: https://bugzilla.redhat.com/show_bug.cgi?id=905396 -- 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: Adding vagrant images to the Fedora build
On Wed, Nov 27, 2013 at 11:12 AM, Christopher Meng cicku...@gmail.comwrote: Check this: https://bugzilla.redhat.com/show_bug.cgi?id=905396 The review is being done here https://bugzilla.redhat.com/show_bug.cgi?id=1020456. He needs to be sponsored first! Any takers? -- Arun S A G http://zer0c00l.in/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
File ExtUtils-XSpp-0.18.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-ExtUtils-XSpp: c44ad3281df81319d02833a4e42282ac ExtUtils-XSpp-0.18.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-XSpp] 0.18 bump
commit a271c30fd6a154a9110f1ff955d37b223334cbe0
Author: Petr Písař ppi...@redhat.com
Date: Tue Nov 26 09:30:21 2013 +0100
0.18 bump
.gitignore |1 +
perl-ExtUtils-XSpp.spec | 46 --
sources |2 +-
3 files changed, 34 insertions(+), 15 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 4478a61..e082512 100644
--- a/.gitignore
+++ b/.gitignore
@@ -4,3 +4,4 @@ ExtUtils-XSpp-0.12.tar.gz
/ExtUtils-XSpp-0.1602.tar.gz
/ExtUtils-XSpp-0.1603.tar.gz
/ExtUtils-XSpp-0.1700.tar.gz
+/ExtUtils-XSpp-0.18.tar.gz
diff --git a/perl-ExtUtils-XSpp.spec b/perl-ExtUtils-XSpp.spec
index cf39c7c..1c5dca1 100644
--- a/perl-ExtUtils-XSpp.spec
+++ b/perl-ExtUtils-XSpp.spec
@@ -1,27 +1,43 @@
Name: perl-ExtUtils-XSpp
-# Use four digits since 0.1601
-Version:0.1700
-Release:3%{?dist}
+Epoch: 1
+Version:0.18
+Release:1%{?dist}
Summary:C++ variant of Perl's XS language
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/ExtUtils-XSpp/
Source0:
http://search.cpan.org/CPAN/authors/id/S/SM/SMUELLER/ExtUtils-XSpp-%{version}.tar.gz
BuildArch: noarch
+BuildRequires: perl
BuildRequires: perl(base)
BuildRequires: perl(File::Spec)
+BuildRequires: perl(lib)
BuildRequires: perl(Module::Build)
+BuildRequires: perl(strict)
+BuildRequires: perl(warnings)
+# Run-time:
+BuildRequires: perl(Carp)
+BuildRequires: perl(Digest::MD5)
+# Exporter not used at tests
+BuildRequires: perl(ExtUtils::ParseXS) = 3.07
+BuildRequires: perl(ExtUtils::Typemaps)
+BuildRequires: perl(File::Basename)
+BuildRequires: perl(File::Path)
+# Getopt::Long not used at tests
+BuildRequires: perl(IO::Handle)
+# IPC::Open2 not used at tests
+BuildRequires: perl(vars)
+# Tests:
+BuildRequires: perl(if)
BuildRequires: perl(Test::Base)
+BuildRequires: perl(Test::Base::Filter)
BuildRequires: perl(Test::Differences)
BuildRequires: perl(Test::More)
-BuildRequires: perl(ExtUtils::ParseXS) = 0.2202
-Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
Requires: perl(IPC::Open2)
-# RPM 4.8 style
-%filter_from_requires /ExtUtils::XSpp::Lexer/d
-%filter_setup
-# RPM 4.9 style
-%global __requires_exclude
%{?__requires_exclude:__requires_exclude|}ExtUtils::XSpp::Lexer
+Requires: perl(ExtUtils::ParseXS) = 3.07
+
+%global __requires_exclude_from
%{?__requires_exclude_from:__requires_exclude_from|}^%{_datadir}/doc
%description
ExtUtils::XSpp handles the XS++ language, used to create an extension interface
@@ -31,25 +47,27 @@ between Perl and C++ code/library.
%setup -q -n ExtUtils-XSpp-%{version}
%build
-%{__perl} Build.PL installdirs=vendor
+perl Build.PL installdirs=vendor
./Build
%install
./Build install destdir=$RPM_BUILD_ROOT create_packlist=0
-find $RPM_BUILD_ROOT -depth -type d -empty -exec rmdir {} \;
-
%{_fixperms} $RPM_BUILD_ROOT/*
%check
./Build test
%files
-%doc Changes README XSP.yp
+%doc Changes examples README XSP.yp
%{_bindir}/xspp
%{perl_vendorlib}/ExtUtils*
%{_mandir}/man?/*
%changelog
+* Tue Nov 26 2013 Petr Pisar ppi...@redhat.com - 1:0.18-1
+- 0.18 bump
+- Use two-digit versions again
+
* Sat Aug 03 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 0.1700-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
diff --git a/sources b/sources
index 15fc485..bb707cd 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-37a49cdabe593d9730e9280907f7b941 ExtUtils-XSpp-0.1700.tar.gz
+c44ad3281df81319d02833a4e42282ac ExtUtils-XSpp-0.18.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 1033066] perl-Path-IsDev-1.000002 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1033066 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC|ppi...@redhat.com | Assignee|jples...@redhat.com |ppi...@redhat.com -- 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=T3snIg1aYYa=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 1032078] ExtUtils-XSpp-0.18 bump
https://bugzilla.redhat.com/show_bug.cgi?id=1032078 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-ExtUtils-XSpp-0.18-1.f ||c21 Resolution|--- |RAWHIDE Last Closed||2013-11-26 03:40:31 -- 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=M69ZrwzhT3a=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 Path-IsDev-1.000002.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-Path-IsDev: 5645c9006031cc1fed8dce70095e312e Path-IsDev-1.02.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-Path-IsDev] 1.000002 bump
commit 177d5ee5b57b300e6930ff20a5613672a31bd5d7
Author: Petr Písař ppi...@redhat.com
Date: Tue Nov 26 10:05:55 2013 +0100
1.02 bump
.gitignore |1 +
perl-Path-IsDev.spec | 16
sources |2 +-
3 files changed, 10 insertions(+), 9 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 4334162..3bf1abd 100644
--- a/.gitignore
+++ b/.gitignore
@@ -4,3 +4,4 @@
/Path-IsDev-0.4.0.tar.gz
/Path-IsDev-0.6.0.tar.gz
/Path-IsDev-1.00.tar.gz
+/Path-IsDev-1.02.tar.gz
diff --git a/perl-Path-IsDev.spec b/perl-Path-IsDev.spec
index 053af79..a4d36e9 100644
--- a/perl-Path-IsDev.spec
+++ b/perl-Path-IsDev.spec
@@ -1,5 +1,5 @@
Name: perl-Path-IsDev
-Version:1.00
+Version:1.02
Release:1%{?dist}
Summary:Determine if a given Path resembles a development source tree
License:GPL+ or Artistic
@@ -8,12 +8,12 @@ URL:http://search.cpan.org/dist/Path-IsDev/
Source0:
http://www.cpan.org/authors/id/K/KE/KENTNL/Path-IsDev-%{version}.tar.gz
BuildArch: noarch
BuildRequires: perl
-BuildRequires: perl(Module::Build) = 0.3601
+BuildRequires: perl(Module::Build) = 0.4202
BuildRequires: perl(strict)
BuildRequires: perl(warnings)
# Run-time
BuildRequires: perl(Carp)
-BuildRequires: perl(Class::Tiny) = 0.011
+BuildRequires: perl(Class::Tiny) = 0.010
BuildRequires: perl(Config)
BuildRequires: perl(File::HomeDir)
BuildRequires: perl(Module::Runtime)
@@ -23,13 +23,10 @@ BuildRequires: perl(Role::Tiny::With)
BuildRequires: perl(Scalar::Util)
BuildRequires: perl(Sub::Exporter)
# Tests
-BuildRequires: perl(File::Spec)
BuildRequires: perl(File::Temp)
BuildRequires: perl(FindBin)
-BuildRequires: perl(IO::Handle)
-BuildRequires: perl(IPC::Open3)
BuildRequires: perl(Test::Fatal)
-BuildRequires: perl(Test::More) = 0.99
+BuildRequires: perl(Test::More) = 1.001002
Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
Requires: perl(Carp)
Requires: perl(File::HomeDir)
@@ -43,7 +40,7 @@ Requires: perl(Scalar::Util)
This module is more or less a bunch of heuristics for determining if a
given path is a development tree root of some kind.
-This has many useful applications, notably ones that require behaviours for
+This has many useful applications, notably ones that require behaviors for
installed modules to be different to those that are still in
development
@@ -67,6 +64,9 @@ perl Build.PL installdirs=vendor
%{_mandir}/man3/*
%changelog
+* Tue Nov 26 2013 Petr Pisar ppi...@redhat.com - 1.02-1
+- 1.02 bump
+
* Thu Oct 24 2013 Jitka Plesnikova jples...@redhat.com - 1.00-1
- 1.00 bump
diff --git a/sources b/sources
index 23d41fc..6ad2eb9 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-9ffbd766f6aa97205eaedba5ce219488 Path-IsDev-1.00.tar.gz
+5645c9006031cc1fed8dce70095e312e Path-IsDev-1.02.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 1033066] perl-Path-IsDev-1.000002 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1033066 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-Path-IsDev-1.02-1. ||fc21 Resolution|--- |RAWHIDE Last Closed||2013-11-26 04:16:16 -- 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=Y6JKCGLbSPa=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 1034098] perl-CGI-3.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1034098 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC||ppi...@redhat.com Assignee|jples...@redhat.com |ppi...@redhat.com -- 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=aKqRbSyw22a=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 CGI.pm-3.64.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-CGI: 396afa921d7ce76aa3a5dc4ff744bf3d CGI.pm-3.64.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-CGI] 3.64 bump
commit 6eb8dc39ade1bca3376aac09ebf4609b8c25a70a
Author: Petr Písař ppi...@redhat.com
Date: Tue Nov 26 10:31:45 2013 +0100
3.64 bump
.gitignore|1 +
perl-CGI.spec | 14 --
sources |2 +-
3 files changed, 14 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 93e9c84..32fe5dd 100644
--- a/.gitignore
+++ b/.gitignore
@@ -4,3 +4,4 @@
/CGI.pm-3.61.tar.gz
/CGI.pm-3.62.tar.gz
/CGI.pm-3.63.tar.gz
+/CGI.pm-3.64.tar.gz
diff --git a/perl-CGI.spec b/perl-CGI.spec
index 6a1743a..ded120b 100644
--- a/perl-CGI.spec
+++ b/perl-CGI.spec
@@ -1,7 +1,7 @@
Name: perl-CGI
Summary:Handle Common Gateway Interface requests and responses
-Version:3.63
-Release:291%{?dist}
+Version:3.64
+Release:1%{?dist}
License:(GPL+ or Artistic) and Artistic 2.0
Group: Development/Libraries
Source0:
http://search.cpan.org/CPAN/authors/id/M/MA/MARKSTOS/CGI.pm-%{version}.tar.gz
@@ -13,9 +13,13 @@ BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(base)
BuildRequires: perl(Carp)
BuildRequires: perl(constant)
+%if 0%(perl -e 'print $] = 5.019')
+BuildRequires: perl(deprecate)
+%endif
BuildRequires: perl(Exporter)
BuildRequires: perl(FCGI) = 0.67
BuildRequires: perl(File::Spec) = 0.82
+BuildRequires: perl(if)
BuildRequires: perl(overload)
BuildRequires: perl(strict)
BuildRequires: perl(vars)
@@ -31,6 +35,9 @@ BuildRequires: perl(lib)
BuildRequires: perl(Test::More) = 0.98
BuildRequires: perl(utf8)
Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
+%if 0%(perl -e 'print $] = 5.019')
+Requires: perl(deprecate)
+%endif
Requires: perl(FCGI) = 0.67
Requires: perl(File::Spec) = 0.82
Obsoletes: %{name}-tests = 3.49
@@ -75,6 +82,9 @@ make test
%{_mandir}/man3/*.3*
%changelog
+* Tue Nov 26 2013 Petr Pisar ppi...@redhat.com - 3.64-1
+- 3.64 bump
+
* Sat Aug 03 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 3.63-291
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
diff --git a/sources b/sources
index 894f124..33c6f70 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-78eb3acb736205ca12ec2c79bc737e6c CGI.pm-3.63.tar.gz
+396afa921d7ce76aa3a5dc4ff744bf3d CGI.pm-3.64.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 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
[perl-CGI] Remove old Obsoletes statement
commit cd2c1389969deab7ecf4e8b6743c32f41176486b
Author: Petr Písař ppi...@redhat.com
Date: Tue Nov 26 10:32:13 2013 +0100
Remove old Obsoletes statement
perl-CGI.spec |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
---
diff --git a/perl-CGI.spec b/perl-CGI.spec
index ded120b..3b597e7 100644
--- a/perl-CGI.spec
+++ b/perl-CGI.spec
@@ -40,7 +40,6 @@ Requires: perl(deprecate)
%endif
Requires: perl(FCGI) = 0.67
Requires: perl(File::Spec) = 0.82
-Obsoletes: %{name}-tests = 3.49
%{?perl_default_filter}
# Remove under-specified dependencies
--
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 1034098] perl-CGI-3.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1034098 --- Comment #1 from Petr Pisar ppi...@redhat.com --- This is pure bug-fixing release suitable for F≥19. -- 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=he1NG3NbXDa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-CGI/f20] 3.64 bump
commit b2955478bf117f1d2407647ef294ec0aa0e98b47
Author: Petr Písař ppi...@redhat.com
Date: Tue Nov 26 10:31:45 2013 +0100
3.64 bump
.gitignore|1 +
perl-CGI.spec | 14 --
sources |2 +-
3 files changed, 14 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 93e9c84..32fe5dd 100644
--- a/.gitignore
+++ b/.gitignore
@@ -4,3 +4,4 @@
/CGI.pm-3.61.tar.gz
/CGI.pm-3.62.tar.gz
/CGI.pm-3.63.tar.gz
+/CGI.pm-3.64.tar.gz
diff --git a/perl-CGI.spec b/perl-CGI.spec
index 6a1743a..ded120b 100644
--- a/perl-CGI.spec
+++ b/perl-CGI.spec
@@ -1,7 +1,7 @@
Name: perl-CGI
Summary:Handle Common Gateway Interface requests and responses
-Version:3.63
-Release:291%{?dist}
+Version:3.64
+Release:1%{?dist}
License:(GPL+ or Artistic) and Artistic 2.0
Group: Development/Libraries
Source0:
http://search.cpan.org/CPAN/authors/id/M/MA/MARKSTOS/CGI.pm-%{version}.tar.gz
@@ -13,9 +13,13 @@ BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(base)
BuildRequires: perl(Carp)
BuildRequires: perl(constant)
+%if 0%(perl -e 'print $] = 5.019')
+BuildRequires: perl(deprecate)
+%endif
BuildRequires: perl(Exporter)
BuildRequires: perl(FCGI) = 0.67
BuildRequires: perl(File::Spec) = 0.82
+BuildRequires: perl(if)
BuildRequires: perl(overload)
BuildRequires: perl(strict)
BuildRequires: perl(vars)
@@ -31,6 +35,9 @@ BuildRequires: perl(lib)
BuildRequires: perl(Test::More) = 0.98
BuildRequires: perl(utf8)
Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
+%if 0%(perl -e 'print $] = 5.019')
+Requires: perl(deprecate)
+%endif
Requires: perl(FCGI) = 0.67
Requires: perl(File::Spec) = 0.82
Obsoletes: %{name}-tests = 3.49
@@ -75,6 +82,9 @@ make test
%{_mandir}/man3/*.3*
%changelog
+* Tue Nov 26 2013 Petr Pisar ppi...@redhat.com - 3.64-1
+- 3.64 bump
+
* Sat Aug 03 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 3.63-291
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
diff --git a/sources b/sources
index 894f124..33c6f70 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-78eb3acb736205ca12ec2c79bc737e6c CGI.pm-3.63.tar.gz
+396afa921d7ce76aa3a5dc4ff744bf3d CGI.pm-3.64.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-CGI/f19] Update dependencies and license
commit efb4598c1cb3120a79a191dee421a935fc1ad2df
Author: Jitka Plesnikova jples...@redhat.com
Date: Mon Jun 24 16:19:44 2013 +0200
Update dependencies and license
perl-CGI.spec | 16 ++--
1 files changed, 14 insertions(+), 2 deletions(-)
---
diff --git a/perl-CGI.spec b/perl-CGI.spec
index e906357..1c656c6 100644
--- a/perl-CGI.spec
+++ b/perl-CGI.spec
@@ -1,12 +1,13 @@
Name: perl-CGI
Summary:Handle Common Gateway Interface requests and responses
Version:3.63
-Release:2%{?dist}
-License:GPL+ or Artistic
+Release:3%{?dist}
+License:(GPL+ or Artistic) and Artistic 2.0
Group: Development/Libraries
Source0:
http://search.cpan.org/CPAN/authors/id/M/MA/MARKSTOS/CGI.pm-%{version}.tar.gz
URL:http://search.cpan.org/dist/CGI
BuildArch: noarch
+BuildRequires: perl
BuildRequires: perl(ExtUtils::MakeMaker)
# Run-requires:
BuildRequires: perl(base)
@@ -15,13 +16,20 @@ BuildRequires: perl(constant)
BuildRequires: perl(Exporter)
BuildRequires: perl(FCGI) = 0.67
BuildRequires: perl(File::Spec) = 0.82
+BuildRequires: perl(overload)
+BuildRequires: perl(strict)
+BuildRequires: perl(vars)
+BuildRequires: perl(warnings)
# Apache modules are optional
# Tests:
+BuildRequires: perl(Config)
BuildRequires: perl(Encode)
+BuildRequires: perl(FileHandle)
BuildRequires: perl(IO::File)
BuildRequires: perl(IO::Handle)
BuildRequires: perl(lib)
BuildRequires: perl(Test::More) = 0.98
+BuildRequires: perl(utf8)
Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
Requires: perl(FCGI) = 0.67
Requires: perl(File::Spec) = 0.82
@@ -67,6 +75,10 @@ make test
%{_mandir}/man3/*.3*
%changelog
+* Mon Jun 24 2013 Jitka Plesnikova jples...@redhat.com - 3.63-3
+- Specify all dependencies
+- Update License - CGI.pm is distributed under GPL and Artistic 2.0
+
* Thu Feb 14 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 3.63-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
--
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-CGI/f19] 3.64 bump
commit 8c74715f4dc03fdedbd2440e384c95a1a81d1a5a
Author: Petr Písař ppi...@redhat.com
Date: Tue Nov 26 10:31:45 2013 +0100
3.64 bump
.gitignore|1 +
perl-CGI.spec | 14 --
sources |2 +-
3 files changed, 14 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 93e9c84..32fe5dd 100644
--- a/.gitignore
+++ b/.gitignore
@@ -4,3 +4,4 @@
/CGI.pm-3.61.tar.gz
/CGI.pm-3.62.tar.gz
/CGI.pm-3.63.tar.gz
+/CGI.pm-3.64.tar.gz
diff --git a/perl-CGI.spec b/perl-CGI.spec
index 1c656c6..e263225 100644
--- a/perl-CGI.spec
+++ b/perl-CGI.spec
@@ -1,7 +1,7 @@
Name: perl-CGI
Summary:Handle Common Gateway Interface requests and responses
-Version:3.63
-Release:3%{?dist}
+Version:3.64
+Release:1%{?dist}
License:(GPL+ or Artistic) and Artistic 2.0
Group: Development/Libraries
Source0:
http://search.cpan.org/CPAN/authors/id/M/MA/MARKSTOS/CGI.pm-%{version}.tar.gz
@@ -13,9 +13,13 @@ BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(base)
BuildRequires: perl(Carp)
BuildRequires: perl(constant)
+%if 0%(perl -e 'print $] = 5.019')
+BuildRequires: perl(deprecate)
+%endif
BuildRequires: perl(Exporter)
BuildRequires: perl(FCGI) = 0.67
BuildRequires: perl(File::Spec) = 0.82
+BuildRequires: perl(if)
BuildRequires: perl(overload)
BuildRequires: perl(strict)
BuildRequires: perl(vars)
@@ -31,6 +35,9 @@ BuildRequires: perl(lib)
BuildRequires: perl(Test::More) = 0.98
BuildRequires: perl(utf8)
Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
+%if 0%(perl -e 'print $] = 5.019')
+Requires: perl(deprecate)
+%endif
Requires: perl(FCGI) = 0.67
Requires: perl(File::Spec) = 0.82
Obsoletes: %{name}-tests = 3.49
@@ -75,6 +82,9 @@ make test
%{_mandir}/man3/*.3*
%changelog
+* Tue Nov 26 2013 Petr Pisar ppi...@redhat.com - 3.64-1
+- 3.64 bump
+
* Mon Jun 24 2013 Jitka Plesnikova jples...@redhat.com - 3.63-3
- Specify all dependencies
- Update License - CGI.pm is distributed under GPL and Artistic 2.0
diff --git a/sources b/sources
index 894f124..33c6f70 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-78eb3acb736205ca12ec2c79bc737e6c CGI.pm-3.63.tar.gz
+396afa921d7ce76aa3a5dc4ff744bf3d CGI.pm-3.64.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 1034098] perl-CGI-3.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1034098 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-CGI-3.64-1.fc21 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=kMl6x2oROna=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 1034099] perl-Class-XSAccessor-1.19 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1034099 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC||ppi...@redhat.com Assignee|jples...@redhat.com |ppi...@redhat.com -- 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=Y3aU8KMZFta=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 1034098] perl-CGI-3.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1034098 --- Comment #2 from Fedora Update System upda...@fedoraproject.org --- perl-CGI-3.64-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/perl-CGI-3.64-1.fc20 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=6ZsQ5dCKNRa=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 1034098] perl-CGI-3.64 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1034098 --- Comment #3 from Fedora Update System upda...@fedoraproject.org --- perl-CGI-3.64-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/perl-CGI-3.64-1.fc19 -- 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=wVePyd7GWIa=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 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
File Class-XSAccessor-1.19.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-Class-XSAccessor: 5c5dea74f00ad37c5119dd22b28a5563 Class-XSAccessor-1.19.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-Class-XSAccessor] 1.19 bump
commit cc7956de59114ab754f7c43cbab710f5f53ce6db
Author: Petr Písař ppi...@redhat.com
Date: Tue Nov 26 11:06:31 2013 +0100
1.19 bump
.gitignore |1 +
.rpmlint |2 ++
perl-Class-XSAccessor.spec | 18 +-
sources|2 +-
4 files changed, 17 insertions(+), 6 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index f9e46e7..e1dc78c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -8,3 +8,4 @@ Class-XSAccessor-1.05.tar.gz
/Class-XSAccessor-1.14.tar.gz
/Class-XSAccessor-1.16.tar.gz
/Class-XSAccessor-1.18.tar.gz
+/Class-XSAccessor-1.19.tar.gz
diff --git a/.rpmlint b/.rpmlint
new file mode 100644
index 000..2d95675
--- /dev/null
+++ b/.rpmlint
@@ -0,0 +1,2 @@
+from Config import *
+addFilter(spelling-error .* accessors);
diff --git a/perl-Class-XSAccessor.spec b/perl-Class-XSAccessor.spec
index 3e5351c..fb4a4ac 100644
--- a/perl-Class-XSAccessor.spec
+++ b/perl-Class-XSAccessor.spec
@@ -1,23 +1,28 @@
Name: perl-Class-XSAccessor
-Version:1.18
-Release:3%{?dist}
+Version:1.19
+Release:1%{?dist}
Summary:Generate fast XS accessors without run-time compilation
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/Class-XSAccessor/
Source0:
http://www.cpan.org/authors/id/S/SM/SMUELLER/Class-XSAccessor-%{version}.tar.gz
BuildRequires: perl
-BuildRequires: perl(Carp)
BuildRequires: perl(Config)
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(strict)
+BuildRequires: perl(warnings)
+# Run-time:
+BuildRequires: perl(Carp)
+BuildRequires: perl(XSLoader)
+# Tests:
+BuildRequires: perl(constant)
+BuildRequires: perl(Data::Dumper)
BuildRequires: perl(Test::More)
BuildRequires: perl(threads)
BuildRequires: perl(Time::HiRes)
-BuildRequires: perl(warnings)
-BuildRequires: perl(XSLoader)
Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
+# Do not require private module
%global __requires_exclude
%{?__requires_exclude:__requires_exclude|}perl\\(Class::XSAccessor::Heavy\\)
%description
@@ -51,6 +56,9 @@ make test
%{_mandir}/man3/Class::*
%changelog
+* Tue Nov 26 2013 Petr Pisar ppi...@redhat.com - 1.19-1
+- 1.19 bump
+
* Sat Aug 03 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.18-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
diff --git a/sources b/sources
index 3d01df2..d955ffa 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-a1e84d23febccd57388bc22a1510ba2a Class-XSAccessor-1.18.tar.gz
+5c5dea74f00ad37c5119dd22b28a5563 Class-XSAccessor-1.19.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 1034104] perl-Pod-Markdown-1.500 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1034104 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC|mmasl...@redhat.com |ppi...@redhat.com Assignee|jples...@redhat.com |ppi...@redhat.com -- 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=NLTZhREUoea=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 1034099] perl-Class-XSAccessor-1.19 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1034099 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-Class-XSAccessor-1.19- ||1.fc21 Resolution|--- |RAWHIDE Last Closed||2013-11-26 05:17:36 -- 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=JsUWvsFWF1a=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 ZMQ-LibZMQ3-1.14.tar.gz uploaded to lookaside cache by jpo
A file has been added to the lookaside cache for perl-ZMQ-LibZMQ3: 87f6fa1231a878ca6b3beed88eb8ece7 ZMQ-LibZMQ3-1.14.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-ZMQ-LibZMQ3] Update to version 1.14
commit 1dda88963a6ff36fb962ee7410891089fd5f0b25
Author: Jose Pedro Oliveira j...@di.uminho.pt
Date: Tue Nov 26 10:19:56 2013 +
Update to version 1.14
.gitignore|1 +
perl-ZMQ-LibZMQ3.spec |7 +--
sources |2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 2c291e2..1723abc 100644
--- a/.gitignore
+++ b/.gitignore
@@ -4,3 +4,4 @@
/ZMQ-LibZMQ3-1.11.tar.gz
/ZMQ-LibZMQ3-1.12.tar.gz
/ZMQ-LibZMQ3-1.13.tar.gz
+/ZMQ-LibZMQ3-1.14.tar.gz
diff --git a/perl-ZMQ-LibZMQ3.spec b/perl-ZMQ-LibZMQ3.spec
index 2fb0d52..5702afc 100644
--- a/perl-ZMQ-LibZMQ3.spec
+++ b/perl-ZMQ-LibZMQ3.spec
@@ -1,6 +1,6 @@
Name: perl-ZMQ-LibZMQ3
-Version:1.13
-Release:3%{?dist}
+Version:1.14
+Release:1%{?dist}
Summary:Perl wrapper for the libzmq 3.x library
License:GPL+ or Artistic
@@ -59,6 +59,9 @@ make test
%changelog
+* Tue Nov 26 2013 Jose Pedro Oliveira jpo at di.uminho.pt - 1.14-1
+- Update to version 1.14
+
* Sun Aug 04 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.13-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
diff --git a/sources b/sources
index 3c5582e..29e306f 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-84ec02f16a9de6b3e284883514a2d712 ZMQ-LibZMQ3-1.13.tar.gz
+87f6fa1231a878ca6b3beed88eb8ece7 ZMQ-LibZMQ3-1.14.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 Pod-Markdown-1.500.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-Pod-Markdown: 1d485b736ec62127748b65b2d6866f31 Pod-Markdown-1.500.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-Pod-Markdown] 1.500 bump
commit 6b9d90790251722b326c1024a72c114c0d44ede1
Author: Petr Písař ppi...@redhat.com
Date: Tue Nov 26 12:13:40 2013 +0100
1.500 bump
.gitignore |1 +
.rpmlint |2 ++
perl-Pod-Markdown.spec | 24 +---
sources|2 +-
4 files changed, 17 insertions(+), 12 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 0bce20d..25d46aa 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,3 +2,4 @@
/Pod-Markdown-1.321.tar.gz
/Pod-Markdown-1.322.tar.gz
/Pod-Markdown-1.401.tar.gz
+/Pod-Markdown-1.500.tar.gz
diff --git a/.rpmlint b/.rpmlint
new file mode 100644
index 000..15b4f3c
--- /dev/null
+++ b/.rpmlint
@@ -0,0 +1,2 @@
+from Config import *
+addFilter(spelling-error .* subclasses);
diff --git a/perl-Pod-Markdown.spec b/perl-Pod-Markdown.spec
index d707c1c..4687194 100644
--- a/perl-Pod-Markdown.spec
+++ b/perl-Pod-Markdown.spec
@@ -1,5 +1,5 @@
Name: perl-Pod-Markdown
-Version:1.401
+Version:1.500
Release:1%{?dist}
Summary:Convert POD to Markdown
License:GPL+ or Artistic
@@ -7,22 +7,23 @@ Group: Development/Libraries
URL:http://search.cpan.org/dist/Pod-Markdown/
Source0:
http://www.cpan.org/authors/id/R/RW/RWSTAUNER/Pod-Markdown-%{version}.tar.gz
BuildArch: noarch
-BuildRequires: perl = 0:5.008
+BuildRequires: perl
BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(strict)
+BuildRequires: perl(warnings)
+# Run-time:
+BuildRequires: perl(parent)
+BuildRequires: perl(Pod::ParseLink) = 1.10
+BuildRequires: perl(Pod::Parser) = 1.51
+# Tests:
BuildRequires: perl(File::Spec)
BuildRequires: perl(File::Spec::Functions)
BuildRequires: perl(File::Temp)
-BuildRequires: perl(IPC::Open3)
BuildRequires: perl(IO::Handle)
+BuildRequires: perl(IPC::Open3)
BuildRequires: perl(List::Util)
-BuildRequires: perl(parent)
-BuildRequires: perl(Pod::ParseLink) = 1.10
-BuildRequires: perl(Pod::Parser) = 1.51
-BuildRequires: perl(strict)
BuildRequires: perl(Test::Differences)
BuildRequires: perl(Test::More) = 0.88
-BuildRequires: perl(Test::Script) = 1.05
-BuildRequires: perl(warnings)
Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
%description
@@ -37,9 +38,7 @@ make %{?_smp_mflags}
%install
make pure_install DESTDIR=$RPM_BUILD_ROOT
-
find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \;
-
%{_fixperms} $RPM_BUILD_ROOT/*
%check
@@ -52,6 +51,9 @@ make test
%{_bindir}/*
%changelog
+* Tue Nov 26 2013 Petr Pisar ppi...@redhat.com - 1.500-1
+- 1.500 bump
+
* Wed Nov 06 2013 Jitka Plesnikova jples...@redhat.com - 1.401-1
- 1.401 bump
diff --git a/sources b/sources
index bdc5987..b6192f0 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-cd03d67c143bc650d71fd5459b79c0b9 Pod-Markdown-1.401.tar.gz
+1d485b736ec62127748b65b2d6866f31 Pod-Markdown-1.500.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 1034104] perl-Pod-Markdown-1.500 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1034104 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-Pod-Markdown-1.500-1.f ||c21 Resolution|--- |RAWHIDE Last Closed||2013-11-26 06:24:05 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Nv3UGbOkula=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-PlRPC] Document the Storable and encryption is not secure
commit b9497b8d780a54ff5be6661c5f24d70135e0bb79
Author: Petr Písař ppi...@redhat.com
Date: Tue Nov 26 14:08:09 2013 +0100
Document the Storable and encryption is not secure
...urity-notice-on-Storable-and-reply-attack.patch | 105
perl-PlRPC.spec|9 ++-
2 files changed, 113 insertions(+), 1 deletions(-)
---
diff --git
a/perl-PlRPC-0.2020-Security-notice-on-Storable-and-reply-attack.patch
b/perl-PlRPC-0.2020-Security-notice-on-Storable-and-reply-attack.patch
new file mode 100644
index 000..877e7bc
--- /dev/null
+++ b/perl-PlRPC-0.2020-Security-notice-on-Storable-and-reply-attack.patch
@@ -0,0 +1,105 @@
+From 29f5ad4805a04e4c4fd18795f7153798c80a46ce Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= ppi...@redhat.com
+Date: Mon, 18 Nov 2013 12:20:52 +0100
+Subject: [PATCH] Security notice on Storable and reply attack
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Signed-off-by: Petr Písař ppi...@redhat.com
+---
+ README | 16
+ lib/RPC/PlServer.pm | 15 +++
+ 2 files changed, 31 insertions(+)
+
+diff --git a/README b/README
+index 8a68657..48a33e4 100644
+--- a/README
b/README
+@@ -204,6 +204,7 @@ EXAMPLE
+ require RPC::PlServer;
+ require MD5;
+
++
+ package MD5_Server; # Clients need to request application
+ # MD5_Server
+
+@@ -245,6 +246,10 @@ SECURITY
+ that I missed something. Security was a design goal, but not *the*
+ design goal. (A well known problem ...)
+
++Due to implementation of PlRPC, it's hard to use internal authentication
++mechanisms properly to achieve secured remote calls. Therefore users are
++advised to use an external authentication mechanism like TLS or IPsec.
++
+ I highly recommend the following design principles:
+
+ Protection against trusted users
+@@ -263,6 +268,14 @@ SECURITY
+ Be restrictive
+ Think twice, before you give a client access to a method.
+
++Use of Storable
++Storable module used for serialization and deserialization
++underneath is inherently insecure. Deserialized data can contain
++objects which lead to loading foreign modules and executing possible
++attached destructors. Do not accept host-based unauthorized
++connections. The Storable module is exercised before checking user
++password.
++
+ perlsec
+ And just in case I forgot it: Read the perlsec man page. :-)
+
+@@ -283,6 +296,9 @@ SECURITY
+ authorized, you should switch to a user based key. See the
+ DBI::ProxyServer for an example.
+
++Please note PlRPC encryption does not protect from reply attacks.
++You should have implement it on the application or the cipher level.
++
+ AUTHOR AND COPYRIGHT
+ The PlRPC-modules are
+
+diff --git a/lib/RPC/PlServer.pm b/lib/RPC/PlServer.pm
+index 10b56c9..ce38594 100644
+--- a/lib/RPC/PlServer.pm
b/lib/RPC/PlServer.pm
+@@ -613,6 +613,10 @@ I did my best to avoid security problems, but it is more
than likely,
+ that I missed something. Security was a design goal, but not *the*
+ design goal. (A well known problem ...)
+
++Due to implementation of PlRPC, it's hard to use internal authentication
++mechanisms properly to achieve secured remote calls. Therefore users are
++advised to use an external authentication mechanism like TLS or IPsec.
++
+ I highly recommend the following design principles:
+
+ =head2 Protection against trusted users
+@@ -637,6 +641,14 @@ object handle is valid before coercing a method on it.
+
+ Think twice, before you give a client access to a method.
+
++=item Use of Storable
++
++LStorable module used for serialization and deserialization underneath is
++inherently insecure. Deserialized data can contain objects which lead to
++loading foreign modules and executing possible attached destructors. Do not
++accept host-based unauthorized connections. The LStorable module is
++exercised before checking user password.
++
+ =item perlsec
+
+ And just in case I forgot it: Read the Cperlsec man page. :-)
+@@ -667,6 +679,9 @@ login phase, where to use a host based key. As soon as the
user
+ has authorized, you should switch to a user based key. See the
+ DBI::ProxyServer for an example.
+
++Please note PlRPC encryption does not protect from reply attacks. You should
++have implement it on the application or the cipher level.
++
+ =back
+
+ =head1 AUTHOR AND COPYRIGHT
+--
+1.8.3.1
+
diff --git a/perl-PlRPC.spec b/perl-PlRPC.spec
index 597550d..63997b3 100644
--- a/perl-PlRPC.spec
+++ b/perl-PlRPC.spec
@@ -1,6 +1,6 @@
Name: perl-PlRPC
Version:0.2020
-Release:15%{?dist}
+Release:16%{?dist}
License:GPL+ or Artistic
Group: Development/Libraries
Summary:Interface for writing PlRPC clients and servers
@@ -8,6 +8,9 @@ Url:
File Readonly-1.04.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-Readonly: 875c911ed43d0ecf2c5abed60ee6ae18 Readonly-1.04.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-DBI] Add a security warning about use of RPC::PlClient
commit 63844185cea5650895489e8d5a27101fea1d6e9e
Author: Petr Písař ppi...@redhat.com
Date: Tue Nov 26 14:33:11 2013 +0100
Add a security warning about use of RPC::PlClient
DBI-1.630-Security-notice-for-Proxy.patch | 55 +
perl-DBI.spec |8 -
2 files changed, 62 insertions(+), 1 deletions(-)
---
diff --git a/DBI-1.630-Security-notice-for-Proxy.patch
b/DBI-1.630-Security-notice-for-Proxy.patch
new file mode 100644
index 000..f79b352
--- /dev/null
+++ b/DBI-1.630-Security-notice-for-Proxy.patch
@@ -0,0 +1,55 @@
+From cd8fcbbf402e1d70c9f325f8b0fcd99e02cf14be Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= ppi...@redhat.com
+Date: Mon, 18 Nov 2013 12:52:09 +0100
+Subject: [PATCH] Security notice for Proxy
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+PlRPC is not secure due to Storable. Warn Proxy users about it.
+
+Signed-off-by: Petr Písař ppi...@redhat.com
+---
+ lib/DBD/Proxy.pm | 7 +++
+ lib/DBI/ProxyServer.pm | 7 +++
+ 2 files changed, 14 insertions(+)
+
+diff --git a/lib/DBD/Proxy.pm b/lib/DBD/Proxy.pm
+index 287b2dc..5948255 100644
+--- a/lib/DBD/Proxy.pm
b/lib/DBD/Proxy.pm
+@@ -974,6 +974,13 @@ The workaround is storing the modified local copy back to
the server:
+ $dbh-{csv_tables} = $tables;
+
+
++=head1 SECURITY WARNING
++
++LRPC::PlClient used underneath is not secure due to serializing and
++deserializing data with LStorable module. Use the proxy driver only in
++trusted environment.
++
++
+ =head1 AUTHOR AND COPYRIGHT
+
+ This module is Copyright (c) 1997, 1998
+diff --git a/lib/DBI/ProxyServer.pm b/lib/DBI/ProxyServer.pm
+index 68ad4af..78a0d78 100644
+--- a/lib/DBI/ProxyServer.pm
b/lib/DBI/ProxyServer.pm
+@@ -867,6 +867,13 @@ Don't try to put parameters into the sql-query like this:
+ =back
+
+
++=head1 SECURITY WARNING
++
++LRPC::PlServer used underneath is not secure due to serializing and
++deserializing data with LStorable module. Use the proxy driver only in
++trusted environment.
++
++
+ =head1 AUTHOR
+
+ Copyright (c) 1997Jochen Wiedmann
+--
+1.8.3.1
+
diff --git a/perl-DBI.spec b/perl-DBI.spec
index 4e87dcf..a009e9a 100644
--- a/perl-DBI.spec
+++ b/perl-DBI.spec
@@ -8,12 +8,14 @@
Name: perl-DBI
Version:1.630
-Release:1%{?dist}
+Release:2%{?dist}
Summary:A database access API for perl
Group: Development/Libraries
License:GPL+ or Artistic
URL:http://dbi.perl.org/
Source0:http://www.cpan.org/authors/id/T/TI/TIMB/DBI-%{version}.tar.gz
+# Add a security warning about use of RPC::PlClient, bug #1030578, CPAN
RT#90475
+Patch0: DBI-1.630-Security-notice-for-Proxy.patch
BuildRequires: perl
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(File::Find)
@@ -95,6 +97,7 @@ database interface independent of the actual database being
used.
%prep
%setup -q -n DBI-%{version}
+%patch0 -p1
iconv -f iso8859-1 -t utf-8 lib/DBD/Gofer.pm lib/DBD/Gofer.pm.new
mv lib/DBD/Gofer.pm{.new,}
chmod 644 ex/*
@@ -138,6 +141,9 @@ make test
%{_mandir}/man3/*.3*
%changelog
+* Tue Nov 26 2013 Petr Pisar ppi...@redhat.com - 1.630-2
+- Add a security warning about use of RPC::PlClient (bug #1030578)
+
* Tue Oct 29 2013 Jitka Plesnikova jples...@redhat.com - 1.630-1
- 1.630 bump
--
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-Readonly] Update to 1.04
commit a342c6972eeadba1d6800c4c5c35d8bec2ca3f1d
Author: Paul Howarth p...@city-fan.org
Date: Tue Nov 26 13:44:21 2013 +
Update to 1.04
- New upstream release 1.04
- Module now maintained by Sanko Robinson; please see TODO for a possible
set
of changes to this module that may affect code written for old, pre-perl
5.14.0 platforms!
- This release by SANKO - update source URL
- Switch to Module::Build flow
- Update shellbang patch
- Modernize spec since EPEL 7 will never have buildreq CPAN::Meta
- Drop obsoletes/provides for old -tests subpackage
.gitignore |2 +-
...preter.patch = Readonly-1.04-interpreter.patch | 44 +++---
perl-Readonly.spec | 59 +++-
sources|2 +-
4 files changed, 57 insertions(+), 50 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index a18cd64..197bacb 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1 @@
-Readonly-1.03.tar.gz
+/Readonly-[0-9.]*.tar.gz
diff --git a/Readonly-1.03-interpreter.patch b/Readonly-1.04-interpreter.patch
similarity index 72%
rename from Readonly-1.03-interpreter.patch
rename to Readonly-1.04-interpreter.patch
index ba3a812..98739a2 100644
--- a/Readonly-1.03-interpreter.patch
+++ b/Readonly-1.04-interpreter.patch
@@ -3,86 +3,86 @@
@@ -1,4 +1,4 @@
-#!perl -I..
+#!/usr/bin/perl -I..
-
# Readonly array tests
-
+ use strict;
+ use Test::More tests = 23;
--- t/deepa.t
+++ t/deepa.t
@@ -1,4 +1,4 @@
-#!perl -I..
+#!/usr/bin/perl -I..
-
# Test Array vs Array1 functionality
-
+ use strict;
+ use Test::More tests = 13;
--- t/deeph.t
+++ t/deeph.t
@@ -1,4 +1,4 @@
-#!perl -I..
+#!/usr/bin/perl -I..
-
# Test Hash vs Hash1 functionality
-
+ use strict;
+ use Test::More tests = 13;
--- t/deeps.t
+++ t/deeps.t
@@ -1,4 +1,4 @@
-#!perl -I..
+#!/usr/bin/perl -I..
-
# Test Scalar vs Scalar1 functionality
-
+ use strict;
+ use Test::More tests = 21;
--- t/docs.t
+++ t/docs.t
@@ -1,4 +1,4 @@
-#!perl -I..
+#!/usr/bin/perl -I..
-
# Examples from the docs -- make sure they work!
-
+ use strict;
+ use Test::More tests = 22;
--- t/export.t
+++ t/export.t
@@ -1,4 +1,4 @@
-#!perl -I..
+#!/usr/bin/perl -I..
-
# Readonly hash tests
-
+ use strict;
+ use Test::More tests = 1;
--- t/hash.t
+++ t/hash.t
@@ -1,4 +1,4 @@
-#!perl -I..
+#!/usr/bin/perl -I..
-
# Readonly hash tests
-
+ use strict;
+ use Test::More tests = 20;
--- t/readonly.t
+++ t/readonly.t
@@ -1,4 +1,4 @@
-#!perl -I..
+#!/usr/bin/perl -I..
-
# Test the Readonly function
-
+ use strict;
+ use Test::More tests = 19;
--- t/reassign.t
+++ t/reassign.t
@@ -1,4 +1,4 @@
-#!perl -I..
+#!/usr/bin/perl -I..
-
# Readonly reassignment-prevention tests
-
+ use strict;
+ use Test::More tests = 22;
--- t/scalar.t
+++ t/scalar.t
@@ -1,4 +1,4 @@
-#!perl -I..
+#!/usr/bin/perl -I..
-
# Readonly scalar tests
-
+ use strict;
+ use Test::More tests = 12;
--- t/tie.t
+++ t/tie.t
@@ -1,4 +1,4 @@
-#!perl -I..
+#!/usr/bin/perl -I..
-
# Test the Readonly function
-
+ use strict;
+ use Test::More tests = 4;
diff --git a/perl-Readonly.spec b/perl-Readonly.spec
index 2455776..eb94f00 100644
--- a/perl-Readonly.spec
+++ b/perl-Readonly.spec
@@ -1,29 +1,34 @@
Name: perl-Readonly
-Version: 1.03
-Release: 24%{?dist}
+Version: 1.04
+Release: 1%{?dist}
Summary: Facility for creating read-only scalars, arrays, hashes
Group: Development/Libraries
License: GPL+ or Artistic
URL: http://search.cpan.org/dist/Readonly/
-Source0:
http://search.cpan.org/CPAN/authors/id/R/RO/ROODE/Readonly-%{version}.tar.gz
-Patch0:Readonly-1.03-interpreter.patch
-BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(id -nu)
+Source0:
http://search.cpan.org/CPAN/authors/id/S/SA/SANKO/Readonly-%{version}.tar.gz
+Patch0:Readonly-1.04-interpreter.patch
BuildArch: noarch
+# Module Build
+BuildRequires: perl(CPAN::Meta)
+BuildRequires: perl(CPAN::Meta::Prereqs)
+BuildRequires: perl(File::Basename)
+BuildRequires: perl(File::Spec)
+BuildRequires: perl(Module::Build)
+BuildRequires: perl(utf8)
+BuildRequires: perl(warnings)
+# Module Runtime
BuildRequires: perl(Carp)
BuildRequires: perl(Exporter)
-BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(strict)
-BuildRequires: perl(Test::More)
BuildRequires: perl(vars)
+# Test Suite
+BuildRequires: perl(Test::More)
+# Runtime
Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
Requires: perl(Carp)
# Speed it up since we can
Requires: perl(Readonly::XS)
-# Obsolete/provide old -tests subpackage (can be removed in F19 development
cycle)
-Obsoletes: perl-Readonly-tests %{version}-%{release}
-Provides: perl-Readonly-tests = %{version}-%{release}
-
[perl-Readonly] Created tag perl-Readonly-1.04-1.fc21
The lightweight tag 'perl-Readonly-1.04-1.fc21' was created pointing to: a342c69... Update to 1.04 -- 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 NetPacket-1.4.3.tar.gz uploaded to lookaside cache by jpo
A file has been added to the lookaside cache for perl-NetPacket: 9ca7dfe00957a3bcb54f3bb10671eaef NetPacket-1.4.3.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 IO-Socket-SSL-1.961.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-IO-Socket-SSL: 37e02a0f553beff38869d2fa308860db IO-Socket-SSL-1.961.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-NetPacket] Update to 1.4.3
commit b40cc695ab480c4198299ef09c356c1c349477e7
Author: Jose Pedro Oliveira j...@di.uminho.pt
Date: Tue Nov 26 15:55:03 2013 +
Update to 1.4.3
.gitignore |1 +
perl-NetPacket.spec |5 -
sources |2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 230bbba..a9e645a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -8,3 +8,4 @@
/NetPacket-1.4.0.tar.gz
/NetPacket-1.4.1.tar.gz
/NetPacket-1.4.2.tar.gz
+/NetPacket-1.4.3.tar.gz
diff --git a/perl-NetPacket.spec b/perl-NetPacket.spec
index 874b90e..0831b6e 100644
--- a/perl-NetPacket.spec
+++ b/perl-NetPacket.spec
@@ -1,5 +1,5 @@
Name: perl-NetPacket
-Version:1.4.2
+Version:1.4.3
Release:1%{?dist}
Summary:Assemble/disassemble network packets at the protocol level
License:Artistic 2.0
@@ -50,6 +50,9 @@ rm -rf $RPM_BUILD_ROOT
%{_mandir}/man3/*
%changelog
+* Tue Nov 26 2013 Jose Pedro Oliveira jpo at di.uminho.pt - 1.4.3-1
+- Update to 1.4.3
+
* Thu Sep 26 2013 Jose Pedro Oliveira jpo at di.uminho.pt - 1.4.2-1
- Update to 1.4.2
diff --git a/sources b/sources
index ce87682..71b9de1 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-617348362205a18c6053b47d047b07e0 NetPacket-1.4.2.tar.gz
+9ca7dfe00957a3bcb54f3bb10671eaef NetPacket-1.4.3.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Socket-SSL] Update to 1.961
commit c150007ab90652e50ea3fcfb5ff8226115f941e1
Author: Paul Howarth p...@city-fan.org
Date: Tue Nov 26 15:55:35 2013 +
Update to 1.961
- New upstream release 1.961
- IO::Socket::SSL::Utils::CERT_create can now create CA-certificates that
are not self-signed (by giving issuer_*)
perl-IO-Socket-SSL.spec |7 ++-
sources |2 +-
2 files changed, 7 insertions(+), 2 deletions(-)
---
diff --git a/perl-IO-Socket-SSL.spec b/perl-IO-Socket-SSL.spec
index c448bfa..32030e3 100644
--- a/perl-IO-Socket-SSL.spec
+++ b/perl-IO-Socket-SSL.spec
@@ -1,5 +1,5 @@
Name: perl-IO-Socket-SSL
-Version: 1.960
+Version: 1.961
Release: 1%{?dist}
Summary: Perl library for transparent SSL
Group: Development/Libraries
@@ -70,6 +70,11 @@ rm -rf %{buildroot}
%{_mandir}/man3/IO::Socket::SSL::Utils.3pm*
%changelog
+* Tue Nov 26 2013 Paul Howarth p...@city-fan.org - 1.961-1
+- Update to 1.961
+ - IO::Socket::SSL::Utils::CERT_create can now create CA-certificates that
+are not self-signed (by giving issuer_*)
+
* Wed Nov 13 2013 Paul Howarth p...@city-fan.org - 1.960-1
- Update to 1.960
- Only documentation enhancements:
diff --git a/sources b/sources
index 17d800c..c1ac956 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-a66549aecfa2e9fc1eb6f7bcd29d1461 IO-Socket-SSL-1.960.tar.gz
+37e02a0f553beff38869d2fa308860db IO-Socket-SSL-1.961.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 Math-NumSeq-67.tar.gz uploaded to lookaside cache by churchyard
A file has been added to the lookaside cache for perl-Math-NumSeq: 734b315dc880865380c18d329af5c2ba Math-NumSeq-67.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-NumSeq] New version 67 (#1030911)
commit 70843fc1a8b3d6ebc976a867da1c9f88ba290d6a
Author: Miro Hrončok m...@hroncok.cz
Date: Tue Nov 26 17:13:31 2013 +0100
New version 67 (#1030911)
.gitignore|1 +
perl-Math-NumSeq.spec |5 -
sources |2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 9b34b05..6869e53 100644
--- a/.gitignore
+++ b/.gitignore
@@ -4,3 +4,4 @@
/Math-NumSeq-64.tar.gz
/Math-NumSeq-65.tar.gz
/Math-NumSeq-66.tar.gz
+/Math-NumSeq-67.tar.gz
diff --git a/perl-Math-NumSeq.spec b/perl-Math-NumSeq.spec
index ef9bc7a..c20209f 100644
--- a/perl-Math-NumSeq.spec
+++ b/perl-Math-NumSeq.spec
@@ -1,5 +1,5 @@
Name: perl-Math-NumSeq
-Version:66
+Version:67
Release:1%{?dist}
Summary:Number sequences
License:GPLv3+
@@ -96,6 +96,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Tue Nov 26 2013 Miro Hrončok mhron...@redhat.com - 67-1
+- New version 67 (#1030911)
+
* Wed Oct 23 2013 Miro Hrončok mhron...@redhat.com - 66-1
- New version 66 (#1022678)
diff --git a/sources b/sources
index 417e09b..2d3b0b3 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-72b83ebaf2f7423183b2a340dfdb8712 Math-NumSeq-66.tar.gz
+734b315dc880865380c18d329af5c2ba Math-NumSeq-67.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Socket-SSL] Created tag perl-IO-Socket-SSL-1.961-1.fc21
The lightweight tag 'perl-IO-Socket-SSL-1.961-1.fc21' was created pointing to: c150007... Update to 1.961 -- 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 111 (#1030912)
commit 2a18677ffd7ad9b2c6b3bed076b400db9c151804
Author: Miro Hrončok m...@hroncok.cz
Date: Tue Nov 26 17:19:12 2013 +0100
New version 111 (#1030912)
.gitignore |1 +
perl-Math-PlanePath.spec |7 +--
sources |2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 6854a26..2d13ca6 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
/Math-PlanePath-98.tar.gz
/Math-PlanePath-105.tar.gz
/Math-PlanePath-110.tar.gz
+/Math-PlanePath-111.tar.gz
diff --git a/perl-Math-PlanePath.spec b/perl-Math-PlanePath.spec
index 4bd0d79..5a5b14a 100644
--- a/perl-Math-PlanePath.spec
+++ b/perl-Math-PlanePath.spec
@@ -1,5 +1,5 @@
Name: perl-Math-PlanePath
-Version:110
+Version:111
Release:1%{?dist}
Summary:Mathematical paths through the 2-D plane
License:GPLv3+
@@ -59,6 +59,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Tue Nov 26 2013 Miro Hrončok mhron...@redhat.com - 111-1
+- New version 111 (#1030912)
+
* Mon Sep 02 2013 Miro Hrončok mhron...@redhat.com - 110-1
- New upstream release
@@ -105,4 +108,4 @@ make test
- New release
* Sun Sep 23 2012 Miro Hrončok m...@hroncok.cz 88-1
-- Specfile autogenerated by cpanspec 1.78 adn revised.
+- Specfile autogenerated by cpanspec 1.78 and revised.
diff --git a/sources b/sources
index 8b0c0c9..b51ee1f 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-314a7766c1dcc0df7a65d9b6ccc03a02 Math-PlanePath-110.tar.gz
+40afd50f14dacf080213d7b59c8d421e Math-PlanePath-111.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 1030911] perl-Math-NumSeq-67 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1030911 Miro Hrončok mhron...@redhat.com changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |RAWHIDE Last Closed||2013-11-26 11:19:53 --- Comment #1 from Miro Hrončok mhron...@redhat.com --- http://koji.fedoraproject.org/koji/taskinfo?taskID=6227752 Let's keep this rawhide only unless needed by some other package. -- 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=7Y80bAEe1Ea=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Module-Build-WithXSpp] New version 0.14 (#1014201)
commit cb12aa5c997cacfcafd448aba781c58029c2f699
Author: Miro Hrončok m...@hroncok.cz
Date: Tue Nov 26 17:23:49 2013 +0100
New version 0.14 (#1014201)
.gitignore |1 +
perl-Module-Build-WithXSpp.spec |7 +--
sources |2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 0fc8da0..5780c99 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
/Module-Build-WithXSpp-0.12.tar.gz
/Module-Build-WithXSpp-0.13.tar.gz
+/Module-Build-WithXSpp-0.14.tar.gz
diff --git a/perl-Module-Build-WithXSpp.spec b/perl-Module-Build-WithXSpp.spec
index bd8597d..b0e8fe4 100644
--- a/perl-Module-Build-WithXSpp.spec
+++ b/perl-Module-Build-WithXSpp.spec
@@ -1,6 +1,6 @@
Name: perl-Module-Build-WithXSpp
-Version:0.13
-Release:3%{?dist}
+Version:0.14
+Release:1%{?dist}
Summary:XS++ enhanced flavor of Module::Build
License:GPL+ or Artistic
Group: Development/Libraries
@@ -49,6 +49,9 @@ easier to use for wrapping C++ using XS++ (ExtUtils::XSpp).
%{_mandir}/man3/*
%changelog
+* Tue Nov 26 2013 Miro Hrončok mhron...@redhat.com - 0.14-1
+- New version 0.14 (#1014201)
+
* Sat Aug 03 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 0.13-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
diff --git a/sources b/sources
index c927568..976bdfd 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-8e4f4ab5782d2916f182129d48172e10 Module-Build-WithXSpp-0.13.tar.gz
+f3d6ad08127f62eed9baef131870f450 Module-Build-WithXSpp-0.14.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 Module-Build-WithXSpp-0.14.tar.gz uploaded to lookaside cache by churchyard
A file has been added to the lookaside cache for perl-Module-Build-WithXSpp: f3d6ad08127f62eed9baef131870f450 Module-Build-WithXSpp-0.14.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 1030912] perl-Math-PlanePath-111 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1030912 Miro Hrončok mhron...@redhat.com changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |RAWHIDE Last Closed||2013-11-26 11:24:23 --- Comment #1 from Miro Hrončok mhron...@redhat.com --- http://koji.fedoraproject.org/koji/taskinfo?taskID=6227772 Let's keep this rawhide only unless needed by some other package. -- 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=qU3W9HN3r7a=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 1014201] perl-Module-Build-WithXSpp-0.14 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1014201 Miro Hrončok mhron...@redhat.com changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |RAWHIDE Last Closed||2013-11-26 11:25:11 --- Comment #1 from Miro Hrončok mhron...@redhat.com --- http://koji.fedoraproject.org/koji/taskinfo?taskID=6227803 Let's keep this rawhide only unless needed by some other package. -- 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=xf0Dbtg3FRa=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 849703] Regular Expression matching in signal handler causes side-effects
https://bugzilla.redhat.com/show_bug.cgi?id=849703 --- Comment #18 from Fedora Update System upda...@fedoraproject.org --- perl-5.16.3-245.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=ljuKKA4fYta=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 1028949] Locale::Maketext interpolating escaped backslashes improperly
https://bugzilla.redhat.com/show_bug.cgi?id=1028949 --- Comment #5 from Fedora Update System upda...@fedoraproject.org --- perl-5.16.3-245.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=jNy65ddNMKa=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 1030907] perl-Archive-Extract-0.70 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1030907 --- Comment #4 from Fedora Update System upda...@fedoraproject.org --- perl-Archive-Extract-0.70-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=11BlbA0gFMa=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 1031298] Missing perl(Return::Value) needed by the perl-Email-Send module-check
https://bugzilla.redhat.com/show_bug.cgi?id=1031298 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version||perl-Email-Send-2.199-2.fc1 ||9 Resolution|--- |ERRATA Last Closed||2013-11-26 23:36:37 --- Comment #6 from Fedora Update System upda...@fedoraproject.org --- perl-Email-Send-2.199-2.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=tl31hgpddoa=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 1031298] Missing perl(Return::Value) needed by the perl-Email-Send module-check
https://bugzilla.redhat.com/show_bug.cgi?id=1031298 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Fixed In Version|perl-Email-Send-2.199-2.fc1 |perl-Email-Send-2.199-2.fc1 |9 |8 --- Comment #7 from Fedora Update System upda...@fedoraproject.org --- perl-Email-Send-2.199-2.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=RKBJh0Je51a=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
