Package: znc
Version: 1.2-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
doing an apt-get upgrade
* What exactly did you do (or not do) that was effective (or ineffective)?
i noticed a new znc pakage (1.2-2) was available. i already had 1.2-1
installed (since i tend to upgrade every 1/2 weeks) but the instance running
was still 1.0something since i didnt restart znc for a while and its not done
automatically after an upgrade
* What was the outcome of this action?
the outcome was that after killing znc (yes im an evil bastard) and
trying to restart it there was no znc binary found on the system although apt
is convinced the pakage installed correctly
i worked around this by manually compiling and installing it (which
works fine, but now im unsure if future apt updates are a good idea).
* What outcome did you expect instead?
well, guess...
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages znc depends on:
ii libc6 2.17-97
ii libgcc1 1:4.8.2-10
ii libsasl2-2 2.1.25.dfsg1-17
ii libstdc++6 4.8.2-10
Versions of packages znc recommends:
ii znc-perl 1.2-2
ii znc-python 1.2-2
ii znc-tcl 1.2-2
znc suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
