| View previous topic :: View next topic |
| Author |
Message |
BitJam
Advocate
Joined: 12 Aug 2003
Posts: 2508
Location: Silver City, NM
|
 Posted: Mon Jan 28, 2008 10:23 pm Post subject: Why is only kdm-3.5.8-r1 stable? [solved] |
 |
|
If I try an emerge -av -uDN world I get: | Code: | !!! All ebuilds that could satisfy "~kde-base/kcontrol-3.5.8" have been masked.
!!! One of the following masked packages is required to complete your request:
- kde-base/kcontrol-3.5.8 (masked by: ~amd64 keyword)
- kde-base/kcontrol-3.5.8-r1 (masked by: ~amd64 keyword)
- kde-base/kcontrol-3.5.8-r2 (masked by: ~amd64 keyword)
For more information, see MASKED PACKAGES section in the emerge man page or
refer to the Gentoo Handbook.
(dependency required by "kde-base/kdm-3.5.8-r1" [ebuild]) |
If I add kcontrol to /etc/portage/package.keyword then the failure moves to a different KDE package, libkonq.
I would have expected all of the KDE 3.5.8.x packages to have gone stable at the same time. Making only one (or a few of them) stable prevents me from even being able to see what other packages in Portage can be updated.
Edit: The rest of kde-3.5.8.x went stable the following day.
Last edited by BitJam on Tue Jan 29, 2008 5:08 pm; edited 1 time in total |
|
| Back to top |
|
 |
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1709
|
| Posted: Tue Jan 29, 2008 12:30 am Post subject: |
|
|
| BitJam wrote: | | I would have expected all of the KDE 3.5.8.x packages to have gone stable at the same time. |
That would be the logical conclusion, but the Gentoo developers (from my experience) are so packed with things to do that they mark things stable as they come. I'd either stay at 3.5.7 or prepare yourself for many inclusions to your keywords file. |
|
| Back to top |
|
|
BitJam
Advocate
Joined: 12 Aug 2003
Posts: 2508
Location: Silver City, NM
|
| Posted: Tue Jan 29, 2008 12:48 am Post subject: |
|
|
I agree with everything you said except the problem I have is that "emerge -av -uDN world" won't tell me about any other packages because of the stupid KDE blockage.
A couple weeks ago I had a similar problem where a dev put a broken nvidia-drivers ebuild into unstable so it would be "easier to move it around". It seems especially egregious to intentionally bork the ebuild tree like this because we as users are asked to only sync at most once a day. So if you happen to catch one of these mistakes then you are supposed to wait a day before moving forward. |
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1709
|
| Posted: Tue Jan 29, 2008 12:56 am Post subject: |
|
|
Oof. Ya, thats happened to me a few times before. Best I could say is to wait a couple of days, re-sync and try again. Chances are that if a few packages are upgraded, the rest are prone to follow in the wake.  |
|
| Back to top |
|
|
|
Desktop Environments
