From owner-freebsd-current Fri Oct 18 12:41:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC9DC37B401 for ; Fri, 18 Oct 2002 12:41:20 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 4AB4D43EB3 for ; Fri, 18 Oct 2002 12:41:20 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 46821 invoked by uid 1000); 18 Oct 2002 19:41:21 -0000 Date: Fri, 18 Oct 2002 12:41:21 -0700 (PDT) From: Nate Lawson To: "Long, Scott" Cc: current@freebsd.org Subject: RE: cdrtools doesn't build on -current (pkg_add -r segfault) In-Reply-To: <6100BCEB85F8E244959C756C04E0EDD161CAD1@otcexc01.otc.adaptec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 18 Oct 2002, Long, Scott wrote: > Nate Lawson wrote: > > On Fri, 18 Oct 2002, Scott Long wrote: > > > [...] > > > **Warning, rant** > > > The ports collection is one of the crown jewels of FreeBSD. > > > Unfortunately, even as more ports committers are added, more and > > > more ports break or become harder to build. On top of that, > > > pkg_add has become close to worthless now that the -r feature > > > is so fragile. > > > > I found a bug in libfetch a while back that causes pkg_add -r > > to seg fault > > on the 2nd package. This was also reported by numerous people. See > > thread: > > > > > > I received NO replies but am not the maintainer of libfetch. So this > > message will serve as a warning -- if someone more familiar > > with the code > > does not fix it the "right" way, I will fix it and you may > > not like it. > > If you have a fix and the maintainer has not replied, then please do > commit your fix as soon as possible. The worst that could happen is > that the maintainer wakes up. > > Scott If you check the email, it's not a simple fix and there are two widely divergent paths to take regarding who owns the cached connection. That's why I was waiting on the author. But since this has been around for too long and I think I know the right answer, I'll build a fix for the first path and commit it. Ping me next Friday if I haven't done it by then. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message