Re: amending the new package process
- Original Message - I think the last bullet point here is the important part. I understand the disposition for a technical solution, but someone that just drops their package in - even after two months - isn't really getting a sense of community out of the experience. The process as-is, while it can be frustrating for all the reasons described, encourages new contributors to get acquainted with their fellow packagers and their sponsors. I'm not suggesting a de facto you must be sociable to be a Fedora Packager, but the process does reinforce that you're not alone when you get stuck, and you're not so isolated that nobody cares if you make a mistake. The informal reviews, irc chats, and list mails don't just garner experience; they help develop a sense of participation, and that leads to greater contributor retention. I believe we are talking past each other. My point is * The process doesn't work and your reply is: * The process was designed with good mindset, and should help everyone become better acquanted with Fedora. The latter are intentions and side effects which are good, _if and only if_ the process works well, which is not the case here. Maybe some list or other communication channel that's more clearly for packaging issues - I'm told devel@ can be intimidating - would help, but I'm not really suggesting anything specific. Everyone in the thread here, and probably far more, have answered inane questions from me at one time or another :P Sometimes more process and more guides can help, and sometimes you just need to bounce your understanding of the subject off someone to clear up misconceptions and gain a little confidence. That part isn't broken, but maybe new packagers don't know it. The issue I'm trying to point is not lack of communication or getting informal reviews. The issue I'm trying to point is about getting _formal_ reviews, or to simply, to get the job done. regards, Nikos -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1142983] perl-WWW-Shorten-3.06 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1142983 --- Comment #1 from Fedora Update System upda...@fedoraproject.org --- perl-WWW-Shorten-3.06-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/perl-WWW-Shorten-3.06-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=Ao7O9QddrDa=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-Date-Easter] Upgrade to 1.22
commit 85454d75bc338addbf2569c8d96cc2a863844c46
Author: David Dick dd...@cpan.org
Date: Sat Jan 24 19:41:36 2015 +1100
Upgrade to 1.22
.gitignore|1 +
perl-Date-Easter.spec | 14 +++---
sources |2 +-
3 files changed, 13 insertions(+), 4 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 16590f2..5ab770e 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
/Date-Easter-1.20.tar.gz
/Date-Easter-1.21.tar.gz
+/Date-Easter-1.22.tar.gz
diff --git a/perl-Date-Easter.spec b/perl-Date-Easter.spec
index 68c8451..16a888c 100644
--- a/perl-Date-Easter.spec
+++ b/perl-Date-Easter.spec
@@ -1,6 +1,6 @@
Name: perl-Date-Easter
-Version:1.21
-Release:2%{?dist}
+Version:1.22
+Release:1%{?dist}
Summary:Calculates Easter for any given year
License:Artistic 2.0
Group: Development/Libraries
@@ -38,12 +38,20 @@ find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {}
\;
make test
%files
-%doc LICENSE README
+%if 0%{?_licensedir:1}
+%license LICENSE
+%else
+%doc LICENSE
+%endif
+%doc README
%{perl_vendorlib}/*
%{_mandir}/man3/*
%{_bindir}/*
%changelog
+* Sat Jan 24 2015 David Dick dd...@cpan.org - 1.22-1
+- Upgrade to 1.22
+
* Tue Aug 26 2014 Jitka Plesnikova jples...@redhat.com - 1.21-2
- Perl 5.20 rebuild
diff --git a/sources b/sources
index 667ab01..d1b52db 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-f6d61dc6756210b8ad6437f4ae0dbd78 Date-Easter-1.21.tar.gz
+05030e2943f4daf99d7715e80b9e3cfc Date-Easter-1.22.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
Re: Bodhi policy for pushing updates to stable
Kamil Paral wrote: So, enforcing upgrade path for stable releases sounds good. But when we add development releases into the mix, we need to break upgrade path in certain cases. And we probably need to come up with a different solution to ensure you can correctly upgrade to it on the release day (maybe by using yum distro-sync-like approach instead of yum-update-like approach?). We will need to deal with these problems as our automation coverage increases. IMHO, we should 1. abolish the Alpha and Beta freezes (just take ALL new builds until the criteria are met), 2. open up the 0-day updates immediately on Final freeze, 3. in Final freeze periods, distinguish between freeze overrides and normal stable updates in Bodhi, instead of the current stable = freeze override setup. 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
[EPEL-devel] Fedora EPEL 5 updates-testing report
The following Fedora EPEL 5 Security updates need testing: Age URL 1007 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5630/bugzilla-3.2.10-5.el5 462 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11893/libguestfs-1.20.12-1.el5 226 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1626/puppet-2.7.26-1.el5 80 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3784/mantis-1.2.17-3.el5 76 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3849/sblim-sfcb-1.3.8-2.el5 42 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4430/phpMyAdmin4-4.0.10.7-2.el5 28 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4917/dokuwiki-0-0.23.20140929b.el5 10 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0261/libsndfile-1.0.17-6.el5 10 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0280/drupal7-context-3.6-1.el5 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0369/polarssl-1.3.2-4.el5 The following builds have been pushed to Fedora EPEL 5 updates-testing CGSI-gSOAP-1.3.7-2.el5 dpm-xrootd-3.5.2-1.el5 gfal2-plugin-xrootd-0.3.4-1.el5 perl-Apache-Session-Browseable-1.0.2-2.el5 php-htmLawed-1.1.19-1.el5 php-pear-Net-Sieve-1.3.4-1.el5 polarssl-1.3.2-4.el5 salt-2014.7.1-1.el5 voms-2.0.12-2.el5 Details about builds: CGSI-gSOAP-1.3.7-2.el5 (FEDORA-EPEL-2015-0404) GSI plugin for gSOAP Update Information: Implementing new license packaging guidelines. ChangeLog: * Wed Jan 21 2015 Mattias Ellert mattias.ell...@fysast.uu.se - 1.3.7-2 - Rebuild for gsoap 2.8.21 (Fedora 22) - Implement new license packaging guidelines dpm-xrootd-3.5.2-1.el5 (FEDORA-EPEL-2015-0379) XROOT interface to the Disk Pool Manager (DPM) Update Information: Update for new upstream release ChangeLog: * Mon Jan 12 2015 Alejandro Alvarez aalva...@cern.ch - 3.5.2-1 - Upstream release 3.5.2 gfal2-plugin-xrootd-0.3.4-1.el5 (FEDORA-EPEL-2015-0412) Provide xrootd support for GFAL2 Update Information: Upstream release 0.3.4 ChangeLog: * Mon Jan 19 2015 Alejandro Alvarez Ayllon aalvarez at cern.ch - 0.3.4-1 - Update for new upstream release * Sat Aug 16 2014 Fedora Release Engineering rel-...@lists.fedoraproject.org - 0.3.pre1-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_22_Mass_Rebuild * Mon Jul 7 2014 Alejandro Alvarez Ayllon aalvarez at cern.ch - 0.3.pre1-1 - Update for upstream preview release, with fixes for xrootd 4 * Sat Jun 7 2014 Fedora Release Engineering rel-...@lists.fedoraproject.org - 0.2.2-5 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild * Wed Aug 14 2013 Adrien Devresse adevress at cern.ch - 0.2.3-4 - unversionned documentation directory * Sat Aug 3 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org - 0.2.2-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild perl-Apache-Session-Browseable-1.0.2-2.el5 (FEDORA-EPEL-2015-0386) Add index and search methods to Apache::Session Update Information: This is the first Fedora/EPEL release of perl-Apache-Session-Browseable. References: [ 1 ] Bug #1182960 - Review Request: perl-Apache-Session-Browseable - Add index and search methods to Apache::Session https://bugzilla.redhat.com/show_bug.cgi?id=1182960 php-htmLawed-1.1.19-1.el5 (FEDORA-EPEL-2015-0374) PHP code to purify and filter HTML Update Information: Version 1.1.19 - 19 January 2015: * Fix for a bug in cleaning of soft-hyphens in URL values, etc.
[Bug 1184825] perl-Date-Easter-1.22 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1184825 --- Comment #3 from Fedora Update System upda...@fedoraproject.org --- perl-Date-Easter-1.22-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/perl-Date-Easter-1.22-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=w8tTYpdUWLa=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-WWW-Shorten/f20] (2 commits) ...Update to 3.06 (bz#1142983)
Summary of changes: a811d60... Perl 5.20 rebuild (*) 18984e6... Update to 3.06 (bz#1142983) (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File Date-Easter-1.22.tar.gz uploaded to lookaside cache by ddick
A file has been added to the lookaside cache for perl-Date-Easter: 05030e2943f4daf99d7715e80b9e3cfc Date-Easter-1.22.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 1183582] perl-MooX-Options-4.015 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1183582 --- Comment #1 from Fedora Update System upda...@fedoraproject.org --- perl-MooX-Options-4.015-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/perl-MooX-Options-4.015-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=jIdw0lvcFQa=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-Date-Easter/f20] (2 commits) ...Upgrade to 1.22
Summary of changes: f41652e... Perl 5.20 rebuild (*) 85454d7... Upgrade to 1.22 (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1184825] perl-Date-Easter-1.22 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1184825 --- Comment #1 from Fedora Update System upda...@fedoraproject.org --- perl-Date-Easter-1.22-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/perl-Date-Easter-1.22-1.el6 -- 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=QyCijaczx6a=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-WWW-Shorten/f21] (2 commits) ...Update to 3.06 (bz#1142983)
Summary of changes: a811d60... Perl 5.20 rebuild (*) 18984e6... Update to 3.06 (bz#1142983) (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-WWW-Shorten] Update to 3.06 (bz#1142983)
commit 18984e67afb0d7636c621a74d9c9d501941c2dcf
Author: Julian C. Dunn jd...@aquezada.com
Date: Fri Jan 23 23:53:35 2015 -0500
Update to 3.06 (bz#1142983)
.gitignore|1 +
perl-WWW-Shorten.spec |7 +--
sources |2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 857b9f7..ee03788 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,3 +2,4 @@
/WWW-Shorten-3.03.tar.gz
/WWW-Shorten-3.04.tar.gz
/WWW-Shorten-3.05.tar.gz
+/WWW-Shorten-3.06.tar.gz
diff --git a/perl-WWW-Shorten.spec b/perl-WWW-Shorten.spec
index 8302d01..f7e4499 100644
--- a/perl-WWW-Shorten.spec
+++ b/perl-WWW-Shorten.spec
@@ -1,6 +1,6 @@
Name: perl-WWW-Shorten
-Version:3.05
-Release:2%{?dist}
+Version:3.06
+Release:1%{?dist}
Summary:Interface to URL shortening sites
License:Artistic 2.0
Group: Development/Libraries
@@ -48,6 +48,9 @@ find $RPM_BUILD_ROOT -depth -type d -exec rmdir {}
2/dev/null \;
%{_mandir}/man3/*
%changelog
+* Fri Jan 23 2015 Julian C. Dunn jd...@aquezada.com - 3.06-1
+- Upgrade to 3.06 (bz#1142983)
+
* Fri Aug 29 2014 Jitka Plesnikova jples...@redhat.com - 3.05-2
- Perl 5.20 rebuild
diff --git a/sources b/sources
index 0fd358f..fd589fd 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-bdc5be1fac9ec6310e7c8163f29f4d47 WWW-Shorten-3.05.tar.gz
+7fec4441d031973710ee61999f964bd2 WWW-Shorten-3.06.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
autoreconf on build
I notice that Debian recently [since July 2014] started to recommend that packagers run autoreconf on build. Their reasons are given here and seem to be good ones: https://wiki.debian.org/Autoreconf In the interests of fairness I can think of two drawbacks too: - newer versions of (especially) automake have not always been improvements, and some upstreams may wish to stick with older ones - autoreconf is slow Debian have probably hit most of the bugs by now, and I think this is a good recommendation that perhaps Fedora packagers should be encouraged to follow too. What do you think? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top -- 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: autoreconf on build
On 01/24/2015 03:14 PM, Richard W.M. Jones wrote: I notice that Debian recently [since July 2014] started to recommend that packagers run autoreconf on build. Their reasons are given here and seem to be good ones: https://wiki.debian.org/Autoreconf In the interests of fairness I can think of two drawbacks too: - newer versions of (especially) automake have not always been improvements, and some upstreams may wish to stick with older ones - autoreconf is slow Debian have probably hit most of the bugs by now, and I think this is a good recommendation that perhaps Fedora packagers should be encouraged to follow too. What do you think? This is bad advice. Autoreconf only works if a package has been prepared for it and if a package is actively maintained. In many other cases autoreconf can cause subtile and hard to find issues. In complex cases, it doesn't work at all. Ralf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Test-Announce] Fedora 22 Rawhide 20150124 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 22 Rawhide 20150124. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: pyparted - 20150110: 3.10.2-1, 20150124: 3.10.3-1 lorax - 20150110: 22.1-1, 20150124: 22.3-1 python-blivet - 20150110: 0.74-1, 20150124: 0.75-1 anaconda - 20150110: 22.14-1, 20150124: 22.16-1 Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/22 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150124_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150124_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150124_Base https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150124_Server https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150124_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150124_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150124_Security_Lab Thank you for testing! -- Mail generated by relval: https://www.happyassassin.net/wikitcms/ On behalf of: adamwill ___ 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: autoreconf on build
On Sat, 24 Jan 2015 19:42:20 +0100, Ralf Corsepius wrote: In many other cases autoreconf can cause subtile and hard to find issues. In complex cases, it doesn't work at all. Especially the former can be troublesome if they don't cause a build to fail. For example, it can lead to issues such as undefined/unsubstituted macros, dropped lines from Makefile*.in templates, files like config.h.in or even m4 files. Packaging guidelines that ask packagers to run autoreconf always will lead to packagers adding something to a spec file without spending extra time on carefully examining the results. -- 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: Bodhi policy for pushing updates to stable
On Sat, 2015-01-24 at 16:11 -0600, Dennis Gilmore wrote: With a change along those lines, I think we could plausibly look at hard enforcement of the upgrade path, and it would be a good improvement. It may be necessary to have *some* kind of override mechanism for the case where we have a major security issue we really need to fix in stable ASAP, and karma for Branched is lagging behind. There should be a good way to have enforcement. It will take extra thought. knowing where we are in the release process can let us check against different repos. Final Freeze is the tricky bit and perhaps we just push stable updates and cherry pick in fixes. Hum, good points earlier on. So thinking this through again...the bit I forgot to mention - the reason why 'updates' matters - is that on fedup to Branched, updates- testing is (usually) not used, because fedup takes its repo set from the release being upgraded from. I don't know if it'd be practical to change that, or if we should just look at the distro-sync mode as the 'solution'. It'd be good to get Will's thoughts. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
rawhide report: 20150124 changes
Compose started at Sat Jan 24 05:15:03 UTC 2015 New package: gnome-builder-3.15.4.1-1.fc22 IDE for writing GNOME-based software New package: perl-Crypt-Random-TESHA2-0.01-1.fc22 Random numbers using timer/schedule entropy New package: python-sep-0.2.0-1.fc22 Astronomical source extraction and photometry in Python New package: rt-4.0.22-3.fc22 Request tracker New package: rubygem-rails-deprecated_sanitizer-1.0.3-2.fc22 Deprecated sanitizer API extracted from Action View Removed package: cloud-initramfs-tools-0.20-3.fc21 Updated Packages: GAPDoc-1.5.1-6.fc22 --- * Fri Jan 23 2015 Jerry James loganje...@gmail.com - 1.5.1-6 - Fix scriptlets so they don't complain when uninstalling - Use license macro Size change: 3200 bytes accountsservice-0.6.40-1.fc22 - * Fri Jan 23 2015 Ray Strode rstr...@redhat.com 0.6.40-1 - Update to 0.6.40 Size change: -1778 bytes anaconda-22.16-1.fc22 - * Fri Jan 23 2015 Brian C. Lane b...@redhat.com - 22.16-1 - Add some tests for kickstart and package selection for dnf. (clumens) - Double quote when printing error results from a kickstart test. (clumens) - Restrict payload kernel versions to kernels in the payload (#1074358) (dshea) - Actually add the new definition of an already-defined repo. (clumens) - Move hdiso handling code to PackagePayload (#1180765) (dshea) - Actually install the metacity theme data (dshea) - Show the event box immediately when setting infobar messages. (dshea) - Move environment group selection logic to PackagePayload (#1179362) (dshea) - Add a parameter to environmentGroups for wheter to include optionlist. (dshea) - Remove unused methods for deselecting environments (dshea) Size change: 5284 bytes antimicro-2.10.1-2.fc22 --- * Sat Jan 03 2015 Jeff Backus jeff.bac...@gmail.com - 2.10.1-2 - added appdata support Size change: 956 bytes atlas-3.10.1-18.fc22 * Fri Jan 23 2015 Frantisek Kluknavsky fkluk...@redhat.com - 3.10.1-18 - unbundled lapack (only a few modified routines shipped with atlas sources are supposed to stay) Size change: -6264249 bytes bash-4.3.33-2.fc22 -- * Fri Jan 23 2015 Elad Alfassa e...@fedoraproject.org - 4.3.25-3 - Enable PIE (hardened build) Size change: -959 bytes calibre-2.17.0-1.fc22 - * Fri Jan 23 2015 Kevin Fenzi ke...@scrye.com 2.17.0-1 - Update to 2.17.0 Size change: -46660 bytes calligra-2.8.7-5.fc22 - * Fri Jan 23 2015 Marek Kasik mka...@redhat.com 2.8.7-5 - Rebuild (poppler-0.30.0) Size change: -1022 bytes cmake-3.1.1-1.fc22 -- * Fri Jan 23 2015 Orion Poplawski or...@cora.nwra.com - 3.1.1-1 - Update to 3.1.1 - Drop ruby patch applied upstream Size change: 1120 bytes coin-or-Ipopt-3.11.10-2.fc22 * Fri Jan 23 2015 Antonio Trande sagitterATfedoraproject.org - 3.11.10-2 - Fix libraries's symlinks (bz#1152812) Size change: -993 bytes cups-filters-1.0.61-3.fc22 -- * Fri Jan 23 2015 Marek Kasik mka...@redhat.com - 1.0.61-3 - Rebuild (poppler-0.30.0) Size change: -1021 bytes eclipse-eclemma-2.3.2-3.fc22 * Fri Jan 23 2015 Mat Booth mat.bo...@redhat.com - 2.3.2-3 - Patch to explicitly depend on hamcrest core in tests - Fix files listed twice warning Size change: -494 bytes eclipse-egit-3.6.2-1.fc22 - * Fri Jan 23 2015 Alexander Kurtakov akurt...@redhat.com 3.6.2-1 - Update to upstream 3.6.2 release. Size change: -1072 bytes eclipse-egit-github-3.6.2-1.fc22 * Fri Jan 23 2015 Alexander Kurtakov akurt...@redhat.com 3.6.2-1 - Update to upstream 3.6.2 release. Size change: -1418 bytes eclipse-jgit-3.6.2-2.fc22 - * Fri Jan 23 2015 Roland Grunberg rgrun...@redhat.com - 3.6.2-2 - Use Equinox's OSGi runtime instead of Felix's. * Fri Jan 23 2015 Alexander Kurtakov akurt...@redhat.com 3.6.2-1 - Update to upstream 3.6.2. Size change: -32 bytes evas-generic-loaders-1.7.10-3.fc22 -- * Fri Jan 23 2015 Marek Kasik mka...@redhat.com - 1.7.10-3 - Rebuild (poppler-0.30.0) Size change: -1011 bytes felix-scr-annotations-1.9.10-1.fc22 --- * Fri Jan 23 2015 gil cattaneo punto...@libero.it 1.9.10-1 - update to 1.9.10 Size change: 4655 bytes felix-scr-generator-1.12.0-1.fc22 - * Fri Jan 23 2015 gil cattaneo punto...@libero.it 1.12.0-1 - update to 1.12.0 Size change: 5755 bytes gambas3-3.6.1-3.fc22 * Fri Jan 23 2015 Marek Kasik mka...@redhat.com 3.6.1-3 - Rebuild (poppler-0.30.0) Size change: -1022 bytes gap-4.7.6-3.fc22 * Fri Jan 23 2015 Jerry James loganje...@gmail.com - 4.7.6-3 - Fix scriptlets so they don't complain when uninstalling - Drop obsolete Group tags
File MooX-Options-4.015.tar.gz uploaded to lookaside cache by ddick
A file has been added to the lookaside cache for perl-MooX-Options: cd2b948ae1c6f29ffc2739a99abe11d4 MooX-Options-4.015.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 1184825] perl-Date-Easter-1.22 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1184825 --- Comment #4 from Fedora Update System upda...@fedoraproject.org --- perl-Date-Easter-1.22-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/perl-Date-Easter-1.22-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=vUNEsEJSK1a=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-MooX-Options/f21] Generate warning when missing required params
Summary of changes: 3fbaa56... Generate warning when missing required params (*) (*) 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
[Bug 1184825] perl-Date-Easter-1.22 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1184825 --- Comment #2 from Fedora Update System upda...@fedoraproject.org --- perl-Date-Easter-1.22-1.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/perl-Date-Easter-1.22-1.el7 -- 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=ivGRJoJDRNa=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 1171037] perl-MooX-Cmd-0.011 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1171037 --- Comment #2 from Fedora Update System upda...@fedoraproject.org --- perl-MooX-Cmd-0.011-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/perl-MooX-Cmd-0.011-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=Pm6gTjeq30a=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 1171037] perl-MooX-Cmd-0.011 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1171037 --- Comment #1 from Fedora Update System upda...@fedoraproject.org --- perl-MooX-Cmd-0.011-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/perl-MooX-Cmd-0.011-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=H0iPu3vnira=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
Re: amending the new package process
- Original Message - 2015-01-21 11:49 GMT+01:00 Nikos Mavrogiannopoulos n...@redhat.com: Step 6: ... If the proposed package is not reviewed for 2 months, the package must be reviewed by the submitter, and a git module with the master branch will be approved. I share your concern about the pending list but self-review is not acceptable. Just licensing review itself would be a blocker to your proposal. I don't understand what you mean above. But if we were to have a staging repository as suggested by Josh and Jaroslav, it could be something that we could consider. I believe it is really orthogonal to the issue. A staging repository will not solve the issue of adding a library which is a dependency of a package in Fedora proper. Moreover if it works better than the process we currently have, we end up having the staging repository always being added by the users, defeating the purpose of the processes we set. regards, Nikos -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1183582] perl-MooX-Options-4.015 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1183582 --- Comment #2 from Fedora Update System upda...@fedoraproject.org --- perl-MooX-Options-4.015-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/perl-MooX-Options-4.015-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=yasb87QQsOa=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-MooX-Options/f20] Generate warning when missing required params
Summary of changes: 3fbaa56... Generate warning when missing required params (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Date-Easter/el6] (2 commits) ...Upgrade to 1.22
Summary of changes: f41652e... Perl 5.20 rebuild (*) 85454d7... Upgrade to 1.22 (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Date-Easter/epel7] (2 commits) ...Upgrade to 1.22
Summary of changes: f41652e... Perl 5.20 rebuild (*) 85454d7... Upgrade to 1.22 (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: amending the new package process
On 01/24/2015 12:32 AM, Kevin Kofler wrote: In many Free Software projects (e.g., GCC, KDE, etc.), the people who are allowed to approve other people's commits can also approve their own. This is not entirely true. GCC and related projects apply a pretty complex peer review process, with defined roles and privileges. (Cf. the file MAINTAINERS in GCC's sourcetree for details). Somewhat over-simplified the process condenses into All proposed changes must be peer-reviewed by somebody who is formally in charge of a component to be changed. Exceptions apply for obvious changes. Ralf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[perl-Date-Easter/f21] (2 commits) ...Upgrade to 1.22
Summary of changes: f41652e... Perl 5.20 rebuild (*) 85454d7... Upgrade to 1.22 (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-MooX-Options] Generate warning when missing required params
commit 3fbaa56df64fbcff7abe6699ddfd3a33f720d968
Author: David Dick dd...@cpan.org
Date: Sat Jan 24 19:22:02 2015 +1100
Generate warning when missing required params
.gitignore |1 +
perl-MooX-Options.spec | 12 ++--
sources|2 +-
3 files changed, 12 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index bb1f83b..d7499ad 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
/MooX-Options-4.009.tar.gz
/MooX-Options-4.012.tar.gz
/MooX-Options-4.013.tar.gz
+/MooX-Options-4.015.tar.gz
diff --git a/perl-MooX-Options.spec b/perl-MooX-Options.spec
index 5f91664..98e275d 100644
--- a/perl-MooX-Options.spec
+++ b/perl-MooX-Options.spec
@@ -1,5 +1,5 @@
Name: perl-MooX-Options
-Version:4.013
+Version:4.015
Release:1%{?dist}
Summary:Explicit Options eXtension for Object Class
License:GPL+ or Artistic
@@ -69,11 +69,19 @@ chmod -c -x lib/MooX/Options.pm
./Build test
%files
-%doc Changes etc LICENSE README
+%if 0%{?_licensedir:1}
+%license LICENSE
+%else
+%doc LICENSE
+%endif
+%doc Changes etc README
%{perl_vendorlib}/*
%{_mandir}/man3/*
%changelog
+* Sat Jan 24 2015 David Dick dd...@cpan.org - 4.015-1
+- Generate warning when missing required params
+
* Wed Nov 26 2014 David Dick dd...@cpan.org - 4.013-1
- Adding autorange support
diff --git a/sources b/sources
index efdcb84..6e801ef 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-e541f8875e6564032c26ec32595302b8 MooX-Options-4.013.tar.gz
+cd2b948ae1c6f29ffc2739a99abe11d4 MooX-Options-4.015.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
Re: Bodhi policy for pushing updates to stable
On Sat, 2015-01-24 at 17:42 +0100, Kevin Kofler wrote: Kamil Paral wrote: So, enforcing upgrade path for stable releases sounds good. But when we add development releases into the mix, we need to break upgrade path in certain cases. And we probably need to come up with a different solution to ensure you can correctly upgrade to it on the release day (maybe by using yum distro-sync-like approach instead of yum-update-like approach?). We will need to deal with these problems as our automation coverage increases. IMHO, we should 1. abolish the Alpha and Beta freezes (just take ALL new builds until the criteria are met), This is worth considering, at least, as the milestone freezes have (obviously, the clue's in the name) been around since *before* No Frozen Rawhide. In a sense, they and NFR aim to address the address the same problem: the tension between doing development work, and stabilizing a release. So I think it's at least worth considering. My instinct is still to oppose it, though, because we *do* still have potentially destabilizing changes landing in Branched during freezes. We quite often get an entire new GNOME build during freeze; sometimes we consider these and freeze-override them in, but we probably don't want one landing on the Wednesday we're trying to polish up an RC for approval on Thursday. Same applies to the kernel, and various other bits like dracut and parted which affect the install-and-firstboot critpath parts especially. 2. open up the 0-day updates immediately on Final freeze, 3. in Final freeze periods, distinguish between freeze overrides and normal stable updates in Bodhi, instead of the current stable = freeze override setup. So there was some discussion of this whole issue on test@ around the F21 release time and I was a bit curt - retrospective apologies for that, release times are always a bit stressful. Someone proposed that using the 'updates' repository during the Branched period could help solve quite a few things here, and I think that's an interesting idea. To recap, at present, we don't use 'updates' for Branched at all until the few days between the Final Go decision and the actual release date, when we populate it with the '0-day' update set. Once we hit the 'Bodhi enablement point', builds go to updates-testing first, then when they're marked as 'stable' (either manually or via autokarma), they are pushed directly to 'fedora', not to 'updates'. Someone - I forget who, I'm sorry - suggested that we could push updates marked as 'stable' during milestone freezes into 'updates'. For Alpha and Beta, we'd then flush them from 'updates' back into 'fedora' immediately following the milestone release; for Final they'd just stay there and become 0-days. With a bit of time to think about it, I think this is actually potentially a very good idea. It gives us two solid improvements: 1. We can keep pushing out new builds to a place where users will actually get them, without destabilizing the image composes 2. It would address the problem kparal identifies - when sending an update to a stable release would break the upgradepath because Branched is frozen, but we do really want the upgrade out for stable users One issue I can see with it is, what do we do with the buildroot? If we have 'updates' in the buildroot then builds getting pushed to updates could *indirectly* affect the image composes by causing issues in package builds to fix blocker/FE bugs. So I'd probably prefer to see only 'fedora' used as the buildroot for Branched. With a change along those lines, I think we could plausibly look at hard enforcement of the upgrade path, and it would be a good improvement. It may be necessary to have *some* kind of override mechanism for the case where we have a major security issue we really need to fix in stable ASAP, and karma for Branched is lagging behind. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1175143] ctstream-22 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1175143 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Fixed In Version|ctstream-23-1.fc21 |ctstream-23-1.el7 --- Comment #12 from Fedora Update System upda...@fedoraproject.org --- ctstream-23-1.el7 has been pushed to the Fedora EPEL 7 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=jU9bZivdjwa=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 1176864] ctstream-23 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1176864 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Fixed In Version|ctstream-23-1.fc21 |ctstream-23-1.el7 --- Comment #9 from Fedora Update System upda...@fedoraproject.org --- ctstream-23-1.el7 has been pushed to the Fedora EPEL 7 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=qdRiBkTCDCa=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
Re: amending the new package process
PT == Pete Travis li...@petetravis.com writes: PT Maybe some list or other communication channel that's more clearly PT for packaging issues - I'm told devel@ can be intimidating - would PT help, but I'm not really suggesting anything specific. Just to be sure, you do know about packag...@lists.fedoraproject.org, right? I can't think of any list that's more clearly for packaging issues. It's there and it's active. Or did you mean something for new packagers? I'd be happy to be on that one, too. - J -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1174161] Epel7 branch?
https://bugzilla.redhat.com/show_bug.cgi?id=1174161 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version||perl-Net-Patricia-1.22-6.el ||7 Resolution|--- |ERRATA Last Closed||2015-01-24 13:52:12 --- Comment #7 from Fedora Update System upda...@fedoraproject.org --- perl-Net-Patricia-1.22-6.el7 has been pushed to the Fedora EPEL 7 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=giyquE9MXNa=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
Re: Bodhi policy for pushing updates to stable
On Sat, 2015-01-24 at 11:05 -0800, Adam Williamson wrote: With a change along those lines, I think we could plausibly look at hard enforcement of the upgrade path, and it would be a good improvement. It may be necessary to have *some* kind of override mechanism for the case where we have a major security issue we really need to fix in stable ASAP, and karma for Branched is lagging behind. I should also note for completeness the other string to this debate: https://github.com/wgwoods/fedup/issues/21 that would make the upgradepath issue more or less moot, as you can already use --distro-sync for yum/dnf upgrades. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: autoreconf on build
On Sat, Jan 24, 2015 at 07:42:20PM +0100, Ralf Corsepius wrote: On 01/24/2015 03:14 PM, Richard W.M. Jones wrote: I notice that Debian recently [since July 2014] started to recommend that packagers run autoreconf on build. Their reasons are given here and seem to be good ones: https://wiki.debian.org/Autoreconf In the interests of fairness I can think of two drawbacks too: - newer versions of (especially) automake have not always been improvements, and some upstreams may wish to stick with older ones - autoreconf is slow Debian have probably hit most of the bugs by now, and I think this is a good recommendation that perhaps Fedora packagers should be encouraged to follow too. What do you think? This is bad advice. Autoreconf only works if a package has been prepared for it and if a package is actively maintained. ... which would be a bug in the upstream package. But yes I agree this is possibly controversial. On the other hand Debian likely will have encountered these bugs before us. In many other cases autoreconf can cause subtile and hard to find issues. In complex cases, it doesn't work at all. Again, bugs in the upstream package. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top -- 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-Net-Twitter
perl-Net-Twitter has broken dependencies in the rawhide tree: On x86_64: perl-Net-Twitter-4.01008-1.fc22.noarch requires perl(authentication) On i386: perl-Net-Twitter-4.01008-1.fc22.noarch requires perl(authentication) On armhfp: perl-Net-Twitter-4.01008-1.fc22.noarch requires perl(authentication) 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
Re: koji hubs updated
On Sat, 24 Jan 2015 14:36:43 +0100 Robert Scheck rob...@fedoraproject.org wrote: On Fri, 23 Jan 2015, Kevin Fenzi wrote: There's one issue we are looking into to be aware of, builds now give: SysCallError: (-1, 'Unexpected EOF') instead of watching the build you just started. The build is running fine and you can follow it on the web interface. Hopefully we will push out a fix soon. Being on EL-6, the build is unfortunately not running. I just receive this: $ fedpkg build --nowait Could not execute build: (-1, 'Unexpected EOF') $ FYI, we debugged this some on irc and found that it was an old koji version on your client. With the latest update everything works. kevin pgphZtAxqoriw.pgp Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
File Catalyst-Action-REST-1.18.tar.gz uploaded to lookaside cache by eseyman
A file has been added to the lookaside cache for perl-Catalyst-Action-REST: 99a4f697a42ca6cdd7a18d7eacea0c4b Catalyst-Action-REST-1.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
File GD-SecurityImage-1.73.tar.gz uploaded to lookaside cache by eseyman
A file has been added to the lookaside cache for perl-GD-SecurityImage: 1236ad8bc2a808814aa5c102835e1252 GD-SecurityImage-1.73.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-WWW-Mechanize] Update to 1.74
commit 41faf69dd0cd17673adcb1991618893130165fa7
Author: Emmanuel Seyman emman...@seyman.fr
Date: Sun Jan 25 04:00:38 2015 +0100
Update to 1.74
.gitignore |1 +
perl-WWW-Mechanize.spec |7 +--
sources |2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 8c63797..a377039 100644
--- a/.gitignore
+++ b/.gitignore
@@ -5,3 +5,4 @@ WWW-Mechanize-1.62.tar.gz
/WWW-Mechanize-1.71.tar.gz
/WWW-Mechanize-1.72.tar.gz
/WWW-Mechanize-1.73.tar.gz
+/WWW-Mechanize-1.74.tar.gz
diff --git a/perl-WWW-Mechanize.spec b/perl-WWW-Mechanize.spec
index 81f7d03..a7959d3 100644
--- a/perl-WWW-Mechanize.spec
+++ b/perl-WWW-Mechanize.spec
@@ -6,8 +6,8 @@
%bcond_with livetests
Name: perl-WWW-Mechanize
-Version:1.73
-Release:3%{?dist}
+Version:1.74
+Release:1%{?dist}
Summary:Automates web page form link interaction
Group: Development/Libraries
License:GPL+ or Artistic
@@ -108,6 +108,9 @@ make test
%{_mandir}/man3/*.3pm*
%changelog
+* Sun Jan 25 2015 Emmanuel Seyman emman...@seyman.fr - 1.74-1
+- Update to 1.74
+
* Fri Aug 29 2014 Jitka Plesnikova jples...@redhat.com - 1.73-3
- Perl 5.20 rebuild
diff --git a/sources b/sources
index a38c489..f100d22 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-de0a9c528c12793c881151301bc14d1a WWW-Mechanize-1.73.tar.gz
+8ec615225037ac66a2d37f4e9693ef86 WWW-Mechanize-1.74.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-QWizard
perl-QWizard has broken dependencies in the epel-5 tree: On ppc: perl-QWizard-3.15-8.el5.noarch requires perl(Gtk2) On x86_64: perl-QWizard-3.15-8.el5.noarch requires perl(Gtk2) On i386: perl-QWizard-3.15-8.el5.noarch requires perl(Gtk2) On ppc: perl-QWizard-3.15-10.el5.noarch requires perl(Gtk2) On x86_64: perl-QWizard-3.15-10.el5.noarch requires perl(Gtk2) On i386: perl-QWizard-3.15-10.el5.noarch requires perl(Gtk2) 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
Broken dependencies: perl-SVK
perl-SVK has broken dependencies in the epel-5 tree: On ppc: perl-SVK-2.0.2-1.el5.noarch requires perl(SVN::Mirror) = 0:0.71 On x86_64: perl-SVK-2.0.2-1.el5.noarch requires perl(SVN::Mirror) = 0:0.71 On i386: perl-SVK-2.0.2-1.el5.noarch requires perl(SVN::Mirror) = 0:0.71 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
Broken dependencies: perl-XML-Xerces
perl-XML-Xerces has broken dependencies in the epel-5 tree: On ppc: perl-XML-Xerces-2.7.0_0-4.el5.ppc requires libxerces-c.so.27 On x86_64: perl-XML-Xerces-2.7.0_0-4.el5.x86_64 requires libxerces-c.so.27()(64bit) On i386: perl-XML-Xerces-2.7.0_0-4.el5.i386 requires libxerces-c.so.27 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
Broken dependencies: perl-Getopt-GUI-Long
perl-Getopt-GUI-Long has broken dependencies in the epel-5 tree: On ppc: perl-Getopt-GUI-Long-0.91-5.el5.noarch requires perl(Gtk2) On x86_64: perl-Getopt-GUI-Long-0.91-5.el5.noarch requires perl(Gtk2) On i386: perl-Getopt-GUI-Long-0.91-5.el5.noarch requires perl(Gtk2) 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
adding new driver to kernel src and building rpm
I'm trying to do the following:
1) add the smi2021 driver for EasyCap Somagic usb frame grabbers into the
kernel tree
2) compile the kernel with smi2021 as a module
3) build the rpm.
I got the driver from Jon Arne Jorgensen's kernel branch on github:
https://github.com/jonjonarnearne/smi2021
then tried to follow these instructions:
https://fedoraproject.org/wiki/Building_a_custom_kernel
but the whole thing fails with this eror:
Patch10: smi2021.patch
+ case $patch in
+ patch -p1 -F1 -s
+ chmod +x scripts/checkpatch.pl
+ touch .scmversion
+ mkdir configs
+ for i in '*.config'
+ mv kernel-3.17.8-aarch64.config .config
++ head -1 .config
++ cut -b 3-
+ Arch=arm64
+ make ARCH=arm64 listnewconfig
+ grep -E '^CONFIG_'
+ '[' -s .newoptions ']'
+ cat .newoptions
CONFIG_VIDEO_SMI2021
+ exit 1
error: Bad exit status from /var/tmp/rpm-tmp.sASN4F (%prep)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.sASN4F (%prep)
So I spent a lot of time trying to figure this out and I know why it happens
but I don't know how to fix it.
The smi2021.patch being applied above is the diff between the kernel trees
with and without the driver. The patch succeeds. The problem is that in
order to have the module compiled I did make oldconfig and so I ended up with
CONFIG_VIDEO_SMI2021=m
in the kernel-3.17.8-x86_64 **ONLY**. Then the kernel.spec has some code
that runs oldconfig over **ALL** the kernel*.config files:
for i in *.config
do
mv $i .config
Arch=`head -1 .config | cut -b 3-`
make ARCH=$Arch listnewconfig | grep -E '^CONFIG_' .newoptions || true
%if %{listnewconfig_fail}
if [ -s .newoptions ]; then
cat .newoptions
exit 1
fi
%endif
rm -f .newoptions
make ARCH=$Arch oldnoconfig
echo # $Arch configs/$i
cat .config configs/$i
done
# end of kernel config
%endif
Of course, none of the other config files (for other architectures then
x86_64) have the CONFIG_VIDEO_SMI2021 options, hence the error.
So the key question is what is the proper way to add a new driver to the
kernel tree and run
rpmbuild -bb --target=$(uname -m) kernel.spec
on it? Do I put CONFIG=VIDEO_SMI2021=m in SOURCES/config-local, or what?
For what it's worth, I am able to do
make oldconfig# picks up the option for the new driver
make
in the kernel tree with the new code in it and it goes through without errors.
So if I want to run the new kernel with the new driver, I can, but I'd rather
do this by building the custom rpm, as I don't know when or if this driver
will be included in the vanilla kernel.
Please help, I'm at the end of my wits. Thanks!
--
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 new driver to kernel src and building rpm
On Sun, 2015-01-25 at 06:50 +, Amadeus W.M. wrote: I'm trying to do the following: 1) add the smi2021 driver for EasyCap Somagic usb frame grabbers into the kernel tree 2) compile the kernel with smi2021 as a module 3) build the rpm. I got the driver from Jon Arne Jorgensen's kernel branch on github: https://github.com/jonjonarnearne/smi2021 then tried to follow these instructions: https://fedoraproject.org/wiki/Building_a_custom_kernel but the whole thing fails with this eror: Patch10: smi2021.patch + case $patch in + patch -p1 -F1 -s + chmod +x scripts/checkpatch.pl + touch .scmversion + mkdir configs + for i in '*.config' + mv kernel-3.17.8-aarch64.config .config ++ head -1 .config ++ cut -b 3- + Arch=arm64 + make ARCH=arm64 listnewconfig + grep -E '^CONFIG_' + '[' -s .newoptions ']' + cat .newoptions CONFIG_VIDEO_SMI2021 + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.sASN4F (%prep) Please help, I'm at the end of my wits. Thanks! You just have to put the new config option in one of the config* files that's part of the kernel package git checkout itself - one that gets included in the appropriate arch builds. If you want to build the driver as a module for all arches, put CONFIG_VIDEO_SMI2021=m in config-generic , for instance. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[perl-GD-SecurityImage] Update to 1.73
commit f67443ba2edfe191654f45126df38a5d28ca6034
Author: Emmanuel Seyman emman...@seyman.fr
Date: Sun Jan 25 03:44:24 2015 +0100
Update to 1.73
.gitignore |1 +
perl-GD-SecurityImage.spec | 10 +++---
sources|2 +-
3 files changed, 9 insertions(+), 4 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 69e16d8..948c74c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
GD-SecurityImage-1.70.tar.gz
/GD-SecurityImage-1.71.tar.gz
/GD-SecurityImage-1.72.tar.gz
+/GD-SecurityImage-1.73.tar.gz
diff --git a/perl-GD-SecurityImage.spec b/perl-GD-SecurityImage.spec
index 39f5612..7bf11b2 100644
--- a/perl-GD-SecurityImage.spec
+++ b/perl-GD-SecurityImage.spec
@@ -1,12 +1,13 @@
Name: perl-GD-SecurityImage
-Version:1.72
-Release:6%{?dist}
+Version:1.73
+Release:1%{?dist}
Summary:Security image (captcha) generator
License:GPL+ or Artistic
-Group: Development/Libraries
+
URL:http://search.cpan.org/dist/GD-SecurityImage/
Source0:
http://www.cpan.org/authors/id/B/BU/BURAK/GD-SecurityImage-%{version}.tar.gz
BuildArch: noarch
+BuildRequires: perl
BuildRequires: perl(GD)
BuildRequires: perl(Image::Magick)
BuildRequires: perl(Module::Build)
@@ -48,6 +49,9 @@ find $RPM_BUILD_ROOT -depth -type d -exec rmdir {}
2/dev/null \;
%{_mandir}/man3/*
%changelog
+* Sun Jan 25 2015 Emmanuel Seyman emman...@seyman.fr - 1.73-1
+- Update to 1.73
+
* Wed Aug 27 2014 Jitka Plesnikova jples...@redhat.com - 1.72-6
- Perl 5.20 rebuild
diff --git a/sources b/sources
index 37248c3..fc6b37a 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-679aae59342fb88389eda8647bf4974c GD-SecurityImage-1.72.tar.gz
+1236ad8bc2a808814aa5c102835e1252 GD-SecurityImage-1.73.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 Mojolicious-5.74.tar.gz uploaded to lookaside cache by eseyman
A file has been added to the lookaside cache for perl-Mojolicious: 7f414285940dc5180dbe979139ac430b Mojolicious-5.74.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 Moo-1.007000.tar.gz uploaded to lookaside cache by eseyman
A file has been added to the lookaside cache for perl-Moo: 45dfb1157721f15d1f80b6514031d4f6 Moo-1.007000.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 re-engine-RE2-0.13.tar.gz uploaded to lookaside cache by eseyman
A file has been added to the lookaside cache for perl-re-engine-RE2: 85bf2cf9be48d287fdd3b0037cd9cefd re-engine-RE2-0.13.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 WWW-Mechanize-1.74.tar.gz uploaded to lookaside cache by eseyman
A file has been added to the lookaside cache for perl-WWW-Mechanize: 8ec615225037ac66a2d37f4e9693ef86 WWW-Mechanize-1.74.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-String-Random] Update to 0.28
commit 5eede0ca6c4625f6956a2e523215ec7a71a3c066
Author: Emmanuel Seyman emman...@seyman.fr
Date: Sun Jan 25 03:56:31 2015 +0100
Update to 0.28
.gitignore |1 +
perl-String-Random.spec |7 +--
sources |2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 54dfe8d..6e280f6 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,3 +2,4 @@ String-Random-0.22.tar.gz
/String-Random-0.24.tar.gz
/String-Random-0.25.tar.gz
/String-Random-0.26.tar.gz
+/String-Random-0.28.tar.gz
diff --git a/perl-String-Random.spec b/perl-String-Random.spec
index 87972a7..460a805 100644
--- a/perl-String-Random.spec
+++ b/perl-String-Random.spec
@@ -1,6 +1,6 @@
Name: perl-String-Random
-Version:0.26
-Release:3%{?dist}
+Version:0.28
+Release:1%{?dist}
Summary:Perl module to generate random strings based on a pattern
License:GPL+ or Artistic
URL:http://search.cpan.org/dist/String-Random/
@@ -43,6 +43,9 @@ find $RPM_BUILD_ROOT -depth -type d -exec rmdir {}
2/dev/null \;
%changelog
+* Sun Jan 25 2015 Emmanuel Seyman emman...@seyman.fr - 0.28-1
+- Update to 0.28
+
* Wed Aug 27 2014 Jitka Plesnikova jples...@redhat.com - 0.26-3
- Perl 5.20 rebuild
diff --git a/sources b/sources
index 8d8c7ec..11f051f 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-d98a5d8eec5b46c3d357236cbf7c70d6 String-Random-0.26.tar.gz
+22b63b03a0586e17de9509e0b80fa026 String-Random-0.28.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-Moo] Update to 1.007000
commit 76dfc0c0220e960031e7f6602c7e2a4e3718c97e
Author: Emmanuel Seyman emman...@seyman.fr
Date: Sun Jan 25 03:52:49 2015 +0100
Update to 1.007000
.gitignore|1 +
perl-Moo.spec |5 -
sources |2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 0716542..d671151 100644
--- a/.gitignore
+++ b/.gitignore
@@ -19,3 +19,4 @@
/Moo-1.005000.tar.gz
/Moo-1.006000.tar.gz
/Moo-1.006001.tar.gz
+/Moo-1.007000.tar.gz
diff --git a/perl-Moo.spec b/perl-Moo.spec
index 3bc5665..9079c63 100644
--- a/perl-Moo.spec
+++ b/perl-Moo.spec
@@ -1,5 +1,5 @@
Name: perl-Moo
-Version:1.006001
+Version:1.007000
Release:1%{?dist}
Summary:Minimalist Object Orientation (with Moose compatibility)
License:GPL+ or Artistic
@@ -94,6 +94,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Sun Jan 25 2015 Emmanuel Seyman emman...@seyman.fr - 1.007000-1
+- Update to 1.007000
+
* Mon Nov 10 2014 Emmanuel Seyman emman...@seyman.fr - 1.006001-1
- Update to 1.006001
diff --git a/sources b/sources
index c6da390..6343721 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-814b4b4f465a1d3c84f91bd0f30f1fbf Moo-1.006001.tar.gz
+45dfb1157721f15d1f80b6514031d4f6 Moo-1.007000.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 String-Random-0.28.tar.gz uploaded to lookaside cache by eseyman
A file has been added to the lookaside cache for perl-String-Random: 22b63b03a0586e17de9509e0b80fa026 String-Random-0.28.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
Re: Bodhi policy for pushing updates to stable
On Sat, Jan 24, 2015 at 11:05:52 -0800, Adam Williamson adamw...@fedoraproject.org wrote: Someone proposed that using the 'updates' repository during the Branched period could help solve quite a few things here, and I think that's an interesting idea. The other thing it fixes is packages dgowing up as orphaned when they move from updates-testung to the release, because the composes don't happen at the same time. I notice this because I check a lot, but most people don't. I like to get rid of the test builds if they are being unpushed, but not if they are moving to thbranched release. It's possible to go check this, but it's apain. -- 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-Authen-Simple
perl-Authen-Simple has broken dependencies in the epel-6 tree: On ppc64: perl-Authen-Simple-0.4-5.el6.noarch requires perl(Crypt::PasswdMD5) 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-Mojolicious] Update to 5.74
commit 5a676b7b30d453f8926bd76a28bb260a48f06243
Author: Emmanuel Seyman emman...@seyman.fr
Date: Sun Jan 25 03:49:01 2015 +0100
Update to 5.74
.gitignore|1 +
perl-Mojolicious.spec |5 -
sources |2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index a470c16..d244c4b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -157,3 +157,4 @@ Mojolicious-0.26.tar.gz
/Mojolicious-5.70.tar.gz
/Mojolicious-5.71.tar.gz
/Mojolicious-5.72.tar.gz
+/Mojolicious-5.74.tar.gz
diff --git a/perl-Mojolicious.spec b/perl-Mojolicious.spec
index f5789d2..233ca4b 100644
--- a/perl-Mojolicious.spec
+++ b/perl-Mojolicious.spec
@@ -1,5 +1,5 @@
Name: perl-Mojolicious
-Version:5.72
+Version:5.74
Release:1%{?dist}
Summary:A next generation web framework for Perl
License:Artistic 2.0
@@ -62,6 +62,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Sun Jan 25 2015 Emmanuel Seyman emman...@seyman.fr - 5.74-1
+- Update to 5.74
+
* Sun Jan 18 2015 Emmanuel Seyman emman...@seyman.fr - 5.72-1
- Update to 5.72
diff --git a/sources b/sources
index ed86651..8b4695e 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-797f28b188dec6e6a899b9b481ee8228 Mojolicious-5.72.tar.gz
+7f414285940dc5180dbe979139ac430b Mojolicious-5.74.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-SVK
perl-SVK has broken dependencies in the epel-5 tree: On ppc: perl-SVK-2.0.2-1.el5.noarch requires perl(SVN::Mirror) = 0:0.71 On x86_64: perl-SVK-2.0.2-1.el5.noarch requires perl(SVN::Mirror) = 0:0.71 On i386: perl-SVK-2.0.2-1.el5.noarch requires perl(SVN::Mirror) = 0:0.71 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
Broken dependencies: perl-XML-Xerces
perl-XML-Xerces has broken dependencies in the epel-5 tree: On ppc: perl-XML-Xerces-2.7.0_0-4.el5.ppc requires libxerces-c.so.27 On x86_64: perl-XML-Xerces-2.7.0_0-4.el5.x86_64 requires libxerces-c.so.27()(64bit) On i386: perl-XML-Xerces-2.7.0_0-4.el5.i386 requires libxerces-c.so.27 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
Broken dependencies: perl-Getopt-GUI-Long
perl-Getopt-GUI-Long has broken dependencies in the epel-5 tree: On ppc: perl-Getopt-GUI-Long-0.91-5.el5.noarch requires perl(Gtk2) On x86_64: perl-Getopt-GUI-Long-0.91-5.el5.noarch requires perl(Gtk2) On i386: perl-Getopt-GUI-Long-0.91-5.el5.noarch requires perl(Gtk2) 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
Broken dependencies: perl-QWizard
perl-QWizard has broken dependencies in the epel-5 tree: On ppc: perl-QWizard-3.15-8.el5.noarch requires perl(Gtk2) On x86_64: perl-QWizard-3.15-8.el5.noarch requires perl(Gtk2) On i386: perl-QWizard-3.15-8.el5.noarch requires perl(Gtk2) 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-re-engine-RE2] Update to 0.13
commit 37bb58223f3beedf47c20cb7ece1d6e7c81153d8
Author: Emmanuel Seyman emman...@seyman.fr
Date: Sun Jan 25 04:07:45 2015 +0100
Update to 0.13
.gitignore |1 +
perl-re-engine-RE2.spec |5 -
sources |2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index baeaa49..57cf288 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
/re-engine-RE2-0.11.tar.gz
/re-engine-RE2-0.12.tar.gz
+/re-engine-RE2-0.13.tar.gz
diff --git a/perl-re-engine-RE2.spec b/perl-re-engine-RE2.spec
index 0db661b..1744178 100644
--- a/perl-re-engine-RE2.spec
+++ b/perl-re-engine-RE2.spec
@@ -1,6 +1,6 @@
Name: perl-re-engine-RE2
Summary: RE2 regex engine
-Version: 0.12
+Version: 0.13
Release: 1%{?dist}
License: GPL+ or Artistic
URL: http://search.cpan.org/dist/re-engine-RE2/
@@ -62,6 +62,9 @@ make test
%changelog
+* Sun Jan 25 2015 Emmanuel Seyman emman...@seyman.fr - 0.13-1
+- Update to 0.13
+
* Sun Jan 18 2015 Emmanuel Seyman emman...@seyman.fr - 0.12-1
- Update to 0.12
- Drop upstreamed patches
diff --git a/sources b/sources
index b37a758..1a0fbb7 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-5a334a6ce3206297cd6a6d702cc18742 re-engine-RE2-0.12.tar.gz
+85bf2cf9be48d287fdd3b0037cd9cefd re-engine-RE2-0.13.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
Re: koji hubs updated
On Fri, 23 Jan 2015, Kevin Fenzi wrote: There's one issue we are looking into to be aware of, builds now give: SysCallError: (-1, 'Unexpected EOF') instead of watching the build you just started. The build is running fine and you can follow it on the web interface. Hopefully we will push out a fix soon. Being on EL-6, the build is unfortunately not running. I just receive this: $ fedpkg build --nowait Could not execute build: (-1, 'Unexpected EOF') $ Greetings, Robert pgpdUDZlhypJT.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: amending the new package process
Ralf Corsepius wrote: This is not entirely true. GCC and related projects apply a pretty complex peer review process, with defined roles and privileges. (Cf. the file MAINTAINERS in GCC's sourcetree for details). Somewhat over-simplified the process condenses into All proposed changes must be peer-reviewed by somebody who is formally in charge of a component to be changed. Exceptions apply for obvious changes. It has been a while since I have last been following the GCC mailing lists (so this may or may not have changed since then), but at least back then, a maintainer for a given part of GCC was allowed to commit to that part of GCC without having it reviewed by a second person, and a global maintainer was allowed to commit to ANY part of GCC without having it reviewed by a second person. If you were allowed to approve other people's commits, you were also allowed to approve your own. There were also people only allowed to write after approval, but that was only the default/least-trusted level of commit access granted, and write after approval developers were also not allowed to review other people's submissions (unlike our system where any packager can review other packager's submissions, but never their own). Has this changed since? 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: Bodhi policy for pushing updates to stable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 24 Jan 2015 11:05:52 -0800 Adam Williamson adamw...@fedoraproject.org wrote: On Sat, 2015-01-24 at 17:42 +0100, Kevin Kofler wrote: Kamil Paral wrote: So, enforcing upgrade path for stable releases sounds good. But when we add development releases into the mix, we need to break upgrade path in certain cases. And we probably need to come up with a different solution to ensure you can correctly upgrade to it on the release day (maybe by using yum distro-sync-like approach instead of yum-update-like approach?). We will need to deal with these problems as our automation coverage increases. IMHO, we should 1. abolish the Alpha and Beta freezes (just take ALL new builds until the criteria are met), This is worth considering, at least, as the milestone freezes have (obviously, the clue's in the name) been around since *before* No Frozen Rawhide. In a sense, they and NFR aim to address the address the same problem: the tension between doing development work, and stabilizing a release. So I think it's at least worth considering. My instinct is still to oppose it, though, because we *do* still have potentially destabilizing changes landing in Branched during freezes. We quite often get an entire new GNOME build during freeze; sometimes we consider these and freeze-override them in, but we probably don't want one landing on the Wednesday we're trying to polish up an RC for approval on Thursday. I share the fear that we will never get to the point of the criteria being met. Same applies to the kernel, and various other bits like dracut and parted which affect the install-and-firstboot critpath parts especially. 2. open up the 0-day updates immediately on Final freeze, 3. in Final freeze periods, distinguish between freeze overrides and normal stable updates in Bodhi, instead of the current stable = freeze override setup. So there was some discussion of this whole issue on test@ around the F21 release time and I was a bit curt - retrospective apologies for that, release times are always a bit stressful. Someone proposed that using the 'updates' repository during the Branched period could help solve quite a few things here, and I think that's an interesting idea. To recap, at present, we don't use 'updates' for Branched at all until the few days between the Final Go decision and the actual release date, when we populate it with the '0-day' update set. Once we hit the 'Bodhi enablement point', builds go to updates-testing first, then when they're marked as 'stable' (either manually or via autokarma), they are pushed directly to 'fedora', not to 'updates'. Someone - I forget who, I'm sorry - suggested that we could push updates marked as 'stable' during milestone freezes into 'updates'. For Alpha and Beta, we'd then flush them from 'updates' back into 'fedora' immediately following the milestone release; for Final they'd just stay there and become 0-days. This actually changes little and gives us more work. for Alpha and Beta we push updates daily to updates-testing and it is enabled for users so they always get all potential bug fixes. At the point we hit the final Freeze we disable updates-testing on users machines. at this point we could look at pushing out updates. and cherry picking in fixes for the final release. The one place things would change if we pushed stable updates during freeze is that build would land in the buildroot a bit earlier. With a bit of time to think about it, I think this is actually potentially a very good idea. It gives us two solid improvements: 1. We can keep pushing out new builds to a place where users will actually get them, without destabilizing the image composes We have this today for the most part except for final freeze. 2. It would address the problem kparal identifies - when sending an update to a stable release would break the upgradepath because Branched is frozen, but we do really want the upgrade out for stable users There is always potential issues with upgrades. One issue I can see with it is, what do we do with the buildroot? If we have 'updates' in the buildroot then builds getting pushed to updates could *indirectly* affect the image composes by causing issues in package builds to fix blocker/FE bugs. So I'd probably prefer to see only 'fedora' used as the buildroot for Branched. This is a really tricky area. we would only use fedora for compose process but we could have to pull in extra builds because they were built against something newer. With a change along those lines, I think we could plausibly look at hard enforcement of the upgrade path, and it would be a good improvement. It may be necessary to have *some* kind of override mechanism for the case where we have a major security issue we really need to fix in stable ASAP, and karma for
File WWW-Shorten-3.06.tar.gz uploaded to lookaside cache by jdunn
A file has been added to the lookaside cache for perl-WWW-Shorten: 7fec4441d031973710ee61999f964bd2 WWW-Shorten-3.06.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
Re: initscripts
Am 23.01.2015 um 19:26 schrieb Dan Winship: On 01/23/2015 10:53 AM, Reindl Harald wrote: on servers and static machines you don't need any dynamic network configuration which is why NM in F22 will have a configure-and-quit mode for such machines which is still no valid reason to reconfigure network on tons of machines which just works for years untouched just for the fun of change something signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Flash plugin 0-day vulnerability in the wild
On Friday, January 23, 2015 08:44:03 AM Andrew Lutomirski wrote: $ sandbox -X xterm [nothing happens] It made me install selinux-policy-sandbox and seunshare. I am able to run Firefox under sandbox without any problem. I am running Fedora 21 KDE. -- Regards, Sudhir Khanger, sudhirkhanger.com, github.com/donniezazen, 5577 8CDB A059 085D 1D60 807F 8C00 45D9 F5EF C394. signature.asc Description: This is a digitally signed message part. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
