unnecessary debconf prompt on upgrade

Bug #911961 reported by Steve Langasek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dictionaries-common (Ubuntu)
Fix Released
High
Martin Pitt
Precise
Fix Released
High
Martin Pitt

Bug Description

On upgrade to the latest precise daily, update-default-ispell gave me a wholly unnecessary pair of debconf prompts. The first seems to be because it thought my existing debconf setting was invalid; the second to ask me which ispell dictionary I wanted as the default even though I have only one installed.

Before the debconf prompt, the following console output was displayed:

 [ispell,dc_debconf_select] error: [undefined] does not correspond to any package

The changelog of today's dictionaries-common upload includes this comment:

  * Drop the debconf priority change in dc-debconf-select.pl. According to
    Agustin this is only shown in error cases now, which we actually do want.

seems this isn't terribly accurate.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: dictionaries-common 1.12.1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
Uname: Linux 3.2.0-7-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Wed Jan 4 11:09:51 2012
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: dictionaries-common
UpgradeStatus: Upgraded to precise on 2011-11-08 (56 days ago)

Revision history for this message
Steve Langasek (vorlon) wrote :
Steve Langasek (vorlon)
Changed in dictionaries-common (Ubuntu):
importance: Undecided → High
status: New → Triaged
assignee: nobody → Martin Pitt (pitti)
Revision history for this message
Martin Pitt (pitti) wrote :

Unfortunately I'm not able to actually reproduce this. I tried precise->precise, oneiric live CD -> precise, and my oneiric stable VM -> precise; in my workstation both debconf questions have a value, in the other two cases they were undefined.

But anyway, the debconf error should only be shown if there actually is a defined value which doesn't correspond to a package. Complaining about "undefined" indeed doesn't make much sense.

Changed in dictionaries-common (Ubuntu Precise):
status: Triaged → In Progress
milestone: none → precise-alpha-2
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package dictionaries-common - 1.12.1ubuntu2

---------------
dictionaries-common (1.12.1ubuntu2) precise; urgency=low

  * scripts/system/dc-debconf-select.pl: Do not show debconf error for
    undefined default values, just if the value is defined and corresponds to
    a non-installed dictionary. (LP: #911961)
 -- Martin Pitt <email address hidden> Fri, 06 Jan 2012 12:53:25 +0100

Changed in dictionaries-common (Ubuntu Precise):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.