Yes, but for some reason it got masked yesterday morning. I updated 6 servers and it downgraded them all. Now I'm doing it again and it looks like it's unmasked again. (grrrrrrr)

=C=
* Cal Evans
* http://www.eicc.com
* We take care of your IT,
* So you can take care of your business.
*
* I think inside the sphere.


MAL wrote:
Cal Evans wrote:

==========================================
machine root # emerge -pUv world
 >>> --upgradeonly implies --update... adding --update to options.

These are the packages that I would merge, in order:

Calculating world dependencies |
!!! all ebuilds that could satisfy ">=sys-apps/portage-2.0.49" have been masked.
!!! (dependency required by "sys-apps/coreutils-5.0-r3" [ebuild])


!!! Problem with ebuild sys-apps/debianutils-1.16.7-r3
!!! Possibly a DEPEND/*DEPEND problem.

!!! Depgraph creation failed.
==========================================

Ok, so coreutils requires portage 2.0.49 but 2.0.49 was masked this morning. So now emerge -pUv world now fails. Any idea when portage 2.0.49 will be back?


2.0.49-r3 is unmasked, i've been using it for weeks.

Also, why does emerge not honor the -U flag when it comes to portage? I did not want to downgrade but emerge ignores that when it comes to portage and downgrades it anyhow.


Guess the dependency checking only goes one level deep.

MAL


-- [EMAIL PROTECTED] mailing list



--
[EMAIL PROTECTED] mailing list



Reply via email to