Ubuntu
update-motd package

package update-motd (not installed) failed to install/upgrade: no package named `update-motd' is installed, cannot configure

Bug #400462 reported by Paul Hummer
190
This bug affects 37 people
Affects Status Importance Assigned to Milestone
update-motd (Ubuntu)
Fix Released
High
Dustin Kirkland 

Bug Description

Binary package hint: update-motd

Just another apt-get update on karmic gave me another crash detection.

Description: Ubuntu karmic (development branch)
Release: 9.10

update-motd:
  Installed: (none)
  Candidate: 3.3-0ubuntu1
  Version table:
     3.3-0ubuntu1 0
        500 http://us.archive.ubuntu.com karmic/main Packages

ProblemType: Package
Architecture: amd64
Date: Thu Jul 16 18:37:33 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: no package named `update-motd' is installed, cannot configure
Package: update-motd (not installed)
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SourcePackage: update-motd
Title: package update-motd (not installed) failed to install/upgrade: no package named `update-motd' is installed, cannot configure
Uname: Linux 2.6.31-3-generic x86_64

Related branches

lp:ubuntu/karmic/update-motd
Revision history for this message
Paul Hummer (rockstar) wrote :
nullack (nullack)
Changed in update-motd (Ubuntu):
status: New → Confirmed
Revision history for this message
Jithin Emmanuel (jithin1987) wrote :

Same issue here. Just now saw this in todays updates.

Revision history for this message
Don Forigua (ingforigua) wrote :

i confirm this bug on my ubuntu karmic

Revision history for this message
Shane Fagan (shanepatrickfagan) wrote :

Same here

Revision history for this message
roscio1975 (stefano-manocchio-gmail) wrote :

me too!

Dustin Kirkland  (kirkland)
Changed in update-motd (Ubuntu):
importance: Undecided → High
Revision history for this message
Hellsgator (hellsgate) wrote :

confirmed. same issue, failed to install.

Revision history for this message
Michael Vogt (mvo) wrote :

I can reproduce the problem here and I'm currently debugging it.

Apt does call "dpkg --configure update-motd" during the install (because it upgrades it to a new version). But because the package has a empty filelist dpkg things its no more and marks it purged.

Revision history for this message
Michael Vogt (mvo) wrote :

For apt there is no way in advance to know if a package will empty. In order to make this work, there should be a switch for dpkg like "--force-configure" so that dpkg does not error if a package can not be configured (because its now empty) or because its already configured.

Dustin Kirkland  (kirkland)
Changed in update-motd (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-motd - 3.4-0ubuntu1

---------------
update-motd (3.4-0ubuntu1) karmic; urgency=low

  * debian/rules: ensure that this package isn't *totally* empty,
    so install docs, was causing nasty failures on upgrades, LP: #400462

 -- Dustin Kirkland <email address hidden> Fri, 17 Jul 2009 03:27:10 -0500

Changed in update-motd (Ubuntu):
status: Fix Committed → Fix Released
Dustin Kirkland  (kirkland)
Changed in update-motd (Ubuntu):
assignee: nobody → Dustin Kirkland (kirkland)
status: Fix Released → Confirmed
Revision history for this message
Fer (fernando-gil-lopez) wrote :

Also confirmed in 32bits version

Dustin Kirkland  (kirkland)
Changed in update-motd (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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