Dale schreef:
> Bob Sanders wrote:
> 
> 
>> Before you do that, get rid of /root/.revdep* Run - python-updater 
>> Then - perl-cleaner all Then - emerge -uDNav world Then -
>> revdep-rebuild -p
>> 
> 
> OK.  I went in circles with those for a while.  I have now come to a 
> brick wall here.  I had a earlier thread about this just in case.  I 
> have a package.use file that tells it not to do the doc thing for 
> gentoo-sources but it seems it is more stubborn than I am.
> 
> 
>> [EMAIL PROTECTED] / # emerge -uDNavp world
>> 
>>>>> --pretend disables --ask... removing --ask from options.
>> 
>> These are the packages that I would merge, in order:
>> 
>> Calculating world dependencies ...done! [ebuild  N    ]
>> app-text/xmlto-0.0.18  0 kB
>> 
>> Total size of downloads: 0 kB [EMAIL PROTECTED] / #

Did you re-emerge gentoo-sources after removing the "doc" USE flag?

If not, then the currently installed version, which was installed using
the "doc" flag, would still require that xmlto be installed.

That brings me to another question, because if you didn't re-emerge
gentoo-sources, and you have changed the USE flag, then it *should* be
coming up as recompileable when you do a --newuse (-N).

Why isn't it? Most likely because you have not actually changed the USE
flag.

What is the format of the relevant entry in /etc/portage/package.use?

If it does not look like this

sys-kernel/gentoo-sources -doc

then fix it. Alternatively, you could just remove "doc" or add "-doc" to
/etc/make.conf, if you don't use that USE flag the majority of the time,
and only add it for those packages you *do* use it for. This is how I do
it, doc is off by default, but enabled specifically for imagemagick, for
which I need all the docs I can get.

Also, try

emerge -uDNptv world

emerge --update --deep --newuse --pretend --tree --verbose

(with --tree being the important change)

 to see what packages are requiring xmlto. We're
just guessing that it's gentoo-sources, really; maybe it's not.

> 
> I did take the -p out and try it but it failed, like I expected.  May
> be something in the command that is making it want to ignore the 
> package.use file.  Anyway . . . . . .

No, your syntax in package.use is likely wrong. Happens to all of us. :-) .

> OK, the revdep-rebuild command now gives me this:
<snip>
> 
> Dynamic linking on your system is consistent... All done.
> 

Great. No more need to deal with that atm, then.

> Don't get me started on that libingif and giflib circle either.  :/
> I'm not sure what to do about that.  The forums don't seem to have a
> fix either.  If I emerge it, it gripes, if I unmerge it, it gripes.
> I'm confused.
> 
> What next, hammer?  Will a emerge -ev world help those broken things?
> 
*Will* you stop trying to get authorization for emerge -e at every
opportunity!!!??? :-)

It's really not necessary. And you're getting yourself all worked up
over a relatively minor issue (or in fact a couple of them).

As I said, you probably have a typo in /etc/portage/package.use. You
want to spend a week reinstalling your system over a typo?

As for the gif/libungif problem, search the ML archives; we just talked
about this last week. I'd have to look it up, but iirc the solution has
to do with uninstalling either gif or libungif and the program that's
being a problem about it, then reinstalling the apps in the correct order.

But depending on your usage patterns, perhaps you don't even need to
worry about this *at this minute*. If the program or programs that
depend on the gif/libungif circle are not mission critical for you atm
(or you aren't using it because you're solving the other issues), then
put the issue on the back burner for now.

Basically, you seem to be upset because Portage is having a fit when you
try to update world. Not because a program is broken, or because you
can't do some specific task (because a program is broken). If that is a
correct assessment of the situation, then have some perspective.

You don't have to update world every day, or even every month. So don't.
If things work OK for what you need them to do, then the fact that you
can't update easily right now is *not a problem*. Certainly not one
needing a reinstall of the entire system.

If something specific is broken due to the gif/libungif issue, then tell
us what that is. It may be that gif/libungif needs to be sorted out to
fix whatever is broken, but we can cross that bridge when we come to it.

It's really not a big deal. Relax.

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

Reply via email to