Hi, Just Lately I have been having some trouble upgrading my pkgs, I have been running BSD-6.3 for a fair while now & have been able to keep my system always up to date til now .

AnyWay I am now wondering if my system is now telling me I need to upgrade my Kernel if I want to have an up to date system.
I have picked this error out to give as an example & was hoping if someone could tell what it means or what I need to do as I am a little bit nervous about upgrading kernel etc & was hoping it might not mean I needto just yet.
Thanks anyOne

Sorry ' I just realised I didnt finish of my Question by adding the error ,I must of been working ahead of myself.
AnyWay I am re Running the software to try & get the error Back so I can Repost as I was sure I saved a Copy of error like i usually do but cant Find it.
I will hopefully be back shortly with info.
Thanks

It Turns out I actually did save the error but to a different new folder , I forgot I created it as I play between 2 PC's .
AnyWay Before I found the original error I Updated PortSnap with "#portsnap fetch update"
then "# portsdb -Uu"
then "#cd /usr/ports"
then "# make fetchindex"
then "#pkgdb -uF

And then ran "portmanager -u" & it was looking real good til it got to around 40% & then came similar errors.But slightly different.
So I did get to upgrade some pkgs which shortned the list a bit.
The first error is the one I was to originally show before I ran Portmanager but didnt show up on errors this time.
And second is after trying to upgrade with Portmanager -u.
I would appreciate any help as I have found in past it hard to uninstall some pkgs that belong to another pkg but I will have to learn how it seems.

install -o root -g wheel -m 444 /usr/ports/audio/pulseaudio/work/pulseaudio-0.9.10/src/client.conf /usr/local/etc/pulse/client.conf-dist
pulse-rt:*:557:
You already have a group "pulse-rt", so I will use it.
pulse:*:563:
You already have a group "pulse", so I will use it.
pulse-access:*:564:
You already have a group "pulse-access", so I will use it.
pulse:*:563:563::0:0:PulseAudio System User:/nonexistent:/sbin/nologin
You already have a user "pulse", so I will use it.

===>
Pulseaudio is designed to run in realtime, to achieve this pulseaudio is
marked SUID root by default. To take advantage of pulseaudio's realtime
functionality you must be a member of the 'pulse-rt' group.

This port has installed the following files which may act as network
servers and may therefore pose a remote security risk to the system.
/usr/local/lib/pulse-0.9/modules/libsocket-server.so

If there are vulnerabilities in these programs there may be a security
risk to the system. FreeBSD makes no guarantee about the security of
ports included in the Ports Collection. Please type 'make deinstall'
to deinstall the port if this is a concern.

For more information, and contact details about the security
status of this software, see the following webpage:http://pulseaudio.org/
===> Cleaning for pulseaudio-0.9.10_2

If you are using portsnap, it keeps the INDEXes up to date. There is no reason for a seperate make fetchindex.

If you are using portmanager, you do not need to use pkgdb and portsdb, which are part of the portupgrade suite. portmanager does not use pkgdb or portsdb, as it relies on the systems database files, which the ports system keeps up to date.

Lastly, keeping your FreeBSD kernel and world up to date is not difficult. You will need the source tree (/usr/src) which you should install from your disk or a downloaded package, csup to update it, and then to do a buildworld cycle to finish it. A little bit of knolwedge about your system is an advantage. Normally I'd just point you to the handbook chapter, but the handbook is somewhat over-complex.

__________________The only dumb question is a question not asked.
The only dumb answer is an answer not given.

Thanks for pointing those things out about PortManager etc as it can be hard to pick up on those types of things until you properly understand & work out the differences between pkg managers.
I actually deliberatly typed in those commands hoping someone might point out anything noticable.
I actually would always start off using "portupgrade" for upgrading pkgs etc first & then when an error forced portupgrade to stop I would turn to one of the other pkg managers like "portmaster & portmanager" to see if they fix the error because they do things differently & alot of the times they saved the day , but this time neither fully got me through all the upgrades but did help .

BSD is the longest I have had any Desktop stay on my PC while constantly keeping my system up to date & I dont want to lose it so I will hopefully upgrade my Kernel properly when I do give it ago.
I actually thought BSD-unix would break the quickest of all the Linux-Unix distro's I have tried but has been nothing but the greatest Joy & success over the few years using Computers & Linux-Unix.
The other problem with one of the errors is it says
"avahi-libdns-0.6.22_1 /net/avahi-libdns marked IGNORE reason: conflicts with another installed port" But doesnt seem to explain whick pkg it conflicks with- & as I explained above-you cant always delete a pkg as it wont let you because of dependencies etc.

& Also

error: unrecognized command line option "-Wno-pointer-sign"
*** Error code 1
which is what originally I think caused me to think I needed to upgrade Kernel.
AnyWay

(Another thing is that we do not generally speak of "upgrading the kernel". FreeBSD is an entire operating system, and the kernel is part of it. You will be upgrading the entire base system - to be precise, everything that you did not install using ports)

Secondly, choose a package manager and stick to it. portmaster is probably better, but portupgrade is better supported for the present.

Now, more questions: Do you have anything in your /etc/make.conf? Many persons from a Linux background tend to put all sorts of rubbish in there(for instance, options from a newer gcc version), and it does cause problems.

Errors like these can be caused by out of date gcc versions, but the ports collection is very good at detecting and flagging them before it gets to the stage of bombing out.

avahi-libdns conflicts with mDNSresponder. (I found that by looking int net/avahi-libdns/Makefile, and finding the CONFLICTS entry.) They do the same job, by the looks of it, so either can probably be used.
Both portmaster and portupgrade have a -o option to cover these cases - something like#portupgrade -o net/avahi-libdns mDNSresponder\* should replace mDNSresponder with avadi-libdns, healing all orphaned dependencies along the way.

__________________The only dumb question is a question not asked.
The only dumb answer is an answer not given.

He clearly has modified CFLAGS in make.conf by that compile line... Please see http://gentoo-wiki.com/Safe_Cflags and ensure that you are using safe CFLAGS for your processor. If it still breaks, remove all of them and try again.

It sounds a good idea theoretically to stick with one package manager & I seriously considered it .
But because I mainly use Portupgrade I decided to give it another go without adjusting anything after running both Portmanager & portmaster as I explained earlier, -which upgraded pkgs portupgrade complained about.
& now all the pkgs that were left over which master & manager didn't do are now been upgraded by portupgrade & all the problems listed above with the errors are fixed & this is the method I have been using for a while now.

I have added my make.conf to show if anything is unusual,
as its alot different to using Gentoo it seems.
As I read that using portmaster properly may mean changing your make.conf to get proper value from it etc.

I am hoping to stick with one Manager as I keep picking up more tips along the way.

Thanks, -I actually should of explained that I am using the
" DesktopBSD pkg manager " which uses "portupgrade" & is a fantastic tool ,& has a section for unistalling or deleting software you installed after installing your OS.
But anything else that has dependencies etc it doesnt seem to let you delete.
AnyWay I will look further into ways to delete pkgs etc as you explained as I remember being able to delete pkgs some years ago when I first tried FreeBSD but forgot the routines,
As I found when I tried deleting from console recently a couple of times it complained about dependencies etc as I forgot there are options you can use with pkg_delete & others as you pointed out like "pkg_delete -xf".

The one thing I have started using more often now are the "man pages"
Thanks