Re: [gentoo-user-br] erro no emerge --uDN world

[Davi]

Em Sexta 22 Junho 2007 20:02, Raphael MD escreveu:
> Bem sobre os problema dos error com o emerge -uDN world que param o
processo, a menssagem do problema atual é a seguinte:
> >localhost Desktop # emerge -uDN world

localhost Desktop # ????

Você fez:

localhost Desktop $ su
Password:
localhost Desktop #

Certo?
Você não está usando o ambiente gráfico como root, certo?

> >Calculating world dependencies /
> >!!! Ebuilds for the following packages are either all
> >!!! masked or don't exist:
> >app-crypt/openssl-tpm-engine

# emerge --search openssl-tpm-engine

> >... done!
> >!!! Error: the <dev-libs/boost-1.34.0 package conflicts with another
> > package; !!!        the two packages cannot be installed on the same
> > system together. !!!        Please use 'emerge --pretend' to determine
> > blockers.
> >For more information about Blocked Packages, please refer to the following
> >section of the Gentoo Linux x86 Handbook (architecture is irrelevant):
> >http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked
>

Como o Fabiano já disse: coloca o CD de boot e refaz do zero tudo...

> So que desta vez eu ja dei emerge -C boost, para removê-lo
> Ja dei emerge openssl, para reinstalar o openssl e não deu certo.
>
> Ai então dei:
>
> localhost Desktop # emerge --pretend boost
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild  N    ] dev-libs/boost-1.33.1-r1  USE="doc -bcp -bjam -debug -icu
> -pyste -threads -threadsonly" [blocks B     ] <dev-libs/boost-1.34.0 (is
> blocking dev-util/boost-build-1.34.0)
>

emerge -C serve para quê?
*Você* sabe para que serve o -C?
Sabe o que o -C faz?

Eu sou extremamente contra as flags reduzidas serem usadas a torto e a 
direito...

Até que você *aprenda*, procure usar:

# emerge --unmerge PACOTE
# emerge --search PACOTE
# emerge --deep --update --newuse world
# emerge --sync
# emerge --ask --verbose --tree PACOTE
# emerge --pretend PACOTE

E por aí vai...

Veja: você não leu os manuais... Então não convém ficar tentando brincar com 
opções reduzidas... Até que você *saiba* o que está fazendo...

Conselho de amigo... =)

> E começo então a achar q eu emergi a versão 1.34.0 na época que o
> ACCEPT="~x86" estava no meu make.conf
>

Hum... ~x86...

> Alguma sugestão?!?
>

RTFM

# emerge wtf

# wtf rtfm


Já te foi dito: ninguém aqui tem algo contra ajudar ninguém.
Mas, a rigor, não há desculpas para não ler o manual.

http://www.catb.org/~esr/faqs/smart-questions.html#before

[conteudo]

Before You Ask

Before asking a technical question by e-mail, or in a newsgroup, or on a 
website chat board, do the following:

   1.

      Try to find an answer by searching the archives of the forum you plan to 
post to.
   2.

      Try to find an answer by searching the Web.
   3.

      Try to find an answer by reading the manual.
   4.

      Try to find an answer by reading a FAQ.
   5.

      Try to find an answer by inspection or experimentation.
   6.

      Try to find an answer by asking a skilled friend.
   7.

      If you're a programmer, try to find an answer by reading the source 
code.

When you ask your question, display the fact that you have done these things 
first; this will help establish that you're not being a lazy sponge and 
wasting people's time. Better yet, display what you have learned from doing 
these things. We like answering questions for people who have demonstrated 
they can learn from the answers.

Use tactics like doing a Google search on the text of whatever error message 
you get (searching Google groups as well as Web pages). This might well take 
you straight to fix documentation or a mailing list thread answering your 
question. Even if it doesn't, saying “I googled on the following phrase but 
didn't get anything that looked promising” is a good thing to do in e-mail or 
news postings requesting help, if only because it records what searches won't 
help.

Take your time. Do not expect to be able to solve a complicated problem with a 
few seconds of Googling. Read and understand the FAQs, sit back, relax and 
give the problem some thought before approaching experts. Trust us, they will 
be able to tell from your questions how much reading and thinking you did, 
and will be more willing to help if you come prepared. Don't instantly fire 
your whole arsenal of questions just because your first search turned up no 
answers (or too many).

Prepare your question. Think it through. Hasty-sounding questions get hasty 
answers, or none at all. The more you do to demonstrate that having put 
thought and effort into solving your problem before seeking help, the more 
likely you are to actually get help.

Beware of asking the wrong question. If you ask one that is based on faulty 
assumptions, J. Random Hacker is quite likely to reply with a uselessly 
literal answer while thinking “Stupid question...”, and hoping the experience 
of getting what you asked for rather than what you needed will teach you a 
lesson.

Never assume you are entitled to an answer. You are not; you aren't, after 
all, paying for the service. You will earn an answer, if you earn it, by 
asking a substantial, interesting, and thought-provoking question — one that 
implicitly contributes to the experience of the community rather than merely 
passively demanding knowledge from others.

On the other hand, making it clear that you are able and willing to help in 
the process of developing the solution is a very good start. “Would someone 
provide a pointer?”, “What is my example missing?”, and “What site should I 
have checked?” are more likely to get answered than “Please post the exact 
procedure I should use.” because you're making it clear that you're truly 
willing to complete the process if someone can just point you in the right 
direction.

[/conteudo]


Eu podia ser bonzinho e traduzir essa coisa para você... Ou, melhor ainda, te 
mandar a versão traduzida... A lista, com certeza, agradeceria...
Mas acredito que a lista vai agradecer, ainda mais, se você achar a versão 
traduzida por si mesmo.

[]s

-- 
Davi Vidal
davividal@×××××××××××××.br
davividal@×××××.com
--
"Religion, ideology, resources, land,
spite, love or "just because"...
No matter how pathetic the reason,
it's enough to start a war. "
--------------------------------------------------------
Por favor não faça top-posting, coloque a sua resposta abaixo desta linha.
Please don't do top-posting, put your reply below the following line.
--------------------------------------------------------