wine-patches
Hello, I sent a ~200KB patch to wine-patches last night and it disappeared without a trace. I'm wondering if it got lost or just went to moderation. Regards, Daniel PS.I just resent it, still no luck.
Re: wine-patches
On Thu, May 02, 2013 at 08:12:53AM +0200, Daniel Jeliński wrote: Hello, I sent a ~200KB patch to wine-patches last night and it disappeared without a trace. I'm wondering if it got lost or just went to moderation. Regards, Daniel PS.I just resent it, still no luck. If you are subscribed, the list size trigger will probably have happened and it is waiting for moderation. What is in the 200KB patch? If its sourcecode, it is too large even without looking at it. :) Ciao, Marcus
Re: Mail problems for wine-patches
I also unsubscribed and subscribed again to the wine-patches list. Any ideas? Has wine-patches a whitelist? We use an exim rule to screen out IP addresses flagged in the SORBS database. Unfortunately, the outbound mailer for your domain is listed; here is the exim error report: 212.227.17.11 is listed at dnsbl.sorbs.net (127.0.0.6: Currently Sending Spam See: http://www.sorbs.net/lookup.shtml?212.227.17.11) I have temporarily added *.web.de to the whitelist which should, in theory, allow these emails through. I'll allow Jeremy Newman to comment on what he thinks would be a better long term solution. (It looks like it's touch and go, because you go this email through somehow :-/). Cheers, Jeremy
Mail problems for wine-patches
I send several patches the last days with git and with the webmail interface from web.de, but nothing arrived at the wine-patches archive or the patches queue page. I also unsubscribed and subscribed again to the wine-patches list. Any ideas? Has wine-patches a whitelist? -- By by ... Detlef
wine-patches mailinglist problem
Hi, The wine-patches mailing list seems to stopped working. As you can see at http://www.winehq.org/pipermail/wine-patches/ there's no December 2012, but i sent a patch hours ago. I'm not aware of a mailing list memberships reminder from that list. -- Best Regards, André Hentschel
wine-patches
Hi,
I sent this email on wine-patch but... nothing.
Am I doing something wrong ?
Am I blacklisted ?
Vincent
---BeginMessage---
From bdf47b42a1560e9e097770f54d8f36a234f6d686 Mon Sep 17 00:00:00 2001
From: Vincent Hardy vincent.hardy...@gmail.com
Date: Mon, 24 Jan 2011 10:33:36 +0100
Subject: Loading PCSC-lite library
---
configure.ac |3 +++
dlls/winscard/winscard.c | 42 ++
2 files changed, 45 insertions(+), 0 deletions(-)
diff --git a/configure.ac b/configure.ac
index 4d049b6..c6a1714 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1638,6 +1638,9 @@ fi
dnl Check for libodbc
WINE_CHECK_SONAME(odbc,SQLConnect,,[AC_DEFINE_UNQUOTED(SONAME_LIBODBC,[libodbc.$LIBEXT])])
+dnl Check for libpcsclite
+WINE_CHECK_SONAME(pcsclite,SCardEstablishContext,,[AC_DEFINE_UNQUOTED(SONAME_LIBPCSCLITE,[libpcsclite.$LIBEXT])])
+
dnl Check for any sound system
if test x$ALSALIBS$COREAUDIO$NASLIBS$ESDLIBS$ac_cv_lib_soname_jack = x -a \
$ac_cv_header_sys_soundcard_h != yes -a \
diff --git a/dlls/winscard/winscard.c b/dlls/winscard/winscard.c
index 412299c..f2e4454 100644
--- a/dlls/winscard/winscard.c
+++ b/dlls/winscard/winscard.c
@@ -17,16 +17,22 @@
*/
#include config.h
+#include wine/port.h
#include stdarg.h
#include windef.h
#include winbase.h
#include wine/debug.h
+#include wine/library.h
#include winscard.h
#include winternl.h
+static BOOL PCSCLite_loadlib(void);
+static BOOL PCSCLite_loadfunctions(void);
+
WINE_DEFAULT_DEBUG_CHANNEL(winscard);
static HMODULE WINSCARD_hModule;
+static void *g_pcscliteHandle = NULL;
static HANDLE g_startedEvent = NULL;
const SCARD_IO_REQUEST g_rgSCardT0Pci = { SCARD_PROTOCOL_T0, 8 };
@@ -44,6 +50,10 @@ BOOL WINAPI DllMain (HINSTANCE hinstDLL, DWORD fdwReason, LPVOID lpvReserved)
{
DisableThreadLibraryCalls(hinstDLL);
WINSCARD_hModule = hinstDLL;
+
+if (PCSCLite_loadlib())
+PCSCLite_loadfunctions();
+
/* FIXME: for now, we act as if the pcsc daemon is always started */
g_startedEvent = CreateEventA(NULL,TRUE,TRUE,NULL);
break;
@@ -51,6 +61,13 @@ BOOL WINAPI DllMain (HINSTANCE hinstDLL, DWORD fdwReason, LPVOID lpvReserved)
case DLL_PROCESS_DETACH:
{
CloseHandle(g_startedEvent);
+
+if (g_pcscliteHandle)
+{
+wine_dlclose(g_pcscliteHandle, NULL, 0);
+g_pcscliteHandle = NULL;
+}
+
break;
}
}
@@ -58,6 +75,31 @@ BOOL WINAPI DllMain (HINSTANCE hinstDLL, DWORD fdwReason, LPVOID lpvReserved)
return TRUE;
}
+static BOOL PCSCLite_loadlib(void)
+{
+char error[256];
+
+if (g_pcscliteHandle)
+return TRUE;/* already loaded */
+else
+{
+g_pcscliteHandle = wine_dlopen(SONAME_LIBPCSCLITE, RTLD_LAZY | RTLD_GLOBAL, error, sizeof(error));
+if (g_pcscliteHandle)
+return TRUE;
+else
+{
+WARN(Failed to open library %s : %s\n, debugstr_a(SONAME_LIBPCSCLITE), error);
+return FALSE;
+}
+}
+}
+
+static BOOL PCSCLite_loadfunctions(void)
+{
+FIXME(%s\n, SONAME_LIBPCSCLITE);
+return TRUE;
+}
+
HANDLE WINAPI SCardAccessStartedEvent(void)
{
return g_startedEvent;
--
1.7.3.4
---End Message---
Re: wine-patches
Hi Vincent,
I sent this email on wine-patch but... nothing.
Am I doing something wrong ?
Sorry, I should have replied earlier. The patch doesn't appear to fix
anything, so it's unclear where you're going with it. It'd be better
to send a more complete patch series.
For example,
+static BOOL PCSCLite_loadfunctions(void)
+{
+FIXME(%s\n, SONAME_LIBPCSCLITE);
+return TRUE;
+}
this just adds spam to the console. Also, why do you return BOOL,
when the return value is never checked?
More nitpicking:
+static void *g_pcscliteHandle = NULL;
The initialization is unnecessary, statics are implicitly initialized to 0.
+if (g_pcscliteHandle)
+{
+wine_dlclose(g_pcscliteHandle, NULL, 0);
+g_pcscliteHandle = NULL;
The assignment of NULL is unneeded, the process is being unloaded.
+if (g_pcscliteHandle)
+return TRUE;/* already loaded */
+else
This check is unneeded, the function is only called at process load,
i.e. only once.
--Juan
Spotted on Reddit's frontpage [ wine-patches the black hole of code? ]
Spotted on Reddit's frontpage wine-patches the black hole of code? http://kazade.livejournal.com/2451.html Access Yahoo!7 Mail on your mobile. Anytime. Anywhere. Show me how: http://au.mobile.yahoo.com/mail
Re: Spotted on Reddit's frontpage [ wine-patches the black hole of code? ]
On Mon, Jul 27, 2009 at 8:09 AM, nnsaturn_syst...@yahoo.com wrote: Spotted on Reddit's frontpage wine-patches the black hole of code? http://kazade.livejournal.com/2451.html Access Yahoo!7 Mail on your mobile. Anytime. Anywhere. Show me how: http://au.mobile.yahoo.com/mail I used to think it was difficult to get a patch into Wine - until I started sending patches to some other open source projects. It never took more than 2 days for a Wine patch I sent it to get accepted. By comparison, I submitted a modest OpenJDK patch (http://bugs.openjdk.java.net/show_bug.cgi?id=100041) around May 2008, I've had to completely rewrite it once, it's on the 5th revision (excluding 2 more revisions from before their bugzilla was opened), and it's still not accepted. IRC is a dream compared to weeks/months of waiting for your patch sponsor to reply on bugzilla. Think Wine doesn't accept patches easily, and it's hard to get feedback? Think again. Damjan Jovanovic
Re: Spotted on Reddit's frontpage [ wine-patches the black hole of code? ]
Damjan Jovanovic damjan@gmail.com wrote: Think Wine doesn't accept patches easily, and it's hard to get feedback? Think again. I think it's not worth an effort to take seriously one post of apparently clueless anonymous user and a forward to wine-devel of another anonymous user. We've been through this maintenance/ governance subject before, no need to iterate. -- Dmitry.
Re: Spotted on Reddit's frontpage [ wine-patches the black hole of code? ]
Dmitry Timoshkov wrote: Damjan Jovanovic damjan@gmail.com wrote: Think Wine doesn't accept patches easily, and it's hard to get feedback? Think again. I think it's not worth an effort to take seriously one post of apparently clueless anonymous user and a forward to wine-devel of another anonymous user. We've been through this maintenance/ governance subject before, no need to iterate. I'd rather have the opposite problem. We should be inundated with praise for how easy and fun it is to become a Wine developer. Instead of worries about silently dropped patches, contributors should be complaining about how they got too much help. First the patchwatcher tool told them their first patch broke the test suite on a platform they didn't think of. Then their second patch, which passed, was put on a landing page where another developer could click a button and send a review. Then their third patch sat in the queue for two weeks because Alexandre was on vacation, so patchwatcher again sent them an email suggesting they check in on IRC to see if there were other issues. It's only a vision now, but that's the kind of problem with sending patches I'd like us to be dismissing as nonsense. I'll be working on getting patchwatcher back online this week and Luke (the author of that article) already has a prototype of the patch tracking system he mentions. Thanks, Scott Ritchie
Re: Spotted on Reddit's frontpage [ wine-patches the black hole of code? ]
On Monday 27 July 2009 13:08:44 Scott Ritchie wrote: First the patchwatcher tool told them their first patch broke the test suite on a platform they didn't think of. Probably doable, once we get patchwatcher back up. Then their second patch, which passed, was put on a landing page where another developer could click a button and send a review. Android has a git-compatible code review tool called gerrit, iirc. It looks a bit painful to set up, so I've never given it a try myself. But even if we had such a tool I'm not yet convinced it would help much. There's too many areas where you're not scratching anybody else's itch. And if it doesn't have emacs integration, Alexandre won't use it ;). Of course I'm happy to be prooven wrong on this. Cheers, Kai -- Kai Blin WorldForge developer http://www.worldforge.org/ Wine developerhttp://wiki.winehq.org/KaiBlin Samba team member http://www.samba.org/samba/team/ -- Will code for cotton. signature.asc Description: This is a digitally signed message part.
Re: wine-patches Digest, Vol 47, Issue 188
2009/6/23 Pavel Procházka pavelvonlost...@seznam.cz hello I want to ask you if i should resend the patch in correct form, sorry for the last patch. Thank you for answer do not send normal messages to wine-patches. send those to wine-devel, wine-patches is for messages with attached patches only. yes, you should resend your patches with the corrections and suggestions stefan and james gave you. put (resend) or (try 2) on the subject. you should avoid resending more than 2 or 3 times a week, unless you've cleared with julliard. regards.
Re: wine-patches Digest, Vol 47, Issue 40
Message: 2 Date: Thu, 04 Jun 2009 22:37:48 +0200 From: Piotr Caban piotr.ca...@gmail.com Subject: jscript: Added Date_getFullYear and Date_getUTCFullYear implementation (3/7) To: wine-patc...@winehq.org Message-ID: 4a28309c.9000...@gmail.com Content-Type: text/plain; charset=utf-8 --- dlls/jscript/date.c | 73 ++-- dlls/jscript/tests/api.js |9 + 2 files changed, 78 insertions(+), 4 deletions(-) Whats wrong with this patch? All the date expressions (e.g. day_from_year) are copied from ECMA-262 standard specification. Because of the date range it can be keep in double without error. Piotr Caban
Re: wine-patches Digest, Vol 47, Issue 40
Piotr Caban piotr.ca...@gmail.com writes: Whats wrong with this patch? All the date expressions (e.g. day_from_year) are copied from ECMA-262 standard specification. Because of the date range it can be keep in double without error. Look a bit closer at your constant definitions... -- Alexandre Julliard julli...@winehq.org
Running a conformance test on windows before submitting to wine-patches.
I would like to submit the following AcceptEx conformance test to
wine-patches, but I don't have a windows box (and i haven't got qemu
setup(correctly) yet). Would someone run this and let me know how/if
it failes (or succeeds... it should succeed).
Thanks
- Scott
From 00a1b8b04f99cfae3b77f6362068dbeba78d581e Mon Sep 17 00:00:00 2001
From: Scott Lindeneau [EMAIL PROTECTED]
Date: Thu, 21 Aug 2008 02:14:49 +0900
Subject: [PATCH] AcceptEx Conformance Tests. - Simple
---
dlls/ws2_32/tests/sock.c | 204 --
1 files changed, 198 insertions(+), 6 deletions(-)
diff --git a/dlls/ws2_32/tests/sock.c b/dlls/ws2_32/tests/sock.c
index e2d2162..310e32f 100644
--- a/dlls/ws2_32/tests/sock.c
+++ b/dlls/ws2_32/tests/sock.c
@@ -20,7 +20,7 @@
*/
#include stdarg.h
-
+#include stdio.h
#include windef.h
#include winbase.h
#include winsock2.h
@@ -31,7 +31,7 @@
#include winerror.h
#define MAX_CLIENTS 4 /* Max number of clients */
-#define NUM_TESTS 4 /* Number of tests performed */
+#define NUM_TESTS 5 /* Number of tests performed */
#define FIRST_CHAR 'A' /* First character in transferred pattern */
#define BIND_SLEEP 10 /* seconds to wait between attempts to bind() */
#define BIND_TRIES 6 /* Number of bind() attempts */
@@ -54,7 +54,6 @@
ok ( cond tmp, msg, GetCurrentThreadId(), err); \
} while (0);
-
/ Structs and typedefs ***/
typedef struct thread_info
@@ -583,6 +582,181 @@ static VOID WINAPI select_server ( server_params *par )
server_stop ();
}
+/*
+ * overlapped_server: A (partially)non-blocking server built on acceptex.
+ */
+static VOID WINAPI overlapped_server ( server_params *par )
+{
+test_params *gen = par-general;
+server_memory *mem;
+ HANDLE hCompPort;
+ WSAEVENT peerSockets[MAX_CLIENTS];
+ WSAOVERLAPPED overLap[MAX_CLIENTS];
+ LPSOCKADDR addrAddr;
+ LPSOCKADDR addrPeer;
+ int outBuf[MAX_CLIENTS];
+ int event_i;
+ int size;
+int n_expected = gen-n_chunks * gen-chunk_size, i,
+id = GetCurrentThreadId(), n_connections = 0, n_sent, n_recvd,
+n_set, delta, n_ready;
+char *p;
+fd_set fds_recv, fds_send, fds_openrecv, fds_opensend;
+
+trace ( overlapped_server (%x) starting\n, id );
+
+set_so_opentype ( TRUE ); /* overlapped server */
+ par-sock_flags = WSA_FLAG_OVERLAPPED;
+server_start ( par );
+mem = TlsGetValue ( tls );
+
+ /*Create completion port*/
+ hCompPort = CreateIoCompletionPort( INVALID_HANDLE_VALUE, NULL,
(u_long)0, 0 );
+ ok( hCompPort != NULL, CreateIoCompletionPort failed\n );
+ /*Associate completion port with listening port*/
+ ok( CreateIoCompletionPort((HANDLE)mem-s, hCompPort, (u_long)0, 0) !=
NULL, CreateIoCompletionPort failed\n );
+
+wsa_ok ( set_blocking ( mem-s, FALSE ), 0 ==, overlapped_server (%x):
failed to set blocking mode: %d\n );
+wsa_ok ( listen ( mem-s, SOMAXCONN ), 0 ==, overlapped_server (%x):
listen failed: %d\n );
+
+ /*empty overlapped structures*/
+ memset( overLap,0,sizeof(WSAOVERLAPPED) * MAX_CLIENTS );
+ for ( i = 0; i min ( gen-n_clients, MAX_CLIENTS ); i++ )
+ {
+ /*Create accepting socket*/
+ mem-sock[i].s = WSASocketA ( AF_INET, gen-sock_type,
gen-sock_prot,
+ NULL, 0, par-sock_flags );
+ /*Create event to wait on*/
+ peerSockets[i] = WSACreateEvent();
+ overLap[i].hEvent = peerSockets[i];
+ /*Call AcceptEx*/
+ AcceptEx( mem-s, /*listen socket*/
+ mem-sock[i].s, /*accept socket*/
+ mem-sock[i].buf, /*socket buffer*/
+ 0, /*don't recieve any data*/
+ sizeof(struct sockaddr_in) + 16, /*size
of address*/
+ sizeof(struct sockaddr_in) + 16, /*size
of address*/
+ (LPDWORD)(outBuf + i), /*Pointer to an
int that returns the number of bytes recieved*/
+ (overLap + i) ); /*Overlapped data
structure */
+ ok(WSAGetLastError() == ERROR_IO_PENDING, AcceptEx returned
unexpected value\n);
+ /*Associeate accepting socket with completionport*/
+ ok( CreateIoCompletionPort((HANDLE)mem-sock[i].s, hCompPort,
(u_long)0, 0) != NULL , CreateIoCompletionPort failed\n );
+ }
+
+trace ( overlapped_server (%x) ready\n, id );
+SetEvent ( server_ready ); /* notify clients */
+
+FD_ZERO ( fds_openrecv );
+FD_ZERO ( fds_recv );
+FD_ZERO ( fds_send );
+FD_ZERO ( fds_opensend );
+
+FD_SET ( mem-s, fds_openrecv );
+ event_i = WSA_WAIT_TIMEOUT;
+while(1)
+{
+ int bytes
Re: Running a conformance test on windows before submitting to wine-patches.
On Wed, Aug 20, 2008 at 12:23 PM, Scott Lindeneau [EMAIL PROTECTED] wrote: I would like to submit the following AcceptEx conformance test to wine-patches, but I don't have a windows box (and i haven't got qemu setup(correctly) yet). Would someone run this and let me know how/if it failes (or succeeds... it should succeed). Thanks - Scott Does it depend on another patch: [EMAIL PROTECTED]:~/wine-git/dlls/ws2_32/tests$ make crosstest i586-mingw32msvc-gcc protocol.cross.o sock.cross.o testlist.cross.o -o ws2_32_crosstest.exe -L../../../dlls -L../../../dlls/ws2_32 -L../../../dlls/kernel32 -lws2_32 -lkernel32 sock.cross.o: In function `overlapped_server':/home/austin/wine-git/dlls/ws2_32/tests/sock.c:633: undefined reference to [EMAIL PROTECTED]' :/home/austin/wine-git/dlls/ws2_32/tests/sock.c:677: undefined reference to [EMAIL PROTECTED]' collect2: ld returned 1 exit status make: *** [ws2_32_crosstest.exe] Error 1
Re: Running a conformance test on windows before submitting to wine-patches.
It did. I wrote the test using a different set of patches which let it compile with wine. I will look up how to cross compile it and do that next time. Sorry for the inconvenience. On Thu, Aug 21, 2008 at 2:36 AM, Austin English [EMAIL PROTECTED] wrote: On Wed, Aug 20, 2008 at 12:34 PM, Scott Lindeneau [EMAIL PROTECTED] wrote: I don't think so? I've never written a conformance test before. I did implement AcceptEx in wine, but it shouldn't need that patch to compile for windows should it? Or maybe I need to load it into memory instead of just calling it first... Terribly sorry. I'm making myself a nuisance. I will try writing it using the windows WSAIoctl call to load it into memory first. MSDN does say I need that. -Scott On Thu, Aug 21, 2008 at 2:29 AM, Austin English [EMAIL PROTECTED] wrote: On Wed, Aug 20, 2008 at 12:23 PM, Scott Lindeneau [EMAIL PROTECTED] wrote: I would like to submit the following AcceptEx conformance test to wine-patches, but I don't have a windows box (and i haven't got qemu setup(correctly) yet). Would someone run this and let me know how/if it failes (or succeeds... it should succeed). Thanks - Scott Does it depend on another patch: [EMAIL PROTECTED]:~/wine-git/dlls/ws2_32/tests$ make crosstest i586-mingw32msvc-gcc protocol.cross.o sock.cross.o testlist.cross.o -o ws2_32_crosstest.exe -L../../../dlls -L../../../dlls/ws2_32 -L../../../dlls/kernel32 -lws2_32 -lkernel32 sock.cross.o: In function `overlapped_server':/home/austin/wine-git/dlls/ws2_32/tests/sock.c:633: undefined reference to [EMAIL PROTECTED]' :/home/austin/wine-git/dlls/ws2_32/tests/sock.c:677: undefined reference to [EMAIL PROTECTED]' collect2: ld returned 1 exit status make: *** [ws2_32_crosstest.exe] Error 1 Please bottom post on wine-devel. In the future, sending a compiled exe is helpful, saves time. Does it even past make test for you? [EMAIL PROTECTED]:~/wine-git/dlls/ws2_32/tests$ make test ccache gcc -c -I. -I. -I../../../include -I../../../include -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2 -o protocol.o protocol.c ccache gcc -c -I. -I. -I../../../include -I../../../include -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2 -o sock.o sock.c sock.c: In function âoverlapped_serverâ: sock.c:670: warning: pointer targets in passing argument 3 of âGetOverlappedResultâ differ in signedness ccache gcc -c -I. -I. -I../../../include -I../../../include -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2 -o testlist.o testlist.c ../../../tools/winegcc/winegcc -B../../../tools/winebuild -mconsole protocol.o sock.otestlist.o -o ws2_32_test.exe.so ../../../libs/port/libwine_port.a -lws2_32 -lkernel32 sock.o: In function `overlapped_server': /home/austin/wine-git/dlls/ws2_32/tests/sock.c:633: undefined reference to `AcceptEx' /home/austin/wine-git/dlls/ws2_32/tests/sock.c:677: undefined reference to `GetAcceptExSockaddrs' collect2: ld returned 1 exit status winegcc: ccache failed make: *** [ws2_32_test.exe.so] Error 2
Re: Running a conformance test on windows before submitting to wine-patches.
Sorry about not knowing how to cross compile before. Here is the
patch(gmail doesn't let me attach exe's... I will look into this).
Please try this. Tell me if I am doing something wrong (again).
-Scott
From 3a7d296ed2184fd22b70d96880afc86927801ab7 Mon Sep 17 00:00:00 2001
From: Scott Lindeneau [EMAIL PROTECTED]
Date: Thu, 21 Aug 2008 04:21:22 +0900
Subject: [PATCH] AcceptEx Conformance tests.
---
dlls/ws2_32/tests/sock.c | 238 -
1 files changed, 232 insertions(+), 6 deletions(-)
diff --git a/dlls/ws2_32/tests/sock.c b/dlls/ws2_32/tests/sock.c
index e2d2162..cf96a63 100644
--- a/dlls/ws2_32/tests/sock.c
+++ b/dlls/ws2_32/tests/sock.c
@@ -20,7 +20,7 @@
*/
#include stdarg.h
-
+#include stdio.h
#include windef.h
#include winbase.h
#include winsock2.h
@@ -31,7 +31,7 @@
#include winerror.h
#define MAX_CLIENTS 4 /* Max number of clients */
-#define NUM_TESTS 4 /* Number of tests performed */
+#define NUM_TESTS 5 /* Number of tests performed */
#define FIRST_CHAR 'A' /* First character in transferred pattern */
#define BIND_SLEEP 10 /* seconds to wait between attempts to bind() */
#define BIND_TRIES 6 /* Number of bind() attempts */
@@ -54,7 +54,6 @@
ok ( cond tmp, msg, GetCurrentThreadId(), err); \
} while (0);
-
/ Structs and typedefs ***/
typedef struct thread_info
@@ -583,6 +582,215 @@ static VOID WINAPI select_server ( server_params *par )
server_stop ();
}
+/*
+ * overlapped_server: A (partially)non-blocking server built on acceptex.
+ */
+static VOID WINAPI overlapped_server ( server_params *par )
+{
+test_params *gen = par-general;
+server_memory *mem;
+ HANDLE hCompPort;
+ WSAEVENT peerSockets[MAX_CLIENTS];
+ WSAOVERLAPPED overLap[MAX_CLIENTS];
+ LPSOCKADDR addrAddr;
+ LPSOCKADDR addrPeer;
+ LPFN_ACCEPTEX lpfnAcceptEx = NULL;
+ GUID GuidAcceptEx = WSAID_ACCEPTEX;
+ LPFN_GETACCEPTEXSOCKADDRS lpfnGetAcceptExSockaddrs = NULL;
+ GUID GuidGetAccpetExSockaddrs = WSAID_GETACCEPTEXSOCKADDRS;
+ int dummy,dummy2;
+ int outBuf[MAX_CLIENTS];
+ int event_i;
+ int size;
+int n_expected = gen-n_chunks * gen-chunk_size, i,
+id = GetCurrentThreadId(), n_connections = 0, n_sent, n_recvd,
+n_set, delta, n_ready;
+char *p;
+fd_set fds_recv, fds_send, fds_openrecv, fds_opensend;
+
+trace ( overlapped_server (%x) starting\n, id );
+
+set_so_opentype ( TRUE ); /* overlapped server */
+ par-sock_flags = WSA_FLAG_OVERLAPPED;
+server_start ( par );
+mem = TlsGetValue ( tls );
+
+ /*Create completion port*/
+ hCompPort = CreateIoCompletionPort( INVALID_HANDLE_VALUE, NULL,
(u_long)0, 0 );
+ ok( hCompPort != NULL, CreateIoCompletionPort failed\n );
+ /*Associate completion port with listening port*/
+ ok( CreateIoCompletionPort((HANDLE)mem-s, hCompPort, (u_long)0, 0) !=
NULL, CreateIoCompletionPort failed\n );
+
+wsa_ok ( set_blocking ( mem-s, FALSE ), 0 ==, overlapped_server (%x):
failed to set blocking mode: %d\n );
+wsa_ok ( listen ( mem-s, SOMAXCONN ), 0 ==, overlapped_server (%x):
listen failed: %d\n );
+
+ WSAIoctl(mem-s,
+ SIO_GET_EXTENSION_FUNCTION_POINTER,
+ GuidAcceptEx,
+ sizeof(GuidAcceptEx),
+ lpfnAcceptEx,
+ sizeof(lpfnAcceptEx),
+ dummy,
+ NULL,
+ NULL);
+ wsa_ok(lpfnAcceptEx, NULL !=, overlapped_server (%x): WSAIoctl failed
loading AcceptEx: %d\n);
+ WSAIoctl(mem-s,
+ SIO_GET_EXTENSION_FUNCTION_POINTER,
+ GuidGetAccpetExSockaddrs,
+ sizeof(GuidGetAccpetExSockaddrs),
+ lpfnGetAcceptExSockaddrs,
+ sizeof(lpfnGetAcceptExSockaddrs),
+ dummy2,
+ NULL,
+ NULL);
+ wsa_ok(lpfnGetAcceptExSockaddrs, NULL !=, overlapped_server (%x):
WSAIoctl failed loading GetAcceptExSockaddrs: %d\n);
+
+ if(lpfnGetAcceptExSockaddrs == NULL || lpfnAcceptEx == NULL){
+ trace ( overlapped_server (%x) failing stop\n, id );
+ server_stop();
+ }
+
+
+ /*empty overlapped structures*/
+ memset( overLap,0,sizeof(WSAOVERLAPPED) * MAX_CLIENTS );
+ for ( i = 0; i min ( gen-n_clients, MAX_CLIENTS ); i++ )
+ {
+ /*Create accepting socket*/
+ mem-sock[i].s = WSASocketA ( AF_INET, gen-sock_type,
gen-sock_prot,
+ NULL, 0, par-sock_flags );
+ /*Create event to wait on*/
+ peerSockets[i] = WSACreateEvent();
+ overLap[i].hEvent = peerSockets[i];
+ /*Call AcceptEx*/
+
+ lpfnAcceptEx( mem-s, /*listen socket*/
+ mem-sock[i].s, /*accept socket*/
+ mem-sock[i].buf, /*socket buffer*/
+
Re: Running a conformance test on windows before submitting to wine-patches.
On Wed, Aug 20, 2008 at 2:25 PM, Scott Lindeneau [EMAIL PROTECTED] wrote: Sorry about not knowing how to cross compile before. Here is the patch(gmail doesn't let me attach exe's... I will look into this). Please try this. Tell me if I am doing something wrong (again). -Scott Got some warnings, might check into that. [EMAIL PROTECTED]:~/wine-git/dlls/ws2_32/tests$ make crosstest i586-mingw32msvc-gcc -c -I. -I. -I../../../include -I../../../include -g -O2 -o protocol.cross.o protocol.c i586-mingw32msvc-gcc -c -I. -I. -I../../../include -I../../../include -g -O2 -o sock.cross.o sock.c sock.c: In function `overlapped_server': sock.c:636: warning: assignment makes integer from pointer without a cast sock.c:636: warning: comparison between pointer and integer sock.c:636: warning: comparison between pointer and integer sock.c:646: warning: assignment makes integer from pointer without a cast sock.c:646: warning: comparison between pointer and integer sock.c:646: warning: comparison between pointer and integer ../../../tools/make_ctests -o testlist.c protocol.c sock.c i586-mingw32msvc-gcc -c -I. -I. -I../../../include -I../../../include -g -O2 -o testlist.cross.o testlist.c i586-mingw32msvc-gcc protocol.cross.o sock.cross.o testlist.cross.o -o ws2_32_crosstest.exe -L../../../dlls -L../../../dlls/ws2_32 -L../../../dlls/kernel32 -lws2_32 -lkernel32 Passes for me in 2k (That test failure you see was already there, but it's a different function anyway). -Austin sock.c:2450: STARTING TEST 0 sock.c:408: simple_server (1b8) starting sock.c:417: simple_server (1b8) ready sock.c:422: simple_server (1b8): waiting for client sock.c:807: simple_client (148): starting sock.c:810: simple_client (148): server ready sock.c:807: simple_client (1c4): starting sock.c:810: simple_client (1c4): server ready sock.c:821: simple_client (148) connected sock.c:422: simple_server (1b8): waiting for client sock.c:840: simple_client (148) exiting sock.c:821: simple_client (1c4) connected sock.c:450: simple_server (1b8) exiting sock.c:840: simple_client (1c4) exiting sock.c:2452: TEST 0 COMPLETE sock.c:2450: STARTING TEST 1 sock.c:408: simple_server (480) starting sock.c:417: simple_server (480) ready sock.c:422: simple_server (480): waiting for client sock.c:928: event_client (5c8): starting sock.c:928: event_client (5e4): starting sock.c:930: event_client (5c8): server ready sock.c:950: event_client (5c8) connected sock.c:988: event_client (5c8): all data sent - shutdown sock.c:422: simple_server (480): waiting for client sock.c:1009: event_client (5c8): all data received sock.c:1021: event_client (5c8): close event sock.c:1039: event_client (5c8) exiting sock.c:930: event_client (5e4): server ready sock.c:950: event_client (5e4) connected sock.c:988: event_client (5e4): all data sent - shutdown sock.c:450: simple_server (480) exiting sock.c:1009: event_client (5e4): all data received sock.c:1021: event_client (5e4): close event sock.c:1039: event_client (5e4) exiting sock.c:2452: TEST 1 COMPLETE sock.c:2450: STARTING TEST 2 sock.c:468: select_server (5d4) starting sock.c:477: select_server (5d4) ready sock.c:807: simple_client (1fc): starting sock.c:810: simple_client (1fc): server ready sock.c:807: simple_client (13c): starting sock.c:810: simple_client (13c): server ready sock.c:501: select_server (5d4): accepting client connection sock.c:821: simple_client (1fc) connected sock.c:501: select_server (5d4): accepting client connection sock.c:821: simple_client (13c) connected sock.c:840: simple_client (1fc) exiting sock.c:840: simple_client (13c) exiting sock.c:581: select_server (5d4) exiting sock.c:2452: TEST 2 COMPLETE sock.c:2450: STARTING TEST 3 sock.c:408: simple_server (424) starting sock.c:417: simple_server (424) ready sock.c:422: simple_server (424): waiting for client sock.c:857: simple_client (1f8): starting sock.c:860: simple_client (1f8): server ready sock.c:857: simple_client (5d8): starting sock.c:860: simple_client (5d8): server ready sock.c:872: simple_client (1f8) connected sock.c:422: simple_server (424): waiting for client sock.c:910: simple_client (1f8) exiting sock.c:872: simple_client (5d8) connected sock.c:450: simple_server (424) exiting sock.c:910: simple_client (5d8) exiting sock.c:2452: TEST 3 COMPLETE sock.c:2450: STARTING TEST 4 sock.c:611: overlapped_server (5e0) starting sock.c:680: overlapped_server (5e0) ready sock.c:807: simple_client (388): starting sock.c:810: simple_client (388): server ready sock.c:807: simple_client (284): starting sock.c:810: simple_client (284): server ready sock.c:821: simple_client (388) connected sock.c:821: simple_client (284) connected sock.c:705: overlapped_server (5e0): accepting client connection sock.c:705: overlapped_server (5e0): accepting client connection sock.c:840: simple_client (284) exiting sock.c:840: simple_client (388) exiting sock.c:790:
Re: Running a conformance test on windows before submitting to wine-patches.
Thanks. I'll typecast the warnings out or write a new macro for wsa_ok -Scott On Thu, Aug 21, 2008 at 4:42 AM, Austin English [EMAIL PROTECTED] wrote: On Wed, Aug 20, 2008 at 2:25 PM, Scott Lindeneau [EMAIL PROTECTED] wrote: Sorry about not knowing how to cross compile before. Here is the patch(gmail doesn't let me attach exe's... I will look into this). Please try this. Tell me if I am doing something wrong (again). -Scott Got some warnings, might check into that. [EMAIL PROTECTED]:~/wine-git/dlls/ws2_32/tests$ make crosstest i586-mingw32msvc-gcc -c -I. -I. -I../../../include -I../../../include -g -O2 -o protocol.cross.o protocol.c i586-mingw32msvc-gcc -c -I. -I. -I../../../include -I../../../include -g -O2 -o sock.cross.o sock.c sock.c: In function `overlapped_server': sock.c:636: warning: assignment makes integer from pointer without a cast sock.c:636: warning: comparison between pointer and integer sock.c:636: warning: comparison between pointer and integer sock.c:646: warning: assignment makes integer from pointer without a cast sock.c:646: warning: comparison between pointer and integer sock.c:646: warning: comparison between pointer and integer ../../../tools/make_ctests -o testlist.c protocol.c sock.c i586-mingw32msvc-gcc -c -I. -I. -I../../../include -I../../../include -g -O2 -o testlist.cross.o testlist.c i586-mingw32msvc-gcc protocol.cross.o sock.cross.o testlist.cross.o -o ws2_32_crosstest.exe -L../../../dlls -L../../../dlls/ws2_32 -L../../../dlls/kernel32 -lws2_32 -lkernel32 Passes for me in 2k (That test failure you see was already there, but it's a different function anyway). -Austin
Re: Running a conformance test on windows before submitting to wine-patches.
On Thu, Aug 21, 2008 at 04:25:07AM +0900, Scott Lindeneau wrote: Sorry about not knowing how to cross compile before. Here is the patch(gmail doesn't let me attach exe's... I will look into this). Please try this. Tell me if I am doing something wrong (again). Thanks for working on this. Before you submit this to wine-patches, get rid of the tabs so the indentation lines up. It will get auto-rejected for inconsistent indentation. ;)
Re: Running a conformance test on windows before submitting to wine-patches.
Guh. Ill figure it out eventually I guess. Which tabs are you talking about in particular? All of them? On Thu, Aug 21, 2008 at 5:48 AM, Dan Hipschman [EMAIL PROTECTED] wrote: On Thu, Aug 21, 2008 at 04:25:07AM +0900, Scott Lindeneau wrote: Sorry about not knowing how to cross compile before. Here is the patch(gmail doesn't let me attach exe's... I will look into this). Please try this. Tell me if I am doing something wrong (again). Thanks for working on this. Before you submit this to wine-patches, get rid of the tabs so the indentation lines up. It will get auto-rejected for inconsistent indentation. ;)
Re: Running a conformance test on windows before submitting to wine-patches.
On Thu, Aug 21, 2008 at 05:54:07AM +0900, Scott Lindeneau wrote: Guh. Ill figure it out eventually I guess. Which tabs are you talking about in particular? All of them? Yes, just stick with spaces, and it seems the convention is four spaces per indentation level.
Wine patches integrated into Valgrind svn
Hey, the Valgrind developers finally merged the Wine support patches! I just built Valgrind from svn as described here: http://valgrind.org/downloads/repository.html and on a fresh install of Gutsy, it just worked, no patches. To run Valgrind's tests under Wine, I configure valgrind with --prefix=/usr/local/valgrind-svn, then do something like cd wine-git/tools wget http://kegel.com/wine/valgrind/runtests.patch wget http://kegel.com/wine/valgrind/valgrind-daily.sh wget http://kegel.com/wine/valgrind/valgrind-suppressions wget http://kegel.com/wine/valgrind/valgrind-split-pl.txt -O valgrind-split.pl patch -p2 runtests.patch Then to run all the tests, I do cd ~/wine-git sh tools/valgrind-daily.sh or to run just one test, I do export RUNTEST_USE_VALGRIND=1 cd ~/wine-git/dlls/riched20/tests make test I've only verified that this works well on one machine so far, but I have high hopes. Anyone else feel like giving it a whirl? - Dan
Re: What the hell is up with searching google for wine-devel and wine-patches posts?
On Wed, Nov 07, 2007 at 01:36:01AM -0500, Steven Edwards wrote: I used to just be able to search as follows wine-patches Steven Edwards and see every patch I ever submitted to wine. For searching mailinglists I found http://search.gmane.org/ (e.g. use gmane.comp.emulators.wine.patches as group) very useful. Jan
What the hell is up with searching google for wine-devel and wine-patches posts?
Hi, I guess this issue is more directed at Dan and the rest of the google guys we have lurking here but has anyone else noticed how hard it is to do a google search for discussions on wine-devel or look for patches that have been submitted? I used to just be able to search as follows wine-patches Steven Edwards and see every patch I ever submitted to wine. Ditto for most threads on wine-devel. This is really getting to be a pain for me because I need to be able to search for patches that might not have been merged in but still have merit for some of my customers. Thanks -- Steven Edwards There is one thing stronger than all the armies in the world, and that is an idea whose time has come. - Victor Hugo
Re: What the hell is up with searching google for wine-devel and wine-patches posts?
Steven Edwards wrote: Hi, I guess this issue is more directed at Dan and the rest of the google guys we have lurking here but has anyone else noticed how hard it is to do a google search for discussions on wine-devel or look for patches that have been submitted? I used to just be able to search as follows wine-patches Steven Edwards and see every patch I ever submitted to wine. Ditto for most threads on wine-devel. This is really getting to be a pain for me because I need to be able to search for patches that might not have been merged in but still have merit for some of my customers. Thanks Try: site:http://www.winehq.org/pipermail/wine-patches/ Steven Edwards Thanks, Scott Ritchie
Re: What the hell is up with searching google for wine-devel and wine-patches posts?
On Nov 7, 2007 2:23 AM, Scott Ritchie [EMAIL PROTECTED] wrote: Try: site:http://www.winehq.org/pipermail/wine-patches/ Steven Edwards Thanks that works a little better, though normally I would do something like wine-devel AUTHOR Subject and depending on how much discussion a certain patch set had gotten its relivancy would be higher. Ditto for the patches list. Using site: seems to help a bit but the behavior of the search has still changed as is kind of annoying. Anyone have any idea why? -- Steven Edwards There is one thing stronger than all the armies in the world, and that is an idea whose time has come. - Victor Hugo
wine-patches
Why do the patches I send to wine-patches never show up in the list? Are they being received? _ Mortgage rates near historic lows. Refinance $200,000 loan for as low as $771/month* https://www2.nextag.com/goto.jsp?product=10035url=%2fst.jsptm=ysearch=mortgage_text_links_88_h27f8disc=yvers=689s=4056p=5117
Re: wine-patches
EA Durbin [EMAIL PROTECTED] wrote: Why do the patches I send to wine-patches never show up in the list? Are they being received? How do you check? http://www.winehq.org/pipermail/wine-patches http://www.winehq.org/pipermail/wine-patches/2007-April/037735.html http://www.winehq.org/pipermail/wine-patches/2007-April/037785.html -- Dmitry.
Re: wine-patches
EA Durbin schreef: Why do the patches I send to wine-patches never show up in the list? Are they being received? Try subscribing to the wine-patches mailing list, if you're only interested in sending patches you can turn off receiving messages from that list.
Re: wine-patches
I've checked the mailing list, they don't appear to be in the list. From: Dmitry Timoshkov [EMAIL PROTECTED] To: EA Durbin [EMAIL PROTECTED],wine-devel@winehq.org Subject: Re: wine-patches Date: Wed, 11 Apr 2007 00:43:39 +0900 EA Durbin [EMAIL PROTECTED] wrote: Why do the patches I send to wine-patches never show up in the list? Are they being received? How do you check? http://www.winehq.org/pipermail/wine-patches http://www.winehq.org/pipermail/wine-patches/2007-April/037735.html http://www.winehq.org/pipermail/wine-patches/2007-April/037785.html -- Dmitry. _ Cant afford to quit your job? Earn your AS, BS, or MS degree online in 1 year. http://www.classesusa.com/clickcount.cfm?id=866145goto=http%3A%2F%2Fwww.classesusa.com%2Ffeaturedschools%2Fonlinedegreesmp%2Fform-dyn1.html%3Fsplovr%3D866143
some emails not arriving to wine-patches (was CMD.EXE resubmits)
There does not seem to be a patch attached. They followed However - I sent all 9, and got immediate cc: copies returned to me for all 9. Browsing the patches through either gmame or wine-patches archives, only shows 1,2,5 and 7 got through. This is the same as yesterday when a number of the 19 I sent failed to get through and vanished (no rejection emails or anything).. - Can anyone who subscribes to wine-patches tell me if they received any more than 1,2,5 and 7? - Anyone got any ideas as to what might be going on, or how to persue it... I'd blame the ISP but I've never (knowingly) lost emails before, only when sent to wine-patches! I did contact the ISP help desk and they said its probably a problem with the receiving mail server (surprise, surprise) Jason
Re: some emails not arriving to wine-patches (was CMD.EXE resubmits)
Ann Jason Edmeades wrote: As an FYI I sent the same patchset to another email account (not on my ISP, just one of the free ones) and they all got through 4 times. It would start to point to the wine-patches side of things, but I have never seen anyone else have problems Note I am not seeing any rejection emails either You won't get rejection emails. The patches are not showing up in the moderation queue, and you only get rejections if they show up there. Though I don't know where they are going. I think a month or two ago Jeremy mentioned making some changes to limit the number of simultaneous email connections... or something like that. I really didn't understand it, so I didn't pay close attention.
Re: some emails not arriving to wine-patches (was CMD.EXE resubmits)
I've asked Jeremy to take a look and see if anything obvious is going on. Cheers, Jeremy Ann Jason Edmeades wrote: As an FYI I sent the same patchset to another email account (not on my ISP, just one of the free ones) and they all got through 4 times. It would start to point to the wine-patches side of things, but I have never seen anyone else have problems Note I am not seeing any rejection emails either Jason
wine-patches archive attachments have strange mime type?
When I'm looking at the wine-patches archives, e.g. at http://winehq.org/pipermail/wine-patches/2006-April/025521.html and the patch is an attachment, the archive's link to the attachment, e.g. http://www.winehq.org/pipermail/wine-patches/attachments/20060408/64e34006/76c37de4da1db3f8e92003d8ff125509c04bb644.diff can't be displayed by my copy of Firefox; it doesn't recognize the DIFF or PATCH mime types. I tried adding them in /etc/mime.types, and I tried looking for a way to set them in Firefox, but no joy. Should the server be serving these up as mime type text/plain? - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv
Re: The wine-patches archives
On 7/1/05, Jeremy Newman [EMAIL PROTECTED] wrote: What are you talking about? Nothing, I downloaded the down loadable version and it was 10.2 MB while the site was only reporting 9 MB ... I thought we were stuck at 9, then a patch came in and it rolled over to 10.. Tom
The wine-patches archives
Looks like Downloadable version is stuck at 9 MB last time I checked we were at a new record of 10.2 MB . Newman to the rescue ? Cheers, Tom
Problems posting to wine-patches
Sorry about posting here, but... I seem to be having problems posting to wine-patches, and don't seem to be able to get through to Jeremy Newman either. Other people seem to be getting through okay. Am I the only one? Any ideas why? I know they are not getting stuck in the moderation queue; they seem to be disappearing without a trace that I can find.
Problems with wine-patches
Hi, I'm not able to send (what I think is normal) email to wine-patches anymore. The Test mail worked. Any ideas? Cheers, Paul.
Re: Problems with wine-patches
Le jeudi 10 fvrier 2005 10:42 +0100, Paul Vriens a crit : Hi, I'm not able to send (what I think is normal) email to wine-patches anymore. The Test mail worked. Any ideas? Cheers, Paul. I have the same problem when I send patches that are too big. They never appear in wine-patches.
Re: Problems with wine-patches
On Thu, 10 Feb 2005 13:14:19 +0100, Jonathan Ernst wrote: I have the same problem when I send patches that are too big. They never appear in wine-patches. I expect they're being held in the moderation queue, normally they'll be released shortly when that happens but you can always compress the patch or post a URL to it if it's really too big. Better way is to make the patches smaller of course ...
Re: Problems with wine-patches
On Thu, 2005-02-10 at 14:49, Mike Hearn wrote: On Thu, 10 Feb 2005 13:14:19 +0100, Jonathan Ernst wrote: I have the same problem when I send patches that are too big. They never appear in wine-patches. I expect they're being held in the moderation queue, normally they'll be released shortly when that happens but you can always compress the patch or post a URL to it if it's really too big. Better way is to make the patches smaller of course ... Yeah, but this patch was smaller than the ones I've send before. I've gzipped it now and it's accepted! Weird! Cheers, Paul
Re: Problems with wine-patches
Paul Vriens wrote: Hi, I'm not able to send (what I think is normal) email to wine-patches anymore. The Test mail worked. Any ideas? Cheers, Paul. I hade the same problem about a week to ten days ago. You will see where I also sent a test to wine-patches. Then the problem went just away. Tom
Re: Problems with wine-patches
Mike Hearn wrote: On Thu, 10 Feb 2005 13:14:19 +0100, Jonathan Ernst wrote: I have the same problem when I send patches that are too big. They never appear in wine-patches. I expect they're being held in the moderation queue, normally they'll be released shortly when that happens but you can always compress the patch or post a URL to it if it's really too big. Better way is to make the patches smaller of course ... Well, when I came in this morning for moderation, the wine-patches queue was empty. But it was the only one; rather unusual. So either someone else cleared out only the wine-patches queue, or wine-patches might indeed be broken.
Re: Problems with wine-patches
Duane Clark wrote: Well, when I came in this morning for moderation, the wine-patches queue was empty. But it was the only one; rather unusual. So either someone else cleared out only the wine-patches queue, or wine-patches might indeed be broken. Tom asked me to let his opengl patch trough, so I did that list. Ivan.
Re: Problems with wine-patches
Tom asked me to let his opengl patch trough, so I did that list. Is it just a problem of upping the default 40K size? afair, that's the mailman default. Perhaps we should just raise it. Cheers, Jer
Re: Problems with wine-patches
On Thu, 2005-02-10 at 19:33, Jeremy White wrote: Tom asked me to let his opengl patch trough, so I did that list. Is it just a problem of upping the default 40K size? afair, that's the mailman default. Perhaps we should just raise it. Cheers, Jer My patch was a mere 3815 bytes (gzipped 1055), so that can't be it. Paul.
Re: Problems with wine-patches
Paul Vriens wrote: On Thu, 2005-02-10 at 19:33, Jeremy White wrote: Tom asked me to let his opengl patch trough, so I did that list. Thanks Ivan... Is it just a problem of upping the default 40K size? afair, that's the mailman default. Perhaps we should just raise it. I would say Yes... The 40K size limit isn't just on these list but alot of other list out there. The only problem with 40K is its arcane! This was the limit 10 years ago when people had 9600 and 14400 modems. Cheers, Jer My patch was a mere 3815 bytes (gzipped 1055), so that can't be it. Paul. This was my test message : http://www.winehq.org/hypermail/wine-patches/2005/02/0054.html The patch I was trying to send was status-5.diff about 20K if I remember correct.. I bounced for two day's before it cleared up. Juan Lang sent a bounce test : http://www.winehq.org/hypermail/wine-patches/2005/01/0555.html So your not alone... :-) Tom
Re: Problems with wine-patches
Jeremy White wrote: Tom asked me to let his opengl patch trough, so I did that list. Is it just a problem of upping the default 40K size? afair, that's the mailman default. Perhaps we should just raise it. The wine-patches list is 80KB, but the others are 40. The main reason I have left them that size is that occasionally someone's computer gets infected and starts spamming the list with legitimate from addresses. The size limit occasionally helps block them. I don't think the limit is causing problems; most people on the list understand how it works. Though I have no idea what happened to Paul's posts.
Re: Virus on wine-patches@winehq.org
Vincent Béron wrote: Also, I'd like to take this time to thank Duane for his hard work as lists moderator. Without him either we'd get a lot more of those mails, or we'd need to block non-registered people. Vincent Not trying to say that our moderators are not doing a splendid work, but why not install ClamAV on the mail server? I installed it last weekend on mine, and it did wonders! http://www.clamav.net/ http://www.amavis.org/ Shachar -- Shachar Shemesh Lingnu OpenSource Consulting http://www.lingnu.com/
Virus on wine-patches@winehq.org
Could someone please remove the following postings from the archive as they contain viruses? http://www.winehq.org/hypermail/wine-patches/2004/04/0082.html http://www.winehq.org/hypermail/wine-patches/2004/04/0084.html Rolf Kalbermatter
Re: Virus on wine-patches@winehq.org
Le mar 06/04/2004 à 06:07, Rolf Kalbermatter a écrit : Could someone please remove the following postings from the archive as they contain viruses? http://www.winehq.org/hypermail/wine-patches/2004/04/0082.html http://www.winehq.org/hypermail/wine-patches/2004/04/0084.html Rolf Kalbermatter Just so everybody is sure, they do not come from me. The originator (as per the headers) is Received: from 54WZ402-LRG016.net (68.116.153.107.ts46v-12.otne2.ftwrth.tx.charter.com [68.116.153.107]) by So if your ISP is Charter Communications and/or you live in Texas, mayber it'd be time to check your system for viruses. Also, I'd like to take this time to thank Duane for his hard work as lists moderator. Without him either we'd get a lot more of those mails, or we'd need to block non-registered people. Vincent
