tags 784783 - moreinfo thanks On Wed, 13 May 2015, Jonathon Anderson wrote:
> As I recall, I was following this guide: > > https://www.linode.com/docs/security/upgrading/upgrade-to-debian-8-jessie > > And my upgrade failed first during this install: > > sudo apt-get install apt dpkg aptitude > > I *think* that I first had krb5-admin-server break during *that* > install; but maybe I'm misremembering, and I lost an ssh session or > something. Okay, this gets more interesting; again in a (new) clean wheezy VM with a kdc/kadmind running and not much else, after swapping jessie in the sources.list and apt-get update, apt-get install apt dpkg aptitude wants to remove libkadm5srv-mit8 and add new packages: gcc-4.9-base init-system-helpers libboost-iostreams1.55.0 libdb5.3 libkadm5clnt-mit9 libkadm5srv-mit9 libkdb5-7 libperl4-corelibs-perl and to upgrade a long list, including apt, aptitude, and dpkg, as well as ~all of the src:krb5 packages not already mentioned. Again saying 'yes' to libc's question about restarting services without asking, I do see some issues. In the terminal log Preparing to unpack .../krb5-admin-server_1.12.1+dfsg-19_amd64.deb ... [ ok ] Stopping Kerberos administrative servers: kadmind. Unpacking krb5-admin-server (1.12.1+dfsg-19) over (1.10.1+dfsg-5+deb7u3) ... dpkg: libkadm5srv-mit8:amd64: dependency problems, but removing anyway as you requested: krb5-kdc depends on libkadm5srv-mit8 (>= 1.10+dfsg~); however: Package libkadm5srv-mit8:amd64 is to be removed. [...] [FAIL] Starting Kerberos KDC: krb5kdc failed! Setting up krb5-admin-server (1.12.1+dfsg-19) ... Installing new version of config file /etc/init.d/krb5-admin-server ... [....] Starting Kerberos administrative servers: kadmindkadmind: could not initialize loop, aborting failed! [...] And no running krb5kdc or kadmind processes. auth.log has krb5kdc complaining "Cannot allocate memory - while creating main loop", and the same kadmind error quoted above. dpkg -l|grep -v ^ii finds only rc libkadm5srv-mit8:amd64 The error "while creating main loop" is something of an artificial use of ENOMEM, as it is used when loop_init(VERTO_EV_TYPE_NONE); fails, which may or may not be due to a failure to allocate memory. Upgrading libverto-libev1 lets the kdc start properly. I guess it seems like we need a versioned dependency on libverto-libev1, then. -Ben -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
