[Pkg-sysvinit-devel] Bug#784567: intent to NMU sysvinit really soon -- followup fix

[Petter Reinholdtsen]

I noticed something strange when I upgraded my sid chroot for the first
time in a while.  I only used 'apt-get upgrade', and the util-linux and
most sysvinit packages were held back:

The following packages have been kept back:
  cpp-4.8 cpp-4.9 g++-4.9 gcc-4.8 gcc-4.8-base gcc-4.9 gcc-4.9-base
  git-buildpackage initscripts libasan0 libasan1 libatomic1
  libavcodec-dev libavcodec56 libavformat-dev libavformat56
  libavresample-dev libavresample2 libavutil-dev libavutil54 libcilkrts5
  libcloog-isl4 libgcc-4.8-dev libgcc-4.9-dev libgcc1 libgfortran3
  libglib2.0-0 libglib2.0-bin libgomp1 libgphoto2-6 libitm1
  liblist-moreutils-perl liblsan0 libpam-systemd libpcre3 libpcre3-dev
  libpcrecpp0 libquadmath0 libsane libsane-common libstdc++-4.9-dev
  libstdc++6 libsystemd0 libtsan0 libubsan0 rsyslog systemd
  sysvinit-utils util-linux virtualbox virtualbox-qt vmdebootstrap

But even then, I saw this unexpected message at the end of the upgrade:

  Running hooks in /etc/ca-certificates/update.d...

  /etc/ca-certificates/update.d/jks-keystore: 33:
    /etc/ca-certificates/update.d/jks-keystore: mountpoint: not found
  the keytool command requires a mounted proc fs (/proc).
  E: /etc/ca-certificates/update.d/jks-keystore exited with code 1.
  done.

I guess things will improve with a dist-upgrade, but this tell me the
ordering of dependencies/breaks is not quite right.

-- 
Happy hacking
Petter Reinholdtsen