cannot achieve system upgrade with synaptic

I broke one of my "Big Rules", and upgraded to Ardour 2.2 in the middle of a big project. Thankfully the workflow is so much better in 2.2 that it took me all of 10min to be at home with the new editing model. There are still a few things I'd like changed (for instance the inverted black selection colours - it hides the lower waveforms a bit when you want to match them visually) - The SVN version apparently has this fixed already, so, we'll just wait a short while for 2.3 (or 2.2 SP1 - dose speak) So, one more recording session to go for my project - and then it's time for Mastering! Cheers,

well, I finally have the Ardour 2.2 update, and suffice it to say it is a huge improvement. i have yet to log into Gnome to see if the flakiness has been remedied, but otherwise smooth sailing. Time to record! dav=-0

Compiling isn't that bad, and it's an excellent way to be able to keep up on the bleeding edge of what is going on. Better still, it's pretty easy to maintain _two_ versions of Ardour, and that way you can keep your system completely on stable repos. You get to play with the latest shiny toys, but don't have to risk blowing things up. You can get real work (or play) done instead of futzing around with operating system stuff. I have compiled Ardour exactly once, on a laptop I could take someplace that had broadband. That laptop was not otherwise suitable for recording/Ardour, it was just a test to see if I could figure it out. Compiling Ardour is different than the usual configure/make/make install. I am in the dark ages of dialup at home, and I probably can't download all the pieces needed. It's actually one of those things, where once you get all the packages needed, you can start the process by typing only five letters. You can safely keep the needed packages updated with Synaptic, download the latest source from time to time, and fire it off again to play with a new version with no risk of blowing up the system.

After struggling with this for some time, I found a solution. I was also incorrect earlier in mentioning my repos, I have Testing/Tryout enabled as well. When I say solution, this means it is completely _not_ tested well, and is probably not recommended except for the brave or the stupid. I qualify as both! Excited about the 64studio and 64studio-tasksel-data possible solutions, I updated apt, and removed those two, (Synaptic immediately suggested a new 64studio-tasksel-data) but still got the "cdd-utils is trying to overwrite whatever". I poked around a bit, and found that 64studio-themes and 64studio-utils both depended on this. Here's a way to see it: # apt-cache depends 64studio-utils and that returns pages of junk to look for. This way gets right to the point: # apt-cache depends 64studio-utils | grep cdd-utils and it only spits out this: Depends: cdd-utils Ahh, there it is in more readable fashion. It's the same results with 64studio-themes, but not with cdd-utils. i.e., I thought that I should be able to run 'apt-cache depends' on cdd-utils and have it spit out a list of things that needed it, but all it showed was itself. Lacking any more clever methods, I just groped through Synaptic pretending to remove things until I found those two. Brute force and awkwardness, as my dad used to say. I decided to remove those two packages, and Viola! Ardour 2.2 finally installed (after being cached locally for several days)! But beware, this is probably not a recommended thing to do! I cheerfully logged off and back on to see what was damaged, and I wasn't that suprised to see an error about 'can't load 64theme' (because I knew I had removed it), but it showed me the stupid Debian flower login. "no problem" I thought, "I can install more GDM greeter themes". I was quite suprised however, to have no panel (taskbar) at the bottom! Wallpaper and desktop shortcuts were intact, as well as my precious xorg.conf. As per Federico's problem, I checked Nautilus and it worked fine. I (superficially?) fixed it in ten seconds, by right-clicking, chose Add New Panel, right-clicked that and added the Main Menu and I was back in business. Added a clock, Window List/Workplace Switcher and a terminal shortcut, that's all I need on a taskbar anyway. I installed GDM-themes, chose another one from Administration--Login Window and I was back in business. HOWEVER, I was wondering what cdd-utils really was. A quick google around, and it's something for custom debian distributions, of which 64studio definitely is. This puzzled me, because I have remastered several Debian custom distros, and that wasn't anything I was familiar with. HOWEVER, I may have easily scrambled something that will rear it's head later, if cdd-utils is something that is referred to later. I am limited to dialup at home, and come upgrade time, I usually just don't format the drives with data and /home and reinstall. I update a few packages, but at ten megabytes an hour, any major upgrade is impractical.

Perhaps we should call 64studio testing the "Tryout" repository, as it is not debian testing based. Free was talking about fixing "Tryout" - 2.1 pre 7

I have always used the stock repos on this install. I also forgot to comment, that I also manually tried removing dd-utils_0.3_all.deb from the apt cache. I thought that perhaps it was corrupted, and that would force Synaptic to download a fresh one (albeit the same version).

Yup, the answer is in the mailing list archive (don't know why I did not try looking for information in the maling list before): Free said: "If you remove the 64studio package, then the 64studio-tasksel-data package, then reinstall the 64studio package, that should be fixed." Well, that worked for me. Now I'm using testing again :) And everything looks just fine!

Free sent a mail to the development mailing list yesterday, about fixing the testing repository. He has done it, but you need to downgrade some packages to fix the problem. My system is packed for transport at the moment, so I cannot post the mail here yet. I'll see if I can do it tonight.

I am having the same problem with cdd-utils_0.3_all.deb I am not using any testing repos, just 64studio and I think Etch. Last night I reloaded the repos, and still had the same problem. Is there any risk in forcing it? I am on dialup, and would rather not bork the system as well. I have installed SVN 2.0-ongoing on a test machine, but don't want to mess up the main machine (in the middle of a project).

I loaded my big project, fingers crossed - and everything still works. Rubber band is a neat feature. Just take a look at the new editing commands to familiarize yourself. Cheers

I found ardour 2.2 in the testing repository today. Did not have time to install yet, but just thought I'll let you know...

From the Linux Audio mailing list, the answer is by Paul Davies. I infer that Susanne is having problems with the VST plugins, but no more than that. I have installed ardour 2.1 from 64studio testing (therefore with no VST support, I am using VSTHost for the VST plugin I use) and, like Dav, I am longing to have the 2.2 running. Of course, I'll back up my projects just in case as Quentin suggests. On Wed, 2008-01-23 at 16:31 +0100, Susanne Schneider wrote: > hi all, > this week I compiled Ardour 2.2 with vst support and now have to experience my already existing sessions opening without vst plugins... > It's not a catastropy as I'm only a hobby musician and can rebuild my few sessions (I mostly use ladspa anyway). > Of course it would be nice to be able to open the old sessions completely, including vst-plugins - does anyone know if there is a solution for that? not yet. we changed the way plugins are identified between 2.1 and 2.2, and i forgot to deal with back-compatibility. --p

Yes - I said it. Make backups of your projects BEFORE you move to 2.2 because I honestly don't know. If it works fine (and it should) no problems! If not, you can go back to 2.1

Do you know if the new workflow is likely to change the way Ardour opens and saves '*.ardour' files? I also have things in the works, that i'd like not to lose control of. Should it open my sessions okay? And save them? thanx- dav=-0

The guys will now put their energy in getting the 2.1 release done. Just after that you can expect ardour 2.2 in the new testing repository. Speaking of the work flow, maybe it is a good thing 2.2 is not yet available, because I have a large project to finish in the next two weeks...

So- to clarify , I thought i'd be getting the new Ardour 2.2. IS this not the case? Is intended to go into the repository soon? I AM all excited about the new workflow- and a bit daunted. I'm guessing i'l have to wait a few more days yes? lotsa love dav=-0

I noticed the same with nautilus, especially in the "Browser windows" mode. I am going STABLE as well...

Well david, I just can say that after what I did and upgrading everything with synaptic(using the testing repo) my system looked prety well until I restarted, Then I started having problems with Nautilus. It crashes a LOT. I'm not sure if it has anything to do with this cdd-utils package, but I think I will just install 64studio again, and stay STABLE untils this problem has been solved. So i hope to get some news from the community about this, so I know when I can activate my testing repos again. Cheers, Federico

I downloaded the current Master ISO from 64studio's apt site. It is not ready yet, and I had to change a few thinks, but it worked. I am back at 2.1 Pre7. Ardour should be 2.1 Cheers,

Now i have new gimp, ( 2.4) but ardour and others have not been upgraded. New gimp is nice, but that's not the point. Also, my gnome launcher panel is all screwed up suddenly - the gimp launcher has no icon, and will not launche the new gimp recently installed. What is the newest Ardour version number again?

Well i got tired of not been able to install new software because of that so i installed cdd-utils_0.3_all.deb with dpkg --force-all -i. Synaptic stopped complaining. I hope i did not break anything. I really dont want to reinstall 64 studio again.

Same problem here. The first time it happened i thoght it was my fault, cause I had installed some packages from SID. But now I have made a complete new intall, and get the exact same error. :( Now i have forgoten how I got flash running the last time. I tryed with a backported version of gnash for etch, but it did not work. :(

I am experiencing similar problems. One of the latest changes on testing breaks the upgrades... I reported it to Daniel and Free, and they should have a fix for us soon.