I'm looking for a part-time remote job.

Hire me

I'm the author of:

Mastering Redmine is a comprehensive guide with tips, tricks and best practices, and an easy-to-learn structure.

Check the book's project or

Buy the book

Social pages of the book:

By buying this book you also donate to Redmine (see this page).

Follow me:

Support #2052

Misleading warning message when creating a (sub)repository

Added by Lluís - over 8 years ago. Updated over 8 years ago.

Target version:
Start date:
15 Jun 2012
Due date:
19 Jun 2012
% Done:


Redmine version:
External issue:


Creating a new repository in project “test”, I used identifier “foo” and path "/scm/git/test.foo”
(in order to exploit redmine’s multiple repository support).

Still, after creation SCM creator complains with “Redmine based authentication can not be used with this repository name.”,
which is not really true (at least when using Redmine.pm with git smart protocol support).


#1 Updated by Andriy Lesyuk over 8 years ago

  • Tracker changed from Bug to Support
  • Status changed from New to Open

You may be right... I’m not sure.

How does Redmine.pm with git smart protocol manages to handle repos with different identifiers? In other words how can I check this to hide the message?

#2 Updated by Lluís - over 8 years ago

I think git smart protocol support is not really involved in that, and Redmine.pm just strips \..* from the end of the repository name in order to accept projects with multiple repositories. For example, access to http://server/git/project.something is checked against project.

In fact, I’ve tried using SCM creator with a new repository identifier “foo” (for project “test”) and creating repository at "/home/code/git/test.bar”. I can access http://server/git/test.bar, just because I’m part of project “test”, but http://server/git/test.foo does not exist; so it looks like the identifier is just a nice thing to have when watching redmine’s web, but it’s not enforced (as redmine does not have per-repository security policies).

#3 Updated by Andriy Lesyuk over 8 years ago

  • Due date set to 19 Jun 2012
  • Status changed from Open to In Progress
  • Assignee set to Andriy Lesyuk
  • Target version set to 0.4.0
  • % Done changed from 0 to 100

Should be fixed... Can you confirm?

#4 Updated by Lluís - over 8 years ago

Works like a charm, thanks.

#5 Updated by Andriy Lesyuk over 8 years ago

  • Status changed from In Progress to Closed


Also available in: Atom PDF

Terms of use | Privacy policy