Date: Wed, 19 Mar 2014 18:09:43 +0100 From: Kurt Jaeger <lists@opsec.eu> To: "Dr. Peter Voigt" <pvoigt@uos.de> Cc: freebsd-ports@freebsd.org Subject: Re: Update of quazip-0.5.1 to quazip-0.6.2 fails Message-ID: <20140319170943.GP53062@home.opsec.eu> In-Reply-To: <20140319174857.40e83d09@tiger2008.drpetervoigt.private> References: <20140319140512.6035e0d5@tiger2008.drpetervoigt.private> <20140319133614.GO53062@home.opsec.eu> <20140319174857.40e83d09@tiger2008.drpetervoigt.private>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > > > 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 ? 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 > 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. 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. -- pi@opsec.eu +49 171 3101372 6 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140319170943.GP53062>