After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 601149 - Can't create project from existing git repository
Can't create project from existing git repository
Status: RESOLVED NOTABUG
Product: anjuta
Classification: Applications
Component: plugins: project-manager
2.28.x
Other Linux
: Normal major
: ---
Assigned To: Naba Kumar
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-08 13:43 UTC by Gal Rosen
Modified: 2009-11-16 17:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot of the error (185.03 KB, image/png)
2009-11-15 07:11 UTC, Gal Rosen
Details
A tar file of my test repository (50.00 KB, application/x-tar)
2009-11-15 10:48 UTC, Gal Rosen
Details

Description Gal Rosen 2009-11-08 13:43:00 UTC
I get this message while trying to import:

"Could not find a valid project backend for the directory given (scst). Please select a different directory, or try upgrading to a newer version of Anjuta."
Comment 1 Sébastien Granjoux 2009-11-10 20:00:21 UTC
Anjuta supports autotools project and partially makefile project.

A valid autotools project needs to have in the project directory a file named configure.ac or configure.in and Makefile.am.

A makefile project needs to have in the project directory a file named Makefile.

Is your project use autotools or makefile ?
Comment 2 James Liggett 2009-11-11 20:59:39 UTC
*** Bug 601567 has been marked as a duplicate of this bug. ***
Comment 3 James Liggett 2009-11-11 21:00:58 UTC
So is this even a git bug? It seems like a project manager issue to me...
Comment 4 Sébastien Granjoux 2009-11-11 21:17:39 UTC
I get this bug here too.

I haven't done any investigation but I think it is not in the project manager. I have been able to checkout the project from git and import it from the local directory without any troubles.

I think it is a problem in the project import dialog, not using the right argument to get the project from git or something like this.
Comment 5 Gal Rosen 2009-11-12 07:00:33 UTC
(In reply to comment #1)
> Anjuta supports autotools project and partially makefile project.
> 
> A valid autotools project needs to have in the project directory a file named
> configure.ac or configure.in and Makefile.am.
> 
> A makefile project needs to have in the project directory a file named
> Makefile.
> 
> Is your project use autotools or makefile ?

A makefile project.
Comment 6 Sébastien Granjoux 2009-11-12 18:04:42 UTC
(In reply to comment #5)
> A makefile project.

Thanks. I get this bug too and I don't think it's related to your project. It is probably a bug in the import from git dialog.

In the meantime, you should be able to open your project by getting it from git using the command line and then importing the local directory in Anjuta.
Comment 7 Sébastien Granjoux 2009-11-14 21:52:52 UTC
I will try to look at this tomorrow. It seems that the problem appears only if you change the destination directory.

It could be a problem in the ianjuta_vcs_checkout function in git plugin. The working directoy looks strange when running the clone command.
Comment 8 Gal Rosen 2009-11-15 07:11:08 UTC
Created attachment 147758 [details]
Screenshot of the error
Comment 9 Gal Rosen 2009-11-15 07:12:10 UTC
(In reply to comment #6)
> (In reply to comment #5)
> > A makefile project.
> 
> Thanks. I get this bug too and I don't think it's related to your project. It
> is probably a bug in the import from git dialog.
> 
> In the meantime, you should be able to open your project by getting it from git
> using the command line and then importing the local directory in Anjuta.

This does not work as well. I cloned the repository into a local directory, and still while trying to create project from existing source, I get the same problem.
Comment 10 Sébastien Granjoux 2009-11-15 09:14:30 UTC
> This does not work as well. I cloned the repository into a local directory, and
> still while trying to create project from existing source, I get the same
> problem.

In this case, the problem is more complex. This is probably the anjuta makefile project backend which is not able to load your project.

I'm currently working on this backend, but it will take time before it can replace the current code. Anyway, I will be interested to check that the new code can load your project or at least understand why it doesn't work. Do you have a link where I could get your project or could you send it to me ?
Comment 11 Sébastien Granjoux 2009-11-15 10:08:09 UTC
I have fixed the problem in the git plugin, so closing bug #601567 which is not a duplicate of this one in this case.

The project manager issue is still here but then I need more information (the project itself or a simplified project which cannot be imported).
Comment 12 Gal Rosen 2009-11-15 10:48:08 UTC
Created attachment 147763 [details]
A tar file of my test repository
Comment 13 Sébastien Granjoux 2009-11-15 11:14:21 UTC
(In reply to comment #12)
> Created an attachment (id=147763) [details]
> A tar file of my test repository

It's quite easy, there is no makefile in your project directory. Perhaps you have forgotten to commit it in git repository.
Comment 14 Gal Rosen 2009-11-15 12:19:08 UTC
(In reply to comment #13)
> (In reply to comment #12)
> > Created an attachment (id=147763) [details] [details]
> > A tar file of my test repository
> 
> It's quite easy, there is no makefile in your project directory. Perhaps you
> have forgotten to commit it in git repository.

So if I have git repository with couple of makefile files but not in the parent directory, what should I do ?
Comment 15 Gal Rosen 2009-11-15 13:50:40 UTC
OK, I guess that I can clone the repository with command line, then when creating the Anjuta project give the path of the Makefile in my repository.

Am I right ?
Comment 16 Sébastien Granjoux 2009-11-15 14:38:46 UTC
(In reply to comment #15)
> OK, I guess that I can clone the repository with command line, then when
> creating the Anjuta project give the path of the Makefile in my repository.
> Am I right ?

Well, you could probably create several anjuta projects, one for each makefile, this way.

The makefile support in Anjuta is rather basic. Currently, Anjuta makefile backend needs a makefile in the project directory. It reads this makefile in order to find all source files of the project.

This could be improved but it will be very very difficult to support any structure using makefiles and I don't really see the interest.
Comment 17 Gal Rosen 2009-11-16 07:17:51 UTC
So I guess that you can close this BUG.