[Bug 328442] Re: Tor 0.1.2.x abandoned by upstream

Martin Pitt martin.pitt at ubuntu.com
Thu Feb 12 10:55:00 UTC 2009


I still remember the thread, and back then we concluded that we can
pursue the path of updating stables to new upstream versions if we get
enough testing *and* the upgrade does not break existing user
configuration.  I subscribed motu-sru for their feedback as well, since
the package is in universe.

Are there any configuration settings in 0.1.x. which are not handled any
more by 0.2? If so, what happens for those?

Should we put the current intrepid package (2.0.31) into hardy-proposed?
In other words, is 2.0.31 "good enough" for now? This would be slightly
safer, since the intrepid version already got testing. We could then
update all stable releases to a newer 0.2.x later, in a separate SRU.

Or rather update jaunty and intrepid-proposed to the latest upstream
microrelease first (which should become a separate SRU bug, see above),
test it, get it into intrepid-updates, and then backport this to hardy?

Thanks for any insight, Roger!

** Changed in: tor (Ubuntu Hardy)
       Status: New => Triaged

-- 
Tor 0.1.2.x abandoned by upstream
https://bugs.launchpad.net/bugs/328442
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs




More information about the universe-bugs mailing list