Summary: | virtual/dev-manager-0: emerge --depclean tries to unmerge sys-fs/udev when sys-apps/busybox[mdev] is installed | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Grzegorz {NineX} Krzystek <ninex> |
Component: | Core - Dependencies | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | bkohler |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 395319, 395427 | ||
Bug Blocks: |
Description
Grzegorz {NineX} Krzystek
2011-12-20 20:50:03 UTC
The virtual/dev-manager dependencies look like this: || ( sys-fs/udev sys-fs/devfsd sys-fs/static-dev sys-freebsd/freebsd-sbin ) Do you have another one of those installed, such as sys-fs/devfsd or sys-fs/static-dev? If so, then this behavior is expected. (In reply to comment #1) > The virtual/dev-manager dependencies look like this: > > || ( sys-fs/udev sys-fs/devfsd sys-fs/static-dev sys-freebsd/freebsd-sbin ) > > Do you have another one of those installed, such as sys-fs/devfsd or > sys-fs/static-dev? If so, then this behavior is expected. sys-apps/busybox-1.19.0 have IUSE="... +mdev" ninex@ks388000:~$ cat /usr/portage/virtual/dev-manager/dev-manager-0.ebuild # Copyright 1999-2011 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/virtual/dev-manager/dev-manager-0.ebuild,v 1.2 2011/12/20 15:55:18 vapier Exp $ EAPI="2" DESCRIPTION="Virtual for the device filesystem manager" SLOT="0" KEYWORDS="alpha amd64 arm hppa ia64 m68k ~mips ppc ppc64 s390 sh sparc x86 ~sparc-fbsd ~x86-fbsd" IUSE="" DEPEND="" RDEPEND="|| ( sys-apps/busybox[mdev] sys-fs/udev sys-fs/devfsd sys-fs/static-dev sys-freebsd/freebsd-sbin )" it is dangerous ;P (In reply to comment #2) > (In reply to comment #1) > > The virtual/dev-manager dependencies look like this: > > > > || ( sys-fs/udev sys-fs/devfsd sys-fs/static-dev sys-freebsd/freebsd-sbin ) > > > > Do you have another one of those installed, such as sys-fs/devfsd or > > sys-fs/static-dev? If so, then this behavior is expected. > > sys-apps/busybox-1.19.0 have IUSE="... +mdev" > > > ninex@ks388000:~$ cat /usr/portage/virtual/dev-manager/dev-manager-0.ebuild > # Copyright 1999-2011 Gentoo Foundation > # Distributed under the terms of the GNU General Public License v2 > # $Header: /var/cvsroot/gentoo-x86/virtual/dev-manager/dev-manager-0.ebuild,v > 1.2 2011/12/20 15:55:18 vapier Exp $ > > EAPI="2" > > DESCRIPTION="Virtual for the device filesystem manager" > > SLOT="0" > KEYWORDS="alpha amd64 arm hppa ia64 m68k ~mips ppc ppc64 s390 sh sparc x86 > ~sparc-fbsd ~x86-fbsd" > IUSE="" > > DEPEND="" > RDEPEND="|| ( > sys-apps/busybox[mdev] > sys-fs/udev > sys-fs/devfsd > sys-fs/static-dev > sys-freebsd/freebsd-sbin > )" > > > > it is dangerous ;P added -mdev my USE reemerged busybox, that solved problem look at #395319 Since portage behaves as it's supposed to, given the sys-apps/busybox[mdev] choice in virtual/dev-manager (bug #395319), this bug belongs to base-system since they maintain the virtual. This is big. Current stable systems all have udev eligible for depclean right now. i've dropped IUSE=+mdev for all busybox ebuilds, and moved udev to first in the ||() list in the dev-manager virtual otherwise, if a user has manually built busybox with USE=mdev, then it does satisfy the virtual/dev-manager dependency which means udev could be removed whether the user wants that behavior is up to them |