Changes between Version 1 and Version 2 of Ticket #48175, comment 2
- Timestamp:
- Jun 27, 2015, 11:49:21 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #48175, comment 2
v1 v2 1 1 Replying to [comment:1 larryv@…]: 2 2 3 Got it, thanks. At the first three locations it's looking for the ppc binary, which will always fail (expected behavior).3 Got it, thanks. At the first three locations it's looking for the ppc binary, which will always fail (expected). 4 4 5 Then it searches for the source in 14 different locations. As far as I can see, the only location of the 14 that has the tor-0.2.6.8 (or above) source archives is torproject itself, which is the one location the certificate issue occurs with (the rest are plain http). The source hasn't propagated out to the other locations as yet for some reason.5 Then it searches for the source in 14 different locations. As far as I can see, the only location of the 14 that has the tor-0.2.6.8 (or above) source archives is torproject itself, which is the one location the certificate issue occurs with (the rest are plain http). The source hasn't propagated out to the other locations as yet, which is why the fetch fails for those. 6 6 7 7 I can manually fetch the source from torproject and make it work from there as a workaround, while I'm looking into the cert issue with torproject when running the port command.