Re: [Rosegarden-devel] Rosegarden 10.10 released for testing

2010-11-02 Thread Orcan Ogetbil
On Tue, Nov 2, 2010 at 6:16 AM, Chris Cannam wrote: > On Tue, Nov 2, 2010 at 2:07 AM, D. Michael McIntyre > wrote: >> I rolled out the release today.  Rather than going through the usual process >> of making a token attempt to get people to test it before publishing the >> release, I compiled the t

Re: [Rosegarden-devel] 10.04.2 provisional

2010-04-29 Thread Orcan Ogetbil
On Thu, Apr 29, 2010 at 5:26 AM, Chris Cannam wrote: > On Thu, Apr 29, 2010 at 10:06 AM, Chris Cannam > wrote: >> On Thu, Apr 29, 2010 at 9:53 AM, Chris Cannam >> wrote: >>> I'll wait until I have one positive response (someone telling me it >>> builds, runs, and reports the right version). >> >> I

Re: [Rosegarden-devel] [Rosegarden-user] ROSEGARDEN 10.04 RELEASED

2010-04-27 Thread Orcan Ogetbil
On Thu, Apr 22, 2010 at 9:44 PM, Thomas Sattler wrote: > >> * Restore duration-change shortcuts in notation forgotten in 10.02 >> (Thorsten Alteholz) > > > Thanks so much for getting this fix into the new version!  Since I work so > much with the Notation Editor, I had to downgrade Thorn back to 1.

Re: [Rosegarden-devel] release?

2010-04-22 Thread Orcan Ogetbil
On Thu, Apr 22, 2010 at 5:01 PM, D. Michael McIntyre wrote: > On Thursday 22 April 2010, Chris Cannam wrote: > >> This is a routine maintenance release with a number of bug fixes > > OK, I folded that into the stub release note I had ready, and I rolled a > tarball.  I'm test building the tarba

[Rosegarden-devel] some user feedback from Fedora

2010-02-28 Thread Orcan Ogetbil
Hi all, I submitted rosegarden-10.02.1 to our testing repo last week and we started getting some user evaluations in our audio production lists. Niels Mayer gave us a very nice feedback with his opinions about usability of rosegarden-10.02.1. I thought it would be good to share this with the devel

Re: [Rosegarden-devel] Packaging issues on Fedora

2010-02-20 Thread Orcan Ogetbil
On Sat, Feb 20, 2010 at 6:26 AM, Luis Garrido wrote: >> I understand. But there is a strict Fedora policy here that a fonts >> file must go to /usr/share/fonts (period) >> (I can try dealing with this with symlinks though. Yet I still have to >> patch the fonts out of the .qrc file) >> This is main

Re: [Rosegarden-devel] Packaging issues on Fedora

2010-02-20 Thread Orcan Ogetbil
On Fri, Feb 19, 2010 at 11:01 AM, Dave Plater wrote: > I'm lead to understand that > /usr/share/icons/hicolor/32x32/rosegarden.png is the correct place and Minor correction: This needs to be /usr/share/icons/hicolor/32x32/apps/rosegarden.png which is correct in your standard installation. Then Ic

Re: [Rosegarden-devel] Packaging issues on Fedora

2010-02-20 Thread Orcan Ogetbil
On Fri, Feb 19, 2010 at 5:43 AM, Chris Cannam wrote: > On Fri, Feb 19, 2010 at 6:54 AM, D. Michael McIntyre > wrote: > > Happy to do something to help out here, but I want to be clearer on > what's needed.  The configure sets CXXFLAGS to contain both defines > that are meaningful to our code (e.g.

Re: [Rosegarden-devel] Packaging issues on Fedora

2010-02-20 Thread Orcan Ogetbil
On Fri, Feb 19, 2010 at 4:06 AM, Dave Plater wrote: > On 02/19/2010 08:54 AM, D. Michael McIntyre wrote: >> >>> 2) Can we add the line >>>    GenericName=Audio and MIDI Sequencer >>> to data/desktop/rosegarden.desktop ? >>> >> Yes. >> > I've copied and fixed the desktop file a long time ago and ins

Re: [Rosegarden-devel] Packaging issues on Fedora

2010-02-20 Thread Orcan Ogetbil
Hi Michael, thanks for your reply! On Fri, Feb 19, 2010 at 1:54 AM, D. Michael McIntyre wrote: > On Thursday 18 February 2010, Orcan Ogetbil wrote: > >> 6) The DSSI and LADSPA plugin paths are wrong on 64 bit systems. I am >> attaching a patch to correct the issue. > > Wr

[Rosegarden-devel] Packaging issues on Fedora

2010-02-18 Thread Orcan Ogetbil
Hi all, I am one of the comaintainers of the Rosegarden package at Fedora. I wanted to update our version to 10.02. During the preparation I came upon some issues that I wanted to report. I thought maybe if I can get my "fixes" upstreamed, I won't have to deal with updating my patches in the subse