Hello. Did I miss something here? What would be the next step to submit the
repo https://github.com/Felixoid/golang-github-naegelejd-go-acl to the
created salsa
https://salsa.debian.org/go-team/packages/golang-github-naegelejd-go-acl as
well?

I've created a guest user felixoid-guest and couldn't push into repo
because of lack of permissions:
> GitLab: You are not allowed to push code to this project.

Best regards,
Mikhail.

ср, 8 мая 2019 г. в 14:48, Mikhail f. Shiryaev <mr.felix...@gmail.com>:

> Package: wnpp
> Severity: wishlist
> Owner: Mikhail f. Shiryaev <mr.felix...@gmail.com>
>
> * Package name    : golang-github-naegelejd-go-acl
>   Version         : 0.0~git20160113.f33f861-1
>   Upstream Author : Joseph Naegele
> * URL             : https://github.com/naegelejd/go-acl
> * License         : MIT
>   Programming Lang: Go
>   Description     : Golang POSIX 1e ACL bindings
>
>  go-acl Golang POSIX.1e ACL bindings.  Essentially bindings to
>  /usr/include/sys/acl.h notesmac os x Mac OS X does not seem to support
>  basic POSIX1.e ACLs. They do provide the POSIX API for NFSv4 ACLs. It
>  would be nice for this package to also support NFSv4 ACLs.  freebsd By
>  default, FreeBSD does not enable POSIX1.e ACLs on the root partition. To
>  enable them, reboot into single-user mode and execute: $ tunefs -a enable
>  $ reboot
>  .
>  Source: https://www.freebsd.org/doc/handbook/fs-acl.html info The
>  IEEE POSIX.1e specification describes five security extensions to the
>  base POSIX.1 API: Access Control Lists (ACLs), Auditing, Capabilities,
>  Mandatory Access Control, and Information Flow Labels.  The specificaiton
>  was abandoned before finalization, however most UNIX-like operating
>  systems have some form of ACL implementation.
>  .
>  Source: http://www.gsp.com/cgi-bin/man.cgi?section=3&topic=posix1e
>  copying Copyright (c) 2015 Joseph Naegele. See LICENSE file.
>

Reply via email to