From: Mikhail Efremov <sem@altlinux.org>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] [#218713] EPERM (try 6) rpm-build-ruby.git=0.7.2-alt2 ruby-rake.git=12.3.2-alt2 ...
Date: Fri, 18 Jan 2019 11:50:54 +0300
Message-ID: <20190118085054.77bbe921@sem-notebook> (raw)
In-Reply-To: <20190118073631.44aeec31@sem-notebook>
On Fri, 18 Jan 2019 10:36:31 +0300 Mikhail Efremov wrote:
> > girar-check-perms: access to libidn2 DENIED for majioa: does not
> > belong to approved builders list: sem viy @qa libidn2: Operation
> > not permitted
>
> Не знаю про другие пакеты в этом таске, но зачем нужно пересобирать
> libidn2?
> girar-check-perms: access to libidn2 ALLOWED for cas: member of
> approved group libidn2: Update approved by cas
Таск DONE, так зачем нужно было это делать? А то у меня уже желание
убрать @qa из acl своих пакетов.
--
WBR, Mikhail Efremov
next prev parent reply other threads:[~2019-01-18 8:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 7:36 ` Mikhail Efremov
2019-01-18 8:50 ` Mikhail Efremov [this message]
2019-01-18 11:07 ` Dmitry V. Levin
2019-01-18 11:24 ` Anton Farygin
2019-01-18 11:32 ` Michael Shigorin
2019-01-18 11:41 ` Anton Farygin
2019-01-18 11:43 ` Dmitry V. Levin
2019-01-18 11:45 ` Anton Farygin
2019-01-18 12:23 ` [devel] ошибки в "своих/чужих" пакетах и политика ACL (was: [#218713] EPERM (try 6) ...) Michael Shigorin
2019-01-18 12:26 ` [devel] ошибки в "своих/чужих" пакетах и политика ACL Anton Farygin
2019-01-18 23:30 ` [devel] ошибки в "своих/чужих" пакетах и политика ACL (was: [#218713] EPERM (try 6) ...) Dmitry V. Levin
2019-01-19 8:37 ` [devel] [JT] Re: ошибки в "своих/чужих" пакетах и политика ACL Michael Shigorin
2019-01-18 12:49 ` [devel] [#218713] EPERM (try 6) rpm-build-ruby.git=0.7.2-alt2 ruby-rake.git=12.3.2-alt2 Vladimir Lettiev
2019-01-18 15:20 ` Mikhail Efremov
2019-01-18 16:58 ` Anton Farygin
2019-01-18 12:37 ` Andrey Cherepanov
2019-01-18 13:07 ` Anton Farygin
2019-01-18 14:46 ` Anton Farygin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190118085054.77bbe921@sem-notebook \
--to=sem@altlinux.org \
--cc=devel@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git