Your message dated Sat, 09 Nov 2024 10:51:02 +0000 with message-id <b0a29248bc631362ed06a8879f93b8cdae5414d0.ca...@adam-barratt.org.uk> and subject line Closing bugs released with 12.8 has caused the Debian Bug report #1081317, regarding bookworm-pu: package vmdb2/0.27+really.0.26-1+deb12u1 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 ow...@bugs.debian.org immediately.) -- 1081317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: release.debian.org Severity: normal Hi, I am about to upload version 0.27+really.0.26-1+deb12u1 (uff, what a mouthful! 😉) of vmdb2. This upload addresses bug #1032363: vmdb2 sets LC_ALL=C at startup, which is incompatible with Ansible, that requires a UTF8 environment. Upstream has included this fix for newer releases. I want this to be included in the stable release as well. I will be uploading it trusting the relevant diff is quite minimal, but am filing this bug following usual procedure :-) The debdiff follows inline: $ debdiff ../build-area/vmdb2_0.27+really.0.26-1{,+deb12u1}.dsc dpkg-source: warning: extracting unsigned source package (/home/gwolf/vcs/build-area/vmdb2_0.27+really.0.26-1.dsc) dpkg-source: warning: extracting unsigned source package (/home/gwolf/vcs/build-area/vmdb2_0.27+really.0.26-1+deb12u1.dsc) diff -Nru vmdb2-0.27+really.0.26/debian/changelog vmdb2-0.27+really.0.26/debian/changelog --- vmdb2-0.27+really.0.26/debian/changelog 2023-05-06 19:06:53.000000000 -0600 +++ vmdb2-0.27+really.0.26/debian/changelog 2024-09-10 11:32:05.000000000 -0600 @@ -1,3 +1,9 @@ +vmdb2 (0.27+really.0.26-1+deb12u1) bookworm; urgency=medium + + * Set the locale to UTF-8, as Ansible fails otherwise (Closes: #1032363) + + -- Gunnar Wolf <gw...@debian.org> Tue, 10 Sep 2024 11:32:05 -0600 + vmdb2 (0.27+really.0.26-1) unstable; urgency=medium * Rolling back the import of 0.27 due to the request of the Debian diff -Nru vmdb2-0.27+really.0.26/debian/patches/series vmdb2-0.27+really.0.26/debian/patches/series --- vmdb2-0.27+really.0.26/debian/patches/series 2023-05-06 19:06:53.000000000 -0600 +++ vmdb2-0.27+really.0.26/debian/patches/series 2024-09-10 11:32:05.000000000 -0600 @@ -1,2 +1,3 @@ 001_set_architecture_for_later_stages omit_new_ext4_flags +set_UTF8_locale diff -Nru vmdb2-0.27+really.0.26/debian/patches/set_UTF8_locale vmdb2-0.27+really.0.26/debian/patches/set_UTF8_locale --- vmdb2-0.27+really.0.26/debian/patches/set_UTF8_locale 1969-12-31 18:00:00.000000000 -0600 +++ vmdb2-0.27+really.0.26/debian/patches/set_UTF8_locale 2024-09-10 11:32:05.000000000 -0600 @@ -0,0 +1,13 @@ +Index: vmdb2/vmdb/runcmd.py +=================================================================== +--- vmdb2.orig/vmdb/runcmd.py ++++ vmdb2/vmdb/runcmd.py +@@ -46,7 +46,7 @@ def progress(msg): + def runcmd(argv, **kwargs): + progress("Exec: %r" % (argv,)) + env = kwargs.get("env", os.environ.copy()) +- env["LC_ALL"] = "C" ++ env["LC_ALL"] = "C.UTF8" + kwargs["env"] = env + kwargs["stdout"] = kwargs.get("stdout", subprocess.PIPE) + kwargs["stderr"] = kwargs.get("stderr", subprocess.PIPE)
--- End Message ---
--- Begin Message ---Source: release.debian.org Version: 12.8 Hi, Each of the updates tracked by these bugs was included in today's 12.8 bookworm point release. Regards, Adam
--- End Message ---
