Gentoo emerge config files in etc need updating No credit cyprus sex chat cam rooms
Thanks for the info , I may look into the kompare also,cause it gets to be a pain babysitting the changes you make sometimes,mainly cause Im relatively new to linux so I dont know right off the top of my head if the update it says I need is really needed or not.I think if I could actually see a gui of the two that would in fact be easier I think.For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook.As you may know the core of sys-kernel/hardened-sources has been the grsecurity patches.
The rule of thumb is that if you've modified the configuration file for whatever reason then do an interactive merge and see what is going to be changed. As these tools are verified to be acceptable for general use they are included in the gentoo base.
* IMPORTANT: 12 news items need reading for repository 'gentoo'. * IMPORTANT: 5 config files in '/etc/portage' need updating. [ebuild N ] perl-core/parent-0.228-r1 [ebuild N ] perl-core/Data-Dumper-2.154.0 [ebuild N ] virtual/perl-parent-0.228-r1 [ebuild N ] virtual/perl-Data-Dumper-2.154.0 [ebuild U #] dev-lang/perl-5.20.2 [5.16.3] USE="-berkdb*" [ebuild N ] dev-perl/Net-SMTP-SSL-1.10.0-r1 [ebuild N ] virtual/perl-if-0.60.300 [ebuild N ] virtual/perl-Exporter-5.710.0-r1 [ebuild N ] virtual/perl-Carp-1.330.100 [ebuild N ] perl-core/CGI-4.90.0 USE="" [ebuild N ] virtual/perl-CGI-4.90.0 [ebuild N ] dev-perl/Error-0.170.210 USE="" [ebuild N ] dev-vcs/git-2.3.1 USE="blksha1 cgi curl gpg iconv nls pcre perl python threads webdav -cvs -doc -emacs -gnome-keyring -gtk -highlight -mediawiki (-ppcsha1) -subversion -tk -xinetd" PYTHON_TARGETS="python2_7" !!!
* See the CONFIGURATION FILES section of the emerge * man page to learn how to update config files. Multiple package instances within a single package slot have been pulled !!!
If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously.
You may want to try a larger value of the --backtrack option, such as --backtrack=30, in order to see if that will solve this conflict automatically.