From: "Girar awaiter (vt)" <girar-builder@altlinux.org>
To: Vitaly Chikunov <vt@altlinux.org>
Cc: sisyphus-incominger@lists.altlinux.org,
girar-builder-p11@altlinux.org,
girar-builder-p11@lists.altlinux.org
Subject: [#406503] p11 EPERM (try 2) liburing.git=2.13-alt1
Date: Wed, 28 Jan 2026 09:46:04 +0000
Message-ID: <girar.task.406503.2.1@gyle.mskdc.altlinux.org> (raw)
In-Reply-To: <girar.task.406503.1.1@gyle.mskdc.altlinux.org>
https://git.altlinux.org/tasks/406503/logs/events.2.1.log
https://packages.altlinux.org/tasks/406503
2026-Jan-28 09:41:57 :: task #406503 for p11 resumed by vt:
2026-Jan-28 09:41:57 :: message: kernel-6.18
#100 build 2.13-alt1 from /people/vt/packages/liburing.git fetched at 2026-Jan-28 09:32:35
2026-Jan-28 09:41:59 :: [i586] #100 liburing.git 2.13-alt1: build start
2026-Jan-28 09:41:59 :: [x86_64] #100 liburing.git 2.13-alt1: build start
2026-Jan-28 09:41:59 :: [aarch64] #100 liburing.git 2.13-alt1: build start
2026-Jan-28 09:42:09 :: [i586] #100 liburing.git 2.13-alt1: build OK (cached)
2026-Jan-28 09:42:10 :: [x86_64] #100 liburing.git 2.13-alt1: build OK (cached)
2026-Jan-28 09:42:16 :: [aarch64] #100 liburing.git 2.13-alt1: build OK (cached)
2026-Jan-28 09:42:17 :: 100: build check OK (cached)
2026-Jan-28 09:42:18 :: build check OK
2026-Jan-28 09:42:26 :: #100: liburing.git 2.13-alt1: version check OK
2026-Jan-28 09:42:27 :: build version check OK
2026-Jan-28 09:42:29 :: noarch check OK
2026-Jan-28 09:42:31 :: plan: src +1 -1 =19989, aarch64 +3 -3 =35242, i586 +3 -3 =34157, x86_64 +3 -3 =36052
#100 liburing 2.6-alt1 -> 2.13-alt1
Thu Dec 18 2025 Vitaly Chikunov <vt@altlinux> 2.13-alt1
- Update to liburing-2.13 (2025-12-12).
Sun Aug 24 2025 Vitaly Chikunov <vt@altlinux> 2.12-alt1
- Update to liburing-2.12 (2025-08-21).
Tue Jun 17 2025 Vitaly Chikunov <vt@altlinux> 2.11-alt1
- Update to liburing-2.11 (2025-06-16).
Fri May 30 2025 Vitaly Chikunov <vt@altlinux> 2.10-alt1
- Update to liburing-2.10 (2025-05-23).
Tue Feb 04 2025 Vitaly Chikunov <vt@altlinux> 2.9-alt1
- Update to liburing-2.9 (2025-02-03).
[...]
2026-Jan-28 09:43:27 :: patched apt indices
2026-Jan-28 09:43:38 :: created next repo
2026-Jan-28 09:43:48 :: duplicate provides check OK
2026-Jan-28 09:44:31 :: dependencies check OK
2026-Jan-28 09:44:32 :: [x86_64 i586 aarch64] no need to repeat ELF symbols check
2026-Jan-28 09:44:32 :: [x86_64 i586 aarch64] ELF symbols check OK
2026-Jan-28 09:44:43 :: [i586] #100 liburing: install check OK (cached)
2026-Jan-28 09:44:44 :: [x86_64] #100 liburing: install check OK (cached)
2026-Jan-28 09:44:47 :: [i586] #100 liburing-debuginfo: install check OK (cached)
2026-Jan-28 09:44:48 :: [x86_64] #100 liburing-debuginfo: install check OK (cached)
2026-Jan-28 09:44:51 :: [aarch64] #100 liburing: install check OK (cached)
2026-Jan-28 09:44:51 :: [i586] #100 liburing-devel: install check OK (cached)
2026-Jan-28 09:44:53 :: [x86_64] #100 liburing-devel: install check OK (cached)
2026-Jan-28 09:44:59 :: [aarch64] #100 liburing-debuginfo: install check OK (cached)
2026-Jan-28 09:45:07 :: [aarch64] #100 liburing-devel: install check OK (cached)
2026-Jan-28 09:45:08 :: [x86_64-i586] plan: #0 +2 -2 =11786
2026-Jan-28 09:45:25 :: [x86_64-i586] generated apt indices
2026-Jan-28 09:45:27 :: [x86_64-i586] created next repo
2026-Jan-28 09:45:38 :: [x86_64-i586] dependencies check OK
2026-Jan-28 09:45:39 :: gears inheritance check OK
2026-Jan-28 09:45:39 :: srpm inheritance check OK
girar-check-perms: access to liburing DENIED for vt: project `liburing' is not listed in the acl file for repository `p11', and the policy for such projects in `p11' is to deny
check-subtask-perms: #100: liburing: needs approvals from members of @maint and @tester groups
2026-Jan-28 09:45:41 :: acl check FAILED
2026-Jan-28 09:45:54 :: created contents_index files
2026-Jan-28 09:46:01 :: created hash files: aarch64 i586 src x86_64-i586 x86_64
2026-Jan-28 09:46:04 :: task #406503 for p11 EPERM
next prev parent reply other threads:[~2026-01-28 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 9:41 [#406503] p11 TESTED liburing.git=2.13-alt1 Girar awaiter (vt)
2026-01-28 9:46 ` Girar awaiter (vt) [this message]
2026-01-28 9:50 ` [#406503] p11 EPERM (try 3) liburing.git=2.13-alt1 Girar awaiter (vt)
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=girar.task.406503.2.1@gyle.mskdc.altlinux.org \
--to=girar-builder@altlinux.org \
--cc=devel@lists.altlinux.org \
--cc=girar-builder-p11@altlinux.org \
--cc=girar-builder-p11@lists.altlinux.org \
--cc=sisyphus-incominger@lists.altlinux.org \
--cc=vt@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 Girar Builder robot reports
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/sisyphus-incominger/0 sisyphus-incominger/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 sisyphus-incominger sisyphus-incominger/ http://lore.altlinux.org/sisyphus-incominger \
sisyphus-incominger@lists.altlinux.org sisyphus-incominger@lists.altlinux.ru sisyphus-incominger@lists.altlinux.com
public-inbox-index sisyphus-incominger
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.sisyphus-incominger
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git