Re: Bugzilla Desktop Client
On 09/06/2009 05:42 PM, Kevin Kofler wrote: nodata wrote: I'd suggest hiding all of the Component, Version, Severity, Hardware, OS information. That makes no sense whatsoever, this information is required by the developers for actually fixing the bug! In my understanding, the purpose of this tool is to make bug reporting easy, so it make sense to not ask the user questions which are better answered by the application, doing an automatic query. Trying to help the user figure out the component somehow (e.g. look up by executable name and/or look up by menu entry which does an rpm -qf to find the binary package and then queries RPM again for the matching source package) makes sense, hiding it entirely doesn't. I think by default this application (Boog) must ask by default maximum 3 questions: the application name (preferably selected from a nice list, with icons and full names), a description and maybe a summary (the summary is needed by Bugzilla). Everything (version numbers, logs, configs) else can be collected automatically. Then an advanced user can inspect/modify the data, before sending, but a beginner can just send it as is. -- nicu :: http://nicubunu.ro :: http://nicubunu.blogspot.com/ photography: http://photoblog.nicubunu.ro/ my Fedora stuff: http://fedora.nicubunu.ro/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Bugzilla Desktop Client
On 09/06/2009 09:30 AM, Rahul Sundaram wrote: You might want to look at https://fedorahosted.org/boog/ We need to avoid duplication of work. Kushal Das hasn't started working on the GUI since we are waiting on the design team to provide mockups but he has a command line client that does a bunch of nifty things. While there is probably a lot of room for collaboration, those tools looks like having different targets, not replacements for each other: one is a general bugzilla client aiming to be able to work with as many ticketing systems as possible and another is intended to make bug reporting easy *for Fedora*. -- nicu :: http://nicubunu.ro :: http://nicubunu.blogspot.com/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: what features are required in Fedora kernel
Steve Grubb píše v Pá 04. 09. 2009 v 14:41 -0400: On Friday 04 September 2009 02:17:10 pm Dan Horák wrote: I am building kernels for some ARM based devices that use Fedora/ARM as user-land. Glad to see someone else looking at the ARM kernel. These devices are usually very limited in the size of kernel that can be stored in their flash memories (like 2MB kernel, 4MB ramdisk). So I would like to know what kernel features make a Fedora kernel, what are the MUST HAVE features? Maybe some usb devices. Which ones...I don't know. :) USB support is built as modular so I can enable all :-) Now I have those on my list - audit Note that the audit system on ARM is dysfunctional. No one has ever taken the time to write the requisite code in arch/arm/kernel/ptrace.c to call audit_syscall_entry(). Without that code upstream (or as a patch), the audit system is limited to user space originating events. I don't know if SE Linux AVC's are affected by the audit system not having its hands on a lot of information during the syscall. good to know - SELinux - IPv6 - Netfilter for both IPv4 and IPv6 Netfilter is needed badly on that arch since the default system image has a mail server listening to the public IP address and running as root. Iptables is needed to block this access. I have uploaded my kernel + modules, see https://www.redhat.com/archives/fedora-arm/2009-September/msg6.html for details. Dan -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Bugzilla Desktop Client
Le Lun 7 septembre 2009 09:22, Nicu Buculei a écrit : While there is probably a lot of room for collaboration, those tools looks like having different targets, not replacements for each other: one is a general bugzilla client aiming to be able to work with as many ticketing systems as possible and another is intended to make bug reporting easy *for Fedora*. And many Fedora devs will ask to report the bug upstream instead, so a tool that only works with bugzilla.redhat.com is pretty useless -- Nicolas Mailhot -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: what features are required in Fedora kernel
Mike McGrath píše v Pá 04. 09. 2009 v 15:55 -0500: On Fri, 4 Sep 2009, Dan Horák wrote: Hi all, I am building kernels for some ARM based devices that use Fedora/ARM as user-land. These devices are usually very limited in the size of kernel that can be stored in their flash memories (like 2MB kernel, 4MB ramdisk). So I would like to know what kernel features make a Fedora kernel, what are the MUST HAVE features? This is an interesting question. I'd hate to think that something being unable to be included because of technical reasons would cause us to be unable to call something Fedora. It's not meant as a strict question what can or can't be called Fedora, but rather what are the important features that are used by the user space tools in Fedora. Dan -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Bugzilla Desktop Client
2009/9/6 Björn Persson bj...@xn--rombobjrn-67a.se: Yaakov Nemoy wrote: You can always revoke a pub uuid in the future. Perhaps a message about that will encourage people to be more forthcoming with Smolt profiles within such a tool. Obviously, including a smolt profile just automates certain kinds of information (read: privacy) disclosures, which is sometimes necessary in a bug report anyways. Unless that information as cached elsewhere, revoking a public UUID essentially makes people forget the details though. Once published, always public. You can of course hope that nobody saved a copy of your details before you retracted them, but you can never be sure. The only safe assumption is that any information you publish remains public forever. That said, I'm personally not very concerned about letting people know what hardware I have; my secrets are of other kinds. (But of course I wouldn't want anything to be published without my permission.) When i put together that algorithm, i took that fact into account. The words i used is that a secret between two people in not a secret. If the facts change though, and you don't tell anyone, then the change, (or the delta or patch, if you will) is a secret. Releasing the fact shouldn't force you to release the change. Another fact to take into account is that although you may have released it, and parts of it may have been copied into the bug report, it's not necessarily true that the information is cached somewhere. There's a percentage chance it has been, and then another percentage chance that someone knows where to look to find it. Revoking the public part of the secret doesn't absolve you of privacy concerns, but, in certain circumstances, it can mitigate them. Given how statistics and numbers work nowadays, anything that lets you mitigate issues can have a cummulative effect with other things. Then it's just a question of not being the slowest sheep when the wolves show up. -Yaakov -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Bugzilla Desktop Client
On 09/07/2009 01:36 PM, Nicolas Mailhot wrote: Le Lun 7 septembre 2009 09:22, Nicu Buculei a écrit : While there is probably a lot of room for collaboration, those tools looks like having different targets, not replacements for each other: one is a general bugzilla client aiming to be able to work with as many ticketing systems as possible and another is intended to make bug reporting easy *for Fedora*. As I indicated, both of them use python-bugzilla and python-bugzilla doesn't yet with many ticketing systems. And many Fedora devs will ask to report the bug upstream instead, so a tool that only works with bugzilla.redhat.com is pretty useless If you want, check the number of bugs reported against RH bugzilla where the maintainer does not push the reporters themselves to report again to upstream. I suspect you will find that a very high number. Neverthless, if someone wants to extend python-bugzilla to work with other bugzilla's feel free to talk to Will Woods about it. Rahul -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Bugzilla Desktop Client
2009/9/7 Rahul Sundaram wrote: On 09/07/2009 01:36 PM, Nicolas Mailhot wrote: [..] And many Fedora devs will ask to report the bug upstream instead, so a tool that only works with bugzilla.redhat.com is pretty useless [..] If you want, check the number of bugs reported against RH bugzilla where the maintainer does not push the reporters themselves to report again to upstream. I suspect you will find that a very high number. Neverthless, if someone wants to extend python-bugzilla to work with other bugzilla's feel free to talk to Will Woods about it. [..] btw .. python-bugzilla does work with upstream bugzilla nicely, and it is of course not meant for other ticketing systems. -- Rakesh Pandit https://fedoraproject.org/ freedom, friends, features, first -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Bugzilla Desktop Client
On 09/07/2009 02:32 PM, Rakesh Pandit wrote: btw .. python-bugzilla does work with upstream bugzilla nicely, and it is of course not meant for other ticketing systems. The problem is that deployments of bugzilla (GNOME, KDE etc) tend to be customized and if we want to support them, we need to test/tweak to make sure they work will with the ones we care about. Rahul -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Bugzilla Desktop Client
On 09/07/2009 02:36 PM, Rahul Sundaram wrote: On 09/07/2009 02:32 PM, Rakesh Pandit wrote: btw .. python-bugzilla does work with upstream bugzilla nicely, and it is of course not meant for other ticketing systems. The problem is that deployments of bugzilla (GNOME, KDE etc) tend to be customized and if we want to support them, we need to test/tweak to make sure they work will with the ones we care about. Rahul Yeah, that is going to be a bottleneck. But that has to be fixed while working. Customization also has levels. If they are customizing with customizing interfaces already provided by bugzilla, then it wouldn't be a problem. One can use bzobj.__proxy.api and cf_* keys. But if they have tweaked it beyond that then it gets worse. -- Regards, Rakesh Pandit -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Bugzilla Desktop Client
On Mon, Sep 7, 2009 at 2:46 PM, Rakesh Panditrakesh.pan...@gmail.com wrote: Yeah, that is going to be a bottleneck. But that has to be fixed while working. Customization also has levels. If they are customizing with customizing interfaces already provided by bugzilla, then it wouldn't be a problem. One can use bzobj.__proxy.api and cf_* keys. But if they have tweaked it beyond that then it gets worse. For generic uses, bug.* methods are good enough to do almost everything. But people try to customise bugzilla beyond eveything :( Kushal -- http://fedoraproject.org http://kushaldas.in -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Where are selinux workarounds/exceptions/hacks tracked?
On 09/05/2009 12:17 PM, nodata wrote: I remember ages and ages ago when selinux first came to Fedora that lots of apps (Java, flash, Mozilla/Firefox) didn't work because the apps did dodgy things with memory. I was wondering if these dodgy things still existed, and if they did, what effort was being put into making them go away? Is it tracked anywhere? Thanks. Java/Mono/Wine all have to do the dodgy things in memory, Since by there nature they write to a memory location and then execute the code. I believe firefox/Mozilla has been fixed. Also certain libflash instances have been fixed. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Completed review requests bugzilla report: May, Jun, Jul Aug
Start Date: 2009-05-01 00:00:00 End Date: 2009-08-31 00:00:00 Parag AN(पराग) - 160 Jason Tibbitts - 63 Jussi Lehtola - 62 Mamoru Tasaka - 42 Orcan 'oget' Ogetbil - 25 Jochen Schmitt - 22 Andrew Overholt - 20 Christoph Wickert - 18 David Nalley - 16 Alexander Kurtakov - 15 Peter Lemenkov - 15 Jan Klepek - 12 Lubomir Rintel - 12 Chris Weyl - 10 Dan Horák - 10 Andrew Colin Kissa - 9 Chitlesh GOORAH - 9 Mattias Ellert - 9 Yaakov Nemoy - 9 Michel Alexandre Salim - 8 Peter Robinson - 8 Fabian Affolter - 7 Tom spot Callaway - 7 Brennan Ashton - 6 Kevin Fenzi - 6 Marcela Maslanova - 6 Martin Gieseking - 6 Thomas Sailer - 6 Toshio Ernie Kuratomi - 6 Yanko Kaneti - 6 Allisson Azevedo - 5 Dennis Gilmore - 5 Erik van Pienbroek - 5 Hans de Goede - 5 Ian Weller - 5 Jerry James - 5 Matej Cepl - 5 Michal Ingeli - 5 Nicolas Mailhot - 5 Nils Philippsen - 5 Rahul Sundaram - 5 Christian Krause - 4 Emmanuel Seyman - 4 Jens Petersen - 4 Matthias Clasen - 4 Nuno Santos - 4 manuel wolfshant - 4 Ben Boeckel - 3 Caolan McNamara - 3 Guido Grazioli - 3 Iain Arnell - 3 Jeff Johnston - 3 Lorenzo Villani - 3 Mike Bonnet - 3 Nick Bebout - 3 Nicolas Chauvet (kwizart) - 3 Nikolay Vladimirov - 3 Pavel Alexeev (aka Pahan-Hubbitus) - 3 Rakesh Pandit - 3 Remi Collet - 3 Steven M. Parrish - 3 Wesley S. Hearn - 3 Bastien Nocera - 2 Bob Relyea - 2 David Lutterkort - 2 Felix Kaechele - 2 Igor Jurišković - 2 Ivana Varekova - 2 Jon Ciesla - 2 Matthew Barnes - 2 Michael Schwendt - 2 Mike McGrath - 2 Owen Taylor - 2 Praveen K Paladugu - 2 Rasmus Ory Nielsen - 2 Sergio Pascual - 2 Stepan Kasal - 2 Warren Togami - 2 Xavier Lamien - 2 Zarko (grof) - 2 srinivas - 2 Adel Gadllah - 1 Alex Lancaster - 1 Alexey Torkhov - 1 Andreas Osowski - 1 Armin - 1 Bill Nottingham - 1 Bryan O'Sullivan - 1 Christopher Aillon - 1 D. Marlin - 1 Daniel Berrange - 1 Dave Malcolm - 1 David Hannequin - 1 Denis Arnaud - 1 Dominic Hopf - 1 Edwin ten Brink - 1 Eelko Berkenpies - 1 Fabio Massimo Di Nitto - 1 Fernando Nasser - 1 Gary T. Giesen - 1 Gianluca Sforna - 1 Guillaume Kulakowski - 1 Harald Hoyer - 1 Jarod Wilson - 1 Jeff Sheltren - 1 Jeremy Katz - 1 Jesse Keating - 1 Jim Meyering - 1 John (J5) Palmieri - 1 Jon Stanley - 1 Josh Boyer - 1 José Matos - 1 Julian Aloofi - 1 Kalev Lember - 1 Lucian Langa - 1 Luya Tshimbalanga - 1 Mat Booth - 1 Michal Nowak - 1 Miloslav Trmač - 1 Paul Lange - 1 Paul W. Frields - 1 Peter Gordon - 1 Randall Berry - 1 Ray Van Dolson - 1 Rex Dieter - 1 Richard W.M. Jones - 1 Ricky Zhou - 1 Robin Norwood - 1 Ruben Kerkhof - 1 Sandro Mathys - 1 Scott Seago - 1 Sebastian Dziallas - 1 Silas Sewell - 1 Simon Wesp - 1 Sven Lankes - 1 Terje Røsten - 1 Till Maas - 1 Tomas Mraz - 1 Ville Skyttä - 1 Ville-Pekka Vainio - 1 Walter Gould - 1 leigh scott - 1 Total reviews modified: 833 Merge Reviews: 27 Review Requests: 795 This report by generated by bzReviewReport.py. The source is available at: https://fedorahosted.org/triage/browser/scripts/bzReviewReport.py Please submit patches or bug reports at: https://fedorahosted.org/triage/ -- Rakesh Pandit https://fedoraproject.org/ freedom, friends, features, first -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Evolution in koji not correct version?
On Sat, 2009-09-05 at 08:02 -0500, Mike Chambers wrote: Latest release in rawhide for evo is evolution-2.27.91-1.fc12.x86_64. The latest built in koji is evolution-2.27.5-3.1.fc12. Hi, thank you for noticing. I just built a 2.27.92, which had been released today, thus we are back on the right track. Bye, Milan -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
What happens to hermes.ko in 2.6.30
Hello All! I just wondering why hermes_dld.ko hermes.ko were disabled in 2.6.30. Did they obsoleted by orinoco*.ko ? -- With best regards, Peter Lemenkov. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Adding a project to transifex
I went over to https://translate.fedoraproject.org/ earlier with the idea of adding my project. Firstly, there's no hint of how to do this from the front page. After some Leisure Suit Larry style clicking on stuff at random until something favourable happens, I found a link carefully hidden at the bottom of the browse all projects page. The link says: Couldn't find your project? Go ahead and aadd it/a! So, I clicked in 'add it', which gives me: === Forbidden access Looks like you do not have the necessary permissions to the required action. Here's a link to the homepage. You know, just in case. === That's everything, btw. No link to an admin contact, process, mailing list, documentation, or anything. Just a promise of being able to add my project, then a bucket of cold water. Despite that, I'd still like to add my project to Transifex! Can anybody point me to the process? Thanks, Matt -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Adding a project to transifex
Matthew Booth wrote: I went over to https://translate.fedoraproject.org/ earlier with the idea of adding my project. The translations are now hosted at http://transifex.net/ (the main Transifex instance). Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Adding a project to transifex
On Mon, Sep 7, 2009 at 4:28 PM, Matthew Booth wrote: I went over to https://translate.fedoraproject.org/ earlier with the idea of adding my project. Firstly, there's no hint of how to do this from the front page. After some Leisure Suit Larry style clicking on stuff at random until something favourable happens, I found a link carefully hidden at the bottom of the browse all projects page. The link says: Couldn't find your project? Go ahead and aadd it/a! So, I clicked in 'add it', which gives me: === Forbidden access Looks like you do not have the necessary permissions to the required action. Here's a link to the homepage. You know, just in case. === That's everything, btw. No link to an admin contact, process, mailing list, documentation, or anything. Just a promise of being able to add my project, then a bucket of cold water. Despite that, I'd still like to add my project to Transifex! Can anybody point me to the process? Thanks, Matt Go to https://fedoraproject.org/wiki/L10N -- Frequently Asked Questions -- 1.3.8 How do I add a module to Transifex? (#add-transifex) This will tell you what to do step by step. Orcan -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Adding a project to transifex
On 07/09/09 21:56, Orcan Ogetbil wrote: Despite that, I'd still like to add my project to Transifex! Can anybody point me to the process? Thanks, Matt Go to https://fedoraproject.org/wiki/L10N -- Frequently Asked Questions -- 1.3.8 How do I add a module to Transifex? (#add-transifex) This will tell you what to do step by step. Thanks, I'm fairly sure this is what I'm looking for. If anybody's listening, it would be nice to have this linked from the website! Matt -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Adding a project to transifex
On 07/09/09 21:55, Kevin Kofler wrote: Matthew Booth wrote: I went over to https://translate.fedoraproject.org/ earlier with the idea of adding my project. The translations are now hosted at http://transifex.net/ (the main Transifex instance). Was there an official announcement about that? Matt -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Adding a project to transifex
On Mon, Sep 7, 2009 at 23:17, Matthew Boothmbo...@redhat.com wrote: On 07/09/09 21:55, Kevin Kofler wrote: Matthew Booth wrote: I went over to https://translate.fedoraproject.org/ earlier with the idea of adding my project. The translations are now hosted at http://transifex.net/ (the main Transifex instance). Was there an official announcement about that? I think the guys at Indifex (the company that Dimitris and others founded) only created transifex.net like a place to host translations, just like Gitorious or Fedorahosted for hosting development, not as a replacement of Fedora's Transifex instance. So I guess you could host your project there, or in translate.fp.o. The only difference is that there, you might have a much bigger community of translators, not just Fedora translators. For more informations, I suggest you ask the Infrastructure team in #fedora-admin or on their mailing-list. They'll be more indicated to answer you about hosting on translate.fp.o ;) -- Mathieu Bridon (bochecha) -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Rawhide fonts problem report for 2009-09-06
Hi, The package wine-fonts is not mentioned, why? It contains /usr/share/wine/fonts/symbol.ttf26040 /usr/share/wine/fonts/tahoma.ttf89124 /usr/share/wine/fonts/tahomabd.ttf 80408 /usr/share/wine/fonts/vgas1255.fon 6480 BTW is the name tahoma a trademark? -- bbbush ^_^ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Evolution in koji not correct version?
On Mon, 2009-09-07 at 20:10 +0200, Milan Crha wrote: On Sat, 2009-09-05 at 08:02 -0500, Mike Chambers wrote: Latest release in rawhide for evo is evolution-2.27.91-1.fc12.x86_64. The latest built in koji is evolution-2.27.5-3.1.fc12. Hi, thank you for noticing. I just built a 2.27.92, which had been released today, thus we are back on the right track. Bye, Milan Got it, thanks. That version also fixes the restore problem from the bug below... https://bugzilla.redhat.com/show_bug.cgi?id=520013 -- Mike Chambers Madisonville, KY Best lil town on Earth! -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
alsa support in sidplay
Hello Linus,
since when we culled OSS support in Fedora's kernel, sidplay
could not delight our ears with the three celestial, synth
voices of the SID.
If you like this patch, I'll go on and commit myself using my
überpackager superpowers. I'm also planning to submit the
autoconf changes upstream.
diff -u -p -r1.6 sidplay.spec
--- sidplay.spec11 May 2009 20:10:35 - 1.6
+++ sidplay.spec8 Sep 2009 04:13:27 -
@@ -3,7 +3,7 @@
Name: sidplay
Version: 2.0.9
-Release: 7%{?dist}
+Release: 8%{?dist}
Summary: A command-line tool for playing back SID files
URL: http://sidplay2.sourceforge.net/
Group: Applications/Multimedia
@@ -12,6 +12,8 @@
# http://packages.debian.org/unstable/oldlibs/sidplay
Patch0:sidplay_2.0.9-5.diff.gz
Patch1:gcc440.patch
+Patch2:sidplay-alsa.patch
+Patch3:sidplay-autohell-fixes.patch
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
License: GPL
BuildRequires: libsidplay-devel
@@ -35,9 +37,12 @@
%setup -q
%patch0 -p1
%patch1 -p1
+%patch2 -p1
+%patch3 -p1
%build
-%configure --with-sidbuilders=%{_libdir}/sidplay/builders
+ACLOCAL='aclocal -I unix' autoreconf -v --force --install
+%configure --with-sidbuilders=%{_libdir}/sidplay/builders --with-alsa
make %{?_smp_mflags}
%install
@@ -54,6 +59,11 @@
%{_bindir}/*
%changelog
+* Mon Sep 07 2009 Bernie Innocenti ber...@codewiz.org 2.0.9-7
+- Add sidplay-alsa.patch, stolen from Gentoo
+- Add sidplay-autohell-fixes.patch, rolled in house
+- Rock!
+
* Mon May 11 2009 Linus Walleij tr...@df.lth.se 2.0.9-6
- Located a suspect GCC 4.4.0 rebuild bug.
From http://bugs.gentoo.org/98769
diff -Nrup sidplay-2.0.9.orig/configure.ac sidplay-2.0.9/configure.ac
--- sidplay-2.0.9.orig/configure.ac 2009-09-06 00:26:21.370889171 -0400
+++ sidplay-2.0.9/configure.ac 2009-09-06 00:26:38.631866724 -0400
@@ -24,6 +24,8 @@ AC_CHECK_HEADERS(sys/ioctl.h linux/sound
sys/soundcard.h soundcard.h sys/audio.h sun/audioio.h sun/dbriio.h sys/audioio.h \
audio.h dmedia/audio.h)
+AC_ARG_WITH(alsa,[ --with-alsa Use ALSA library for sound],[WANT_ALSA=$withval],[WANT_ALSA=no])
+
AH_TOP(
[/* Define supported audio driver */
#undef HAVE_HARDSID
@@ -60,9 +62,17 @@ case $host in
AC_MSG_RESULT(irix)
AC_CHECK_LIB(audio, main, [AUDIO_LDADD=-laudio AC_SUBST(AUDIO_LDADD)])
;;
-*linux*) AC_DEFINE(HAVE_OSS)
-audiodrv_libadd=./audio/oss/liboss.a
-AC_MSG_RESULT(oss)
+*linux*)
+if test $WANT_ALSA = yes ; then
+ AC_DEFINE(HAVE_ALSA)
+ audiodrv_libadd=./audio/alsa/libalsa.a
+ AC_MSG_RESULT(alsa)
+ AC_CHECK_LIB(asound, main, [AUDIO_LDFLAGS=-lasound AC_SUBST(AUDIO_LDFLAGS)])
+ else
+ AC_DEFINE(HAVE_OSS)
+ audiodrv_libadd=./audio/oss/liboss.a
+ AC_MSG_RESULT(oss)
+ fi
;;
*netbsd*) AC_DEFINE(HAVE_OSS)
audiodrv_libadd=./audio/oss/liboss.a
diff -Nrup sidplay-2.0.9.orig/src/audio/alsa/audiodrv.cpp sidplay-2.0.9/src/audio/alsa/audiodrv.cpp
--- sidplay-2.0.9.orig/src/audio/alsa/audiodrv.cpp 2009-09-06 00:26:21.372869292 -0400
+++ sidplay-2.0.9/src/audio/alsa/audiodrv.cpp 2009-09-06 00:26:38.633866542 -0400
@@ -2,6 +2,9 @@
// Advanced Linux Sound Architecture (ALSA) specific audio driver interface.
// --
/***
+ * 2005-07-12: Heikki Orsila heikki.ors...@iki.fi
+ * Fixed use of obsolete parts of ALSA API
+ *
* $Log: audiodrv.cpp,v $
* Revision 1.7 2002/03/04 19:07:48 s_a_white
* Fix C++ use of nothrow.
@@ -31,6 +34,7 @@
#include audiodrv.h
#ifdef HAVE_ALSA
+#include iostream
#include stdio.h
#ifdef HAVE_EXCEPTIONS
# include new
@@ -57,88 +61,86 @@ void Audio_ALSA::outOfOrder ()
void *Audio_ALSA::open (AudioConfig cfg, const char *)
{
AudioConfig tmpCfg;
-int mask, wantedFormat, format;
-int rtn;
-int card = -1, dev = 0;
-
-if (_audioHandle != NULL)
-{
+snd_pcm_uframes_t buffer_frames;
+snd_pcm_hw_params_t *hw_params;
+
+// Transfer input parameters to this object.
+// May later be replaced with driver defaults.
+tmpCfg = cfg;
+unsigned int rate = tmpCfg.frequency;
+
+if (_audioHandle != NULL) {
_errorString = ERROR: Device already in use;
return NULL;
}
-if ((rtn = snd_pcm_open_preferred (_audioHandle, card, dev, SND_PCM_OPEN_PLAYBACK)))
-{
+if (snd_pcm_open (_audioHandle, default, SND_PCM_STREAM_PLAYBACK, 0)) {
_errorString = ERROR: Could not open audio device.;
goto open_error;
}
-
-// Transfer input parameters to this object.
-// May later be replaced with driver defaults.
-tmpCfg = cfg;
-snd_pcm_channel_params_t pp;
-snd_pcm_channel_setup_t setup;
-
-
Re: Rawhide fonts problem report for 2009-09-06
Le mardi 08 septembre 2009 à 09:11 +0800, Yuan Yijun a écrit : Hi, The package wine-fonts is not mentioned, why? Excellent question, it certainly should have been, and I have no idea why. Maybe it was not present in the source repo I used¹ when the test was run ? Otherwise repoquery may have a bug somewhere BTW is the name tahoma a trademark? It certainly is, but sine IIRC some badly written windows app crash directly if some specific windows fonts are not present, I suppose it made it as part of the windows ABI. You should ask spot for an opinion. ¹ http://download.fedora.redhat.com/pub/fedora/linux/development/x86_64/os/Packages/ -- Nicolas Mailhot signature.asc Description: Ceci est une partie de message numériquement signée -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
[Bug 520505] Spurious dependency on perl(Test::More)
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=520505 --- Comment #11 from Ville Skyttä ville.sky...@iki.fi 2009-09-07 16:13:55 EDT --- (In reply to comment #10) is this all handwaving and FUD? Thank you for so kindly considering differing opinions. -- 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 Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 520505] Spurious dependency on perl(Test::More)
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=520505 --- Comment #12 from Chris Weyl cw...@alumni.drew.edu 2009-09-07 16:47:41 EDT --- (In reply to comment #11) (In reply to comment #10) is this all handwaving and FUD? Thank you for so kindly considering differing opinions. As I said, I'm more than open to different opinions and the merits of these approaches. You claimed I'd done actual harm to Fedora, effectively saying that your opinions are fact and empirically quantifiable. I welcome and seek feedback, as this isn't dicta but rather an evolving process; but simply slamming the practice, citing actual harm, and then claiming that ..a guideline will be needed isn't very constructive. How about, instead of bashing, we sit down and try to work out how to best do this -- that is, including the test suite in some form that satisfies both of us and benefits the community as a whole. I'd like to see the evidence of any concrete harm done specific to including the test suites in %_docdir, but I haven't seen any yet, despite repeated requests. If there is actually any harm caused here, I'd like to correct it. -- 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 Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
