On Thu, Jan 20, 2011 at 07:59:38PM +0100, Alessandro Ghedini wrote:
> Hi all,
> I've just adopted the bug #520271 (RFA: ecasound2.2), I think it is a good
> candidate to get maintained by the Multimedia Team. 
> The main problem I see is that the source package is named 'ecasound2.2' 
> even if the current version is 2.7.0 (2.7.2 if you consider upstream). 
> >From the README.Debian:
>      ecasound2.2 release was a major change from 2.0 series; 
>      and that was the reason for ecasound2.2 package name; we had two
>      versions to coexist.
>      For transition purposes Debian source package name still retains 
>      the ecasound2.2 name.
> I think this may lead to confusion and renaming the source package to just 
> 'ecasound' would make things cleaner and clearer. AFAIK a solution would be 
> to upload the new 'ecasound' and ask for removal for the 'ecasound2.2'. 
> Is this right?

I haven't see a reply to this. One question I have is 
about handling bug relationships for all the renamed

For example, can a new source package 'ecasound' close bugs
submitted against package ecasound2.2?



Joel Roth

pkg-multimedia-maintainers mailing list

Reply via email to