[Pushmi-users] svm locking issue, potentially related revision number problem

Wed May 2 15:07:12 EDT 2007

After installing subversion 1.4.3 and libsvn1 1.4.3 out of the Debian
experimental repository, everything seems to work just fine. I'll have
to do more vigorous testing, but at the moment that seems to have
solved the issues!

Thanks
 Aaron

On 5/2/07, Patrick Desnoyers <Patrick.Desnoyers at gameloft.com> wrote:
>
> Never tried it on Etch yet... I am still running Sarge.
>
> Not sure if 1.4.2 will do... I am running 1.4.3 and I remember something
> not working in 1.4.2 altho I think it was the verification process
> (pushmi verify). You may have to backport 1.4.3 (should be easy tho...
> Tell me if you need help).
>
> Here is a list of packages my pushmi package depends on. You probably
> don't need the ones related to Apache.
>
> Install these and see if it helps.
>
> Depends: libapp-cli-perl, liblocale-maketext-simple-perl,
> libsvn-core-perl, libsvn-perl, libsvn-simple-perl,
> libdata-hierarchy-perl, libclass-data-inheritable-perl,
> libclass-autouse-perl, libperlio-eol-perl, libterm-readkey-perl,
> libcache-memcached-perl, memcached, libsys-syscall-perl,
> libdanga-socket-perl, python-subversion, libuniversal-require-perl,
> libyaml-syck-perl, librunapp-perl, libsvn-mirror-perl,
> libpath-class-perl, libsvn-mirror-perl, libclass-accessor-perl,
> libperlio-via-symlink-perl, libperlio-via-dynamic-perl,
> libapache2-mod-perl2,libstring-crc32-perl, liblog-log4perl-perl,
> liblog-dispatch-perl, libversion-perl, libpod-simple-perl,
> libapache2-svn, libalgorithm-diff-perl, libipc-run3-perl, svk
>
>
>
> If it still fails, the author of pushmi will be back shortly. You should
> have an answer pretty quickly.
>
> Im interested in knowing what kind of requirements you have for this
> software ? What will you use it for ? :-)
>
> Patrick
>
> -----Original Message-----
> From: pushmi-users-bounces at bestpractical.com
> [mailto:pushmi-users-bounces at bestpractical.com] On Behalf Of Aaron
> Dulles-Coelho
> Sent: May 2, 2007 10:35 AM
> To: pushmi-users at bestpractical.com
> Subject: Re: [Pushmi-users] svm locking issue,potentially related
> revision number problem
>
> Sure...
>
> All machines are Debian Etch (4.0)
> All machines run Perl 5.8.8
>
> The systems share passwd and shadow info from a central cfengine
> service, and they accept passwordless ssh between them. I say this
> because that's how svn+ssh:// works on this set-up... it's a
> passwordless ssh that starts an svnserve process started on the server.
>
> I'll note the modules that are specified as required by Pushmi's
> Makefile.PL
>
> Pushmi is 0.994.0
>
> version.pm version 0.7203
>
> SVN::Core is 1.4.2. I think. Only one copy of Core.pm exists on the
> system, and it's provided by a Debian package libsvn-perl. The file
> itself has no version info, but the libsvn-perl deb package is
> 1.4.2dfsg1-2
>
> SVK 2.0.1
>
> App::CLI 0.07
>
> Cache::Memcached 1.34
>
> YAML::Syck 0.71
>
> Log::Log4perl 1.07
>
> Here's a question I've been researching but can't find any answers to:
> what's the specification of SVN::Repos::replay2() ? I can't find source
> for this anywhere!
>
> Aaron
>
> On 5/2/07, Patrick Desnoyers <Patrick.Desnoyers at gameloft.com> wrote:
> > For the lock problem, this is normal behavior :-). I agree it is a bit
>
> > confusing, but it means it locked the repo before trying the sync, the
>
> > successfully unlocked it ( result 1).
> >
> > For the more important problem, I do not know exactly. Can you send
> > the versions of the required perl packages and describe your system a
> bit ?
> > (OS, etc...)
> >
> > Patrick
> >
> > -----Original Message-----
> > From: pushmi-users-bounces at bestpractical.com
> > [mailto:pushmi-users-bounces at bestpractical.com] On Behalf Of Aaron
> > Dulles-Coelho
> > Sent: May 2, 2007 9:52 AM
> > To: pushmi-users at bestpractical.com
> > Subject: [Pushmi-users] svm locking issue,potentially related revision
>
> > number problem
> >
> > Hi,
> >
> > I'm testing Pushmi to see if I can make a proper, writeable repository
>
> > mirror. Names of servers have been changed to protect the innocent ;)
> > First of all, I have issues with locks -- Pushmi can't seem to unlock.
> > It also has strange revision number problems when I try to commit to
> > the Pushmi mirror. Here's the set-up ...
> >
> >
> > master:/# svnadmin create /svn; chgrp users svn -R;chmod g+w svn/db -R
>
> > slave:/# cat /etc/pushmi.conf
> > authproxy_port: 11211
> > slave:/# ps ax|grep memcached
> >  7129 ?        S      0:00 /usr/bin/memcached -m 64 -p 11211 -u root
> > slave:/# pushmi mirror /svn svn+ssh://master/svn Mirror initialized.
> >
> > At this point I get strange lock issues when I try to sync...
> >
> > slave:/# pushmi sync --nowait /svn
> > locked by /svn:svm:lock:_
> > unlock result: 1
> >
> > This surely isn't right! When I commit changes to the master and
> > re-run the sync, everything syncs up, but the unlock error continues
> >
> > client:~$ svn co svn+ssh://master/svn master Checked out revision 0.
> > client:~$ cd master; echo a > a; svn add a; svn ci -m 'added file a'
> > A         a
> > Adding         a
> > Transmitting file data .
> > Committed revision 1.
> >
> > slave:/# pushmi sync --nowait /svn
> > locked by /svn:svm:lock:_
> > Retrieving log information from 1 to 1 unlock result: 1 [/svn] sync
> > revision 1 to 1
> >
> >
> > Now here's a potentially related issue. When I make a checkout of the
> > slave repository, make a change, and commit, I get a strange revision
> > numbering error...
> >
> > client:~$ svn co svn+ssh://slave/svn slave
> > A    slave/a
> > Checked out revision 1.
> > client:~$ cd slave; echo b > b; svn add b; svn ci -m 'added file b'
> > A         b
> > Adding         b
> > Transmitting file data .svn: Commit failed (details follow):
> > svn: 'pre-commit' hook failed with error output:
> > No such revision -2
> >
> > Here's the output from the pushmi log...
> > slave:/# cat /tmp/pushmi.log
> > [7458][250] pushmi.runhook - [/svn] committing from txn 1-1 by dulles
> > [7458][434] pushmi.runhook - Fail to replay:  at
> > /usr/local/share/perl/5.8.8/Pushmi/Command/Runhook.pm line 91
> >         eval {...} called at
> > /usr/local/share/perl/5.8.8/Pushmi/Command/Runhook.pm line 90
> >
> >
> Pushmi::Command::Runhook::run('Pushmi::Command::Runhook=HASH(0x82c2168)'
> > ,
> > '/svn') called at /usr/local/share/perl/5.8.8/App/CLI/Command.pm line
> > 53
> >
> > App::CLI::Command::run_command('Pushmi::Command::Runhook=HASH(0x82c216
> > 8)
> > ',
> > '/svn') called at /usr/local/share/perl/5.8.8/App/CLI.pm line 79
> >         App::CLI::dispatch('Pushmi::Command') called at
> > /usr/local/bin/pushmi line 32 [7458][434] pushmi.runhook - [/svn]
> > Failed to replay txn to mirror: No such revision -2 [7458][436]
> > pushmi.svkmirror - locked by /svn:svm:lock:_ [7458][647]
> > pushmi.runhook
> > - Unlock on failure [7458][648] pushmi.svkmirror - unlock result: 1
> >
> >
> > Any notions on how to tackle these problems?
> >
> > --
> > Aaron
> > _______________________________________________
> > Pushmi-users mailing list
> > Pushmi-users at bestpractical.com
> > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/pushmi-users
> >
> _______________________________________________
> Pushmi-users mailing list
> Pushmi-users at bestpractical.com
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/pushmi-users
>