Precisely. Aptitude is the culprit here. I've switched our package manager 
to apt which is more conservative and it does not remove the packages when 
upgrading php, which, for now is a workable solution. I need to find the 
time to put this in as  Debian bug and see what they say. 

I can't see a plausible explanation for why requesting an upgrade to one 
package could feasibly result in the removal of the same package (same 
thing happens if you upgrade an extension first). 

e.g. 

root@vps814:/home/cadre/stresler# aptitude install php5-mysql
The following packages will be upgraded: 
  php5-common php5-mysql 
2 packages upgraded, 0 newly installed, 0 to remove and 29 not upgraded.
Need to get 0 B/633 kB of archives. After unpacking 0 B will be used.
The following packages have unmet dependencies:
  php5-xsl: Depends: php5-common (= 5.3.3-7+squeeze14) but 
5.3.3-7+squeeze17 is to be installed.
  libapache2-mod-php5: Depends: php5-common (= 5.3.3-7+squeeze14) but 
5.3.3-7+squeeze17 is to be installed.
  php5-mcrypt: Depends: php5-common (= 5.3.3-7+squeeze14) but 
5.3.3-7+squeeze17 is to be installed.
  php5-cgi: Depends: php5-common (= 5.3.3-7+squeeze14) but 
5.3.3-7+squeeze17 is to be installed.
  php5-cli: Depends: php5-common (= 5.3.3-7+squeeze14) but 
5.3.3-7+squeeze17 is to be installed.
The following actions will resolve these dependencies:

      Remove the following packages:              
1)      libapache2-mod-php5                       
2)      php-apc                                   
3)      php-pear                                  
4)      php5                                      
5)      php5-adodb                                
6)      php5-cgi                                  
7)      php5-cli                                  
8)      php5-imagick                              
9)      php5-mcrypt                               
10)     php5-memcache                             
11)     php5-memcached                            
12)     php5-mysql                                
13)     php5-suhosin                              
14)     php5-xsl                             


#12 on that list is the package I am requesting be upgraded/installed. How 
can its removal ever be an intended result? 

On Tuesday, September 24, 2013 11:58:27 PM UTC-4, mcd wrote:

> I guess I'm confused at why aptitude would remove php5-memcache in order 
> to upgrade php5-common. Or if it really needed to do that, shouldn't it be 
> smart enough to automatically install the upgraded version? I confess I'm 
> more familiar with RedHat/CentOS, and Yum is smart enough to handle 
> upgrading packages and their dependencies smoothly. I had though aptitude 
> was smart enough too, based on my limited experience with it. Anyway, if 
> you're still stuck I guess that's what I would try to figure out.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to