Re: What are the rules for which package we build against in F-13?
On 03/08/2010 04:37 PM, Josh Boyer wrote: The buildroots are populated from packages in the: dist-f13 dist-f13-override dist-f12-updates tags. If a package isn't in one of those tags, it's not going to be in the buildroot. If you need to build against a newer version of a package, then you need to file a ticket on the rel-eng trac instance asking for a buildroot override (which will get it tagged into dist-f13-override). Sorry to revive this old thread, but does this imply that one cannot use 'make chain-build' for F-13 updates then ? I have a 5 level-deep sets of updates I need to test for the new stable gtkmm stack. I can't say I'm thrilled at the idea of filing a dozen of rel-eng tickets and waiting for a week to do this, rather than use a single command... -denis -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: What are the rules for which package we build against in F-13?
Denis Leroy wrote, at 04/07/2010 03:20 PM +9:00: On 03/08/2010 04:37 PM, Josh Boyer wrote: The buildroots are populated from packages in the: dist-f13 dist-f13-override dist-f12-updates tags. If a package isn't in one of those tags, it's not going to be in the buildroot. If you need to build against a newer version of a package, then you need to file a ticket on the rel-eng trac instance asking for a buildroot override (which will get it tagged into dist-f13-override). Sorry to revive this old thread, but does this imply that one cannot use 'make chain-build' for F-13 updates then ? Yes. Mamoru -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Using capabilities for libpcap apps
Radek Vokál píše v Út 06. 04. 2010 v 22:47 +0200: Hi all, I need few suggestions about this .. https://blog.wireshark.org/2010/02/running-wireshark-as-you/ .. Gerald Combs, the upstream maintainer of wireshark, suggests to use capabilities instead of consolehelper+root privileges for dumpcap/wireshark. It makes whole lot of sense, so I've looked if other apps in Fedora are already using it and I haven't found any. Honestly I'm not sure about right way to use them. The idea is to add something like following to %post # groupadd -g wireshark # chgrp wireshark /usr/bin/dumpcap for creating the group you should use the standard scriptlet from https://fedoraproject.org/wiki/Packaging/UsersAndGroups and set the group via %attr in %files # setcap cap_net_raw,cap_net_admin+eip /usr/bin/dumpcap # setcap cap_net_raw,cap_net_admin+eip /usr/bin/tshark I would add this commands to %post too Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Using capabilities for libpcap apps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I was speaking about this with Rahul Sundaram and he pointed me to: http://fedoraproject.org/wiki/Features/LowerProcessCapabilities I would suggest using libpcap-ng rather than libpcap if it works. Radek Vokál wrote: Hi all, I need few suggestions about this .. https://blog.wireshark.org/2010/02/running-wireshark-as-you/ .. Gerald Combs, the upstream maintainer of wireshark, suggests to use capabilities instead of consolehelper+root privileges for dumpcap/wireshark. It makes whole lot of sense, so I've looked if other apps in Fedora are already using it and I haven't found any. Honestly I'm not sure about right way to use them. The idea is to add something like following to %post # groupadd -g wireshark # chgrp wireshark /usr/bin/dumpcap # setcap cap_net_raw,cap_net_admin+eip /usr/bin/dumpcap # setcap cap_net_raw,cap_net_admin+eip /usr/bin/tshark Suggestions? Ideas? Spec file patches? Any help is welcome. Radek - -- Regards, Huzaifa Sidhpurwala, RHCE, CCNA (IRC: huzaifas) GnuPG Fingerprint: 3A0F DAFB 9279 02ED 273B FFE9 CC70 DCF2 DA5B DAE5 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org/ iD8DBQFLvCbzzHDc8tpb2uURAhmUAJ9m3DzIXyuF5Q87RsRTwWN94KZiYQCfQuAn gPmMlJxwAKWCGyQJoCBbpSw= =Wkq8 -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Using capabilities for libpcap apps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Huzaifa Sidhpurwala wrote: Ah Sorry, scratch the last line please, an oversight :) I would suggest using libpcap-ng rather than libpcap if it works. - -- Regards, Huzaifa Sidhpurwala, RHCE, CCNA (IRC: huzaifas) GnuPG Fingerprint: 3A0F DAFB 9279 02ED 273B FFE9 CC70 DCF2 DA5B DAE5 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org/ iD8DBQFLvCeAzHDc8tpb2uURAlpdAJ9+BCrK1bdIlxhVvClowrxcpgnM6ACeJ+m9 z3Nec3oCE70JFCf5EqnpbF0= =ZK2e -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: What are the rules for which package we build against in F-13?
On 04/07/2010 08:30 AM, Mamoru Tasaka wrote: Denis Leroy wrote, at 04/07/2010 03:20 PM +9:00: On 03/08/2010 04:37 PM, Josh Boyer wrote: The buildroots are populated from packages in the: dist-f13 dist-f13-override dist-f12-updates tags. If a package isn't in one of those tags, it's not going to be in the buildroot. If you need to build against a newer version of a package, then you need to file a ticket on the rel-eng trac instance asking for a buildroot override (which will get it tagged into dist-f13-override). Sorry to revive this old thread, but does this imply that one cannot use 'make chain-build' for F-13 updates then ? Yes. Thanks Mamoru-san, Well, this is not the most motivating news. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Hibernation causing many crashes; get a rid of it
Hi! I do agree with Stefan as hibernation is really useful feature: I set the laptop to hibernate on low battery power, so I can continue my work after charge. Never got any problems with it (except of long time to bring the PC up). Best regards. On 6 April 2010 19:07, stefan riemens fgfs.ste...@gmail.com wrote: Just to let you know: I hardly ever do a real shutdown, always suspending and hibernating... Works like a charm here (even running virtual machines in VirtualBox survive a suspend-resume of the host... Go figure!) So I wouldn't call it useless, although restore from hibernate takes quite some time with the ever-increasing amount of memory modern machines ship with... Stefan 2010/4/6, Rahul Sundaram methe...@gmail.com: On 04/06/2010 09:39 PM, Roman Rakus wrote: Hi all, since we have abrt, I'm getting many bug reports for bash. Nearly all of them are caused by hibernation. User hibernates the computer and than - crash here and there. What about to get a rid of hibernation since it is useless? If you got bugs in your software, fix it. What's wrong with hibernation? Rahul -- 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 -- Best regards. Marian Holovatskyy newme...@gmail.com +380937235051 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: What are the rules for which package we build against in F-13?
On Wed, 07 Apr 2010 08:37:25 +0200, Denis wrote: On 04/07/2010 08:30 AM, Mamoru Tasaka wrote: Denis Leroy wrote, at 04/07/2010 03:20 PM +9:00: On 03/08/2010 04:37 PM, Josh Boyer wrote: The buildroots are populated from packages in the: dist-f13 dist-f13-override dist-f12-updates tags. If a package isn't in one of those tags, it's not going to be in the buildroot. If you need to build against a newer version of a package, then you need to file a ticket on the rel-eng trac instance asking for a buildroot override (which will get it tagged into dist-f13-override). Sorry to revive this old thread, but does this imply that one cannot use 'make chain-build' for F-13 updates then ? Yes. Thanks Mamoru-san, Well, this is not the most motivating news. How easy is it for releng to create a custom buildroot/tag, which could be used instead of working with an override tag? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Hibernation causing many crashes; get a rid of it
On 04/06/2010 06:17 PM, Rahul Sundaram wrote: If you got bugs in your software, fix it. What's wrong with hibernation? That's what I don't know. I know nearly nothing about hibernation. I have mark bugs as duplicates and reassigned it to kernel guys. See https://bugzilla.redhat.com/show_bug.cgi?id=551570. RR -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: urgent testing call: F13 kernel-2.6.33.1-24.fc13
On 06/04/10 23:22, Adam Williamson wrote: Works fine on Dell Vostro 200 as factory minus included soft. Kernel.x86_64 System i686 Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit CPU(s):1 Thread(s) per core:1 Core(s) per socket:1 CPU socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family:6 Model: 22 Stepping: 1 CPU MHz: 1600.000 L1d cache: 32K L1i cache: 32K L2 cache: 512K 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02) -- Regards, Frank Murphy UTF_8 Encoded, Fedora.x86 64-32 Hybrid -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: urgent testing call: F13 kernel-2.6.33.1-24.fc13
Hi, kernel-2.6.33.1-24.fc13 works for me (amd64 system with nvidia chipset). Regards, Hans On 04/06/2010 11:53 PM, Adam Williamson wrote: Hi, everyone. We're looking at pulling kernel-2.6.33.1-24.fc13 into Fedora 13 Beta, quite late, because current Beta candidate builds include kernel-2.6.33.1-19.fc13 which is known to include a severe bug that breaks boot on systems with Broadcom wired ethernet adapters supported by the b44 module. However, -24 has other changes from -19, including to the nouveau (NVIDIA graphics) and iwlwifi (Intel wifi) drivers. We really need as many people as possible to test kernel -24, which you can get at http://koji.fedoraproject.org/koji/buildinfo?buildID=164598 , and confirm that it works okay on your systems. To install it, use 'rpm -ivh' for the kernel and -devel packages. If you have kernel-headers installed, 'rpm -Uvh' that first. Then reboot to the kernel and check that it boots up okay. Please reply to this thread with your results. Thanks! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RPM packaging workshop example
On 03/29/2010 03:55 AM, Michal Schmidt wrote: On Mon, 29 Mar 2010 03:43:23 +0530 Rahul Sundaram wrote: For the purpose of doing a RPM packaging workshop, I need a simple clear hello world type example using autotools. Can anyone point me to something suitable for the purpose? You mean GNU hello? :-) http://www.gnu.org/software/hello/ A tutorial is available at https://fedoraproject.org/wiki/A_Short_RPM_Tutorial Thanks to Przemek Klosowski for writing it. Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RPM packaging workshop example
On 04/07/2010 01:50 PM, Rahul Sundaram wrote:
On 03/29/2010 03:55 AM, Michal Schmidt wrote:
On Mon, 29 Mar 2010 03:43:23 +0530 Rahul Sundaram wrote:
For the purpose of doing a RPM packaging workshop, I need a simple
clear hello world type example using autotools. Can anyone point me to
something suitable for the purpose?
You mean GNU hello? :-)
http://www.gnu.org/software/hello/
A tutorial is available at
https://fedoraproject.org/wiki/A_Short_RPM_Tutorial
Thanks to Przemek Klosowski for writing it.
There is a small bug in the example:
Instead of
%find_lang %{name}
rm -f $RPM_BUILD_ROOT/usr/share/info/dir
this should be
%find_lang %{name}
rm -f $RPM_BUILD_ROOT%{_infodir}/dir
Background: The example uses %configure
i.e. it passes --infodir=%{_infodir} to configure,
i.e. it's %{_infodir} where dir is being installed,
not /usr/share/info
Ralf
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RPM packaging workshop example
On Wed, Apr 7, 2010 at 2:07 PM, Ralf Corsepius rc040...@freenet.de wrote: There is a small bug in the example: Corrected. Thanks -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Talking about live upgrade
Hi, all Several days ago, I wrote an article about upgrading. Many users meets the same problem. Also Casey Dahlin gives me a lot of advices. Maybe devel list is fit for a border discuss about upgrade experience. Will Live upgrade replace preupgrade? Now we can not get access to my blog because of censorship in China. I will solve it in several days. Please wait for moments. I paste my article at Fpaste: http://fpaste.org/tTLC/ Thank you -- Fedora Debian User, former Ubuntu User My Page: http://www.liangsuilong.info Fedora Project Contributor -- Packager Ambassador https://fedoraproject.org/wiki/User:Liangsuilong -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RPM packaging workshop example
On 04/07/2010 05:37 PM, Ralf Corsepius wrote:
There is a small bug in the example:
Instead of
%find_lang %{name}
rm -f $RPM_BUILD_ROOT/usr/share/info/dir
this should be
%find_lang %{name}
rm -f $RPM_BUILD_ROOT%{_infodir}/dir
Someone else fixed it now. Thanks.
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Two new applications to package and add to Fedora
Hi List I'm new to this list, a brief intro - I currently work for the University of Southampton (ECS) as a systems administrator / programmer and also run my small development company, Interlinux Ltd. See LinkedIn http://www.linkedin.com/in/dbrasher 'to the chase: I have coded two projects (beta1 and beta2) that I would like to package and add to Fedora (extras?). I hope this archive this over several weeks and I (my company) will be the long-term maintainer. 1) DIASER (2005-2010) - Long-term geo-redundancy archiving software [for the cloud] written in Perl. https://sourceforge.net/projects/dspaceinvadors/ 2) DSI (2001-2010) - Pristine (code) Space Invaders clone written in C and recently revived for fun and to support DIASER. https://sourceforge.net/projects/dspaceinvadors/ Where do I start? TIA - Damian -- Damian L Brasher BSc(Open) RHCE MBCS e: dbras...@interlinux.co.uk w: http://www.diaser.org.uk - Open Source Data Vault Application - beta-1 w: http://www.walkingwiththeelephants.co.uk ebook about small scale OSS collaborative development -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Two new applications to package and add to Fedora
Hi List I'm new to this list, a brief intro - I currently work for the University of Southampton (ECS) as a systems administrator / programmer and also run my small development company, Interlinux Ltd. See LinkedIn http://www.linkedin.com/in/dbrasher 'to the chase: I have coded two projects (beta1 and beta2) that I would like to package and add to Fedora (extras?). I hope this archive this over several weeks and I (my company) will be the long-term maintainer. 1) DIASER (2005-2010) - Long-term geo-redundancy archiving software [for the cloud] written in Perl. https://sourceforge.net/projects/diaser/ 2) DSI (2001-2010) - Pristine (code) Space Invaders clone written in C and recently revived for fun and to support DIASER. https://sourceforge.net/projects/dspaceinvadors/ Where do I start? TIA - Damian -- Damian L Brasher BSc(Open) RHCE MBCS e: dbras...@interlinux.co.uk w: http://www.diaser.org.uk - Open Source Data Vault Application - beta-1 w: http://www.walkingwiththeelephants.co.uk ebook about small scale OSS collaborative development -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Two new applications to package and add to Fedora
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/07/2010 08:32 AM, Damian Brasher wrote: Hi List I'm new to this list, a brief intro - I currently work for the University of Southampton (ECS) as a systems administrator / programmer and also run my small development company, Interlinux Ltd. See LinkedIn http://www.linkedin.com/in/dbrasher 'to the chase: I have coded two projects (beta1 and beta2) that I would like to package and add to Fedora (extras?). I hope this archive this over several weeks and I (my company) will be the long-term maintainer. 1) DIASER (2005-2010) - Long-term geo-redundancy archiving software [for the cloud] written in Perl. https://sourceforge.net/projects/dspaceinvadors/ 2) DSI (2001-2010) - Pristine (code) Space Invaders clone written in C and recently revived for fun and to support DIASER. https://sourceforge.net/projects/dspaceinvadors/ Where do I start? TIA - Damian Follow the package review process for Fedora described here: http://fedoraproject.org/wiki/Package_Review_Process Welcome to Fedora! - -- Stephen Gallagher RHCE 804006346421761 Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAku8fPkACgkQeiVVYja6o6O4RQCgkOA6DWbUFEEtF5Zrelk3UBg8 GgEAn1fRfNrX0JUYuh+fCFN6CM4QQ04P =Ici6 -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Two new applications to package and add to Fedora
On 04/07/2010 06:02 PM, Damian Brasher wrote: I have coded two projects (beta1 and beta2) that I would like to package and add to Fedora (extras?). There is no extras repository since Fedora 7 release. I hope this archive this over several weeks and I (my company) will be the long-term maintainer. 1) DIASER (2005-2010) - Long-term geo-redundancy archiving software [for the cloud] written in Perl. https://sourceforge.net/projects/dspaceinvadors/ 2) DSI (2001-2010) - Pristine (code) Space Invaders clone written in C and recently revived for fun and to support DIASER. https://sourceforge.net/projects/dspaceinvadors/ Where do I start? Here: http://fedoraproject.org/wiki/Join_the_package_collection_maintainers If you have questions, feel free to ask. Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RPM packaging workshop example
On Wed, Apr 7, 2010 at 2:18 PM, Rahul Sundaram methe...@gmail.com wrote:
On 04/07/2010 05:37 PM, Ralf Corsepius wrote:
There is a small bug in the example:
Instead of
%find_lang %{name}
rm -f $RPM_BUILD_ROOT/usr/share/info/dir
this should be
%find_lang %{name}
rm -f $RPM_BUILD_ROOT%{_infodir}/dir
Someone else fixed it now. Thanks.
Yes, I was. Probably the replay was lost.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Macbook Pro 13.3 (5,5) Fedora 12 notes
Folks, In case this helps anyone else setting up a Macbook Pro 13.3 model 5,5. 1). Installation proceeds normally. You may want to install rEFIt to allow dual booting with Mac OS X, in which case Anaconda should oblige by placing grub on the partition of your /boot partition. You then only need to run gptsync by choosing the Partitioning Tool next boot. I took my new Macbook apart and upgraded the disk to a 500GB model from the tiny one it came with. They wanted a small fortune for a non 7200K drive upgrade, so I laughed. My partitions are as follows: 1: EFI (hidden in OSX) 2: OSX (100GB) 3: Linux Boot (1GB) 4: Linux LVM (swap,root,100GB) 5: Shared (hfsplus,100GB) 6: Data (2ext4,200GB) The first three partitions are mapped to the MBR style GRUB is looking for following a gptsync within the EFI booter tool. 2). The new install has no networking because the 432b reversion part is unsupported by the b43 Open Source driver (they are working on it). You will need to download the wl driver from Broadcom. It won't load out of the box because it can't see the device. For the moment, the following hack in /usr/local/bin/wl_hack.sh (called from /etc/rc.local) suffices to load (this is weird, seems the second load/unload results in some ACPI power state change and the device will then show up randomly): #!/bin/sh # for some reason we don't see the bcm part unless we unload/reload b43/wl. modprobe b43 modprobe -r b43 modprobe wl modprobe -r wl modprobe b43 modprobe -r b43 modprobe wl It may still drop off the network from time to time. An upstream driver will be really helpful when that is available. I will need a backport of a future stable wireless tree to 2.6.32 since I am not planning to upgrade my X drivers for the incompatible ABI in future nouveau. 3). Sound won't work out of the box, but it will (including the headphone detection) if you do the following: rpm -e alsa-plugins-pulseaudio Then alsamixer will show all of the channel options, which you should set to 100% volume for now. The GNOME volume controls will now work. Add alsa-plugins-pulseaudio to and exclude line /etc/yum.conf to prevent it ever getting installed again. Also add kernel to that line while you're at it if you'll be fixing the mouse in the next step. I like to build my own kernels for Fedora so I generally forbid it installing. 4). Out of the box, the mouse experience is horrible. You may want to create an xorg.conf file (using Xorg -configure), but there is a better way to configure the mouse on recent systems. Place the following in /etc/hal/fdi/policy/20thirdparty/10-synaptics.fdi: ?xml version=1.0 encoding=ISO-8859-1? deviceinfo version=0.2 device match key=info.capabilities contains=input.touchpad !-- To add custom options for the touchpad, modify the examples below to suit your needs. The available options are listed in the synaptics man page. After modifyfing this file, you must restart HAL. Check the output of lshal whether your modifications have been merged successfully. Note: Options must always be type string. The following examples enable left, right, middle clicks on single, double, triple finger tapping, respectively. merge key=input.x11_options.TapButton1 type=string1/merge merge key=input.x11_options.TapButton2 type=string3/merge merge key=input.x11_options.TapButton3 type=string2/merge -- merge key=input.x11_driver type=stringsynaptics/merge merge key=input.x11_options.SHMConfig type=stringOn/merge merge key=input.x11_options.TapButton2 type=string0/merge merge key=input.x11_options.TapButton3 type=string0/merge !-- Not needed with the hacked up 2-finger-click-to-drag-driver merge key=input.x11_options.ClickFinger2 type=string0/merge merge key=input.x11_options.ClickFinger3 type=string0/merge -- /match /device /deviceinfo That will turn off the most annoying TapButton options and tell X to start the synaptics touchpad driver with the ability to dynamically tune the driver using a shared memory mechanism. This enables synclient. You need a fixed bcm5974 mouse driver (with the attached patch - cleaned up version to follow) that correctly supports two finger click-and-drag. I have modified an existing patch for 2.6.32 kernels and will post a kmod in due course. With that patch enabled you won't need to turn off the ClickButton support and can both drag and right/middle click. 5). The gnome-power-manager gets a little confused sometimes. Make sure it is always showing at least (sometimes it doesn't notice the battery even though that is showing in lshal, etc.): gconftool-2 -s -t string /apps/gnome-power-manager/ui/icon_policy always You will also need to chvt or similar to/from another VT on resume in order for the display to wake up. The HAL scripts specifically disable
Re: non-responsive maintainer: thomasvs
On Tue, Apr 06, 2010 at 08:53:10PM +0200, Julian Sikorski wrote: W dniu 06.04.2010 15:56, Thomas Vander Stichele pisze: On Sat, 2010-04-03 at 20:10 +0200, Julian Sikorski wrote: Dear all, it seems like thomasvs became unresponsive. I have filed a bug asking about python-twisted update [1] on 6th of February. It was then duped by a similar bug [2] on 23rd of March. I have also emailed Thomas on 26th of March. None of the queries met any response. Should I initiate the non-responsive maintainer process? Hi Julian, I'm still around, but a direct mail to me is the easiest way to get my attention (as I suspect is the case for most developers). I saw you did two weeks ago asking about an update, but that's a different beast then marking me as unresponsive :) I think in general it would be good that when people want to initiate the non-responsive maintainer process, they first of all mail the person involved saying so. For practical reasons contacting me over IRC doesn't always work since I'm on three different machines regularly, and I only check bugzilla stuff once a month relying on getting a mail or poke if something is critical. As for the issue at hand, Twisted is a complex beast to upgrade and validate, so I sure could use help there! I see in the bug report you made a list of current dependendants, we could divide them up and verify them ? Thomas Sorry if I acted to quickly, but the lack of response to my email made me afraid that you might be gone. Anyway, when it comes to the update, I'm happy to help. The total number of downstream packages dependent on twisted is 33. Should we expect breakage? Were there any API changes in twisted? I think we could start by dividing the list of the packages fifty-fifty, and check if they work at all. Then, I think it would be a good idea to bring maintainers into the loop since they actually know what the packages are supposed to do. The cleaned-up list follows below: buildbot-0:0.7.12-1.fc12.noarch cnucnu-0:0-0.3.20100110.fc12.noarch desktopcouch-0:0.6.3-3.fc12.noarch elisa-base-0:0.5.35-2.fc12.noarch elisa-plugins-bad-0:0.5.35-2.fc12.noarch elisa-plugins-ugly-0:0.5.35-1.fc11.noarch entertainer-0:0.4.2-7.fc12.noarch flumotion-0:0.6.1-1.fc12.x86_64 gadget-0:0.0.3-4.fc12.noarch itaka-0:0.2.2-1.fc12.noarch jabbim-0:0.5-0.12.svn20091030.fc12.noarch londonlaw-0:0.2.1-7.fc12.noarch nwsserver-0:2.0.0-1.fc12.noarch openxcap-0:1.1.2-1.fc12.noarch orbited-0:0.7.10-3.fc12.noarch poker-network-0:1.7.3-3.fc12.noarch postr-0:0.12.3-8.fc12.x86_64 pyicq-t-0:0.8.1.5-5.fc12.noarch pyjigdo-0:0.4.0.1-2.fc12.noarch python-Coherence-0:0.6.4-1.fc12.noarch python-desktopcouch-0:0.6.3-3.fc12.noarch python-foolscap-0:0.4.2-3.fc12.noarch python-gnutls-0:1.1.9-1.fc12.x86_64 python-morbid-0:0.8.7.3-1.fc12.noarch python-nevow-0:0.9.32-3.fc12.noarch python-pyrad-0:1.1-3.fc12.noarch python-sippy-0:1.0.1-1.fc12.noarch python-wokkel-0:0.6.3-1.fc12.noarch pyutil-0:1.6.1-4.fc12.noarch pywbem-0:0.7.0-3.fc12.noarch rhythmbox-upnp-0:0.12.5-8.fc12.x86_64 supybot-0:0.83.4.1-2.fc12.noarch telepathy-sunshine-0:0.1.6-1.fc12.noarch The python-mwlib package is dependent on twisted-core; will packages like that one be affected too? -- Paul W. Frieldshttp://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ Where open source multiplies: http://opensource.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Talking about live upgrade
On Wed, Apr 7, 2010 at 8:21 AM, Liang Suilong liangsuil...@gmail.com wrote: Will Live upgrade replace preupgrade? No. It's much less engineering work to fix the few bugs preupgrade has than to make live upgrade reliable. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: urgent testing call: F13 kernel-2.6.33.1-24.fc13
Already running 2.6.33.1-26.fc13.i686 on my HP s3707c (AMD 5400+ Nvidia 9100 onboard) . No problems -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Using capabilities for libpcap apps
Quoting Miroslav Lichvar (mlich...@redhat.com): On Tue, Apr 06, 2010 at 10:47:22PM +0200, Radek Vokál wrote: Hi all, I need few suggestions about this .. https://blog.wireshark.org/2010/02/running-wireshark-as-you/ .. Gerald Combs, the upstream maintainer of wireshark, suggests to use capabilities instead of consolehelper+root privileges for dumpcap/wireshark. It makes whole lot of sense, so I've looked if other apps in Fedora are already using it and I haven't found any. Honestly I'm not sure about right way to use them. The idea is to add something like following to %post # groupadd -g wireshark # chgrp wireshark /usr/bin/dumpcap # setcap cap_net_raw,cap_net_admin+eip /usr/bin/dumpcap # setcap cap_net_raw,cap_net_admin+eip /usr/bin/tshark This is useful to avoid having setuid binary, but how will regular users get access to the wireshark group? Maybe through policykit? The originally quoted URL also says: # groupadd -g wireshark # usermod -a -G wireshark gerald -serge -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Synaptics click and drag problems
On Tue, Apr 06, 2010 at 04:22:34PM -0400, Jon Masters wrote: That would seem to do exactly what I wanted. I sent the author an email and will see if this still works with the recent driver (it should do). If so, then this would be a good candidate for reworking into upstream. Please don't attempt to put this in the kernel. It's an entirely inappropriate place to do it. If you're interested in making this work, there's a woeful lack of manpower upstream - I'm sure your contributions would be gratefully received. -- Matthew Garrett | mj...@srcf.ucam.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] F-13-Beta RC#5 available for testing
Greetings, Fedora 13 Beta RC#5 is available for testing. Beta RC#5 includes an updated kernel to address F13Beta blocker bug#577463. Comparisons against RC#4 are available (i386 [1] and x86_64 [2]). Once again, thanks to Andre for creating the test results page and providing Delta ISO's. There isn't a lot of time until the go/no_go meeting this evening. Please take a minute to install the live image and run through a few tests in the matrix. We are looking to identify issues that impact the Beta release criteria [3]. Available tests are linked from the following wiki pages: * Installation - https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test * Desktop - https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test As always, feel free to discuss problems/issues with other testers on #fedora-qa or t...@lists.fedoraproject.org. Thanks, James [1] https://fedoraproject.org/w/uploads/0/0d/F-13-Beta-RC5-i386.repodiff [2] https://fedoraproject.org/w/uploads/2/21/F-13-Beta-RC5-x86_64.repodiff [3] https://fedoraproject.org/wiki/Fedora_13_Beta_Release_Criteria signature.asc Description: This is a digitally signed message part ___ 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: Using capabilities for libpcap apps
2010/4/6 Radek Vokál radekvo...@gmail.com: Hi all, I need few suggestions about this .. https://blog.wireshark.org/2010/02/running-wireshark-as-you/ .. Gerald Combs, the upstream maintainer of wireshark, suggests to use capabilities instead of consolehelper+root privileges for dumpcap/wireshark. Using PolicyKit instead of hardcoding a Unix group gives a lot more flexibility to system administrators. For example, in Fedora we could interactively prompt for the root password by default. Or we could default to allowing console users auth. Or require the user's password. Or in fact, allow it for a given Unix group. Basically, you already have the privileged component/user session separation, which is great, so the dumpcap program just needs to be runnable as a DBus service, it could expose say an API to get a file descriptor which gives a dump stream for a given interface. Documentation lives at: http://hal.freedesktop.org/docs/PolicyKit/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] F-13-Beta Go/No-Go Meeting #2 @ 2010-04-08 00:00 UTC (2010-04-07 @ 8pm EDT)
# F-13-Beta Go/No-Go meeting # Date: 2010-04-08 # Time: 00:00 UTC (tonight @ 20:00 EDT, 17:00 PDT) # Location: #fedora-meeting on irc.freenode.net Before each public release Development, QA, and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the: Go/No-Go Meeting. Verifying that the Release criteria are met is the responsibility of the QA Team. Release Criteria are set for each public release and are found at https://fedoraproject.org/wiki/Fedora_Release_Criteria For more details about this important meeting see https://fedoraproject.org/wiki/Engineering_Readiness_Meetings To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto Thanks, James signature.asc Description: This is a digitally signed message part ___ 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: urgent testing call: F13 kernel-2.6.33.1-24.fc13
Running ok here on my HP Pavilion dv9750ed lappy [dmesg attached] dmesg Description: Binary data -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Macbook Pro 13.3 (5,5) Fedora 12 notes
On Wed, Apr 07, 2010 at 09:12:53AM -0400, Jon Masters wrote: merge key=input.x11_driver type=stringsynaptics/merge merge key=input.x11_options.SHMConfig type=stringOn/merge Never, ever, ever do this. Ever. Configure synaptics using xinput. Beyond that, I can't find bugs filed from you on any of the It doesn't work issues. If anything that doesn't depend on non-free components we can't ship fails to work out of the box, please make sure it's filed. It's not acceptable for users to have to remove packages, run scripts or manually change VTs in order for this to work, and perpetuating these workarounds in locations that are likely to encoruage others to do the same just means that it's less likely we'll ever fix the underlying problem. -- Matthew Garrett | mj...@srcf.ucam.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
review swap
Anyone interested in swapping reviews? I'de like to get this put to bed: https://bugzilla.redhat.com/show_bug.cgi?id=570166 If someone has something they want reviewed, let me know. Thanks! Neil -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: review swap
Neil Horman wrote: Anyone interested in swapping reviews? I'de like to get this put to bed: https://bugzilla.redhat.com/show_bug.cgi?id=570166 If someone has something they want reviewed, let me know. Thanks! Neil I'll have a go. I have https://bugzilla.redhat.com/show_bug.cgi?id=569833 and https://bugzilla.redhat.com/show_bug.cgi?id=575822 outstanding, take your pick, if you like. -J -- 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: review swap
On Wed, Apr 07, 2010 at 09:16:09AM -0500, Jon Ciesla wrote: Neil Horman wrote: Anyone interested in swapping reviews? I'de like to get this put to bed: https://bugzilla.redhat.com/show_bug.cgi?id=570166 If someone has something they want reviewed, let me know. Thanks! Neil I'll have a go. I have https://bugzilla.redhat.com/show_bug.cgi?id=569833 and https://bugzilla.redhat.com/show_bug.cgi?id=575822 outstanding, take your pick, if you like. I've grabbed 575822, thanks! Neil -J -- 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 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RPM packaging workshop example
On 04/07/2010 05:37 PM, Ralf Corsepius wrote:
There is a small bug in the example:
Instead of
%find_lang %{name}
rm -f $RPM_BUILD_ROOT/usr/share/info/dir
this should be
%find_lang %{name}
rm -f $RPM_BUILD_ROOT%{_infodir}/dir
Hmm. The original example works. Changing that and building the spec
doesn't actually work. Have you checked that?
Rahul
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: urgent testing call: F13 kernel-2.6.33.1-24.fc13
On 04/07/2010 12:21 AM, Michal Schmidt wrote: On Tue, 06 Apr 2010 15:45:39 -0700 John Reiser wrote: Then I did rpm --erase of -24 and rpm --install of -24, and the message was: - /sbin/new-kernel-pkg: line 289: 2334 Segmentation fault (core dumped) Is it reproducible if you run dracut by hand?: dracut -f -v /boot/initramfs-2.6.33.1-24.fc13.x86_64.img \ 2.6.33.1-24.fc13.x86_64 Yes, the Segmentation fault (core dumped) is reproducible. Did abrt catch the segfault? If yes, did you post the report to Bugzilla? https://bugzilla.redhat.com/show_bug.cgi?id=580141 I had to look for the abrt report; there wasn't any icon displayed in the Gnome desktop menu bar. So I didn't see it yesterday, and this report is from a re-run this morning. -- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: RPM packaging workshop example
On 04/07/2010 04:59 PM, Rahul Sundaram wrote:
On 04/07/2010 05:37 PM, Ralf Corsepius wrote:
There is a small bug in the example:
Instead of
%find_lang %{name}
rm -f $RPM_BUILD_ROOT/usr/share/info/dir
this should be
%find_lang %{name}
rm -f $RPM_BUILD_ROOT%{_infodir}/dir
Hmm. The original example works. Changing that and building the spec
doesn't actually work. Have you checked that?
You have
rm -f $RPM_BUILD_ROOT%{infodir}/dir
in the Wiki.
It should be
rm -f $RPM_BUILD_ROOT%{_infodir}/dir
Note: %{_infodir} vs. %{infodir}
Ralf
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: urgent testing call: F13 kernel-2.6.33.1-24.fc13
On Tue, 2010-04-06 at 14:53 -0700, Adam Williamson wrote: Hi, everyone. We're looking at pulling kernel-2.6.33.1-24.fc13 into Fedora 13 Beta, quite late, because current Beta candidate builds include kernel-2.6.33.1-19.fc13 which is known to include a severe bug that breaks boot on systems with Broadcom wired ethernet adapters supported by the b44 module. However, -24 has other changes from -19, including to the nouveau (NVIDIA graphics) and iwlwifi (Intel wifi) drivers. We really need as many people as possible to test kernel -24, which you can get at http://koji.fedoraproject.org/koji/buildinfo?buildID=164598 , and confirm that it works okay on your systems. To install it, use 'rpm -ivh' for the kernel and -devel packages. If you have kernel-headers installed, 'rpm -Uvh' that first. Then reboot to the kernel and check that it boots up okay. Please reply to this thread with your results. Thanks! Thanks to everyone for their testing, it's greatly appreciated. Based on the positive response here and on forums, we spun a new RC of the beta with the -24 kernel included, so now if you still want to help testing, please test that. See http://lists.fedoraproject.org/pipermail/test-announce/2010-April/61.html . -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: geos soname bump in F-12 updates
On Wed, Apr 7, 2010 at 12:50 PM, Orion Poplawski or...@cora.nwra.comwrote: Looks like the geos update for F-12 bumped the soname: -- Processing Dependency: libgeos-3.2.0.so for package: python-basemap-0.99.2-6.fc12.i686 --- Package geos.i686 0:3.2.1-1.fc12 set to be updated --- Package geos-devel.i686 0:3.2.1-1.fc12 set to be updated -- Finished Dependency Resolution Error: Package: python-basemap-0.99.2-6.fc12.i686 (@updates) Requires: libgeos-3.2.0.so Removing: geos-3.2.0-1.fc12.i686 (@updates) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest # repoquery --whatrequires libgeos-3.2.0.so python-basemap-0:0.99.2-6.fc12.i686 player-0:3.0.1-4.fc12.i686 So it looks like python-basemap and player need to get rebuilt. The soname got bumped in F-13 and devel too. I rebuilt Player two days ago and submitted it to updates-testing, but the request for F-12 is still pending. Rich Mattes -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com -- 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
[389-devel] Please review: Bug 572162 - the string |* within a search filter on a non-indexed attribute returns all elements.
https://bugzilla.redhat.com/show_bug.cgi?id=572162 https://bugzilla.redhat.com/attachment.cgi?id=405023action=diff https://bugzilla.redhat.com/attachment.cgi?id=405023action=edit -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: Macbook Pro 13.3 (5,5) Fedora 12 notes
7). The webcam isn't working out of the box and nor is bluetooth. There are instructions online covering these. Are you talking about isight-firmware-tools [1]? I orphaned it sometime ago but no one picked it up. Cheers, Debarshi [1] https://admin.fedoraproject.org/pkgdb/acls/name/isight-firmware-tools -- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -- Abraham Lincoln -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: vga_switcharoo
On Wed, Apr 07, 2010 at 09:14:09AM -0700, Adam Williamson wrote: FWIW, I figure the support is currently reasonably useless for NVIDIA chips, as there's nothing for which nouveau-on-NVIDIA is actually faster than intel-on-Intel in Linux, AFAIK. So aside from going 'ooh, it works, shiny', there's no actual reason to switch to the NVIDIA chip, even if you can make it fly. I don't believe you can use the feature with the NVIDIA proprietary driver. The only obvious reason is to be able to use displayport, since the switching implementation conveniently borrows some pins on the Intel gpu that are otherwise required for it. -- Matthew Garrett | mj...@srcf.ucam.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: vga_switcharoo
On Wed, 2010-04-07 at 18:11 +0100, Matthew Garrett wrote: On Wed, Apr 07, 2010 at 09:14:09AM -0700, Adam Williamson wrote: FWIW, I figure the support is currently reasonably useless for NVIDIA chips, as there's nothing for which nouveau-on-NVIDIA is actually faster than intel-on-Intel in Linux, AFAIK. So aside from going 'ooh, it works, shiny', there's no actual reason to switch to the NVIDIA chip, even if you can make it fly. I don't believe you can use the feature with the NVIDIA proprietary driver. The only obvious reason is to be able to use displayport, since the switching implementation conveniently borrows some pins on the Intel gpu that are otherwise required for it. Any digital output at all, in fact. - 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
Re: Two new applications to package and add to Fedora
Stephen Gallagher wrote: On 04/07/2010 08:32 AM, Damian Brasher wrote: https://sourceforge.net/projects/dspaceinvadors/ My mistake https://sourceforge.net/projects/diaser/ not dspaceinvaders for both:) 2) DSI (2001-2010) - Pristine (code) Space Invaders clone written in C and recently revived for fun and to support DIASER. https://sourceforge.net/projects/dspaceinvadors/ Where do I start? Follow the package review process for Fedora described here: http://fedoraproject.org/wiki/Package_Review_Process Okay Welcome to Fedora! Cheers :) -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: geos soname bump in F-12 updates
On Wed, Apr 7, 2010 at 8:50 AM, Orion Poplawski or...@cora.nwra.com wrote: Looks like the geos update for F-12 bumped the soname: python-basemap-0:0.99.2-6.fc12.i686 Sigh thanks for the heads up. I'll push a rebuild now. -jefNot to be picky, but it sure would be nice if there was some way I could get a heads up about this sort of problem before a soname change lands in updates-released so I can help as the basemap package maintainer before unsuspecting users see breakage.spaleta -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: vga_switcharoo
On Wed, 2010-04-07 at 13:12 -0400, Adam Jackson wrote: On Wed, 2010-04-07 at 18:11 +0100, Matthew Garrett wrote: On Wed, Apr 07, 2010 at 09:14:09AM -0700, Adam Williamson wrote: FWIW, I figure the support is currently reasonably useless for NVIDIA chips, as there's nothing for which nouveau-on-NVIDIA is actually faster than intel-on-Intel in Linux, AFAIK. So aside from going 'ooh, it works, shiny', there's no actual reason to switch to the NVIDIA chip, even if you can make it fly. I don't believe you can use the feature with the NVIDIA proprietary driver. The only obvious reason is to be able to use displayport, since the switching implementation conveniently borrows some pins on the Intel gpu that are otherwise required for it. Any digital output at all, in fact. Ah, wasn't aware of that. Thanks. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F-13 Branched report: 20100407 changes
Compose started at Wed Apr 7 09:15:04 UTC 2010 Broken deps for i386 -- edje-0.9.9.050-6.fc12.i686 requires libembryo.so.0 edje-devel-0.9.9.050-6.fc12.i686 requires embryo-devel gnome-web-photo-0.9-4.fc13.i686 requires gecko-libs = 0:1.9.2.1 hornsey-1.5.2-0.1.fc13.i686 requires libclutter-gst-0.10.so.0 libnodeupdown-backend-openib-1.9-5.fc13.i686 requires libosmcomp.so.3(OSMCOMP_2.3) libnodeupdown-backend-openib-1.9-5.fc13.i686 requires libosmcomp.so.3 moblin-app-installer-0.4.0-0.7.fc13.i686 requires libpackagekit-glib2.so.13 pyclutter-gst-0.9.2-1.fc12.i686 requires libclutter-gst-0.10.so.0 sepostgresql-8.4.2-2488.fc13.i686 requires postgresql-server = 0:8.4.2 totem-youtube-2.29.92-1.fc13.i686 requires libgdata.so.7 zikula-module-menutree-2.2-1.fc13.noarch requires zikula = 0:1.2 Broken deps for x86_64 -- edje-0.9.9.050-6.fc12.i686 requires libembryo.so.0 edje-0.9.9.050-6.fc12.x86_64 requires libembryo.so.0()(64bit) edje-devel-0.9.9.050-6.fc12.i686 requires embryo-devel edje-devel-0.9.9.050-6.fc12.x86_64 requires embryo-devel gnome-web-photo-0.9-4.fc13.x86_64 requires gecko-libs = 0:1.9.2.1 hornsey-1.5.2-0.1.fc13.x86_64 requires libclutter-gst-0.10.so.0()(64bit) libnodeupdown-backend-openib-1.9-5.fc13.x86_64 requires libosmcomp.so.3(OSMCOMP_2.3)(64bit) libnodeupdown-backend-openib-1.9-5.fc13.x86_64 requires libosmcomp.so.3()(64bit) moblin-app-installer-0.4.0-0.7.fc13.x86_64 requires libpackagekit-glib2.so.13()(64bit) pyclutter-gst-0.9.2-1.fc12.x86_64 requires libclutter-gst-0.10.so.0()(64bit) sepostgresql-8.4.2-2488.fc13.x86_64 requires postgresql-server = 0:8.4.2 totem-youtube-2.29.92-1.fc13.x86_64 requires libgdata.so.7()(64bit) zikula-module-menutree-2.2-1.fc13.noarch requires zikula = 0:1.2 Summary: Added Packages: 0 Removed Packages: 0 Modified Packages: 0 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
ideas for Summer Coding deadline moved to 14 April
In today's SIG meeting we finalized the Summer Coding 2010 schedule, and that included adding more time for ideas to be listed for students. The new deadline is next Wed. 14 April. We are inviting students to begin working on proposals starting today, with those due on 21 April. https://fedoraproject.org/wiki/Summer_Coding_2010_schedule https://fedoraproject.org/wiki/Summer_Coding_2010_ideas Thanks - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team:Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41 pgpu0vp3fa8hD.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Macbook Pro 13.3 (5,5) Fedora 12 notes
On Wed, 2010-04-07 at 20:08 +0300, Debarshi Ray wrote: 7). The webcam isn't working out of the box and nor is bluetooth. There are instructions online covering these. Are you talking about isight-firmware-tools [1]? I orphaned it sometime ago but no one picked it up. Yea. Upstream doesn't support pulling out the firmware from the current OSX driver here anyway. I believe I have a newer iSight on this system. But it's lower on my priority list than even full multitouch gesture support is (which is already about as low as possible - drag and drop is all I want to do, with a horrible hack if necessary, as I have) since I'll only use it to make a small number of video calls. Jon. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Macbook Pro 13.3 (5,5) Fedora 12 notes
On Wed, 2010-04-07 at 15:06 +0100, Matthew Garrett wrote: On Wed, Apr 07, 2010 at 09:12:53AM -0400, Jon Masters wrote: merge key=input.x11_driver type=stringsynaptics/merge merge key=input.x11_options.SHMConfig type=stringOn/merge Never, ever, ever do this. Ever. Configure synaptics using xinput. What would be the correct way to enable synclient support? I didn't find any documentation so had to go poking to figure out the right thing. Beyond that, I can't find bugs filed from you on any of the It doesn't work issues. I only just found all of these issues. I'll file some bugs later. It's not acceptable for users to have to remove packages, run scripts or manually change VTs in order for this to work, and perpetuating these workarounds in locations that are likely to encoruage others to do the same just means that it's less likely we'll ever fix the underlying problem. I agree. I'm not interested in perpetuating anything, however I am interested in a Macbook being useful right now rather than in 6 or 12 months from now. Therefore I'll take some horrible VT hack for suspend, and I'll live with a kludged up mouse driver that actually works for me. I wanted to share some instructions for those who can't figure this out but nonetheless do buy a Macbook and want to run Fedora with it today. Also, I repartitioned part of it earlier in order to keep a small staging (F13) and rawhide around. I'll try the latest bits and give an update on what works - I don't mind being a guinea pig and rebooting to test, but I'm not running rawhide as my regular desktop experience ;) Jon. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Macbook Pro 13.3 (5,5) Fedora 12 notes
On Wed, Apr 7, 2010 at 11:14 PM, Jon Masters j...@redhat.com wrote: On Wed, 2010-04-07 at 15:06 +0100, Matthew Garrett wrote: On Wed, Apr 07, 2010 at 09:12:53AM -0400, Jon Masters wrote: merge key=input.x11_driver type=stringsynaptics/merge merge key=input.x11_options.SHMConfig type=stringOn/merge Never, ever, ever do this. Ever. Configure synaptics using xinput. What would be the correct way to enable synclient support? I didn't find any documentation so had to go poking to figure out the right thing. It is very easy ... it just works with a new enough driver / xserver (i.e F-12+) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Macbook Pro 13.3 (5,5) Fedora 12 notes
On Wed, Apr 07, 2010 at 05:14:32PM -0400, Jon Masters wrote: What would be the correct way to enable synclient support? I didn't find any documentation so had to go poking to figure out the right thing. Don't use synclient. Use xinput. I only just found all of these issues. I'll file some bugs later. Please file bugs before posting workarounds. It means there's a much better chance of these issues not perpetuating. I agree. I'm not interested in perpetuating anything, however I am interested in a Macbook being useful right now rather than in 6 or 12 months from now. Therefore I'll take some horrible VT hack for suspend, and I'll live with a kludged up mouse driver that actually works for me. I wanted to share some instructions for those who can't figure this out but nonetheless do buy a Macbook and want to run Fedora with it today. With the exception of the closed driver requirements, I'm unaware of any reason why these issues wouldn't be fixed within a week. Encouraging others to utilise these workarounds perpetuates the implication that they're necessary, reducing the probability that anyone will ever get around to filing a bug and things getting fixed. Search Google and you'll find thousands of pages where people describe their workarounds, in many cases for issues that never get dealt with properly because people have their itch scratched and can't be bothered reporting the problem. This hurts the people who then have to continue applying their workarounds every cycle, and hurts the people who won't even bother trying to find workarounds or file bugs when things don't just work out of the box. -- Matthew Garrett | mj...@srcf.ucam.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Macbook Pro 13.3 (5,5) Fedora 12 notes
On Wed, Apr 07, 2010 at 11:18:37PM +0200, drago01 wrote: On Wed, Apr 7, 2010 at 4:06 PM, Matthew Garrett mj...@srcf.ucam.org wrote: Never, ever, ever do this. Ever. Configure synaptics using xinput. Can we just patch this out of the driver and let it print a warning when someone sets the option? Very possible. I'll talk to Peter. -- Matthew Garrett | mj...@srcf.ucam.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Macbook Pro 13.3 (5,5) Fedora 12 notes
On Wed, 2010-04-07 at 22:27 +0100, Matthew Garrett wrote: On Wed, Apr 07, 2010 at 05:14:32PM -0400, Jon Masters wrote: What would be the correct way to enable synclient support? I didn't find any documentation so had to go poking to figure out the right thing. Don't use synclient. Use xinput. I know how to use list-props to view various properties, but I can't see e.g. how to set the button tap and click properties on this device from the list of properties returned - what am I missing? btw, the HAL fdi policy file I created was based upon a boilerplate version already shipping with HAL in F12. That would probably also need removing if it isn't already gone in rawhide. Jon. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: urgent testing call: F13 kernel-2.6.33.1-24.fc13
On Wed, 2010-04-07 at 22:30 +0200, Stefan Schulze Frielinghaus wrote: On Mi, 2010-04-07 at 09:17 -0700, Adam Williamson wrote: [...] Thanks to everyone for their testing, it's greatly appreciated. Based on the positive response here and on forums, we spun a new RC of the beta with the -24 kernel included, so now if you still want to help testing, please test that. See http://lists.fedoraproject.org/pipermail/test-announce/2010-April/61.html . Kernel 2.6.33.1-19 and -24 do _not_ really work for me. I hadn't had the time to file a proper bug report but since no one screamed here an now, I will have to do so ;-) If -19 didn't work for you, we actually care less, strange as that may seem. Mostly this was about making sure -24 has no regressions compared to -19. Sorry for this quick and dirty bug report. Hopefully I will find some time during the weekend. Otherwise, hope this helps. Please file a regular report, or this won't get followed up. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: vga_switcharoo
On 04/07/2010 01:47 PM, Adam Williamson wrote: On Wed, 2010-04-07 at 13:12 -0400, Adam Jackson wrote: Ah, wasn't aware of that. Thanks. Also I think without the switcheroo the power consumption may be a lot higher (rumor- is that true ?) - lowering power consumption on the unused card may be helpful too ... Thanks ... -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: vga_switcharoo
On 04/07/2010 08:21 PM, Adam Williamson wrote: On Wed, 2010-04-07 at 20:10 -0400, Mail Lists wrote: On 04/07/2010 01:47 PM, Adam Williamson wrote: On Wed, 2010-04-07 at 13:12 -0400, Adam Jackson wrote: Ah, wasn't aware of that. Thanks. Also I think without the switcheroo the power consumption may be a lot higher (rumor- is that true ?) - lowering power consumption on the unused card may be helpful too ... Well, I would think that if you boot with the Intel adapter active, it wouldn't power up the NVIDIA one. But I'm just guessing :) I guessed the same, until google found claims to the contrary '-) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Macbook Pro 13.3 (5,5) Fedora 12 notes
On Wed, Apr 07, 2010 at 10:27:42PM +0100, Matthew Garrett wrote: On Wed, Apr 07, 2010 at 11:18:37PM +0200, drago01 wrote: On Wed, Apr 7, 2010 at 4:06 PM, Matthew Garrett mj...@srcf.ucam.org wrote: Never, ever, ever do this. Ever. Configure synaptics using xinput. Can we just patch this out of the driver and let it print a warning when someone sets the option? Very possible. I'll talk to Peter. SHM configuration was removed last April and these days SHM is only used for monitoring the hardware state if needed. http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/commit/?id=c09a3d50e995302ec08c5d5f8c679148613e1656 is the last commit in that series. Cheers, Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F-13-Beta Go/No-Go Meeting #2 @ 2010-04-08 00:00 UTC Recap
Greetings, Representatives from Fedora QA, Rel-Eng and Development met on IRC to review whether the Fedora 13 Beta release criteria [1] have been met. The team agreed that the Beta criteria *have* been met with F-13-Beta-RC5. For additional details, please refer to the attached minutes. Thanks, James [1] https://fedoraproject.org/wiki/Fedora_13_Beta_Release_Criteria #fedora-meeting: F-13-Beta engineering readiness meeting Meeting started by jlaska at 00:01:48 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2010-04-08/f-13-beta-eng-readiness.2010-04-08-00.01.log.html . Meeting summary --- * Waiting for critical mass (jlaska, 00:01:59) * Why are we here? (jlaska, 00:07:20) * The purpose is to decide whether the beta has met the release criteria (jlaska, 00:07:25) * LINK: https://fedoraproject.org/wiki/Fedora_13_Beta_Release_Criteria (jlaska, 00:07:30) * Go or No Go? (jlaska, 00:10:30) * AGREED: The Beta release criteria have been met with F-13-Beta-RC5 (jlaska, 00:20:51) * What's next? (jlaska, 00:21:55) * adamw removing bug#579739 from F13Beta (jlaska, 00:22:22) * RelEng will begin staging to mirrors starting Thu Apr 8 (jlaska, 00:23:32) Meeting ended at 00:29:32 UTC. Action Items Action Items, by person --- * **UNASSIGNED** * (none) People Present (lines said) --- * jlaska (50) * adamw (18) * Oxf13 (18) * nirik (8) * stickster (5) * zodbot (3) * drago01 (2) * poelcat (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot 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: Macbook Pro 13.3 (5,5) Fedora 12 notes
On Wed, Apr 07, 2010 at 10:27:03PM +0100, Matthew Garrett wrote: On Wed, Apr 07, 2010 at 05:14:32PM -0400, Jon Masters wrote: What would be the correct way to enable synclient support? I didn't find any documentation so had to go poking to figure out the right thing. Don't use synclient. Use xinput. synclient uses the same backend approach as xinput does and it is safe to use. It uses device properties since 1.1 (F-12)by default and the commandline-option to force the use of SHM was removed in 1.2 (F-12). In F12, Jon's option has zero effect on the use of synclient. xinput is IMO too generic to be really user-friendly, especially since you still need to figure out what property to trigger. Similar options may be bunched together in one property so you need to make sure you don't overwrite the other options. As an example, to set one-finger tapping you need to run: xinput --set-prop Synaptics Touchpad Synaptics Tap Actions 0 0 0 0 1 0 0 substituting the zeros with whatever value was there before to avoid changing another option. With synclient, the same is synclient TapButton1=1 In both cases, the request sent to the server is identical, or should be anyway. I recommend the use of synclient to users testing the driver for that reason, xinput is the generic swiss property knife. Jon: there's a synaptics configuration tab in system-preferences-mouse for the most common settings including the option to turn tapping on or off (off should actually be the default, not sure why it wasn't on your box). Cheers, Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
gtkmm24 updates to F13 (was Re: What are the rules for which package we build against in F-13)
On 04/07/2010 09:35 AM, Michael Schwendt wrote: On Wed, 07 Apr 2010 08:37:25 +0200, Denis wrote: On 04/07/2010 08:30 AM, Mamoru Tasaka wrote: Denis Leroy wrote, at 04/07/2010 03:20 PM +9:00: On 03/08/2010 04:37 PM, Josh Boyer wrote: The buildroots are populated from packages in the: dist-f13 dist-f13-override dist-f12-updates tags. If a package isn't in one of those tags, it's not going to be in the buildroot. If you need to build against a newer version of a package, then you need to file a ticket on the rel-eng trac instance asking for a buildroot override (which will get it tagged into dist-f13-override). Sorry to revive this old thread, but does this imply that one cannot use 'make chain-build' for F-13 updates then ? Yes. Thanks Mamoru-san, Well, this is not the most motivating news. How easy is it for releng to create a custom buildroot/tag, which could be used instead of working with an override tag? Yikes, I'm pretty stumped. How can we deal with such a burdensome process for something that is not even released yet ? Unfortunately I do not have the spare time nor the patience to go through with it, I will have to pass the buck on this. Heck I can't even create scratch builds for my own testing. -denis -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 579929] Uneeded chain of requires lead to texlive installation
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=579929 Paul Howarth p...@city-fan.org changed: What|Removed |Added Status|NEW |CLOSED Resolution||DUPLICATE --- Comment #2 from Paul Howarth p...@city-fan.org 2010-04-07 02:21:58 EDT --- This problem comes from pari's dependency on tetex-xdvi; the maintainer was asked to address this over 5 months ago in Bug #530565 but hasn't responded yet. *** This bug has been marked as a duplicate of bug 530565 *** -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- 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 569301] Branch perl-Config-IniHash for EPEL
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=569301 --- Comment #5 from Fedora Update System upda...@fedoraproject.org 2010-04-07 18:18:44 EDT --- perl-Config-IniHash-3.00.00-5.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update perl-Config-IniHash'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/perl-Config-IniHash-3.00.00-5.el5 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- 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 Log-Dispatchouli-1.100712.tar.gz uploaded to lookaside cache by iarnell
A file has been added to the lookaside cache for perl-Log-Dispatchouli: 9966cd95880556ea2e8de83098dda093 Log-Dispatchouli-1.100712.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
rpms/perl-Log-Dispatchouli/F-12 perl-Log-Dispatchouli.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2
Author: iarnell
Update of /cvs/pkgs/rpms/perl-Log-Dispatchouli/F-12
In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv32597/F-12
Modified Files:
.cvsignore sources
Added Files:
perl-Log-Dispatchouli.spec
Log Message:
initial import
--- NEW FILE perl-Log-Dispatchouli.spec ---
Name: perl-Log-Dispatchouli
Version:1.100712
Release:1%{?dist}
Summary:Simple wrapper around Log::Dispatch
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/Log-Dispatchouli/
Source0:
http://www.cpan.org/authors/id/R/RJ/RJBS/Log-Dispatchouli-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(Log::Dispatch)
BuildRequires: perl(Log::Dispatch::Array)
BuildRequires: perl(Log::Dispatch::File)
BuildRequires: perl(Log::Dispatch::Screen)
BuildRequires: perl(Log::Dispatch::Syslog)
BuildRequires: perl(Params::Util)
BuildRequires: perl(String::Flogger)
BuildRequires: perl(Try::Tiny) = 0.04
# tests
BuildRequires: perl(Pod::Coverage::TrustPod)
BuildRequires: perl(Test::Deep)
BuildRequires: perl(Test::More)
BuildRequires: perl(Test::Pod)
BuildRequires: perl(Test::Pod::Coverage)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
# not automatically detected
Requires: perl(Log::Dispatch::Array)
Requires: perl(Log::Dispatch::File)
Requires: perl(Log::Dispatch::Screen)
Requires: perl(Log::Dispatch::Syslog)
%{?perl_default_filter}
%description
Log::Dispatchouli is a thin layer above Log::Dispatch and meant to make it
dead simple to add logging to a program without having to think much about
categories, facilities, levels, or things like that. It is meant to make
logging just configurable enough that you can find the logs you want and
just easy enough that you will actually log things.
%prep
%setup -q -n Log-Dispatchouli-%{version}
# test fails
rm t/release-pod-coverage.t
%build
%{__perl} Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
rm -rf $RPM_BUILD_ROOT
make pure_install DESTDIR=$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
RELEASE_TESTING=1 make test
%clean
rm -rf $RPM_BUILD_ROOT
%files
%defattr(-,root,root,-)
%doc Changes dist.ini LICENSE META.json README
%{perl_vendorlib}/*
%{_mandir}/man3/*
%changelog
* Fri Apr 02 2010 Iain Arnell iarn...@gmail.com 1.100712-1
- Specfile autogenerated by cpanspec 1.78.
- use perl_default_filter and DESTDIR
Index: .cvsignore
===
RCS file: /cvs/pkgs/rpms/perl-Log-Dispatchouli/F-12/.cvsignore,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- .cvsignore 8 Apr 2010 02:53:58 - 1.1
+++ .cvsignore 8 Apr 2010 03:19:23 - 1.2
@@ -0,0 +1 @@
+Log-Dispatchouli-1.100712.tar.gz
Index: sources
===
RCS file: /cvs/pkgs/rpms/perl-Log-Dispatchouli/F-12/sources,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- sources 8 Apr 2010 02:53:58 - 1.1
+++ sources 8 Apr 2010 03:19:24 - 1.2
@@ -0,0 +1 @@
+9966cd95880556ea2e8de83098dda093 Log-Dispatchouli-1.100712.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
rpms/perl-Log-Dispatchouli/devel perl-Log-Dispatchouli.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2
Author: iarnell
Update of /cvs/pkgs/rpms/perl-Log-Dispatchouli/devel
In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv32597/devel
Modified Files:
.cvsignore sources
Added Files:
perl-Log-Dispatchouli.spec
Log Message:
initial import
--- NEW FILE perl-Log-Dispatchouli.spec ---
Name: perl-Log-Dispatchouli
Version:1.100712
Release:1%{?dist}
Summary:Simple wrapper around Log::Dispatch
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/Log-Dispatchouli/
Source0:
http://www.cpan.org/authors/id/R/RJ/RJBS/Log-Dispatchouli-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(Log::Dispatch)
BuildRequires: perl(Log::Dispatch::Array)
BuildRequires: perl(Log::Dispatch::File)
BuildRequires: perl(Log::Dispatch::Screen)
BuildRequires: perl(Log::Dispatch::Syslog)
BuildRequires: perl(Params::Util)
BuildRequires: perl(String::Flogger)
BuildRequires: perl(Try::Tiny) = 0.04
# tests
BuildRequires: perl(Pod::Coverage::TrustPod)
BuildRequires: perl(Test::Deep)
BuildRequires: perl(Test::More)
BuildRequires: perl(Test::Pod)
BuildRequires: perl(Test::Pod::Coverage)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
# not automatically detected
Requires: perl(Log::Dispatch::Array)
Requires: perl(Log::Dispatch::File)
Requires: perl(Log::Dispatch::Screen)
Requires: perl(Log::Dispatch::Syslog)
%{?perl_default_filter}
%description
Log::Dispatchouli is a thin layer above Log::Dispatch and meant to make it
dead simple to add logging to a program without having to think much about
categories, facilities, levels, or things like that. It is meant to make
logging just configurable enough that you can find the logs you want and
just easy enough that you will actually log things.
%prep
%setup -q -n Log-Dispatchouli-%{version}
# test fails
rm t/release-pod-coverage.t
%build
%{__perl} Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
rm -rf $RPM_BUILD_ROOT
make pure_install DESTDIR=$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
RELEASE_TESTING=1 make test
%clean
rm -rf $RPM_BUILD_ROOT
%files
%defattr(-,root,root,-)
%doc Changes dist.ini LICENSE META.json README
%{perl_vendorlib}/*
%{_mandir}/man3/*
%changelog
* Fri Apr 02 2010 Iain Arnell iarn...@gmail.com 1.100712-1
- Specfile autogenerated by cpanspec 1.78.
- use perl_default_filter and DESTDIR
Index: .cvsignore
===
RCS file: /cvs/pkgs/rpms/perl-Log-Dispatchouli/devel/.cvsignore,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- .cvsignore 8 Apr 2010 02:53:58 - 1.1
+++ .cvsignore 8 Apr 2010 03:19:24 - 1.2
@@ -0,0 +1 @@
+Log-Dispatchouli-1.100712.tar.gz
Index: sources
===
RCS file: /cvs/pkgs/rpms/perl-Log-Dispatchouli/devel/sources,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- sources 8 Apr 2010 02:53:58 - 1.1
+++ sources 8 Apr 2010 03:19:24 - 1.2
@@ -0,0 +1 @@
+9966cd95880556ea2e8de83098dda093 Log-Dispatchouli-1.100712.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 Perl-PrereqScanner-0.100830.tar.gz uploaded to lookaside cache by iarnell
A file has been added to the lookaside cache for perl-Perl-PrereqScanner: 86886120ebd2f30bc17cd82ef7513ded Perl-PrereqScanner-0.100830.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
rpms/perl-Perl-PrereqScanner/F-11 perl-Perl-PrereqScanner.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2
Author: iarnell
Update of /cvs/pkgs/rpms/perl-Perl-PrereqScanner/F-11
In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv826/F-11
Modified Files:
.cvsignore sources
Added Files:
perl-Perl-PrereqScanner.spec
Log Message:
initial import
--- NEW FILE perl-Perl-PrereqScanner.spec ---
Name: perl-Perl-PrereqScanner
Version:0.100830
Release:2%{?dist}
Summary:Tool to scan your Perl code for its prerequisites
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/Perl-PrereqScanner/
Source0:
http://www.cpan.org/authors/id/J/JQ/JQUELIN/Perl-PrereqScanner-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(namespace::autoclean)
BuildRequires: perl(PPI) = 1.205
BuildRequires: perl(PPI::Document)
BuildRequires: perl(Version::Requirements) = 0.100630
# tests
BuildRequires: perl(Pod::Coverage::TrustPod)
BuildRequires: perl(Test::More)
BuildRequires: perl(Test::Pod)
BuildRequires: perl(Test::Pod::Coverage)
BuildRequires: perl(Try::Tiny)
Requires: perl(PPI::Document)
Requires: perl(Try::Tiny)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
%{?perl_default_filter}
%description
The scanner will extract loosely your distribution prerequisites from
your files.
%prep
%setup -q -n Perl-PrereqScanner-%{version}
%build
%{__perl} Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
rm -rf $RPM_BUILD_ROOT
make pure_install DESTDIR=$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
RELEASE_TESTING=1 make test
%clean
rm -rf $RPM_BUILD_ROOT
%files
%defattr(-,root,root,-)
%doc Changes dist.ini LICENSE META.json README
%{perl_vendorlib}/*
%{_bindir}/*
%{_mandir}/man3/*
%changelog
* Thu Apr 08 2010 Iain Arnell iarn...@gmail.com 0.100830-2
- drop perl BR
* Sun Apr 04 2010 Iain Arnell iarn...@gmail.com 0.100830-1
- Specfile autogenerated by cpanspec 1.78.
- use perl_default_filter and DESTDIR
Index: .cvsignore
===
RCS file: /cvs/pkgs/rpms/perl-Perl-PrereqScanner/F-11/.cvsignore,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- .cvsignore 8 Apr 2010 02:54:20 - 1.1
+++ .cvsignore 8 Apr 2010 03:25:06 - 1.2
@@ -0,0 +1 @@
+Perl-PrereqScanner-0.100830.tar.gz
Index: sources
===
RCS file: /cvs/pkgs/rpms/perl-Perl-PrereqScanner/F-11/sources,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- sources 8 Apr 2010 02:54:20 - 1.1
+++ sources 8 Apr 2010 03:25:06 - 1.2
@@ -0,0 +1 @@
+86886120ebd2f30bc17cd82ef7513ded Perl-PrereqScanner-0.100830.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
rpms/perl-Perl-PrereqScanner/F-12 perl-Perl-PrereqScanner.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2
Author: iarnell
Update of /cvs/pkgs/rpms/perl-Perl-PrereqScanner/F-12
In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv826/F-12
Modified Files:
.cvsignore sources
Added Files:
perl-Perl-PrereqScanner.spec
Log Message:
initial import
--- NEW FILE perl-Perl-PrereqScanner.spec ---
Name: perl-Perl-PrereqScanner
Version:0.100830
Release:2%{?dist}
Summary:Tool to scan your Perl code for its prerequisites
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/Perl-PrereqScanner/
Source0:
http://www.cpan.org/authors/id/J/JQ/JQUELIN/Perl-PrereqScanner-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(namespace::autoclean)
BuildRequires: perl(PPI) = 1.205
BuildRequires: perl(PPI::Document)
BuildRequires: perl(Version::Requirements) = 0.100630
# tests
BuildRequires: perl(Pod::Coverage::TrustPod)
BuildRequires: perl(Test::More)
BuildRequires: perl(Test::Pod)
BuildRequires: perl(Test::Pod::Coverage)
BuildRequires: perl(Try::Tiny)
Requires: perl(PPI::Document)
Requires: perl(Try::Tiny)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
%{?perl_default_filter}
%description
The scanner will extract loosely your distribution prerequisites from
your files.
%prep
%setup -q -n Perl-PrereqScanner-%{version}
%build
%{__perl} Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
rm -rf $RPM_BUILD_ROOT
make pure_install DESTDIR=$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
RELEASE_TESTING=1 make test
%clean
rm -rf $RPM_BUILD_ROOT
%files
%defattr(-,root,root,-)
%doc Changes dist.ini LICENSE META.json README
%{perl_vendorlib}/*
%{_bindir}/*
%{_mandir}/man3/*
%changelog
* Thu Apr 08 2010 Iain Arnell iarn...@gmail.com 0.100830-2
- drop perl BR
* Sun Apr 04 2010 Iain Arnell iarn...@gmail.com 0.100830-1
- Specfile autogenerated by cpanspec 1.78.
- use perl_default_filter and DESTDIR
Index: .cvsignore
===
RCS file: /cvs/pkgs/rpms/perl-Perl-PrereqScanner/F-12/.cvsignore,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- .cvsignore 8 Apr 2010 02:54:20 - 1.1
+++ .cvsignore 8 Apr 2010 03:25:06 - 1.2
@@ -0,0 +1 @@
+Perl-PrereqScanner-0.100830.tar.gz
Index: sources
===
RCS file: /cvs/pkgs/rpms/perl-Perl-PrereqScanner/F-12/sources,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- sources 8 Apr 2010 02:54:20 - 1.1
+++ sources 8 Apr 2010 03:25:06 - 1.2
@@ -0,0 +1 @@
+86886120ebd2f30bc17cd82ef7513ded Perl-PrereqScanner-0.100830.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
rpms/perl-Perl-PrereqScanner/devel perl-Perl-PrereqScanner.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2
Author: iarnell
Update of /cvs/pkgs/rpms/perl-Perl-PrereqScanner/devel
In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv826/devel
Modified Files:
.cvsignore sources
Added Files:
perl-Perl-PrereqScanner.spec
Log Message:
initial import
--- NEW FILE perl-Perl-PrereqScanner.spec ---
Name: perl-Perl-PrereqScanner
Version:0.100830
Release:2%{?dist}
Summary:Tool to scan your Perl code for its prerequisites
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/Perl-PrereqScanner/
Source0:
http://www.cpan.org/authors/id/J/JQ/JQUELIN/Perl-PrereqScanner-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(namespace::autoclean)
BuildRequires: perl(PPI) = 1.205
BuildRequires: perl(PPI::Document)
BuildRequires: perl(Version::Requirements) = 0.100630
# tests
BuildRequires: perl(Pod::Coverage::TrustPod)
BuildRequires: perl(Test::More)
BuildRequires: perl(Test::Pod)
BuildRequires: perl(Test::Pod::Coverage)
BuildRequires: perl(Try::Tiny)
Requires: perl(PPI::Document)
Requires: perl(Try::Tiny)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
%{?perl_default_filter}
%description
The scanner will extract loosely your distribution prerequisites from
your files.
%prep
%setup -q -n Perl-PrereqScanner-%{version}
%build
%{__perl} Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
rm -rf $RPM_BUILD_ROOT
make pure_install DESTDIR=$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
RELEASE_TESTING=1 make test
%clean
rm -rf $RPM_BUILD_ROOT
%files
%defattr(-,root,root,-)
%doc Changes dist.ini LICENSE META.json README
%{perl_vendorlib}/*
%{_bindir}/*
%{_mandir}/man3/*
%changelog
* Thu Apr 08 2010 Iain Arnell iarn...@gmail.com 0.100830-2
- drop perl BR
* Sun Apr 04 2010 Iain Arnell iarn...@gmail.com 0.100830-1
- Specfile autogenerated by cpanspec 1.78.
- use perl_default_filter and DESTDIR
Index: .cvsignore
===
RCS file: /cvs/pkgs/rpms/perl-Perl-PrereqScanner/devel/.cvsignore,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- .cvsignore 8 Apr 2010 02:54:20 - 1.1
+++ .cvsignore 8 Apr 2010 03:25:06 - 1.2
@@ -0,0 +1 @@
+Perl-PrereqScanner-0.100830.tar.gz
Index: sources
===
RCS file: /cvs/pkgs/rpms/perl-Perl-PrereqScanner/devel/sources,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- sources 8 Apr 2010 02:54:20 - 1.1
+++ sources 8 Apr 2010 03:25:06 - 1.2
@@ -0,0 +1 @@
+86886120ebd2f30bc17cd82ef7513ded Perl-PrereqScanner-0.100830.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
Summer Coding 2010 ideas due 9 April
While we finish the Summer Coding 2010 page (http://bit.ly/FSC-2010), it is past time for you all to let us know the problems you would like to see solved by summer coding/internship students. By Friday 09 April. Idea page is here: https://fedoraproject.org/wiki/Category:Summer_Coding_2010_ideas How-to fill out an ideas page is here: https://fedoraproject.org/wiki/How_to_create_an_idea_page_for_Summer_Coding Let’s get this filled with serious ideas you are willing to mentor for or help find the mentor. Join the discussion list and be prepared to talk about your ideas or proposals. http://lists.fedoraproject.org/mailman/listinfo/summer-coding-discuss If you were already a mentor and want to help with mentoring, such as proposal reviews, let us know and join the mentors list. http://lists.fedoraproject.org/mailman/listinfo/summer-coding-mentors Tracking these ideas is a PITA and in fact the lack of an ideas page lead to us not getting in the Google Summer of Code this year. This is all part of a larger issue around tracking smaller ideas for beginners and students, but for now this will have to do. Anyone want to hack on OpenHatch.org, please help. We’re hoping some of the functionality we are handling manually may be included in upcoming versions of OpenHatch. If that direction gets us fruit, we may use OpenHatch as an ongoing way to expose projects to students and other new contributors. (This email derived from my post at http://bit.ly/bofYla) - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team:Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41 pgplTQcWDAuiF.pgp Description: PGP signature ___ devel-announce mailing list devel-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce
ideas for Summer Coding deadline moved to 14 April
In today's SIG meeting we finalized the Summer Coding 2010 schedule, and that included adding more time for ideas to be listed for students. The new deadline is next Wed. 14 April. We are inviting students to begin working on proposals starting today, with those due on 21 April. https://fedoraproject.org/wiki/Summer_Coding_2010_schedule https://fedoraproject.org/wiki/Summer_Coding_2010_ideas Thanks - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team:Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41 pgpSc7U0MV4zP.pgp Description: PGP signature ___ devel-announce mailing list devel-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce
