I've added a bug here:
https://bugs.edge.launchpad.net/ubuntu/+bug/413657
As a user, tor is necessary for daily use anyway.
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://bugs.launchpad.net/bugs/328442
You received this bug notification because you are a member of Ubuntu
Bugs, w
@Ralph: you can get packages for 9.04 here:
https://wiki.torproject.org/noreply/TheOnionRouter/TorOnDebian
As for the question about getting tor back in the current and future
releases of Ubuntu: having tor in ubuntu requires a maintainer that is
willing to keep the packages updated (this includes
Whilst I understand the reasons stated above for tor having been dropped
from 9.04, it came as a surprise to upgrade from 8.10 to find it
missing! I didn't spot anything about lack of tor in the 9.04 release
notes either. That leaves me with a machine that was mainly for running
tor without a lot
This bug was fixed in the package tor - 0.2.0.34-1~intrepid+1
---
tor (0.2.0.34-1~intrepid+1) intrepid-proposed; urgency=low
* Build 0.2.0.34 for intrepid. (LP: #328442)
* Conflict with libssl0.9.8 (<< 0.9.8g-4ubuntu3.1) on intrepid
-- Runa SandvikMon, 09 Feb 2009 10:09:54
+
This bug was fixed in the package tor - 0.2.0.34-1~hardy+1
---
tor (0.2.0.34-1~hardy+1) hardy-proposed; urgency=low
* Build 0.2.0.34 for hardy. (LP: #328442)
* Conflict with libssl0.9.8 (<< 0.9.8g-4ubuntu3.1) on hardy
-- Runa SandvikMon, 09 Feb 2009 10:09:54
+0100
** Change
Runa, thank you for your efforts!
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
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@lists.ubuntu.com
h
This was originally titled differently. I change the jaunty task to
"invalid" to be less confusing.
** Changed in: tor (Ubuntu Jaunty)
Status: Fix Released => Invalid
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://bugs.launchpad.net/bugs/328442
You received this bug noti
@Nizar: like Martin Pitt wrote earlier in this bug report - tor has been
removed from jaunty.
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://bugs.launchpad.net/bugs/328442
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Runa : ok, but as i see in the top of this page, this bug is also
nominated for jaunty :)
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://bugs.launchpad.net/bugs/328442
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Tags added: verification-done
** Tags removed: verification-needed
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
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
@Martin: I didn't change anything. There is a config file in both the
hardy-version and in the new version (this goes for the version in
intrepid as well).
@Nizar: Thanks for testing, but tor isn't going into jaunty at this
point.
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://
i tested with success, tor (v0.2.0.34) deb package available in the
torproject website on jaunty 64 bits.
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://bugs.launchpad.net/bugs/328442
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks for testing, it seems you covered both hardy and intrepid now.
The conffile dpkg question in hardy is unfortunate. It seems that
/etc/tor/torrc wasn't a conffile in original hardy's version, but is now
in the new version? Or did you actually change it manually?
--
Tor 0.1.2.x abandoned by
I have tested tor on hardy (using hardy-proposed) and everything works
just fine.
Preparing to replace tor 0.1.2.19-2 (using .../tor_0.2.0.34-1~hardy+1_i386.deb)
...
Stopping tor daemon: ..tor.
Unpacking replacement tor ...
Selecting previously deselected package tor-g
Right, sorry. It was stuck in the NEW queue because of the newly built
package "tor-geoipdb". I processed it now, will be available on
archive.u.c. in about an hour.
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://bugs.launchpad.net/bugs/328442
You received this bug notification
I can't find tor in hardy-proposed and I thought the conflict was the
reason.
'rmadison tor' shows:
tor | 0.2.0.34-1~hardy+1 | hardy-proposed/universe | source, amd64
Also, the page for the i386-build[1] says that a few binaries are still
awaiting acceptance.
[1]:
https://launchpad.net/ubuntu/+s
Runa,
I don't think this is necessary. You patched
-Conflicts: libssl0.9.8 (<< 0.9.8g-4ubuntu3.1)
+Conflicts: libssl0.9.8 (<< 0.9.8g-4ubuntu3)
But hardy has
libssl0.9.8 | 0.9.8g-4ubuntu3 | hardy | amd64, i386
libssl0.9.8 | 0.9.8g-4ubuntu3.5 | hardy-security | amd64, i386
libssl0.9.8 | 0
I've built a new hardy-backport (and set the conflict to an older
version of libssl); http://folk.ntnu.no/runasand/tor/hardy/fixed/
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://bugs.launchpad.net/bugs/328442
You received this bug notification because you are a member of Ubuntu
i waited a long time for vidalia to be packaged on ubuntu, and when we got it,
tor is removed :)
vidalia, use is using tor, so having vidalia without tor is useless
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://bugs.launchpad.net/bugs/328442
You received this bug notification
tor being removed is quite annoying. I'll try using the packages from
the tor project.
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://bugs.launchpad.net/bugs/328442
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Eric B. [2009-04-28 7:15 -]:
> So, let me get this right: Tor is in both hardy- and intrepid-proposed,
> but has been removed from the jaunty repositories?
Correct.
> Following the previous comments is confusing; why is it like this
again?
Because nobody stepped up in time in Jaunty to comm
@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, wh
I have tested tor on intrepid (using intrepid-proposed) and everything
works just fine.
Preparing to replace tor 0.2.0.31-1 (using
.../tor_0.2.0.34-1~intrepid+1_i386.deb) ...
Stopping tor daemon: ..tor.
Unpacking replacement tor ...
Processing triggers for man-db ...
S
Accepted into hardy-proposed; please test and give feedback here. Please
see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you in advance!
** Changed in: tor (Ubuntu Hardy)
Status: Triaged => Fix Committed
--
Tor 0.1.2.x abandoned
Accepted into intrepid-proposed; please test and give feedback here.
Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
** Changed in: tor (Ubuntu Intrepid)
Status: Confirmed => Fix Committed
** Tags added: ver
Hi Guys, probably I am getting it wrong, cause english is not my mother
tongue, but what I am reading here is that you are discussing to remove
tor rather than just taking the new versions.
I am just a simple Ubuntu user, just like thousands of others out there.
I am using tor on daily base and if
@Martin: Thanks for letting the Ubuntu users know of that problem, so we
can remove tor from our system and us your debs instead... thats what
the ubuntu repos are for, right ;)
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://bugs.launchpad.net/bugs/328442
You received this bug n
"Fix Released" seems rather misleading.
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
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@lists.ubuntu
I have built, installed and tested 0.2.0.34 on both hardy and intrepid.
When testing I first installed tor directly from the repository,
configured and started it before I upgraded - to make sure that the
configuration continues to work. I also checked all bugs marked "fixed
released" to make sure
Thanks for the build logs, but those are the least of my concerns. We
need someone who actively uses tor, can test upgrades and
configuration compatiblity between 1.x and 2.x (hardy upgrade), test
for regressions, etc. This is a serious maintainer job, I'm afraid.
--
Tor 0.1.2.x abandoned by upst
Prevu-build log for hardy (I used tor_0.2.0.34-1ubuntu1.dsc) attached.
** Attachment added: "hardy-build.txt"
http://launchpadlibrarian.net/25615413/hardy-build.txt
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://bugs.launchpad.net/bugs/328442
You received this bug notificati
Prevu-build log for intrepid (I used tor_0.2.0.34-1ubuntu1.dsc)
attached.
** Attachment added: "intrepid-build.txt"
http://launchpadlibrarian.net/25615405/intrepid-build.txt
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://bugs.launchpad.net/bugs/328442
You received this bug n
I held back the removal since my "call for maintainership" on the ML got
two replies. But there hasn't been any action yet, so I removed tor from
jaunty now.
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://bugs.launchpad.net/bugs/328442
You received this bug notification because
Seems like I made a duplicate bug report when I filed #362447 requesting
backports:
https://bugs.launchpad.net/ubuntu/+source/tor/+bug/362447
Like I have previously written; there are no source changes needed.
Version 0.2.0.34 builds in clean intrepid- and hardy-pbuilder and runs
like a charm.
-
Ok. So the current status as I understand it is that Ubuntu would rather
ship known-vulnerable (and in the Intrepid case, known-remote-root-vulnerable!)
versions of Tor rather than use the Ubuntu debs that we provide.
Sounds like the correct solution is to a) take it out of Jaunty (as Martin said
I'm willing to take this on...
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
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@lists.ubuntu.com
http
Iain Lane [2009-03-09 15:39 -]:
> But it has been updated in Jaunty. "All" we need to do is push this
> version down through the releases, right?
Well, that "all" encompasses instaling the current hardy version,
configuring it, checking that it works, backporting the jaunty
package, installing
But it has been updated in Jaunty. "All" we need to do is push this
version down through the releases, right? It seems from reading this
report that this should be mostly transparent to our users, but we can
put a NEWS file in the releases if this would be more appropriate. This
seems much better t
I guess so. I mailed ubuntu-devel-discuss@ again, but if there will be
nobody stepping up, I'll remove it from jaunty.
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
https://bugs.launchpad.net/bugs/328442
You received this bug notification because you are a member of Ubuntu
Bugs, which
Ok.
Should we take Tor out of Jaunty, then?
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
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@lists.u
Roger,
the primary problem here that nobody "took" the bug, there is no
assignee. As discussed back then, we'd need someone who actually uses
the packge, maintains it, and can test it.
So please don't stall the advisory further, since it's not at all clear
when this will get fixed in Ubuntu stabl
I should mention that we've been holding back on the detailed security advisory
for bugs fixed in 0.2.0.33 and 0.2.0.34, until Ubuntu and the *BSDs have had
time
to upgrade.
I think the BSDs have upgraded now, so we're just waiting on Ubuntu. At some
point
we're going to have to release the advi
** Changed in: tor (Ubuntu Intrepid)
Status: New => Confirmed
--
Tor 0.1.2.x abandoned by upstream, update to 0.2.0.34
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
For whoever is working on the packages, there are hardy and
intrepid 0.2.0.34 debs available here:
https://wiki.torproject.org/noreply/TheOnionRouter/TorOnDebian
built by the Debian maintainer.
You may or may not find them useful. :)
** Summary changed:
- Tor 0.1.2.x abandoned by upstream, updat
44 matches
Mail list logo
