From owner-freebsd-ports@FreeBSD.ORG Wed Mar 19 19:15:17 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C3AB7BBC for ; Wed, 19 Mar 2014 19:15:17 +0000 (UTC) Received: from smtp-auth.serv.Uni-Osnabrueck.DE (vm135.rz.uni-osnabrueck.de [131.173.16.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4ADF09F for ; Wed, 19 Mar 2014 19:15:16 +0000 (UTC) Received: from hal9000.drpetervoigt.private (p5DC4C4C9.dip0.t-ipconnect.de [93.196.196.201]) (authenticated bits=0) by smtp-auth.serv.Uni-Osnabrueck.DE (8.13.8/8.13.8) with ESMTP id s2JJF1pS004647 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Mar 2014 20:15:02 +0100 Received: from tiger2008.drpetervoigt.private (tiger2008.drpetervoigt.private [192.168.1.96]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: pvoigt) by hal9000.drpetervoigt.private (Postfix) with ESMTPSA id 783321E0042; Wed, 19 Mar 2014 20:03:15 +0100 (CET) Date: Wed, 19 Mar 2014 20:03:14 +0100 From: "Dr. Peter Voigt" To: Kurt Jaeger Subject: Re: Update of quazip-0.5.1 to quazip-0.6.2 fails Message-ID: <20140319200314.0eb3df25@tiger2008.drpetervoigt.private> In-Reply-To: <20140319170943.GP53062@home.opsec.eu> References: <20140319140512.6035e0d5@tiger2008.drpetervoigt.private> <20140319133614.GO53062@home.opsec.eu> <20140319174857.40e83d09@tiger2008.drpetervoigt.private> <20140319170943.GP53062@home.opsec.eu> Organization: =?UTF-8?B?VW5pdmVyc2l0w6R0IE9zbmFicsO8Y2s=?= X-Mailer: Claws Mail 3.9.3 (GTK+ 2.22.1; x86_64-unknown-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.12.6.90315 (Univ. Osnabrueck) X-PMX-Spam: Gauge=IIIIIIII, Probability=8%, Report= EU_TLD 0.1, HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, FROM_NAME_PHRASE 0, RDNS_POOLED 0, RDNS_SUSP 0, RDNS_SUSP_SPECIFIC 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_MSGID 0, __HAS_REPLYTO 0, __HAS_X_MAILER 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __RDNS_POOLED_10 0, __REPLYTO_SAMEAS_FROM 0, __REPLYTO_SAMEAS_FROM_ACC 0, __REPLYTO_SAMEAS_FROM_ADDY 0, __REPLYTO_SAMEAS_FROM_DOMAIN 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __SUBJ_ALPHA_NEGATE 0, __TO_MALFORMED_2 0, __URI_NS X-PMX-Spam-Level: IIIIIIII Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: "Dr. Peter Voigt" List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Mar 2014 19:15:17 -0000 Am Wed, 19 Mar 2014 18:09:43 +0100 schrieb Kurt Jaeger : > Hi! Hi kurt, > > > > > I am running 10.0-RELEASE and when trying to upgrade > > > > quazip-0.5.1 to quazip-0.6.2 after latest update of the ports > > > > tree I obtain the following error: > > > > Please deinstall the old quazip before building the new port. > > > thanks for your feedback. However, I am not sure, if I've got you > > right: Currently BUILDING of the new quazip version fails. How can > > deinstallation of the old version correct this behavior? > > The build imports some definitions from old .h files or so ? OK that helps. > > I saw the same problem, deinstalled the old version, build and > it worked. There are cases where ports have this kind of quirk. > Sometimes, it's documented in /usr/ports/UPDATING. > > > And if I force uninstallion of the old version and if subsequently > > building of the new version should fail, I will be left with broken > > dependencies: > > You are right, that might be a problem. You can handle it this way: > > Create a package file: > > pkg create quazip-0.5.1 > > It will create a quazip-0.5.1.txz in the working directory. > > Then deinstall, and if the build fails, re-add the old pkg: > > pkg add quazip-0.5.1.txz > Yeah, thanks. I have learned a lot about pkg(ng) and packages. I did create the backup package but did not need it, because installation of new quazip version went smoothly. > > Thanks for doing so. I am rather new to FreeBSD and do not yet know, > > when there is time to directly contact a port maintainer. Until now > > I have first reported an issue to the forum or the mailing list. > > And in a second step I have informed the corresponding port > > maintainer. Is this the recommended way to proceed? > > In general, informing the maintainer, probably generating a > problem-report (using the command send-pr) is the correct way. > Ah, I have not been aware of the existence of this command. I'v used in the past a more unformal way of sending an email containing the - in my opinion - relevant information. > > In that special case > > http://www.freshports.org/archivers/quazip/ > > shows that the update was done after the maintainer failed to approve > the update. So in this particular case informing him might be > superfluous. > Well, I am obviously not much trained in reading the commit history. I would conclude from the last entry "17 Mar 2014 15:54:23" and "Approved by: maintainer timeout (nivit, >4 weeks)" that the maintainer did not approve the commit and thus the commit remained untested. Can one conclude from this that the maintainer is aware of problems without reporting them? I cannot read that the maintainer "failed to approve". Or can I assume for sure every port maintainer has subscribed to this this mailing list? Please give me a hint, if I have got the wrong information. Regards, Peter