On 2008-12-27 10:35 +0100, Frans Pop wrote:

> Package: dpkg
> Version: 1.14.23
> Severity: important
>
> I've thought about filing this as release critical as it is really weird
> behavior and seems like a fairly recent regression from somewhere.
> I had already seen this a few weeks ago while using pbuilder and dismissed
> it as random weirdness, but I now also see it in Debian Installer.
>
> Attached the full installation log, but here is a sample:
> Dec 27 08:13:51 in-target: Selecting previously deselected package busybox.
> Dec 27 08:13:51 in-target: (Reading database ...
> [...]
> Dec 27 08:13:56 in-target: SELECTING PREVIOUSLY DESELECTED PACKAGE 
> LIBVOLUME-ID0.
> Dec 27 08:13:56 in-target: (READING DATABASE ...
> [...]
> Dec 27 08:15:28 in-target: Selecting previously deselected package usbutils.
> Dec 27 08:15:28 in-target: (Reading database ...
> [...]
> Dec 27 08:26:47 in-target: SELECTING PREVIOUSLY DESELECTED PACKAGE 
> EXIM4-CONFIG.
> Dec 27 08:26:47 in-target: (READING DATABASE ...
>
> Note that it seems limited to dpkg and that it's not persistent from one
> invocation to the next. The output of aptitude (and apt?) remains correct
> in lower/mixed case.

But it also applies to the output of the maintainer scripts called by dpkg.

> I guess the first time I saw this with pbuilder was about a month ago. Before
> that I had never seen this behavior.
>
> Any idea what could be causing this switch to all CAPS?

Not really an idea, but I see a pattern.  The switch to CAPS always
seems to happen after a call to set the title in debconf:

> Dec 27 08:13:56 debconf: Obsolete command TITLE Configuring udev called
> Dec 27 08:13:56 in-target: Preconfiguring packages ...
> Dec 27 08:13:56 in-target: Fetched 650kB in 0s (1484kB/s)
> Dec 27 08:13:56 in-target: SELECTING PREVIOUSLY DESELECTED PACKAGE 
> LIBVOLUME-ID0.
> Dec 27 08:13:56 in-target: (READING DATABASE ... 
> Dec 27 08:13:56 in-target: 9314 FILES AND DIRECTORIES CURRENTLY INSTALLED.)
> Dec 27 08:13:56 in-target: UNPACKING LIBVOLUME-ID0 (FROM 
> .../LIBVOLUME-ID0_0.125-7_AMD64.DEB) ...
> Dec 27 08:13:57 in-target: SELECTING PREVIOUSLY DESELECTED PACKAGE UDEV.
> Dec 27 08:13:57 in-target: UNPACKING UDEV (FROM .../UDEV_0.125-7_AMD64.DEB) 
> ...
> Dec 27 08:13:57 debconf: Obsolete command TITLE Configuring udev called
> Dec 27 08:13:57 in-target: SELECTING PREVIOUSLY DESELECTED PACKAGE LIBKLIBC.
> Dec 27 08:13:57 in-target: UNPACKING LIBKLIBC (FROM 
> .../LIBKLIBC_1.5.12-2_AMD64.DEB) ...
> Dec 27 08:13:58 in-target: SELECTING PREVIOUSLY DESELECTED PACKAGE 
> KLIBC-UTILS.
> Dec 27 08:13:58 in-target: UNPACKING KLIBC-UTILS (FROM 
> .../KLIBC-UTILS_1.5.12-2_AMD64.DEB) ...
> Dec 27 08:13:58 in-target: SELECTING PREVIOUSLY DESELECTED PACKAGE 
> INITRAMFS-TOOLS.
> Dec 27 08:13:58 in-target: UNPACKING INITRAMFS-TOOLS (FROM 
> .../INITRAMFS-TOOLS_0.92N_ALL.DEB) ...
> Dec 27 08:13:58 in-target: PROCESSING TRIGGERS FOR MAN-DB ...
> Dec 27 08:14:00 in-target: SETTING UP LIBVOLUME-ID0 (0.125-7) ...
> Dec 27 08:14:00 in-target: SETTING UP UDEV (0.125-7) ...
> Dec 27 08:14:00 in-target: A CHROOT ENVIRONMENT HAS BEEN DETECTED, UDEV NOT 
> STARTED.
> Dec 27 08:14:00 in-target: SETTING UP LIBKLIBC (1.5.12-2) ...
> Dec 27 08:14:00 in-target: SETTING UP KLIBC-UTILS (1.5.12-2) ...
> Dec 27 08:14:00 in-target: SETTING UP INITRAMFS-TOOLS (0.92N) ...
> Dec 27 08:14:00 in-target: UPDATE-INITRAMFS: DEFERRING UPDATE (TRIGGER 
> ACTIVATED)
> Dec 27 08:14:00 in-target: PROCESSING TRIGGERS FOR INITRAMFS-TOOLS ...

So maybe debconf is the culprit?

Sven



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to