[freebsd-questions] Re: [freebsd-questions] Re: weird error messages with various ports

Charlie cwr at SDF.ORG
Wed Jan 29 14:06:47 UTC 2014

On Mon, 27 Jan 2014, Erich Dollansky wrote:

> Date: Mon, 27 Jan 2014 20:30:02 +0800
> From: Erich Dollansky <erichsfreebsdlist at alogt.com>
> To: _1126 <lists at elfsechsundzwanzig.de>
> Cc: freebsd-questions at freebsd.org
> Subject: Re: [freebsd-questions] Re: [freebsd-questions] Re: weird error
>     messages with various ports
> Hi,
> On Mon, 27 Jan 2014 13:10:12 +0100
> _1126 <lists at elfsechsundzwanzig.de> wrote:
>> On Mon, Jan 27, 2014 at 08:03:26PM +0800, Erich Dollansky wrote:
>>> On Mon, 27 Jan 2014 12:49:19 +0100
>>> _1126 <lists at elfsechsundzwanzig.de> wrote:
>>>> On Mon, Jan 27, 2014 at 07:18:58PM +0800, Erich Dollansky wrote:
>>>>> On Mon, 27 Jan 2014 12:05:19 +0100
>>>>> lists at elfsechsundzwanzig.de wrote:
>>>>>> This is my first posting on this mailinglist, so I hope I am
>>>>>> doing everything ok.
>>>>> do not worry to much about this.
>>>>>> I am running a 10.0-RELEASE on a Thinkpad X220 - and
>>>>>> everything was just fine.
>>>>> I do the same.
>>>>>> Until I did a
>>>>>> $ sudo portsnap fetch update
>>>>>> today and afterwards a
>>>>>> $ sudo portmaster -aD
>>>>> I did nearly the same either yesterday night or this morning
>>>>> but I used svn and portupgrade without any problems.
>>>>> How old was your ports tree before the upgrade?
>>>> Three days old.
>>> ok, get the latest one and try again. If it still does not work, I
>>> could give you the revision number of my working ports tree.
>> It still does not work. However, I do not have a revision number,
>> IIUC, because I'm updating my ports with portsnap and not with svn,
>> right? I might try to checkout ports anew and see whether that works
>> then.
> of course.
> You might should consider to switch to svn and portupgrade. There is
> one advantage of this pair. Portupgrade does not leave you with a
> machine that cannot be used anymore. The worst case is that no port
> gets upgraded but your machine still works. Svn has the advantage that
> you can chose your port 'version' if the current revision does not work
> for you.
> Anyway, some other reported the same problem with a current ports tree.
> I have the revision number 341159 in case of you want to try.
> Erich
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"

I might suggest you look into poudriere if you are concerned about not 
breaking a system by doing port upgrades. Poudriere is an awesome tool 
that allows you to build packages and essentially maintain your own local 
package repo.

So, on your desktop (or whatever) machine that you want to keep running 
smoothly, you would simply use 'pkg' to install and upgrade everything. 
You would use poudriere to build the packages from ports. The advantages 
being: if a port breaks during build, your system will remain untouched. 
You just wait for the problem to be fixed, then rebuild your packages. 
Once the packages are built successfully, you can upgrade your system. The 
second advantage being that if you have several machines to maintain, you 
no longer have to wait for each one to build ports. Just build once using 
poudriere, fire up a web server to host the package repo, and point all 
the machines at that repo. Build once, install many!


cwr at sdf.org
SDF Public Access UNIX System - http://sdf.org

More information about the freebsd-questions mailing list