[64studio-devel] Upgrade and Kept Back Packages

[dave]

Hi Susan,


Susan Dridi wrote:
> Hi Dave and All,
>
> dave wrote:
>   
>> Hi Susan,
>>
>> Susan Dridi wrote:
>>     
>>> Hi All,
>>>
>>> I did an apt-get update and apt-get upgrade tonight and got the message:
>>>
>>> The following packages have been kept back:
>>>    aeolus ardour blender
>>>
>>>   
>>>       
>> I am using "i386".
>> The 64studio here, the one I keep at 64studio testing,
>> is keeping these back.
>> blender flac gigedit
>> if I type in a terminal
>> # dpkg -l | grep "ardour"
>> ardour = 2.4.1-1~etch1
>> are you on the same version?
>>     
>
> I forgot to say, I'm using the 64 bit version of 64 Studio 2.1. I
> installed 2.0 and then upgraded to 2.1.
>
> $sudo dpkg -l | grep "ardour"
>
> 2.0.3-2~bpo.1
>
> $sudo dpkg -l | grep "blender"
>
> 2.42a-4.64studio1
>
> $sudo dpkg -l | grep "aeolus"
>
> 0.6.6+2-4~bpo.1
>
> When I do apt-cache show ardour, I see:
>
> Version: 1:2.4.1-1~etch1
> Conflicts: ardour-gtk
>
>   

I remember doing this update/upgrade quite some time back.
Browse down to "Hows that for speed" posted by Daniel.
I'm not sure about using this with 2.0 to 2.1 and I don't want
you to break your system. Maybe this explains your Ardour on hold?
I would just wait!
http://www.64studio.com/node/417
I'm not sure. Just something to think about.
I still have a 2.0 install I've upgraded, I will check it out.

>> even if I enable 64studio backports, I have no ardour on hold.
>>     
>>> I don't use synaptic, so I don't think that's the problem. (There is 
>>> evidently a bug if you switch between synaptic and apt, sorry I can't 
>>> remember the details that my friend patiently explained to me.)
>>>
>>>   
>>>       
>> Thank you for this info, I am going to google to find out more.
>> The upgrade to lenny I did this morning (on a testing disk)
>> was much better when I didn't touch synaptic.
>> I am going to have to find out about this bug
>>     
>
> I just wanted to clarify. If you just use apt or if you just use
> synaptic, there is no problem. The problem apparently happens when you
> switch from using synaptic to apt. I'm really sorry, I don't have any
> more details. I think my friend was going to file a bug report.
>
> Cheers!
>
> -Susan
>
>
>
>
> _______________________________________________
> 64studio-devel mailing list
> 64studio-devel at 64studio.com
> http://lists.64studio.com/mailman/listinfo/64studio-devel
>
>   

apt/synaptic bug:
This tip you gave is important,
I always used apt-get to remove the software I don,t use

Like this in a terminal: type

$ dpkg --get-selections > software1
and again
$ dpkg --get-selections > software2

This will create 2 files in your home directory
software1
software2
These list the software installed, leave software1 alone.

# grep "iceweasel" software2
# grep "blue" software2
# grep "bluetooth" software2
etc.,etc., only you know what is not needed.

# apt-get remove --purge (not needed software)

Watch very carefully for shared libs and others apt might try to remove.
This method will also keep a .bash_history of the software you have removed.

$ dpkg --get-selections > software2
again will update the file minus the software removed.

Sometimes I use synaptic to remove the software,
and enable/disable repositories, before going back to apt.

So I was going back and forth a lot!
Your post explains a lot.
I still keep browsing for info on the bug, but all I find are apt bugs & 
synaptic bugs.
I will keep looking.

Thanks again!

Cheers,
dave.