| 1 |
Abhay Kedia schreef: |
| 2 |
> On Sunday 29 January 2006 06:41, Ian wrote: |
| 3 |
>> unmask all of the packages im building in package.keywords. |
| 4 |
>> |
| 5 |
> You seem to have added them to package.unmask as well. Don't do that. |
| 6 |
> |
| 7 |
> |
| 8 |
> |
| 9 |
Just as a note, there doesn't seem to be a choice in this regard (i.e., |
| 10 |
you have to add kdewhatever-3.5.1 to package.unmask). If I don't add it |
| 11 |
to package.unmask, I get a halt from Portage because some of the |
| 12 |
dependent packages that [ nomerge ] packages want to emerge are masked. |
| 13 |
The only way I've found around it in the past three days is to just go |
| 14 |
ahead and unmask them, let Portage fail to download then tarballs, and |
| 15 |
then do a --resume --skipfirst to proceed. |
| 16 |
|
| 17 |
I could of course not --deep the update, but that covers everything, |
| 18 |
which I don't want. I also upgraded Portage to see if it was a Portage |
| 19 |
problem, but that didn't help either. |
| 20 |
|
| 21 |
It's odd, imo... Portage shouldn't really consider masked packages for |
| 22 |
updates, but in this case I can't seem to get it to stop. I was also |
| 23 |
wondering if it was a bug, and in what (KDE, Portage... something). It |
| 24 |
seems to me that the devs have done this before (put a package in the |
| 25 |
tree just before it was available, masked), and I can't figure out why |
| 26 |
its not working this time the way it has in the past. If its something |
| 27 |
I've done, I can't figure out what |
| 28 |
|
| 29 |
But I've been busy, so I've only had time to be annoyed by it, not |
| 30 |
investigate it. |
| 31 |
|
| 32 |
Holly |
| 33 |
-- |
| 34 |
gentoo-user@g.o mailing list |
Archives