Re: Packaging changes for libev in Rawhide
On Fri, 2013-11-22 at 16:06 +0100, Kevin Kofler wrote: > Mathieu Bridon wrote: > > * Move the headers back to /usr/include, as upstream intended > > * Put the event.h header into a libev-libevent-devel subpackage, and > > make it Conflicts: libevent-devel (this is what Debian did) > > -1 > > Conflicts are evil, and this pointless conflict is very easily avoided by > moving the header to a subdirectory as the package now does. > > (I actually think that BOTH libev and libevent should use a subdirectory for > their headers. event.h is a very generic header name that doesn't belong in > /usr/include at all.) > > Upstream needs to comprehend that they cannot just spam their headers > directly into /usr/include; if they don't, we have no other choice than > moving them without their consent. As said before, I disagree, and I want to get our package back in line with upstream and other distros. That being said, there is another possibility: if you feel so strongly that our current packaging of libev is the way it should be and it shouldn't change, then please take the package, so I'm not at the receiving end of users' requests and confusion. I argued the point with upstream, they refuse it, I don't feel like arguing more about it. -- Mathieu -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
EPEL Fedora 5 updates-testing report
The following Fedora EPEL 5 Security updates need testing: Age URL 580 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5630/bugzilla-3.2.10-5.el5 94 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11276/ssmtp-2.61-21.el5 70 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11560/fail2ban-0.8.10-4.el5 34 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11893/libguestfs-1.20.12-1.el5 14 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12067/drupal7-context-3.1-1.el5 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12091/bip-0.8.9-1.el5 2 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12157/varnish-2.0.6-4.el5 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12159/389-ds-base-1.2.11.25-1.el5 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12169/gc-7.1-6.el5 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12174/drupal7-7.24-1.el5 The following builds have been pushed to Fedora EPEL 5 updates-testing 389-adminutil-1.1.19-1.el5 389-ds-base-1.2.11.25-1.el5 drupal7-7.24-1.el5 gc-7.1-6.el5 lhapdf-5.9.1-2.el5 Details about builds: 389-adminutil-1.1.19-1.el5 (FEDORA-EPEL-2013-12165) Utility library for 389 administration Update Information: Ticket #47415 "Manage certificates" crashes admin server ChangeLog: * Wed Nov 20 2013 Rich Megginson - 1.1.19-1 - Ticket #47415 "Manage certificates" crashes admin server - 8647ad8 fix compiler warnings - enhancements to test ticket 47415 * Mon Aug 19 2013 Rich Megginson - 1.1.18-1 - ee1ef81 add Eclipse generated files - Ticket #47486 - compiler warnings in adminutil, admin, dsgw - 77fd77a fix mem leak in admldapBuildInfoSSL when there is no password * Fri Apr 19 2013 Noriko Hosoi - 1.1.17-1 -bump version to 1.1.17 Resolves: Bug 856089 - slapi_ldap_bind() doesn't check bind results (Ticket 479 - Console logins fail intermittenly) Resolves: Bug 905266 - BIND operation result not checked properly in admin server and adminutil 389-ds-base-1.2.11.25-1.el5 (FEDORA-EPEL-2013-12159) 389 Directory Server (base) Update Information: Each release has bug fixes in addition to the CVE fix rebase to 1.2.11.24 ChangeLog: * Thu Nov 21 2013 Rich Megginson - 1.2.11.25-1 - Ticket #47605 CVE-2013-4485: DoS due to improper handling of ger attr searches - Ticket #47596 attrcrypt fails to find unlocked key - Revert "Ticket #47559 hung server - related to sasl and initialize" - Ticket #47585 Replication Failures related to skipped entries due to cleaned rids - Ticket #47581 - Winsync plugin segfault during incremental backoff (phase 2) - Ticket #47581 - Winsync plugin segfault during incremental backoff - Ticket 47577 - crash when removing entries from cache - Ticket #47559 hung server - related to sasl and initialize - fe52f44 ticket #47550 wip - Ticket #47550 logconv: failed logins: Use of uninitialized value in numeric comparison at logconv.pl line 949 - Ticket #47551 logconv: -V does not produce unindexed search report - Ticket 47517 - fix memory leak in ldbm_delete.c - Ticket #47488 - Users from AD sub OU does not sync to IPA - minor fixes for bdb 4.2/4.3 and mozldap - Tickets: 47510 & 47543 - 389 fails to build when using Mozldap * Tue Oct 15 2013 Rich Megginson - 1.2.11.23-3.1 - add mutex around ldap ssl functions/bind/unbind * Wed Oct 2 2013 Rich Megginson - 1.2.11.23-3 - bump version to rebuild again * Wed Oct 2 2013 Rich Megginson - 1.2.11.23-2 - forgot to bump the source version * Wed Oct 2 2013 Rich Megginson - 1.2.11.23-1 - Ticket #422 - 389-ds-base - Can't call method "getText" - Ticket 47509 - CLEANALLRUV doesnt run across all replicas - Ticket 47533 logconv: some stats do not work across server restarts - Ticket #47501 logconv.pl uses /var/tmp for BDB temp files - Ticket 47520 - Fix various issues with logconv.pl - Ticket #47387 - improve logconv.pl performance with large access logs - Ticket 47354 - Indexed search are logged with 'notes=U' in the access logs - Ticket 47461 - logconv.pl - Use of comma-less variable list is deprecated - Ticket 47447 - logconv.pl man page missing -m,-M,-B,-D - Ticket #47348 - add etimes to per second/minute stats - Ticket #47341 - logconv.pl -m time calculation is wrong - Ticket #47336 - logconv.pl -m not working for all stats - Ticket 611 - logconv.pl missing stats for StartTLS, LDAPI, and AUTOBIND - TIcket 419 -
EPEL Fedora 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 580 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5620/bugzilla-3.4.14-2.el6 94 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11274/ssmtp-2.61-21.el6 55 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11703/chicken-4.8.0.4-4.el6 36 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11865/quassel-0.9.1-1.el6 19 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12025/seamonkey-2.22-1.el6 14 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12064/drupal7-context-3.1-1.el6 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12079/bip-0.8.9-1.el6 8 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12040/python-djblets-0.7.23-1.el6,ReviewBoard-1.7.18-1.el6 8 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12102/moodle-2.4.7-1.el6 2 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12156/varnish-2.1.5-5.el6 2 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12154/mediawiki119-1.19.9-1.el6 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12171/drupal7-7.24-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing 389-adminutil-1.1.19-1.el6 ansible-1.4-1.el6 cloud-initramfs-tools-0.20-2.el6 cloud-utils-0.27-10.el6 drupal7-7.24-1.el6 glpi-0.83.9.1-5.el6 gofer-0.77-1.el6 lhapdf-5.9.1-2.el6 mom-0.3.2-6.el6 openstack-utils-2013.2-2.el6 php-Pimple-1.1.0-4.el6 php-pecl-http-2.0.0-1.el6 php-tcpdf-6.0.047-1.el6 Details about builds: 389-adminutil-1.1.19-1.el6 (FEDORA-EPEL-2013-12162) Utility library for 389 administration Update Information: Ticket #47415 "Manage certificates" crashes admin server mem leak, compiler warnings This relase fixes 2 bugs in login and bind. ChangeLog: * Wed Nov 20 2013 Rich Megginson - 1.1.19-1 - Ticket #47415 "Manage certificates" crashes admin server - 8647ad8 fix compiler warnings - enhancements to test ticket 47415 * Mon Aug 19 2013 Rich Megginson - 1.1.18-1 - ee1ef81 add Eclipse generated files - Ticket #47486 - compiler warnings in adminutil, admin, dsgw - 77fd77a fix mem leak in admldapBuildInfoSSL when there is no password * Fri Apr 19 2013 Noriko Hosoi - 1.1.17-1 -bump version to 1.1.17 Resolves: Bug 856089 - slapi_ldap_bind() doesn't check bind results (Ticket 479 - Console logins fail intermittenly) Resolves: Bug 905266 - BIND operation result not checked properly in admin server and adminutil ansible-1.4-1.el6 (FEDORA-EPEL-2013-12175) SSH-based configuration management, deployment, and task execution system Update Information: Update to 1.4 upstream version with tons of new modules and bugfixes. See http://blog.ansibleworks.com/2013/11/21/ansible-1-4-released/ and https://github.com/ansible/ansible/blob/devel/CHANGELOG.md for more information. ChangeLog: * Thu Nov 21 2013 Kevin Fenzi 1.4-1 - Update to 1.4 cloud-initramfs-tools-0.20-2.el6 (FEDORA-EPEL-2013-12173) Cloud image initramfs management utilities Update Information: various growroot fixes ChangeLog: * Mon Nov 18 2013 Juerg Haefliger - 0.20-2 - [1009172] dracut-modules-growroot does not enlarge /dev/mmcblk0 - [1016648] ARM guest on x86_64 fails to boot, /dev/vda3 does not exist * Fri Sep 13 2013 Juerg Haefliger - 0.20-1 - Rebase to upstream version 0.20ubuntu1. * Fri Sep 13 2013 Juerg Haefliger - 0.20-0.6.bzr85 - [1003153] Mark the 50growroot directory as owned by the package. * Sat Aug 3 2013 Fedora Release Engineering - 0.20-0.5.bzr85 - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild References: [ 1 ] Bug #1003153 - dracut growroot module leaves an empty directory around which breaks dracut https://bugzilla.redhat.com/show_bug.cgi?id=1003153 [ 2 ] Bug #1016648 - ARM guest on x86_64 fails to boot, mount: special device /dev/vda3 does not exist https://bugzilla.redhat.com/show_bug.cgi?id=1016648 [ 3 ] Bug #100
Re: Introduction
On Fri, Nov 22, 2013 at 5:54 PM, Alek Paunov wrote: > On 22.11.2013 14:58, Tako Schotanus wrote: >> >> So I'm completely new to this packaging business, I managed to piece >> together a SPEC file that results in an actually working RPM for our project >> and even Koji seems to accept it, but there's so much information to absorb >> that I'm feeling a bit out of my depth. (Our project being a programming >> language we're dealing with some difficult issues with respect to versioning >> and such, for now I've copied Java's with alternatives and such which might >> or not be a good idea). So if there are some friendly people here that can >> guide me through my first real submission that would be great! > > > I really don't know weather this idea is appropriate [*], but since Ceylon > development is github based anyway and Ceylon is a fresh new development > stack (according to Fedora.next terminology :-) ), what about new github > account: fstack-ceylon (Ceylon related packages for Fedora) containing > something like: > > gh:fstack-ceylon/ceylon/ceylon.spec > gh:fstack-ceylon/ecliplse-ceylon-ide/ecliplse-ceylon-ide.spec > ... etc > > formed in the same shape as the future dist-git repos (being drafts for > them) for all the incoming Ceylon SRPMs. > > You could then clone/commit there your current .spec drafts and receive > issues and pull requests containing packages improvements (e.g. with > pointers to relevant guidelines parts) if it turns out that such style of > community work on the specs seems efficient to the established packagers, > who already offered help. > > I imagine few additional pros: > - Ceylon stack packaging "story" collected under a github account can become > a visible guide for the new stacks Fedora integration (especially for the > potential contributors which are new to the tracking of the bugzilla.rh > packaging bugs and the other Fedora communication channels). > - the whole collection of the specs, when polished could be forked and > tweaked for other RPM based distributions. > > Kind Regards, > Alek > > [*] because 1) it seems that few voices are firmly against Fedora specific > work on github and 2) this would lead to some bug-tracking fragmentation > between github/bugzilla, but I hope the latter is more technical > (synchronization/indexing) issue. The issue tracker is optional on github, that would only leave the pull requests for fragmentation. > > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[389-devel] please review: Ticket 47525 - Allow memberOf to use an alternate config area
https://fedorahosted.org/389/ticket/47525/ https://fedorahosted.org/389/attachment/ticket/47525/0001-Ticket-47525-Allow-memberOf-to-use-an-alternate-conf.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
Re: Introduction
On 22.11.2013 14:58, Tako Schotanus wrote: So I'm completely new to this packaging business, I managed to piece together a SPEC file that results in an actually working RPM for our project and even Koji seems to accept it, but there's so much information to absorb that I'm feeling a bit out of my depth. (Our project being a programming language we're dealing with some difficult issues with respect to versioning and such, for now I've copied Java's with alternatives and such which might or not be a good idea). So if there are some friendly people here that can guide me through my first real submission that would be great! I really don't know weather this idea is appropriate [*], but since Ceylon development is github based anyway and Ceylon is a fresh new development stack (according to Fedora.next terminology :-) ), what about new github account: fstack-ceylon (Ceylon related packages for Fedora) containing something like: gh:fstack-ceylon/ceylon/ceylon.spec gh:fstack-ceylon/ecliplse-ceylon-ide/ecliplse-ceylon-ide.spec ... etc formed in the same shape as the future dist-git repos (being drafts for them) for all the incoming Ceylon SRPMs. You could then clone/commit there your current .spec drafts and receive issues and pull requests containing packages improvements (e.g. with pointers to relevant guidelines parts) if it turns out that such style of community work on the specs seems efficient to the established packagers, who already offered help. I imagine few additional pros: - Ceylon stack packaging "story" collected under a github account can become a visible guide for the new stacks Fedora integration (especially for the potential contributors which are new to the tracking of the bugzilla.rh packaging bugs and the other Fedora communication channels). - the whole collection of the specs, when polished could be forked and tweaked for other RPM based distributions. Kind Regards, Alek [*] because 1) it seems that few voices are firmly against Fedora specific work on github and 2) this would lead to some bug-tracking fragmentation between github/bugzilla, but I hope the latter is more technical (synchronization/indexing) issue. -- 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] Fedora Base Design Working Group (2013-11-22) meeting minutes and logs
Meeting ended Fri Nov 22 16:07:41 2013 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2013-11-22/fedora_base_design_working_group.2013-11-22-15.00.html Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2013-11-22/fedora_base_design_working_group.2013-11-22-15.00.txt Log: http://meetbot.fedoraproject.org/fedora-meeting/2013-11-22/fedora_base_design_working_group.2013-11-22-15.00.log.html Please remember to CC: meetingminu...@lists.fedoraproject.org on your summary/minutes email. Thanks & regards, Phil -- Philipp Knirsch | Tel.: +49-711-96437-470 Manager Core Services| Fax.: +49-711-96437-111 Red Hat GmbH | Email: Phil Knirsch 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: Introduction
Oops, and thanks to you too Michael, hadn't seen your message yet :) - Original Message - From: "Michael Cronenworth" To: "Development discussions related to Fedora" Sent: Friday, November 22, 2013 3:29:35 PM Subject: Re: Introduction Tako Schotanus wrote: > I'm Tako, a Software Engineer for Red Hat working on a new language, Ceylon > (http://ceylon-lang.org), that runs on top of the Java and Javascript VMs. We > just published out first 1.0.0 and although we already had RPMs (and ZIPs > and DEBs) that could be downloaded from our website for a while now we'd like > to add the package to the official Fedora repositories now that we're at > 1.0.0 (also because Ubuntu is working on getting the package into their repos > and as a RedHat sponsored project it would be weird if we didn't do the same > for Fedora, right?) Welcome! > > So I'm completely new to this packaging business, I managed to piece together > a SPEC file that results in an actually working RPM for our project and even > Koji seems to accept it, but there's so much information to absorb that I'm > feeling a bit out of my depth. (Our project being a programming language > we're dealing with some difficult issues with respect to versioning and such, > for now I've copied Java's with alternatives and such which might or not be a > good idea). So if there are some friendly people here that can guide me > through my first real submission that would be great! The package submission process is documented on the Fedora wiki. http://fedoraproject.org/wiki/Package_Review_Process Feel free to ask us any additional questions. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Introduction
Hi Tim, thanks for the info! I had already started on the first Wiki and got to the point where I was able to build with Koji. But the docs about requirements (naming, packaging, java etc) ... well that's a LOT to digest at once. Especially when it's only for a single package :) So I'm sure I'll appear on IRC with stupid noob questions! Thanks! -Tako - Original Message - From: "Tim St Clair" To: "Development discussions related to Fedora" Cc: "Fedora Big Data SIG" Sent: Friday, November 22, 2013 3:54:42 PM Subject: Re: Introduction Feel free to ping me on freenode #fedora-devel, or #fedora-bigdata. We've been doing a fair amount of packaging lately, and could offer up tips where needed. I often find the best starting point is here: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers You will want to also read: https://fedoraproject.org/wiki/Packaging:Java Cheers, Tim - Original Message - > From: "Tako Schotanus" > To: devel@lists.fedoraproject.org > Sent: Friday, November 22, 2013 6:58:03 AM > Subject: Introduction > > > Hi, > > I read that somebody wanting to be a package maintainer should introduce > themselves, well here goes. > > I'm Tako, a Software Engineer for Red Hat working on a new language, Ceylon > (http://ceylon-lang.org), that runs on top of the Java and Javascript VMs. > We just published out first 1.0.0 and although we already had RPMs (and > ZIPs and DEBs) that could be downloaded from our website for a while now > we'd like to add the package to the official Fedora repositories now that > we're at 1.0.0 (also because Ubuntu is working on getting the package into > their repos and as a RedHat sponsored project it would be weird if we didn't > do the same for Fedora, right?) > > So I'm completely new to this packaging business, I managed to piece together > a SPEC file that results in an actually working RPM for our project and even > Koji seems to accept it, but there's so much information to absorb that I'm > feeling a bit out of my depth. (Our project being a programming language > we're dealing with some difficult issues with respect to versioning and > such, for now I've copied Java's with alternatives and such which might or > not be a good idea). So if there are some friendly people here that can > guide me through my first real submission that would be great! > > Cheers, > > Tako Schotanus > Senior Software Developer > Ceylon Language Project > www.ceylon-lang.org > RedHat > > > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- Cheers, Tim -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Using git for patch management in Fedora
Richard W.M. Jones wrote: > Several packages are using git for patch management. eg: > > http://pkgs.fedoraproject.org/cgit/erlang.git/tree/erlang.spec#n46 > http://pkgs.fedoraproject.org/cgit/libguestfs.git/tree/libguestfs.spec?h=f20#n22 > http://pkgs.fedoraproject.org/cgit/qemu.git/tree/ > http://pkgs.fedoraproject.org/cgit/ocaml.git/tree/ocaml.spec#n16 Ewww, we need packaging guidelines banning this bizarre practice. I can see using git-am if you're backporting upstream patches from upstream git (though patch and thus %patchN is usually good enough for that, too), but for Fedora-specific patches, it's really the wrong tool for the job. > Some of these packages have invented home-brewed methods to generate > the Patch lines in the spec file, eg: > > http://pkgs.fedoraproject.org/cgit/erlang.git/tree/otp-get-patches.sh > http://pkgs.fedoraproject.org/cgit/libguestfs.git/tree/copy-patches.sh?h=f20 Ewww! Yuck! 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: Packaging changes for libev in Rawhide
+1 to everything kevin just said. Just because other folks are employing bad practices, doesn't mean we should. If that means dependent packages need to add an extra -I location, that is a far better solution then polluting & causing potential conflicts. Cheers, Tim - Original Message - > From: "Kevin Kofler" > To: devel@lists.fedoraproject.org > Sent: Friday, November 22, 2013 9:06:07 AM > Subject: Re: Packaging changes for libev in Rawhide > > Mathieu Bridon wrote: > > * Move the headers back to /usr/include, as upstream intended > > * Put the event.h header into a libev-libevent-devel subpackage, and > > make it Conflicts: libevent-devel (this is what Debian did) > > -1 > > Conflicts are evil, and this pointless conflict is very easily avoided by > moving the header to a subdirectory as the package now does. +1 > > (I actually think that BOTH libev and libevent should use a subdirectory for > their headers. event.h is a very generic header name that doesn't belong in > /usr/include at all.) > +1 > Upstream needs to comprehend that they cannot just spam their headers > directly into /usr/include; if they don't, we have no other choice than > moving them without their consent. > +1 > 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 -- Cheers, Tim -- 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: Using git for patch management in Fedora
Richard W.M. Jones wrote: > This recipe has worked for me for years. The patches are probably > implicitly ordered by their names (ie. 0001-...patch etc) I think they're actually ordered by their patch number in the specfile. 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: Packaging changes for libev in Rawhide
Mathieu Bridon wrote: > * Move the headers back to /usr/include, as upstream intended > * Put the event.h header into a libev-libevent-devel subpackage, and > make it Conflicts: libevent-devel (this is what Debian did) -1 Conflicts are evil, and this pointless conflict is very easily avoided by moving the header to a subdirectory as the package now does. (I actually think that BOTH libev and libevent should use a subdirectory for their headers. event.h is a very generic header name that doesn't belong in /usr/include at all.) Upstream needs to comprehend that they cannot just spam their headers directly into /usr/include; if they don't, we have no other choice than moving them without their consent. 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: Introduction
Feel free to ping me on freenode #fedora-devel, or #fedora-bigdata. We've been doing a fair amount of packaging lately, and could offer up tips where needed. I often find the best starting point is here: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers You will want to also read: https://fedoraproject.org/wiki/Packaging:Java Cheers, Tim - Original Message - > From: "Tako Schotanus" > To: devel@lists.fedoraproject.org > Sent: Friday, November 22, 2013 6:58:03 AM > Subject: Introduction > > > Hi, > > I read that somebody wanting to be a package maintainer should introduce > themselves, well here goes. > > I'm Tako, a Software Engineer for Red Hat working on a new language, Ceylon > (http://ceylon-lang.org), that runs on top of the Java and Javascript VMs. > We just published out first 1.0.0 and although we already had RPMs (and > ZIPs and DEBs) that could be downloaded from our website for a while now > we'd like to add the package to the official Fedora repositories now that > we're at 1.0.0 (also because Ubuntu is working on getting the package into > their repos and as a RedHat sponsored project it would be weird if we didn't > do the same for Fedora, right?) > > So I'm completely new to this packaging business, I managed to piece together > a SPEC file that results in an actually working RPM for our project and even > Koji seems to accept it, but there's so much information to absorb that I'm > feeling a bit out of my depth. (Our project being a programming language > we're dealing with some difficult issues with respect to versioning and > such, for now I've copied Java's with alternatives and such which might or > not be a good idea). So if there are some friendly people here that can > guide me through my first real submission that would be great! > > Cheers, > > Tako Schotanus > Senior Software Developer > Ceylon Language Project > www.ceylon-lang.org > RedHat > > > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- Cheers, Tim -- 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: File conflict when upgrading package
Mattias Ellert wrote:
> os.execute("rm -rf %{_datadir}/applications/%{name}.desktop")
Ewww… Using os.execute in Lua scriptlets is scary because the whole point of
writing them in Lua rather than shell is to avoid depending on stuff being
installed on the file system. Now in this case, you'll likely get away with
it because your scriptlet runs the rm only if the directory existed to begin
with, which is not the case in the "initial installation" use case where
things like rm are unavailable. Still, actually deleting things from within
Lua would be cleaner (but likely more work to do recursively, sure; it'd
help if RPM exported some rm_rf or so function to Lua scriptlets).
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: Introduction
Tako Schotanus wrote: I'm Tako, a Software Engineer for Red Hat working on a new language, Ceylon (http://ceylon-lang.org), that runs on top of the Java and Javascript VMs. We just published out first 1.0.0 and although we already had RPMs (and ZIPs and DEBs) that could be downloaded from our website for a while now we'd like to add the package to the official Fedora repositories now that we're at 1.0.0 (also because Ubuntu is working on getting the package into their repos and as a RedHat sponsored project it would be weird if we didn't do the same for Fedora, right?) Welcome! So I'm completely new to this packaging business, I managed to piece together a SPEC file that results in an actually working RPM for our project and even Koji seems to accept it, but there's so much information to absorb that I'm feeling a bit out of my depth. (Our project being a programming language we're dealing with some difficult issues with respect to versioning and such, for now I've copied Java's with alternatives and such which might or not be a good idea). So if there are some friendly people here that can guide me through my first real submission that would be great! The package submission process is documented on the Fedora wiki. http://fedoraproject.org/wiki/Package_Review_Process Feel free to ask us any additional questions. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [pkgdb2] call for testers, bug reports and RFE
On Fri, Nov 22, 2013 at 02:34:28PM +0100, Kevin Kofler wrote: > Miro Hrončok wrote: > > The reason is simple. Fedorahosted lacks features, is unplesant and need > > byrocracy even to create a repository. > > Creating a repository is actually the only time "bureaucracy" is required. > Giving write permissions just works over FAS. (There's a FAS group for every > repository that is created, the developer only needs to request group > membership through FAS and you can approve it, all self-service in FAS.) > Clones, commits, pushes etc. are plain git (or SVN or whatever you chose! > Fedorahosted is much more flexible than GitHub there) just as on GitHub or > anywhere else. A Trac site is automatically created along with the > repository if requested (you're expected to say in the repository request > whether you want Trac or not, normally you should always say "yes"), it has > bug trackers which work with FAS accounts (and Trac's issue tracker is no > worse than GitHub's, they're actually very similar), a repository browser, > and a wiki that you can edit (no "bureaucracy"). You also get a directory > for file releases below https://fedorahosted.org/releases/ that accepts SCP > uploads. > > I really don't see what is missing there, apart from missing automation for > the one-time creation process. You're forgeting, patch/code reviews, possibility to close or refer to a ticket from the git commit, the possibility to easily follow a project and be informed of its changes (yes, I know, you can create mailing list and have all the commits and action from the trac be sent to said list, I already do this for fedocal) and probably some more feature I'm forgetting. Anyway, did you see the link in the footer? The one that says 'pkgdb'? 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: Fedora 20 TC2 AMIs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/21/2013 03:13 PM, Vitaly Kuznetsov wrote: > Matthew Miller writes: > >> On Thu, Nov 21, 2013 at 01:30:15PM +0100, Vitaly Kuznetsov wrote: >>> I ran basic tests agains them and they're ok. The only issue I still >>> see is wrong SELinux context for several files: >>> >>> # restorecon -Rvn -e/dev -e/proc -e/sys -e/run -e/tmp/ / restorecon >>> reset /var/cache/yum context >>> system_u:object_r:file_t:s0->system_u:object_r:rpm_var_cache_t:s0 >>> restorecon reset /var/log/boot.log context >>> system_u:object_r:var_log_t:s0->system_u:object_r:plymouthd_var_log_t:s0 >>> >>> restorecon reset /boot/extlinux/ldlinux.sys context system_u:object_r:file_t:s0->system_u:object_r:boot_t:s0 >> >> That's weird. We're running fixfiles at the end of the build process to >> clean up anything like that. > > I looked into kickstart, you do '/usr/sbin/fixfiles -R -a restore'. I tried > running it manually on fresh instance: > > # /usr/sbin/fixfiles -R -a restore 75k/sbin/restorecon set context > /boot/extlinux/ldlinux.sys->system_u:object_r:boot_t:s0 failed:'Operation > not permitted' 80k/sbin/restorecon set context > /boot/extlinux/ldlinux.sys->system_u:object_r:boot_t:s0 failed:'Operation > not permitted' 177k/sbin/restorecon set context > /boot/extlinux/ldlinux.sys->system_u:object_r:boot_t:s0 failed:'Operation > not permitted' > > However /boot/extlinux/ldlinux.sys is the only file needs fixind after > this: > > # restorecon -Rvn -e/dev -e/proc -e/sys -e/run -e/tmp/ / restorecon reset > /boot/extlinux/ldlinux.sys context > system_u:object_r:file_t:s0->system_u:object_r:boot_t:s0 > > Anyway, https://bugzilla.redhat.com/show_bug.cgi?id=1033274 as suggested by > dwalsh) > Any change something is mounted on top of these files/directories when the fixfiles is run. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKPXq8ACgkQrlYvE4MpobPw7wCeMz5w3mGE9PRI+qRJxQTDmpK3 gzYAoN2VWaVI5iGpxkVN/vTA+JTfKWoh =WycT -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: [pkgdb2] call for testers, bug reports and RFE
Miro Hrončok wrote: > The reason is simple. Fedorahosted lacks features, is unplesant and need > byrocracy even to create a repository. Creating a repository is actually the only time "bureaucracy" is required. Giving write permissions just works over FAS. (There's a FAS group for every repository that is created, the developer only needs to request group membership through FAS and you can approve it, all self-service in FAS.) Clones, commits, pushes etc. are plain git (or SVN or whatever you chose! Fedorahosted is much more flexible than GitHub there) just as on GitHub or anywhere else. A Trac site is automatically created along with the repository if requested (you're expected to say in the repository request whether you want Trac or not, normally you should always say "yes"), it has bug trackers which work with FAS accounts (and Trac's issue tracker is no worse than GitHub's, they're actually very similar), a repository browser, and a wiki that you can edit (no "bureaucracy"). You also get a directory for file releases below https://fedorahosted.org/releases/ that accepts SCP uploads. I really don't see what is missing there, apart from missing automation for the one-time creation process. 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
[389-devel] Please review: Ticket #47527 - Allow referential integrity suffixes to be configurable
https://fedorahosted.org/389/ticket/47527 https://fedorahosted.org/389/attachment/ticket/47527/0001-Ticket-47527-Allow-referential-integrity-suffixes-to.patch -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Introduction
Hi, I read that somebody wanting to be a package maintainer should introduce themselves, well here goes. I'm Tako, a Software Engineer for Red Hat working on a new language, Ceylon (http://ceylon-lang.org), that runs on top of the Java and Javascript VMs. We just published out first 1.0.0 and although we already had RPMs (and ZIPs and DEBs) that could be downloaded from our website for a while now we'd like to add the package to the official Fedora repositories now that we're at 1.0.0 (also because Ubuntu is working on getting the package into their repos and as a RedHat sponsored project it would be weird if we didn't do the same for Fedora, right?) So I'm completely new to this packaging business, I managed to piece together a SPEC file that results in an actually working RPM for our project and even Koji seems to accept it, but there's so much information to absorb that I'm feeling a bit out of my depth. (Our project being a programming language we're dealing with some difficult issues with respect to versioning and such, for now I've copied Java's with alternatives and such which might or not be a good idea). So if there are some friendly people here that can guide me through my first real submission that would be great! Cheers, Tako Schotanus Senior Software Developer Ceylon Language Project www.ceylon-lang.org RedHat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
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-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
F-20 Branched report: 20131122 changes
Compose started at Fri Nov 22 09: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 [condor-wallaby] condor-wallaby-client-5.0.3-5.fc20.noarch requires python-qpid-qmf >= 0:0.9.1073306 [fence-agents] fence-agents-common-4.0.4-3.fc20.armv7hl requires pexpect [fts] fts-server-3.1.1-1.fc20.armv7hl requires libactivemq-cpp.so.14 [glpi] glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Version glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Stdlib glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-ServiceManager glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Loader glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-I18n glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Cache-apc glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Cache [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 [ipython] python-ipython-console-0.13.2-2.fc20.noarch requires pexpect python3-ipython-console-0.13.2-2.fc20.noarch requires python3-pexpect [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 [openlmi-providers] openlmi-0.4.0-1.fc20.noarch requires openlmi-power [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-requests-oauthlib] python-requests-oauthlib-0.4.0-2.fc20.noarch requires python-oauthlib [python-tag] python-tag-2013.1-1.fc20.armv7hl requires libboost_python.so.1.53.0 [qpid-cpp] qpid-cpp-server-ha-0.24-6.fc20.armv7hl requires qpid-qmf(armv7hl-32) qpid-tools-0.24-6.fc20.noarch requires python-qpid-qmf [rootplot] rootplot-2.2.1-7.fc19.noarch requires root-python [ruby-spqr] ruby-spqr-0.3.6-7.fc20.noarch requires ruby-qpid-qmf [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 [sigul] sigul-0.100-3.fc20.noarch requires pexpect [spacewalk-admin] spacewalk-admin-2.0.1-2.fc20.noarch requir
[Bug 1030908] perl-Archive-Zip-1.33 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1030908 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-Archive-Zip-1.33-1.fc2 ||1 Resolution|--- |RAWHIDE Last Closed||2013-11-22 07:40:46 -- 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=5cLfCGoQXe&a=cc_unsubscribe -- 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-Archive-Zip] 1.33 bump
commit 260f386668dc06443c8a23c1c4ddff1b6c21ca3c
Author: Jitka Plesnikova
Date: Fri Nov 22 13:35:04 2013 +0100
1.33 bump
.gitignore |1 +
Archive-Zip-cpan-rt-54827.patch | 12 ++--
perl-Archive-Zip.spec | 25 -
sources |2 +-
4 files changed, 28 insertions(+), 12 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index f3c9537..ab80062 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,2 @@
Archive-Zip-1.30.tar.gz
+/Archive-Zip-1.33.tar.gz
diff --git a/Archive-Zip-cpan-rt-54827.patch b/Archive-Zip-cpan-rt-54827.patch
index 9d78db7..e22477d 100644
--- a/Archive-Zip-cpan-rt-54827.patch
+++ b/Archive-Zip-cpan-rt-54827.patch
@@ -1,7 +1,7 @@
-diff -up Archive-Zip-1.30/lib/Archive/Zip/Member.pm.bug
Archive-Zip-1.30/lib/Archive/Zip/Member.pm
Archive-Zip-1.30/lib/Archive/Zip/Member.pm.bug 2009-06-30
13:51:10.0 +0200
-+++ Archive-Zip-1.30/lib/Archive/Zip/Member.pm 2012-03-19 13:13:11.028294275
+0100
-@@ -159,13 +159,13 @@ sub bitFlag {
+diff -up Archive-Zip-1.33/lib/Archive/Zip/Member.pm.orig
Archive-Zip-1.33/lib/Archive/Zip/Member.pm
+--- Archive-Zip-1.33/lib/Archive/Zip/Member.pm.orig2013-11-10
04:47:27.0 +0100
Archive-Zip-1.33/lib/Archive/Zip/Member.pm 2013-11-22 12:48:19.848476120
+0100
+@@ -167,13 +167,13 @@ sub bitFlag {
# Set General Purpose Bit Flags according to the desiredCompressionLevel
setting
if ( $self->desiredCompressionLevel == 1 ||
$self->desiredCompressionLevel == 2 ) {
@@ -16,5 +16,5 @@ diff -up Archive-Zip-1.30/lib/Archive/Zip/Member.pm.bug
Archive-Zip-1.30/lib/Arc
-$self->{'bitFlag'} = DEFLATING_COMPRESSION_MAXIMUM;
+$self->{'bitFlag'} |= DEFLATING_COMPRESSION_MAXIMUM;
}
- $self->{'bitFlag'};
- }
+
+ if ($Archive::Zip::UNICODE) {
diff --git a/perl-Archive-Zip.spec b/perl-Archive-Zip.spec
index f7263f8..0b6620a 100644
--- a/perl-Archive-Zip.spec
+++ b/perl-Archive-Zip.spec
@@ -1,35 +1,47 @@
Name: perl-Archive-Zip
-Version:1.30
-Release:13%{?dist}
+Version:1.33
+Release:1%{?dist}
Summary:Perl library for accessing Zip archives
Group: Development/Libraries
License:GPL+ or Artistic
URL:http://search.cpan.org/dist/Archive-Zip/
-Source0:
http://search.cpan.org/CPAN/authors/id/A/AD/ADAMK/Archive-Zip-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/P/PH/PHRED/Archive-Zip-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
#https://rt.cpan.org/Public/Bug/Display.html?id=54827
Patch0: Archive-Zip-cpan-rt-54827.patch
+BuildRequires: perl
+BuildRequires: perl(Config)
BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(strict)
# Run-time
+BuildRequires: perl(bytes)
BuildRequires: perl(Carp)
BuildRequires: perl(constant)
BuildRequires: perl(Cwd)
BuildRequires: perl(Compress::Raw::Zlib)
+BuildRequires: perl(Encode)
BuildRequires: perl(Exporter)
+BuildRequires: perl(File::Basename)
+BuildRequires: perl(File::Copy)
+BuildRequires: perl(File::Find)
BuildRequires: perl(File::Path)
BuildRequires: perl(File::Spec) >= 0.80
BuildRequires: perl(File::Temp)
+BuildRequires: perl(FileHandle)
+BuildRequires: perl(integer)
BuildRequires: perl(IO::File)
BuildRequires: perl(IO::Seekable)
BuildRequires: perl(Time::Local)
+BuildRequires: perl(vars)
# Tests
BuildRequires: perl(Data::Dumper)
BuildRequires: perl(File::Spec::Unix)
BuildRequires: perl(IO::Scalar)
BuildRequires: perl(Test::More)
+BuildRequires: perl(warnings)
BuildRequires: unzip
BuildRequires: zip
@@ -84,6 +96,9 @@ rm -rf $RPM_BUILD_ROOT
%changelog
+* Fri Nov 22 2013 Jitka Plesnikova - 1.33-1
+- 1.33 bump
+
* Sat Aug 03 2013 Fedora Release Engineering
- 1.30-13
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
@@ -139,7 +154,7 @@ rm -rf $RPM_BUILD_ROOT
* Fri Jan 11 2008 Tom "spot" Callaway - 1.20-4
- rebuild for new perl
-* Mon Aug 23 2007 Robin Norwood - 1.20-3
+* Thu Aug 23 2007 Robin Norwood - 1.20-3
- Fix license tag
* Wed Jun 27 2007 Robin Norwood - 1.20-2
@@ -171,7 +186,7 @@ rm -rf $RPM_BUILD_ROOT
* Thu Apr 14 2005 Jose Pedro Oliveira - 1.14-1
- Update to 1.14.
-* Fri Apr 7 2005 Michael Schwendt
+* Fri Apr 8 2005 Michael Schwendt
- rebuilt
* Sun Aug 15 2004 Ville Skyttä - 0:1.12-0.fdr.1
diff --git a/sources b/sources
index b920f72..bd10378 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-40153666e7538b410e001aa8a810e702 Archive-Zip-1.30.tar.gz
+b732d154306efc85260c9b47cb567d10 Archive-Zip-1.33.tar.gz
--
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
File Archive-Zip-1.33.tar.gz uploaded to lookaside cache by jplesnik
A file has been added to the lookaside cache for perl-Archive-Zip: b732d154306efc85260c9b47cb567d10 Archive-Zip-1.33.tar.gz -- 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-CPAN-Changes] Created tag perl-CPAN-Changes-0.26-1.fc21
The lightweight tag 'perl-CPAN-Changes-0.26-1.fc21' was created pointing to: 3668cf9... Update to 0.26 -- 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-CPAN-Changes] Update to 0.26
commit 3668cf9f79335445acaefbacbe477812b948ddc3
Author: Paul Howarth
Date: Fri Nov 22 11:58:14 2013 +
Update to 0.26
- New upstream release 0.26:
- Fix reference issues when adding a release (CPAN RT#90605)
perl-CPAN-Changes.spec |6 +-
sources|2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/perl-CPAN-Changes.spec b/perl-CPAN-Changes.spec
index 1d32d73..ff53ef7 100644
--- a/perl-CPAN-Changes.spec
+++ b/perl-CPAN-Changes.spec
@@ -1,6 +1,6 @@
Name: perl-CPAN-Changes
Summary: Read and write Changes files
-Version: 0.25
+Version: 0.26
Release: 1%{?dist}
License: GPL+ or Artistic
Group: Development/Libraries
@@ -61,6 +61,10 @@ make test TEST_FILES="$(echo $(find xt/ -name '*.t'))"
%{_mandir}/man3/Test::CPAN::Changes.3pm*
%changelog
+* Fri Nov 22 2013 Paul Howarth - 0.26-1
+- Update to 0.26:
+ - Fix reference issues when adding a release (CPAN RT#90605)
+
* Wed Oct 9 2013 Paul Howarth - 0.25-1
- Update to 0.25:
- Fix Dist::Zilla date parsing: now puts timezone data in note section
diff --git a/sources b/sources
index 00ec03d..f554a0a 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-f123c91e84b8c4596bb1542d20a5d36f CPAN-Changes-0.25.tar.gz
+5717e9f7e2a0ca490b53bbcaf4766734 CPAN-Changes-0.26.tar.gz
--
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
File CPAN-Changes-0.26.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-CPAN-Changes: 5717e9f7e2a0ca490b53bbcaf4766734 CPAN-Changes-0.26.tar.gz -- 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
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-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1033513] Retire perl-B-Keywords in EPEL6
https://bugzilla.redhat.com/show_bug.cgi?id=1033513 --- Comment #3 from Paul Howarth --- Indeed; this package pre-dates the introduction of the 0. prefix. At the time we went with a strategy of cloning the package from RHEL and building that. -- 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=TlEyTnD49V&a=cc_unsubscribe -- 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
[Bug 1033513] Retire perl-B-Keywords in EPEL6
https://bugzilla.redhat.com/show_bug.cgi?id=1033513 --- Comment #2 from Tuomo Soini --- In this case package should have build with 0. prefix for release number but that's not fixable any more. -- 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=LnbD0P2RDT&a=cc_unsubscribe -- 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
[Bug 1033521] Retire perl-Exception-Class in EPEL6
https://bugzilla.redhat.com/show_bug.cgi?id=1033521 Paul Howarth changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |NOTABUG Last Closed||2013-11-22 05:07:59 --- Comment #1 from Paul Howarth --- It's not available on all architectures and is therefore needed to satisfy dependencies on the architectures where it's not available directly in RHEL-6. This has been the case since EPEL-6 was started. See Bug #620416. -- 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=5NwjQTjgLa&a=cc_unsubscribe -- 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
[Bug 1033517] Retire perl-Devel-Cycle on EPEL6
https://bugzilla.redhat.com/show_bug.cgi?id=1033517 Paul Howarth changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |NOTABUG Last Closed||2013-11-22 05:05:25 --- Comment #1 from Paul Howarth --- It's not available on all architectures and is therefore needed to satisfy dependencies on the architectures where it's not available directly in RHEL-6. This has been the case since EPEL-6 was started. See Bug #620410. -- 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=uCpF8GYQkZ&a=cc_unsubscribe -- 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
[Bug 1033521] New: Retire perl-Exception-Class in EPEL6
https://bugzilla.redhat.com/show_bug.cgi?id=1033521 Bug ID: 1033521 Summary: Retire perl-Exception-Class in EPEL6 Product: Fedora EPEL Version: el6 Component: perl-Exception-Class Severity: medium Assignee: p...@city-fan.org Reporter: t...@foobar.fi QA Contact: extras...@fedoraproject.org CC: p...@city-fan.org, perl-de...@lists.fedoraproject.org, st...@silug.org Description of problem: perl-Exception-Class is part of rhel6 so it must be retired from epel6. -- 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=3lgbjV0xms&a=cc_unsubscribe -- 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
[Bug 1033513] Retire perl-B-Keywords in EPEL6
https://bugzilla.redhat.com/show_bug.cgi?id=1033513 Paul Howarth changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |NOTABUG Last Closed||2013-11-22 05:02:55 --- Comment #1 from Paul Howarth --- It's not available on all architectures and is therefore needed to satisfy dependencies on the architectures where it's not available directly in RHEL-6. This has been the case since EPEL-6 was started. See Bug #620421. -- 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=CIevCmtVX2&a=cc_unsubscribe -- 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
[Bug 1033519] New: Retire perl-Email-Date-Format in EPEL6
https://bugzilla.redhat.com/show_bug.cgi?id=1033519 Bug ID: 1033519 Summary: Retire perl-Email-Date-Format in EPEL6 Product: Fedora EPEL Version: el6 Component: perl-Email-Date-Format Severity: medium Assignee: tcall...@redhat.com Reporter: t...@foobar.fi QA Contact: extras...@fedoraproject.org CC: perl-de...@lists.fedoraproject.org, tcall...@redhat.com Description of problem: perl-Email-Date-Format is part of rhel6 so it must be retired in epel6. -- 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=YkKtaVU5GH&a=cc_unsubscribe -- 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
[Bug 1033517] New: Retire perl-Devel-Cycle on EPEL6
https://bugzilla.redhat.com/show_bug.cgi?id=1033517 Bug ID: 1033517 Summary: Retire perl-Devel-Cycle on EPEL6 Product: Fedora EPEL Version: el6 Component: perl-Devel-Cycle Severity: medium Assignee: p...@city-fan.org Reporter: t...@foobar.fi QA Contact: extras...@fedoraproject.org CC: p...@city-fan.org, perl-de...@lists.fedoraproject.org Description of problem: perl-Devel-Cycle is part of rhel6 so it must be retired from epel6. -- 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=FNrFQQqEfk&a=cc_unsubscribe -- 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
[Bug 1033516] New: Retire perl-Class-Trigger in EPEL6
https://bugzilla.redhat.com/show_bug.cgi?id=1033516 Bug ID: 1033516 Summary: Retire perl-Class-Trigger in EPEL6 Product: Fedora EPEL Version: el6 Component: perl-Class-Trigger Severity: medium Assignee: tcall...@redhat.com Reporter: t...@foobar.fi QA Contact: extras...@fedoraproject.org CC: perl-de...@lists.fedoraproject.org, tcall...@redhat.com, trem...@tremble.org.uk Description of problem: perl-Class-Trigger is part of rhel6 so it must be retired on epel6. -- 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=iQINxQDqYL&a=cc_unsubscribe -- 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-DBD-ODBC] Modified sources.
commit 8d529fb60590e5898416b943bcc18ded2e44834c Author: Jan Holcapek Date: Fri Nov 22 10:58:06 2013 +0100 Modified sources. sources |1 + 1 files changed, 1 insertions(+), 0 deletions(-) --- diff --git a/sources b/sources index e69de29..694e441 100644 --- a/sources +++ b/sources @@ -0,0 +1 @@ +3c750cde8e39fbba804043485f18ba68 DBD-ODBC-1.45.tar.gz -- 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
[Bug 1033515] New: Retire perl-Class-Data-Inheritable in EPEL6
https://bugzilla.redhat.com/show_bug.cgi?id=1033515 Bug ID: 1033515 Summary: Retire perl-Class-Data-Inheritable in EPEL6 Product: Fedora EPEL Version: el6 Component: perl-Class-Data-Inheritable Severity: medium Assignee: tcall...@redhat.com Reporter: t...@foobar.fi QA Contact: extras...@fedoraproject.org CC: perl-de...@lists.fedoraproject.org, tcall...@redhat.com, trem...@tremble.org.uk Description of problem: perl-Class-Data-Inheritable is part of rhel6 so it must be retired in epel6. -- 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=gzxmxJrR9E&a=cc_unsubscribe -- 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
[Bug 1033514] New: Retire perl-Class-Accessor in EPEL6
https://bugzilla.redhat.com/show_bug.cgi?id=1033514 Bug ID: 1033514 Summary: Retire perl-Class-Accessor in EPEL6 Product: Fedora EPEL Version: el6 Component: perl-Class-Accessor Severity: medium Assignee: tcall...@redhat.com Reporter: t...@foobar.fi QA Contact: extras...@fedoraproject.org CC: perl-de...@lists.fedoraproject.org, tcall...@redhat.com, trem...@tremble.org.uk Description of problem: perl-Class-Accessor is part of rhel6 now so it must be retired in epel6 -- 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=rVvSbt9UPm&a=cc_unsubscribe -- 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
[Bug 1033513] New: Retire perl-B-Keywords in EPEL6
https://bugzilla.redhat.com/show_bug.cgi?id=1033513 Bug ID: 1033513 Summary: Retire perl-B-Keywords in EPEL6 Product: Fedora EPEL Version: el6 Component: perl-B-Keywords Severity: medium Assignee: p...@city-fan.org Reporter: t...@foobar.fi QA Contact: extras...@fedoraproject.org CC: p...@city-fan.org, perl-de...@lists.fedoraproject.org Description of problem: perl-B-Keywords is part of rhel6 so it must be retired in epel6. -- 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=Uh5vjAjuKG&a=cc_unsubscribe -- 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-DBD-ODBC] Initial import (#1028521).
commit 043e5e60ea8183887962eb7a9a707c98b6b643f6
Author: Jan Holcapek
Date: Fri Nov 22 10:54:50 2013 +0100
Initial import (#1028521).
.gitignore |1 +
perl-DBD-ODBC.spec | 53
2 files changed, 54 insertions(+), 0 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index e69de29..7f39fcc 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/DBD-ODBC-1.45.tar.gz
diff --git a/perl-DBD-ODBC.spec b/perl-DBD-ODBC.spec
new file mode 100644
index 000..2d1e7cc
--- /dev/null
+++ b/perl-DBD-ODBC.spec
@@ -0,0 +1,53 @@
+Name: perl-DBD-ODBC
+Version:1.45
+Release:1%{?dist}
+Summary:ODBC Driver for DBI
+License:GPL+ or Artistic
+Group: Development/Libraries
+URL:http://search.cpan.org/dist/DBD-ODBC/
+Source0:
http://www.cpan.org/modules/by-module/DBD/DBD-ODBC-%{version}.tar.gz
+BuildRequires: perl
+BuildRequires: perl(Config)
+BuildRequires: perl(Data::Dumper)
+BuildRequires: perl(DBI)
+BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(Test::Pod)
+BuildRequires: perl(Test::Pod::Coverage)
+BuildRequires: unixODBC-devel
+Requires: perl(DBI)
+Requires: perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo
$version))
+Requires: unixODBC
+
+
+%description
+This module is needed to access ODBC databases from within Perl. The
+module uses the unixODBC manager to connect to the database.
+
+%prep
+%setup -q -n DBD-ODBC-%{version}
+
+%build
+PERL_MM_USE_DEFAULT=1 %{__perl} Makefile.PL INSTALLDIRS=vendor
OPTIMIZE="$RPM_OPT_FLAGS"
+make %{?_smp_mflags}
+
+%install
+make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
+find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \;
+find $RPM_BUILD_ROOT -type f -name '*.bs' -size 0 -exec rm -f {} \;
+%{_fixperms} $RPM_BUILD_ROOT/*
+
+%check
+make test
+
+%files
+%doc Changes FAQ README TO_DO
+%{perl_vendorarch}/auto/*
+%{perl_vendorarch}/DBD*
+%{_mandir}/man3/*
+
+%changelog
+* Fri Nov 22 2013 Jan Holcapek 1.45-1
+- Initial import (#1028521).
+
+* Fri Nov 08 2013 Jan Holcapek 1.45-1
+- Specfile autogenerated by cpanspec 1.78.
--
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
File DBD-ODBC-1.45.tar.gz uploaded to lookaside cache by holcapek
A file has been added to the lookaside cache for perl-DBD-ODBC: 3c750cde8e39fbba804043485f18ba68 DBD-ODBC-1.45.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Source file audit - 2013-11-17
On Fri, Nov 22, 2013 at 2:51 AM, Björn Persson wrote: [...HTTPS stuff...] I think I've made my opinion clear already, won't parrot it and waste people's time any more. Just read my previous mails again in response to your latest questions. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
