Re: Problem with Git Push

2018-01-05 Thread eamanu15 . 
Hello Gianfranco, My username is @eamanu-guest or my mail
emmanuelaria...@gmail.com.
Thanks for all!!!

Regards

El vie., 5 de ene. de 2018 a la(s) 07:30, Gianfranco Costamagna <
locutusofb...@debian.org> escribió:

> Hello, please give me your salsa username and use that one.
> I'm going to delete the one in collab-maint right now :)
>
> G.
>
>
>
>
> Il Giovedì 4 Gennaio 2018 22:33, eamanu15 . 
> ha scritto:
>
>
>
> Gianfranco,
>
>
>
> >this is a private repo
> >
> >please push there
> >git remote add upstream git+ssh://
> youru...@anonscm.debian.org/git/collab-maint/cligh.git
> >
> >I just created a clone of that repo, and we will need a new unstable
> upload with the new VCS fields in case.
> >
>
> I have this error:
>
> remote: error: insufficient permission for adding an object to repository
> database ./objects
> remote: fatal: failed to write object
> error: unpack failed: unpack-objects abnormal exit
> To git+ssh://anonscm.debian.org/git/collab-maint/cligh.git
>  ! [remote rejected] master -> master (unpacker error)
> error: failed to push some refs to 'git+ssh://
> eamanu-gu...@anonscm.debian.org/git/collab-maint/cligh.git'
>
> What happens? That sound like I don't authorized my ssh-key, but I do.
>
>
> --
>
> Arias Emmanuel
> https://www.linkedin.com/in/emmanuel-arias-437a6a8a
> http://eamanu.com
>


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: Problem with Git Push

2018-01-05 Thread Gianfranco Costamagna 
Hello, please give me your salsa username and use that one.
I'm going to delete the one in collab-maint right now :)

G.




Il Giovedì 4 Gennaio 2018 22:33, eamanu15 .  ha 
scritto:



Gianfranco, 



>this is a private repo
>
>please push there
>git remote add upstream 
>git+ssh://youru...@anonscm.debian.org/git/collab-maint/cligh.git
>
>I just created a clone of that repo, and we will need a new unstable upload 
>with the new VCS fields in case.
>

I have this error:

remote: error: insufficient permission for adding an object to repository 
database ./objects
remote: fatal: failed to write object
error: unpack failed: unpack-objects abnormal exit
To git+ssh://anonscm.debian.org/git/collab-maint/cligh.git
 ! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to 
'git+ssh://eamanu-gu...@anonscm.debian.org/git/collab-maint/cligh.git'

What happens? That sound like I don't authorized my ssh-key, but I do. 


-- 

Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: Problem with Git Push

2018-01-04 Thread eamanu15 . 
Gianfranco,


> this is a private repo
>
> please push there
> git remote add upstream git+ssh://
> youru...@anonscm.debian.org/git/collab-maint/cligh.git
>
> I just created a clone of that repo, and we will need a new unstable
> upload with the new VCS fields in case.
>

I have this error:






*remote: error: insufficient permission for adding an object to repository
database ./objectsremote: fatal: failed to write objecterror: unpack
failed: unpack-objects abnormal exitTo
git+ssh://anonscm.debian.org/git/collab-maint/cligh.git
 ! [remote rejected]
master -> master (unpacker error)error: failed to push some refs to
'git+ssh://eamanu-gu...@anonscm.debian.org/git/collab-maint/cligh.git
'*

What happens? That sound like I don't authorized my ssh-key, but I do.


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: Problem with Git Push

2018-01-04 Thread Ross Gammon 
On 01/04/2018 05:05 PM, Gianfranco Costamagna wrote:
> I don't see any collab-maint on salsa
> 

From salsa announcement:

"Collab-maint


If you want to allow other Debian Developers to work on your packages or
software, you can create projects within the
**Debian** group. Every Debian Developer has write access to projects
created in this group.
If you create a project within the Debian group, you are implicitly
welcoming all DDs to contribute directly to the project.

Guest users can only be added to individual projects with the Debian
group, but not to the entire Debian group. This is different to the
policy for the collab-maint group on Alioth."

> https://salsa.debian.org/debian/cligh

So that URL seems the right place for packages that would have gone in
the old collab-maint on Alioth.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature

Re: Problem with Git Push

2018-01-04 Thread Gianfranco Costamagna 
Hello,

>Are there some chance that the repo of cligh is in Salsa?


I don't see any collab-maint on salsa, and I prefer to wait some more days 
before
migrating to it...
anyhow, created by importing from collab-maint https link
https://salsa.debian.org/debian/cligh

have fun!

G.

El jue., 4 de ene. de 2018 a la(s) 11:01, eamanu15 . 
 escribió:

please push there
>>git remote add upstream 
>>git+ssh://youru...@anonscm.debian.org/git/collab-maint/cligh.git
>>
>>I just created a clone of that repo, and we will need a new unstable upload 
>>with the new VCS fields in case.
>>
>>
>Ok, Thanks!.  I will make this tonight
>
>
>
>Regards!
>
>Emmanuel
>
>
>-- 
>
>Arias Emmanuel
>https://www.linkedin.com/in/emmanuel-arias-437a6a8a
>http://eamanu.com
>
-- 

Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: Problem with Git Push

2018-01-04 Thread eamanu15 . 
Gianfranco,

Are there some chance that the repo of cligh is in Salsa?

El jue., 4 de ene. de 2018 a la(s) 11:01, eamanu15 . <
emmanuelaria...@gmail.com> escribió:

> please push there
>> git remote add upstream git+ssh://
>> youru...@anonscm.debian.org/git/collab-maint/cligh.git
>>
>> I just created a clone of that repo, and we will need a new unstable
>> upload with the new VCS fields in case.
>>
>> Ok, Thanks!.  I will make this tonight
>
>
> Regards!
> Emmanuel
>
>
> --
> Arias Emmanuel
> https://www.linkedin.com/in/emmanuel-arias-437a6a8a
> http://eamanu.com
>
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: Problem with Git Push to git clone git://anonscm.debian.org/user

2018-01-04 Thread Geert Stappers 
On Thu, Jan 04, 2018 at 02:15:25PM +, eamanu15 . wrote:
> Geert Stappers:
> }  Think "website"   all can read, few are allowed to write.
> }the readers are anonym, the writers have identified them self.
> > 
> > This is what I have in  ~/src/pkg-package/.git/config among others lines
> >
> >[remote "origin"]
> > url = https://anonscm.debian.org/git/team/pkg-package.git
> > fetch = +refs/heads/*:refs/remotes/origin/*
> >[remote "alioth"]
> > url = ssh://stapp...@git.debian.org/git/team/pkg-package.git
> > fetch = +refs/heads/*:refs/remotes/alioth/*
> >
>
> Ok, I understand. This is like to run *git remote add alioth [URL]* ?

Where the important part of URL is that it contains an username.


And about Alioth: It has a succesor named Salsa.


Groeten
Geert Stappers
--
Leven en laten leven

Re: Problem with Git Push to git clone git://anonscm.debian.org/user

2018-01-04 Thread eamanu15 . 
This is what I have in  ~/src/pkg-package/.git/config among others lines
>
>[remote "origin"]
> url = https://anonscm.debian.org/git/team/pkg-package.git
> fetch = +refs/heads/*:refs/remotes/origin/*
>[remote "alioth"]
> url = ssh://stapp...@git.debian.org/git/team/pkg-package.git
> fetch = +refs/heads/*:refs/remotes/alioth/*
>

Ok, I understand. This is like to run *git remote add alioth [URL]* ?

>
> `git pull` reads from origin URL
>
> When I want to _write_ I use different path, the alioth URL, I do
>  `git push alioth`
>
>
> Groeten
> Geert Stappers
> --
> Leven en laten leven
>
>

-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: Problem with Git Push

2018-01-04 Thread eamanu15 . 
>
> please push there
> git remote add upstream git+ssh://
> youru...@anonscm.debian.org/git/collab-maint/cligh.git
>
> I just created a clone of that repo, and we will need a new unstable
> upload with the new VCS fields in case.
>
> Ok, Thanks!.  I will make this tonight


Regards!
Emmanuel


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: Problem with Git Push

2018-01-04 Thread Alexander Wirt 
On Thu, 04 Jan 2018, Gianfranco Costamagna wrote:

> Hello,
> 
> 
> >Afterclone, I add the new changes and I try to make a push origin but I have 
> >this error:The requested URL returned error: 403.
> 
> 
> this is a private repo
> 
> please push there
> git remote add upstream 
> git+ssh://youru...@anonscm.debian.org/git/collab-maint/cligh.git
> 
> I just created a clone of that repo, and we will need a new unstable upload 
> with the new VCS fields in case.
Don't use alioth for new packages / repos. Alioth is deprecated.

Re: Problem with Git Push

2018-01-04 Thread Gianfranco Costamagna 
Hello,


>Afterclone, I add the new changes and I try to make a push origin but I have 
>this error:The requested URL returned error: 403.


this is a private repo

please push there
git remote add upstream 
git+ssh://youru...@anonscm.debian.org/git/collab-maint/cligh.git

I just created a clone of that repo, and we will need a new unstable upload 
with the new VCS fields in case.

G.

Re: Problem with Git Push to git clone git://anonscm.debian.org/user

2018-01-04 Thread Geert Stappers 
On Thu, Jan 04, 2018 at 01:43:31PM +0100, Geert Stappers wrote:
> On Thu, Jan 04, 2018 at 01:30:52PM +0100, Geert Stappers wrote:
> > On Thu, Jan 04, 2018 at 11:55:05AM +, eamanu15 . wrote:
> > >...
> > > 
> > > *git clone git://anonscm.debian.org/users/kaction-guest/cligh.git*
> > > After clone, I add the new changes and I try to make a push origin but I
> > > have this error:
> > > 
> > > *The requested URL returned error: 403.*
> > 
> > HTTP & HTTPS use error code 403 to express "forbidden"
> > 
> > 
> > > What is the problem?
> > 
> > My guess is the assumption that read permission implies write permission.
> > 
> > 
> > Add a "write URL" to your  git config
> > 
> 
> At http://losc.nl/Breda/maint.html#_commit_privilege  in dutch a verbose 
> version.
> 
> Some dutch words allready translated
> 
>lezen :   to read
>schrijven :  to write
> 

The thing I'm trying to explain


  Yes, I understand the expection that reading and writing travel the same path.

  Think "website"   all can read, few are allowed write.
the readers are anonym, the writers have identified them self.


Thing that makes it more complicated to come with a solution:

  As Debian Developer I may have privileges that Alioth guest don't have.



This is what I have in  ~/src/pkg-package/.git/config among others lines

   [remote "origin"]
url = https://anonscm.debian.org/git/team/pkg-package.git
fetch = +refs/heads/*:refs/remotes/origin/*
   [remote "alioth"]
url = ssh://stapp...@git.debian.org/git/team/pkg-package.git
fetch = +refs/heads/*:refs/remotes/alioth/*



`git pull` reads from origin URL

When I want to _write_ I use different path, the alioth URL, I do
 `git push alioth`
 

Groeten
Geert Stappers
-- 
Leven en laten leven

Re: Problem with Git Push to git clone git://anonscm.debian.org/user

2018-01-04 Thread Geert Stappers 
On Thu, Jan 04, 2018 at 01:30:52PM +0100, Geert Stappers wrote:
> On Thu, Jan 04, 2018 at 11:55:05AM +, eamanu15 . wrote:
> >...
> > 
> > *git clone git://anonscm.debian.org/users/kaction-guest/cligh.git*
> > After clone, I add the new changes and I try to make a push origin but I
> > have this error:
> > 
> > *The requested URL returned error: 403.*
> 
> HTTP & HTTPS use error code 403 to express "forbidden"
> 
> 
> > What is the problem?
> 
> My guess is the assumption that read permission implies write permission.
> 
> 
> Add a "write URL" to your  git config
> 

At http://losc.nl/Breda/maint.html#_commit_privilege  in dutch a verbose 
version.

Some dutch words allready translated

   lezen :   to read
   schrijven :  to write




Groeten
Geert Stappers
-- 
Leven en laten leven

Re: Problem with Git Push to git clone git://anonscm.debian.org/user

2018-01-04 Thread Geert Stappers 
On Thu, Jan 04, 2018 at 11:55:05AM +, eamanu15 . wrote:
> Dear mentors,
> 
> I am new on debian and I adopt my first package (cligh).
> 
> So, first I upload the new version of the package to mentors.debian (me
> like maintainer) and then was uploaded to the official repository.
> 
> Now, in https://tracker.debian.org/pkg/cligh there is an action need that
> is *The VCS repository is NOT up to date
> , push the missing
> commits. *For this reason, I go to the repository  and do a
> 
> *git clone git://anonscm.debian.org/users/kaction-guest/cligh.git*
> After clone, I add the new changes and I try to make a push origin but I
> have this error:
> 
> *The requested URL returned error: 403.*

HTTP & HTTPS use error code 403 to express "forbidden"


> What is the problem?

My guess is the assumption that read permission implies write permission.


> I have alioth user and Shared CVS / SSH authorized keys.
> 
> Do I need a personal repo? (If this is true, how could I create?)


Add a "write URL" to your  git config



Groeten
Geert Stappers
-- 
Leven en laten leven

Problem with Git Push

2018-01-04 Thread eamanu15 . 
Dear mentors,

I am new on debian and I adopt my first package (cligh).

So, first I upload the new version of the package to mentors.debian (me
like maintainer) and then was uploaded to the official repository.

Now, in https://tracker.debian.org/pkg/cligh there is an action need that
is *The VCS repository is NOT up to date
, push the missing
commits. *For this reason, I go to the repository  and do a

*git clone git://anonscm.debian.org/users/kaction-guest/cligh.git*
After clone, I add the new changes and I try to make a push origin but I
have this error:

*The requested URL returned error: 403.*
What is the problem?

I have alioth user and Shared CVS / SSH authorized keys.

Do I need a personal repo? (If this is true, how could I create?)


Thanks!
Regards!
Emmanuel


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com