Comment 3 for bug 28682

Well, this issue is rather difficult to handle. I'll elaborate on what happens and then perhaps we can see if there's a better solution.

There were two changes implemented that affect this:
- First, the input widget used for entering the sourcepackage name now [only] matches exact strings. So if you enter "my" it will fail and show you options containing that fragment, but if you enter "mysql" it will do an exact match, find the package name, and then move on.

- The next step after that is verifying whether there is a package with that name published in Ubuntu. There is no source or binary package called "mysql" in Ubuntu -- there is mysql-dfsg-5.0 (as apt-cache showsrc mysql-dfsg-5.0 will show you however)

Given that we were unable to find a package with that name in Ubuntu, we add the comment and life goes on. The person triaging Ubuntu bugs can use that information to assign to the correct package, so I think it's not the worst solution, but there may be better ones.