Re: How can we make F17 be able to boot on Macs (with or without reFit)
On Apr 24, 2012, at 7:39 PM, Matthew Garrett wrote: On Tue, Apr 24, 2012 at 07:08:39PM -0600, Chris Murphy wrote: On Apr 24, 2012, at 6:39 PM, Matthew Garrett wrote: Ok, I'll have to look at the CD issue. Can you report the initramfs problem? Yes. What component? Put it against the kernel for now, and we'll see if we can figure out what's going on. https://bugzilla.redhat.com/show_bug.cgi?id=816040 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
On 25/04/12 03:46, Brendan Jones wrote: I fully agree. We need to help the design team out, Agree, give ideas Drop the name but lets vote on a theme No, I think it should all be left to the design them. (with advice from legal, if necessary) Not in a let them do the work, but more of a the design team are the ones that understand design and concept. Give them the latitude to do what they know. When I tried college!. You could only include sources that were peer reviewed. Not stuff that had been voted on by x number of people in the street. Give the design team the freedom they need. Those with a background in design, step up. Help them out, don't complain after the fact. But for arthritis, I would be with them (my excuse, and sticking to it). -- Regards, Frank Jack of all, fubars -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F17 TC1 DVD still no btrfs as install option?
No installation type lists btrfs as an option for / or /home, whether LVM is checked or unchecked. Is this still being worked on? Or is this how it will be for release? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 TC1 DVD still no btrfs as install option?
Dne 25.4.2012 09:30, Chris Murphy napsal(a): No installation type lists btrfs as an option for / or /home, whether LVM is checked or unchecked. Is this still being worked on? Or is this how it will be for release? +1. I'd like to see this fixed before final. Vit -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
On Wed, Apr 25, 2012 at 9:05 AM, Frank Murphy frankl...@gmail.com wrote: On 25/04/12 03:46, Brendan Jones wrote: I fully agree. We need to help the design team out, Agree, give ideas Drop the name but lets vote on a theme No, I think it should all be left to the design them. (with advice from legal, if necessary) Not in a let them do the work, but more of a the design team are the ones that understand design and concept. Give them the latitude to do what they know. When I tried college!. You could only include sources that were peer reviewed. Not stuff that had been voted on by x number of people in the street. Give the design team the freedom they need. Those with a background in design, step up. Help them out, don't complain after the fact. But for arthritis, I would be with them (my excuse, and sticking to it). As Mairin told us, the design team don't need a theme to add a nice touch to our favorite distro! We should let them work with their skills -- Kévin Raymond (shaiton) GPG-Key: A5BCB3A2 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
Michael Cronenworth wrote: It would be nice to have a third option: -Change release names to release theme. We don't really need a name (IMO), but the theme adds a nice touch. A colour would be a nice clear release theme. You could even increment the first letter of the colour for each subsequent release. e.g. Amaranth - Blue - Celadon - ... See e.g http://en.wikipedia.org/wiki/List_of_colors There shouldn't be any major internationalisation issues, except for unlucky colours, which are plain superstition. It would be easy to make a theme which included that colour somewhere. Maybe someone else uses this scheme, however. Jeremy -- http://jeremysanders.net/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
File Net-SSLeay-1.48.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-Net-SSLeay: 4e10d9da28f26732e37807820bf72af5 Net-SSLeay-1.48.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-Net-SSLeay] Update to 1.48
commit 327192316b956f52de8894f2125b651362f9fcf3
Author: Paul Howarth p...@city-fan.org
Date: Wed Apr 25 10:00:13 2012 +0100
Update to 1.48
- New upstream release 1.48
- removed unneeded Debian_CPANTS.txt from MANIFEST
- fixed incorrect documentation about the best way to call CTX_set_options
- fixed problem that caused Undefined subroutine utf8::encode in
t/local/33_x509_create_cert.t (on perl 5.6.2)
- in examples and pod documentation, changed #!/usr/local/bin/perl to
#!/usr/bin/perl
- t/local/06_tcpecho.t now tries a number of ports to bind to until
successful
- No longer need to fix shellbangs in examples
perl-Net-SSLeay.spec | 20 +++-
sources |2 +-
2 files changed, 16 insertions(+), 6 deletions(-)
---
diff --git a/perl-Net-SSLeay.spec b/perl-Net-SSLeay.spec
index 960f65b..6ed5600 100644
--- a/perl-Net-SSLeay.spec
+++ b/perl-Net-SSLeay.spec
@@ -1,6 +1,6 @@
Name: perl-Net-SSLeay
-Version: 1.47
-Release: 3%{?dist}
+Version: 1.48
+Release: 1%{?dist}
Summary: Perl extension for using OpenSSL
Group: Development/Libraries
License: OpenSSL
@@ -39,10 +39,8 @@ so you can write servers or clients for more complicated
applications.
%prep
%setup -q -n Net-SSLeay-%{version}
-# Fix permissions and shellbangs in examples
-# to avoid bogus doc-file dependencies
+# Fix permissions in examples to avoid bogus doc-file dependencies
chmod -c 644 examples/*
-perl -pi -e 's|/usr/local/bin/perl|/usr/bin/perl|' examples/*.pl
# Remove redundant unversioned provide if we don't have rpm 4.9 or later
%global provfilt /bin/sh -c %{__perl_provides} | grep -Fvx
'perl(Net::SSLeay)'
@@ -81,6 +79,18 @@ rm -rf %{buildroot}
%{_mandir}/man3/Net::SSLeay::Handle.3pm*
%changelog
+* Wed Apr 25 2012 Paul Howarth p...@city-fan.org - 1.48-1
+- update to 1.48
+ - removed unneeded Debian_CPANTS.txt from MANIFEST
+ - fixed incorrect documentation about the best way to call CTX_set_options
+ - fixed problem that caused Undefined subroutine utf8::encode in
+t/local/33_x509_create_cert.t (on perl 5.6.2)
+ - in examples and pod documentation, changed #!/usr/local/bin/perl to
+#!/usr/bin/perl
+ - t/local/06_tcpecho.t now tries a number of ports to bind to until
+successful
+- no longer need to fix shellbangs in examples
+
* Thu Apr 19 2012 Paul Howarth p...@city-fan.org - 1.47-3
- simplify Test::Kwalitee conditional
diff --git a/sources b/sources
index 53bf95c..06732ff 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-5488d82a8e9291d6a7de5202a95cbbed Net-SSLeay-1.47.tar.gz
+4e10d9da28f26732e37807820bf72af5 Net-SSLeay-1.48.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: Fedora 18 Release name voting and Poll for whether to continue naming releases
On Wed, Apr 25, 2012 at 10:55 AM, Jeremy Sanders jer...@jeremysanders.net wrote: Amaranth - Blue - Celadon - ... See e.g http://en.wikipedia.org/wiki/List_of_colors There shouldn't be any major internationalisation issues, Well, two out of the three have no equivalent in Czech language. That doesn't prevent us from using the English name, but explaining what Beefy Miracle means would be easier than Celadon. Mirek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
On Wed, Apr 25, 2012 at 10:55 AM, Jeremy Sanders jer...@jeremysanders.net wrote: Michael Cronenworth wrote: It would be nice to have a third option: -Change release names to release theme. We don't really need a name (IMO), but the theme adds a nice touch. A colour would be a nice clear release theme. You could even increment the first letter of the colour for each subsequent release. e.g. Amaranth - Blue - Celadon - ... See e.g http://en.wikipedia.org/wiki/List_of_colors There shouldn't be any major internationalisation issues, except for unlucky colours, which are plain superstition. It would be easy to make a theme which included that colour somewhere. Maybe someone else uses this scheme, however. Jeremy -- http://jeremysanders.net/ Many Linux distributions are identified by a color. I would personally hate to have a purple, green or orange background… -- Kévin Raymond (shaiton) GPG-Key: A5BCB3A2 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-Net-SSLeay/f17] (3 commits) ...Update to 1.48
Summary of changes: e2b5365... make module Kwalitee conditional on distribution (*) 21741bc... Simplify Test::Kwalitee conditional (*) 3271923... Update to 1.48 (*) (*) 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
Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
Kévin Raymond wrote: Many Linux distributions are identified by a color. I would personally hate to have a purple, green or orange background… I wouldn't use the colour as the basis of the whole theme, but use it in a tasteful manner in highlights, etc. Jeremy -- http://jeremysanders.net/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F-17 Branched report: 20120425 changes
Compose started at Wed Apr 25 08:15:05 UTC 2012 Broken deps for x86_64 -- [aeolus-conductor] aeolus-conductor-0.4.0-2.fc17.noarch requires ruby(abi) = 0:1.8 [aeolus-configserver] aeolus-configserver-0.4.5-1.fc17.noarch requires ruby-nokogiri [dh-make] dh-make-0.55-4.fc17.noarch requires debhelper [dustmite] dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires libphobos2-ldc.so()(64bit) [egoboo] egoboo-2.7.5-11.fc17.x86_64 requires libenet-1.2.1.so()(64bit) [gcc-python-plugin] gcc-python2-debug-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python2-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python3-debug-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python3-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 [gorm] gorm-1.2.13-0.2.20110331.fc17.i686 requires libobjc.so.3 gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-gui.so.0.20 gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-base.so.1.23 gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libobjc.so.3()(64bit) gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libgnustep-gui.so.0.20()(64bit) gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libgnustep-base.so.1.23()(64bit) [ibus-panel-extensions] ibus-panel-extensions-1.4.99.20111207-2.fc17.i686 requires libibus-1.0.so.0 ibus-panel-extensions-1.4.99.20111207-2.fc17.x86_64 requires libibus-1.0.so.0()(64bit) [matreshka] matreshka-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-fastcgi-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-fastcgi-0.1.1-9.fc17.i686 requires libgnarl-4.6.so matreshka-fastcgi-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-fastcgi-0.1.1-9.fc17.x86_64 requires libgnarl-4.6.so()(64bit) matreshka-sql-core-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-core-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-sql-postgresql-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-postgresql-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-sql-sqlite-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-sqlite-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) [mcollective] mcollective-common-1.3.1-7.fc17.noarch requires ruby(abi) = 0:1.8 [meshlab] meshlab-1.3.1-2.fc17.x86_64 requires libmuparser.so.0()(64bit) [moksha] moksha-0.5.0-5.fc15.noarch requires pyevent [natus] libnatus-V8-0.1.5-2.fc15.x86_64 requires libv8-3.0.0.1.so()(64bit) [ocaml-augeas] ocaml-augeas-0.4-9.fc15.x86_64 requires ocaml(runtime) = 0:3.12.0 [openvrml] libopenvrml-0.18.8-2.fc16.i686 requires libboost_thread-mt.so.1.47.0 libopenvrml-0.18.8-2.fc16.i686 requires libboost_system-mt.so.1.47.0 libopenvrml-0.18.8-2.fc16.i686 requires libboost_filesystem-mt.so.1.47.0 libopenvrml-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) libopenvrml-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) libopenvrml-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) libopenvrml-gl-0.18.8-2.fc16.i686 requires libboost_thread-mt.so.1.47.0 libopenvrml-gl-0.18.8-2.fc16.i686 requires libboost_system-mt.so.1.47.0 libopenvrml-gl-0.18.8-2.fc16.i686 requires libboost_filesystem-mt.so.1.47.0 libopenvrml-gl-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) libopenvrml-gl-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) libopenvrml-gl-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires java-1.6.0-openjdk(x86-64) openvrml-javascript-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) openvrml-javascript-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) openvrml-javascript-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) openvrml-nodes-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) openvrml-nodes-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) openvrml-nodes-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) openvrml-xembed-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit)
Re: F17 TC1 DVD still no btrfs as install option?
On 25/04/12 09:48, Vít Ondruch wrote: +1. I'd like to see this fixed before final. Yes, me too. Afaik, SuSE supports btrfs even for their enterprise distro. -- Matthias Runge mru...@matthias-runge.de mru...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
On Wed, Apr 25, 2012 at 4:09 AM, Kévin Raymond shai...@fedoraproject.org wrote: On Wed, Apr 25, 2012 at 10:55 AM, Jeremy Sanders jer...@jeremysanders.net wrote: Michael Cronenworth wrote: It would be nice to have a third option: -Change release names to release theme. We don't really need a name (IMO), but the theme adds a nice touch. A colour would be a nice clear release theme. You could even increment the first letter of the colour for each subsequent release. e.g. Amaranth - Blue - Celadon - ... See e.g http://en.wikipedia.org/wiki/List_of_colors There shouldn't be any major internationalisation issues, except for unlucky colours, which are plain superstition. It would be easy to make a theme which included that colour somewhere. Maybe someone else uses this scheme, however. Jeremy -- http://jeremysanders.net/ Many Linux distributions are identified by a color. I would personally hate to have a purple, green or orange background… So are we, blue. -J -- Kévin Raymond (shaiton) GPG-Key: A5BCB3A2 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- http://cecinestpasunefromage.wordpress.com/ in your fear, seek only peace in your fear, seek only love -d. bowie -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 TC1 DVD still no btrfs as install option?
On Wed, Apr 25, 2012 at 7:34 AM, Matthias Runge mru...@matthias-runge.de wrote: On 25/04/12 09:48, Vít Ondruch wrote: +1. I'd like to see this fixed before final. Yes, me too. Afaik, SuSE supports btrfs even for their enterprise distro. It's deferred. There's still no viable btrfs.fsck. I believe you can create btrfs filesystems via kickstart, but that is it. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
On 04/24/2012 05:14 AM, Miroslav Suchý wrote: I can keep only 3-5last releases in my poor head. Then just *don't*. F14 is the past. Let it go. -- Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
On 25.4.2012 15:05, Peter Jones wrote: On 04/24/2012 05:14 AM, Miroslav Suchý wrote: I can keep only 3-5last releases in my poor head. Then just *don't*. F14 is the past. Let it go. Tell it to Mythdora which is based on Fedora Cambridge. Or RaspberryPi remix which is based on Fedora Laughlin. And many others. Fedora is not isolated world. Mirek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
On Wed, Apr 25, 2012 at 2:35 PM, Miroslav Suchy msu...@redhat.com wrote: On 25.4.2012 15:05, Peter Jones wrote: On 04/24/2012 05:14 AM, Miroslav Suchý wrote: I can keep only 3-5last releases in my poor head. Then just *don't*. F14 is the past. Let it go. Tell it to Mythdora which is based on Fedora Cambridge. Or RaspberryPi remix which is based on Fedora Laughlin. There will be a remix for the Raspbery Pi based on F-17 very shortly. F-17 is the first ARM release that we've caught up post the bringup of a completely new 2nd ARM platform. Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: How can we make F17 be able to boot on Macs (with or without reFit)
On 04/24/2012 10:20 PM, John Reiser wrote: Choosing the Windows logo gets a VGA-like display (black with white character-cell text): 1. 2. 3. Select CD-ROM Boot Type : and there is no response to console keyboard. So FAIL again. Even though this disc is wrong for that machine, so the test isn't really valid, it's worth mentioning that *any* time you see this screen, it's a bug in the CSM - the BIOS emulation layer on top of UEFI is completely failing to comply with the El Torito standard for CD booting when it sees multiple boot sections on a CD. Rather than implementing correct support to select which boot section to use, this version of the CSM, which is shared among Apple machines and other vendors' alike, presents all of the choices as a menu instead. Awesomely the keyboard driver not being present is a /second/ firmware bug. On some machines it is present, and on those selecting 1 will work and continue booting as if on a BIOS machine. Apple have fixed this on newer hardware, but I don't think they've ever pushed a fix back to this generation. -- Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
exiv2-0.23 coming soon
I plan on importing exiv2-0.23 into rawhide soon'ish. It includes an ABI bump, so dependent packages will require rebuilding, including: calligra darktable entangle geeqie gipfel gnome-color-manager gnome-commander gpscorrelate gthumb gwenview hugin immix kde-runtime krename libextractor libgexiv2 libkexiv2 luminance-hdr merkaartor oyranos pyexiv2 rawstudio strigi ufraw I'll take care of kicking off a round of rebuilds for these. -- rex ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: disruptive libffi upgrade
On Sat, 2012-04-14 at 10:09 -0400, Colin Walters wrote: On Fri, 2012-04-13 at 20:58 -0400, Anthony Green wrote: Sorry folks -- thanks for untagging. I'll ping the list again after May 9, as was suggested earlier in this thread. Here's a lightly tested patch which implements my suggestion of keeping the symbols as empty stubs. Ok, so the current state of things now is that the libffi build has been untagged, which basically means that while the build is now unused, but the Fedora package git is a time bomb for whoever goes to work on it next unless we also revert the changes there. And the longer we let the upstream release stand, it's more likely various distributions and operating systems consume it and we end up with different ABIs in the wild. Anthony, any opinions on this patch? I really think the cost to libffi for keeping the debug-only symbols as stubs is tiny relative to the cost of bumping the ABI. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: How can we make F17 be able to boot on Macs (with or without reFit)
On Wed, Apr 25, 2012 at 01:39:20AM +0100, Matthew Garrett wrote: Ok, I'll have to look at the CD issue. Can you report the initramfs problem? Figured out the CD problem, I'll push a fix to git. Looking at the initramfs problem now. -- Matthew Garrett | mj...@srcf.ucam.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
File constant-defer-5.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-constant-defer: 519232b64896395b84b41f5300d1cab3 constant-defer-5.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: F17 TC1 DVD still no btrfs as install option?
On Wed, Apr 25, 2012 at 01:34:07PM +0200, Matthias Runge wrote: On 25/04/12 09:48, Vít Ondruch wrote: +1. I'd like to see this fixed before final. Yes, me too. Afaik, SuSE supports btrfs even for their enterprise distro. For added laughs, SLES does not support read-write ext4. Ext4 read-only support is provided for migrating to btrfs. -- Tomasz Torcz ,,(...) today's high-end is tomorrow's embedded processor.'' xmpp: zdzich...@chrome.pl -- Mitchell Blank on LKML -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-constant-defer] Import
commit af34c75358aad7b813795c2aac12c7c5eeb536b1
Author: Petr Písař ppi...@redhat.com
Date: Wed Apr 25 17:07:56 2012 +0200
Import
.gitignore |1 +
perl-constant-defer.spec | 57 ++
sources |1 +
3 files changed, 59 insertions(+), 0 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index e69de29..24fb515 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/constant-defer-5.tar.gz
diff --git a/perl-constant-defer.spec b/perl-constant-defer.spec
new file mode 100644
index 000..d7b0b38
--- /dev/null
+++ b/perl-constant-defer.spec
@@ -0,0 +1,57 @@
+Name: perl-constant-defer
+Version:5
+Release:1%{?dist}
+Summary:Constant subs with deferred value calculation
+License:GPLv3+
+Group: Development/Libraries
+URL:http://search.cpan.org/dist/constant-defer/
+Source0:
http://www.cpan.org/authors/id/K/KR/KRYDE/constant-defer-%{version}.tar.gz
+BuildArch: noarch
+# The inc/my_pod2html is not called
+BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(lib)
+# Run-Time:
+BuildRequires: perl(Carp)
+# Tests:
+BuildRequires: perl(Devel::FindRef)
+BuildRequires: perl(Exporter)
+BuildRequires: perl(Scalar::Util)
+BuildRequires: perl(Test)
+BuildRequires: perl(Test::More)
+# Optionals tests:
+BuildRequires: perl(Data::Dumper)
+BuildRequires: perl(Devel::StackTrace)
+Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+Requires: perl(Carp)
+
+%description
+constant::defer creates a subroutine which on the first call runs given
+code to calculate its value, and on the second and subsequent calls just
+returns that value, like a constant. The value code is discarded once run,
+allowing it to be garbage collected.
+
+%prep
+%setup -q -n constant-defer-%{version}
+chmod -x examples/*
+
+%build
+%{__perl} Makefile.PL INSTALLDIRS=vendor
+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 -depth -type d -exec rmdir {} 2/dev/null \;
+%{_fixperms} $RPM_BUILD_ROOT/*
+
+%check
+make test
+
+%files
+%doc Changes COPYING examples README
+%{perl_vendorlib}/*
+%{_mandir}/man3/*
+
+%changelog
+* Wed Apr 25 2012 Petr Pisar ppi...@redhat.com 5-1
+- Specfile autogenerated by cpanspec 1.78.
diff --git a/sources b/sources
index e69de29..89e633c 100644
--- a/sources
+++ b/sources
@@ -0,0 +1 @@
+519232b64896395b84b41f5300d1cab3 constant-defer-5.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-RPM2
perl-RPM2 has broken dependencies in the rawhide tree: On x86_64: perl-RPM2-1.0-2.fc17.x86_64 requires librpmio.so.2()(64bit) perl-RPM2-1.0-2.fc17.x86_64 requires librpm.so.2()(64bit) On i386: perl-RPM2-1.0-2.fc17.i686 requires librpmio.so.2 perl-RPM2-1.0-2.fc17.i686 requires librpm.so.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
New cfitsio (3.300) in rawhide
Hi, a new cfistio package (3.300) as landed in rawhide. Packages depending on cfitsio should be rebuilt. -- Sergio Pascual http://guaix.fis.ucm.es/~spr +34 91 394 5018 gpg fingerprint: 5203 B42D 86A0 5649 410A F4AC A35F D465 F263 BCCC Departamento de Astrofísica -- Universidad Complutense de Madrid (Spain) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: New cfitsio (3.300) in rawhide
On Wed, Apr 25, 2012 at 10:35 AM, Sergio Pascual sergi...@fis.ucm.es wrote: Hi, a new cfistio package (3.300) as landed in rawhide. Packages depending on cfitsio should be rebuilt. soname bumps should be announced in advance, ideally. -J -- Sergio Pascual http://guaix.fis.ucm.es/~spr +34 91 394 5018 gpg fingerprint: 5203 B42D 86A0 5649 410A F4AC A35F D465 F263 BCCC Departamento de Astrofísica -- Universidad Complutense de Madrid (Spain) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- http://cecinestpasunefromage.wordpress.com/ in your fear, seek only peace in your fear, seek only love -d. bowie -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Testing packages with mock and Xnest?
On Fri, Apr 20, 2012 at 12:15:45PM -0500, Richard Shaw wrote: Here's the draft: https://fedoraproject.org/wiki/Packaging/Testing Comments/additions welcomed! Cool. Ive read the draft now. I thought it was going to be about using Xnest with graphical unittests. Oops. Doesn't 100% fit in the Packaging Guidelines but perhaps we can link to it when we mention that reviewers should test that a package functions as intended. /me notices that although that instruction is in the ReviewGuidelines we dont seem to have it on the main Guidelines page. -Toshio pgpABxr9YaOvX.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 TC1 DVD still no btrfs as install option?
On Wed, Apr 25, 2012 at 11:07 AM, Tomasz Torcz to...@pipebreaker.pl wrote: On Wed, Apr 25, 2012 at 01:34:07PM +0200, Matthias Runge wrote: On 25/04/12 09:48, Vít Ondruch wrote: +1. I'd like to see this fixed before final. Yes, me too. Afaik, SuSE supports btrfs even for their enterprise distro. For added laughs, SLES does not support read-write ext4. Ext4 read-only support is provided for migrating to btrfs. That's because Btrfs is way more stable than ext4, Josef -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 TC1 DVD still no btrfs as install option?
On Wed, 2012-04-25 at 12:03 -0400, Josef Bacik wrote: On Wed, Apr 25, 2012 at 11:07 AM, Tomasz Torcz to...@pipebreaker.pl wrote: On Wed, Apr 25, 2012 at 01:34:07PM +0200, Matthias Runge wrote: On 25/04/12 09:48, Vít Ondruch wrote: +1. I'd like to see this fixed before final. Yes, me too. Afaik, SuSE supports btrfs even for their enterprise distro. For added laughs, SLES does not support read-write ext4. Ext4 read-only support is provided for migrating to btrfs. That's because Btrfs is way more stable than ext4, [citation needed] -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
File Net-Twitter-3.18002.tar.gz uploaded to lookaside cache by jdunn
A file has been added to the lookaside cache for perl-Net-Twitter: 6bb5ffa27023ed854841bc80b0ee4797 Net-Twitter-3.18002.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-Net-Twitter] Upgrade to 3.18002
commit 387342c8e0fe3f903259516c5731faeff7bbc834
Author: Julian C. Dunn jd...@aquezada.com
Date: Wed Apr 25 12:29:15 2012 -0400
Upgrade to 3.18002
.gitignore|1 +
perl-Net-Twitter.spec |7 +--
sources |2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index a10652d..3011bad 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,2 @@
/Net-Twitter-3.18001.tar.gz
+/Net-Twitter-3.18002.tar.gz
diff --git a/perl-Net-Twitter.spec b/perl-Net-Twitter.spec
index 461e4ef..7396616 100644
--- a/perl-Net-Twitter.spec
+++ b/perl-Net-Twitter.spec
@@ -1,5 +1,5 @@
Name: perl-Net-Twitter
-Version:3.18001
+Version:3.18002
Release:1%{?dist}
Summary:Perl interface to the Twitter API
License:GPL+ or Artistic
@@ -47,7 +47,7 @@ BuildRequires: perl(Try::Tiny) = 0.03
BuildRequires: perl(URI) = 1.4
BuildRequires: perl(URI::Escape)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
-Requires: perl(Net::Netrc)
+Requires: perl(Net::Netrc)
%description
This module provides a perl interface to the Twitter APIs. See
@@ -78,5 +78,8 @@ env TEST_POD=1 make test
%{_mandir}/man3/*
%changelog
+* Wed Apr 25 2012 Julian C. Dunn jd...@aquezada.com 3.18002-1
+- Upgrade to 3.18002
+
* Tue Mar 27 2012 Julian C. Dunn jd...@aquezada.com 3.18001-1
- Initial release.
diff --git a/sources b/sources
index 7158f51..88d388d 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-88665d245f72b48ee87817edb5906d00 Net-Twitter-3.18001.tar.gz
+6bb5ffa27023ed854841bc80b0ee4797 Net-Twitter-3.18002.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
Self Introduction
Hello all! I'm trying to package Fest for Fedora, and I need a sponsor for this first package: https://bugzilla.redhat.com/show_bug.cgi?id=816264 This is my first package, but I'm not new to Fedora, I recently joined Red Hat, after many year of Free Software work with other companies, I've been using Fedora since Fedora Core 1, and before that I was a Red Hat Linux user (since 6.0!). During the years, I've contribute some fixes here and there in Fedora packages (although mostly upstream), but this is my first attempt at packaging a full rpm set of packages. Cheers, Mario -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 TC1 DVD still no btrfs as install option?
On Wed, Apr 25, 2012 at 12:25 PM, Colin Walters walt...@verbum.org wrote: On Wed, 2012-04-25 at 12:03 -0400, Josef Bacik wrote: On Wed, Apr 25, 2012 at 11:07 AM, Tomasz Torcz to...@pipebreaker.pl wrote: On Wed, Apr 25, 2012 at 01:34:07PM +0200, Matthias Runge wrote: On 25/04/12 09:48, Vít Ondruch wrote: +1. I'd like to see this fixed before final. Yes, me too. Afaik, SuSE supports btrfs even for their enterprise distro. For added laughs, SLES does not support read-write ext4. Ext4 read-only support is provided for migrating to btrfs. That's because Btrfs is way more stable than ext4, [citation needed] https://twitter.com/#!/josefbacik/status/195190540529184768 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RFC: Primary architecture promotion requirements
On Mon, 2012-04-23 at 12:59 -0700, Brendan Conoboy wrote: It's not about anaconda specifically, it's about having a standard installer experience across all PAs to the extent technically sensible. Maybe something else will supplant anaconda in time. FWIW, in writing the QA release criteria, we used the generic term 'the installer' rather than the specific 'anaconda' to avoid this kind of ambiguity. In general I tend to prefer the use of generic terms in this kind of policy document for exactly this reason - to acknowledge and protect against the possibility of the currently-favoured implementation of any particular thing changing in future. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
On Tue, 2012-04-24 at 13:59 +0100, Ian Malone wrote: On 23 April 2012 14:06, Adam Williamson awill...@redhat.com wrote: I'm not against release names because some people are supposed to have been offended by the words 'Beefy Miracle' I don't know about offended, it just sounds silly. Some who follow a religion which venerates the cow have asserted that they find the name offensive, apparently -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: firewalld / iptables.service past F17
On Tue, 2012-04-24 at 09:30 -0500, Jon Ciesla wrote: Nothing is being taken away, the default is being changed. If you're using Fedora in production, I presume you're installing with Kickstart. It's worth noting that if the question is how does firewalld handle upgrades, I think it may be somewhat irrelevant because AFAIK even when firewalld was going to be the F17 default, we never implemented anything to cause upgraded systems to switch to it. It was only new installs which were getting firewalld. Upgraded ones stuck with the static iptables/s-c-f/lokkit system. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Self introduction and sponsorship request
On Tue, 2012-04-24 at 14:33 -0300, Paulo César Pereira de Andrade wrote: Note that I am a Mandriva employee and my major interest is to become more aware of how Fedora works, so, I want to contribute like I did with several other projects in the past, that is, after work at home and/or weekends. Welcome to Fedora, Paulo! Don't worry about that humming sound, it's just the mind control ray cranking up =) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 TC1 DVD still no btrfs as install option?
On Wed, 2012-04-25 at 09:03 -0400, Josh Boyer wrote: On Wed, Apr 25, 2012 at 7:34 AM, Matthias Runge mru...@matthias-runge.de wrote: On 25/04/12 09:48, Vít Ondruch wrote: +1. I'd like to see this fixed before final. Yes, me too. Afaik, SuSE supports btrfs even for their enterprise distro. It's deferred. There's still no viable btrfs.fsck. I believe you can create btrfs filesystems via kickstart, but that is it. It's btrfs-as-default that's deferred. We've had it available as an option via interactive anaconda for many releases now (for a while it required a Sekrit kernel parameter to prove you were One Of The Initiated, but that was dropped a while back). Its absence as an option in the interactive installer in F17 is a regression, but an intentional one. See http://fedorapeople.org/groups/docs/release-notes/en-US/ , section 2.3.3: 2.3.3. btrfs btrfs is not available as a target file system during installation. This is a temporary situation and will be resolved in Fedora 18. btrfs is still available after installation. The reason is that anaconda's *backend* code for dealing with btrfs was rewritten early in F17 cycle to be much more sophisticated and take advantage of all btrfs' shiny features. At that time, it was still expected that the new anaconda UI would land for F17, so the frontend code in the old UI was not updated to cope with the new backend code. Unfortunately, newui got deferred to F18, so now we're stuck in F17 with some awesome backend code but no matching frontend code. No-one has time to substantially rewrite the oldui partitioning code just for btrfs, so it's been taken out from the UI entirely just for this release. You can still use btrfs during installation in F17 but only if you use a kickstart. Happily, upgrading installations with btrfs partitions works fine. (Side thought on the release notes for the documentation team - it seems a bit odd that this is in the 'notes for system administrators' section when sections exist for both 'file systems' and 'installer', either of which seems more appropriate for a note about use of a file system in the installer. : Also, it would be good if the note explained that you can use btrfs via kickstart.) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 TC1 DVD still no btrfs as install option?
2012/4/25 Josef Bacik jo...@toxicpanda.com: On Wed, Apr 25, 2012 at 12:25 PM, Colin Walters walt...@verbum.org wrote: On Wed, 2012-04-25 at 12:03 -0400, Josef Bacik wrote: On Wed, Apr 25, 2012 at 11:07 AM, Tomasz Torcz to...@pipebreaker.pl wrote: On Wed, Apr 25, 2012 at 01:34:07PM +0200, Matthias Runge wrote: On 25/04/12 09:48, Vít Ondruch wrote: +1. I'd like to see this fixed before final. Yes, me too. Afaik, SuSE supports btrfs even for their enterprise distro. For added laughs, SLES does not support read-write ext4. Ext4 read-only support is provided for migrating to btrfs. That's because Btrfs is way more stable than ext4, [citation needed] https://twitter.com/#!/josefbacik/status/195190540529184768 Is this a joke? Btrfs more stable than ext4??? Not really??? -- Chris -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 TC1 DVD still no btrfs as install option?
On Wed, Apr 25, 2012 at 1:22 PM, Chris xchris...@googlemail.com wrote: 2012/4/25 Josef Bacik jo...@toxicpanda.com: On Wed, Apr 25, 2012 at 12:25 PM, Colin Walters walt...@verbum.org wrote: On Wed, 2012-04-25 at 12:03 -0400, Josef Bacik wrote: On Wed, Apr 25, 2012 at 11:07 AM, Tomasz Torcz to...@pipebreaker.pl wrote: On Wed, Apr 25, 2012 at 01:34:07PM +0200, Matthias Runge wrote: On 25/04/12 09:48, Vít Ondruch wrote: +1. I'd like to see this fixed before final. Yes, me too. Afaik, SuSE supports btrfs even for their enterprise distro. For added laughs, SLES does not support read-write ext4. Ext4 read-only support is provided for migrating to btrfs. That's because Btrfs is way more stable than ext4, [citation needed] https://twitter.com/#!/josefbacik/status/195190540529184768 Is this a joke? Btrfs more stable than ext4??? Not really??? According to the stab-o-matic stability testing framework[1] btrfs scores a 63 whereas ext4 scores a 37, so yes, I'm completely serious, Josef [1] credit goes to Sandeen for that one. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 TC1 DVD still no btrfs as install option?
2012/4/25 Josef Bacik jo...@toxicpanda.com: On Wed, Apr 25, 2012 at 1:22 PM, Chris xchris...@googlemail.com wrote: 2012/4/25 Josef Bacik jo...@toxicpanda.com: On Wed, Apr 25, 2012 at 12:25 PM, Colin Walters walt...@verbum.org wrote: On Wed, 2012-04-25 at 12:03 -0400, Josef Bacik wrote: On Wed, Apr 25, 2012 at 11:07 AM, Tomasz Torcz to...@pipebreaker.pl wrote: On Wed, Apr 25, 2012 at 01:34:07PM +0200, Matthias Runge wrote: On 25/04/12 09:48, Vít Ondruch wrote: +1. I'd like to see this fixed before final. Yes, me too. Afaik, SuSE supports btrfs even for their enterprise distro. For added laughs, SLES does not support read-write ext4. Ext4 read-only support is provided for migrating to btrfs. That's because Btrfs is way more stable than ext4, [citation needed] https://twitter.com/#!/josefbacik/status/195190540529184768 Is this a joke? Btrfs more stable than ext4??? Not really??? According to the stab-o-matic stability testing framework[1] btrfs scores a 63 whereas ext4 scores a 37, so yes, I'm completely serious, And why is Btrfs marked as experimental by upstream? If it is really more stable than ext4, why does RHEL 6.3 beta not support Btrfs? I am very surprised... -- Chris -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] ABRT Test Day tomorrow - 2012-Apr-26
Friends of ABRT, Quality Engineers, fellow testers - There's a Test Day going on tomorrow, Thursday 2012-Apr-26: https://fedoraproject.org/wiki/Test_Day:2012-04-26_ABRT_and_deduplication_service Looking at ABRT v2.0.10 (and related components) in Fedora 17 (see the feature page at https://fedoraproject.org/wiki/Features/ABRTBacktraceDeduplication). As always, the event is in #fedora-test-day in Freenode IRC, and all the test instructions are on the Wiki. There will be a good turnout of developers, so it's a great chance to help shake out any remaining ABRT bugs for Fedora 17. Please help out if you have a chance! Thanks, Richard Michal ___ 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
Re: F17 TC1 DVD still no btrfs as install option?
On Wed, 25 Apr 2012, Josef Bacik wrote: On Wed, Apr 25, 2012 at 1:22 PM, Chris xchris...@googlemail.com wrote: 2012/4/25 Josef Bacik jo...@toxicpanda.com: On Wed, Apr 25, 2012 at 12:25 PM, Colin Walters walt...@verbum.org wrote: On Wed, 2012-04-25 at 12:03 -0400, Josef Bacik wrote: On Wed, Apr 25, 2012 at 11:07 AM, Tomasz Torcz to...@pipebreaker.pl wrote: On Wed, Apr 25, 2012 at 01:34:07PM +0200, Matthias Runge wrote: On 25/04/12 09:48, Vít Ondruch wrote: +1. I'd like to see this fixed before final. Yes, me too. Afaik, SuSE supports btrfs even for their enterprise distro. For added laughs, SLES does not support read-write ext4. Ext4 read-only support is provided for migrating to btrfs. That's because Btrfs is way more stable than ext4, [citation needed] https://twitter.com/#!/josefbacik/status/195190540529184768 Is this a joke? Btrfs more stable than ext4??? Not really??? According to the stab-o-matic stability testing framework[1] btrfs scores a 63 whereas ext4 scores a 37, so yes, I'm completely serious, Josef [1] credit goes to Sandeen for that one. Josef, I'm a little confused here too. Can you explain to me the testing infrastructure involved with stab-o-matic? thanks, -sv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 TC1 DVD still no btrfs as install option?
Am 25.04.2012 18:03, schrieb Josef Bacik: On Wed, Apr 25, 2012 at 11:07 AM, Tomasz Torcz to...@pipebreaker.pl wrote: On Wed, Apr 25, 2012 at 01:34:07PM +0200, Matthias Runge wrote: On 25/04/12 09:48, Vít Ondruch wrote: +1. I'd like to see this fixed before final. Yes, me too. Afaik, SuSE supports btrfs even for their enterprise distro. For added laughs, SLES does not support read-write ext4. Ext4 read-only support is provided for migrating to btrfs. That's because Btrfs is way more stable than ext4, oh no, please do not make such jokes as long there exists even no fsck and as long there are zero production worksloads generic tests are useless and what about workloads like virtual machines where AFAIK BTRFS is still completly unuseable BTRFS has many nice things and will be in the future a good FS but call it more stable than ext4 while ext4 is since years useable for production is a past-1st-april joke signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
On 25/04/12 17:51, Adam Williamson wrote: which venerates the cow Ah, now Adam, As bad as she is you can't be calling anyone a cow ;) -- Regards, Frank Jack of all, fubars -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 TC1 DVD still no btrfs as install option?
On Wed, Apr 25, 2012 at 1:35 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 25.04.2012 18:03, schrieb Josef Bacik: On Wed, Apr 25, 2012 at 11:07 AM, Tomasz Torcz to...@pipebreaker.pl wrote: On Wed, Apr 25, 2012 at 01:34:07PM +0200, Matthias Runge wrote: On 25/04/12 09:48, Vít Ondruch wrote: +1. I'd like to see this fixed before final. Yes, me too. Afaik, SuSE supports btrfs even for their enterprise distro. For added laughs, SLES does not support read-write ext4. Ext4 read-only support is provided for migrating to btrfs. That's because Btrfs is way more stable than ext4, oh no, please do not make such jokes as long there exists even no fsck and as long there are zero production worksloads generic tests are useless and what about workloads like virtual machines where AFAIK BTRFS is still completly unuseable BTRFS has many nice things and will be in the future a good FS but call it more stable than ext4 while ext4 is since years useable for production is a past-1st-april joke Wow ok I would have thought after the stab-o-matic thing it would have been obvious I was kidding, Btrfs still has a little ways to go before it is as stable as Ext4, though we are getting closer. Thanks, Josef -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 TC1 DVD still no btrfs as install option?
On 04/25/2012 06:22 PM, Chris wrote: 2012/4/25 Josef Bacik jo...@toxicpanda.com: That's because Btrfs is way more stable than ext4, [citation needed] https://twitter.com/#!/josefbacik/status/195190540529184768 Is this a joke? Btrfs more stable than ext4??? Not really??? I think the tongue-in-cheek tags in Josef's mail collided with some antitongue-in-cheek tags in the intertubes and were annihilated. ;) Regards, Bryn. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Orphaning Papyon
Hi all, I'm orphaning papyon, since Empathy no longer uses telepathy-butterfly for MSN support. papyon is pretty much dead upstream, but I believe a few of the lesser known IM clients may still be using. Thanks, /B -- Brian Pepple bpep...@fedoraproject.org https://fedoraproject.org/wiki/User:Bpepple gpg --keyserver pgp.mit.edu --recv-keys 810CC15E BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Self introduction and sponsorship request
Em 25 de abril de 2012 14:07, Adam Williamson awill...@redhat.com escreveu: On Tue, 2012-04-24 at 14:33 -0300, Paulo César Pereira de Andrade wrote: Note that I am a Mandriva employee and my major interest is to become more aware of how Fedora works, so, I want to contribute like I did with several other projects in the past, that is, after work at home and/or weekends. Welcome to Fedora, Paulo! Don't worry about that humming sound, it's just the mind control ray cranking up =) Hi Adam, nice to meet you again :-) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
On Wed, 2012-04-25 at 18:58 +0100, Frank Murphy wrote: On 25/04/12 17:51, Adam Williamson wrote: which venerates the cow Ah, now Adam, As bad as she is you can't be calling anyone a cow ;) Er...wha? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 TC1 DVD still no btrfs as install option?
On 25/04/12 19:17, Adam Williamson wrote: Its absence as an option in the interactive installer in F17 is a regression, but an intentional one. See http://fedorapeople.org/groups/docs/release-notes/en-US/ , section 2.3.3: 2.3.3. btrfs btrfs is not available as a target file system during installation. This is a temporary situation and will be resolved in Fedora 18. btrfs is still available after installation. The reason is that anaconda's *backend* code for dealing with btrfs was rewritten early in F17 cycle to be much more sophisticated and take advantage of all btrfs' shiny features. At that time, it was still expected that the new anaconda UI would land for F17, so the frontend code in the old UI was not updated to cope with the new backend code. Unfortunately, newui got deferred to F18, so now we're stuck in F17 with some awesome backend code but no matching frontend code. No-one has time to substantially rewrite the oldui partitioning code just for btrfs, so it's been taken out from the UI entirely just for this release. Thank you Adam for this explanation! Sounds reasonable, and I'd say, let's take another round and make it rock solid for F18. -- Matthias Runge mru...@matthias-runge.de mru...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
On 25/04/12 19:25, Adam Williamson wrote: On Wed, 2012-04-25 at 18:58 +0100, Frank Murphy wrote: On 25/04/12 17:51, Adam Williamson wrote: which venerates the cow Ah, now Adam, As bad as she is you can't be calling anyone a cow ;) Er...wha? I thought you were calling the cow a cow. Which in some western cultures is a derogatory term. So you shouldn't call a cow a cow. -- Regards, Frank Jack of all, fubars -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17 TC1 DVD still no btrfs as install option?
Josef Bacik wrote: Wow ok I would have thought after the stab-o-matic thing it would have been obvious I was kidding, Btrfs still has a little ways to go before it is as stable as Ext4, though we are getting closer. Thanks, I see you don't have a sarcasm tag. Please take the one I've attached. Use with caution! :) *** * Attachment: * *** * /sarcasm * *** -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
On Wed, 2012-04-25 at 19:37 +0100, Frank Murphy wrote: On 25/04/12 19:25, Adam Williamson wrote: On Wed, 2012-04-25 at 18:58 +0100, Frank Murphy wrote: On 25/04/12 17:51, Adam Williamson wrote: which venerates the cow Ah, now Adam, As bad as she is you can't be calling anyone a cow ;) Er...wha? I thought you were calling the cow a cow. Which in some western cultures is a derogatory term. So you shouldn't call a cow a cow. I...no, I was referring to cows. You know. The things which have four legs, go moo, and dispense tasty, tasty milk. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
OT Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
On 25/04/12 19:43, Adam Williamson wrote: I...no, I was referring to cows. You know. The things which have four legs, go moo, and dispense tasty, tasty milk. Ah right, we call it the fridge. Goes rrr every so often. -- Regards, Frank Jack of all, fubars -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: OT Re: Fedora 18 Release name voting and Poll for whether to continue naming releases
On Wed, Apr 25, 2012 at 1:48 PM, Frank Murphy frankl...@gmail.com wrote: On 25/04/12 19:43, Adam Williamson wrote: I...no, I was referring to cows. You know. The things which have four legs, go moo, and dispense tasty, tasty milk. Ah right, we call it the fridge. Goes rrr every so often. I have both milk and rum in my fridge, but I still call it my fridge. -J -- Regards, Frank Jack of all, fubars -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- http://cecinestpasunefromage.wordpress.com/ in your fear, seek only peace in your fear, seek only love -d. bowie -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Testing packages with mock and Xnest?
On Wed, Apr 25, 2012 at 10:46 AM, Toshio Kuratomi a.bad...@gmail.com wrote: On Fri, Apr 20, 2012 at 12:15:45PM -0500, Richard Shaw wrote: Here's the draft: https://fedoraproject.org/wiki/Packaging/Testing Comments/additions welcomed! Cool. Ive read the draft now. I thought it was going to be about using Xnest with graphical unittests. Oops. Doesn't 100% fit in the Packaging Guidelines but perhaps we can link to it when we mention that reviewers should test that a package functions as intended. Hmm... I think that would be quite a bit more complicated. I don't think Xnest would be the right tool for that. I really don't know enough about X to guess. I would think that the build server probably runs without X and even if it could run some sort of headless X just for testing purposes we probably would have to make sure that each package building in parallel that needed this feature (however unlikely) ran on a different display. What's the limit on the number of displays anyway? The main reason I include it under the Packaging Guidelines umbrella is that I use it to run rpmlint on installed packages, especially libraries, where you can find additional problems that rpmlint can't detect from checking the RPMs. I'm not saying we should make it a requirement, but perhaps strongly recommended would be a good idea. /me notices that although that instruction is in the ReviewGuidelines we dont seem to have it on the main Guidelines page. I assume you're talking about? http://fedoraproject.org/wiki/Packaging/Guidelines#rpmlint Thanks, Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[389-devel] please review ticket #216 - RFE - disable replication agreements
https://fedorahosted.org/389/ticket/216 https://fedorahosted.org/389/attachment/ticket/216/0001-Ticket-216-RFE-Disable-replication-agreements.patch Thanks, Mark -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: Testing packages with mock and Xnest?
On Wed, 2012-04-25 at 14:39 -0500, Richard Shaw wrote: Hmm... I think that would be quite a bit more complicated. I don't think Xnest would be the right tool for that. I really don't know enough about X to guess. I would think that the build server probably runs without X and even if it could run some sort of headless X just for testing purposes we probably would have to make sure that each package building in parallel that needed this feature (however unlikely) ran on a different display. What's the limit on the number of displays anyway? Something on the order of 65536 - 6000. There's a -displayfd feature in our X (and soon in upstream's) to do the much more sensible thing of simply _picking_ an unused display number and handing it back to the launching process, rather than the launcher needing to guess one that's unused. But in any event Xnest would not be suitable for this environment, because Xnest needs another server to display on. Xvfb would work for fully-automated things though. - ajax signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Minutes from weekly Fedora ARM status meeting (2012/04/25)
On 04/24/2012 12:27 PM, Jon Masters wrote: Let's have one of our weekly status calls tomorrow pm. I aim to send these reminders out more regularly so that we can get in the habit. If the times no longer work for those involved in the Fedora ARM project, please do let us know asap. Sadly, not every time will always work :) Meeting is on #fedora-meeting for a (trial) change. Link to the meeting minutes: http://meetbot.fedoraproject.org/fedora-meeting/2012-04-25/fedora-meeting.2012-04-25-19.59.html Jon. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [fedora-arm] Weekly ARM status call - TOMORROW (Wed 2012/04/25)
On 04/24/2012 01:33 PM, Jerry James wrote: On Tue, Apr 24, 2012 at 10:29 AM, Jon Masters j...@redhat.com wrote: Times in various timezones: PDT: 2pm CDT: 3pm EDT: 4pm UTC: 8pm BST: 9pm CST: 10pm Shouldn't that be PDT: 1pm MDT: 2pm Yes, as I said on IRC I was going to make a joke about MDT depending how far South you are, but nobody would get it :) Anyway, I was wrong about the offsets and I'll fix it next time. Jon. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Proposal for revitalizing the sponsorship process for packaging
For a while now I have been working on a proposal for some changes to both the way we elevate packagers to sponsors and what (to a small extent) sponsors actually do. Please note that this is not a proposal for any changes to how people are made members of the packager group in the first place and does not change the privileges of existing sponsors. My proposal is at https://fedoraproject.org/wiki/User:Tibbs/RevitalizingSponsorshipProposal I've run this by FESCo, whose response was favorable, so I'm sending this to a larger audience. Please let me know what you think. - J -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposal for revitalizing the sponsorship process for packaging
On Wed, Apr 25, 2012 at 4:03 PM, Jason L Tibbitts III ti...@math.uh.edu wrote: For a while now I have been working on a proposal for some changes to both the way we elevate packagers to sponsors and what (to a small extent) sponsors actually do. Please note that this is not a proposal for any changes to how people are made members of the packager group in the first place and does not change the privileges of existing sponsors. My proposal is at https://fedoraproject.org/wiki/User:Tibbs/RevitalizingSponsorshipProposal I've run this by FESCo, whose response was favorable, so I'm sending this to a larger audience. Please let me know what you think. Looks good to me. I was unaware that sponsors are (currently) also provenpackagers. I've considered the idea of becoming a sponsor myself, but when I read the archived tickets where other people smarter than me have been denied, the barrier to entry seemed too high. Previously I've just used the co-maintain to proxy sponsor route, which isn't super optimal. Could you expand a bit on what you consider high-quality, non-trivial package reviews ? - Ken -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposal for revitalizing the sponsorship process for packaging
KD == Ken Dreyer ktdre...@ktdreyer.com writes: KD Looks good to me. I was unaware that sponsors are (currently) also KD provenpackagers. I've considered the idea of becoming a sponsor KD myself, but when I read the archived tickets where other people KD smarter than me have been denied, the barrier to entry seemed too KD high. Yes, that's the problem I'm trying to address. KD Could you expand a bit on what you consider high-quality, KD non-trivial package reviews ? As explained in the proposal, that's intentionally left vague. The idea is to have the sponsors discuss whether the reviews meet the criteria. If the authority for elevating packagers to sponsors were delegated to the sponsors, we could even work out refinements to this ourselves. Currently it's in the hands of FESCo and to my knowledge there are no published criteria available. I know I have my own opinions, which might not be the same as those of everyone else. For the record, my opinion would be something close to package reviews which are comprehensive, don't miss important packaging problems and aren't entirely of identical autogenerated Perl modules or the like. - J -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposal for revitalizing the sponsorship process for packaging
On 04/25/2012 10:03 PM, Jason L Tibbitts III wrote: For a while now I have been working on a proposal for some changes to both the way we elevate packagers to sponsors and what (to a small extent) sponsors actually do. Please note that this is not a proposal for any changes to how people are made members of the packager group in the first place and does not change the privileges of existing sponsors. My proposal is at https://fedoraproject.org/wiki/User:Tibbs/RevitalizingSponsorshipProposal I've run this by FESCo, whose response was favorable, so I'm sending this to a larger audience. Please let me know what you think. Why not just drop the sponsorship process and just raise the barrier of entry for the packaging process instead? Like having to have been a comaintainer for atleast one release cycle then completed x many reviews in the next etc. ( essentally what you propose there just without the sponsor ) and finally you are maintaining your own package or if we drop that outdated ownership model we have in place are free to roam free in the packaging community and assist when ever, where ever possible... JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: firewalld / iptables.service past F17
On 25/04/12 10:55 AM, Adam Williamson wrote: On Tue, 2012-04-24 at 09:30 -0500, Jon Ciesla wrote: Nothing is being taken away, the default is being changed. If you're using Fedora in production, I presume you're installing with Kickstart. It's worth noting that if the question is how does firewalld handle upgrades, I think it may be somewhat irrelevant because AFAIK even when firewalld was going to be the F17 default, we never implemented anything to cause upgraded systems to switch to it. It was only new installs which were getting firewalld. Upgraded ones stuck with the static iptables/s-c-f/lokkit system. Does that imply that new installs will be easily switched from firewalld to static iptables? I always do new install but I want to keep my firewall static, with my current iptables script. Dariusz -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposal for revitalizing the sponsorship process for packaging
On Wed, 2012-04-25 at 22:43 +, Jóhann B. Guðmundsson wrote: Why not just drop the sponsorship process and just raise the barrier of entry for the packaging process instead? Like having to have been a comaintainer for atleast one release cycle then completed x many reviews in the next etc. ( essentally what you propose there just without the sponsor ) and finally you are maintaining your own package or if we drop that outdated ownership model we have in place are free to roam free in the packaging community and assist when ever, where ever possible... This approach completely disregards the very common example of I'm an upstream maintainer of a cool project. I want to package and maintain it for Fedora. Under your approach, they'd first have to become involved in other projects before being allowed to add their package. This is unacceptable and would basically guarantee that no upstream would willingly involve itself with Fedora. signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-Net-SSLeay] Created tag perl-Net-SSLeay-1.48-1.fc17
The lightweight tag 'perl-Net-SSLeay-1.48-1.fc17' was created pointing to: 3271923... Update to 1.48 -- 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-Net-SSLeay] Created tag perl-Net-SSLeay-1.48-1.fc18
The lightweight tag 'perl-Net-SSLeay-1.48-1.fc18' was created pointing to: 3271923... Update to 1.48 -- 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-Google-Contacts/f16] Adding an example script due to poor API documentation.
commit 9287023a4ea6175baf2db6e4d0b95190df2cfe0b
Author: Avi Alkalay avibra...@gmail.com
Date: Wed Apr 25 08:51:18 2012 -0300
Adding an example script due to poor API documentation.
.gitignore |2 +
example.pl | 71
sources|2 +-
3 files changed, 74 insertions(+), 1 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 68545cc..3d815b3 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,3 @@
/WWW-Google-Contacts-0.33.tar.gz
+/WWW-Google-Contacts-0.34.tar.gz
+/example.pl
diff --git a/example.pl b/example.pl
new file mode 100755
index 000..482342a
--- /dev/null
+++ b/example.pl
@@ -0,0 +1,71 @@
+#!/usr/bin/perl
+
+
+#
+#
+# This is a useful example script that will:
+#
+# - iterate through all contacts
+# - select a few based on a group name
+# - check if it has phone numbers
+# - edit those phone numbers
+# - commit changes back to Google Contacts
+#
+# This script by Avi Alkalay avi at unix dot sh
+#
+# $Id: gcontacts.pl 526 2012-04-24 11:49:33Z aviram $
+#
+#
+
+use WWW::Google::Contacts;
+
+my $google = WWW::Google::Contacts-new( username = YOUR_GOOGLE_USERNAME,
password = YOUR_GOOGLE_PASSWORD );
+
+
+my $contactIterator = $google-contacts;
+my $contact;
+
+while ($contact = $contactIterator-next) {
+ my $modified=0;
+
+ # Filter contacts by group name
+ if (contactHasGroup($contact,'System Group: My Contacts')) {
+ # Check if has phone number
+ if ($contact-{phone_number}) {
+ # Iterate through phone numbers
+ foreach (@{$contact-{phone_number}}) {
+ my $p=$_;
+
+ # Check if phone number matches the pattern we
are looking for
+ if ($p-{value}=~m/^\(0(\d\d)\)/) {
+ my $old=$p-{value};
+
+ # Do some modifications of phone prefix
and mark contact modified
+ $p-{value}=~s/^\(0(\d\d)\)/+55
\($1\)/g;
+ $modified=1;
+
+ # Print on screen what we are doing
+ print $contact-full_name . ::
$p-{label} :: $old = $p-{value}\n;
+ }
+ }
+ }
+ }
+
+ # If contact was modified above, commit changes back to Google Contacts
+ if ($modified eq 1) {
+ $contact-update;
+ }
+}
+
+
+
+sub contactHasGroup() {
+ my $c=shift;
+ my $g=shift;
+
+ foreach ($c-groups) {
+ return 1 if ($_-{title} eq $g);
+ }
+
+ return 0;
+}
diff --git a/sources b/sources
index aae3bc9..67b9048 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-3e33a1d0dc9f50fdd45652783b461383 WWW-Google-Contacts-0.33.tar.gz
+1dba94186ce5a558f80f735958e4996e example.pl
--
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-Google-Contacts/f16] New upstream version, added example script and made the build more reliable
commit 29f60420bca979e0d2693e059bcfbe471ed00831
Author: Avi Alkalay avibra...@gmail.com
Date: Wed Apr 25 09:05:25 2012 -0300
New upstream version, added example script and made the build more reliable
perl-WWW-Google-Contacts.spec | 24 +---
1 files changed, 21 insertions(+), 3 deletions(-)
---
diff --git a/example.pl b/example.pl
old mode 100755
new mode 100644
diff --git a/perl-WWW-Google-Contacts.spec b/perl-WWW-Google-Contacts.spec
index f522044..fc47a09 100644
--- a/perl-WWW-Google-Contacts.spec
+++ b/perl-WWW-Google-Contacts.spec
@@ -1,11 +1,12 @@
Name: perl-WWW-Google-Contacts
-Version:0.33
-Release:3%{?dist}
+Version:0.34
+Release:1%{?dist}
Summary:Use Perl to access, list and edit Google Contacts
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/WWW-Google-Contacts/
Source0:
http://www.cpan.org/authors/id/M/ME/MERIXZON/WWW-Google-Contacts-%{version}.tar.gz
+Source1: example.pl
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
BuildRequires: perl(Class::MOP) = 1.09
@@ -47,10 +48,20 @@
http://code.google.com/apis/contacts/docs/3.0/developers_guide_protocol.html
%setup -q -n WWW-Google-Contacts-%{version}
%build
+unset PERL5LIB
+unset PERL_LOCAL_LIB_ROOT
+unset PERL_MB_OPT
+unset PERL_MM_OPT
+
%{__perl} Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
+unset PERL5LIB
+unset PERL_LOCAL_LIB_ROOT
+unset PERL_MB_OPT
+unset PERL_MM_OPT
+
rm -rf $RPM_BUILD_ROOT
make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
@@ -58,6 +69,8 @@ make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \;
find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2/dev/null \;
+cp %{SOURCE1} .
+
%{_fixperms} $RPM_BUILD_ROOT/*
%check
@@ -68,11 +81,16 @@ rm -rf $RPM_BUILD_ROOT
%files
%defattr(-,root,root,-)
-%doc Changes dist.ini LICENSE README
+%doc Changes dist.ini LICENSE README example.pl
%{perl_vendorlib}/*
%{_mandir}/man3/*
%changelog
+* Tue Apr 24 2012 Avi Alkalay avibra...@gmail.com 0.34-1
+- Upstream update
+- Unset various PERL* shell variables comonly used by people that use CPAN to
compile and install Perl modules on their home directory
+- API documentation is quite poor so I'm adding an example script
+
* Wed Mar 21 2012 Avi Alkalay a...@unix.sh 0.33-3
- Removed duplicate Requires
- Refined for Fedora and EPEL sponsorship
--
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-Google-Contacts/f16] Updated upstream, included an example usage script, made build more reliable
commit 3711a850571da9c2bd40e508031be6995475225d Author: Avi Alkalay avibra...@gmail.com Date: Wed Apr 25 09:16:52 2012 -0300 Updated upstream, included an example usage script, made build more reliable sources |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/sources b/sources index 67b9048..f5209ab 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -1dba94186ce5a558f80f735958e4996e example.pl +157db4b73f957b6cdb54c6754f37c085 WWW-Google-Contacts-0.34.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-Google-Contacts/f16] Updated upstream, included an example usage script, made build more reliable
commit 36b03e133eed68116d900359b3bce7a6434b139e
Author: Avi Alkalay avibra...@gmail.com
Date: Wed Apr 25 09:26:29 2012 -0300
Updated upstream, included an example usage script, made build more reliable
perl-WWW-Google-Contacts.spec |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/perl-WWW-Google-Contacts.spec b/perl-WWW-Google-Contacts.spec
index fc47a09..c7a879e 100644
--- a/perl-WWW-Google-Contacts.spec
+++ b/perl-WWW-Google-Contacts.spec
@@ -1,6 +1,6 @@
Name: perl-WWW-Google-Contacts
Version:0.34
-Release:1%{?dist}
+Release:2%{?dist}
Summary:Use Perl to access, list and edit Google Contacts
License:GPL+ or Artistic
Group: Development/Libraries
@@ -86,7 +86,7 @@ rm -rf $RPM_BUILD_ROOT
%{_mandir}/man3/*
%changelog
-* Tue Apr 24 2012 Avi Alkalay avibra...@gmail.com 0.34-1
+* Tue Apr 24 2012 Avi Alkalay avibra...@gmail.com 0.34-2
- Upstream update
- Unset various PERL* shell variables comonly used by people that use CPAN to
compile and install Perl modules on their home directory
- API documentation is quite poor so I'm adding an example script
--
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
exiv2-0.23 coming soon
I plan on importing exiv2-0.23 into rawhide soon'ish. It includes an ABI bump, so dependent packages will require rebuilding, including: calligra darktable entangle geeqie gipfel gnome-color-manager gnome-commander gpscorrelate gthumb gwenview hugin immix kde-runtime krename libextractor libgexiv2 libkexiv2 luminance-hdr merkaartor oyranos pyexiv2 rawstudio strigi ufraw I'll take care of kicking off a round of rebuilds for these. -- rex ___ devel-announce mailing list devel-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce
