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

_1126 lists at elfsechsundzwanzig.de
Tue Jan 28 08:49:45 UTC 2014


On Mon, Jan 27, 2014 at 08:30:02PM +0800, Erich Dollansky wrote:
> 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.

I can see why a ports tree that is being checked out with svn instead
of being updated with portsnap might be a wise choice, but I'm not
quite sure if I understand correctly what the abilities of portupgrade
are that portmaster lacks? Do you want to elaborate on that? ;)


More information about the freebsd-questions mailing list