[Digikam-devel] Re: kde:digikam-software-compilation up and working

[Michael G. Hansen]

On 02/22/2011 08:53 PM, Marcel Wiesweg wrote:
> Hi,
>
> the repository kde:digikam-software-compilation repository should now be
> working as we want it. The shipped .gits script has received to small but
> important fixes.
> No more kde:// hack, all repositories will inherit the prefix from the super-
> repo (non-developers will clone from anongit, developers clone from kde: )
>
> It has downloaded and switched branches for me just fine from a clean
> checkout, any testing is welcome.

When I just copy the git URL from projects.kde.org and clone from that, 
download-repos fails:

mike at operator:/c/temp/kde/trunk-src$ git clone 
git://anongit.kde.org/digikam-software-compilation digikam-sc.2
Cloning into digikam-sc.2...
remote: Counting objects: 72, done.
remote: Compressing objects: 100% (37/37), done.
remote: Total 72 (delta 32), reused 64 (delta 28)
Receiving objects: 100% (72/72), 26.53 KiB, done.
Resolving deltas: 100% (32/32), done.
mike at operator:/c/temp/kde/trunk-src$ cd digikam-sc.2/

mike at operator:/c/temp/kde/trunk-src/digikam-sc.2$ ./download-repos
Cloning into core...
fatal: Unable to look up  (port 9418) (Name or service not known)
Could not clone git://anongit.kde.orgdigikam onto core
cd: 5: can't cd to core
cd: 6: can't cd to extra/kipi-plugins
cd: 7: can't cd to extra/libkexiv2
cd: 8: can't cd to extra/libkdcraw

I suggest to check for error conditions after calling gits populate, to 
avoid further cd errors.

But if I download from kde:digikam-software-compilation it works fine:

mike at operator:/c/temp/kde/trunk-src$ git clone 
kde:digikam-software-compilation digikam-sc.2
Cloning into digikam-sc.2...
remote: Counting objects: 72, done.
remote: Compressing objects: 100% (37/37), done.
remote: Total 72 (delta 32), reused 64 (delta 28)
Receiving objects: 100% (72/72), 26.53 KiB, done.
Resolving deltas: 100% (32/32), done.

download-repos works fine, but ends with this:

Branch 2.0 set up to track remote branch development/2.0 from origin.
Switched to a new branch '2.0'
Branch 2.0 set up to track remote branch development/2.0 from origin.
Switched to a new branch '2.0'
Branch 2.0 set up to track remote branch development/2.0 from origin.
Switched to a new branch '2.0'
Branch 2.0 set up to track remote branch development/2.0 from origin.
Switched to a new branch '2.0'

Looks like it once again set up a 2.0 branch as we discussed yesterday 
in private mails...

Michael