2009/5/5 Vitaliy Margolen :
> Mike Kaplinskiy wrote:
>> executable, so you would run it like:
>>
>> ./wine ./programs/winedbg/winedbg.exe.so
>
> './wine winedbg' will do the same.
Will that look-up in ./programs/winedbg before looking in $PREFIX/lib/wine/?
Mike Kaplinskiy wrote:
> executable, so you would run it like:
>
> ./wine ./programs/winedbg/winedbg.exe.so
'./wine winedbg' will do the same.
Vitaliy.
Roderick Colenbrander and I were talking about the severity levels on
irc the other day. We tried to outline the existing severity process
that seems to be in use (not what is neccesarily listed in bugzilla)
and came up with the following levels of bug severity:
* normal
* major (release level, e
> How about?
>
> ERR("didn't find any trusted root certificates. Are they installed?\n");
Done, and sent. Thanks for the suggestion and the help.
--Juan
On Mon, May 4, 2009 at 8:51 PM, Juan Lang wrote:
>> I'm a bit busy with other things, so time's a bit short. Would you
>> mind pointing me in the right direction for the best approach for
>> this? Or perhaps send a patch?
>
> Sure. How's the attached look to you? Should it be an ERR instead?
T
> I'm a bit busy with other things, so time's a bit short. Would you
> mind pointing me in the right direction for the best approach for
> this? Or perhaps send a patch?
Sure. How's the attached look to you? Should it be an ERR instead?
What text would you find more helpful?
--Juan
From 0fcce29
Ben Klein wrote:
> 2009/5/5 Mike Kaplinskiy :
>
>> On Mon, May 4, 2009 at 9:27 PM, Christopher Harvey
>> wrote:
>>
>>> I just built wine out of git.
>>> Ran this:
>>> wine-git $ find . -name winedbg
>>> ./programs/winedbg
>>>
>>> notice there is no winedbg program. The output there is a fo
2009/5/5 Mike Kaplinskiy :
> On Mon, May 4, 2009 at 9:27 PM, Christopher Harvey
> wrote:
>> I just built wine out of git.
>> Ran this:
>> wine-git $ find . -name winedbg
>> ./programs/winedbg
>>
>> notice there is no winedbg program. The output there is a folder only.
>> Where is the winedbg progr
On Mon, May 4, 2009 at 9:27 PM, Christopher Harvey
wrote:
> I just built wine out of git.
> Ran this:
> wine-git $ find . -name winedbg
> ./programs/winedbg
>
>
> notice there is no winedbg program. The output there is a folder only.
> Where is the winedbg program within the git tree?
>
>
>
I'm p
I just built wine out of git.
Ran this:
wine-git $ find . -name winedbg
./programs/winedbg
notice there is no winedbg program. The output there is a folder only.
Where is the winedbg program within the git tree?
On Mon, May 4, 2009 at 4:57 PM, Juan Lang wrote:
>> Alternatively, how about printing an error in crypt32 itself if no
>> trusted root certificates are found? That way applications get the
>> same benefit, not just the test suite? E.g., how we do for ntlm_auth
>> in secur32?
>
> That sounds like a
> Alternatively, how about printing an error in crypt32 itself if no
> trusted root certificates are found? That way applications get the
> same benefit, not just the test suite? E.g., how we do for ntlm_auth
> in secur32?
That sounds like a good approach.
--Juan
On Mon, May 4, 2009 at 2:43 PM, Austin English wrote:
> On Mon, May 4, 2009 at 12:19 PM, Juan Lang wrote:
>>> We have a similar warning already:
>>> http://source.winehq.org/git/wine.git/?a=blob;f=dlls/ws2_32/tests/sock.c#l2454
>>
>> That warning is appropriate, because it's testing IPv6, so the
On Mon, May 4, 2009 at 12:19 PM, Juan Lang wrote:
>> We have a similar warning already:
>> http://source.winehq.org/git/wine.git/?a=blob;f=dlls/ws2_32/tests/sock.c#l2454
>
> That warning is appropriate, because it's testing IPv6, so the warning
> applies in all cases. The reason I'm objecting in
I tried applying this patch, but the files are corrupt. It looks like
the UTF-8 encoding was not preserved. You should send the patch as an
attachment instead of inline.
-Newman
Łukasz Wojniłowicz wrote:
---
include/data.php |4 +
templates/pl/.cvsignore|
2009/5/4 James Mckenzie :
> Ben Klein wrote on May 4th:
>>
>>Final post from me.
>>
>>2009/5/5 Nicklas Börjesson :
>>> b) I thought that priority was developer priority and severity was
>>> severity for the users.
>>
>>Nope. Both for the benefit of developers, hence why they're both on bugzilla.
>>
James Mckenzie wrote:
One question: Does Bugzilla have a place for user's to place the Impact on
their ability to use a Windows program? This is much different than the
priority and severity fields.
Yes, here:
http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity
Ben Klein wrote on May 4th:
>
>Final post from me.
>
>2009/5/5 Nicklas Börjesson :
>> b) I thought that priority was developer priority and severity was
>> severity for the users.
>
>Nope. Both for the benefit of developers, hence why they're both on bugzilla.
>
>
One question: Does Bugzilla have
> We have a similar warning already:
> http://source.winehq.org/git/wine.git/?a=blob;f=dlls/ws2_32/tests/sock.c#l2454
That warning is appropriate, because it's testing IPv6, so the warning
applies in all cases. The reason I'm objecting in this case is that
the warning is printed for any failure,
On Mon, May 4, 2009 at 11:54 AM, Juan Lang wrote:
>> Would changing it to:
>> "CERT_TRUST_IS_UNTRUSTED_ROOT is expected if no trusted root
>> certificate is available."
>> be better?
>
> I don't think so. I think this test is a special case, because it
> depends on your system's configuration, wh
> OpenSolaris doesn't have any Verisign root certificates installed by
> default, which is the problem there.
Yep, I know.
> Would changing it to:
> "CERT_TRUST_IS_UNTRUSTED_ROOT is expected if no trusted root
> certificate is available."
> be better?
I don't think so. I think this test is a sp
On Mon, May 4, 2009 at 11:18 AM, Juan Lang wrote:
> Hi Austin,
>
>> The error is very cryptic...currently only shows up on OpenSolaris and
>> FreeBSD (if /usr/ports/security/ca_root_nss isn't installed). It
>> apparently also shows up on some Linux distributions that don't ship
>> OpenSSL with any
Hi Austin,
> The error is very cryptic...currently only shows up on OpenSolaris and
> FreeBSD (if /usr/ports/security/ca_root_nss isn't installed). It
> apparently also shows up on some Linux distributions that don't ship
> OpenSSL with any certificates.
While the error may be cryptic, it shows a
Hi, I just noticed commit efa96b30134261920ea12d8c324f9bef34b4.
This change is misleading:
- "Chain %d, element [%d,%d]: expected error %08x, got %08x\n",
+ "Chain %d, element [%d,%d]: expected error %08x, got %08x. %08x is "
+ "expected if no valid Verisign root certif
Final post from me.
2009/5/5 Nicklas Börjesson :
> b) I thought that priority was developer priority and severity was
> severity for the users.
Nope. Both for the benefit of developers, hence why they're both on bugzilla.
Guys, y'all are going in a circular argument. No need to cc wine-devel
on it anymore.
Let's work toward making normal the default level, and move on with our lives.
Any developer/user focus for bugzilla argument is WAY beyond beating a
dead horse.
--
-Austin
On Mon, May 04, 2009 at 10:12:04PM +1000, Ben Klein wrote:
> 2009/5/4 Ben Klein :
>> Then they disappear. There would be no way to search for metabugs, for
>> example, whereas at the moment you can search for Blockers. There's no
>> point in keeping metabugs if there's no
> There's no point in keep
2009/5/4 Ben Klein :
> Then they disappear. There would be no way to search for metabugs, for
> example, whereas at the moment you can search for Blockers. There's no
> point in keeping metabugs if there's no
SUSPENSE!
Lost a chunk of line there.
There's no point in keeping metabugs if there's n
2009/5/4 Nicklas Börjesson :
> As I wrote in my earlier post, Austin told me about the voting functionality,
> and If that is considered when priorities are made, it is likely to keep
> things pretty on track, making my proposed changes far less important.
> I still think my thoughts aren't that of
On Mon, 4 May 2009 00:31:09 -0500
Austin English wrote:
> >
> > But how would the restriction work? Not that I'm likely to ever submit
> > a Major or Critical bug report, but I know what they mean ;)
> >
>
> I don't know if bugzilla supports that or not.
>
> But changing the default to normal
Hello Dumitriu,
Dimitriu Petru wrote:
> I'm here again for the Romanian translation of Wine.
> I only want somebody to change in the translation "Proprietă?i pentru"
> with "Proprietăţi pentru" because it shows ugly in ReactOS.
That change is wrong as the correct glyph to use is "t with comma belo
André Hentschel wrote:
> suggested by Dimitriu Petru
> ---
> dlls/comdlg32/cdlg_Ro.rc |4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
This patch is wrong. The Romanian language uses "ț" aka "t with comma
below accent" and not "ţ" which is "t with cedilla".
bye
michael
On Sun, 2009-05-03 at 16:05 +0200, Roderick Colenbrander wrote:
> We do support some alpha support using XRender, can't you use this
> too? I think that's the general method for using alpha at the moment
> on X.
Yes and I'm using GdiAlphaBlend - for rendering, and I have fixes to use
it. It's what
33 matches
Mail list logo
