On Thu, Apr 12, 2012 at 16:58, Daniel Jelinski wrote:
> 2012/4/12 Scott Ritchie :
>> On 4/12/12 1:23 AM, Daniel Jeliński wrote:
>>>
>>> Hello all,
>>> I am trying to get Microsoft SQL Server Management Studio to work
>>> flawlessly under Wine. For the most part I create and triage related bug
>>>
2012/4/12 Scott Ritchie :
> On 4/12/12 1:23 AM, Daniel Jeliński wrote:
>>
>> Hello all,
>> I am trying to get Microsoft SQL Server Management Studio to work
>> flawlessly under Wine. For the most part I create and triage related bug
>> reports, but recently I also started tinkering with code, speci
On 4/12/12 1:23 AM, Daniel Jeliński wrote:
Hello all,
I am trying to get Microsoft SQL Server Management Studio to work
flawlessly under Wine. For the most part I create and triage related bug
reports, but recently I also started tinkering with code, specifically
with comctl library, which I am m
Marcus, Alexey, thank you for your ideas. I just did several builds to
see how to make things work. Here's what I got:
make clean && make - does not work (the problem persists)
make distclean && ./configure && make - same as above
git clean -xdf && ./configure && make - this one finally worked.
I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
12.04.2012 12:23, Daniel Jeliński wrote:
> ... This time make clean && make depend && make did not help.
>
I had hit the problems like you describe several times while doing bisecting.
After a lot of trial and error testing I had finally come up with
On Thu, Apr 12, 2012 at 10:23:07AM +0200, Daniel Jeliński wrote:
> Hello all,
> I am trying to get Microsoft SQL Server Management Studio to work
> flawlessly under Wine. For the most part I create and triage related
> bug reports, but recently I also started tinkering with code,
> specifically wit
Hello all,
I am trying to get Microsoft SQL Server Management Studio to work
flawlessly under Wine. For the most part I create and triage related bug
reports, but recently I also started tinkering with code, specifically
with comctl library, which I am most familiar with.
Back on subject.
On Tue, 25 Oct 2011, Damjan Jovanovic wrote:
[...]
> Now the next question is, how to get the binaries to run on any distro? Or
> should I just compile on Ubuntu because most people run that (do they still,
> after Unity?)?
Compile on Debian Stable or even Debian OldStable, taking care to still
m
2011/10/18 André Hentschel
> Am 18.10.2011 10:45, schrieb Damjan Jovanovic:
> > This tool compiled all 35000 or so commits from Wine 1.0 to around 4th
> October 2011 in only 7 days, generating a Git repository of Wine binaries
> that's only 26 gigabytes in size. Regression t
ompressing full wine builds.
Joel
* Are binaries deterministic like this? or do they tend to be completely
scrambled?
On 18 October 2011 at 09:45 Damjan Jovanovic wrote:
> Hi
>
> Since the beginning, I've had issues with regression testing. Despite the
On Wed, Oct 19, 2011 at 04:18:50PM +0200, Frédéric Delanoy wrote:
> On Wed, Oct 19, 2011 at 15:50, Marcus Meissner wrote:
> > On Wed, Oct 19, 2011 at 02:42:29PM +0100, Ken Sharp wrote:
> >>
> >>
> >> On 19/10/11 13:43, Frédéric Delanoy wrote:
> >> >On Wed, Oct 19, 2011 at 14:08, Joel Holdsworth
On Wed, Oct 19, 2011 at 15:50, Marcus Meissner wrote:
> On Wed, Oct 19, 2011 at 02:42:29PM +0100, Ken Sharp wrote:
>>
>>
>> On 19/10/11 13:43, Frédéric Delanoy wrote:
>> >On Wed, Oct 19, 2011 at 14:08, Joel Holdsworth
>> >wrote:
>> >>Alternatively, have you considered doing a .tar.gz of every bu
On Wed, Oct 19, 2011 at 02:42:29PM +0100, Ken Sharp wrote:
>
>
> On 19/10/11 13:43, Frédéric Delanoy wrote:
> >On Wed, Oct 19, 2011 at 14:08, Joel Holdsworth
> >wrote:
> >>Alternatively, have you considered doing a .tar.gz of every build snapshot,
> >>and placing that on a server somewhere?
> >
On 19/10/11 13:43, Frédéric Delanoy wrote:
On Wed, Oct 19, 2011 at 14:08, Joel Holdsworth wrote:
Alternatively, have you considered doing a .tar.gz of every build snapshot,
and placing that on a server somewhere?
e.g. a folder full of 36def4af0ca85a1d0e66b5207056775bcb3b09ff.tar.gz files?
a 26Gb repository when most of the
> commits will be irrelevant.
Cloning a multi-gig repository is a no-go for many (most?) people,
especially for a regression testing they might do only once or
twice...
>
> Extra bonus points for doing a better job of compressing the small deltas
>
deltas
between binaries*, rather than compressing full wine builds.
Joel
* Are binaries deterministic like this? or do they tend to be completely
scrambled?
On 18 October 2011 at 09:45 Damjan Jovanovic wrote:
> Hi
>
> Since the beginning, I've had issues with regression te
2011/10/18 André Hentschel
> Am 18.10.2011 10:45, schrieb Damjan Jovanovic:
> > This tool compiled all 35000 or so commits from Wine 1.0 to around 4th
> October 2011 in only 7 days, generating a Git repository of Wine binaries
> that's only 26 gigabytes in size. Regression t
Am 18.10.2011 10:45, schrieb Damjan Jovanovic:
> This tool compiled all 35000 or so commits from Wine 1.0 to around 4th
> October 2011 in only 7 days, generating a Git repository of Wine binaries
> that's only 26 gigabytes in size. Regression testing with binaries is a
> pleasu
On Tue, Oct 18, 2011 at 10:26, Dmitry Timoshkov wrote:
> Austin English wrote:
>
>
>> > Reverting a patch in latest git is not always possible, instead it's
>> > a very useful test to revert the patch at the suspected regression point
>> > and see if that really helps.
>>
>> That still doesn't re
Austin English wrote:
> > Reverting a patch in latest git is not always possible, instead it's
> > a very useful test to revert the patch at the suspected regression point
> > and see if that really helps.
>
> That still doesn't require a full regression test, just:
> $ git checkout -f $SHA1SUM
On Tue, Oct 18, 2011 at 09:01, Dmitry Timoshkov wrote:
> Damjan Jovanovic wrote:
>> > Moreover, often users get asked 'does reverting commit ' help? Without
>> > performing a proper regression test it's impossible to asnwer that
>> > question.
>> >
>> >
>> Reverting a commit in the latest git
Damjan Jovanovic wrote:
> > Moreover, often users get asked 'does reverting commit ' help? Without
> > performing a proper regression test it's impossible to asnwer that
> > question.
> >
> >
> Reverting a commit in the latest git is just 1 round of
> patch+configure+make+run, and reverting to
On Tue, Oct 18, 2011 at 2:32 PM, Dmitry Timoshkov wrote:
> Henri Verbeet wrote:
>
> > On 18 October 2011 10:45, Damjan Jovanovic wrote:
> > > (especially during "reverse regression testing"), users find it too
> long and
> > > technical, and on
On Tue, Oct 18, 2011 at 13:42, Damjan Jovanovic wrote:
> If you are talking about using compiling with ccache instead of the binary
> repository, "configure" alone is > 40 seconds
configure -C option can speed it up a lot
Henri Verbeet wrote:
> On 18 October 2011 10:45, Damjan Jovanovic wrote:
> > (especially during "reverse regression testing"), users find it too long and
> > technical, and only a small minority of regressions are ever bisected. And
> Not true. Even for the regressi
On 18 October 2011 13:42, Damjan Jovanovic wrote:
> There's currently another 182 regressions that were closed "ABANDONED".
> Maybe if regression testing was easier and faster, people wouldn't abandon
> them?
>
Maybe. That's 182 closed ABANDONED, out of 2590
Exciting!
On 10/18/2011 01:45 AM, Damjan Jovanovic wrote:
> I haven't figured out how to make the binaries available to users. Few
> users can clone a 26 gigabyte repository, and even fewer places can
> serve that much to multiple users. Maybe Git can compress it further?
> The other idea I had is
On Tue, Oct 18, 2011 at 12:08 PM, Henri Verbeet wrote:
> On 18 October 2011 10:45, Damjan Jovanovic wrote:
> > (especially during "reverse regression testing"), users find it too long
> and
> > technical, and only a small minority of regressions are ever bisected.
&g
On 18 October 2011 10:45, Damjan Jovanovic wrote:
> (especially during "reverse regression testing"), users find it too long and
> technical, and only a small minority of regressions are ever bisected. And
Not true. Even for the regressions that are still open it's currentl
On Tue, Oct 18, 2011 at 10:45 AM, Damjan Jovanovic wrote:
> Hi
>
> Since the beginning, I've had issues with regression testing. Despite the
> fact it's very useful, it takes forever, it's easy to make a mistake
> (especially during "reverse regression te
Hi
Since the beginning, I've had issues with regression testing. Despite the
fact it's very useful, it takes forever, it's easy to make a mistake
(especially during "reverse regression testing"), users find it too long and
technical, and only a small minority of regressio
Austin English wrote:
> On Thu, Nov 19, 2009 at 9:41 AM, James Mckenzie
> wrote:
>
>>> From: Austin English
>>> Sent: Nov 19, 2009 10:31 AM
>>> To: James Mckenzie
>>> Cc: Wine Development Mailing List
>>> Subject: Re: Difficult
Austin English wrote:
>
>On Thu, Nov 19, 2009 at 9:41 AM, James Mckenzie
> wrote:
>>>From: Austin English
>>>Sent: Nov 19, 2009 10:31 AM
>>>To: James Mckenzie
>>>Cc: Wine Development Mailing List
>>>Subject: Re: Difficulties with Regression
On Thu, Nov 19, 2009 at 9:41 AM, James Mckenzie
wrote:
>>From: Austin English
>>Sent: Nov 19, 2009 10:31 AM
>>To: James Mckenzie
>>Cc: Wine Development Mailing List
>>Subject: Re: Difficulties with Regression Testing
>>
>>On Thu, Nov 19, 2009 at
>From: Austin English
>Sent: Nov 19, 2009 10:31 AM
>To: James Mckenzie
>Cc: Wine Development Mailing List
>Subject: Re: Difficulties with Regression Testing
>
>On Thu, Nov 19, 2009 at 8:51 AM, James Mckenzie
> wrote:
>> All:
>>
>> I've been running
e-1.1.11. I've been following
> the instructions on the Regression Testing Wiki page. I am on the fourth git
> bisect good and I run into two different problems:
>
> 1. The tools/Makefile.in file gets corrupted on the fourth git bisect good.
> This is unexpected as I am not awar
All:
I've been running regression tests to find a commit between wine-1.1.10 and
wine-1.1.11 that breaks the EM_FORMATRANGE patch or to discover what I need to
do to fix the patch to make it work with wine-1.1.11. I've been following the
instructions on the Regression Testing Wiki p
Erich Hoover wrote:
> On Sun, Aug 16, 2009 at 1:10 PM, James McKenzie
> mailto:jjmckenzi...@earthlink.net>> wrote:
>
> Looks like a patch to 0.9.61 broke the EM_FORMATRANGE patch that I was
> working on. I've received guidance from Dylan Smith on how to
> redo the
> patch and I wil
On Sun, Aug 16, 2009 at 2:10 PM, James
McKenzie wrote:
> Looks like a patch to 0.9.61 broke the EM_FORMATRANGE patch that I was
> working on. I've received guidance from Dylan Smith on how to redo the
> patch and I will once I get the old patch working with 1.0.
>
> Guidance on how to use git to r
On Sun, Aug 16, 2009 at 1:10 PM, James McKenzie
wrote:
> Looks like a patch to 0.9.61 broke the EM_FORMATRANGE patch that I was
> working on. I've received guidance from Dylan Smith on how to redo the
> patch and I will once I get the old patch working with 1.0.
>
> Guidance on how to use git to
Looks like a patch to 0.9.61 broke the EM_FORMATRANGE patch that I was
working on. I've received guidance from Dylan Smith on how to redo the
patch and I will once I get the old patch working with 1.0.
Guidance on how to use git to run bisect tests would be appreciated. Do
I get the commit numbe
On Fri, Apr 17, 2009 at 3:03 PM, Austin English wrote:
> On Fri, Apr 17, 2009 at 10:06 AM, Dan Kegel wrote:
>> It looks like you can build Abiword for Windows on Linux:
>> http://abiword.com/mailinglists/abiword-dev/2008/Jan/0021.html
>> Has anybody tried running the Abiword unit or regression te
On Fri, Apr 17, 2009 at 10:06 AM, Dan Kegel wrote:
> It looks like you can build Abiword for Windows on Linux:
> http://abiword.com/mailinglists/abiword-dev/2008/Jan/0021.html
> Has anybody tried running the Abiword unit or regression tests on Wine?
> http://www.abisource.com/wiki/Unit_Test
> http
On Fri, Apr 17, 2009 at 8:45 AM, Steven Edwards wrote:
> On Fri, Apr 17, 2009 at 11:06 AM, Dan Kegel wrote:
>> It looks like you can build Abiword for Windows on Linux:
>> http://abiword.com/mailinglists/abiword-dev/2008/Jan/0021.html
>
> It was winelibed already. We didn't look at the regression
On Fri, Apr 17, 2009 at 11:06 AM, Dan Kegel wrote:
> It looks like you can build Abiword for Windows on Linux:
> http://abiword.com/mailinglists/abiword-dev/2008/Jan/0021.html
It was winelibed already. We didn't look at the regression tests when
the winelib port was done however. It would be inte
It looks like you can build Abiword for Windows on Linux:
http://abiword.com/mailinglists/abiword-dev/2008/Jan/0021.html
Has anybody tried running the Abiword unit or regression tests on Wine?
http://www.abisource.com/wiki/Unit_Test
http://svn.abisource.com/abiword-testsuite/trunk/README
- Dan
On Dec 9, 2007 2:13 AM, Maarten Lankhorst <[EMAIL PROTECTED]> wrote:
> Try my hack:
> http://repo.or.cz/w/wine/hacks.git?a=commit;h=df41d984eafa372547b9aa5ae80a3adff5f8efb7
>
> You need to do autoconf after applying, then build with configure
> --disable-tests. I still wish alexandre would accept t
Hi Dan,
Dan Kegel schreef:
> Lots of the time in regression searches is spent
> compiling tests, but when you're only going to
> run the app that's breaking, that's not too useful.
> How does one disable compilation of conformance tests?
> I have this funny feeling Lei or Mikolaj did this
> recent
Lots of the time in regression searches is spent
compiling tests, but when you're only going to
run the app that's breaking, that's not too useful.
How does one disable compilation of conformance tests?
I have this funny feeling Lei or Mikolaj did this
recently, but I couldn't track it down.
James Hawkins wrote:
>
> On Nov 17, 2007, at 6:24 AM, Paul Vriens <[EMAIL PROTECTED]>
> wrote:
>
>> Hi,
>>
>> I've opened a bug (which if fixed now btw) and the regression
>> testing page at
>> http://wiki.winehq.org/RegressionTesting said
On Nov 17, 2007, at 6:24 AM, Paul Vriens <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> I've opened a bug (which if fixed now btw) and the regression
> testing page at
> http://wiki.winehq.org/RegressionTesting said "Also be sure to add
> the author of
> the pa
On Nov 17, 2007 3:44 PM, Dmitry Timoshkov <[EMAIL PROTECTED]> wrote:
>
> "Paul Vriens" <[EMAIL PROTECTED]> wrote:
>
> > I've opened a bug (which if fixed now btw) and the regression testing page
> > at
> > http://wiki.winehq.org/Regressi
"Paul Vriens" <[EMAIL PROTECTED]> wrote:
> I've opened a bug (which if fixed now btw) and the regression testing page at
> http://wiki.winehq.org/RegressionTesting said "Also be sure to add the author
> of
> the patch to the CC".
>
> So thi
Hi,
I've opened a bug (which if fixed now btw) and the regression testing page at
http://wiki.winehq.org/RegressionTesting said "Also be sure to add the author
of
the patch to the CC".
So this is what I did.
Should that line be removed from the wiki or do we generally want th
Martin wrote:
> Regarding your script interface, I think it should accept these parameters:
> * GIT_ID_1 - bisection start
> * GIT_ID_2 - bisection end
Sure, and/or dates and/or releases.
* PNGs - list of PNG files which describe "bug hit" cases;
No. The script should not invoke autohotkey, eit
Mikolaj Zalewski wrote:
> I now start to understand the structure of the tests. Do you know if
> there is a known regression in current Wine that I could use to try to
> do some scripting? If not I could use wine-0.9.43 as a reference with
> it's Win16 regression that affects the pptviewer and exc
Currently I'm trying to learn how cxtest works. But it looks like a
good idea to find sources of such regressions. I could help to write
such a script. I will check how my script fits into it.
Mikolaj Zalewski
Hi Mikolaj,
nice work!
I saw that you successfully ran cxtest.sh script on your machine and
submitted results. Currently, we are in process of setuping cxtest.sh
(tests Wine make test, Picasa, WinZip, WordViewer, ExcelViewer, PptViewer)
and 3dMark2000 tests nightly on our testing machines. Once w
Completely awesome, thank you!
Mikolaj Zalewski wrote:
> I wrote a small script that automates regression testing. It requires
> an Autohotkey script that tests the program and creates a file
> C:\Test-failed.txt if the test failed. The bash script will then do
> the regression
Hi Mikolaj,
see winebot - a console Wine package tool for Windows programs for how
to automate AutoHotkey installation for given wineprefix.
http://winebot.sandbox.cz
Regards
Vit
Mikolaj Zalewski wrote:
I wrote a small script that automates regression testing. It requires
an Autohotkey
I wrote a small script that automates regression testing. It requires
an Autohotkey script that tests the program and creates a file
C:\Test-failed.txt if the test failed. The bash script will then do the
regression testing. It starts with copying the source tree and
wineprefix so it should
I was able to do regression testing fine until I upgraded to Ubuntu 7.04.
Even the first bisect fails if I do a regression between current wine and
wine-20041019. I get the following error.
../../tools/winegcc/winegcc -B../../tools/winebuild -shared ./ddraw.spec
d3d_utils.o device_main.o
Saulius Krasuckas wrote:
> * On Sun, 13 May 2007, Louis Lenders wrote:
>
>>* EA Durbin hotmail.com> writes:
>>
>>>No, that doesn't help, i've tried distclean, git clean -x, the usual
>>>make clean, and nothing works. Regression testing seems bor
* On Sun, 13 May 2007, Louis Lenders wrote:
> * EA Durbin hotmail.com> writes:
> >
> > No, that doesn't help, i've tried distclean, git clean -x, the usual
> > make clean, and nothing works. Regression testing seems borked passed
> > two bisects.
>
&
EA Durbin hotmail.com> writes:
>
> No, that doesn't help, i've tried distclean, git clean -x, the usual make
> clean, and nothing works. Regression testing seems borked passed two
> bisects.
>
> >From: Louis Lenders yahoo.co.uk>
> >To: wine
No, that doesn't help, i've tried distclean, git clean -x, the usual make
clean, and nothing works. Regression testing seems borked passed two
bisects.
From: Louis Lenders <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: problems regression testing/compiling wine
Date:
E
> winegcc: gcc failed.
> make[2]: *** [winex11.drv.so] Error 2
> make[2]: Leaving directory `/home/eric/wine/dlls/winex11.drv'
> make[1]: *** [winex11.drv] Error 2
> make[1]: Leaving directory `/home/eric/wine/dlls'
> make: *** [dlls] Error 2
>
> _
EA Durbin schreef:
> I'm having problems regression testing between 0.9.15 and 0.9.37. On
> 3+ bisects I keep getting the following error and wine won't compile.
Most of the time when this happens you forget to do a make distclean
first. It is recommended to use ccache and do a
I'm having problems regression testing between 0.9.15 and 0.9.37. On 3+
bisects I keep getting the following error and wine won't compile.
/home/eric/wine/dlls/winex11.drv/palette.c:866: undefined reference to
`GDI_ReleaseObj'
palette.o:/home/eric/wine/dlls/winex11.drv/pale
I'm doing regression testing of Hogia software and have following
compilation
problem near wine-0.9.12:
../../tools/winegcc/winegcc -B../../tools/winebuild -shared ./ddraw.spec
d3d_utils.o device_main.o device_opengl.o direct3d_main.o direct3d_opengl.o
executebuffer.o li
On Mon, 2006-09-11 at 13:36 +0300, Saulius Krasuckas wrote:
> Any chances this patch gets into the webserver? :)
> http://marc.theaimsgroup.com/?l=wine-patches&m=115673906004873&w=2
This usually happens at release time...
--
Dimi Paun <[EMAIL PROTECTED]>
Lattica, Inc.
* On Mon, 28 Aug 2006, Mike McCormack wrote:
> Update regression testing procedure to use Git
Any chances this patch gets into the webserver? :)
http://marc.theaimsgroup.com/?l=wine-patches&m=115673906004873&w=2
On 8/1/06, Mitchell Mebane <[EMAIL PROTECTED]> wrote:
> It requires you to install autoit first. Autoit is a popular windows
> scripting tool which is even somewhat open source,
AutoHotKey (http://www.autohotkey.com/) is GPL and can do most of what
AutoIt can. You might give it a shot.
Thanks
Dan Kegel wrote:
It requires you to install autoit first. Autoit is a popular windows
scripting tool which is even somewhat open source,
see http://www.autoitscript.com/forum/index.php?showtopic=8389,
and in any case is free to use.
AutoHotKey (http://www.autohotkey.com/) is GPL and can do mos
It would be nice to have a simple way to verify that
wine can still install apps properly. Ideally this
test should run on either Windows or Wine unchanged,
and should verify the checksum of all installed files.
So I whipped up a demo of how to do this for winzip 10:
http://kegel.com/wine/test-w
recommend git for regression testing: http://wiki.winehq.org/GitWine
Didn't use it yet for regression testing but from the description it
sounds very easy. No need for the wine-cvs mailing list at all.
bye
michael
This is what i found:
cvs update -PAd -D "2006-01-06 15:52:12 CDT&q
wrong, or
something is really wrong with the regression testing
(documentation). at least it's very confusing!
Anyone can help?
BTW i did not have this trouble finding a regression
in another bug , where the patch was committed about a
half year ago.
__
* On Thu, 27 Oct 2005, Jonathan Ernst wrote:
> * Le mercredi 26 octobre 2005 à 16:49 +0200, Molle Bestefich a écrit :
> >
> > We actually /ask/ people to do regression testing, here f.x.:
> > http://www.winehq.org/site/docs/winedev-guide/x1344 to find a patch
> >
Jonathan Ernst wrote:
> If you remove the word processor I think you'll be under 30-40MB
> uncompressed with these ones:
>
> http://www.damnsmalllinux.org/
> http://www.zenwalk.org/staticpages/index.php?page=20050321031055330
>
> I didn't find a ready to use minidistro with gnome or/and kde as thes
Le vendredi 28 octobre 2005 à 06:21 +, Molle Bestefich a écrit :
> Jonathan Ernst wrote:
> > we could have VMWare installs of Wine and people could download
> > the VMWare image of any Wine release and play it for free using the
> > VMWare player !
>
> Excellent idea!!
>
> > I guess the downl
Jonathan Ernst wrote:
> > The approach is useless however, until these simple fixes are applied
> > to the tarballs (preferably through the versioning system).
>
> How do you decide what things have to be fixed in old tarballs ? Do you
> test each old tarballs every now and then and apply the corre
Le mercredi 26 octobre 2005 à 16:49 +0200, Molle Bestefich a écrit :
>
> We actually /ask/ people to do regression testing, here f.x.:
> http://www.winehq.org/site/docs/winedev-guide/x1344
> to find a patch that breaks things. Some developers has probably
> recommended that
On Wed, Oct 26, 2005 at 10:04:46AM +, Molle Bestefich wrote:
> I want to find which patch ruins an application.
> The application, according to one note, worked in 2003.
> I decide to try and see how it really runs with the 2003 version of
> Wine mentioned in the note.
The question now is: why
* On Wed, 26 Oct 2005, Jonathan Ernst wrote:
> * Le mercredi 26 octobre 2005 ?? 16:49 +0200, Molle Bestefich a ??crit :
> >
> > The approach is useless however, until these simple fixes are applied
> > to the tarballs (preferably through the versioning system).
>
> How do you decide what things
A lot of people have had this same problem in the past. Managing it is
a problem but there is a solution. Establish a policy that all
regression testing be done within the two latest versions. If it
doesn't run now and it did a year ago consider it a different problem.
This is the
Le mercredi 26 octobre 2005 à 16:49 +0200, Molle Bestefich a écrit :
>
> The approach is useless however, until these simple fixes are applied
> to the tarballs (preferably through the versioning system).
How do you decide what things have to be fixed in old tarballs ? Do you
test each old tarba
at else.
That's exactly what should be fixed.
Stuff that prevents older versions from running *at all*.
You know where the problems are;
I know where *some* of them are;
I'm willing to do volunteer work to rectify the situation for everyone
else that wants to do Wine regression testing, but
t the result is , as you say, regression testing is a PITA and
> as a result often gets skipped. The code base has certainly advanced a lot
> but every release seems to create as many problems as it solves.
>
> I managed to get an app working in Feb, luckily I tarballed the whole
&
Very good points. It seems a lot of this has been accepted over the years
on the basis that wine was alpha software and in that context , the past
is the past - get the new release etc.
It seems that the result is , as you say, regression testing is a PITA and
as a result often gets
I then spend several days pulling various releases, just trying to compile them.
They all fail miserably, because some fix required to compile
correctly with newer Linux versions is /missing/.
For example,
- any Wine before 2004-01-02 won't work because it won't compile
against newer ALSA vers
Regression testing with Wine is a pain in the butthole.
For very bad reasons: Stuff that is simple to fix, but haven't been.
I'd like to help improve that situation.
Example:
I want to find which patch ruins an application.
The application, according to one note, worked
On 8/30/05, Oliver Stieber <[EMAIL PROTECTED]> wrote:
> --- Jesse Allen <[EMAIL PROTECTED]> wrote:
> >
> > Well, I do have vertex shaders on. The problem I'm having with
> > battlefield is that the screen moves 25% of the screen off the top and
> > left sides and cutting off 25% of the bottom and
--- Jesse Allen <[EMAIL PROTECTED]> wrote:
> On 8/28/05, Stefan Dösinger <[EMAIL PROTECTED]> wrote:
> > Hi,
> > Just found the old mail, the following might be interesting:
> >
> > > Thanks, I've got the game running how Battlefront looked. Fonts are
> > > messed up, and some rendering problems
--- Jesse Allen <[EMAIL PROTECTED]> wrote:
> On 8/28/05, Ann & Jason Edmeades <[EMAIL PROTECTED]> wrote:
> > Out of interest, does reversing this patch fix the wc3 fonts - If I recall
> > correctly if was the glTranslate calls which originally made the wc3 fonts
> > look correct, and I noticed in
On 8/28/05, Ann & Jason Edmeades <[EMAIL PROTECTED]> wrote:
> Out of interest, does reversing this patch fix the wc3 fonts - If I recall
> correctly if was the glTranslate calls which originally made the wc3 fonts
> look correct, and I noticed in one of the patches Oliver changed them. He's
> proba
Out of interest, does reversing this patch fix the wc3 fonts - If I recall
correctly if was the glTranslate calls which originally made the wc3 fonts
look correct, and I noticed in one of the patches Oliver changed them. He's
probably right, but just in case its worth a test
Try changing
glTransla
On 8/28/05, Stefan Dösinger <[EMAIL PROTECTED]> wrote:
> Hi,
> Just found the old mail, the following might be interesting:
>
> > Thanks, I've got the game running how Battlefront looked. Fonts are
> > messed up, and some rendering problems, but it does run for me.
> > Battlefront has a crashing
Hi,
Just found the old mail, the following might be interesting:
> Thanks, I've got the game running how Battlefront looked. Fonts are
> messed up, and some rendering problems, but it does run for me.
> Battlefront has a crashing problem I know Oliver knows how to fix.
Battlefield renders really
On 7/16/05, Stefan Dösinger <[EMAIL PROTECTED]> wrote:
> Hi,
>
> > Thanks, I've got the game running how Battlefront looked. Fonts are
> > messed up, and some rendering problems, but it does run for me.
> > Battlefront has a crashing problem I know Oliver knows how to fix.
> Isn't Battlefront an
On 7/14/05, Stefan Dösinger <[EMAIL PROTECTED]> wrote:
> or remove the movies/ directory. A NoCD patch is needed for BF1942.exe,
> Mods/bf1942/mods.dll, Mods/Xpack1/Mod.dll and Mods/Xpack2/Mod.dll
> Then it should come up properly, with missing text(font problem?). Starting a
> game works for me,
1 - 100 of 112 matches
Mail list logo
