missing tmp folder causes "unable to create pristine stream"
767 views
Skip to first unread message
Michael Cole
Apr 13, 2020, 9:03:20 PM4/13/20
to TortoiseSVN
Hi, I just ran into this bug: https://stackoverflow.com/questions/35962861/how-to-fix-unable-to-create-pristine-install-stream
The short version is in the latest version I downloaded 3 days ago, there is a bug where a commit is looking for a tmp folder in the repo's .svn folder, but it's missing so the error happens. Creating the tmp folder fixes it.
Stefan
Apr 14, 2020, 1:44:38 AM4/14/20
to TortoiseSVN
you should report that on the subversion users list:
Michael Cole
Apr 14, 2020, 9:31:31 AM4/14/20
to TortoiseSVN on behalf of Stefan
It's a problem with the TortoiseSVN client Stefan, but you're welcome to report it there if you like.
On Tue, Apr 14, 2020 at 12:44 AM Stefan via TortoiseSVN <torto...@googlegroups.com> wrote:
you should report that on the subversion users list:
--
You received this message because you are subscribed to the Google Groups "TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/93823bbc-dae3-4989-9f48-5340bde95723%40googlegroups.com.
Michael Cole
Johan Corveleyn
Apr 14, 2020, 6:35:39 PM4/14/20
to TortoiseSVN on behalf of Michael Cole
Just chiming in here, but you are both right :-).
Yes, it's a problem people are experiencing with the TortoiseSVN
client. But it's (most likely) not specific to the TortoiseSVN client
(which is a GUI on top of the core Subversion libraries, which are
maintained by the Apache Subversion project). It's probably an issue
for the core subversion project. If you try similar operations from
the commandline (with svn.exe), you'll probably get the same error.
That's why Stefan tried to direct you to the subversion users
mailinglist.
@Michael, thanks for reporting this. It sounds to me more like a
feature request: being able to recover from a specific corruption of
the .svn folder (namely that the tmp folder has gone missing, IMHO
most likely caused by some external factor). Nothing is supposed to
mess with the insides of the .svn folder :-). So this comes out as
quite a "low level" error, because it's not something that was
foreseen by the developers.
That being said, on first sight it does look like something that
should be fixable / improvable (if someone finds the time to dig into
it). I guess it's also very easy to reproduce (just delete .svn/tmp
and try to commit something).
Michael, if my above reasoning is correct, would you like to report
this to us...@subversion.apache.org yourself (it's not necessary to
subscribe to post)? If not, no problem, then I'll take it there
(Stefan has enough on his hands already :-)).
--
Johan
> To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/CA%2BHiUNLGCYNoVnUJ3Juwnc_tsAxh4eVCxfSRdLa_qdGR-J__jQ%40mail.gmail.com.
Yes, it's a problem people are experiencing with the TortoiseSVN
client. But it's (most likely) not specific to the TortoiseSVN client
(which is a GUI on top of the core Subversion libraries, which are
maintained by the Apache Subversion project). It's probably an issue
for the core subversion project. If you try similar operations from
the commandline (with svn.exe), you'll probably get the same error.
That's why Stefan tried to direct you to the subversion users
mailinglist.
@Michael, thanks for reporting this. It sounds to me more like a
feature request: being able to recover from a specific corruption of
the .svn folder (namely that the tmp folder has gone missing, IMHO
most likely caused by some external factor). Nothing is supposed to
mess with the insides of the .svn folder :-). So this comes out as
quite a "low level" error, because it's not something that was
foreseen by the developers.
That being said, on first sight it does look like something that
should be fixable / improvable (if someone finds the time to dig into
it). I guess it's also very easy to reproduce (just delete .svn/tmp
and try to commit something).
Michael, if my above reasoning is correct, would you like to report
this to us...@subversion.apache.org yourself (it's not necessary to
subscribe to post)? If not, no problem, then I'll take it there
(Stefan has enough on his hands already :-)).
--
Johan
Johan Corveleyn
Jan 13, 2021, 11:24:13 AM1/13/21
to TortoiseSVN on behalf of Michael Cole
Sorry, apparently I dropped the ball on this one. I completely forgot
to pursue this further, in spite of what I said below.
In the meantime, an issue was created in the SVN issue tracker for
this, by Daniel Camarena:
https://issues.apache.org/jira/browse/SVN-4868
So, thanks to Daniel :-).
(to be clear, that doesn't make the issue "fixed" of course, it just
means it's now in the SVN issue tracker so perhaps this gets picked up
one day by one of the volunteers or by a new contributor ...)
--
Johan
to pursue this further, in spite of what I said below.
In the meantime, an issue was created in the SVN issue tracker for
this, by Daniel Camarena:
https://issues.apache.org/jira/browse/SVN-4868
So, thanks to Daniel :-).
(to be clear, that doesn't make the issue "fixed" of course, it just
means it's now in the SVN issue tracker so perhaps this gets picked up
one day by one of the volunteers or by a new contributor ...)
--
Johan
Reply all
Reply to author
Forward
0 new messages