[64studio-devel] Upgrades: GIMP & GCC

[tim hall]

Free Ekanayaka wrote:
> Hi Tim,
> 
> thanks for the feedback.

A pleasure. :)

> |--==> tim hall writes:
> 
>   th> Hi all,
>   th> I'd just like to confirm that the recent GIMP upgrade currently breaks 
>   th> gnome-core on my machine. This is not good.
> 
> What is broken exactly? 

"Formal" package dependences
I will see if I can trace the chain and see which package is causing 
Synaptic to call for the removal of gnome-core. This could be to do with 
my apt set-up. I'll check.

>   th> I also feel it might be worth mentioning that it looks like Debian are 
>   th> pushing the gcc-4.3 transition through now. I know that there are a 
>   th> couple of important multimedia apps that appear to be having trouble 
>   th> with the transition like openmovieeditor, audacity also appears to have 
>   th> some lively bugs. Rosegarden and Ardour seem to be making it through the 
>   th> pass thanks to the persistence of their maintainers.
> 
> This needs work indeed. Forwarding the relevant bug reports upstream
> would probably be a Good Thing.

OK, will do. Should I Cc: 64studio-devel if I do?

>   th> This process is only relevant to these packages being able to migrate to 
>   th> Debian testing (lenny/sid) as Free already has measures in place to get 
>   th> reasonably up-to-date versions of these multimedia apps into 64 Studio.
> 
> Right, we have a rocking backport system now :)

:) :)

>   th> My concern is that some of the Desktop apps with multimedia functions 
>   th> are becoming out-of-date. 

> At least for flashplugin-nonfree, a backport of the sid version is
> available in the testing branch of 64 Studio. I can try to backport
> lastfm as well, feel free to ask more backports. As long as they
> succeed without too much work there's no problem in adding them.

flashplugin-nonfree and lastfm would be *very* cool!

>   th>  From a user/testers perspective I think it would be great if 64 Studio 
>   th> testing tracked Debian testing all the time. I can just picture Free 
>   th> holding his head in his hands as I type that. ;) It's got to be better 
>   th> than backporting GNOME in order to include the latest GIMP? No?
> 
> Well, 64 Studio/testing has been a bit too much radio-active
> lately. However the idea of 64studio/testing would be basically to be
> a testing area for updates tarted at the testing branch. So,
> everything should be relatively "stable", meaning that main libraries
> and components should not change over the time. It was probably a bad
> move to push on back backports for gimp 2.4.
> 
> Said this, the idea of Debian/testing is different, as this is a
> testing are targeted not to the previously released version, but
> rather to the next one, and things here can break more easly, as main
> components are frequently replace and change over the time. My view is
> this kind of thing is not what 64 Studio wants to offer, which is a
> (supposed to be ;) ever stable and at the same up-to-date system. 
> 
> Anyway as I generally upload everything to Debian/unstable (and hence
> eventually to testing), I would suggest that 64 Studio users willing
> to stick to Debian/testing should simply upgrade to Debian/testing,
> where all the development actually takes place. After that testing
> (lenny) gets released, it serve as a new stable base for 64 Studio and
> the regular 64 Studio users can upgrade as well.

OK, point taken. I actually have a spare(ish) machine that I could try 
this out on and see what breaks.

cheers,

tim