Re: [fluid-dev] Problem in fluidsynth (Ubuntu 11.10) still in Ubuntu 12.04

[Aere Greenway]

Matt:

That was a good suggestion, given the error messages I got.  

I did finally find something similar to what you described (actually, two lines, in a single file in a sub-directory), and changed "precise" to "oneiric", then had the update manager look for updates again.  

This time, I received no error message, but it didn't discover that an update was needed either.  

The version in the of the PPA fix was "1.1.5-1ubuntu1-diwicppa", which is (I think) the same level number as the installed software (something like "1.1.5-2"?), so the updater may not think the fix is applicable (that the fix is older than the installed package).  

The reason I was suggesting we needed to solve the problem again, is that although the original problem was fixed by the PPA, there may have been another change that went in later that re-introduced the problem.  

- Aere

On Sun, 2012-04-29 at 11:38 +1000, Matt Giuca wrote:
>     
> >         So I guess we need to solve this problem yet again.  
> >         
> >     
>     
>     Wait, why do we have to solve it again? Isn't the problem simply that the patch hasn't made it into Ubuntu packages, and the PPA wasn't built for precise?
>     
>     First, a workaround. In your /etc/apt/sources.list, you probably have something like this:
>     
>     http://ppa.launchpad.net/diwic/fluidsynth-test/ubuntu/dists/precise/main/source/Sources
>     
>     I don't know the exact string; I'm guessing from your above error message. Note that it contains the word "precise". Ubuntu upgrader has a habit of changing all of your sources over to the new version name, which sometimes breaks if there isn't a version packaged for that release. So try changing "precise" back to "oneiric" and then re-running apt-get update. That might fix it temporarily.
>     
>     For the long-term solution: what is the patch in question? Did dwic commit the patch into the Subversion repository, or did he just provide a test version in the PPA? If it's the former, can you identify the Subversion commit that fixed the problem? If not, perhaps it's time to put it into Subversion.
>     
>     Of course, David can probably do a better job helping.
>     
> _______________________________________________
> fluid-dev mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/fluid-dev

-- 

Sincerely,
Aere