similar to: Query for old bugs with no activity

Hi there wine list this is not going to be a request for help as much as it's a request for how I can help the wine developers. I've got some time over the next couple of weeks and a stack of applications I want to see if I can get running under wine. I thought if I started testing a whole bunch of things I might be able to gather some useful test data for the wine developers as a way

Howdy Wine users! The list of bugs with downloads that haven't been checked on in a while has gotten pretty long (1,359! as of May 6, 2009). If you're a moderate to advanced user of wine, please help by downloading and testing these applications and testing these bugs. Be sure you're using a recent version of wine (1.1.20 or git) and testing in a clean WINEPREFIX. Quick guide: 1)

Hi All, I Am new to Wine, and I try to get Office 97 to work, but the M$ Office installer dosen't work yet. Se bug 150 on:

too many UNCO bugs are listed for wine < 1.0 . I suggest purging or archiving the really old ones since they must have been fixed or no-one cares for them atm. Either way they're too confusing!

Howdy Wine users! Looking for an easy way to help Wine? There are plenty of bug reports that could use a retest in current Wine, but developers are busy fixing bugs :-). Here's a list of bugs (536) that have a download available, but haven't been checked on in the last 6 months. If you'd got time and bandwidth to kill, and want to help Wine, please test them. After testing, leave a

Morning, I've installed asterisk on FC4 and had a few problems with zaptel stuff. Having installed it on SuSE I was able to check a few things that were different. When installed with the RPMS, the udev stuff gets put into the normal 50-udev file under /etc/udev. On SuSE, it worked when the necessary zaptel section was in a separate file name 55-zaptel.udev (the name is arbitrary,

Hi, where could one find any LLVM development roadmap for this and perhaps next year? Especially would be interesting to know about * planned features for PS3 Cell processor -- as well as for Wii, Xbox360 CPUs * multithreading in general * possibly coming changes in major versioning and related issues * other interesting featuring comments on current status to above listed items are also

Hi Valery, On Tue, 2007-04-10 at 13:15 +0200, Valery Khamenya wrote: > Hi, > > where could one find any LLVM development roadmap for this > and perhaps next year? About the best "roadmap" we have is the list of enhancements in Bugzilla:

Eric Zimmerman wrote: > Chris, > > I'm fine with using JIT, but I'm trying to understand this problem: > 1. My LLVM program does not produce correct results > 2. Using llvm-dis, I disassemble the bytecode to C > 3. I recompile using GCC and the program _works correctly_. > > The only odd thing is when I recompile with GCC, I see these messages: > >

Chris, I'm fine with using JIT, but I'm trying to understand this problem: 1. My LLVM program does not produce correct results 2. Using llvm-dis, I disassemble the bytecode to C 3. I recompile using GCC and the program _works correctly_. The only odd thing is when I recompile with GCC, I see these messages: pal3.c:195: warning: conflicting types for built-in function `strcmp'

https://bugzilla.samba.org/show_bug.cgi?id=5448 Summary: rsync modifies files in place even without --inplace specified Product: rsync Version: 3.0.2 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org

Hello, I recently upgraded a server from CentOS 6.2 to 6.3 I found a change in the behavior of rsyslog's configuration file that I found particularly interesting. The "$PreserveFQDN on" directive was not being recognized as the config remained unchanged during the upgrade. This incorrect behavior caused the host to syslog with only the host name and not it's fully qualified

Why can it not find my object? What am i missing here? Here is my code: require ''rexml/document'' include REXML # classes to represent the objects and relationships in the xml file class Article attr_accessor :id, :post, :archive, :ntype, :head, :blurb, :body, :fblurb, :fimage, :att, :source, :copy, :brand end # the base parser class BaseXMLParser def initialize(filename)