Author Topic: dpkg error on MD  (Read 2376 times)

pigdog

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1105
    • View Profile
dpkg error on MD
« on: July 22, 2009, 04:44:07 pm »
When trying to do apt-get dist-upgrade on MD I was returned this error...

root@dcerouter:/# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? y
Can not write log, openpty() failed (/dev/pts not mounted?)
Setting up linux-restricted-modules-2.6.27-14-generic (2.6.27-14.20) ...
grep: /proc/cmdline: No such file or directory
cat: /proc/mounts: No such file or directory
dpkg: error processing linux-restricted-modules-2.6.27-14-generic (--configure):
 subprocess post-installation script returned error exit status 1
Setting up dbus (1.2.4-0ubuntu1.1) ...
The system user `messagebus' already exists. Exiting.
invoke-rc.d: initscript dbus, action "start" failed.
dpkg: error processing dbus (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of dbus-x11:
 dbus-x11 depends on dbus; however:
  Package dbus is not configured yet.
dpkg: error processing dbus-x11 (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Errors were encountered while processing:
 linux-restricted-modules-2.6.27-14-generic
 dbus
 dbus-x11
E: Sub-process /usr/bin/dpkg returned an error code (1)

Should I try to fix this?  Or should I not be doing dist-upgrade on MD's?

pigdog

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1105
    • View Profile
Re: dpkg error on MD
« Reply #1 on: July 22, 2009, 05:01:07 pm »
O.K. 

On a second MD I applied the language pack first 

apt-get install language support-en

and when I did an apt-get dist-upgrade there was nothing to upgrade, so, I think something is broke on the first MD.

pigdog

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1105
    • View Profile
Re: dpkg error on MD
« Reply #2 on: July 22, 2009, 06:01:30 pm »
O.K.

I tried to fix the problem various ways with configure, reconfigure, -f, etc.  but nothing worked.

I rebuilt the image via Media Director.  Then I installed language-support-en to avoid those errors.

Do a dist-upgrade and it comes back 0 to install.  Do an apt-get update, then an apt-get dist-upgrade and there'll be packages.

(The apt-get update fails because of a public key error.)

If you install the packages then you'll end up with...

Errors were encountered while processing:
 linux-restricted-modules-2.6.27-14-generic
 dbus
 dbus-x11
E: Sub-process /usr/bin/dpkg returned an error code (1)

You can do an apt-get dist-upgrade multiple times with 0 packages to upgrade.

As soon as you do apt-get update and then dist-upgrade it'll get hosed.
« Last Edit: July 22, 2009, 06:47:52 pm by pigdog »

merkur2k

  • Addicted
  • *
  • Posts: 513
    • View Profile
Re: dpkg error on MD
« Reply #3 on: July 22, 2009, 09:36:01 pm »
apt-get [dist-]upgrade queries the local package cache and looks for new packages to install.
apt-get update downloads new package information from the repositories and compiles it into the local package cache.
so yeah, you can upgrade as many times as you want and it wont do anything until you update the local package cache. the public key error isnt a hard failure either, it is just indicating that there was a problem with one of the respositories. it still processes all the other repositories.
the prompt root@dcerouter indicates that you are on the core, not an md. what were your prior steps to get this far?

pigdog

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1105
    • View Profile
Re: dpkg error on MD
« Reply #4 on: July 23, 2009, 03:32:28 am »
Hi merkur2k,

Prompt root@dcerouter indicates that you are on a MD when doing chroot /usr/pluto/diskless/XX.

When you are on the Core as root you are dcerouter_1000XXX:~#

The public key error http://forum.linuxmce.org/index.php?topic=7977.0 I haven't tried for a while.

The thing is I tried on a MD was dist-upgrade to get ready for the latest Nvidia and ALSA packages -see Alpha 2.26

# pluto-av-wizard_2.0.0.44.09072222170_i386.deb (556,555) - HDMI sound support
# pluto-boot-scripts_2.0.0.44.09072222170_i386.deb (234) - HDMI sound support
# pluto-website-admin_2.0.0.44.09072222170_i386.deb (220) - HDMI sound support

I understand that the 2 packages (Nvidia & ALSA) have not been committed to svn as the wrapper for installing them is not ready for testing.

At this time these packages (Nvidia & ALSA) can be manually installed.

The apt-get update and apt-get dist-upgrade is just something I wanted to draw attention to.

Even with /etc/dhcp3/dhcpd.conf modified with broadcast-address 192.168.80.255; dist-upgrade did not apply the 3 pluto files to the MD.

As per the HDMI Audio section of http://wiki.linuxmce.org/index.php/LinuxMCE-0810_alpha2#20090722_.28alpha2.26.29

"If you installed 0810 Alpha 2.26 or earlier you will need to do apt-get dist-upgrade on your Core & MD's to get the updated AVwizard that enables HDMI audio to be easily configured..."

I don't know if it is my setup, a misunderstanding on my part, or, the dist-upgrade mechanism isn't doing what I thought it should.

At this point I'm thinking the latter.

Thanks

« Last Edit: July 23, 2009, 03:39:45 am by pigdog »