[pkg-go] You are not allowed to push code to this project

Tong Sun pkgoyq.xpt at neverbox.com
Fri Jun 15 14:04:48 BST 2018


Thanks for your help, Anthony.

On Fri, Jun 15, 2018 at 3:44 AM Anthony Fok  wrote:

> On Thu, Jun 14, 2018 at 9:49 PM, Tong Sun wrote:
>
> ...
>
 Hmm... maybe you didn't *quite* do your homework after all...  :-/

 1. Didn't you read
> https://people.debian.org/~stapelberg/2015/07/27/dh-make-golang.html,
>      i.e., the first link under Documentation on the
> https://go-team.pages.debian.net home page?


Actually I did. Not once, not twice, but many times.


>  2. Don't you think someone would have fixed dh-make-golang,
>      one of the most used tools for the Debian Go Team, a long time ago,
>      if it were to make a silly mistake like that?
>      你竟然未有证据,就质疑 dh-make-golang 搞错!?你有没有搞错!?
>  3. With hundreds of Go libraries that are already packaged for Debian,
>      didn't you try to look at the previous WNPP ITP requests, say,
>      by googling: ITP golang, and you'd have seen that no one appends
>      the -dev to the subject of the ITP message.
> 这些基本求证的动作,不需要教了吧?下次请做足功课!


Well, aren't you too harsh to new packers like me? Not seeing -dev appended
to the subject of the ITP message on the first page doesn't imply that I
won't find it on the second page. Not seeing it on the second page doesn't
imply that I won't find it on the third page. How far ahead of pages that I
have to flip though that I can be 100% percent sure that there are no -dev
appended to the subject of the ITP message? Wouldn't a simple guideline
help new packers from going through hassles like this?

I'm not challenging the authority of dh-make-golang. On contrary, I'm
trying to be cautions, and trying to do my job well. This is why I want to
read all the material before doing my job, so that I will not be accused of
being too green to do anything.

I don't think such kind of frustration is necessary for new packers. People
are allowed to make mistakes, without being accused, especially when there
is not clear document to follow.

Answer:
>
> Source package name: golang-github-danverbraganza-varcaser
> Binary package name: golang-github-danverbraganza-varcaser-dev
>

Thanks.


> You can see how other packages do it by browsing through the list at
> https://salsa.debian.org/go-team/packages/,
>

Yep, that's what I did to verify.

The good news is: You can fix the bug title of
> https://bugs.debian.org/901583
> Start by reading https://www.debian.org/Bugs/server-control .
> I'll leave that as an exercise for you.


OK, I gave it a try and got this far:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901583

Good enough?

Well, normally, someone wanting to join the Debian Go Packaging Team
> would visit https://salsa.debian.org/go-team and click on the
> [Request Access] button right in the middle, and someone would have
> approved your request within a day.
>

Of all the material that I read, never had I see that before.

Nevertheless, to avoid going back and forth and wasting time, I went
> ahead and added you manually.
>

Thanks Anthony.

I pushed it up, but didn't find the `debian/sid` branch on salsa.debian.org
.
what I'm missing?

$ gbp push --verbose --debian-branch=debian/sid
gbp:debug: ['git', 'rev-parse', '--show-cdup']
gbp:debug: ['git', 'rev-parse', '--is-bare-repository']
gbp:debug: ['git', 'rev-parse', '--git-dir']
gbp:debug: ['git', 'symbolic-ref', 'HEAD']
gbp:debug: ['git', 'show-ref', 'refs/heads/debian/sid']
gbp:debug: ['git', 'config', 'branch.debian/sid.remote']
gbp:debug: ['git', 'tag', '-l', 'debian/0.0_git20151108.ce61ec4-1']
gbp:debug: ['git', 'tag', '-l', 'upstream/0.0_git20151108.ce61ec4']
gbp:debug: ['git', 'rev-parse', '--quiet', '--verify',
'upstream/0.0_git20151108.ce61ec4^{commit}']
gbp:debug: ['git', 'rev-parse', '--quiet', '--verify',
'refs/heads/upstream']
gbp:info: Pushing upstream/0.0_git20151108.ce61ec4 to origin
gbp:debug: ['git', 'push', 'origin', 'tag',
'upstream/0.0_git20151108.ce61ec4']
gbp:info: Pushing refs/heads/upstream to origin:refs/heads/upstream
gbp:debug: ['git', 'push', 'origin',
'refs/heads/upstream:refs/heads/upstream']
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-go-maintainers/attachments/20180615/69e9dd7f/attachment-0001.html>


More information about the Pkg-go-maintainers mailing list