[gentoo-user] understanding --depclean

[gentoo-user] understanding --depclean

[Michael P. Soulier]

I'm new to gentoo, and I recently changed my USE flags, so I ran

emerge -p --depclean

to see what it suggests removing. 

Along with many others, I see

 dev-lang/python
    selected: 2.4.4-r13 
   protected: none 
     omitted: 2.5.2-r7 

msoulier@anton:~$ equery list | grep dev-lang/python
dev-lang/python-2.4.4-r13
dev-lang/python-2.5.2-r7

So it's going to remove the redundant python version, is that right? Any
chance of shared files being removed?

Thanks,
Mike
-- 
Michael P. Soulier <msoulier@digitaltorque.ca>
"Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction."
--Albert Einstein

Re: [gentoo-user] understanding --depclean

[Dale]

Michael P. Soulier wrote:
> I'm new to gentoo, and I recently changed my USE flags, so I ran
>
> emerge -p --depclean
>
> to see what it suggests removing. 
>
> Along with many others, I see
>
>  dev-lang/python
>     selected: 2.4.4-r13 
>    protected: none 
>      omitted: 2.5.2-r7 
>
> msoulier@anton:~$ equery list | grep dev-lang/python
> dev-lang/python-2.4.4-r13
> dev-lang/python-2.5.2-r7
>
> So it's going to remove the redundant python version, is that right? Any
> chance of shared files being removed?
>
> Thanks,
> Mike
>   

Run this, emerge -uvDNp world and see if it wants to emerge anything. 
man emerge will tell you what the options are for but the -N is the
important part.  Also, you may want to run python-updater as well just
to see if it picks up anything.  Basically, you want to make sure
everything is using the new version of python before removing the old. 
--depclean has no clue on that one.

Also, anytime you run --depclean, run revdep-rebuild -i afterwards just
in case something did get messed up.  Always do that before you log out
or reboot.  I have been known to switch to another console and login
before logging out of the other one.  Just to be sure.

Be very careful with --depclean.  It can really mess up something if you
are not watching close.  Ask first if you're not sure.

Dale

:-)  :-)

Re: [gentoo-user] understanding --depclean

[Neil Bothwick]

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

On Tue, 11 Nov 2008 23:00:08 -0600, Dale wrote:

> Be very careful with --depclean.  It can really mess up something if you
> are not watching close.

That may have been the case some time ago, but depclean is much safer
now. Notice that the warning at the start of its output has disappeared
now?


-- 
Neil Bothwick

All new: Parts not interchangeable with previous model.

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

Re: [gentoo-user] understanding --depclean

[KH]

Dale schrieb:
> Michael P. Soulier wrote:
>   
>> I'm new to gentoo, and I recently changed my USE flags, so I ran
>>
>> emerge -p --depclean
>>
>> to see what it suggests removing. 
>>
>> Along with many others, I see
>>
>>  dev-lang/python
>>     selected: 2.4.4-r13 
>>    protected: none 
>>      omitted: 2.5.2-r7 
>>
>> msoulier@anton:~$ equery list | grep dev-lang/python
>> dev-lang/python-2.4.4-r13
>> dev-lang/python-2.5.2-r7
>>
>> So it's going to remove the redundant python version, is that right? Any
>> chance of shared files being removed?
>>
>> Thanks,
>> Mike
>>   
>>     
>
> Run this, emerge -uvDNp world and see if it wants to emerge anything. 
> man emerge will tell you what the options are for but the -N is the
> important part.  Also, you may want to run python-updater as well just
> to see if it picks up anything.  Basically, you want to make sure
> everything is using the new version of python before removing the old. 
> --depclean has no clue on that one.
>
> Also, anytime you run --depclean, run revdep-rebuild -i afterwards just
> in case something did get messed up.  Always do that before you log out
> or reboot.  I have been known to switch to another console and login
> before logging out of the other one.  Just to be sure.
>
> Be very careful with --depclean.  It can really mess up something if you
> are not watching close.  Ask first if you're not sure.
>
> Dale
>
> :-)  :-)
>
>   
Hi,
As I have written somewhere else a couple of times. If unmerging a part
of the system consider running quickpkg --include-config=y
<forexamplepython> before. Running revdep-rebuild might show you do have
to reinstall whatever you unmerged but emerge might not be able to do it
any longer if something is really broken.
kh

Re: [gentoo-user] understanding --depclean

[Vladimir Rusinov]

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

On Wed, Nov 12, 2008 at 7:41 AM, Michael P. Soulier <
msoulier@digitaltorque.ca> wrote:

> I'm new to gentoo, and I recently changed my USE flags, so I ran
>
> emerge -p --depclean
>
> to see what it suggests removing.
>
> Along with many others, I see
>
>  dev-lang/python
>    selected: 2.4.4-r13
>   protected: none
>     omitted: 2.5.2-r7
>
> msoulier@anton:~$ equery list | grep dev-lang/python
> dev-lang/python-2.4.4-r13
> dev-lang/python-2.5.2-r7
>
> So it's going to remove the redundant python version, is that right? Any
> chance of shared files being removed?
>

There are chances that it will remove some shared files.
To avoid this use revdep-rebuild after emerge --depclean. revdep-rebuild
would rebuild all packages with broken libraries/binaries.

Python is a bit special: you should use python-updater before unmerging
older python. python-updated would reinstall all python modules for newer
python.

-- 
Vladimir Rusinov
http://greenmice.info/

[-- Attachment #2: Type: text/html, Size: 1423 bytes --]

Re: [gentoo-user] understanding --depclean

[Dale]

Neil Bothwick wrote:
> On Tue, 11 Nov 2008 23:00:08 -0600, Dale wrote:
>
>   
>> Be very careful with --depclean.  It can really mess up something if you
>> are not watching close.
>>     
>
> That may have been the case some time ago, but depclean is much safer
> now. Notice that the warning at the start of its output has disappeared
> now?
>
>
>   

That is true but let's say a person updates python but forgets or
doesn't know,  to run python-updater, will --depclean know that?  What
if emerge doesn't work and they don't have buildpkg of some sort in
make.conf? 

I agree that --depclean is a LOT better but there are still situations
where it can mess up a system.   It is best to be careful and really
look at that list before letting it remove a package.  Basically, don't
type it in and walk off to let it do whatever it wants.

I also seem to remember that big warning when --depclean runs.  I think
that may still be there for a reason.  ;-) 

Dale

:-)  :-) 

Re: [gentoo-user] understanding --depclean

[Dale]

KH wrote:
> Dale schrieb:
>   
>> Michael P. Soulier wrote:
>>   
>>     
>>> I'm new to gentoo, and I recently changed my USE flags, so I ran
>>>
>>> emerge -p --depclean
>>>
>>> to see what it suggests removing. 
>>>
>>> Along with many others, I see
>>>
>>>  dev-lang/python
>>>     selected: 2.4.4-r13 
>>>    protected: none 
>>>      omitted: 2.5.2-r7 
>>>
>>> msoulier@anton:~$ equery list | grep dev-lang/python
>>> dev-lang/python-2.4.4-r13
>>> dev-lang/python-2.5.2-r7
>>>
>>> So it's going to remove the redundant python version, is that right? Any
>>> chance of shared files being removed?
>>>
>>> Thanks,
>>> Mike
>>>   
>>>     
>>>       
>> Run this, emerge -uvDNp world and see if it wants to emerge anything. 
>> man emerge will tell you what the options are for but the -N is the
>> important part.  Also, you may want to run python-updater as well just
>> to see if it picks up anything.  Basically, you want to make sure
>> everything is using the new version of python before removing the old. 
>> --depclean has no clue on that one.
>>
>> Also, anytime you run --depclean, run revdep-rebuild -i afterwards just
>> in case something did get messed up.  Always do that before you log out
>> or reboot.  I have been known to switch to another console and login
>> before logging out of the other one.  Just to be sure.
>>
>> Be very careful with --depclean.  It can really mess up something if you
>> are not watching close.  Ask first if you're not sure.
>>
>> Dale
>>
>> :-)  :-)
>>
>>   
>>     
> Hi,
> As I have written somewhere else a couple of times. If unmerging a part
> of the system consider running quickpkg --include-config=y
> <forexamplepython> before. Running revdep-rebuild might show you do have
> to reinstall whatever you unmerged but emerge might not be able to do it
> any longer if something is really broken.
> kh
>
>
>   

Another good way is to have it in make.conf.  I have buildsyspkg in mine
so that it does it automatically.  It hasn't saved me yet since I follow
my own advice but it may one day.

Dale

:-)  :-) 

Re: [gentoo-user] understanding --depclean

[Neil Bothwick]

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

On Wed, 12 Nov 2008 11:13:00 -0600, Dale wrote:

> > That may have been the case some time ago, but depclean is much safer
> > now. Notice that the warning at the start of its output has
> > disappeared now?


> That is true but let's say a person updates python but forgets or
> doesn't know,  to run python-updater, will --depclean know that?

If packages depnd on the older version of python, depclean won't remove
them. If it's just a matter of depending on the correct modules,
python-updater will fix that after the older python has been removed.

> What if emerge doesn't work and they don't have buildpkg of some sort in
> make.conf?

Why would emerge stop itself working?

> I agree that --depclean is a LOT better but there are still situations
> where it can mess up a system.   It is best to be careful and really
> look at that list before letting it remove a package.  Basically, don't
> type it in and walk off to let it do whatever it wants.

While I always run it with --pretend first, that's because I'm more
curious than paranoid. What are these situations in which it can really
mess up a system and are they situations that any sensible user would put
themselves in?

> I also seem to remember that big warning when --depclean runs.  I think
> that may still be there for a reason.  ;-) 

See above, that warning has been gone for some time. The preamble now
contains this indication that depclean is a lot more cautious.

 * As a safety measure, depclean will not remove any packages
 * unless *all* required dependencies have been resolved.  As a
 * consequence, it is often necessary to run `emerge --update
 * --newuse --deep @system @world` prior to depclean.


-- 
Neil Bothwick

If your VCR still flashes 12:00 - then Linux is not for you.

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

Re: [gentoo-user] understanding --depclean

[Dale]

Neil Bothwick wrote:
> On Wed, 12 Nov 2008 11:13:00 -0600, Dale wrote:
>
>   
>>> That may have been the case some time ago, but depclean is much safer
>>> now. Notice that the warning at the start of its output has
>>> disappeared now?
>>>       
>
>
>   
>> That is true but let's say a person updates python but forgets or
>> doesn't know,  to run python-updater, will --depclean know that?
>>     
>
> If packages depnd on the older version of python, depclean won't remove
> them. If it's just a matter of depending on the correct modules,
> python-updater will fix that after the older python has been removed.
>   

It seems portage has changed a lot in how it tracks things. 

>   
>> What if emerge doesn't work and they don't have buildpkg of some sort in
>> make.conf?
>>     
>
> Why would emerge stop itself working?
>   

From my unerstanding, if it can't find python, no worky.  See above tho.

>   
>> I agree that --depclean is a LOT better but there are still situations
>> where it can mess up a system.   It is best to be careful and really
>> look at that list before letting it remove a package.  Basically, don't
>> type it in and walk off to let it do whatever it wants.
>>     
>
> While I always run it with --pretend first, that's because I'm more
> curious than paranoid. What are these situations in which it can really
> mess up a system and are they situations that any sensible user would put
> themselves in?
>
>   
>> I also seem to remember that big warning when --depclean runs.  I think
>> that may still be there for a reason.  ;-) 
>>     
>
> See above, that warning has been gone for some time. The preamble now
> contains this indication that depclean is a lot more cautious.
>
>  * As a safety measure, depclean will not remove any packages
>  * unless *all* required dependencies have been resolved.  As a
>  * consequence, it is often necessary to run `emerge --update
>  * --newuse --deep @system @world` prior to depclean.
>
>
>   

I haven't used it in a while so I was not aware that it was changed. 
Looks like there as been some new code added here as well. 

I still think it reasonable to say that a person should be careful. 
Nothing is perfect.  I know I watch it when I am doing some house cleaning.

Dale

:-)  :-)