[gentoo-user] What causes a package to be brought in during a big emerge?

[gentoo-user] What causes a package to be brought in during a big emerge?

[Andrew Lowe]

Hi all,
	I've done an:

"emerge --pretend -NuD world"

and whilst reviewing the output, it lists an old package that I played 
around with in the past but now no longer need. In turn I do:

"emerge -C oldPackageNoLongerNeeded"

the package is removed and I in turn do another

"emerge --pretend -NuD world"

but "oldPackageNoLongerNeeded" is still there, although emerge tells me 
its now gone from "U" to "N" ie Update to New. I've fired up "ufed" and 
removed what I thought would be the appropriate USE tag, run the emerge 
again and it's still there. I've tried:

"equery depends oldPackageNoLongerNeeded"

and it lists nothing as needing "oldPackageNoLongerNeeded"

I've looked through the emerge help and nothing springs to mind as 
telling me why "oldPackageNoLongerNeeded" is being brought in.

	So after that rambling intro, is there a package/utility that will tell 
me, when in this situation, what package needs 
"oldPackageNoLongerNeeded" and why it is being brought into my emerge.

	Thanks for any help,
		Andrew

p.s. Tried Google on this and just couldn't seem to get the right 
keywords o find anything.....

Re: [gentoo-user] What causes a package to be brought in during a big emerge?

[Volker Armin Hemmann]

On Samstag 26 September 2009, Andrew Lowe wrote:
> Hi all,
> 	I've done an:
> 
> "emerge --pretend -NuD world"
> 
> and whilst reviewing the output, it lists an old package that I played
> around with in the past but now no longer need. In turn I do:
> 
> "emerge -C oldPackageNoLongerNeeded"
> 
> the package is removed and I in turn do another
> 
> "emerge --pretend -NuD world"
> 
> but "oldPackageNoLongerNeeded" is still there, although emerge tells me
> its now gone from "U" to "N" ie Update to New. I've fired up "ufed" and
> removed what I thought would be the appropriate USE tag, run the emerge
> again and it's still there. I've tried:
> 
> "equery depends oldPackageNoLongerNeeded"
> 
> and it lists nothing as needing "oldPackageNoLongerNeeded"
> 
> I've looked through the emerge help and nothing springs to mind as
> telling me why "oldPackageNoLongerNeeded" is being brought in.
> 
> 	So after that rambling intro, is there a package/utility that will tell
> me, when in this situation, what package needs
> "oldPackageNoLongerNeeded" and why it is being brought into my emerge.
> 
> 	Thanks for any help,
> 		Andrew
> 
> p.s. Tried Google on this and just couldn't seem to get the right
> keywords o find anything.....
> 

maybe it is still left in world file.

Re: [gentoo-user] What causes a package to be brought in during a big emerge?

[Andrew Lowe]

On 26/09/2009 9:08 AM, Volker Armin Hemmann wrote:
> On Samstag 26 September 2009, Andrew Lowe wrote:
>> Hi all,
>> 	I've done an:
>>
>> "emerge --pretend -NuD world"
[snip]
...
...
[snip]
>> p.s. Tried Google on this and just couldn't seem to get the right
>> keywords o find anything.....
>>
>
> maybe it is still left in world file.
>

Volker,
	I'll look into that. On a slightly tangential note, I've been using 
Gentoo for about 6 - 7 years, but not very well. My somewhat limited 
knowledge of portage comes from about 2004 and is probably way out of 
date. Besides the doco listed on the Gentoo Documentation Resources of 
the web site, "Gentoo Handbook" and the doco under the "Gentoo System 
Documentation" heading, anything else you would suggest to get up to date?

	Regards,
		Andrew

[gentoo-user] Re: What causes a package to be brought in during a big emerge?

[Nikos Chantziaras]

On 09/26/2009 04:05 AM, Andrew Lowe wrote:
> Hi all,
> I've done an:
>
> "emerge --pretend -NuD world"
>
> and whilst reviewing the output, it lists an old package that I played
> around with in the past but now no longer need. In turn I do:
>
> "emerge -C oldPackageNoLongerNeeded"
>
> the package is removed and I in turn do another
>
> "emerge --pretend -NuD world"
>
> but "oldPackageNoLongerNeeded" is still there, although emerge tells me
> its now gone from "U" to "N" ie Update to New. I've fired up "ufed" and
> removed what I thought would be the appropriate USE tag, run the emerge
> again and it's still there. I've tried:
>
> "equery depends oldPackageNoLongerNeeded"
>
> and it lists nothing as needing "oldPackageNoLongerNeeded"

"equery depends" won't list anything unless the package is question is 
installed.


> I've looked through the emerge help and nothing springs to mind as
> telling me why "oldPackageNoLongerNeeded" is being brought in.
>
> So after that rambling intro, is there a package/utility that will tell
> me, when in this situation, what package needs
> "oldPackageNoLongerNeeded" and why it is being brought into my emerge.

Yes, the package that will tell you is "emerge" itself.  Use its "-t" 
option to get a dep-graph of why something is getting emerged.  Also, 
you can use its "-v" option if you want to see if the package comes from 
some overlay.

Furthermore, *after* "emerge -C oldPackageNoLongerNeeded", do:

   grep oldPackageNoLongerNeeded /var/lib/portage/world

to see if it's still listed in the world file.  If yes, remove all 
traces of it (you can simply edit this world file with a text editor, 
it's safe, but of course you might still want to make a backup of it.)

Re: [gentoo-user] What causes a package to be brought in during a big emerge?

[Dale]

Andrew Lowe wrote:
> Hi all,
>     I've done an:
>
> "emerge --pretend -NuD world"
>
> and whilst reviewing the output, it lists an old package that I played
> around with in the past but now no longer need. In turn I do:
>
> "emerge -C oldPackageNoLongerNeeded"
>
> the package is removed and I in turn do another
>
> "emerge --pretend -NuD world"
>
> but "oldPackageNoLongerNeeded" is still there, although emerge tells
> me its now gone from "U" to "N" ie Update to New. I've fired up "ufed"
> and removed what I thought would be the appropriate USE tag, run the
> emerge again and it's still there. I've tried:
>
> "equery depends oldPackageNoLongerNeeded"
>
> and it lists nothing as needing "oldPackageNoLongerNeeded"
>
> I've looked through the emerge help and nothing springs to mind as
> telling me why "oldPackageNoLongerNeeded" is being brought in.
>
>     So after that rambling intro, is there a package/utility that will
> tell me, when in this situation, what package needs
> "oldPackageNoLongerNeeded" and why it is being brought into my emerge.
>
>     Thanks for any help,
>         Andrew
>
> p.s. Tried Google on this and just couldn't seem to get the right
> keywords o find anything.....
>
>

Check into the -t option.  That should tell you what pulls it in even
tho it is not installed.  Just add the -t to the option you already have.

Dale

:-)  :-) 

Re: [gentoo-user] Re: What causes a package to be brought in during a big emerge?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 715 bytes --]

On Sat, 26 Sep 2009 05:36:45 +0300, Nikos Chantziaras wrote:

> Furthermore, *after* "emerge -C oldPackageNoLongerNeeded", do:
> 
>    grep oldPackageNoLongerNeeded /var/lib/portage/world
> 
> to see if it's still listed in the world file.  If yes, remove all 
> traces of it (you can simply edit this world file with a text editor, 
> it's safe, but of course you might still want to make a backup of it.)

emerge -C should remove it from the world file. If it does not, something
is broken that requires more than editing world.

You can also check this with emaint -c world.


-- 
Neil Bothwick

This universe is sold by mass, not by volume.
Some expansion may have occurred during shipment

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: What causes a package to be brought in during a big emerge?

[Volker Armin Hemmann]

On Samstag 26 September 2009, Neil Bothwick wrote:
> On Sat, 26 Sep 2009 05:36:45 +0300, Nikos Chantziaras wrote:
> > Furthermore, *after* "emerge -C oldPackageNoLongerNeeded", do:
> >
> >    grep oldPackageNoLongerNeeded /var/lib/portage/world
> >
> > to see if it's still listed in the world file.  If yes, remove all
> > traces of it (you can simply edit this world file with a text editor,
> > it's safe, but of course you might still want to make a backup of it.)
> 
> emerge -C should remove it from the world file. If it does not, something
> is broken that requires more than editing world.
> 
> You can also check this with emaint -c world.
> 

well sometimes an app appears more than once in world  and after an removal 
instances remain - yes, it should not happen.

Re: [gentoo-user] Re: What causes a package to be brought in during a big emerge?

[beolach]

Quoting Nikos Chantziaras <realnc@arcor.de>:
> On 09/26/2009 04:05 AM, Andrew Lowe wrote:
<snip>
>> I've tried:
>>
>> "equery depends oldPackageNoLongerNeeded"
>>
>> and it lists nothing as needing "oldPackageNoLongerNeeded"
>
> "equery depends" won't list anything unless the package is question is
> installed.

Try "equery depends -a oldPackageNoLongerNeeded".  That should search all
available packages in the portage tree, including uninstalled ones.


Conway S. Smith

Re: [gentoo-user] Re: What causes a package to be brought in during a big emerge?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 644 bytes --]

On Sat, 26 Sep 2009 15:22:30 +0200, Volker Armin Hemmann wrote:

> > emerge -C should remove it from the world file. If it does not,
> > something is broken that requires more than editing world.
> > 
> > You can also check this with emaint -c world.
> >   
> 
> well sometimes an app appears more than once in world  and after an
> removal instances remain - yes, it should not happen.

If that because the world file was hand edited, or you you mean one entry
for cat/pkg and one for cat/pkg-ver? 

emaint should still find and fix it.


-- 
Neil Bothwick

If everything is coming your way then you're in the wrong lane.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: What causes a package to be brought in during a big emerge?

[Volker Armin Hemmann]

On Samstag 26 September 2009, Neil Bothwick wrote:
> On Sat, 26 Sep 2009 15:22:30 +0200, Volker Armin Hemmann wrote:
> > > emerge -C should remove it from the world file. If it does not,
> > > something is broken that requires more than editing world.
> > >
> > > You can also check this with emaint -c world.
> >
> > well sometimes an app appears more than once in world  and after an
> > removal instances remain - yes, it should not happen.
> 
> If that because the world file was hand edited, or you you mean one entry
> for cat/pkg and one for cat/pkg-ver?
> 
> emaint should still find and fix it.
> 

the second. And then cat/pkg-ver (cat/pkg:slot) stayed around after an unmerge 
and forced stuff back in.

emaint should find it, but in my experience it failes once in a while.

Re: [gentoo-user] Re: What causes a package to be brought in during a big emerge?

[Dale]

Volker Armin Hemmann wrote:
> On Samstag 26 September 2009, Neil Bothwick wrote:
>   
>> On Sat, 26 Sep 2009 15:22:30 +0200, Volker Armin Hemmann wrote:
>>     
>>>> emerge -C should remove it from the world file. If it does not,
>>>> something is broken that requires more than editing world.
>>>>
>>>> You can also check this with emaint -c world.
>>>>         
>>> well sometimes an app appears more than once in world  and after an
>>> removal instances remain - yes, it should not happen.
>>>       
>> If that because the world file was hand edited, or you you mean one entry
>> for cat/pkg and one for cat/pkg-ver?
>>
>> emaint should still find and fix it.
>>
>>     
>
> the second. And then cat/pkg-ver (cat/pkg:slot) stayed around after an unmerge 
> and forced stuff back in.
>
> emaint should find it, but in my experience it failes once in a while.
>
>
>   

Since the world file is in alphabetical order, it should be easy enough
to find tho.  They should be right there together.

Would it be possible that emerge just removes the first match it sees in
the world file when it unmerges a package?  Could this be a "minor" bug?

Dale

:-) :-) 

Re: [gentoo-user] What causes a package to be brought in during a big emerge?

[Alex Schuster]

Andrew Lowe writes:

> 	So after that rambling intro, is there a package/utility that will tell
> me, when in this situation, what package needs
> "oldPackageNoLongerNeeded" and why it is being brought into my emerge.

Try these:

- add -t to your emerge -pNuD world command
- emerge --depcean -pv oldPackageNoLongerNeeded
- grep oldPackageNoLongerNeeded /var/lib/portage/world

	Wonko