Date: Tue, 9 Sep 2014 13:49:08 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: FreeBSD Ports <freebsd-ports@freebsd.org>, FreeBSD CURRENT <freebsd-current@freebsd.org> Cc: marino@FreeBSD.org Subject: Re: [Bug 144203] textproc/refdb: network clients loop indefinitely when hitting Ctrl-D while client asks for passowrd Message-ID: <20140909134908.6d4cfc03.ohartman@zedat.fu-berlin.de> In-Reply-To: <bug-144203-21963-Q1c4cxMhYJ@https.bugs.freebsd.org/bugzilla/> References: <bug-144203-21963@https.bugs.freebsd.org/bugzilla/> <bug-144203-21963-Q1c4cxMhYJ@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Am Tue, 09 Sep 2014 06:35:29 +0000 bugzilla-noreply@freebsd.org schrieb: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144203 > > --- Comment #8 from John Marino <marino@FreeBSD.org> --- > FYI, I'm removing this port tonight. We've waited long enough. > In the strain of a bug I reported I also tried to fix this port, since the prior maintainer seems to have abandonded this great port. I'm a bit pissed off about the rude tune I feel treated! The developer has patched the original sources to meet some FreeBSD requirements regarding a readline issue now fixed and especially some serious bugs in bib2ris and a transforming/migrating tool using UTF-8 encodings for LaTeX codings. Since not all patches are 100% tested (but they work graeat for me in a scientific environment), the upstream developer hestiates creating the new tarball. As I documented with this PR, I'm wating for the developer to publish a new tarball. I spent lot of time to provide a workaround for fixing the lack of the new tarball and some serious previously unresolved FreeBSD issues and the time I sacrificed is not only "working time"! I mention this since I'm feeling put under pressure as the note sent to me documents. What is the policy of FreeBSD's port system? There are lots of ports waiting to be fixed since they have serious issue, like silc-toolkit. Is this port also about to be deleted or isn't there a "lobby" preventing this? In a hurry, to prevent the destruction of the port textproc/refdb, I provided a patch. The patch is a bit messy since I had to incorporate all changes made in the meanwhile after creation of refdb-1.0.2.tar.gz (provided at: http://sourceforge.net/projects/refdb/files/latest/download). Please see PR "Bug 193484 - [textproc/refdb] Update port". With regards, oh [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJUDuk5AAoJEOgBcD7A/5N8x5kH/iSz6SOmFojIWsSCQiq/pJlS HMlRZ5iGY2tx8UItUP1a8JChxyFZx+me52HPduJX12J+voCTWHJD+bOreSQvn9f5 VB2t8PkxRZ0RfQCZgagFDWk6ApI5Bg/Uo/xtfJojeFFEqKTnNt9AQoCqqky/xFWL icuR4wo0i4cThPevHZ4vHwceG158rjmYXNvL9p5MNyGh4zjBdDCnbSfaPrCEjJmd 3FN20OE6EN1/Skd5lwcYq72LNZUFCuEFktfo12q2cyOHtMG44dANcsWStJf/Yykn 4qI3vWsCl/oqsCptErI0SIC2iclmypo6zIN8UZn/cQLBAMtmvZCcElydZ/Bp8x0= =tEoM -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140909134908.6d4cfc03.ohartman>