1. Edit the \bin\setenv.sh file (or setenv.bat on Windows) and add the “-Datlassian.recovery.password=temporarypassword” argument to the JVM_SUPPORT_RECOMMENDED_ARGS property. The property value must be non-blank,Here we are using “temporarypassword”, but you can use your own value.

2. Start Stash.
3. Log in to Stash using the ‘recovery_admin’ username and the temporary password specified in Step 1.
4. Repair your Stash configuration.You may reset the admin password as well. We strongly recommend that you do not perform other actions while Stash is in recovery mode.
5. Confirm your ability to log in with your usual admin profile.
6. Shut down Stash, remove the atlassian.recovery.password argument from setenv.sh, and restart Stash as usual.

Reference- confluence.atlassian.com/display/STASH/Lockout+recovery+process
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post If you have forgotton the admin password of Stash appeared first on scmGalaxy.

Git is distributes system, the beauty of the git make is more robust and easy to recover from any last known good working copy.

However, You can not always rely on such copy and you will definitely need proper backup solution to deal with such situation.

There are many ways to take backup of git repositories.
I am listing few here.

You can directly take a tar of the git repo directory as it has the whole bare contents of the repo on server. There is a slight possibility that somebody may be working on repo while taking backup.
The following command will give you the bare clone of repo (just like it is in server), then you can take a tar of the location where you have cloned without any issue.
git clone –bare {your backup local repo} {new location where you want to clone}

Reference – www.scmtechblog.net/2015/07/git-repository-backup.html

rajeshkumar replied the topic: Git repository backup
Thanks for useful info.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Git repository backup appeared first on scmGalaxy.

-Saritha

The post Rename the Branch name appeared first on scmGalaxy.

“Server sent unexpected return value (423 Locked) in response to PUT request for”

scmuser replied the topic: Re:Server sent unexpected return value (423 Locked) i
i found the solution using Tortoise Svn. Steal lock and then update and it worked for me.

Raj

The post Server sent unexpected return value (423 Locked) i appeared first on scmGalaxy.

Error validating server certificate for https://XYZ:443:
– Unknown certificate issuer
Fingerprint: 81:bb:5d:da:c5:7d:fa:f3:f4:9f:06:55:c6:34:e3:b4:64:d0:47:bc
Distinguished name: www.digicert.com , DigiCert Inc, US

sgadmin replied the topic: Re:Error validating server certificate for
It seems your cache Security certification for SVN server has been expired to removed. please Click on “Accept Permanently” to get rid of this issues.

Background:

When speaking to Apache via https://, a Subversion client can receive two different types of information:

a server certificate
a demand for a client certificate

If the client receives a server certificate, it needs to verify that it trusts the certificate: is the server really who it claims to be? The OpenSSL library does this by examining the signer of the server certificate, or certifying authority (CA). If OpenSSL is unable to automatically trust the CA, or if some other problem occurs (such as an expired certificate or hostname mismatch), the Subversion commandline client will ask you whether you want to trust the server certificate anyway.

svn list host.example.com/repos/project

Error validating server certificate for ‘ home.example.com:443 ‘:
– The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
– Hostname: host.example.com
– Valid: from Jan 30 19:23:56 2004 GMT until Jan 30 19:23:56 2006 GMT
– Issuer: CA, example.com, Sometown, California, US
– Fingerprint: 7d:e1:a9:34:33:39:ba:6a:e9:a5:c4:22:98:7b:76:5c:92:a0:9c:7b

(R)eject, accept (t)emporarily or accept (p)ermanently?

This dialogue should look familiar; it’s essentially the same question you’ve probably seen coming from your web browser (which is just another HTTP client like Subversion!). If you choose the (p)ermanent option, the server certificate will be cached in your private run-time auth/ area in just the same way your username and password are cached (see the section called “Client Credentials Caching”.) If cached, Subversion will automatically remember to trust this certificate in future negotiations.

Your run-time servers file also gives you the ability to make your Subversion client automatically trust specific CAs, either globally or on a per-host basis. Simply set the ssl-authority-files variable to a semicolon-separated list of PEM-encoded CA certificates:

[global]
ssl-authority-files = /path/to/CAcert1.pem;/path/to/CAcert2.pem

Many OpenSSL installations also have a pre-defined set of “default” CAs that are nearly universally trusted. To make the Subversion client automatically trust these standard authorities, set the ssl-trust-default-ca variable to true.

When talking to Apache, a Subversion client might also receive a challenge for a client certificate. Apache is asking the client to identify itself: is the client really who it says it is? If all goes correctly, the Subversion client sends back a private certificate signed by a CA that Apache trusts. A client certificate is usually stored on disk in encrypted format, protected by a local password. When Subversion receives this challenge, it will ask you for both a path to the certificate and the password which protects it:

$ svn list host.example.com/repos/project

Authentication realm: host.example.com:443
Client certificate filename: /path/to/my/cert.p12
Passphrase for ‘/path/to/my/cert.p12’: ********
…

Notice that the client certificate is a “p12” file. To use a client certificate with Subversion, it must be in PKCS#12 format, which is a portable standard. Most web browsers are already able to import and export certificates in that format. Another option is to use the OpenSSL commandline tools to convert existing certificates into PKCS#12.

Again, the runtime servers file allows you to automate this challenge on a per-host basis. Either or both pieces of information can be described in runtime variables:

[groups]
examplehost = host.example.com

[examplehost]
ssl-client-cert-file = /path/to/my/cert.p12
ssl-client-cert-password = somepassword

Once you’ve set the ssl-client-cert-file and ssl-client-cert-password variables, the Subversion client can automatically respond to a client certificate challenge without prompting you. [24]

The post Error validating server certificate for appeared first on scmGalaxy.

Add a user to the file /etc/subversion/svn-authz, then give that user a password as described below.
A suitable command could be
sudo vim /etc/subversion/svn-authz
or
sudo emacs /etc/subversion/svn-authz.

Adding or changing password for a user
sudo htpasswd -m /etc/subversion/svn-auth-file sally
New password: *******
Re-type new password: *******
Adding password for user sally
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Add User to SVN Server and Set Password appeared first on scmGalaxy.

There are several ways to enable user authentication for web based applications, like .htaccess files, plain tekst files, databases, LDAP, etc. They all have their pros and cons. In case a central, flexible solution is needed, either a database or LDAP solution can be used.

I chose for an LDAP solution since it can be reused by many web and application servers and the applications that run on them while many LDAP solutions provide excellent tooling and easy configuration. Since Yenlo strongly focuses on GlassFish and other Sun tools, I chose OpenDS to authenticate against.The idea is to create a bunch of users and put them into one or more groups. Each group gets access to one specific Subversion repository and every user that needs access to a certain subversion repositoy needs to be in the corresponding group.

This blog describes the basic steps I took to get Basic HTTP authentication for Subversion using Apache2 and OpenDS.
Setting up the server

The server is running on Debian Etch, for which most of the required software is available via the Debian package repository. The packages I installed are
apache2
apache2-mpm-prefork
libapache2-svn
subversion
sun-java6-bin
sun-java6-jdk
sun-java6-jre

Apart form these packages I downloaded and installed the OpenDS 2.2 zip file from the OpenDS homepage. For this purpose I created a user and a group called “opends” and the directory /usr/local/opends which I gave both ownership and group “opends”. Next I logged in as user opends and extracted the zip file into that directory. Finally, as root, I created a start and stop script and used the update-rc.d script to make sure OpenDS is automatically started and stopped when the server is started and stopped.

Setting up Subversion

Let’s suppose that our organisation has decided to create a Subversion repository for each development project that we do. This means that we would get a directory structure like this, with the leaves being the root directories of each repository:
/usr/share/subversion
/repository1
/repository2

The repositories were created as root using these commands in the /usr/share/subversion directory
# svnadmin create repository1
# svnadmin create repository2

That’s all the configuration that was done to the Subversion repositories.

Configuring OpenDS

First, a basic setup of OpenDS needed to be done using the command
$ /usr/local/opends/OpenDS-2.2.0/bin/setup

For more info about this, see Setting Up the Directory Server. Please note that if you are not running OpenDS as root user, it will listen on port 1389.

The next step was to configure OpenDS so it contains a few users and groups. The main configuration tool for OpenDS is called control-panel and, in my case, it can be started as user “opends” by issuing this command:
$ /usr/local/opends/OpenDS-2.2.0/bin/control-panel

With this tool, among other things, you can manage the entries in the directory. For my purpose I created the next layout
base dn (dc=yenlo,dc=nl)
organisation (o=yenlo)
organisational unit (ou=devel)
user (uid=wouter1, password = wouter1)
user (uid=wouter2, password = wouter2)
user (uid=wouter3, password = wouter3)
group (cn=group1, uniqueMember=wouter1,wouter2)
group (cn=group2, uniqueMember=wouter2,wouter3)

which is a very simple layout but sufficient for now. Note that I created two Subversion repositories and therefore two LDAP groups, one for each Subversion repository.

Setting up Apache2 to get access to the Subversion repositories

First I configured Apache2 so the two repositories were accessible to anyone using e.g. a web browser. After libapache2-svn is installed, the module should be enabled in the Apache2 configuration files automatically. To verify this, check the
/etc/apache2/mods-enabled/

directory and make sure these symbolic links exist
dav.load -> ../mods-available/dav.load
dav_svn.conf -> ../mods-available/dav_svn.conf
dav_svn.load -> ../mods-available/dav_svn.load

If the first link is missing, create it as root using
# a2enmod dav

If the second and third are missing, create it as root using
# a2enmod dav_svn

To make sure the modules are loaded by Apache2, restart the server as root using
# /etc/init.d/apache2 restart

Now some modifications need to be made to the dav_svn configuration file
/etc/apache2/mods-available/dav_svn.conf

The idea is that there are two Subversion repositories that need to be configured individually. So, these two entries need to be put in the above mentioned configuration file

DAV svn
SVNPath /usr/share/subversion/repository1
SVNListParentPath On
SVNAutoversioning On
SVNReposName “Repository1 Subversion Repository”


DAV svn
SVNPath /usr/share/subversion/repository2
SVNListParentPath On
SVNAutoversioning On
SVNReposName “Repository2 Subversion Repository”

Now, if you point your browser to either http:///svn/repository1 or http:///svn/repository2 you should see the root of your repository.

Adding LDAP support using OpenDS

In order to use LDAP atuentication with Apache2, these two entries should be present in /etc/apache2/mods-enabled:
authnz_ldap.load -> ../mods-available/authnz_ldap.load
ldap.load -> ../mods-available/ldap.load

If they aren’t present, you can enable them as root with these commands
# a2enmod authnz_ldap
# a2enmod ldap
# /etc/init.d/apache2 restart

Now, each entry in /etc/apache2/mods-available/dav_svn.conf should be extended with these lines in order to get LDAP authentication working with OpenDS. Please note that you should pay attention to the group you assign to each subversion repository location. I am only showing the configuration addition for repository1 and leave it as an excercise to you to setup the second repository configuration. Also please note you make sure the correct password for the Directory Manager is provided. For more info about these configuration settings, please consult the OpenDS WIKI page on Apache Web Server.
AuthType Basic
AuthName “Repository1 Subversion Repository”
AuthBasicProvider ldap
AuthzLDAPAuthoritative off
AuthLDAPURL ldap://localhost:1389/dc=yenlo,dc=nl?uid
AuthLDAPBindDN “cn=Directory Manager”
AuthLDAPBindPassword mypassword
AuthLDAPGroupAttribute uniqueMember
AuthLDAPGroupAttributeIsDN on
Require ldap-group cn=repository1,ou=devel,o=yenlo,dc=yenlo,dc=nl

Issue a final
# /etc/init.d/apache2 restart

and you should be prompted for a username and password when you try to access either repository. Using the correct uid and password combination should grant you access to the repository.

Next stepts

The authentication mechanism we chose, Basic autentication, posts usernames and passwords in plain text, which potentially could be harmful in case someone sniffes the connection. I would strongly recommend to setup SSL based connections. Moreover, this blog post only shows how to secure one repository layout using LDAP. Both Subversion and Apache are sufficiently flexible that other layouts are possible. Those layouts most likely require tweaking of the Apache2 configuration options. Finally, I am not an LDAP expert so the directory structure I chose in OpenDS most likely can be much improved. However, following the steps in this article should get you on your way to using OpenDS incombination with Apache2.

Reference: Referencehttp://www.yenlo.nl/woutervanreeven/2010/03/15/apache2-ldap-authorization-for-subversion-with-opends/
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

rajeshkumar replied the topic: Re:Apache2 LDAP authorization for Subversion with Opends
Subversion authorization through LDAP with OpenDS

If you building a centralized development environment for a team or large group of users, the question of centralizing user identities, authentication and authorization is always popping up and the answer is often to use an LDAP directory server. The developer section of the OpenDS documentation wiki has a set of tutorials for using the OpenDS LDAP directory server with various web servers and open source project like GlassFish, Apache Tomcat, SugarCRM… But not yet for Subversion. Thankfully, Wooter van Reeven, Senior Consultant at Yenlo has just published a long and detailed tutorial for setting up Subversion authentication and authorization through LDAP, with OpenDS and Apache2.

blogs.sun.com/Ludo/entry/subversion_auth…on_through_ldap_with
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Apache2 LDAP authorization for Subversion with OpenDS appeared first on scmGalaxy.

The post How Can I Validate A SVN Server’s Back-up And Rest appeared first on scmGalaxy.

I just setup SVN on a server that is running Ubuntu server as a fresh install. I’ve got it up and running but am having difficult determining how to connect to it.

I’m trying to do an import using the local IP address: http://IP/RepositoryName but it’s saying it can’t resolve the IP. I’m wondering if there’s something on the server I need to setup.

I have not modified dav_svn.conf because there is another server here that is running SVN (I’m migrating it to a new server) and it’s dav_svn.conf is not modified. The current working SVN has a subdomain associated with the IP location of the server but doesn’t do anything special with the ports as far as I can tell.

I’m getting this error via RapidSVN when I try to import…
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post SVN Checkout URL – fresh install appeared first on scmGalaxy.

I would like to learn in depth of SVN hook scripts and SVN properties.
Could anyone please help me?

Thanks,
Vijay

scmuser replied the topic: Re:Need document/links for SVN hooks & Properties
try this
svnbook.red-bean.com/en/1.0/svn-book.html#svn-ch-5-sect-2.1
www.petefreitag.com/item/244.cfm
wordaligned.org/articles/a-subversion-pre-commit-hook

The post Need document/links for SVN hooks & Properties appeared first on scmGalaxy.

We have an existing Subversion repository that uses LDAP to manage users/passwords. There are some new users who we would like to provide read-only access to SVN. I did some Google searches and found a way to open up read-only access to anonymous users, but this is not what we want. We do not want to open up SVN to everyone. We still want to control login through LDAP, but we would like to prevent certain named users from being able to add/edit/delete.

I am assuming this can be done with a hook (pre-commit?), but I have no experience writing hooks. Can someone show me or point me to an example of how to do this?
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

rajeshkumar replied the topic: Re:Hook to make Subversion Read Only for specific use
I use an LDAP setup with config similar to:

in /etc/apache2/sites-enabled/mysite

DAV svn
SVNParentPath /var/svn
SVNListParentPath on
AuthBasicProvider ldap
AuthType Basic
AuthzLDAPAuthoritative Off
AuthzSVNAccessFile “/var/svn/conf/svnaccess.conf”
AuthName “My SVN”
AuthLDAPBindDN “…..”
AuthLDAPBindPassword “…..”
AuthLDAPURL “…..”
Require valid-user

/var/svn/conf/svnaccess.conf
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

rajeshkumar replied the topic: Re:Hook to make Subversion Read Only for specific use
I use an LDAP setup with config similar to:

in /etc/apache2/sites-enabled/mysite

DAV svn
SVNParentPath /var/svn
SVNListParentPath on
AuthBasicProvider ldap
AuthType Basic
AuthzLDAPAuthoritative Off
AuthzSVNAccessFile “/var/svn/conf/svnaccess.conf”
AuthName “My SVN”
AuthLDAPBindDN “…..”
AuthLDAPBindPassword “…..”
AuthLDAPURL “…..”
Require valid-user

/var/svn/conf/svnaccess.conf

[groups]
readonly = user1, user2

[/]
*=rw
@readonly=r
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Hook to make Subversion Read Only for specific use appeared first on scmGalaxy.

#!/bin/bash
for repos in `ls /var/opt/svn/` ; do
RESPOS_DIR=/var/opt/svn/$repos;
svnadmin dump -q $RESPOS_DIR | gzip > ~backup/Dropbox/backups/svn/$repos.dump.gz;
chgrp backup $RESPOS_DIR;
done
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Automatic backup all SVN repositories appeared first on scmGalaxy.

www.placona.co.uk/539/technology/moving-svn-folders/
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Moving SVN Folders appeared first on scmGalaxy.

To apply those revisions to a repository:
svnadmin load –ignore-uuid /path/to/repository < /path/to/dumpfile.svn The --ignore-uuid option allows the import to strip out uuid information from the source repository. I would restrict this operation to repositories with a common revision heritage otherwise the load would probably fail. Regards, Rajesh Kumar Twitt me @ twitter.com/RajeshKumarIn

The post Copy only certain SVN revisions from one repositor appeared first on scmGalaxy.

I have checked Common.pm and comment the code
# $logger->error( $error_string );
(which is not a right approach as we need to catch the error log message)

OR

Anyone suggest me any other tool to integrate Bugzilla with SVN

Thanks in advance

The post Integrate Bugzilla with SVN appeared first on scmGalaxy.

My directory structure:
Two branches:
/main_branch/sourcecodefiles
/build_branch à copy of a main branch

è Development happens only in main branch
è no one will commit in build_branch

My Requirement is: Whenever commit happens in main_branch , it should automatically merge the changes in to build branch (i.e it has to merge the changes and commit a new version of it)

There is no need for reverse merging since no changes will get committed in build branch, also it reduces the risk of merge conflicts.

Please let me know if anyone already has solution for this.

Regards,
Vijay

rajeshkumar replied the topic: Re:SVN query for auto merging!!!
SVN is not much smart enough in case of conflict.

if conflict arises you will have to do manually.

Refer more for
svnbook.red-bean.com/en/1.0/re16.html
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

mnanjala replied the topic: Re: SVN query for auto merging!!!
svnmerge.py will do it but you should write a shell script it will call that svnmerge.py tool once check in happened u can call this script by continuous integration server like Hudson

rajeshkumar replied the topic: Re: SVN query for auto merging!!!
Hi Praveen,

Can you please share the soruce link of svnmerge.py and implementation details.

Thanks in Advance?
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

mnanjala replied the topic: Re: SVN query for auto merging!!!
www.orcaware.com/svn/wiki/Svnmerge.py

The post SVN query for auto merging!!! appeared first on scmGalaxy.

AM trying to have the backup on Windows Dev Server. (Am not used to Windows

I have created a new repository on Windows Server.
Updated the required hooks
and using svnsync for the backup operation.

It worked fine till
committed revision 1.
copied properties for revision 1

…..

committed revision 1.
copied properties for revision 1

…..

Transmitting file data…….
……

And its stuck.
The Repo size is approx 1.2GB

I need to even automate this on Windows server.

Can anybody share inputs who is an expert on Windows or have done this before.

Thanks

The post Need to mirror SVN Repository from remote server to a WindowsDevServer appeared first on scmGalaxy.

I have done the successful migration form CVS to SVN,now i need to migrate few projects from Clearcase to SVN. Could anyone please give some ideas on this?

Thanks,
Vijay

rajeshkumar replied the topic: Re:ClearCase to SVN migration
There were a couple of relevant talks at SubConf:

MM4: Lutz Dornbusch, Polarion: Zero Downtime Migration to Subversion
www.subconf.de/fileadmin/PDF_Dateien/Sub…onf_2008/Vortraege/L
utz_Dornbusch-Zero_Downtime_Migration.pdf

MM5: Robert Cowham and Neal Firth, Vizim: Migrating ClearCase to Subversion
www.subconf.de/fileadmin/PDF_Dateien/Sub…onf_2008/Vortraege/R
obert_Cowham_and_Neal_Firth__Madrid_.pdf

www.unix-girl.com/cc2svn/

Both were well received from what I saw, but I think our approach covers
more options – but then I would say that
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Button replied the topic: Re: ClearCase to SVN migration
Hi Vjay,

Been looking to do something similar myself (migrate from clearcase to subversion that is), and I’ve evaluated a number of tools out there, but all of them appear to have their gaps. The best one I’ve seen so far is www.clearvision-cm.com/clearcase-subversion-migration.html but before purchasing it, I thought I’d check to see which one you used (seeing as this is a fairly old topic now) incase there are any I havn’t seen yet. That one seems pretty complete from what I can tell, but what with it being all our company data I want to make sure I haven’t missed anything

The post ClearCase to SVN migration appeared first on scmGalaxy.

rajeshkumar replied the topic: Re:Branch Managment in Subversion
Hi,

Can you redefine the questions. I may be able to help you out on this?

Regards,
Rajesh
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

mnanjala replied the topic: Re:Branch Managment in Subversion
Sure, what is the best way of branching in Subversion,

-Pravin

rajeshkumar replied the topic: Re:Branch Managment in Subversion
Hi praveen,
you can find SVN (Subversion) Branching Strategy information in url below…

community.scmgalaxy.com/pg/blog/rajeshku…n-branching-strategy
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

mnanjala replied the topic: Re:Branch Managment in Subversion
Thats Awsome and thanks Rajesh

-Pravin

Button replied the topic: Re:Branch Managment in Subversion
The problem with any branching approach, is how do you track what exactly has been merged into trunk, and what activity branches are contained in which tag etc. Check out agilescm, product from clearvision-cm, its pretty amazing and makes all of these tasks seemless, and its free for 10 or below users, see the link below

www.clearvision-cm.com/agilescm/overview

rajeshkumar replied the topic: Re:Branch Managment in Subversion
right now i am on Git. Will try soon
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Branch Managment in Subversion appeared first on scmGalaxy.

I’m in phase of implementing SVN1.7.7 and Bugzilaa 3.6.2 versions using SCMBUG. I’ve done all the configuration changes in Daemon.conf and glue.conf according to our project requirement.

When i try to commit any file against the bug num assigned to me,getting following error.

Error: Scmbug ERROR> Connection.pm:371:Scmbug::Connection::submit_request –

Error: ** Scmbug error 24: The daemon-spawned connection handler exited abnormally. Please check the daemon error logs.

Below are the errors in log files which i got.

2012/04/16 14:49:55 Scmbug WARN> Daemon.pm:582:Scmbug::Daemon::Daemon::spawn_child – 127.0.0.1:56483 Connection from SVN.BASE processed
2012/04/16 14:49:56 Scmbug WARN> Daemon.pm:568:Scmbug::Daemon::Daemon::spawn_child – 127.0.0.1:56484 Processing connection from SVN.BASE
2012/04/16 14:49:56 Scmbug WARN> Process.pm:866:Scmbug::Daemon::Process::process_activity_commit – 127.0.0.1:56484 Processing an ‘activity_commit’ for bug id ‘25007’ from SCM user ‘pramod.ashrith’
2012/04/16 14:49:56 Scmbug ERROR> Error.pm:103:Bugzilla::Error::_throw_error – You are not authorized to access bug #25007. To see this bug, you must
first log in to an account with the appropriate permissions.

I’ve access to the following bug in Bugzilla. Do we need to change anything in any Perl Module files..

Regards,
Pramod

rajeshkumar replied the topic: Re: SCMBUG Integration
I guess there are some issues with Permission. Have you re-verified all of your access such as Bugzilaa + SVN + USER?
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

venkata replied the topic: Re: SCMBUG Integration
Hi Rajesh,

Here are my below cridentials of SVN and Bugzilla.

SVN : pramod.ashrith
Bugzilla: pramod.ashrith@wipro.com

when i try to commit anything against the bug it says you don’t have the permission,i’m not understanding what permission is required, since the bug is assigned against me..please can you help me regarding this..if you share ur contact num i’l try to explain it in detail..you can text me or call me on this num ..

9591300221.

Regards,
Pramod

rajeshkumar replied the topic: Re: SCMBUG Integration
Hi Pramod,

I do not encourage sharing id/password info on public portal. Please try to find answer for following..
1. Do You have access on source code?
2. The web server can Bugzilla/Template.pm?
3. See whats the access level has been used to setup Bugzill/SBN integration.

if you can post error message, that might more helpful for you.

Also, you may want to to free support www.bugzilla.org/support/
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

venkata replied the topic: Re: SCMBUG Integration
Rajesh,

1. I’ve access at source code level.
2. The web server can Bugzilla/Template.pm? I din’t get this point what exactly you mean..
3.we are using email id and username.
exle SVN Usernme: pramod.ashrith
Bugzilla username: pramod.ashrith@abc.com

Scenario 1: When the bug is not assigned against my name when i try to commit i’m getting the proper message saying the bug id is not assigned to you, and it is assigned to some x person.Exle shown below.

Error: ** Scmbug error 7: Bug ‘20902’ does not belong to the product ‘BCG’. It belongs
Error: to product ‘xyz’.
Error: Bug ‘20902’ is not assigned to ‘pramod.ashrith’. It is assigned to ‘sangamesh.halidoddi@xyz.com’.

Scenario 2: when i try to commit any bug which is assigned to me in bugzilla,i’m getting the error in Daemon error logs.

Error: ** Scmbug error 7: Bug ‘25007’ is not assigned to ‘pramod.ashrith’. It is
Error: assigned to ‘pramod.ashrith@abc.com’.

Rajesh,if you observe in scenario 2 Error mesg..pramod.ashrith is SVN username and pramod.ashrith@abc.com is bugzilla username..

Pre-commit is blocking for the commit to happen.

If i use same username in SVN and Bugzilla i.e pramod.ashrith@abc.com
I’m getting below error..

Here Post-commit is blocking and the messages are not getting updated in bugzilla.

Error: ** Scmbug error 24: The daemon-spawned connection handler exited abnormally. Please check the daemon error logs.
Daemon Error log says..

2012/04/27 10:53:19 Scmbug WARN> Daemon.pm:582:Scmbug::Daemon::Daemon::spawn_child – 127.0.0.1:54909 Connection from SVN.BASE processed
2012/04/27 10:53:19 Scmbug WARN> Daemon.pm:568:Scmbug::Daemon::Daemon::spawn_child – 127.0.0.1:54910 Processing connection from SVN.BASE
2012/04/27 10:53:19 Scmbug WARN> Process.pm:866:Scmbug::Daemon::Process::process_activity_commit – 127.0.0.1:54910 Processing an ‘activity_commit’ for bug id ‘25007’ from SCM user ‘pramod.ashrith@abc.com’
2012/04/27 10:53:20 Scmbug ERROR> Error.pm:103:Bugzilla::Error::_throw_error – You are not authorized to access bug #25007. To see this bug, you must
first log in to an account with the appropriate permissions.

If i check Error.pm in the line num 103 it says $DAEMON_ERROR_DAEMON_MODE_MISSING
i’m not getting what exactly it means..

I’ve used DAEMON_MODE has ‘auto’ in daemon.conf file which chooses b/w threaded and forked mode depending on the OS.

Rajesh,i’m stuck in the middle of integration..
1. whether we need to change anything for regulgar expression matching for SVN/Bugzilla in Daemon.conf and glue.conf?
please help me to solve this issue..I hope you have got my issues clearly..If you need any more clarrification from my end..please revert back.

I would like to hear from you soon.

Regards,
Ashrith

venkata replied the topic: Re: SCMBUG Integration
Rajesh,

Any update about the below topic.Please do let me know if you get any idea.

Regards,
Pramod

rajeshkumar replied the topic: Re: SCMBUG Integration
Hi,

I posted same questions in mailing list and found that following answer. Hope this is helpful for you.

> I am just trying to help my friends but finding difficulty. Group members
> would like to take this issues up?

The SCMBug mailing list may be of help, as your problems are really
SCMBug specific. The last post on the list was almost one year ago,
the latest release of SCMBug in February last year and has known
compatibility issues with current versions of Bugzilla. It seems to me
that the author of SCMBug is really busy with his other projects now
and there’s a new extension for Bugzilla available which integrates it
with Subversion. You or your friends therefore may consider not using
SCMBug at all, unless you really need the features it provides.

scmbug-users@net.mkgnu.net
code.google.com/p/bugzilla-vcs/

> If i use same username in SVN and Bugzilla i.e pramod.ashrith@abc.com
> I’m getting below error..

SCMBug provides mechanisms in the configuration file to map SVN- with
Bugzilla-usernames, but in my opinion it is easier to use the same
für both systems.

> 2012/04/27 10:53:20 Scmbug ERROR>
> Error.pm:103:Bugzilla::Error::_throw_error – You are not authorized to
> access bug #25007. To see this bug, you must
> first log in to an account with the appropriate permissions.

I may be wrong but from my understanding SCMBug never needed to
authenticate to Bugzilla because even while it used some of
Bugzilla’s classes, it always was low level underneath authentication
and some things were directly added using the database. The error
message looks to me as if the account used to commit is even not able
to add a comment to the bug using the webinterface and therefore
SCMBug can’t do it, too.

I would check if the account is really able to see and change the bug
using the normal web interface after login to Bugzilla. I would doubt
it can, so change this and SCMBug should work, too.

> If i check Error.pm in the line num 103 it says
> $DAEMON_ERROR_DAEMON_MODE_MISSING
> i’m not getting what exactly it means..

I don’t think 103 is really the line were the error occurs, maybe it’s
some bug in using Log4perl or else.

Mit freundlichen Grüßen,

Thorsten Schöning

For more support, i suggest you to report here…

support-bugzilla@lists.mozilla.org
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post SCMBUG Integration appeared first on scmGalaxy.