From owner-freebsd-ports@FreeBSD.ORG Tue Jun 2 03:44:27 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D34F2E3C for ; Tue, 2 Jun 2015 03:44:27 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from nm28.bullet.mail.bf1.yahoo.com (nm28.bullet.mail.bf1.yahoo.com [98.139.212.187]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 936B1195E for ; Tue, 2 Jun 2015 03:44:27 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1433216660; bh=bFrYIiZwsrDHZ9chq7iUFGCcjQ4zH93RarKZHJXFAqI=; h=Date:From:To:Subject:References:In-Reply-To:From:Subject; b=j0Cp+E6qx0QtO4OIwgJ4pY6/oVkyO9JWOCbYlzEof7Uwgjx1AZoP+8qya2BmliOMaSz58adyNScd1HUwZqhLAsRwe2r9TQDNhE66/LNvaSSvTVbUmgjxJzmQDGP+nO/FXLdwJP87pI8BHMyaa/IKPQyLtJf9QMms6LJk15kV7qhUO45uxxO3K+NRBQcXr06zjSOxJ1MVqYHDjjUrh4TgEO7cEgjztfOhM0ggXdu3JAo5gYyv+nywDjJ3jZkKF0LCrakeUb8ZGjaOXc9KT4VVJhchYFkzCUbWVexydns8xBYddvz+kIQPzpDIcdSnkrAtzUmzFeTXEQgOf48IMXSfxQ== Received: from [98.139.214.32] by nm28.bullet.mail.bf1.yahoo.com with NNFMP; 02 Jun 2015 03:44:20 -0000 Received: from [68.142.230.75] by tm15.bullet.mail.bf1.yahoo.com with NNFMP; 02 Jun 2015 03:44:20 -0000 Received: from [127.0.0.1] by smtp232.mail.bf1.yahoo.com with NNFMP; 02 Jun 2015 03:44:20 -0000 X-Yahoo-Newman-Id: 208790.88365.bm@smtp232.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: Zl8HR3kVM1ksC6yawP__Z7.t8_xMXcSQWjhRRv80fOVm9hp sAl4pxBMKdcXf49Tq_Cqp32LNekidHFBkqhx2agxh9HrK9WykteHGYCatOD9 boAu3ypuejz3LxOb_cLBrvkhbmyZ4ZoLKV18EjTP1PsOBQ9qpLeVRjOUQQVK vawfdfv0KNTlnAw_HpbyhAKimutdJBntZnXjvlSdbQyA3tJxYNj3fvuKDTFn PVqeIIYT6kcjnSjKHKY3xQdIa.Hd49LAEHDf9Qh5kxRXnhhlqYKvQAwKxU7f uS.IwJhsfs_01ILc7Psax6cuTXEP7kUhmqXkFY8RtgfGCwUY8BZ94A0T5iOQ 48g1W1IUKMMq5a.KoPlsA_BBWHxrX_9oga7w5f0f2mtSLYG1MLVWiRXXp1dr s1sGYRcFkj4scTF5i0.v21q71tIBPnLrDIX_i0XGD6AfoaK1gSeLHoqG3Vkx pBDSEKLPuBZlgHjlwh1mtXseF69gk.24KgTFxpcADXrlNRrApivoOzK0bTvQ CJUcq9huOd8wnR3cSfzpkghjJ7WyVIAjxoboimA-- X-Yahoo-SMTP: 6IZaPQyswBAeyzp3urHRlQfBxGxx4Js3YAIn Message-ID: <556D264A.7070107@yahoo.com> Date: Mon, 01 Jun 2015 20:43:06 -0700 From: Jeffrey Bouquet User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: SOLVED: pkg version mismatch [succeeds port...] References: <1433158692.84575.YahooMailBasic@web140904.mail.bf1.yahoo.com> <44iob7upiu.fsf@lowell-desk.lan> In-Reply-To: <44iob7upiu.fsf@lowell-desk.lan> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2015 03:44:27 -0000 On 06/01/15 13:44, Lowell Gilbert wrote: > [pkg@ snipped, because it's irrelevant] > > Jeffrey Bouquet via freebsd-ports writes: > >> I noticed the ports tree here had net/uget 1.10.4_1 even after "svn up"... while >> pkg upgrading installed 2.0. "pkg version" (one of 3 ways) reported >> "succeeds port"... was about to post a question about pkg, but it can be fixed >> by >> >> cd /usr/ports/net/uget >> svn revert . -R >> >> [found at stackoverflow] >> >> [I've about thirty of so of those directories to fix up, for installed ports... it seems]. >> >> Wondering if the fix can be put in CAVEATS or something in the pkg version >> man page... "for those using subversion..." >> >> also if ever a man page with many examples is crafted for subversion on FreeBSD, >> that could be one of them. >> >> Others: >> >> cd /usr/ports >> svn resolve . > These would not be useful to document unless you can document how you > got into those situations in the first place. I think it was disk failure and svn did not like resuming the updates to the directories newly crafted into a everyday install type system from backup. [ I prefer keeping the same tree across years of updates because I am used to saving build logs, .htm and .msg and .txt hint files, etc within the directories. ... for easier reference] > "svn revert" is only > necessary if you made local changes to the sources under svn control, I typically use it to build, ports, say, that are broken due to no fetch possible, for which I already have the sources, so I can "svn revert Makefile" and similar uses. > and even then usually if svn can't automatically merge upstream changes > into yours. "svn resolve" is the way to sort out the merge if svn can't > do it. Just a few days ago I used "svn resolve" to tune the ports tree. Maybe the side effects of that, and/or the response I type to the svn questions (always TC, always r, for those familiar with the two types...text and tree, respetively) are what causes the version mismatches that were present. [ OR the situation in the first paragraph above. ] Part of a daily svn log: ............................................................................ Updating 'usr/ports': ......................... [snipped] Summary of conflicts: Text conflicts: 0 remaining (and 2 already resolved) Tree conflicts: 0 remaining (and 2 already resolved) .................................................................................................................. I tend to annotate uses into hint files (.txt .msg .dat .how .htm) in /usr/src RE svn Has saved a ports tree from newly needing to be downloaded more than once > > It sounds like you're not intending to make local changes at all. In > that case, I'd recommend you use something else (probably portsnap) to > maintain your ports tree. I think, am not sure, that portsnap and svn are the only two. I prefer the more cvs-like workings of svn, and have never used portsnap... I think the former enables one more fine-grained tuning unless one knows the workings of the latter. I could be wrong but... Just information for the list... as a followup. Not wanting to prolong the thread without reason..... > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"