Your message dated Tue, 15 Oct 2019 17:33:26 +0200
with message-id <1905976.h28jQfG3bG@bagend>
and subject line Fixed in 5.6.0-1
has caused the Debian Bug report #933951,
regarding libvirt: upload 5.2 to unstable?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
933951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933951
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libvirt
Version: 5.2.0-2
Severity: wishlist
Now that the freeze is over, how about uploading 5.2.0 to unstable? It seems to
build more places than 5.0.0
(although I haven't looked deeply at either build failure).
My selfish reason is wanting to use libnss_virt_guest, so I guess
backporting packaging change would also be fine with me.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 5.6.0-1
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
