krb5 (1.8+dfsg~alpha1-1) unstable; urgency=low
This version of MIT Kerberos disables DES and 56-bit RC4 by default.
These encryption types are generally regarded as weak; defeating them
is well within the expected resources of some attackers. However,
some applications, such as OpenAFS or Kerberized NFS, still rely on
DES. To re-enable DES support add allow_weak_crypto=true to the
libdefaults section of /etc/krb5.conf
-- Sam Hartman <hartmans@debian.org> Fri, 08 Jan 2010 22:41:14 -0500
krb5 (1.6.dfsg.4~beta1-7) unstable; urgency=low
* In response to MIT's 2006 announcement that Kerberos 4 is at end of
life and no longer under development, this version of the krb5 package
removes most support for krb4. In particular, krb4 headers are no
longer included; applications with krb4 support cannot be built using
libkrb5-dev. In addition, krb4 support has been removed from the KDC
and user utilities. If you do not use Kerberos 4 and do not have
krb4-config installed, you should notice no changes. However, if you
do use Kerberos 4, you must transition away from Kerberos 4 before
upgrading to this version.
* Downgrading from this version to a previous version can be
difficult because of library name changes. Please follow these
instructions:
- Get the libkrb53 and libkadm55 debs you want to downgrade to
-dpkg --force-depends --remove libkrb5-3 libkrb5support0 libdes425-3
libgssapi-krb5-2 libgssrpc4 libkadm5clnt5 libkadm5srv5 libkdb5-4
libk5crypto3
- At this point your system has broken Kerberos libraries
- dpkg -i libkrb53*deb libkadm55*deb (using the debs you got above)
- aptitude -f install to fix any other packages that may be broken

2 Answers
2

When apt-get shows changelogs, it shows them using less (or whatever other pager you may have set - the default is less). If it's less that's running, just hit q to continue. Hitting Ctrl-C kills less, but it also kills apt-get.

First, it looks like your system cannot install packages. So you may need to look into that further. If your system is a low memory VPS, it is possible that you've run out of memory.

I haven't really seen apt terminate without any diagnostics before, but it seems to me that that is what's happening.

However, for your immediate problem, you can try to move apxs2 from another box. First thing to do would be to use ldd /usr/bin/apxs2 on a system that has apache2-dev installed. This command will give you a list of dynamic libraries that the binary needs. You can check if these libraries exist on your target system, and just copy the missing ones across as well. You can put them in /usr/local/lib, or modify LD_LIBRARY_PATH and keep them local. I wouldn't recommend copying the libraries to /lib or /usr/lib, though. That would cause headaches in the long run. This is not really a solution, but it may help in the short term.

thanks for the elaborated answer. I added what happens after apt-get fails. I should have included it in my initial question but i thought it's not related. Can you please take a look and tell me if you think it's still connected to lack of memory?
–
TomOct 2 '11 at 5:28

Low memory issues should result in some sort of log - either an error from APT, or a bus error message, or a OOM dump in dmesg.
–
bdonlanOct 2 '11 at 5:41