From owner-freebsd-questions Mon Jan 20 12:40:10 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A262637B405 for ; Mon, 20 Jan 2003 12:40:08 -0800 (PST) Received: from mired.org (ip68-97-54-220.ok.ok.cox.net [68.97.54.220]) by mx1.FreeBSD.org (Postfix) with SMTP id 9D81443F3F for ; Mon, 20 Jan 2003 12:40:01 -0800 (PST) (envelope-from mwm-dated-1043527200.2ad600@mired.org) Received: (qmail 972 invoked from network); 20 Jan 2003 20:40:00 -0000 Received: from localhost.mired.org (HELO guru.mired.org) (127.0.0.1) by localhost.mired.org with SMTP; 20 Jan 2003 20:40:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15916.24223.901271.278437@guru.mired.org> Date: Mon, 20 Jan 2003 14:39:59 -0600 To: stacey@vickiandstacey.com Cc: FreeBSD Questions , sobomax@FreeBSD.org Subject: Re: portupgrade of jasper-1.500.4 fails In-Reply-To: <1043094762.13652.9.camel@localhost> References: <1043015655.51041.505.camel@localhost> <15916.3804.460155.937665@guru.mired.org> <1043094762.13652.9.camel@localhost> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: Mike Meyer X-Delivery-Agent: TMDA/0.68 (Shut Out) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In <1043094762.13652.9.camel@localhost>, Stacey Roberts typed: > Hello, > > On Mon, 2003-01-20 at 14:59, Mike Meyer wrote: > > In <1043015655.51041.505.camel@localhost>, Stacey Roberts typed: > > > Hello, > > > After a fresh cvsup of my ports tree, I tried to update > > > jasper-1.500.4 using portupgrade, but it fails with errors below. > > > > The proper way to deal with port build failures is to first make sure > > you've got the latest version of the port. If you do and it still > > fails, do a "make maintainer", and send the error report to the email > > address that this prints. > I am not attempting to *build* the port, but update via portupgrade > (isn't that what its for?), which produced the failure. Unless told to do otherwise, portupgrade upgrades the package by building the port. What you posted looked like a build failure. > I *did* run "make maintainer" in that port's dir to obtain the > maintainer's e-mail address - who is cc'd on this post. If posting to > questions is not proper, then I apologize - however, I am not the only > one that does this, and this is the first time I've ever encountered > anyone having a problem with this. It's not a problem. Some build failures are systemic, and questions is the correct place to deal with them. Others are specific to a port, and the maintainer is the best place to get help. http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message