Fwd: [Imap-uw] inbox corruption by iphone
Based on the below it seems the imap-uw port ought to go to an unsupported
state or be otherwise modified?
Brian
-- Forwarded message --
From: David B Funk
Date: Sat, Aug 1, 2015 at 7:59 AM
Subject: Re: [Imap-uw] inbox corruption by iphone
To: brian
Cc: UW imap list imap...@u.washington.edu
Have you tried the Panda IMAP distro?
https://github.com/jonabbey/panda-imap
The mailbox locking problem can be avoided by using an alternate form of
mailbox (such as MIX) instead of the traditional mbox. Of course this won't
work in an environment that requires local direct access to the mailbox by
non-C-client aware mail clients. If you can switch to MIX format there are
many advantages (performance, scale-ability, backup facilitation, etc).
However if you do switch to MIX be -sure- to run the Panda distro, there
were some unfixed bugs in the UW-imap distro that can bite you.
After Mark left UW he started his own company with a fork of the UW-imap
which he called Panda and then started developing a commercial product
from there.
He kept Panda alive and semi-open sourced, making bug-fixes and adding some
small improvements (I know from conversations I had with him in '09 about a
UW-imap bug I found/fixed ). He made it available to people who explicitly
asked him for it.
After his death people took the last known version of Panda and turned it
into a github project and made additional improvements to it (I contributed
one of them ;).
On Sat, 1 Aug 2015, brian wrote:
as expected, thanx for confirming.
Brian
On 8/1/2015 1:25 AM, Chris Bunch wrote:
I have been running a UW_IMAP server on Mac OS X mainly for family
accounts for around 12 years. We are all Mac/iOS users: we noted early on
that UW_IMAP doesn't cope well with more than one client logged into an
account at the same time. When the most any of us had was two machines
(home/office or home/laptop) that was relatively easy to manage but when
iOS came along(iPhones, iPads) came along things began to unravel and the
situation became unworkable. iPhones never stayed in sync with the server,
though I have not seen the specific corruption you mention.
I am now in the process of transferring family accounts to Fastmail and
am setting up Dovecot on Linode/Ubuntu for a few other accounts I manage.
Sadly, UW_IPAD’s future died with Mark Crispin.
C
On 22 Jul 2015, at 08:57, brian br...@brianwhalen.net wrote:
One of the users on my freebsd server that runs uw imap has an
intermittent problem with inbox corruption. Is a fix planned? I see others
have had this issue already. I am essentially seeing this
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557103 though on
Freebsd.
Brian
--
Dave Funk University of Iowa
dbfunk (at) engineering.uiowa.eduCollege of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_adminIowa City, IA 52242-1527
#include std_disclaimer.h
Better is not better, 'standard' is better. B{
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: lang/tcc unusable
El lun, 03-08-2015 a las 18:26 -0400, Jung-uk Kim escribió:
On 08/03/2015 17:40, Carlos Jacobo Puga Medina wrote:
El lun, 03-08-2015 a las 17:26 -0400, Jung-uk Kim escribió:
On 08/03/2015 16:41, Carlos Jacobo Puga Medina wrote:
El lun, 03-08-2015 a las 16:33 -0400, Jung-uk Kim escribió:
Hi Jung-uk,
On 08/03/2015 16:26, Carlos Jacobo Puga Medina wrote:
Hi people,
Recently I added amd64 support to TinyCC, but I encounter
the following problem trying to compile a simple code.
#include stdio.h
int main(){ printf(hello, world!\n); return 0; }
% tcc -o hello hello.c In file included from hello.c:1:
/usr/include/stdio.h:63: error: ';' expected (got
va_list)
I guess that some change introduced in 'stdio.h' causes
this weird behaviour. Last time that TCC worked fine was on
FreeBSD 9.1 -RELEASE/i386.
Also I reported this problem in the tinycc-devel mailing
list [1]
Any thoughts?
I haven't tried tcc but '' is missing for the printf().
Yes, it was a typo here :)
It seems it's a known tcc bug:
http://savannah.nongnu.org/bugs/?30966
Is there something that we can do about it?
Thanks for pointing me, jkim@
It seems there is no easy way to fix this problem without touching
src
tree, e.g.,
--- sys/x86/include/_types.h (revision 286256)
+++ sys/x86/include/_types.h (working copy)
@@ -152,7 +152,7 @@
*/
#ifdef __GNUCLIKE_BUILTIN_VARARGS
typedef __builtin_va_list __va_list; /*
internally known to gcc */
-#elif defined(lint)
+#elif defined(__TINYC__) || defined(lint)
typedef char * __va_list; /*
pretend */
#endif
#if defined(__GNUC_VA_LIST_COMPATIBILITY)
!defined(__GNUC_VA_LIST) \
If you need doing some changes into the src tree. So, what do you
recommend in such case?
Would it be much trouble add the necessary changes to run TCC again?
Furthermore, TinyCC developer has ignored this issue completely.
Cheers,
--
Carlos Jacobo Puga Medina c...@fbsd.es
PGP fingerprint = C60E 9497 5302 793B CC2D BB89 A1F3 5D66 E6D0 5453
signature.asc
Description: This is a digitally signed message part
Re: lang/tcc unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/03/2015 19:23, Carlos Jacobo Puga Medina wrote:
El lun, 03-08-2015 a las 18:26 -0400, Jung-uk Kim escribió:
On 08/03/2015 17:40, Carlos Jacobo Puga Medina wrote:
El lun, 03-08-2015 a las 17:26 -0400, Jung-uk Kim escribió:
On 08/03/2015 16:41, Carlos Jacobo Puga Medina wrote:
El lun, 03-08-2015 a las 16:33 -0400, Jung-uk Kim
escribió:
Hi Jung-uk,
On 08/03/2015 16:26, Carlos Jacobo Puga Medina wrote:
Hi people,
Recently I added amd64 support to TinyCC, but I
encounter the following problem trying to compile a
simple code.
#include stdio.h
int main(){ printf(hello, world!\n); return 0; }
% tcc -o hello hello.c In file included from
hello.c:1: /usr/include/stdio.h:63: error: ';' expected
(got va_list)
I guess that some change introduced in 'stdio.h' causes
this weird behaviour. Last time that TCC worked fine
was on FreeBSD 9.1 -RELEASE/i386.
Also I reported this problem in the tinycc-devel
mailing list [1]
Any thoughts?
I haven't tried tcc but '' is missing for the printf().
Yes, it was a typo here :)
It seems it's a known tcc bug:
http://savannah.nongnu.org/bugs/?30966
Is there something that we can do about it?
Thanks for pointing me, jkim@
It seems there is no easy way to fix this problem without
touching src tree, e.g.,
--- sys/x86/include/_types.h (revision 286256) +++
sys/x86/include/_types.h (working copy) @@ -152,7 +152,7 @@ */
#ifdef __GNUCLIKE_BUILTIN_VARARGS typedef__builtin_va_list
__va_list; /* internally known to gcc */ -#elif defined(lint)
+#elif defined(__TINYC__) || defined(lint) typedef char *
__va_list; /* pretend */ #endif #if
defined(__GNUC_VA_LIST_COMPATIBILITY)
!defined(__GNUC_VA_LIST) \
If you need doing some changes into the src tree.
https://svnweb.freebsd.org/changeset/base/286265
So, what do you recommend in such case? Would it be much trouble
add the necessary changes to run TCC again? Furthermore, TinyCC
developer has ignored this issue completely.
The only hack I see is defining __va_list as a macro from libtcc.c but
it is ugly.
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBCAAGBQJVwAXXAAoJEHyflib82/FGLOwH/3HxMqLqt/G6thF5DqTQsqA+
PoHwp3Qdvkwx9Z/LjjLQlyrtZMSXSBfKv0IisZlblaFqkV0p8rnC/X+hpHhtTm4I
6inQyI36zwCRr3aD31hvRWpeYpjjZSJotsTbvmb4+cvjw4nSyJ43lBcomAyGx9dW
0lDrxVDzUvyVpBqYMGOgp6IvaDpyo2YF8yanpKD1vksdzDi2KvyvkRQx9/3VLu8A
OJla4pluo2Q83wQmRZqJZIu5eqgYQCdI/2ETiV4bVWLarQRkdwWHgjwt2LqQEciE
ZNIGKhFUBDXhXjuw0ND+UofQrt9IZtmNRRYX6LoaDuTdhazlDQKsq/opCHGYVsI=
=bbog
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Problems with update to print/tex-luatex
On Mon, Aug 3, 2015 at 2:03 PM, Dr. Peter Voigt pvo...@uos.de wrote: On Mon, 3 Aug 2015 13:04:19 -0700 Kevin Oberman rkober...@gmail.com wrote: When I tried updating print/tex-luatex today, the install phase failed with a number of missing files. The log showed that the port uses luatex in the install phase but fails due to a missing .so, poppler.so.49. This has been superseded by libpoppler.so.53, but the install was defaulting to the previously built binary, not the newly built one. I was able to get the port installed by deleting the existing port (pkg delete tex-luatex) and deleting work/.stage_done.luatex._usr_local and re-running stage and install. I think a note to that effect should be in UPDATING. Obviously this does impact new installs or poudriere build and probably not package installs, but it does hit upgrades. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Well, I can confirm this behavior from my today experiences with print/tex-luatex. As a result of my upgrade attempt my old print/tex-luatex packages was deleted. I just upgraded all remaining TeXLive packages and tried a fresh installation of print/tex-luatex: This time it installed just fine. I am far from understanding these miracles but I have learned my ports lesson: Some package refuse to upgrade while being installed - the error messages, however are quite different. Peter This is annoyingly common and seldom caught because the standard test method is a virgin install. It can involve using the wrong header files, the wrong shareable, or the wrong executable. As the errors can be be triggered in a variety of ways, they can look quite different. Usually the log can point out the issue as it did in this case. This was an issue with libchamplain for years, but was finally fixed. -- Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: lang/tcc unusable
El lun, 03-08-2015 a las 17:26 -0400, Jung-uk Kim escribió:
On 08/03/2015 16:41, Carlos Jacobo Puga Medina wrote:
El lun, 03-08-2015 a las 16:33 -0400, Jung-uk Kim escribió:
Hi Jung-uk,
On 08/03/2015 16:26, Carlos Jacobo Puga Medina wrote:
Hi people,
Recently I added amd64 support to TinyCC, but I encounter the
following problem trying to compile a simple code.
#include stdio.h
int main(){ printf(hello, world!\n); return 0; }
% tcc -o hello hello.c In file included from hello.c:1:
/usr/include/stdio.h:63: error: ';' expected (got va_list)
I guess that some change introduced in 'stdio.h' causes this
weird behaviour. Last time that TCC worked fine was on FreeBSD
9.1 -RELEASE/i386.
Also I reported this problem in the tinycc-devel mailing list
[1]
Any thoughts?
I haven't tried tcc but '' is missing for the printf().
Yes, it was a typo here :)
It seems it's a known tcc bug:
http://savannah.nongnu.org/bugs/?30966
Is there something that we can do about it?
Thanks for pointing me, jkim@
--
Carlos Jacobo Puga Medina c...@fbsd.es
PGP fingerprint = C60E 9497 5302 793B CC2D BB89 A1F3 5D66 E6D0 5453
signature.asc
Description: This is a digitally signed message part
Re: lang/tcc unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/03/2015 17:40, Carlos Jacobo Puga Medina wrote:
El lun, 03-08-2015 a las 17:26 -0400, Jung-uk Kim escribió:
On 08/03/2015 16:41, Carlos Jacobo Puga Medina wrote:
El lun, 03-08-2015 a las 16:33 -0400, Jung-uk Kim escribió:
Hi Jung-uk,
On 08/03/2015 16:26, Carlos Jacobo Puga Medina wrote:
Hi people,
Recently I added amd64 support to TinyCC, but I encounter
the following problem trying to compile a simple code.
#include stdio.h
int main(){ printf(hello, world!\n); return 0; }
% tcc -o hello hello.c In file included from hello.c:1:
/usr/include/stdio.h:63: error: ';' expected (got
va_list)
I guess that some change introduced in 'stdio.h' causes
this weird behaviour. Last time that TCC worked fine was on
FreeBSD 9.1 -RELEASE/i386.
Also I reported this problem in the tinycc-devel mailing
list [1]
Any thoughts?
I haven't tried tcc but '' is missing for the printf().
Yes, it was a typo here :)
It seems it's a known tcc bug:
http://savannah.nongnu.org/bugs/?30966
Is there something that we can do about it?
Thanks for pointing me, jkim@
It seems there is no easy way to fix this problem without touching src
tree, e.g.,
- --- sys/x86/include/_types.h (revision 286256)
+++ sys/x86/include/_types.h(working copy)
@@ -152,7 +152,7 @@
*/
#ifdef __GNUCLIKE_BUILTIN_VARARGS
typedef__builtin_va_list __va_list; /* internally known to
gcc */
- -#elif defined(lint)
+#elif defined(__TINYC__) || defined(lint)
typedefchar * __va_list; /* pretend */
#endif
#if defined(__GNUC_VA_LIST_COMPATIBILITY) !defined(__GNUC_VA_LIST) \
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBCAAGBQJVv+qlAAoJEHyflib82/FGJ0YH/jX8EZnWenTM2BJEjLNrIA8O
XjYIPgFWkL/DZF8GnTZYv0mcrP9UgxNix2U76PDTBN8n/xkBCIUJpUORysQqTlo5
olU4nVT5EMfVyO2YDKEsb5c+dDsWkE0MPt/t2HE+oPDmml75v3MnCZAQmgIp8VsO
Peb8bhbJ913xECFcW4XhVqKMy+uCsX6tPW/2Epw+p/Ho8Id3RM4A7CBprVhkNkAp
zAPe2/PxAH71m2HzCKq6tMVe4DZKyi708pry0ApbYXYa2+JIA2YXKCBX4ugYJgI0
K860//U30Zn4DeZ/VGxENa9xo+c56g0NcWvjO6qvTOSU1h2ItBVrsvQPBfmLTIQ=
=zBRK
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: lang/tcc unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/03/2015 16:41, Carlos Jacobo Puga Medina wrote:
El lun, 03-08-2015 a las 16:33 -0400, Jung-uk Kim escribió:
Hi Jung-uk,
On 08/03/2015 16:26, Carlos Jacobo Puga Medina wrote:
Hi people,
Recently I added amd64 support to TinyCC, but I encounter the
following problem trying to compile a simple code.
#include stdio.h
int main(){ printf(hello, world!\n); return 0; }
% tcc -o hello hello.c In file included from hello.c:1:
/usr/include/stdio.h:63: error: ';' expected (got va_list)
I guess that some change introduced in 'stdio.h' causes this
weird behaviour. Last time that TCC worked fine was on FreeBSD
9.1 -RELEASE/i386.
Also I reported this problem in the tinycc-devel mailing list
[1]
Any thoughts?
I haven't tried tcc but '' is missing for the printf().
Yes, it was a typo here :)
It seems it's a known tcc bug:
http://savannah.nongnu.org/bugs/?30966
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBCAAGBQJVv9yaAAoJEHyflib82/FGyo0IAJsHtcVWos+Ahd/dgq4O+KXM
OUy5yStNq90ryn2MevVXTlT6Jdp83G1tCa5lWOIr7NGyXKAT9IVpEvcYS2ePgMTU
6ZoE2eX3ZhM1NQCxeSDE0empIaIGwTdlKa89FC+vBjxM+OzqdcLhkgC1KEuXUHUX
DwwgWf/0EHZVY8jwPN7K0I7GUwO613dVQo+eNq6JG8h1Fyjr9P272wEI2LLpGPan
ywnRuEtIPMqitqY3UkStAcj5PPR+53jKgQWD2NdvALIcmF6juiHnTCkgrITCZcNc
c8Cx228MGISbI8NoYrggY2y+2QUwvyMklBopl6Q3q/MKJgWPuSACSQ2gAu/rgaI=
=8p00
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: What's going on with svn server?
On Mon, 3 Aug 2015 09:07:06 +0200 Kurt Jaeger li...@opsec.eu wrote: Hi! svn: E210005: Unable to connect to a repository at URL 'svn://svn.freebsd.org/ports/head' svn: E210005: No repository found in 'svn://svn.freebsd.org/ports/head' Same problem here. Access still works from repo.freebsd.org, but only via svn+ssh. Peter Wemm fixed it. Confirmed. I just found it works again. Thanks. Milan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: What's going on with svn server?
Hi! svn: E210005: Unable to connect to a repository at URL 'svn://svn.freebsd.org/ports/head' svn: E210005: No repository found in 'svn://svn.freebsd.org/ports/head' Same problem here. Access still works from repo.freebsd.org, but only via svn+ssh. Peter Wemm fixed it. -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Problems with update to print/tex-luatex
On Mon, 3 Aug 2015 13:04:19 -0700 Kevin Oberman rkober...@gmail.com wrote: When I tried updating print/tex-luatex today, the install phase failed with a number of missing files. The log showed that the port uses luatex in the install phase but fails due to a missing .so, poppler.so.49. This has been superseded by libpoppler.so.53, but the install was defaulting to the previously built binary, not the newly built one. I was able to get the port installed by deleting the existing port (pkg delete tex-luatex) and deleting work/.stage_done.luatex._usr_local and re-running stage and install. I think a note to that effect should be in UPDATING. Obviously this does impact new installs or poudriere build and probably not package installs, but it does hit upgrades. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Well, I can confirm this behavior from my today experiences with print/tex-luatex. As a result of my upgrade attempt my old print/tex-luatex packages was deleted. I just upgraded all remaining TeXLive packages and tried a fresh installation of print/tex-luatex: This time it installed just fine. I am far from understanding these miracles but I have learned my ports lesson: Some package refuse to upgrade while being installed - the error messages, however are quite different. Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
lang/tcc unusable
Hi people,
Recently I added amd64 support to TinyCC, but I encounter the following
problem trying to compile a simple code.
#include stdio.h
int main(){
printf(hello, world!\n);
return 0;
}
% tcc -o hello hello.c
In file included from hello.c:1:
/usr/include/stdio.h:63: error: ';' expected (got va_list)
I guess that some change introduced in 'stdio.h' causes this weird
behaviour. Last time that TCC worked fine was on FreeBSD 9.1
-RELEASE/i386.
Also I reported this problem in the tinycc-devel mailing list [1]
Any thoughts?
[1]
https://lists.gnu.org/archive/html/tinycc-devel/2015-07/msg00020.html
--
Carlos Jacobo Puga Medina c...@fbsd.es
PGP fingerprint = C60E 9497 5302 793B CC2D BB89 A1F3 5D66 E6D0 5453
signature.asc
Description: This is a digitally signed message part
Re: lang/tcc unusable
El lun, 03-08-2015 a las 16:33 -0400, Jung-uk Kim escribió:
Hi Jung-uk,
On 08/03/2015 16:26, Carlos Jacobo Puga Medina wrote:
Hi people,
Recently I added amd64 support to TinyCC, but I encounter the
following problem trying to compile a simple code.
#include stdio.h
int main(){ printf(hello, world!\n); return 0; }
% tcc -o hello hello.c In file included from hello.c:1:
/usr/include/stdio.h:63: error: ';' expected (got va_list)
I guess that some change introduced in 'stdio.h' causes this weird
behaviour. Last time that TCC worked fine was on FreeBSD 9.1
-RELEASE/i386.
Also I reported this problem in the tinycc-devel mailing list [1]
Any thoughts?
I haven't tried tcc but '' is missing for the printf().
Yes, it was a typo here :)
Jung-uk Kim
--
Carlos Jacobo Puga Medina c...@fbsd.es
PGP fingerprint = C60E 9497 5302 793B CC2D BB89 A1F3 5D66 E6D0 5453
signature.asc
Description: This is a digitally signed message part
Problems with update to print/tex-luatex
When I tried updating print/tex-luatex today, the install phase failed with a number of missing files. The log showed that the port uses luatex in the install phase but fails due to a missing .so, poppler.so.49. This has been superseded by libpoppler.so.53, but the install was defaulting to the previously built binary, not the newly built one. I was able to get the port installed by deleting the existing port (pkg delete tex-luatex) and deleting work/.stage_done.luatex._usr_local and re-running stage and install. I think a note to that effect should be in UPDATING. Obviously this does impact new installs or poudriere build and probably not package installs, but it does hit upgrades. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: lang/tcc unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/03/2015 16:26, Carlos Jacobo Puga Medina wrote:
Hi people,
Recently I added amd64 support to TinyCC, but I encounter the
following problem trying to compile a simple code.
#include stdio.h
int main(){ printf(hello, world!\n); return 0; }
% tcc -o hello hello.c In file included from hello.c:1:
/usr/include/stdio.h:63: error: ';' expected (got va_list)
I guess that some change introduced in 'stdio.h' causes this weird
behaviour. Last time that TCC worked fine was on FreeBSD 9.1
-RELEASE/i386.
Also I reported this problem in the tinycc-devel mailing list [1]
Any thoughts?
I haven't tried tcc but '' is missing for the printf().
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBCAAGBQJVv9AuAAoJEHyflib82/FGcssH/RJOU1MJFGfiV4EzWeSm9rNy
XzqwOQUH3SjcMVf/13JeBOPTYvrpvGra/V6LkazptufyJXWxlIIZ2bLiTwJx+ruw
wDJyzjyXOdvWM202Xz0RvBZiduawQgs4nTBuqPM+7XX1p59njkm0mTQ1nVxQtjcf
4A2h6zSO/65rlkWFkdY+a6QO9J03joV6nwBkD7UIUeoJL4RdiRSaAn6oa6pjB71S
XCS69y9mSoXVE9rWd/nELhy46VCkMrx30l01Dbh61FWJNSKJDilkmeJdp1JvX4Nq
tXPJyGb235jdXzo/dXk2xjPjlRDPvw+dBWG8jNUB/Zh/oYR4StUxpOj8wrvvpZo=
=JZI6
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
