Processing control commands:
reassign -1 dpkg
Bug #763829 [rsyslog] rsyslogd is not correctly restarted, vulnerable version
still running
Bug reassigned from package 'rsyslog' to 'dpkg'.
No longer marked as found in versions rsyslog/8.4.2-1.
Ignoring request to alter fixed versions of bug
Control: reassign -1 src:linux
Control: forcemerge 763831 -1
Control: affects 763831 rsyslog
On Sun, 2014-10-26 at 22:11:21 +0100, Michael Biebl wrote:
Control: reassign -1 dpkg
Am 08.10.2014 um 22:14 schrieb Michael Biebl:
Am 08.10.2014 um 22:11 schrieb Michael Biebl:
Am 08.10.2014 um
Processing control commands:
reassign -1 src:linux
Bug #763829 [dpkg] rsyslogd is not correctly restarted, vulnerable version
still running
Bug reassigned from package 'dpkg' to 'src:linux'.
Ignoring request to alter found versions of bug #763829 to the same values
previously set
Ignoring
Processing control commands:
reopen -1
Bug #766758 {Done: Eugen Dedu eugen.d...@univ-fcomte.fr} [ekiga] ekiga is
partially installed (triggers-awaited)
Bug reopened
Ignoring request to alter fixed versions of bug #766758 to the same values
previously set
reassign -1 dpkg 1.17.21
Bug #766758
I've just upgraded another machine, and:
$ COLUMNS=70 dpkg -l | grep -v '^ii'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Control: severity -1 important
Let's lower this for now, as this is certainly not critical in any
way, and I don't think it's serious for now, too many unknowns, but
I'll bump it again if it happens to be so.
On Mon, 2014-10-27 at 02:14:32 +0100, Vincent Lefevre wrote:
I've just upgraded
Processing control commands:
severity -1 important
Bug #766758 [dpkg] partially installed packages (triggers pending) after upgrade
Severity set to 'important' from 'critical'
--
766758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766758
Debian Bug Tracking System
Contact
On 2014-10-27 02:44:38 +0100, Guillem Jover wrote:
Let's lower this for now, as this is certainly not critical in any
way, and I don't think it's serious for now, too many unknowns, but
I'll bump it again if it happens to be so.
IMHO, it would be bad if it affected stable.
On Mon, 2014-10-27
I've also had this today on all my nodes (with 1.17.21).
Triggers for man-db were not run at the last update run...
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
9 matches
Mail list logo