So, let me get this right: Tor is in both hardy- and intrepid-proposed, but has been removed from the jaunty repositories? Following the previous comments is confusing; why is it like this again?
If its a maintainer issue, why is it in *-proposed? If its a potential upgrade issue, why was it removed from an at-the-time unreleased release instead of being moved to jaunty-{backports,proposed}? If its a security issue, why is Debian using the same version as the removed package?
I was using the latest version in jaunty just fine until I installed the jaunty release from scratch and discovered it had been removed. Now I'm left attempting to verify trust chains to get a properly signed version, or mixing an old *-backports repository into my package database.
At least throw it into jaunty-backports as an unsupported package next time? I mean, its being supported by Debian, isn't that enough to at least get unsupported status?
@Martin Pitt
So, let me get this right: Tor is in both hardy- and intrepid-proposed, but has been removed from the jaunty repositories? Following the previous comments is confusing; why is it like this again?
If its a maintainer issue, why is it in *-proposed? If its a potential upgrade issue, why was it removed from an at-the-time unreleased release instead of being moved to jaunty- {backports, proposed} ? If its a security issue, why is Debian using the same version as the removed package?
I was using the latest version in jaunty just fine until I installed the jaunty release from scratch and discovered it had been removed. Now I'm left attempting to verify trust chains to get a properly signed version, or mixing an old *-backports repository into my package database.
At least throw it into jaunty-backports as an unsupported package next time? I mean, its being supported by Debian, isn't that enough to at least get unsupported status?