please keep GnuBook but close it to new bugs

Hi Mang,

Rather than just closing gnubook we can deactivate and rename it and then create an alias so that people going to gnubook will be automatically redirected to bookreader.

Before we do that, though, you should either transfer all of the existing bugs from gnubook to bookreader or mark them as terminal (WONTFIX, INVALID, etc).

Please let me know if that's how you'd like to proceed.

Hi Brad,

I've already transfered the existing bugs to BookReader using the "Also affects" feature. If you can deactivate and set up the redirect it would be great!

Thanks,
  - mang

I've renamed gnubook to gnubook-deactivated, deactivated it, and setup an alias for gnubook that points to bookreader. I hope that achieves what was wanted.

Thanks, Tom

Thanks for deactivating GnuBook. When I click on a bug that is in both the deactivated GnuBook project and currently active BookReader I get the "Lost Something?" page when it would be better to see the bug in the BookReader project.

For example, if I get the list of bugs in a BookReader milestone on this page:
https://edge.launchpad.net/bookreader/+milestone/r26

The url for bug #428131 on that page doesn't include the project. Here's the URL as listed on the milestone page:
https://bugs.edge.launchpad.net/bugs/428131

When I click the bug URL I get redirected to this page:
https://bugs.edge.launchpad.net/gnubook-deactivated/+bug/428131

This is the page I think I should reach, since I was coming from a BookReader milestone page:
https://bugs.edge.launchpad.net/bookreader/+bug/428131

If you included the project in the URLs for the bugs on the milestone page it would solve the problem.

That's below average :( This is because of bug 364810 where deactivated bugtargets re returned. The is a bug in the UI and API

Okay I think the right short term solution for the BookReader is to fix our old bugs ;)