Solved [Solved] pkg upgrade wants to install apache22, why?

FreeBSD 10 RELEASE, when I run pkg upgrade it wants to install apache22. Can anyone take me through the steps which will bring me to an understanding of why it needs to install apache22? I am currently running apache24 on the system and cannot proceed with the upgrade due to conflicts between apache22 and apache24.

Code:
root@freebsd:/usr/src # pkg upgrade
Updating repository catalogue
Upgrades have been requested for the following 28 packages:

	Installing apache22: 2.2.27_1
	Upgrading apache24: 2.4.9 -> 2.4.9_1
	Upgrading bash: 4.3.0_1 -> 4.3.8
	Upgrading lcms2: 2.5 -> 2.6
	Reinstalling libxcb-1.9.3 (direct dependency changed)
	Upgrading libyaml: 0.1.4_3 -> 0.1.6
	Upgrading p5-IO-Socket-SSL: 1.972 -> 1.975_1
	Upgrading pciids: 20140312 -> 20140402
	Upgrading php5: 5.4.25 -> 5.4.27
	Upgrading sqlite3: 3.8.4.1 -> 3.8.4.2
	Reinstalling xcb-util-0.3.9_1,1 (direct dependency changed)
	Reinstalling xcb-util-renderutil-0.3.8 (direct dependency changed)
	Upgrading xmlto: 0.0.25_2 -> 0.0.26
	Reinstalling ap22-mod_fcgid-2.3.9 (direct dependency changed)
	Reinstalling libX11-1.6.2,1 (direct dependency changed)
	Reinstalling libXext-1.3.2,1 (direct dependency changed)
	Reinstalling libXfixes-5.0.1 (direct dependency changed)
	Reinstalling libXi-1.7.2,1 (direct dependency changed)
	Reinstalling libXinerama-1.1.3,1 (direct dependency changed)
	Reinstalling libXrender-0.9.8 (direct dependency changed)
	Reinstalling libXt-1.1.4,1 (direct dependency changed)
	Reinstalling libXxf86vm-1.1.3 (direct dependency changed)
	Reinstalling libXcomposite-0.4.4,1 (direct dependency changed)
	Reinstalling libXcursor-1.1.14 (direct dependency changed)
	Reinstalling libXdamage-1.1.4 (direct dependency changed)
	Reinstalling libXmu-1.1.2,1 (direct dependency changed)
	Reinstalling libXpm-3.5.11 (direct dependency changed)
	Reinstalling libXrandr-1.4.2 (direct dependency changed)

The upgrade will require 13 MB more space

0 B to be downloaded

Proceed with upgrading packages [y/N]:
 
Re: pkg upgrade wants to install apache22, why?

I'm guessing you have www/mod_php5 installed? That depends on the default Apache version, which is 2.2.
 
Re: pkg upgrade wants to install apache22, why?

Solved. I have ap24-mod_fcgid-2.3.9 installed which depends on apache22.
 
Yes, I am also having this issue. I have a full working setup with www/apache24, with various lang/php5 plugins. I have been reading the manual to see if there is a way to tell ports-mgmt/pkg to ignore the www/apache22 dependency and use www/apache24 instead. It would appear not. :(

We are unable to use pkg lock either; to prevent installation of www/apache22.

You can use a bastardised method of combining ports and packages, but is rather messy. Upgrade the www/apache22 dependent ports then install the remainder packages.
 
Package dependencies are "set in stone", you can't change them. If you want to deviate from the defaults you may want to set up your own repository. Setting up your own repository with ports-mgmt/poudriere is a fairly simple and straightforward process. Then you can change all the defaults on your own packages. Even if you only have one or two machines building your own packages is already quite beneficial because you can build everything without touching any of your currently running systems. Build errors or other issues can be solved locally without running into such a situation half way during the upgrade of that one important production server. Once everything is built you can simply use pkg upgrade to upgrade everything, and that usually only takes a couple of minutes.
 
Back
Top