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.
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.
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
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
and
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)
I changed
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-1.4.16,1.tbz
but failed - File
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:
On Sat, 2011-07-09 at 20:47 +0200, Polytropon wrote:
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:
On Sat, 2011-07-09 at 12:05 -0700, Thomas D. Dean wrote:
Sorry to answer my own post.
The packages that are out-of-date on the system I was updating are in
relationship to 8.2-release.
A couple days ago, I cvsup'd the port tree with
*default release-cvs tag=.
ports-all
Today,
portsnap fetch
On Sat, 09 Jul 2011 12:32:12 -0700, Thomas D. Dean wrote:
On Sat, 2011-07-09 at 12:05 -0700, Thomas D. Dean wrote:
Sorry to answer my own post.
The packages that are out-of-date on the system I was updating are in
relationship to 8.2-release.
A couple days ago, I cvsup'd the port tree
On Sat, 2011-07-09 at 21:45 +0200, Polytropon wrote:
If I understood everything correctly, CVS (csup) and portsnap
do both follow the one tree which gets frequently updated,
and by the tag specified above you'll always get the current
version of the tree. Getting older versions (e. g. the
Thomas D. Dean wrote:
...
For the most recent try, I have
...
# OS_PATCHLEVEL:-p8
# OS_PLATFORM:i386 amd64
# OS_PKGBRANCH: 7-current 6.1-release
OS_RELEASE=8-STABLE
OS_BRANCH=STABLE
OS_PKGBRANCH=8-stable
The comments above were not
On Sat, 2011-07-09 at 19:54 -0400, b. f. wrote:
occasionally trip over problems that will require intervention. (Note
that in the section of the csup file that you reproduced in an earlier
message, 'release-cvs' should be 'release=cvs'.)
The '-' was a typo on my part. The machine I used for
On 7/9/11, Thomas D. Dean tomd...@speakeasy.org wrote:
On Sat, 2011-07-09 at 19:54 -0400, b. f. wrote:
occasionally trip over problems that will require intervention. (Note
that in the section of the csup file that you reproduced in an earlier
message, 'release-cvs' should be 'release=cvs'.)
On 7/10/11, b. f. bf1...@googlemail.com wrote:
On 7/9/11, Thomas D. Dean tomd...@speakeasy.org 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
Hi all...easy question for someone. I'm starting to use one machine
to make my ports and system on and NFS mount and install from that one
central machine. I'm trying to use make package and make
package-recursive for ports...but is there a way to have it NOT try
to install the port, just make
Brian McCann wrote:
Hi all...easy question for someone. I'm starting to use one machine
to make my ports and system on and NFS mount and install from that one
central machine. I'm trying to use make package and make
package-recursive for ports...but is there a way to have it NOT try
to install
Hi,
Background - All was well until the boss upgraded the glibc on the
RedHat server which made all kinds of things unhappy. Taking the
opportunity to convert yet another server here to FreeBSD, I built a new
DNS on FreeBSD 4.9.
I have noticed a couple of odd things.
Typing in
Background - All was well until the boss upgraded the glibc on the
RedHat server which made all kinds of things unhappy. Taking the
opportunity to convert yet another server here to FreeBSD, I built a new
DNS on FreeBSD 4.9.
I have noticed a couple of odd things.
Typing in /usr/sbin/named -v,
Brian Henning [EMAIL PROTECTED] writes:
when performing a 'make package' does that grab all the dependencies for that
package so when you go to install the package it doesn't ask for dependencies?
No. It should be pretty easy to ask it to build packages for the
dependencies too, though.
On Wed, Sep 24, 2003 at 10:55:59AM -0400, Lowell Gilbert wrote:
Brian Henning [EMAIL PROTECTED] writes:
when performing a 'make package' does that grab all the dependencies for that
package so when you go to install the package it doesn't ask for dependencies?
No. It should be pretty
Greetings:
when performing a 'make package' does that grab all the dependencies for that
package so when you go to install the package it doesn't ask for dependencies?
thanks,
brian
___
[EMAIL PROTECTED] mailing list
22 matches
Mail list logo
