June 2010 - Wine-devel - list.winehq.org

Re: advapi32: add HKCU\Software\Classes and HKLM\Software\Classes merge tests
by testbot＠testbot.winehq.org 07 Jun '10

07 Jun '10

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=2508 Your paranoid android. === WNT4WSSP6 (32 bit registry) === registry.c:2003: Test failed: could not open user class key, error 2 registry.c:2009: Test failed: could not create guid key, error 6 === W2KPROSP4 (32 bit registry) === No test summary line found === WXPPROSP3 (32 bit registry) === Timeout

1 0

Re: [7/7] msvcrt/test: Add some simple _vsnwprintf_s tests. (try 2)
by Austin English 07 Jun '10

07 Jun '10

On Sun, Jun 6, 2010 at 11:36 PM, Alexander Scott-Johns <alexander.scott.johns(a)googlemail.com> wrote: > try 2: todo_wines removed since _vsnwprintf_s is fixed by patch 5. The todo_wine's need to be removed in the same patch in which they are fixed, otherwise, the tests will "fail". -- -Austin

2 2

Re: configure.ac: when checking for ALSA, look for snd_pcm_recover() instead of snd_pcm_hw_params_get_access() (try 2)
by Andrew Nguyen 06 Jun '10

06 Jun '10

I hate to nitpick once more, but there are a few things I noticed. My alsa-lib tells me: include/pcm.h:int snd_pcm_recover(snd_pcm_t *pcm, int err, int silent); Therefore, the statement "int ret = snd_pcm_recover(NULL, NULL, NULL);" is somewhat incorrect. Secondly, I think it should be sufficient to drop the AC_COMPILE_IFELSE macro entirely. The purpose in the original test was to distinguish between the version supplied in ALSA 0.9.x and ALSA 1.x, so, while I don't feel strongly about the matter either way, just checking for the existence of the function should be sufficient, as is done in other tests.

1 0

Re: configure.ac: when checking for ALSA, look for snd_pcm_recover() instead of snd_pcm_hw_params_get_access() (try 2)
by Marcus Meissner 06 Jun '10

06 Jun '10

On Sun, Jun 06, 2010 at 02:21:33PM -0500, Austin English wrote: > -- > -Austin > diff --git a/configure.ac b/configure.ac > index 21c0203..46ac100 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -1,4 +1,4 @@ > -dnl Process this file with autoconf to produce a configure script. > +/dnl Process this file with autoconf to produce a configure script. Bad. Ciao, Marcus

1 0

Running tests on wine
by GOUJON Alexandre 06 Jun '10

06 Jun '10

Hi, I would like to do some (typelib) tests on wine. So I followed the instructions at http://www.winehq.org/docs/winedev-guide/testing-wine ( cd dlls/oleaut32/tests/ ; rm typelib.ok && make typelib.ok in my case) but I have err's and fixme's whereas the output on wineTestBot is quite different (http://test.winehq.org/data/9aa9a1229f2195a8b3ac575645a10242ae6e9bc8/wine_n…) I tried WINETEST_DEBUG=1 make typelib.ok but it's the same output. Am I missing something ? Thanks

3 3

Re: [PATCH 3/3] shlwapi: Implement SHSetIniStringW
by testbot＠testbot.winehq.org 06 Jun '10

06 Jun '10

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=2490 Your paranoid android. === W2KPROSP4 (32 bit ordinal) === ordinal.c:604: Test failed: GetShellSecurityDescriptor should fail ordinal.c:627: Test failed: returned value is not valid SD No test summary line found === W7PRO (32 bit ordinal) === ordinal.c:1776: Test failed: got 25 ordinal.c:1826: Test failed: got 25 ordinal.c:1834: Test failed: got 25 ordinal.c:1842: Test failed: got 36, length 37 ordinal.c:1853: Test failed: got 39 === W7PROX64 (32 bit ordinal) === ordinal.c:1776: Test failed: got 22 ordinal.c:1826: Test failed: got 22 ordinal.c:1834: Test failed: got 22 ordinal.c:1842: Test failed: got 31, length 32 ordinal.c:1853: Test failed: got 34 === W7PROX64 (64 bit ordinal) === ordinal.c:1776: Test failed: got 22 ordinal.c:1826: Test failed: got 22 ordinal.c:1834: Test failed: got 22 ordinal.c:1842: Test failed: got 31, length 32 ordinal.c:1853: Test failed: got 34

1 0

Re: [PATCH 2/3] shlwapi: Implement SHGetIniStringW
by testbot＠testbot.winehq.org 06 Jun '10

06 Jun '10

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=2489 Your paranoid android. === W2KPROSP4 (32 bit ordinal) === ordinal.c:603: Test failed: GetShellSecurityDescriptor should fail ordinal.c:626: Test failed: returned value is not valid SD No test summary line found === W7PRO (32 bit ordinal) === ordinal.c:1775: Test failed: got 25 ordinal.c:1825: Test failed: got 25 ordinal.c:1833: Test failed: got 25 ordinal.c:1841: Test failed: got 36, length 37 ordinal.c:1852: Test failed: got 39 === W7PROX64 (32 bit ordinal) === ordinal.c:1775: Test failed: got 22 ordinal.c:1825: Test failed: got 22 ordinal.c:1833: Test failed: got 22 ordinal.c:1841: Test failed: got 31, length 32 ordinal.c:1852: Test failed: got 34 === W7PROX64 (64 bit ordinal) === ordinal.c:1775: Test failed: got 22 ordinal.c:1825: Test failed: got 22 ordinal.c:1833: Test failed: got 22 ordinal.c:1841: Test failed: got 31, length 32 ordinal.c:1852: Test failed: got 34

1 0

Re: [PATCH 1/3] shlwapi: Be less strict on which type of IShellFolder can be enumerated
by testbot＠testbot.winehq.org 06 Jun '10

06 Jun '10

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=2488 Your paranoid android. === W2KPROSP4 (32 bit ordinal) === ordinal.c:595: Test failed: GetShellSecurityDescriptor should fail ordinal.c:618: Test failed: returned value is not valid SD No test summary line found === W7PRO (32 bit ordinal) === ordinal.c:1767: Test failed: got 25 ordinal.c:1817: Test failed: got 25 ordinal.c:1825: Test failed: got 25 ordinal.c:1833: Test failed: got 36, length 37 ordinal.c:1844: Test failed: got 39 === W7PROX64 (32 bit ordinal) === ordinal.c:1767: Test failed: got 22 ordinal.c:1817: Test failed: got 22 ordinal.c:1825: Test failed: got 22 ordinal.c:1833: Test failed: got 31, length 32 ordinal.c:1844: Test failed: got 34 === W7PROX64 (64 bit ordinal) === ordinal.c:1767: Test failed: got 22 ordinal.c:1817: Test failed: got 22 ordinal.c:1825: Test failed: got 22 ordinal.c:1833: Test failed: got 31, length 32 ordinal.c:1844: Test failed: got 34

1 0

Re: appwiz: Add the Polish translation
by Sven Baars 06 Jun '10

06 Jun '10

Hey Łukasz, all your translations are written in UTF-8, but to actually use UTF-8, you also have to include a #pragma code_page(65001) on top of the file. In this case for example +#include "res.h" + +LANGUAGE LANG_POLISH, SUBLANG_DEFAULT + +#pragma code_page(65001) Atm, if you compile wine with this patch applied you see: sven(a)sven-desktop:~/wine-git/dlls/appwiz.cpl$ make LD_LIBRARY_PATH="../../libs/wine:$LD_LIBRARY_PATH" ../../tools/wrc/wrc --nostdinc -I. -I. -I../../include -I../../include -D__WINESRC__ -foPl.res Pl.rc Warning: string "Aby doda� program z dysku, p�yty CD-ROM lub dyskietki, kliknij przycisk Zainstaluj" seems to be UTF-8 but codepage 1250 is in use. Warning: string "To oprogramowanie mo�e by� usuni�te automatycznie. Aby usun�� program lub zmieni� jego zainstalowane komponenty, zaznacz go z listy i naci�nij Zmie�/Usu�." seems to be UTF-8 but codepage 1250 is in use. Warning: string "&Zmie�..." seems to be UTF-8 but codepage 1250 is in use. Warning: string "&Usu�..." seems to be UTF-8 but codepage 1250 is in use. Warning: string "Podane informacje mog� by� przydatne przy otrzymaniu pomocy technicznej dla %s:" seems to be UTF-8 but codepage 1250 is in use. Warning: string "Dodaj/Usu� programy" seems to be UTF-8 but codepage 1250 is in use. Warning: string "Pozwala na instalacj� nowego lub usuni�cie ju� istniej�cego oprogramowania z twojego komputera." seems to be UTF-8 but codepage 1250 is in use. Warning: string "Nie mo�na uruchomi� programu odinstalowuj�cego, '%s'. Czy chcesz usun�� wpis o tym programie z rejestru?" seems to be UTF-8 but codepage 1250 is in use. Warning: string "Nie okre�lone" seems to be UTF-8 but codepage 1250 is in use. Warning: string "&Usu�..." seems to be UTF-8 but codepage 1250 is in use. Warning: string "&Zmie�/Usu�..." seems to be UTF-8 but codepage 1250 is in use. You get warnings like this for every patch that you sent in. You can check it yourself by running "make depend" from the git directory and then "make" from the directory that contains the program or dll. This is at least how I got them. Regards, Sven P.S. You're not the only one making this mistake. I also made it the first time ;) Łukasz Wojniłowicz wrote: > --- > dlls/appwiz.cpl/Makefile.in | 1 + > dlls/appwiz.cpl/Pl.rc | 84 +++++++++++++++++++++++++++++++++++++++++++ > 2 files changed, 85 insertions(+), 0 deletions(-) > create mode 100644 dlls/appwiz.cpl/Pl.rc >

1 0

Release plans
by Alexandre Julliard 06 Jun '10

06 Jun '10

Folks, The 64-bit support is now more or less complete, and we have most of the fancy new icons, so it's time to think about the next stable release. Unless some major problems come up, 1.1.44 will be the last of the 1.1.x series. The next release will be 1.2-rc1, which will mark the beginning of the code freeze. This should result in a 1.2 final sometime in June. As usual the code freeze will become more and more drastic as we get closer to release, so if you have major changes to make, now is pretty much the last minute. I'd encourage everyone to look through the list of nominated 1.2 bugs, and also to check the regression reports for anything that might be in your area. We should strive to have as few regressions from 1.0 as possible, so regressions fixes will have priority during code freeze. And of course changes that don't impact the code, like translations or test fixes, can go in until quite late. -- Alexandre Julliard julliard(a)winehq.org

14 26