On 8/25/2013 2:39 PM, Carmel wrote:
> Using "portupgrade-devel-20130718,3" installed from the ports system,
> attempting to update "texlive-base" always ends like this:
>
> ---> Build of print/texlive-base ended at: Sun, 25 Aug 2013 15:25:25 -0400
>
2013/8/25 Carmel :
> Using "portupgrade-devel-20130718,3" installed from the ports system,
> attempting to update "texlive-base" always ends like this:
>
> ---> Build of print/texlive-base ended at: Sun, 25 Aug 2013 15:25:25 -0400
> (consumed 00:1
Using "portupgrade-devel-20130718,3" installed from the ports system,
attempting to update "texlive-base" always ends like this:
---> Build of print/texlive-base ended at: Sun, 25 Aug 2013 15:25:25 -0400
(consumed 00:11:57)
---> Updating dependency info
---> Modif
Hi,
Is gettext 0.18.3 less forgiving than previous versions?
Or are some of the translations encoded wrong?
I even tried twice to forcefully upgrade everything depending on
converters/libiconv, e.g. portupgrade -fprv converters/libiconv, but
that didn't make a difference.
Is there anyth
On Fri, 11 Jan 2013 15:50:56 +, Matthew Seaman wrote:
> On 11/01/2013 15:18, Walter Hurry wrote:
>> On Thu, 10 Jan 2013 01:50:34 +, Walter Hurry wrote:
>>
>>> Thank you yet again, Matthew. As always, you are a fount of knowledge.
>>>
>>> The guidance on LATEST_LINK has helped a great deal
On 11/01/2013 15:18, Walter Hurry wrote:
> On Thu, 10 Jan 2013 01:50:34 +, Walter Hurry wrote:
>
>> Thank you yet again, Matthew. As always, you are a fount of knowledge.
>>
>> The guidance on LATEST_LINK has helped a great deal. I still have a
>> further question or two though; I shall follow
On Thu, 10 Jan 2013 01:50:34 +, Walter Hurry wrote:
> Thank you yet again, Matthew. As always, you are a fount of knowledge.
>
> The guidance on LATEST_LINK has helped a great deal. I still have a
> further question or two though; I shall follow up within a day or two.
Just one further quest
On Wed, 09 Jan 2013 18:54:35 +, Matthew Seaman wrote:
> On 09/01/2013 18:31, Walter Hurry wrote:
>> I am using pkgng.
>>
>> When I issue 'portupgrade -p', after build and installation,
>> it builds a new package, as advertised. This (by default) is
On 09/01/2013 18:31, Walter Hurry wrote:
> I am using pkgng.
>
> When I issue 'portupgrade -p', after build and installation, it
> builds a new package, as advertised. This (by default) is put into /usr/
> ports/packages/All.
>
> At the same time, it installs
I am using pkgng.
When I issue 'portupgrade -p', after build and installation, it
builds a new package, as advertised. This (by default) is put into /usr/
ports/packages/All.
At the same time, it installs a set of symlinks; one for each relevant
port category, plus one in /usr/port
On 10/28/2012 04:27 PM, Patrick Lamaiziere wrote:
pkg is able to make packages upgrade by itself. I think the good way
to update with packages is "pkg updgrade" then portupgrade to build the
ports without packages avalaible.
Anyway I had many problems with portupgrade and pkg (basica
Got it.
Thanks.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Le Sat, 27 Oct 2012 21:22:32 +0300,
Alexander Kapshuk a écrit :
> Having done all of the above, I ran portupgrade to update all the
> pkgs that needed upgrading on my system, and got the message below:
> root@box0:/root/tmp # portupgrade -varRP --batch -L '%s_%s'
> USING PK
anting to use pkgng for binary packages, there's no need to
>> use portupgrade anymore. Just 'pkg install name', 'pkg upgrade', etc.
>>
> Understood. Thanks.
>
> For some reason I thought I could use the PKGNG tool set together with
> portupgrade the
On 10/28/2012 03:00 AM, Bryan Drewery wrote:
PKGNG is a replacement for the pkg_* tools that record package data in
/var/db/pkg.
It also allows for binary package upgrades.
If you are wanting to use pkgng for binary packages, there's no need to
use portupgrade anymore. Just 'pkg in
On 10/27/2012 1:22 PM, Alexander Kapshuk wrote:
> Quick question about portupgrade's support for pkgng.
>
> The /usr/ports/UPDATING says:
> 20121015:
> AFFECTS: users of ports-mgmt/portupgrade
> AUTHOR: bdrew...@freebsd.org
>
> Portupgrade now supports pkgn
If my reading the code snippet below is right, portupgrade-2.4.10.2 does
not support pkgng yet if pkgdb has been converted for use with pkgng
using pkg2ng.
/usr/ports/ports-mgmt/portupgrade/work/pkgtools-2.4.10.2/bin/portupgrade:561,565
# FIXME: pkgng
if $use_packages
Quick question about portupgrade's support for pkgng.
The /usr/ports/UPDATING says:
20121015:
AFFECTS: users of ports-mgmt/portupgrade
AUTHOR: bdrew...@freebsd.org
Portupgrade now supports pkgng. To use pkgng, enable it in your
make.conf,
and convert your databases.
Th
nc folder as well, to do a manual update
regards,
David Whytcross
- Original Message -
From: "Robert Huff"
To:
Sent: Saturday, August 04, 2012 4:08 AM
Subject: boinc_gui missing after portupgrade
Robert Huff writes:
> I am now missing boinc_gui from /usr/local/bin
&
Robert Huff writes:
> > I am now missing boinc_gui from /usr/local/bin
> >
> > any ideas as to how to get it back ?
>
> I believe the literal answer is "downgrade". :-(
> The more useful answer is "it has been replaced by
> 'boincmgr'". hich, unfortunately, does not seem t
David Whytcross writes:
> I just performed a portupgrade on 9.0-RELEASE to the
> boinc-setathome-enhanced port, which took boinc-client from
> boinc-client-6.4.5_7 to boinc-client-7.0.25_4
>
> I am now missing boinc_gui from /usr/local/bin
>
> any ideas as
Hi guys,
I just performed a portupgrade on 9.0-RELEASE to the boinc-setathome-enhanced
port, which took boinc-client from boinc-client-6.4.5_7 to boinc-client-7.0.25_4
I am now missing boinc_gui from /usr/local/bin
any ideas as to how to get it back ?
Dave Whytcross
On Mon, 25 Jun 2012 00:53:50 -0700 (PDT)
Dan Mahoney, System Admin wrote:
> Hey there,
>
> I'm presently in the process of trying to do a portupgrade from
> rt-3.8.8 to 3.8.13. By all estimations, this is a minor bump.
>
> Already, I've encountered several annoyan
On 2012-06-25 11:47, John Levine wrote:
You would think there's an option to portupgrade that says "don't
upgrade
every single package I've got, but if somewhere in the dependency
chain I
need a newer version of a thing, then do it."
The problem is that the versi
>You would think there's an option to portupgrade that says "don't upgrade
>every single package I've got, but if somewhere in the dependency chain I
>need a newer version of a thing, then do it."
The problem is that the versioning in the ports system doesn&#
On 06/25/12 09:53, Dan Mahoney, System Admin wrote:
Hey there,
I'm presently in the process of trying to do a portupgrade from rt-3.8.8
to 3.8.13. By all estimations, this is a minor bump.
Already, I've encountered several annoyances due to ABI changes, such as
the libtool2.4
On 06/25/12 10:40, Andrea Venturoli wrote:
On 06/25/12 09:53, Dan Mahoney, System Admin wrote:
Hey there,
I'm presently in the process of trying to do a portupgrade from rt-3.8.8
to 3.8.13. By all estimations, this is a minor bump.
Already, I've encountered several annoyances
On 25/06/2012 08:53, Dan Mahoney, System Admin wrote:
> I'm presently in the process of trying to do a portupgrade from rt-3.8.8
> to 3.8.13. By all estimations, this is a minor bump.
>
> Already, I've encountered several annoyances due to ABI changes, such as
> the lib
On 6/25/12 9:53 AM, Dan Mahoney, System Admin wrote:
> Hey there,
>
> I'm presently in the process of trying to do a portupgrade from rt-3.8.8
> to 3.8.13. By all estimations, this is a minor bump.
>
> Already, I've encountered several annoyances due to ABI chang
Hey there,
I'm presently in the process of trying to do a portupgrade from rt-3.8.8
to 3.8.13. By all estimations, this is a minor bump.
Already, I've encountered several annoyances due to ABI changes, such as
the libtool2.4 fun. With normal portupgrade, this forces you to g
On Sat, 09 Jun 2012 20:46:49 +, Walter Hurry wrote:
> On Sat, 09 Jun 2012 18:12:25 +0100, Dave Morgan wrote:
>
>> On 09/06/12 at 04:41P, Walter Hurry wrote:
>>> FreeBSD 9 on x86_64.
>>>
>>> I am in the process of doing a portupgrade on libreoffice
On Sat, 09 Jun 2012 18:12:25 +0100, Dave Morgan wrote:
> On 09/06/12 at 04:41P, Walter Hurry wrote:
>> FreeBSD 9 on x86_64.
>>
>> I am in the process of doing a portupgrade on libreoffice (from 3.4.4
>> to 3.5.2.5). During the build it has (so far) errored out 4 times,
On 09/06/12 at 04:41P, Walter Hurry wrote:
> FreeBSD 9 on x86_64.
>
> I am in the process of doing a portupgrade on libreoffice (from 3.4.4 to
> 3.5.2.5). During the build it has (so far) errored out 4 times, in the
> following modules:
>
> vcl
> framework
> sfx2
>
FreeBSD 9 on x86_64.
I am in the process of doing a portupgrade on libreoffice (from 3.4.4 to
3.5.2.5). During the build it has (so far) errored out 4 times, in the
following modules:
vcl
framework
sfx2
tail_build
Each time, it told me to go into the subdirectory, do a gmake clean and a
On 25 May 2012 12:10, Gary Aitken wrote:
> Has to be something stupid:
>
> 347 /usr/ports#pkg_version -v | grep updating
> p5-XML-Twig-3.39 < needs updating (port has 3.40)
>
> 348 /usr/ports#portupgrade -Rv P5-XML-Twig
> ---> Session started at
Has to be something stupid:
347 /usr/ports#pkg_version -v | grep updating
p5-XML-Twig-3.39< needs updating (port has 3.40)
348 /usr/ports#portupgrade -Rv P5-XML-Twig
---> Session started at: Fri, 25 May 2012 10:03:54 -0600
[Exclude up-to-date packages done]
** No
now installs some files formerly
installed by
X-S
the package for X-S must be deinstalled before updating X-S.
# pkg_delete -fx p5-XML-SAX
# portmaster textproc/p5-XML-SAX
(users of pkgng can substitute pkg_delete with pkg delete)
But what is the instruction for users of portupgrade
installed by
X-S
the package for X-S must be deinstalled before updating X-S.
# pkg_delete -fx p5-XML-SAX
# portmaster textproc/p5-XML-SAX
(users of pkgng can substitute pkg_delete with pkg delete)
But what is the instruction for users of portupgrade
On Sunday 29 April 2012, dgmm wrote:
> When running portupgrade -cfa, is there any way to find out where it's up
> to and/ot what is still in the queue to be re-built?
Oops. It was obvious really.
ls /var/db/pkg -htU
...is good enough for my needs
When running portupgrade -cfa, is there any way to find out where it's up to
and/ot what is still in the queue to be re-built?
--
Dave
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questio
n dhert wrote:
> Today, my nightly run of portsnap informed me there is un update for:
> # pkg_version -vIL=
> portupgrade-2.4.9.3.2 < needs updating (index has 2.4.9.3_1,2)
>
> Since there is no special entry in /usr/ports/UPDATING about the
> portupgrade update,
On 23/04/2012 17:13, n dhert wrote:
Today, my nightly run of portsnap informed me there is un update
for: # pkg_version -vIL= portupgrade-2.4.9.3.2< needs updating
(index has 2.4.9.3_1,2)
=> SHA256 Checksum mismatch for pkgtools-2.4.9.3.tar.bz2.^M ===>
Giving up on fetching files:
Today, my nightly run of portsnap informed me there is un update for:
# pkg_version -vIL=
portupgrade-2.4.9.3.2 < needs updating (index has 2.4.9.3_1,2)
Since there is no special entry in /usr/ports/UPDATING about the
portupgrade update,
I started my weekly
# portupgrade -yaRrpb
this gi
On Wed, 11 Apr 2012 02:52:56 -0700
Cstdenis wrote:
> Portupgrade man page says "By default, portupgrade preserves shared
> libraries on uninstallation for safety."
>
> I ran i in the form of: portupgrade -b pcre
>
> Now /usr/local/lib/libpcre.so.0 does not exist a
Portupgrade man page says "By default, portupgrade preserves shared
libraries on uninstallation for safety."
I ran i in the form of: portupgrade -b pcre
Now /usr/local/lib/libpcre.so.0 does not exist anymore, only the new
/usr/local/lib/libpcre.so.
On 04/12/2011 20:07, Matthew Pounsett wrote:
> On 2011/12/04, at 14:13, Matthew Seaman wrote:
>
>> > 4) Now for the updating bit. I'm going to use portmaster's '-o'
>> > functionality to swap out the postgresql versions. (portupgrade
>> &
On 2011/12/02, at 05:19, Matthew Pounsett wrote:
> I was expecting the following to work:
> sudo portupgrade -rf -o databases/postgresql91-client
> databases/postgresql84-client
>
> However, I'm running into a problem where the ports makefiles, and by
> extension por
On 2011/12/04, at 14:13, Matthew Seaman wrote:
> 4) Now for the updating bit. I'm going to use portmaster's '-o'
> functionality to swap out the postgresql versions. (portupgrade
> has very similar functionality if you prefer that.) postgresql
>
> make deinstall
> That's the ports makefiles talking, isn't it? In order to do that
> deinstall I need to also remove all of the things that depend on
> it... portupgrade is supposed to help me do the in-place upgrade
> without removing everything else first.
>
> Even if I
-pay
>> attention here
>> *** Error code 1
>
>
> postgresql-client-8.4.8
>
> make deinstall
That's the ports makefiles talking, isn't it? In order to do that deinstall I
need to also remove all of the things that depend on it... portupgrade is
supposed t
2011/12/2 Matthew Pounsett :
>
> I'm trying to do a major version upgrade of postgres from 8.4 to 9.1. I've
> dumped the db and uninstalled the postgres-server port, and I'd like to use
> portupgrade to handle the client upgrade, since it has a number of
> depend
I'm trying to do a major version upgrade of postgres from 8.4 to 9.1. I've
dumped the db and uninstalled the postgres-server port, and I'd like to use
portupgrade to handle the client upgrade, since it has a number of dependencies
that probably should be recompiled against the
x27;lib/perl5/5.14.1/man/man3/inc::latest.3.gz': Permission denied
[..]
** Command failed [exit code 2]: /usr/bin/script -qa
/tmp/portinstall2007-84470-1midf4x-0 /usr/bin/env UPGRADE_TOOL=portupgrade
UPGRADE_PORT=p5-Module-Build-0.3800_1 UPGRADE_PORT_VER=0.3800_1
/usr/sbin/pkg_add
On Wed, 2011-08-24 at 11:20 +, o...@aloha.com wrote:
> I too am stuck in ruby-portupgrade swamp :-)
>
> After a fresh install of FreeBSD 8.2 I built potupgrade, then did a
> portsnap and a portupgrade -a, in preparation to install Gnome2. When it
> stopped I followed the
I too am stuck in ruby-portupgrade swamp :-)
After a fresh install of FreeBSD 8.2 I built potupgrade, then did a
portsnap and a portupgrade -a, in preparation to install Gnome2. When it
stopped I followed the instructions in UPDATING, but when I try to
upgrade portupgrade it fails because it
On 08/23/11 11:11, Stanislav Sedov wrote:
Are you sure you have the latest one (2.4.9.2_2,2).
If not, you can grab it from here:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/ports-mgmt/portupgrade/ (the page has a small
"download as a tarball" link
at the bottom).
You are right:
This ruby+portupgrade upgrade seems to be quite a mess. My systems
fetch new ports tree nightly and I upgrade during the day when I have
some spare time.
So, this morning my systems had the new ruby versions
and the UPDATING instruction, but not the new portupgrade port version
(not that it
On Tue, 23 Aug 2011 11:00:48 +0200
Andrea Venturoli mentioned:
> On 08/23/11 09:58, Stanislav Sedov wrote:
> > On Sun, 21 Aug 2011 15:18:28 +0200
> > Andrea Venturoli mentioned:
> >
> >> On 08/21/11 08:26, n dhert wrote:
> >>> I did a portupg
On 08/23/11 09:58, Stanislav Sedov wrote:
On Sun, 21 Aug 2011 15:18:28 +0200
Andrea Venturoli mentioned:
On 08/21/11 08:26, n dhert wrote:
I did a portupgrade on a freebsd 8.2-RELEASE
of the portupgrade program itself
portupgrade-2.4.8_1,2< needs updating (index has 2.4.9,2)
(t
On Sun, 21 Aug 2011 15:18:28 +0200
Andrea Venturoli mentioned:
> On 08/21/11 08:26, n dhert wrote:
> > I did a portupgrade on a freebsd 8.2-RELEASE
> > of the portupgrade program itself
> > portupgrade-2.4.8_1,2<needs updating (index has 2.4.9,2)
> > (that upg
On 08/21/11 08:26, n dhert wrote:
I did a portupgrade on a freebsd 8.2-RELEASE
of the portupgrade program itself
portupgrade-2.4.8_1,2<needs updating (index has 2.4.9,2)
(that upgraded also ruby to 1.9:
I did the same on some boxes and I'm having a lot of troubles too...
# pkgdb
I did a portupgrade on a freebsd 8.2-RELEASE
of the portupgrade program itself
portupgrade-2.4.8_1,2 < needs updating (index has 2.4.9,2)
(that upgraded also ruby to 1.9:
...
===> Cleaning for ruby-1.9.2.290,1
===> Cleaning for ruby19-bdb-0.6.6
===> Cleaning for
On 10/07/2011 14:02, Jerry wrote:
On Sun, 10 Jul 2011 00:35:28 -0400
b. f. articulated:
This is the tag that you would use on src collections to update your
base system sources (usually in /usr/src) to 8-STABLE. You would use
RELENG_8_2 for the 8.2-STABLE security branch, RELENG_8_2_RELEASE fo
> On Sun, 10 Jul 2011 00:35:28 -0400
>
> b. f. articulated:
> > This is the tag that you would use on src collections to update your
> > base system sources (usually in /usr/src) to 8-STABLE. You would use
> > RELENG_8_2 for the 8.2-STABLE security branch, RELENG_8_2_RELEASE for
> > 8.2-RELEASE,
On Sun, 10 Jul 2011 00:35:28 -0400
b. f. articulated:
> This is the tag that you would use on src collections to update your
> base system sources (usually in /usr/src) to 8-STABLE. You would use
> RELENG_8_2 for the 8.2-STABLE security branch, RELENG_8_2_RELEASE for
> 8.2-RELEASE, and so on.
Re
On 7/10/11, b. f. wrote:
> On 7/9/11, Thomas D. Dean wrote:
>> On Sat, 2011-07-09 at 19:54 -0400, b. f. wrote:
> You could cheat, and neither upgrade your base system nor make the
> changes I mentioned in my last message, but instead fool portupgrade
> into thinking that you
f ports via date=
instead of tag= (for details, see, for example, the csup(1) manpage.)
>
> After the build finishes, portupgrade should fetch from 8-stable.
I'm not sure what you mean here. As I wrote before, you need to make
some additional changes to ensure that portupgrade uses 8-stab
a typo on my part. The machine I used for email is not the
machine I am updating.
I am updating that machine, now. The supfile contains
*default release=cvs tag=RELENG_8
This should track 8-stable. Correct?
After the build finishes, portupgrade should fetch from 8-stab
es and variables
(for an example, see below).
>
> # Useful predefined functions:
> #
> # localbase()
> #Returns LOCALBASE.
> ...
>
> But, portupgrade still tries to fetch from 8.2-release.
If you are running 8.2-RELEASE, and yet wish to obtain "8-stable"
packages (whi
rameter, similar to the use of pkg_add -r in case of
> installation instead of update).
>
> But if you require the most recent ports tree, using CVS seems
> to be the better method. As you're updating binary, but with
> using the ports tree (portupgrade relies on that, pkg_add f
days ago, I cvsup'd the port tree with
> *default release-cvs tag=.
> ports-all
>
> Today,
> portsnap fetch extract
> ...
> portsnap fetch update
> ...
> portupgrade -PPRva
>
> Does the portsnap update the port tree relative to 8.2-release or
> 8-stable?
fetch extract
...
portsnap fetch update
...
portupgrade -PPRva
Does the portsnap update the port tree relative to 8.2-release or
8-stable? Or, did cvsup get ports from 8-stable?
Looks like 8-stable.
8-stablem4-1.4.16,1.tbz
8.2-release m4-1.4.15,1.tbz
Anyway, I can get there from here
T
ble" and try again.
>
>
>
Yes. My error. I did not completely remove 8.2-RELEASE when I edited
pkgtools.conf the 2nd time. I introduced this error when I typed the
fetch command. Sorry.
My original problem still exists: portupgrade fails with any out-of-date
package. I should
On Sat, 09 Jul 2011 11:33:00 -0700, Thomas D. Dean wrote:
> > /usr/bin/fetch -v
> 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz'
> looking up ftp.FreeBSD.org
> connecting to ftp.FreeBSD.org:21
> fetch:
> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8-S
On Sat, 2011-07-09 at 14:15 -0400, Chris Brennan wrote:
> On 7/9/2011 1:14 PM, Thomas D. Dean wrote:
> > As root, I attempted to use
> > portupgrade -PPRv m4
> > which attempted to access
> > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-
On 7/9/2011 1:14 PM, Thomas D. Dean wrote:
> As root, I attempted to use
> portupgrade -PPRv m4
> which attempted to access
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tbz
> but failed - File unavailable (e.g. file not found, no access)
>
As root, I attempted to use
portupgrade -PPRv m4
which attempted to access
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tbz
but failed - File unavailable (e.g. file not found, no access)
I changed etc/pkgtools.conf
OS_PKGBRANCH="8-STABLE
my machine:
>
> $ pkg_info -W /usr/local/bin/g-ir-scanner
> /usr/local/bin/g-ir-scanner was installed by package
> gobject-introspection-0.9.12_1
>
> So I suggest you do:
>
> # portupgrade -fv gobject-introspection
>
>
> Regards,
>
That did it, thanks!
--
--
installed by package
gobject-introspection-0.9.12_1
So I suggest you do:
# portupgrade -fv gobject-introspection
Regards,
--
Frank
Contact info: http://www.shute.org.uk/misc/contact.html
___
freebsd-questions@freebsd.org mailing list
http://list
... and the gstreamer upgrade blows up because of this:
/usr/local/bin/g-ir-scanner: not found
Ideas?
--
Tim Daneliuk
tun...@tundraware.com
___
freebsd-questions@freebsd.org mai
> startx command not found :(, no bash
> ran
> # pkg_add -r bash
> # pkg_add -r xfce4
>
> did not succeed, now ran to ports
> # cd /usr/ports/x11-wm/xfce4
> # make install clean
>
> and am stuck here. Hopefully this gets me back on my feet.
> Otherwise, it has been a big exercise :) and definitely
On Fri, May 6, 2011 at 9:59 PM, Antonio Olivares
wrote:
> On Fri, May 6, 2011 at 8:43 PM, Warren Block wrote:
>> On Fri, 6 May 2011, Antonio Olivares wrote:
>>>
>>> On Fri, May 6, 2011 at 1:52 PM, Antonio Olivares
>>>
>>> Sorry for TOP POSTING :(, but do I run
>>> # portmaster -a -f -D
>>>
>>> an
On Fri, May 6, 2011 at 8:43 PM, Warren Block wrote:
> On Fri, 6 May 2011, Antonio Olivares wrote:
>>
>> On Fri, May 6, 2011 at 1:52 PM, Antonio Olivares
>>
>> Sorry for TOP POSTING :(, but do I run
>> # portmaster -a -f -D
>>
>> and do an in place update of all ports?
>> is this the recommended wa
On Fri, 6 May 2011, Antonio Olivares wrote:
On Fri, May 6, 2011 at 1:52 PM, Antonio Olivares
Sorry for TOP POSTING :(, but do I run
# portmaster -a -f -D
and do an in place update of all ports?
is this the recommended way or nuking and rebuilding?
After the attempt to install every port, I'd
On Fri, 6 May 2011 13:57:01 -0500, Antonio Olivares
wrote:
> Sorry for TOP POSTING :(, but do I run
> # portmaster -a -f -D
>
> and do an in place update of all ports?
> is this the recommended way or nuking and rebuilding?
In case you did already remove all installed ports, you
need to install
On Fri, May 6, 2011 at 1:52 PM, Antonio Olivares
wrote:
> Warren,
>
> Sorry to ask, but what does one run after we run
> # portmaster -na
>
> I have cleared all questions and am ready to update, what magical
> command will do it?
>
> Thanks,
>
> Antonio
>
> On Fri, May 6, 2011 at 12:54 PM, Warren
Warren,
Sorry to ask, but what does one run after we run
# portmaster -na
I have cleared all questions and am ready to update, what magical
command will do it?
Thanks,
Antonio
On Fri, May 6, 2011 at 12:54 PM, Warren Block wrote:
> On Fri, 6 May 2011, Polytropon wrote:
>
>> Maybe it's much bet
On Fri, 6 May 2011, Polytropon wrote:
Maybe it's much better if you utilize the ports infra-
structure.
# cd /var/db/pkg
# pkg_delete -fad
or
# pkg_delete -f *
These are both equivalent to
# pkg_delete -a
___
freebsd-ques
# pkg_delete -f *
>
> This should remove all ports in a clean way. You can also
> remove stuff from /usr/ports/distfiles and /usr/ports/packages.
>
> Then make sure you have updated your ports tree. In case
> you also want an OS update, do it _now_ (i. e. prior to
>
On Fri, May 6, 2011 at 12:14 PM, Warren Block wrote:
> On Fri, 6 May 2011, Antonio Olivares wrote:
>
>> This is what I am running now ATM
>>
>> # cd /usr/ports/
>> # make clean build deinstall install
>>
>> Will it install all the ports? or only the ones that are installed?
>
> It's going to try
On Fri, 6 May 2011, Antonio Olivares wrote:
This is what I am running now ATM
# cd /usr/ports/
# make clean build deinstall install
Will it install all the ports? or only the ones that are installed?
It's going to try to install all 22,000 ports. That won't succeed due
to conflicts, but
d your ports tree. In case
you also want an OS update, do it _now_ (i. e. prior to
dealing with ports).
In case you keep using portupgrade (and therefore portinstall),
maybe in combination with pkg_add -r if you prefer - like
me :-) - installing binary packages, make sure that you
run BEF
book/updating-upgrading-freebsdupdate.html
>>
>> ran
>> # freebsd-update fetch
>> # freebsd-update install
>>
>> # portupgrade -af
>>
>> # freebsd-update -r 8.2-RELEASE upgrade
>>
>> then
>>
>> # freebsd-update install
>>
&
> Any suggestions to start over and get this done in a more efficient
> manner. Thinking of nuking OpenOffice
Done:)
grullahighschool# cd openoffice.org-3
grullahighschool# ls
Makefiledistinfofiles pkg-descr pkg-plist
grullahighschool# make deinstall
===> Deinstal
w.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html
>>
>> ran
>> # freebsd-update fetch
>> # freebsd-update install
>>
>> # portupgrade -af
>>
>> # freebsd-update -r 8.2-RELEASE upgrade
>>
>> then
>>
>> # freebsd-up
w.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html
>>
>> ran
>> # freebsd-update fetch
>> # freebsd-update install
>>
>> # portupgrade -af
>>
>> # freebsd-update -r 8.2-RELEASE upgrade
>>
>> then
>>
>> # freebsd-up
On Thu, 5 May 2011, Antonio Olivares wrote:
Dear all,
I was running FreeBSD 8.1 and am in the process of updating it
following advice in handbook:
http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html
ran
# freebsd-update fetch
# freebsd-update install
# portupgrade -af
On Thu, 5 May 2011, Chris Brennan wrote:
something to keep in mind portmaster does the same thing and all of
portupgrades switches work with portmaster,
portmaster doesn't have the same switches as portupgrade. Or, being
more precise, it has some of the same option flags, but they
an
> # freebsd-update fetch
> # freebsd-update install
>
> # portupgrade -af
>
> # freebsd-update -r 8.2-RELEASE upgrade
>
> then
>
> # freebsd-update install
>
> Tried to do this:
> # portupgrade -f ruby
> # rm /var/db/pkg/pkgdb.db
> # portupgrade -f ruby
t a system configured
the way you want, you can follow this idea and make a "portable
system" from that.
> So far it has not prompted me for any configurations. Had done that
> for two/three days with the previous command:
>
> # portupgrade -af
This will stop on any point
1 - 100 of 2237 matches
Mail list logo
