Ubuntu
tor package

not able to upgrade tor (6.10 to 7.04)

Bug #107770 reported by B. van Laer on 2007-04-19

Affects		Status	Importance	Assigned to	Milestone
	tor (Ubuntu)	Invalid	Undecided	Unassigned
	update-manager (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: tor

After reboot, the update manager wants to upgrade nfs and tor. Tor fails to upgrade.

ProblemType: Package
Date: Thu Apr 19 20:49:51 2007
ErrorMessage:
ErrorMessage: subprocess new pre-removal script returned error exit status 1
Package: tor
SourcePackage: tor

Revision history for this message

Sebastian K (staats-mail-junk) wrote on 2007-04-22:

i have the same problem

Revision history for this message

Richard Birnie (rbirnie-deactivatedaccount) wrote on 2007-05-07:

setting status to confirmed since two users report the same issue.

bla, Sebastian K - If either of you still have them could you attach the log files from the upgrade. These will be in /var/log/dist-upgrade

Changed in update-manager:
status:	Unconfirmed → Confirmed

jyb (jeanyves-bossard) on 2007-05-12

Changed in tor:
status:	Unconfirmed → Confirmed

Revision history for this message

B. van Laer (bla-dds) wrote on 2007-06-04:

Dist-upgrade logs Edit (18.0 KiB, application/octet-stream)

Shure.... here is my dist-upgrade folder.

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2008-11-09:

closing update-manager task.

Changed in update-manager:
status:	Confirmed → Invalid

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2008-11-09:

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently and this is likely a dup of bug 130327 .
We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in tor:
status:	Confirmed → Incomplete

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2008-11-22:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!