Your message dated Mon, 4 Sep 2006 22:26:11 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#385540: hal postinst gives errors when installed within chroot has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: hal Severity: normal I run a Debian/Etch chroot environment within Ubuntu/Dapper and CentOS4 host OSs (it's a long story). When aptitude upgrading hal, I get the following output: With Ubuntu/Dapper host OS: Setting up hal (0.5.7.1-1) ... Installing new version of config file /etc/dbus-1/system.d/hal.conf ... Installing new version of config file /etc/dbus-1/event.d/20hal ... adduser: Warning: that home directory does not belong to the user you are currently creating Starting Hardware abstraction layer: hald With CentOS4 host OS: Setting up hal (0.5.7.1-1) ... Installing new version of config file /etc/dbus-1/system.d/hal.conf ... Installing new version of config file /etc/dbus-1/event.d/20hal ... chage: Permission denied. Stopped: adduser: `/usr/bin/chage -M 99999 haldaemon' returned error code 1. Aborting. Removing user `haldaemon'. Removing group `haldaemon'. groupdel: group haldaemon does not exist adduser: `groupdel haldaemon' returned error code 6. Aborting. dpkg: error processing hal (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: hal E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up hal (0.5.7.1-1) ... chage: Permission denied. Stopped: adduser: `/usr/bin/chage -M 99999 haldaemon' returned error code 1. Aborting. Removing user `haldaemon'. Removing group `haldaemon'. groupdel: group haldaemon does not exist adduser: `groupdel haldaemon' returned error code 6. Aborting. dpkg: error processing hal (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: hal These symptoms manifest with hal version 0.5.7.1-1. I do not remember seeing these symptoms with hal version 0.5.7-2; it's possible I did not notice them. Are these symptoms indicative of a problem in the hal package itself? If so, I can collect more information. If this problem is caused by my chroot shenanigans, I'm more than happy for this ticket to be close and I will investigate the problem myself. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.15-1-686-smp Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---On Fri, Sep 01, 2006 at 09:47:56AM +1000, Trent Buck wrote: > Package: hal > Severity: normal > > I run a Debian/Etch chroot environment within Ubuntu/Dapper and CentOS4 > host OSs (it's a long story). When aptitude upgrading hal, I get the > following output: > > With Ubuntu/Dapper host OS: > > Setting up hal (0.5.7.1-1) ... > Installing new version of config file /etc/dbus-1/system.d/hal.conf ... > Installing new version of config file /etc/dbus-1/event.d/20hal ... > adduser: Warning: that home directory does not belong to the user you are > currently creating > Starting Hardware abstraction layer: hald > > With CentOS4 host OS: > > Setting up hal (0.5.7.1-1) ... > Installing new version of config file /etc/dbus-1/system.d/hal.conf ... > Installing new version of config file /etc/dbus-1/event.d/20hal ... > chage: Permission denied. > Stopped: adduser: `/usr/bin/chage -M 99999 haldaemon' returned error code > 1. Aborting. > > Removing user `haldaemon'. > Removing group `haldaemon'. > groupdel: group haldaemon does not exist > adduser: `groupdel haldaemon' returned error code 6. Aborting. > dpkg: error processing hal (--configure): > subprocess post-installation script returned error exit status 2 > > Errors were encountered while processing: > hal > E: Sub-process /usr/bin/dpkg returned an error code (1) > A package failed to install. Trying to recover: > Setting up hal (0.5.7.1-1) ... > chage: Permission denied. > Stopped: adduser: `/usr/bin/chage -M 99999 haldaemon' returned error code > 1. Aborting. > > Removing user `haldaemon'. > Removing group `haldaemon'. > groupdel: group haldaemon does not exist > adduser: `groupdel haldaemon' returned error code 6. Aborting. > dpkg: error processing hal (--configure): > subprocess post-installation script returned error exit status 2 > Errors were encountered while processing: > hal > > These symptoms manifest with hal version 0.5.7.1-1. I do not remember > seeing these symptoms with hal version 0.5.7-2; it's possible I did not > notice them. > > Are these symptoms indicative of a problem in the hal package itself? If > so, I can collect more information. If this problem is caused by my > chroot shenanigans, I'm more than happy for this ticket to be close and > I will investigate the problem myself. I'm closing this one now and fixing the other one in the next upload. Basically the warning (homedir doesn't belong to user) is my fault and will be fixed in the next package. The fact that the haldaemon user can't be created is an error in your setup, though.. Probably you haven't seen it in 0.5.7.1-1 as that didn't create a new user on upgrades. The decision which one to close by mail and which by upload seems a little arbitrary, but this ones seems to be more about the failure to install, while the other one is more about the warning that is given.. Well atleast sortof. Sjoerd -- There can be no twisted thought without a twisted molecule. -- R. W. Gerard
--- End Message ---
