Date: Sun, 6 Nov 2005 23:36:27 +1100 From: Sam Lawrance <boris@brooknet.com.au> To: "Edwin L. Culp" <eculp@encontacto.net> Cc: freebsd-ports@freebsd.org Subject: Re: ANNOUNCE: GNOME 2.12.1 has been merged into the ports tree Message-ID: <C8D2F922-66F0-4653-B4AF-6F86F1675C1A@brooknet.com.au> In-Reply-To: <20051106052710.jn84zulfeo0k4g84@mail.encontacto.net> References: <1131176568.3960.20.camel@shumai.marcuscom.com> <20051106052710.jn84zulfeo0k4g84@mail.encontacto.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/11/2005, at 10:27 PM, Edwin L. Culp wrote: > Quoting Joe Marcus Clarke <marcus@FreeBSD.org>: > > > >> Now that the freeze in preparation for FreeBSD 6.0 is over (an >> excellent >> release to be sure), it is my great pleasure (on behalf of the >> FreeBSD >> GNOME Team) to announce the general availability of GNOME 2.12 for >> FreeBSD. >> >> The official release notes for GNOME 2.12 can be found at >> http://www.gnome.org/start/2.12/notes/en/. FreeBSD-specific >> documentation can be found at http://www.FreeBSD.org/gnome/. The >> documentation has been updated, but it will be a little while >> before the >> website rebuilds. >> >> Upgrading from GNOME 2.10 to 2.12 is tricky. You should NOT use >> portupgrade by itself to do this upgrade. Instead, download the >> gnome_upgrade script from >> http://www.marcuscom.com/downloads/gnome_upgrade212.sh. This >> script is >> a wrapper for portupgrade that contains additional logic to steer >> clear >> of some potential pitfalls with the upgrade. >> >> > Hello, > > It is always nice to know what you should have done;) > > A little late, I'm afraid, but when using the script is being used > and the upgrade fails because of a power outage after the ports > have been uninstalled and not rebuilt, what is the correct > proceedure to follow? > > I reiniciated the update by reexecuting gnome_upgrade212.sh -f and > it seems as though I'm going to loose some ports that were deleted > during the first execution. When I realized that was a posiblity, > I checked the -h option and saw -restart <list filename> that I > should add as an argument and don't know where <list filename> > might be or if I should have created it before iniciating the > upgrade process. > > Something like this: sh gnome_upgrade212.sh -restart /var/tmp/gnome_upgrade_lst.XXXXXX
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C8D2F922-66F0-4653-B4AF-6F86F1675C1A>