On Fri, 12 Apr 2019 21:13:42 +0200, Bo Berglund
wrote:
>Surprise!
>Only a single file was retrieved and this was a common file used by
>both the original project and the Linux project.
>No sign of the Linux project files at all!
>
>Aren't files added on a workstation and committed there supposed
Hi,
Is SlikSVN still being maintained? The latest compiled build available on
the website is 1.9.7 (current version is 1.11.x, with 1.12.x on the way).
If it's no longer being maintained, it would be good to remove it from the
list of valid binaries:
I have a Freepascal project I develop on both Windows and Linux.
I started in Windows and when I wanted to make a version for Linux I
checked out the Windows project to Linux.
Then I worked on the files over there.
The specific project files for linux were added in Linux and committed
to svn.
Guten Tag Stefan Sperling,
am Freitag, 12. April 2019 um 11:45 schrieben Sie:
> Install a package with debug symbols, enable core dumps, and get
> a backtrace with gdb from a core dump.
Does the following help? I've attched some more verbose chrashlog
but without the actual dump, as that is some
On Fri, Apr 12, 2019 at 11:42:54AM +0200, Thorsten Schöning wrote:
> Does the error tell anyone of you anything already?
No.
> What should I do
> to get some hints about which repo is affected with which operation?
Install a package with debug symbols, enable core dumps, and get
a backtrace
Hi all,
today I recognized a segfault in svnserver which seems to have been
documented for UB 16.04 LTS already:
> Apr 12 09:58:55 [...] kernel: [214930.125762] svnserve[556]: segfault at
> 7f5f75994f00 ip 7f5f74ea1065 sp 7ffddc1353f0 error 4 in
>
