[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #3197 [Tor bundles/installation]: m:/tor-mingw/tbb-erinn.git/build-scripts/build-stable-windows/built/share\tor\fallback-consensus (was: m:/tor-mingw/tbb-erinn.git/build-scripts/build-stable-windows/built/share\tor\fallback-consensus": Permission denied)
#3197: m:/tor-mingw/tbb-erinn.git/build-scripts/build-stable-
windows/built/share\tor\fallback-consensus
--------------------------------------+-------------------------------------
Reporter: arma | Owner: erinn
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor bundles/installation | Version:
Keywords: | Parent:
Points: | Actualpoints:
--------------------------------------+-------------------------------------
Description changed by arma:
Old description:
> A user sent us logs of his failed (for some other reason I think)
> bootstrap. He's using Tor 0.2.1.30 -- I'm not sure which bundle.
>
> But the above line was part of his logs. It looks like the bundle had
> some of Erinn's paths still in it.
>
> What steps can we take in our build process (ideally automated) to reduce
> the chance that this recurs?
New description:
A user sent us logs of his failed (for some other reason I think)
bootstrap. He's using Tor 0.2.1.30 -- I'm not sure which bundle.
But this line was part of his logs:
{{{
May 16 22:17:14.078 [Warning] Could not open
"m:/tor-mingw/tbb-erinn.git/build-scripts/build-stable-
windows/built/share\tor\fallback-consensus": Permission denied
}}}
It looks like the bundle had some of Erinn's paths still in it.
What steps can we take in our build process (ideally automated) to reduce
the chance that this recurs?
--
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3197#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs