Your message dated Sat, 22 Mar 2008 09:17:16 -0400 with message-id <20080322131716.GA5604@tang.vireo.org> and subject line fixed by previous upload has caused the Debian Bug report #457007, regarding bug with tempo change to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 457007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457007 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: [cannam@all-day-breakfast.com: Re: [Rosegarden-devel] [Rosegarden-user] bug in debian unstable]
- From: Mike O'Connor <stew@vireo.org>
- Date: Tue, 18 Dec 2007 23:56:12 -0500
- Message-id: <20071219045612.GA30708@tang.vireo.org>
Package: rosegarden Version: 1:1.6.0-1 Forwarded: rosegarden-devel@lists.sourceforge.net Severity: Normal X-Debbugs-CC: rosegarden-devel@lists.sourceforge.net Forwarding this bug which was originally reported to the rosegarden-user list to the Debian bug tracking system.... thanks, stew ----- Forwarded message from Chris Cannam <cannam@all-day-breakfast.com> ----- From: Chris Cannam <cannam@all-day-breakfast.com> To: rosegarden-user@lists.sourceforge.net Cc: rosegarden-devel@lists.sourceforge.net, Paul Ulrich Niggli <paul.niggli@swissonline.ch> Subject: Re: [Rosegarden-devel] [Rosegarden-user] bug in debian unstable Date: Tue, 18 Dec 2007 20:15:37 +0000 On Tuesday 18 December 2007 15:59, Paul Ulrich Niggli wrote: > I think, i found a bug in debian-unstable package > of rosegarden.when i save tempo-changes as > fixed,they get opend as ramp to following tempo. OK, thanks for the test files and description off-list. I was simply misreading the problem -- it's to do with saving files, not loading files. To reproduce without an example file: * start RG (1.6.0) with empty composition * add new (non-ramped) tempo change with any tempo other than 120, at any point after the start (anything that makes the tempo actually change) * save the file * reload it * note that the opening tempo is now ramped to the one you just added This is a pretty significant bug -- the sort of thing one rolls out a point release for, when it's fixed. We have to fix it first of course. Thanks for the report. Chris ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel ----- End forwarded message -----Attachment: signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
- To: 457007-done@bugs.debian.org
- Subject: fixed by previous upload
- From: Mike O'Connor <stew@vireo.org>
- Date: Sat, 22 Mar 2008 09:17:16 -0400
- Message-id: <20080322131716.GA5604@tang.vireo.org>
Version: 1:1.6.1-1
--- End Message ---