Displaying 20 results from an estimated 90 matches for "portupgraded".
Did you mean:
portupgrade
2003 May 27
2
portupgrade issue 4.8-STABLE
Hi all,
Having a bit of a problem with portupgrade on a -STABLE machine:
[root@erwin]/root: portupgrade -aRn
---> Session started at: Tue, 27 May 2003 22:54:00 +1000
closed stream
---> Session ended at: Tue, 27 May 2003 22:54:01 +1000 (consumed 00:00:01)
[root@erwin]/root:
pkgdb -F does the same thing. Any clues?
cheers,
Rob
[root@erwin]/root: uname -a
FreeBSD erwin.number6
2003 Jul 21
1
portupgrade -PP needs glasses ?
does anybody have the same problem as I have :
(running CURRENT, but the problem occurs on STABLE too)
latest portupgrade, ports cvsuped today.
fully reproductible with any package...
am i missing something ? i hope yes...
portinstall -PP teTeX
---> Checking the availability of the latest package of 'print/teTeX'
---> Fetching the package(s) for 'teTeX-2.0.2_2'
2003 Nov 04
10
portupgrade and PHP
Hello,
When I run portupgrade -ra and PHP needs upgrading I am faced with
having to select all the options I want PHP compiled with (again). I
hate this.
How can I continually compile PHP with the same options as the last time?
Thanks!
Rick
2003 Apr 25
4
ruby & portupgrade
I am trying to do an install of portupgrade. As root, I go to
/usr/ports/sysutils/portupgrade and run
make install distclean
The system seems to obtain the pkgtools and some upgrades to it, but is
unable to obtain the required bdb1-0.1.8.tar.gz.
I have also looked at the collection at the freebsd site and tried the
ftp site myself
2007 Sep 06
1
freebsd and latest non-devel port installations
hi,
i''ve run into somewhat of a snag with my puppet instances: when i try to
have puppet install a port via portupgrade, it seems to step up each
version in ports to the latest, if there are multiple versions. i''ve run
into this with two ports so far: vim and postfix.
my package line is:
package { postfix: ensure => latest }
i am however able to specify the version
2007 Oct 01
5
freebsd ports provider patch to use ports tree directly
The included patch is what I''ve been able to throw together in a few
hours after studying the pkgtools code. All I''m using the library for at
the moment is to resolve the proper base location of the ports tree, but
at least by invoking make directly instead of through portupgrade it
works *a lot* better.
Is there a proper way to include/require a third party ruby library?
2010 Dec 16
3
Samba upgrade HowTo requested
Dear Samba friends,
Last weekend I decided to upgrade the samba server. We were running Samba
3.3 something and FreeBSD portupgrade was complaining that this version
should be removed and assumingly replaced by the newest version. I removed
the package via portupgrade and installed the 3.5.6 version. The upgrade
went quite smoothly in general, but I encountered some difficulties with
the printer
2010 Dec 16
3
Samba upgrade HowTo requested
Dear Samba friends,
Last weekend I decided to upgrade the samba server. We were running Samba
3.3 something and FreeBSD portupgrade was complaining that this version
should be removed and assumingly replaced by the newest version. I removed
the package via portupgrade and installed the 3.5.6 version. The upgrade
went quite smoothly in general, but I encountered some difficulties with
the printer
2013 Jun 26
4
portupgrade(1) | portmaster(8) -- which is more effective for large upgrade?
Greetings,
I haven't upgraded my tree(s) for awhile. My last attempt to rebuild after an updating
src && ports, resulted in nearly installing the entire ports tree, which is why I've
waited so long. Try as I might, I've had great difficulty finding something that will
_only_ upgrade what I already have installed, _and_ respect the "options" used during the
original
2013 Jul 03
1
curl and CVE-2013-2174
Dear members,
It may sound a silly question. I have curl installed:
# pkg_info |grep curl
curl-7.24.0_3 Non-interactive tool to get files from FTP, GOPHER, HTTP(S)
Today portsnap updated the ftp/curl port, and patch-CVE-2013-2174 appeared
in files/, but the port version remained such that portaudit, and
portupgrade still complain about curl's version. What is the recommended
way to
2003 Jul 08
4
Hardening production servers
Greetings,
Apologies if this is not the appropriate list, but my questions are about
best practices in maintaining production servers (so I believe I can justify
a post in -stable, short of a -release list :)
I maintain a modest installation of 6 FreeBSD servers. They're CVSUP'd to
RELENG_4_8 (I make buildworld on each individually) and I portupgrade ports
as necessary. In an attempt to
2003 May 19
1
fontconfig and FT_Get_BDF_Property
Hi all,
After upgrading my fontconfig to 2.2.0, fc-cache -vf gives me an error:
/usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libfontconfig.so.1: Undefined
symbol "FT_Get_BDF_Property" when it tries to build the cache for non
bitmapped fonts.
I have:
1. updated my CVS ports tree
2. rebuilt fontconfig, freetype, expat and Xft using portupgrade
(portupgrade -frR )
3. rebuilt my all
2003 May 26
1
portupgrade issue
I am running 4.8-STABLE.
I recently did a cvsup (repeatedly, most recently today). Ever since,
portupgrade dies with the following messages:
zircon# portupgrade -r pkgconfig
/usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:310:in `deorigin': failed to
convert nil into String (PkgDB::DBError)
from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:903:in
`tsort_build'
from
2007 Aug 12
4
freebsd ports provider
I''d like to clarify some points about the ports/package system in FreeBSD. I apoligize
ahead of time if this is
Both packages and ports use the pkgdb system. This isn''t some lame cludge; it''s by design,
and the reason is really quite simple. Packages are built from the ports collection. The
only real difference between them is the mode of delivery.
When you run
2006 May 22
12
FreeBSD Security Survey
Dear FreeBSD users and system administrators,
While the FreeBSD Security Team has traditionally been very good at
investigating and responding to security issues in FreeBSD, this only
solves half of the security problem: Unless users and administrators
of FreeBSD systems apply the security patches provided, the advisories
issued accomplish little beyond alerting potential attackers to the
2008 Feb 28
14
Upgrading to 7.0 - stupid requirements
In http://www.freebsd.org/releases/7.0R/announce.html says
Updating Existing Systems
> An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes
> a major version upgrade, so no matter which method you use to update
> an older system you should reinstall any ports you have installed on
> the machine. This will avoid binaries becoming linked to inconsistent
> sets
2003 May 25
3
Tracking 4-stable rather than 4.8-stable
Hi,
I would like to follow 4-stable on my FreeBSD box, and i can't fetch
binaries from /stand/sysinstall. Can anyone help me?
Here is how i did:
1) I installed 4.8-RELEASE from CD,
2) I used cvsup to upgrade. For this i used the stable-supfile as shown
in the Handbook.
=> My OS version as shown by 'uname -a' and '/stand/sysinstall' is
"4.8-STABLE".
It
2006 Sep 11
2
3.0.23b -> 3.0.23c
I portupgraded my working 3.0.23b PDC on FreeBSD 5.5 to 3.0.23c and found
that all workstations could not login. The log file reads:
get_md4pw: Workstation PC01$: no account in domain
I ran pdbedit -L, and it returned nothing. I use tdbsam backend; all user
accounts show up fine with 3.0.23b. Now they are mi...
2007 Dec 19
2
Invalid request size nsswitch/winbindd
...44)
Dec 19 10:30:00 antares winbindd[90393]: request_len_recv: Invalid request
size received: 2084 (expected 2088)
but the suggested remedy of sttoping and starting samba granting all
winbindd processes died doesn't work for me
I'm running e freebsd 6 box with
samba-3.0.28,1
I ALWAYS portupgraded, never built custom packages or from sources.
a completely similar box (portupgraded in the same way and running the SAME
samba version) doesn't report this error
both samba are attached and referring to the same domain.
actually this error doesn't seem to bring any problem to the user...
2007 Feb 17
1
wrong dovecot GID while upgrading
Hello,
I tried to upgrade dovecot from 1.0.rc7 to rc22 but I got this error at
the end of the upgrade process:
Dovecot has reserved the groupname 'dovecot' and gid '143':
ERROR: groupname 'dovecot' already in use by gid '1003'
Please resolve these issues and try again:
Either remove the conflicting group or if you wish to continue using a
legacy gr