reassign 499014 schroot
thanks
Thanks, it was useful. This happens after reusing an schroot after
installing dbus inside it, if the host does not have the messagebus
user/group. Because schroot by default overrides the NSS databases of
the chroot by those of the host, see
Version: 1.8.18-1
Hi,
I just hit this or a related problem. In a fresh sid chroot, eventually
dpkg would complain:
$ apt-get install nettle-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
severity 499014 serious
thanks
On Mon, Sep 22, 2008 at 07:06:24AM +0200, Michael Biebl wrote:
There was no further information provided. So the only possible
explanation for this scenario is, that the user either
1.) Deleted the messagebus group
2.) Created the messagebus user himself without
Bastian Blank wrote:
severity 499014 serious
thanks
On Mon, Sep 22, 2008 at 07:06:24AM +0200, Michael Biebl wrote:
There was no further information provided. So the only possible
explanation for this scenario is, that the user either
1.) Deleted the messagebus group
2.) Created the
severity 499014 wishlist
stop
On Mon, Sep 22, 2008, Michael Biebl wrote:
3.) Copied /etc/passwd around (without the corresponding /etc/group)
The package is not able to recover from error conditions, in this case a
missing group. How this happened is irrelevant.
I beg to disagree.
severity 499014 important
thanks
Downgrading to severity important.
There was no further information provided. So the only possible
explanation for this scenario is, that the user either
1.) Deleted the messagebus group
2.) Created the messagebus user himself without the corresponding
messagebus
6 matches
Mail list logo
