I just did an in-place fc6-to-f8 upgrade and it went pretty smoothly.
One gotcha was I had to adjust the qjackd settings thusly:
1. Change "Server Path" on qjackctl's Setup page to "pasuspender jackd
--". This suspends PulseAudio so it isn't hogging the ALSA ports while
I'm running jackd.
2. Change the "Interface" setting to "hw:0" from "default". jackd
wouldn't start up otherwise. Any idea why?
New Fedora 8 binaries of Audacity (CVS snapshot from 20080123) for
i386 and x86_64 can be found here:
PPC/ppc64 builds are only available in koji until they expire:
PortAudio v19 in Audacity has seen enough changes as to improve ALSA
support here compared with Audacity 1.3.3-beta and 1.3.4-beta. JACK
support is built in again, but still might be disabled by default in
one of upstream's next releases.
Please keep success/failure reports coming...
> Hi everyone!
> Fedora 8, 7 and 6 still contain Audacity 1.3.2-beta. There have been
> two new beta releases since then. Sooner or later somebody surely will
> open a ticket and use reproachful words when requesting an upgrade to
> 1.3.4-beta, just because it's newer. So, here's some sort of status
> update and the opportunity for the community to help with evaluating
> that latest beta release. We, the packagers, appreciate all forms of
> success and failure reports as well as feedback sent to the Audacity
> developers upstream.
> Fedora 8 binaries of Audacity 1.3.4-beta for i386 and x86_64 can be found here:
> They are not signed, but the directory contains a SHA1SUMs file signed
> with my key.
> The source of these packages can be found in Fedora Package CVS, of
> course, albeit in a separate devel branch. A README file in the
> rpms/audacity directory contains a few notes about that branch:
> The packages were built with wxGTK 2.8.4 as included with Fedora 8 and
> no longer with wxGTK 2.6.x. This may result in changes in the GUI.
> Anyway, I'm interested in success and problem reports, and I'm even
> more interested in anybody's attempts at reporting problems to the
> upstream developers.
I was looking at upgrading ardour to 2.2 for f8 and devel when I came
across the following note:
Important note for upgrading from 2.1 or earlier
Please note that for several of the new features and fixes listed below,
it is necessary to remove or update the following files if you have them
in your ~/.ardour2 directory:
We have still not come up with an easy way to "upgrade" per-user files
when we change key bindings, the menu structures and add/remove various
UI color codes.
So... how should we handle this in our package? It seems nasty to do
something like "rm /home/*/.ardour2/ardour2_ui.rc" at install time, but
that might still be the best way to deal with this.