Login | Register
My pages Projects Community openCollabNet

Discussions > users > Re: error in update_work during / before update

fsvs
Discussion topic

Hide all messages in topic

All messages in topic

Re: error in update_work during / before update

Author pmarek
Full name P.Marek
Date 2006-08-31 00:16:32 PDT
Message On Wednesday 30 August 2006 22:05 Gunter Ohrner wrote:
> > Sorry - how about an ltrace too?
>
> HTH.
Hmmm ... it just dies inside the apr_pool_clear(). Nothing new.


> BTW, I'm using fsvs using an "svn://"-URL in contrast to alocal
> repository. Maybe that makes a difference? (It once did, if you
> remember.)
With a svn+ssh:// it crashes for me too.
Now I have to look why.


Regards,

Phil


--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: error in update_work during / before update

Author Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Full name Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Date 2006-08-30 13:05:17 PDT
Message Am Mittwoch, 30. August 2006 17:35 schrieb Philipp Marek:
> > > Could you provide me with the last lines of "strace -tt -f fsvs
> > > up"?
> Sorry - how about an ltrace too?

HTH.

BTW, I'm using fsvs using an "svn://"-URL in contrast to alocal
repository. Maybe that makes a difference? (It once did, if you
remember.)

Greetings,

  Gunter

close(6 <unfinished ...>
SYS_close(6) = 0
<... close resumed> ) = 0
rename("/var/spool/f​svs/d5/7f/cb86b58bcc​"..., "/var/spool/fsvs/d5/​7f/cb86b58bcc"...
<unfinished ...>
SYS_rename(0x805f008, 0x8907d38, 0, 0x8907d38, 0) = 0
<... rename resumed> ) = 0
apr_md5_final(0x805de74, 0x805de18, 0x4fd53d2c, 0x88c4840, 0xbfb8602c) = 0
svn_stream_close(0x88c6d68, 0x805de74, 0x805de18, 0x4fd53d2c, 0x88c4840) =
0
SYS_close(5) = 0
SYS_close(4) = 0
sprintf("d3e1af81a64​9863a4ea632fbf9b638e​3", "%02x%02x%02x%02x%02​x%02x%02x%02x"...,
0xd3, 0xe1, 0xaf, 0x81, 0xa6, 0x49, 0x86, 0x3a) = 32
apr_pool_clear(0x88c6c18, 0x410db744, 0, 0xbfb860fc, 0x410d52aa
<unfinished ...>
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

--
*** Powered by AudioScrobbler --> http://www.last.fm/u​ser/Interneci/ ***
21:58 | Epica - Force of the Shore
21:54 | Epica - Blank Infinity
21:49 | Epica - Solitary Ground
21:45 | Epica - The last crusade (A New Age Dawns - Part I)
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
Attachments

Re: error in update_work during / before update

Author pmarek
Full name P.Marek
Date 2006-08-30 08:35:25 PDT
Message On Wednesday 30 August 2006 17:00 Gunter Ohrner wrote:
> Am Mittwoch, 30. August 2006 12:57 schrieb Philipp Marek:
> > Could you provide me with the last lines of "strace -tt -f fsvs up"?
Sorry - how about an ltrace too?

Thank you!


Phil

--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: error in update_work during / before update

Author pmarek
Full name P.Marek
Date 2006-08-30 08:34:17 PDT
Message On Wednesday 30 August 2006 17:00 Gunter Ohrner wrote:
> Am Mittwoch, 30. August 2006 12:57 schrieb Philipp Marek:
> > Could you provide me with the last lines of "strace -tt -f fsvs up"?
>
> 16:52:23.886257 open("./.kde/share/a​pps/kwallet/kdewalle​t_cc.kwl.up.tmp",
> O_WRONLY|O_CREAT|O_TRUNC, 0600) = 5
...
> 16:52:38.367358 close(5) = 0
> 16:52:38.367853 close(4) = 0
> 16:52:38.368403 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> 16:52:39.057179 +++ killed by SIGSEGV (core dumped) +++
> Process 19133 detached
Hmmmm ... the files get closed, then the SEGV happens while still in
apr_pool_clear().

I updated to 2.0.55-4.1, committed parts of my home (including kwallet), and
checked them out in /tmp, but I got no error.

I'll look further.


Regards,

Phil

--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: error in update_work during / before update

Author Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Full name Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Date 2006-08-30 08:00:19 PDT
Message Am Mittwoch, 30. August 2006 12:57 schrieb Philipp Marek:
> Could you provide me with the last lines of "strace -tt -f fsvs up"?

16:52:23.886257 open("./.kde/share/a​pps/kwallet/kdewalle​t_cc.kwl.up.tmp",
O_WRONLY|O_CREAT|O_TRUNC, 0600) = 5
16:52:23.965107 brk(0x88f1000) = 0x88f1000
16:52:23.967581
read(3, "XXXXXXXXXXXXXXXXXXX​XXXXXXXXXXXXXXXXXXXX​XXXXXXXXXXX"..., 4096) =
4096
16:52:25.133370
read(3, "XXXXXXXXXXXXXXXXXXX​XXXXXXXXXXXXXXXXXXXX​XXXXXXXXXXX"..., 4096) =
4096
16:52:33.363167
read(3, "XXXXXXXXXXXXXXXXXXX​XXXXXXXXXXXXXXXXXXXX​XXXXXXXXXXX"..., 4096) =
4096
16:52:33.363935
read(3, "XXXXXXXXXXXXXXXXXXX​XXXXXXXXXXXXXXXXXXXX​XXXXXXXXXXX"..., 4096) =
4096
16:52:33.364486
read(3, "XXXXXXXXXXXXXXXXXXX​XXXXXXXXXXXXXXXXXXXX​XXXXXXXXXXX"..., 4096) =
4096
16:52:33.365118
read(3, "XXXXXXXXXXXXXXXXXXX​XXXXXXXXXXXXXXXXXXXX​XXXXXXXXXXX"..., 4096) =
4096
16:52:33.365665
read(3, "XXXXXXXXXXXXXXXXXXX​XXXXXXXXXXXXXXXXXXXX​XXXXXXXXXXX"..., 4096) =
4096
16:52:33.366201
read(3, "XXXXXXXXXXXXXXXXXXX​XXXXXXXXXXXXXXXXXXXX​XXXXXXXXXXX"..., 4096) =
2381
16:52:33.366771 read(3, " ) ) ( textdelta-end ( 2:c5 ) ) "..., 4096) =
4096
16:52:38.305676 brk(0x8914000) = 0x8914000
16:52:38.311493
write(5, "KWALLET\n\r\0\r​\n\0\0\0\0\0\​0\0XXXXXXXXXXXXXXXX​XX"..., 50504) =
50504
16:52:38.318308 getcwd("/home/gunter", 4096) = 13
16:52:38.318838 mkdir("/var/spool/fsvs/d5", 0777) = -1 EEXIST (File
exists)
16:52:38.319354 mkdir("/var/spool/fsvs/d5/7f", 0777) = -1 EEXIST (File
exists)
16:52:38.319909
mkdir("/var/spool/fs​vs/d5/7f/cb86b58bcc1​58ac0ab2d92fd80ae", 0777) = -1
EEXIST (File exists)
16:52:38.320420
open("/var/spool/fsv​s/d5/7f/cb86b58bcc15​8ac0ab2d92fd80ae/md5​s.tmp",
O_WRONLY|O_CREAT|O_T​RUNC|O_LARGEFILE, 0700) = 6
16:52:38.337625 write(6, "5e991ec0d6c5c31c6d7​61c370ad0aabf"..., 64) = 64
16:52:38.342614 close(6) = 0
16:52:38.343452
rename("/var/spool/f​svs/d5/7f/cb86b58bcc​158ac0ab2d92fd80ae/m​d5s.tmp", "/var/spool/fsvs
/d5/7f/cb86b58bcc158​ac0ab2d92fd80ae/md5s​") = 0
16:52:38.367358 close(5) = 0
16:52:38.367853 close(4) = 0
16:52:38.368403 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
16:52:39.057179 +++ killed by SIGSEGV (core dumped) +++
Process 19133 detached

--
*** Powered by AudioScrobbler --> http://www.last.fm/u​ser/Interneci/ ***
00:46 | Nightwish - Nemo
00:42 | Nightwish - Kuolema tekee taiteilijan
00:37 | Nightwish - Slaying the Dreamer
00:32 | Nightwish - Wishmaster
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
Attachments

Re: error in update_work during / before update

Author pmarek
Full name P.Marek
Date 2006-08-30 03:57:43 PDT
Message On Tuesday 29 August 2006 20:53 Gunter Ohrner wrote:
> Am Dienstag, 29. August 2006 10:21 schrieben Sie:
> > I cannot find anything wrong in this pool handling.
> >
> > Which version of apr are you using? I find bug reports about
> > apr_pool_clear() in google.
>
> ii libapr0 2.0.55-4.1
> ii libapr0-dev 2.0.55-4.1
Could you provide me with the last lines of "strace -tt -f fsvs up"?


--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: error in update_work during / before update

Author Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Full name Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Date 2006-08-29 11:53:01 PDT
Message Am Dienstag, 29. August 2006 10:21 schrieben Sie:
> I cannot find anything wrong in this pool handling.

> Which version of apr are you using? I find bug reports about
> apr_pool_clear() in google.
ii libapr0 2.0.55-4.1
ii libapr0-dev 2.0.55-4.1

Greetings,

  Gunter

--
+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+
Be nice to your enemies, it drives them nuts.
+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+
+ PGP-verschlüsselte Mails bevorzugt! +
+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+
Attachments

Re: error in update_work during / before update

Author pmarek
Full name P.Marek
Date 2006-08-29 01:21:57 PDT
Message On Monday 28 August 2006 01:11 Gunter Ohrner wrote:
> > Wait a minute ... what did happen?
>
> Good question - I guess I know and it was my fault and not fsvs': I think
> the file changed after the sync-repos while the Repository also had an
> update available.
>
> However, maybe the error message should elaborate about that a bit.
I'm currently (in the background) rewriting fsvs to handle multiple urls.
There the conflict scenario will (have to be) handled.

> > What should fsvs do? Get the file to a temporary name, take it if it's
> > identical (MD5 available after transfer), and leave it with something
> > like .fsvs-conflict if it's not?
> That sounds like a viable solution.
>
> Ok, I moved the files in question away, but this made fsvs crash which I
> guess was not what should have happened... ;)
>
> Backtrace (extracted from core file, unfortunately without full debugging
> symbols in the libraries depended upon):
>
> *****************
> (gdb) bt
> #0 0x4b880768 in apr_pool_clear () from /usr/lib/libapr-0.so.0
> #1 0x08053d67 in up__close_file ()
I cannot find anything wrong in this pool handling.

Which version of apr are you using? I find bug reports about apr_pool_clear()
in google.


Thank you for your help (and patience)!


Regards,

Phil

--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: error in update_work during / before update

Author Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Full name Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Date 2006-08-27 16:11:52 PDT
Message Am Sonntag, 27. August 2006 09:54 schrieb Philipp Marek:
> > An error occurred at 03:27:42.983: Die Datei existiert bereits (17)
> You've strange times for working :-)

Not really, I used to until rather recently, but adjusted my working cycle
to match the sun's... ;)

This (and today) was just an exception, as I had a rather busy weekend and
wanted to give you feedback in any case.

> Wait a minute ... what did happen?

Good question - I guess I know and it was my fault and not fsvs': I think
the file changed after the sync-repos while the Repository also had an
update available.

However, maybe the error message should elaborate about that a bit.

> What should fsvs do? Get the file to a temporary name, take it if it's
> identical (MD5 available after transfer), and leave it with something
> like .fsvs-conflict if it's not?

That sounds like a viable solution.

Ok, I moved the files in question away, but this made fsvs crash which I
guess was not what should have happened... ;)

Backtrace (extracted from core file, unfortunately without full debugging
symbols in the libraries depended upon):

*****************
(gdb) bt
#0 0x4b880768 in apr_pool_clear () from /usr/lib/libapr-0.so.0
#1 0x08053d67 in up__close_file ()
#2 0x4bee52aa in svn_ra_svn__drive_editorp ()
from /usr/lib/libsvn_ra_svn-1.so.0
#3 0x4bee4d64 in svn_ra_svn__drive_editorp ()
from /usr/lib/libsvn_ra_svn-1.so.0
#4 0x4bee2f87 in svn_ra_svn_drive_editor ()
from /usr/lib/libsvn_ra_svn-1.so.0
#5 0x4bee1358 in ?? () from /usr/lib/libsvn_ra_svn-1.so.0
#6 0x08067990 in ?? ()
#7 0x08065988 in ?? ()
#8 0x0805b400 in __PRETTY_FUNCTION__.7869 ()
#9 0xbf84725c in ?? ()
#10 0x00000000 in ?? ()
*****************

Last lines in the "-d -v"-log just before the crash:

*****************
00:57:28.796 ops__build_path[est_ops.c:561] status=0;
path=./.kde/share/ap​ps/kwallet/kdewallet​_cc.kwl
00:57:28.796 up__apply_textdelta[​update.c:767] target
is ./.kde/share/apps/kw​allet/kdewallet_cc.k​wl,
00:57:28.796 up__apply_textdelta[​update.c:768] temp
is ./.kde/share/apps/kw​allet/kdewallet_cc.k​wl.up
.tmp
00:57:28.815 cs___end_of_block[ch​ecksum.c:417] manber reinit
00:57:28.815 ops__build_path[est_ops.c:515] need 1024 bytes
00:57:28.815 ops__build_path[est_ops.c:523] reusing 11
00:57:28.815 ops__build_path[est_ops.c:561] status=0;
path=./.kde/share/ap​ps/kwallet/kdewallet​_cc.kwl
00:57:28.815 cs__new_manber_filte​r[checksum.c:651] initiating MD5
streaming for ./.kde/share/apps/kwal
let/kdewallet_cc.kwl
00:57:33.307 cs___end_of_block[ch​ecksum.c:476] manber found a border:
23397 41A73191 FE740000 5e991ec0
d6c5c31c6d761c370ad0aabf
00:57:33.308 cs___end_of_block[ch​ecksum.c:488] on return: FE740000
00:57:33.308 cs___update_manber[c​hecksum.c:541] block ends after 23397;
size 23397 bytes (border=23397
).
00:57:33.308 ops__build_path[est_ops.c:475] 0xb7131ac8 found in cache
index 11; lru 11
00:57:33.308 ops__build_path[est_ops.c:561] status=0;
path=./.kde/share/ap​ps/kwallet/kdewallet​_cc.kwl
00:57:33.308 waa__open[waa.c:306] tmp for
target /var/spool/fsvs/d5/7​f/cb86b58bcc158ac0ab​2d92fd80ae/md
5s is /var/spool/fsvs/d5/7​f/cb86b58bcc158ac0ab​2d92fd80ae/md5s.tmp
00:57:33.308 waa__open[waa.c:322] got fh 6
00:57:33.308 waa__open[waa.c:334] reallocate target name array to 8
00:57:33.308 cs___update_manber[c​hecksum.c:559] now doing manber-hashing
for ./.kde/share/apps/kwallet
/kdewallet_cc.kwl...
00:57:33.308 cs___end_of_block[ch​ecksum.c:417] manber reinit
00:57:33.310 cs___end_of_block[ch​ecksum.c:488] on return: D7DA0E7D
00:57:33.310 cs___update_manber[c​hecksum.c:532] block continues after
50504.
00:57:33.310 waa__close[waa.c:377] filehandle 6 should
be /var/spool/fsvs/d5/7​f/cb86b58bcc158ac0ab​2d92
fd80ae/md5s
00:57:33.311 up__close_file[update.c:883] close file:
md5=d3e1af81a649863a​4ea632fbf9b638e3
*****************

Greetings,

  Gunter

--
*** Powered by AudioScrobbler --> http://www.last.fm/u​ser/Interneci/ ***
20:09 | Nemesea - Outro
20:06 | Nemesea - Cry
20:02 | Nemesea - Beyond Evil
19:58 | Nemesea - Disclosure
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
Attachments

Re: error in update_work during / before update

Author pmarek
Full name P.Marek
Date 2006-08-27 00:54:56 PDT
Message On Sunday 27 August 2006 03:30 Gunter Ohrner wrote:
> Mh, I'm not sure if you really want to hear the results... ;)
>
> At least the error message changed:
...
> 03:27:42.982 up__add_entry[update.c:387] add
entry .kde/share/apps/kwal​let/kdewallet_zb.kwl​
> 03:27:42.982 ops__find_entry_byna​me[est_ops.c:620] found kdewallet_zb.kwl on
0x826c878; ignored: 0x2
>
> An error occurred at 03:27:42.983: Die Datei existiert bereits (17)
> in up__add_entry [update.c:403]:
> file .kde/share/apps/kwal​let/kdewallet_zb.kwl​ already exists
> in up__add_file [update.c:685]
> in update_work [update.c:1104]: reporter->finish_report: up__add_file
> in update_work [update.c:1114]: up__add_file
> in main [fsvs.c:524]: action update failed
You've strange times for working :-)

Could you try another sync-repos before update, please?

But that probably wouldn't help ... There's some kind of conflict here - A
file should be added, but it already exists locally.

What should fsvs do? Get the file to a temporary name, take it if it's
identical (MD5 available after transfer), and leave it with something
like .fsvs-conflict if it's not?


Wait a minute ... what did happen?
You put that file on machine A into the repository, overwrote it on B (after
sync and commit) with a newer version ... why should fsvs think that it's
new? Because the "last" revision this working copy is at is wrong.
Could you do a "fsvs info" in your home? To see what revision you wc root is
at?

Thank you.


Regards,

Phil


--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: error in update_work during / before update

Author Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Full name Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Date 2006-08-26 18:30:24 PDT
Message Am Freitag, 25. August 2006 19:16 schrieben Sie:
> I think I found that bug. Nasty, nasty ...
> Thank you for reporting!
> Please try current trunk.

Mh, I'm not sure if you really want to hear the results... ;)

At least the error message changed:

03:27:42.978 up__parse_prop[update.c:81] got property for .:
svn:entry:committed-rev=93
03:27:42.979 up__parse_prop[update.c:81] got property for .:
svn:entry:committed-​date=2006-08-10T22:2​6:50.684494Z
03:27:42.979 up__parse_prop[update.c:81] got property for .:
svn:entry:last-author=gunter
03:27:42.979 up__parse_prop[update.c:81] got property for .:
svn:entry:uuid=de9c9​2fe-7908-0410-9c59-e​1f573f8e05f
03:27:42.979 ops__find_entry_byna​me[est_ops.c:620] found .kde on
0x88a41a4; ignored: 0x1
03:27:42.979 up__parse_prop[update.c:81] got property for .kde:
svn:entry:committed-rev=93
03:27:42.979 up__parse_prop[update.c:81] got property for .kde:
svn:entry:committed-​date=2006-08-10T22:2​6:50.684494Z
03:27:42.979 up__parse_prop[update.c:81] got property for .kde:
svn:entry:last-author=gunter
03:27:42.979 up__parse_prop[update.c:81] got property for .kde:
svn:entry:uuid=de9c9​2fe-7908-0410-9c59-e​1f573f8e05f
03:27:42.979 ops__find_entry_byna​me[est_ops.c:620] found .kde/share on
0x8097798; ignored: 0x1
03:27:42.979 up__parse_prop[update.c:81] got property for share:
svn:entry:committed-rev=93
03:27:42.981 up__parse_prop[update.c:81] got property for share:
svn:entry:committed-​date=2006-08-10T22:2​6:50.684494Z
03:27:42.981 up__parse_prop[update.c:81] got property for share:
svn:entry:last-author=gunter
03:27:42.981 up__parse_prop[update.c:81] got property for share:
svn:entry:uuid=de9c9​2fe-7908-0410-9c59-e​1f573f8e05f
03:27:42.981 ops__find_entry_byna​me[est_ops.c:620] found .kde/share/apps
on 0x8145e28; ignored: 0x1
03:27:42.982 up__parse_prop[update.c:81] got property for apps:
svn:entry:committed-rev=93
03:27:42.982 up__parse_prop[update.c:81] got property for apps:
svn:entry:committed-​date=2006-08-10T22:2​6:50.684494Z
03:27:42.982 up__parse_prop[update.c:81] got property for apps:
svn:entry:last-author=gunter
03:27:42.982 up__parse_prop[update.c:81] got property for apps:
svn:entry:uuid=de9c9​2fe-7908-0410-9c59-e​1f573f8e05f
03:27:42.982 ops__find_entry_byna​me[est_ops.c:620]
found .kde/share/apps/kwallet on 0x814c4f4; ignored: 0x1
03:27:42.982 up__parse_prop[update.c:81] got property for kwallet:
svn:entry:committed-rev=93
03:27:42.982 up__parse_prop[update.c:81] got property for kwallet:
svn:entry:committed-​date=2006-08-10T22:2​6:50.684494Z
03:27:42.982 up__parse_prop[update.c:81] got property for kwallet:
svn:entry:last-author=gunter
03:27:42.982 up__parse_prop[update.c:81] got property for kwallet:
svn:entry:uuid=de9c9​2fe-7908-0410-9c59-e​1f573f8e05f
03:27:42.982 up__add_entry[update.c:387] add
entry .kde/share/apps/kwal​let/kdewallet_zb.kwl​
03:27:42.982 ops__find_entry_byna​me[est_ops.c:620] found kdewallet_zb.kwl
on 0x826c878; ignored: 0x2

An error occurred at 03:27:42.983: Die Datei existiert bereits (17)
  in up__add_entry [update.c:403]:
file .kde/share/apps/kwal​let/kdewallet_zb.kwl​ already exists
  in up__add_file [update.c:685]
  in update_work [update.c:1104]: reporter->finish_report: up__add_file
  in update_work [update.c:1114]: up__add_file
  in main [fsvs.c:524]: action update failed
FSVS (licensed under the GPLv2), (C) by Ph. Marek; version trunk:396


HTH,

  Gunter

--
+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+
"What do people like to drink here, then?"
The landlord looked sideways at his customers, a clever trick given that
they were directly in front of him. -- Mort goes out for a drink
         (Terry Pratchett, Mort)
+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+
+ PGP-verschlüsselte Mails bevorzugt! +
+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+
Attachments

Re: error in update_work during / before update

Author pmarek
Full name P.Marek
Date 2006-08-25 10:16:23 PDT
Message On Saturday 19 August 2006 00:35 Gunter Ohrner wrote:
> Mh, if you have any idea how to extract relevant information from the log
> or how to "anonymize" it a bit, I'd definitely prefer to do that. There
> is no top-secret information in the log, but of course it basically
> contains all path/filenames from the managed home directory...
I believe that's no longer necessary.
I think I found that bug. Nasty, nasty ...
Thank you for reporting!

Please try current trunk.


Regards,

Phil

--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: error in update_work during / before update

Author Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Full name Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Date 2006-08-18 15:35:49 PDT
Message Am Freitag, 18. August 2006 18:28 schrieb Philipp Marek:
> Could you send a complete log of "fsvs -d up"? Maybe bzip2ed?
> Or are there privacy issues?
> I'll try to find a way to restrict the interesting log-lines.

Mh, if you have any idea how to extract relevant information from the log
or how to "anonymize" it a bit, I'd definitely prefer to do that. There
is no top-secret information in the log, but of course it basically
contains all path/filenames from the managed home directory...

Greetings,

  Gunter

--
*** Powered by AudioScrobbler --> http://www.last.fm/u​ser/Interneci/ ***
23:43 | Penumbra - Hope
23:38 | Penumbra - The Prophetess
23:32 | Penumbra - Seclusion
23:28 | Penumbra - Cursed Destiny
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
Attachments

Re: error in update_work during / before update

Author pmarek
Full name P.Marek
Date 2006-08-18 09:28:09 PDT
Message On Friday 18 August 2006 07:12 Gunter Ohrner wrote:
> Am Donnerstag, 17. August 2006 23:31 schrieb Gunter Ohrner:
> > > > > What happens on a new "fsvs sync-repos"?
> >
> > I simple rebootet and reinitiated the sync-repos run which correctly
> > restarted from the beginning.
So at least it's persistent ... Now we only have to know what happens.

Could you send a complete log of "fsvs -d up"? Maybe bzip2ed?
Or are there privacy issues?
I'll try to find a way to restrict the interesting log-lines.


Regards,

Phil


--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: error in update_work during / before update

Author pmarek
Full name P.Marek
Date 2006-08-18 09:26:19 PDT
Message On Thursday 17 August 2006 23:31 Gunter Ohrner wrote:
> Am Donnerstag, 17. August 2006 21:25 schrieb Philipp Marek:
> > parameters I could reproduce your problem; fsvs didn't find the entry
> > because it thought that it should be ignored.
>
> Well, .kde does match an ignore entry in fact. Reading the docs I got the
> impression that ignore patterns only avoid new matched files being
> noticed and commited by fsvs, and not causing problems with already
> managed ones? I understood that also the "fsvs add" was implemented to
> utilize this behaviour and to force some otherwise ignored files to be
> managed anyway. Am I right the way I understood how it should happen, or
> am I trying to misuse the "ignore"-feature?
No, you're completely right.

> The ignore-entry in question is "./.*", which of course matches anything
> starting with ".kde". (And it is supposed to.)
Yes.

> > *My* problem is, that was on a ramfs and the processor freezed once
> > again .... So I'll have to try again.
> >
> :-(
> :
> > > > What happens on a new "fsvs sync-repos"?
> >
> > Take your time.
>
> I also just had a hard freeze during sync-repos. :-/ I hope this doesn't
> damage some internal data structures of fsvs' WAA?
Hmmmm ... is there some freeze_processor() in sync.c? :-)

No; all directory data is written to a temporary file, and renamed if
finished. So this should do no bad things.


> I simple rebootet and reinitiated the sync-repos run which correctly
> restarted from the beginning.
OK. Thank you for your help!


Regards,

Phil


--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: error in update_work during / before update

Author Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Full name Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Date 2006-08-17 22:12:59 PDT
Message Am Donnerstag, 17. August 2006 23:31 schrieb Gunter Ohrner:
> > > > What happens on a new "fsvs sync-repos"?
> I simple rebootet and reinitiated the sync-repos run which correctly
> restarted from the beginning.

Ok, the new sync-repos finished, but the same problem persists.

Greetings,

  Gunter

--
*** Powered by AudioScrobbler --> http://www.last.fm/u​ser/Interneci/ ***
23:36 | Within Temptation - Forsaken
23:31 | Within Temptation - It's the Fear
23:03 | Within Temptation - Jillian (I'd Give My Heart)
22:58 | Within Temptation - Stand My Ground
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
Attachments

Re: error in update_work during / before update

Author Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Full name Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Date 2006-08-17 14:31:43 PDT
Message Am Donnerstag, 17. August 2006 21:25 schrieb Philipp Marek:
> parameters I could reproduce your problem; fsvs didn't find the entry
> because it thought that it should be ignored.

Well, .kde does match an ignore entry in fact. Reading the docs I got the
impression that ignore patterns only avoid new matched files being
noticed and commited by fsvs, and not causing problems with already
managed ones? I understood that also the "fsvs add" was implemented to
utilize this behaviour and to force some otherwise ignored files to be
managed anyway. Am I right the way I understood how it should happen, or
am I trying to misuse the "ignore"-feature?

The ignore-entry in question is "./.*", which of course matches anything
starting with ".kde". (And it is supposed to.)

> *My* problem is, that was on a ramfs and the processor freezed once
> again .... So I'll have to try again.

:-(

> > > What happens on a new "fsvs sync-repos"?
> Take your time.

I also just had a hard freeze during sync-repos. :-/ I hope this doesn't
damage some internal data structures of fsvs' WAA?

I simple rebootet and reinitiated the sync-repos run which correctly
restarted from the beginning.

Greetings,

  Gunter

--
*** Powered by AudioScrobbler --> http://www.last.fm/u​ser/Interneci/ ***
23:03 | Within Temptation - Jillian (I'd Give My Heart)
22:58 | Within Temptation - Stand My Ground
22:51 | Within Temptation - Deceiver of Fools
22:47 | Asp - Ich will brennen
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
Attachments

Re: error in update_work during / before update

Author pmarek
Full name P.Marek
Date 2006-08-17 12:25:20 PDT
Message On Thursday 17 August 2006 20:40 Gunter Ohrner wrote:
> Am Donnerstag, 17. August 2006 18:53 schrieb Philipp Marek:
> > > Could you give me some more details, so I can try to reproduce the
> > > bug?
> >
> > If you can update your fsvs to current trunk, could you try "fsvs info"
> > on the path it reports as missing?
>
> gunter@Zweiblum:~ > fsvs info .kde/share/apps/kwallet
> URL: svn://127.0.0.1/home
> .... 4096 ./.kde/share/apps/kwallet
> Type: directory
> Status: 0x0
> Flags: 0x100000
> Dev: 0
> Inode: 475151
> Mode: 040700
> UID/GID: 1000/1000
> MTime: Mon Aug 7 23:23:39 2006
> CTime: Mon Aug 7 23:23:39 2006
> Revision: 93
> Size: 4096
> gunter@Zweiblum:~ >
So it's an entry which fsvs knows about.

> I'm really hoping it's a genuine problem with fsvs and I'm currently not
> just making some really stupid mistakes on my side, wasting your time...
Well, with some combinations of update/sync-repos/remote-status with -r
parameters I could reproduce your problem; fsvs didn't find the entry because
it thought that it should be ignored.

*My* problem is, that was on a ramfs and the processor freezed once again ....
So I'll have to try again.

> > What happens on a new "fsvs sync-repos"?
>
> Mh, that's easier asked than tried - the repository contains a significant
> number of files, the "server" machine is pretty slow and I'm currently on
> a crappy mobile UMTS/GPRS internet connection - but I'll give my best to
> try... Just do not expect an answer before tomorrow... ;)
Take your time.

Thank you for your help!


Regards,

Phil

--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: error in update_work during / before update

Author Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Full name Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Date 2006-08-17 11:40:03 PDT
Message Am Donnerstag, 17. August 2006 18:53 schrieb Philipp Marek:
> > Could you give me some more details, so I can try to reproduce the
> > bug?
> If you can update your fsvs to current trunk, could you try "fsvs info"
> on the path it reports as missing?

gunter@Zweiblum:~ > fsvs info .kde/share/apps/kwallet
URL: svn://127.0.0.1/home
.... 4096 ./.kde/share/apps/kwallet
        Type: directory
        Status: 0x0
        Flags: 0x100000
        Dev: 0
        Inode: 475151
        Mode: 040700
        UID/GID: 1000/1000
        MTime: Mon Aug 7 23:23:39 2006
        CTime: Mon Aug 7 23:23:39 2006
        Revision: 93
        Size: 4096
gunter@Zweiblum:~ >

I'm really hoping it's a genuine problem with fsvs and I'm currently not
just making some really stupid mistakes on my side, wasting your time...

> What happens on a new "fsvs sync-repos"?

Mh, that's easier asked than tried - the repository contains a significant
number of files, the "server" machine is pretty slow and I'm currently on
a crappy mobile UMTS/GPRS internet connection - but I'll give my best to
try... Just do not expect an answer before tomorrow... ;)

Greetings,

  Gunter

--
*** Powered by AudioScrobbler --> http://www.last.fm/u​ser/Interneci/ ***
20:13 | Suicide Commando - Sterbehilfe
20:06 | Rotersand - Electronic World Transmission (SITD Reconstruction)
19:59 | Funker Vogt - History (Timeless Decay Mix by Icon of Coil)
19:54 | Covenant - Bullet
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
Attachments

Re: error in update_work during / before update

Author Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Full name Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Date 2006-08-17 10:00:07 PDT
Message Am Donnerstag, 17. August 2006 16:30 schrieb Philipp Marek:
> > > I just released a 1.0.12 (before seeing your mail); there are some
> > > problems fixed, this might be among them.
> > Unfortunately it didn't doesn't seem to.
> So it works now ;-) ?

Uhm. Ok, you got me... ;)

> I committed a change to print not-found entries; if you don't want to
> use the trunk of fsvs, I have the patch attached.

The few last lines of the output:

18:36:11.672 update_work[update.c:1098] reporting changed paths
18:36:11.679 ops__build_path[est_ops.c:514] need 1024 bytes
18:36:11.679 ops__build_path[est_ops.c:522] reusing 10
18:36:11.679 ops__build_path[est_ops.c:560] status=0;
path=./.kde/share/ap​ps/kwallet/kdewallet​_zb.kwl
18:36:11.679 ac___up_set_paths[up​date.c:1009]
changed: ./.kde/share/apps/kw​allet/kdewallet_zb.k​wl
18:36:11.679 ops__build_path[est_ops.c:514] need 1024 bytes
18:36:11.679 ops__build_path[est_ops.c:522] reusing 11
18:36:11.679 ops__build_path[est_ops.c:560] status=0;
path=./.kde/share/ap​ps/knotes/notes.ics
18:36:11.679 ac___up_set_paths[up​date.c:1009]
changed: ./.kde/share/apps/kn​otes/notes.ics
18:36:20.965 up__parse_prop[update.c:81] got property for .:
svn:entry:committed-rev=93
18:36:20.965 up__parse_prop[update.c:81] got property for .:
svn:entry:committed-​date=2006-08-10T22:2​6:50.684494Z
18:36:20.965 up__parse_prop[update.c:81] got property for .:
svn:entry:last-author=gunter
18:36:20.965 up__parse_prop[update.c:81] got property for .:
svn:entry:uuid=de9c9​2fe-7908-0410-9c59-e​1f573f8e05f
18:36:20.965 up__parse_prop[update.c:81] got property for .kde:
svn:entry:committed-rev=93
18:36:20.965 up__parse_prop[update.c:81] got property for .kde:
svn:entry:committed-​date=2006-08-10T22:2​6:50.684494Z
18:36:20.965 up__parse_prop[update.c:81] got property for .kde:
svn:entry:last-author=gunter
18:36:20.965 up__parse_prop[update.c:81] got property for .kde:
svn:entry:uuid=de9c9​2fe-7908-0410-9c59-e​1f573f8e05f
18:36:20.965 up__parse_prop[update.c:81] got property for share:
svn:entry:committed-rev=93
18:36:20.965 up__parse_prop[update.c:81] got property for share:
svn:entry:committed-​date=2006-08-10T22:2​6:50.684494Z
18:36:20.965 up__parse_prop[update.c:81] got property for share:
svn:entry:last-author=gunter
18:36:20.965 up__parse_prop[update.c:81] got property for share:
svn:entry:uuid=de9c9​2fe-7908-0410-9c59-e​1f573f8e05f
18:36:20.965 up__parse_prop[update.c:81] got property for apps:
svn:entry:committed-rev=93
18:36:20.965 up__parse_prop[update.c:81] got property for apps:
svn:entry:committed-​date=2006-08-10T22:2​6:50.684494Z
18:36:20.965 up__parse_prop[update.c:81] got property for apps:
svn:entry:last-author=gunter
18:36:20.965 up__parse_prop[update.c:81] got property for apps:
svn:entry:uuid=de9c9​2fe-7908-0410-9c59-e​1f573f8e05f
18:36:20.965 ops__find_entry_byna​me[est_ops.c:623] Searching for kwallet
(.kde/share/apps/kwallet) found no entry (ignored_too=0)

That's what svn and ls have to say about this path:

gunter@Zweiblum:~ > svn ls svn://(XXXX)/.kde/sh​are/apps/kwallet
kdeXXX1.kwl
kdeXXX2.kwl
kdewallet_zb.kwl
gunter@Zweiblum:~ > dir .kde/share/apps/kwallet
insgesamt 116
-rw------- 1 gunter gunter 50504 2006-08-04 10:51 kdeXXX1.kwl
-rw------- 1 gunter gunter 23268 2006-08-04 10:51 kdeXXX2.kwl
-rw-r--r-- 1 gunter gunter 36440 2006-08-17 10:59 kdewallet_zb.kwl
gunter@Zweiblum:~ >

> But to get your actions straight:
> You did "fsvs sync-repos" on machine A, then a commit on A.
> Then the same on B and C, where C has the latest version.

It actually where only 2 machines in this case, but otherwise I did
exactly that, yes. The repository was pre-seeded, so to speak, and then I
synced and committed machine A, then B.

> Then you try an update on A or B, and you get this error? Or is this on
> C?

It happens on both A and B, IIRC. (I quickly tried an update on A last
weekend as I do not have permanent local or remote access to this machine
and IIRC it failed with the same error message.)

The messages I'm currently sending to you are from machine B.

Greetings,

  Gunter

--
*** Powered by AudioScrobbler --> http://www.last.fm/u​ser/Interneci/ ***
16:57 | Dulce Liquido - Pissed Off
16:52 | Decoded Feedback - Phoenix
16:12 | Asp - Ich will brennen
16:08 | Pink Turns Blue - Seven Years (M'Era Luna Edit)
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
Attachments

Re: error in update_work during / before update

Author pmarek
Full name P.Marek
Date 2006-08-17 09:53:03 PDT
Message On Thursday 17 August 2006 18:27 Philipp Marek wrote:
> Could you give me some more details, so I can try to reproduce the bug?
If you can update your fsvs to current trunk, could you try "fsvs info" on the
path it reports as missing?

What happens on a new "fsvs sync-repos"?

Thank you for your help!


Regards,

Phil

--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: error in update_work during / before update

Author pmarek
Full name P.Marek
Date 2006-08-17 09:27:20 PDT
Message Hello Gunter!

> Playing with sync-repos I can reproduce a similar error, which could be
> related. I'll try to fix that.
I just found that that was a bug in the test-scripts (wrong order of
statements).
I cannot find a bug now.

> Please apply the patch below, and send me the last lines of output; and
> please tell me whether the given path already exists or not.
Could you give me some more details, so I can try to reproduce the bug?


Regards,

Phil

--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: error in update_work during / before update

Author pmarek
Full name P.Marek
Date 2006-08-17 07:30:14 PDT
Message On Wednesday 16 August 2006 20:59 Gunter Ohrner wrote:
> Am Mittwoch, 16. August 2006 12:12 schrieb Ph. Marek:
> > > However, if I now try to "fsvs update", the following happens:
> > > An error occurred at 07:31:11.750: Datei oder Verzeichnis nicht
> > > gefunden (2)
> >
> > I just released a 1.0.12 (before seeing your mail); there are some
> > problems fixed, this might be among them.
> Unfortunately it didn't doesn't seem to.
So it works now ;-) ?

> > Could you please try with 1.0.12, and if it fails, send me the output
> > of fsvs up -v -d please?
>
> I hope this fragment suffices?
Sorry, I don't think so. It doesn't say what isn't found.

I committed a change to print not-found entries; if you don't want to use the
trunk of fsvs, I have the patch attached.


But to get your actions straight:
You did "fsvs sync-repos" on machine A, then a commit on A.
Then the same on B and C, where C has the latest version.

Then you try an update on A or B, and you get this error? Or is this on C?


> (Snip)
...
> 20:56:06.686 up__parse_prop[update.c:81] got property for apps:
> svn:entry:uuid=de9c9​2fe-7908-0410-9c59-e​1f573f8e05f
>
>
> An error occurred at 20:56:10.117: Datei oder Verzeichnis nicht gefunden
> (2)
> in update_work [update.c:1104]: reporter->finish_report:
> up__open_directory
> in update_work [update.c:1114]: up__open_directory
> in main [fsvs.c:514]: action update failed
> FSVS (licensed under the GPLv2), (C) by Ph. Marek; version fsvs-1.0.12:362
> (Snap)
Playing with sync-repos I can reproduce a similar error, which could be
related. I'll try to fix that.

Please apply the patch below, and send me the last lines of output; and please
tell me whether the given path already exists or not.


Regards,

Phil

--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!
Attachments

Re: error in update_work during / before update

Author Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Full name Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Date 2006-08-16 11:59:21 PDT
Message Am Mittwoch, 16. August 2006 12:12 schrieb Ph. Marek:
> > However, if I now try to "fsvs update", the following happens:
> > An error occurred at 07:31:11.750: Datei oder Verzeichnis nicht
> > gefunden (2)
> I just released a 1.0.12 (before seeing your mail); there are some
> problems fixed, this might be among them.

Unfortunately it didn't doesn't seem to.

> Could you please try with 1.0.12, and if it fails, send me the output
> of fsvs up -v -d please?

I hope this fragment suffices?

(Snip)
20:56:01.994 update_work[update.c:1056] HEAD is at 93
20:56:03.884 update_work[update.c:1092] setting root revision to 93

20:56:03.884 update_work[update.c:1098] reporting changed paths
20:56:03.934 ops__build_path[est_ops.c:514] need 1024 bytes
20:56:03.934 ops__build_path[est_ops.c:522] reusing 9
20:56:03.934 ops__build_path[est_ops.c:560] status=0;
path=./.kde/share/ap​ps/knotes/notes.ics
20:56:03.934 ac___up_set_paths[up​date.c:1009]
changed: ./.kde/share/apps/kn​otes/notes.ics
20:56:06.683 up__parse_prop[update.c:81] got property for .:
svn:entry:committed-rev=93
20:56:06.683 up__parse_prop[update.c:81] got property for .:
svn:entry:committed-​date=2006-08-10T22:2​6:50.684494Z
20:56:06.684 up__parse_prop[update.c:81] got property for .:
svn:entry:last-author=gunter
20:56:06.684 up__parse_prop[update.c:81] got property for .:
svn:entry:uuid=de9c9​2fe-7908-0410-9c59-e​1f573f8e05f
20:56:06.684 up__parse_prop[update.c:81] got property for .kde:
svn:entry:committed-rev=93
20:56:06.685 up__parse_prop[update.c:81] got property for .kde:
svn:entry:committed-​date=2006-08-10T22:2​6:50.684494Z
20:56:06.685 up__parse_prop[update.c:81] got property for .kde:
svn:entry:last-author=gunter
20:56:06.685 up__parse_prop[update.c:81] got property for .kde:
svn:entry:uuid=de9c9​2fe-7908-0410-9c59-e​1f573f8e05f
20:56:06.686 up__parse_prop[update.c:81] got property for share:
svn:entry:committed-rev=93
20:56:06.686 up__parse_prop[update.c:81] got property for share:
svn:entry:committed-​date=2006-08-10T22:2​6:50.684494Z
20:56:06.686 up__parse_prop[update.c:81] got property for share:
svn:entry:last-author=gunter
20:56:06.686 up__parse_prop[update.c:81] got property for share:
svn:entry:uuid=de9c9​2fe-7908-0410-9c59-e​1f573f8e05f
20:56:06.686 up__parse_prop[update.c:81] got property for apps:
svn:entry:committed-rev=93
20:56:06.686 up__parse_prop[update.c:81] got property for apps:
svn:entry:committed-​date=2006-08-10T22:2​6:50.684494Z
20:56:06.686 up__parse_prop[update.c:81] got property for apps:
svn:entry:last-author=gunter
20:56:06.686 up__parse_prop[update.c:81] got property for apps:
svn:entry:uuid=de9c9​2fe-7908-0410-9c59-e​1f573f8e05f


An error occurred at 20:56:10.117: Datei oder Verzeichnis nicht gefunden
(2)
  in update_work [update.c:1104]: reporter->finish_report:
up__open_directory
  in update_work [update.c:1114]: up__open_directory
  in main [fsvs.c:514]: action update failed
FSVS (licensed under the GPLv2), (C) by Ph. Marek; version fsvs-1.0.12:362
(Snap)

Greetings,

  Gunter

--
*** Powered by AudioScrobbler --> http://www.last.fm/u​ser/Interneci/ ***
17:55 | Asp - Ich will brennen
17:50 | Covenant - Bullet
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
Attachments

Re: error in update_work during / before update

Author pmarek
Full name P.Marek
Date 2006-08-16 03:12:23 PDT
Message Hello Gunter!

> I just wanted to quickly verify if this is a known problem / bug.
>
> I just added some larger, existing directory tree (a home directory),
> present in nearly the same form on several machines, to FSVS followed by
> an "fsvs sync-repos" and "fsvs commit" on all but the committing machine
> to get all information into the repository. I chose the order in doing
> that such that the sync and commit on the machine with the most
> significant / most recent data came last, as a commit after a sync-repos
> will change the most current repository revision to match the comitting
> machine's working copy, as stated by the docs.
>
> However, if I now try to "fsvs update", the following happens:
>
> # fsvs update -v
> An error occurred at 07:31:11.750: Datei oder Verzeichnis nicht gefunden
> (2)
> in update_work: reporter->finish_report: up__open_directory
> in update_work: up__open_directory
> in main: action update failed
> Version fsvs-1.0.11:329
> #
I'm currently not at home, so I cannot take a good look at that.

I just released a 1.0.12 (before seeing your mail); there are some
problems fixed, this might be among them.

> I there anything else I could do to help troubleshooting the problem?
Could you please try with 1.0.12, and if it fails, send me the output of
     fsvs up -v -d
please?
I'll have a look ASAP, I hope it's possible today or tomorrow.


Thank you very much!


Regards,

Phil


--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!
Page: of 2 « Previous | Next »
Messages per page: