Re: [gentoo-user] Trying to do a world update! (Blocked by... )

2006-05-12 Thread Jeremy Olexa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Graham Murray wrote:
> Neil Bothwick <[EMAIL PROTECTED]> writes:
> 
>> unmerge the blocking packages, coldplug, pam-login and ant-tasks. This
>> usually happens because the functionality the package provides is now
>> handled by something else that emerge world needs to bring it. This is
>> certainly the case with udev now handling coldplug's job.
> 
> Which begs the question that if attempting to rebuild all the packages
> in a working system indicates blockers, how did the system get in that
> state and why did portage not indicate a blockage when the incompatible
> packages were installed or upgraded?

Just because they are conflicting now doesn't mean that there was
conflicting packages before. Upgrades do happen, and things do change ;)
Every time you sync and get a new ebuild, you are generally getting a
new version of the package (assuming there is a new version available).

- --
Jeremy Olexa
([EMAIL PROTECTED])
Office: EE/CS 1-201
CS/IT Systems Staff
University of Minnesota

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEZIqmFN7pD9kMi/URAkfTAJ4vYtxZTPGTYufzQyWJaog5dk+zBwCfVtPQ
WitkwasBfNu1qMKQTpTsXQc=
=UqNp
-END PGP SIGNATURE-
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Trying to do a world update! (Blocked by... )

2006-05-12 Thread Neil Bothwick
On Fri, 12 May 2006 02:25:30 -0700, Richard Fish wrote:

> > Which begs the question that if attempting to rebuild all the packages
> > in a working system indicates blockers, how did the system get in that
> > state and why did portage not indicate a blockage when the
> > incompatible packages were installed or upgraded?

Because you are upgrading the packages. The versions you currently have
installed are not blockers, but the new versions are different.

> How are you doing your updates?  If you are not using the --deep
> option, I am not surprised that you never saw the blockers before,
> because portage will consider _only_ those packages actually in world
> for an update unless you use --deep.

That's not necessarily true, depending on the command used to update
world. "emerge world" only updates any packages in world and any forced
dependency updates. "emerge --update world" also considers first level
dependencies and updates those, even if the existing version satisfies
the world packages' dependencies.

As you say, "emerge --deep --update world" goes right down the tree. The
only packages --deep misses are those that are not in world and not
dependencies of world, i.e. non-dependent packages emerged with --oneshot.


-- 
Neil Bothwick

Facts are stubborn, but statistics are more pliable


signature.asc
Description: PGP signature


Re: [gentoo-user] Trying to do a world update! (Blocked by... )

2006-05-12 Thread Richard Fish

On 5/12/06, Graham Murray <[EMAIL PROTECTED]> wrote:


Which begs the question that if attempting to rebuild all the packages
in a working system indicates blockers, how did the system get in that
state and why did portage not indicate a blockage when the incompatible
packages were installed or upgraded?


How are you doing your updates?  If you are not using the --deep
option, I am not surprised that you never saw the blockers before,
because portage will consider _only_ those packages actually in world
for an update unless you use --deep.

-Richard

--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Trying to do a world update! (Blocked by... )

2006-05-12 Thread Graham Murray
Neil Bothwick <[EMAIL PROTECTED]> writes:

> unmerge the blocking packages, coldplug, pam-login and ant-tasks. This
> usually happens because the functionality the package provides is now
> handled by something else that emerge world needs to bring it. This is
> certainly the case with udev now handling coldplug's job.

Which begs the question that if attempting to rebuild all the packages
in a working system indicates blockers, how did the system get in that
state and why did portage not indicate a blockage when the incompatible
packages were installed or upgraded?
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Trying to do a world update! (Blocked by... )

2006-05-11 Thread Neil Bothwick
On Thu, 11 May 2006 16:58:30 -0400, Christopher E wrote:

> I am geting this at the top of my world update, here  is the command
> and the very beggining of the out put:
> Mr-Eyes ~ # emerge -aqDu --newuse world
> [blocks B ] sys-apps/coldplug (is blocking sys-fs/udev-090)
> [blocks B ] sys-apps/pam-login (is blocking
> sys-apps/shadow-4.0.15-r1) [blocks B ]  (is blocking dev-java/ant-core-1.6.5-r2)
> [ebuild U ] sys-devel/patch-2.5.9-r1 [2.5.9]
> 
> What should I do any  help is greatful!

unmerge the blocking packages, coldplug, pam-login and ant-tasks. This
usually happens because the functionality the package provides is now
handled by something else that emerge world needs to bring it. This is
certainly the case with udev now handling coldplug's job.


-- 
Neil Bothwick

Windows Error #01: No error... ...yet.


signature.asc
Description: PGP signature


Re: [gentoo-user] Trying to do a world update! (Blocked by... )

2006-05-11 Thread Rasmus Andersen
On Thu, May 11, 2006 at 04:58:30PM -0400, Christopher E wrote:
> Hello All,
> 
> I am geting this at the top of my world update, here  is the command
> and the very beggining of the out put:
> Mr-Eyes ~ # emerge -aqDu --newuse world
> [blocks B ] sys-apps/coldplug (is blocking sys-fs/udev-090)
> [blocks B ] sys-apps/pam-login (is blocking sys-apps/shadow-4.0.15-r1)
> [blocks B ]  dev-java/ant-core-1.6.5-r2)
> [ebuild U ] sys-devel/patch-2.5.9-r1 [2.5.9]
> 
> What should I do any  help is greatful!

Generally, you should just unmerge the blocking packages (emerge -C).

Rasmus
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Trying to do a world update! (Blocked by... )

2006-05-11 Thread Richard Fish

On 5/11/06, Christopher E <[EMAIL PROTECTED]> wrote:

I am geting this at the top of my world update, here  is the command
and the very beggining of the out put:
Mr-Eyes ~ # emerge -aqDu --newuse world
[blocks B ] sys-apps/coldplug (is blocking sys-fs/udev-090)
[blocks B ] sys-apps/pam-login (is blocking sys-apps/shadow-4.0.15-r1)
[blocks B ] 

The (almost always) correct answer here is to unmerge the blocking
application.  In this case:

emerge --unmerge coldplug pam-login ant-tasks

-Richard

--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Trying to do a world update! (Blocked by... )

2006-05-11 Thread znx

Remove the packages that are blocking.

emerge -C coldplug pam-login ant-tasks

Then emerge world again.

--
gentoo-user@gentoo.org mailing list