search for: pkg_delet

...cvsup of the openssh port. It builds correctly, but refuses to install with the following: ===> Installing for openssh-3.6.1_5 ===> openssh-3.6.1_5 conflicts with installed package(s): ssh2-3.2.9.1_1 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/security/openssh. I was unable to pkg_delete the ssh2 due to other manual requirements. Do I need to delete the ssh2 in /usr/local.etc and the sshd2.sh in /usr/local/etc/rc.d? What exactly is the conflict? tia, Chris

...ing union_lookup panics on our server(s) ... as most on this list already know, we make heavy use of unionfs to share between jails, and I already know that this is the "kernel side" cause of the problem ... but ... From what I can tell, though, the "trigger" for the panic is pkg_delete ... if I build a jail'd environment, using unionfs, SSH into it, make install a port and then pkg_delete it, it will cause the panic ... The machine that it happened to recently isn't the "fullest" one we have, nor the busiest ... the 'busiest' one we have just went 31...

I'm getting the bus error mentioned in PR bin/124353 and I need a bit more detail on how to apply the patch. Right now I'm getting the following error when I try to do a make on cvsup-without-gui: Fatal Error: bad version stamps: SupTCP.m3 I put the changes in the /usr/local/lib/m3/pkg/m3core/src/unix/freebsd-4.amd64/Unix.i3 file I created the file

...defined reference to `XRenderCreateAnimCursor' /usr/X11R6/lib/libXcursor.so: undefined reference to `XRenderCreateCursor' *** Error code 1 Stop in /usr/ports/x11/XFree86-4-clients/work/xc/programs/xcursorgen. /usr/ports/x11/XFree86-4-clients/work/xc/programs/xcursorgen I already tried to pkg_delete all XFree86 packages, and reinstall them from scratch. XFree86-4-libraries which contain libXcursor build ok with no problem. But still cant build Xfree-86-clients. anyone has any suggestions? thx a in advance

...oo as I used the package tools (pkg_add -r) to add few package to the base install. Keeping in mind my server have disk space constrain (small disk install) I would ask an opinion about the followings methods to upgrade packages after a freebsd upgrade (in this case from 9.0 to 9.1): 1) perform # pkg_delete <pkg_name> and then # pkg_add -r <pkg_name> for each of them ? (I think about some package depends on other, this could create some little problem); 2) perform # pkg_add -F <pkg_name> (not tried yet) and overwrite the already installed pkg ? 3) have a separate server on which...

(Previous HTML version of this msg "massaged" by Antigen... :-P ) As root: Uninstall 2.0.7 with pkg_delete samba-2.0.7 Download samba-2.2.5.tar.bz2 from one of the mirror sites onto your OpenBSD machine. bunzip2 samba-2.2.5.tar.bz2 tar -xvf samba-2.2.5.tar Copy the attached files into the samba "source" directory cd to the "samba-2.2.5/source" directory at the command prompt, t...

...mo directory being all screwed up, I just re-rolled the JDK1.1.7 A.OUT release. Hopefully this should allow folks to again run Java programs under FreeBSD 2.*. The FreeBSD port has been upgraded to use the new release, so if you've installed the old (broken) release, please upgrade your port, pkg_delete the old one, and build the new one. Sorry about the hassle! Project Status report: ---------------------- Progress on JDK1.2 is happening slowly. Hopefully things will pickup when the Linux folks release their diffs to the public. There are plans to build a JDK1.1.8 release for FreeBSD, but th...

...(0xc5e062c0) Jul 2 14:35:07 jupiter savecore: reboot after panic: union_lookup returning . (0xbf6fee90) not same as startdir (0xbb6d58c0) had two of them today, dumping nice cores ... I'm suspecting its someone trying to remove a file that is "scrambled" ... I can do similar doing a pkg_delete ... but, is there any way of finding which file? The code is here, but I can't seem to even get an inode out of it to using 'find' to find: (kgdb) list 610 611 #ifdef DIAGNOSTIC 612 if (cnp->cn_namelen == 1 && 613 cnp->cn_nameptr[0] == ...

....] debug: Puppet::Type::Package::ProviderNim: file /usr/sbin/nimclient does not exist debug: Puppet::Type::Package::ProviderZypper: file /usr/bin/zypper does not exist debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does not exist debug: Puppet::Type::Package::ProviderOpenbsd: file pkg_delete does not exist debug: Puppet::Type::Package::ProviderApt: file /usr/bin/apt-get does not exist [...] why does puppet check what service/package type provider has to use if it''s defined? 2.- ) file-metadata I have ~hundred messages like: debug: file_metadata supports formats: b64_zlib_y...

...ppet::Type::Service::ProviderDaemontools: file /usr/bin/svc does not exist debug: Puppet::Type::Service::ProviderRedhat: file /sbin/service does not exist debug: Puppet::Type::Service::ProviderLaunchd: file /bin/launchctl does not exist debug: Puppet::Type::Package::ProviderFreebsd: file /usr/sbin/ pkg_delete does not exist debug: Puppet::Type::Package::ProviderFink: file /sw/bin/fink does not exist debug: Puppet::Type::Package::ProviderRug: file /usr/bin/rug does not exist debug: Puppet::Type::Package::ProviderOpenbsd: file pkg_delete does not exist debug: Puppet::Type::Package::ProviderSunfreeware: f...

my base/default includes this ntp manifest # cat modules/ntp/manifests/ntp.pp # ntp.pp class ntp { case $operatingsystem { centos, redhat: { $service_name = ''ntpd'' $conf_file = ''ntp.conf.el'' } debian, ubuntu: { $service_name = ''ntp'' $conf_file = ''ntp.conf.debian'' } } package {

On Jul 30, 2013, at 10:39 AM, Pavel Potcheptsov (EKTOS) wrote: > Is this a trouble? Driver use path /var/state/ups/ but upsd use path /var/db/nut/upsd.pid Yes, the driver and upsd need to agree on the path to the socket. From the FreeBSD ports tree: /usr/ports/sysutils/nut/Makefile: STATEDIR?= /var/db/nut [...] CONFIGURE_ARGS= --sysconfdir=${PREFIX}/etc/nut \

Running 9.0-Stable on an i386. Whenever I type a command at the prompt I get the output /usr/local/lib/libintl.so.9: Undefined symbol "_ThreadRuneLocale" and nothing else - the command will not run. Just the above output. Commands like "ls" and "exit" work, but not much else. This happends whether I am logged in a user or as root. Cannot even halt the system from

...--with-user=_ups --with-group=_ups --with-statepath=/var/db/nut/ and then build driver and copy again. but this doesn't help (driver pid still in the /var/state/ups). Maybe I must add more arguments to change driver's pid location, but I did next, I changed this argument in openbsd ports: # pkg_delete nut # cd /usr/ports/sysutils/nut/ edit Makefile and change line --with-statepath=/var/db/nut to --with-statepath=/var/state/ups # make install # /etc/rc.d/upsd start upsd(ok) # /etc/rc.d/upsmon start upsmon(ok) # upsc senpro at localhost battery.capacity: 75 battery.charge: 100 battery.runtime: 2...

In the next month or two I've got to upgrade a number of servers that are currently on an EOL'd version of 4-STABLE. I foresee that I'll have very limited time to do full OS upgrades on these systems in the coming several years, so I want to make sure I bring them onto an extended-life branch. Right now 4.11 has the furthest projected EOL date (Jan 31 2007), and the projected EOL

# reboot Connection to 192.168.5.81 closed by remote host. Connection to 192.168.5.81 closed. ppo at admin:/tmp$ ssh root at 192.168.5.81 root at 192.168.5.81's password: Last login: Tue Jul 30 14:10:49 2013 from pc-ppo.kh.ektos OpenBSD 5.3 (GENERIC.MP) #58: Tue Mar 12 18:43:53 MDT 2013 # ps -aux | grep ups root 2254 0.0 0.0 324 700 p0 S+ 5:29PM 0:00.00 grep ups # ps -aux

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

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

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

A while back, I submitted a patch for PR kern/124621, which allows the mounting of an ext2(3) filesystem created with an inode size other than 128. The e2fsprogs' default is now 256, so file systems created on newer Linux distributions or with the port will not be mountable. I was hopeful this would get committed in time for 7.1-RELEASE (and 6.4-RELEASE), however the PR remains open. If