Bug 146369

Summary: [ERROR] cannot portupgrade -f www/apache22
Product: Ports & Packages Reporter: Andrei Lavreniyuk <andy.lavr>
Component: Individual Port(s)Assignee: freebsd-apache (Nobody) <apache>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Andrei Lavreniyuk 2010-05-07 06:00:08 UTC
# portupgrade -f apache-2.2.15_2

--->  Reinstalling 'apache-2.2.15_2' (www/apache22)
--->  Building '/usr/ports/www/apache22'
===>  Cleaning for apache-2.2.15_2

 To enable a module category: WITH_<CATEGORY>_MODULES
 To disable a module category: WITHOUT_<CATEGORY>_MODULES

 Per default categories are:
  AUTH AUTHN AUTHZ DAV CACHE MISC
 Categories available:
  AUTH AUTHN AUTHZ CACHE DAV EXPERIMENTAL LDAP  MISC PROXY SSL SUEXEC THREADS

  To see all available knobs, type make show-options
  To see all modules in different categories, type make show-categories
  You can check your modules configuration by using make show-modules


===>  apache-2.2.15_2 conflicts with installed package(s):
      apr-gdbm-db42-pgsql84-1.4.2.1.3.9

      They install files into the same place.
      Please remove them first with pkg_delete(1).
*** Error code 1

Stop in /usr/ports/www/apache22.
*** Error code 1

Stop in /usr/ports/www/apache22.
** Command failed [exit code 1]: /usr/bin/script -qa /var/tmp/portupgrade20100507-47342-150rkzv-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=apache-2.2.15_2 UPGRADE_PORT_VER=2.2.15_2 make
** Fix the problem and try again.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
     ! www/apache22 (apache-2.2.15_2)   (unknown build error)
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2010-05-07 06:00:18 UTC
Responsible Changed
From-To: freebsd-ports-bugs->apache

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Philip M. Gollucci freebsd_committer freebsd_triage 2010-05-07 06:31:04 UTC
State Changed
From-To: open->closed

devel/apr and www/apache22 install files into the same place if you do 
not have WITH_APR_FROM_PORTS=yes.  So yes, they do *now* correct 
CONFLICT. Using the bundled www/apache22 apr will be desupported in 
weeks not months. This is invalid