From: "Girar awaiter (vseleznv)" <girar-builder@altlinux.org> To: "Vladimir D. Seleznev" <vseleznv@altlinux.org> Cc: girar-builder-p10@altlinux.org, sisyphus-incominger@lists.altlinux.org, girar-builder-p10@lists.altlinux.org Subject: [#293655] p10 EPERM prosody.git=0.11.12-alt1 Date: Mon, 17 Jan 2022 16:43:47 +0000 Message-ID: <girar.task.293655.1.1@gyle.mskdc.altlinux.org> (raw) https://git.altlinux.org/tasks/293655/logs/events.1.1.log subtask name aarch64 armh i586 ppc64le x86_64 #100 prosody 33 51 23 38 21 2022-Jan-17 16:39:28 :: task #293655 for p10 started by vseleznv: 2022-Jan-17 16:39:28 :: message: Backport CVE-2022-0217 fix #100 build 0.11.12-alt1 from /gears/p/prosody.git fetched at 2022-Jan-17 16:39:26 from sisyphus 2022-Jan-17 16:39:29 :: [aarch64] #100 prosody.git 0.11.12-alt1: build start 2022-Jan-17 16:39:29 :: [ppc64le] #100 prosody.git 0.11.12-alt1: build start 2022-Jan-17 16:39:29 :: [x86_64] #100 prosody.git 0.11.12-alt1: build start 2022-Jan-17 16:39:29 :: [armh] #100 prosody.git 0.11.12-alt1: build start 2022-Jan-17 16:39:29 :: [i586] #100 prosody.git 0.11.12-alt1: build start 2022-Jan-17 16:39:50 :: [x86_64] #100 prosody.git 0.11.12-alt1: build OK 2022-Jan-17 16:39:52 :: [i586] #100 prosody.git 0.11.12-alt1: build OK 2022-Jan-17 16:40:02 :: [aarch64] #100 prosody.git 0.11.12-alt1: build OK 2022-Jan-17 16:40:07 :: [ppc64le] #100 prosody.git 0.11.12-alt1: build OK 2022-Jan-17 16:40:20 :: [armh] #100 prosody.git 0.11.12-alt1: build OK 2022-Jan-17 16:40:33 :: #100: prosody.git 0.11.12-alt1: build check OK 2022-Jan-17 16:40:33 :: build check OK 2022-Jan-17 16:40:35 :: noarch check OK 2022-Jan-17 16:40:37 :: plan: src +1 -1 =17672, aarch64 +2 -2 =29344, armh +2 -2 =27582, i586 +2 -2 =30033, ppc64le +2 -2 =29134, x86_64 +2 -2 =30631 #100 prosody 0.11.10-alt1 -> 0.11.12-alt1 Mon Jan 17 2022 Vladimir D. Seleznev <vseleznv@altlinux> 0.11.12-alt1 - Updated to 0.11.12. 2022-Jan-17 16:41:14 :: patched apt indices 2022-Jan-17 16:41:25 :: created next repo 2022-Jan-17 16:41:32 :: duplicate provides check OK 2022-Jan-17 16:42:04 :: dependencies check OK 2022-Jan-17 16:42:28 :: [x86_64 i586 aarch64 ppc64le armh] ELF symbols check OK 2022-Jan-17 16:42:37 :: [x86_64] #100 prosody: install check OK 2022-Jan-17 16:42:38 :: [i586] #100 prosody: install check OK 2022-Jan-17 16:42:42 :: [x86_64] #100 prosody-debuginfo: install check OK 2022-Jan-17 16:42:42 :: [i586] #100 prosody-debuginfo: install check OK 2022-Jan-17 16:42:45 :: [aarch64] #100 prosody: install check OK 2022-Jan-17 16:42:48 :: [ppc64le] #100 prosody: install check OK 2022-Jan-17 16:42:52 :: [aarch64] #100 prosody-debuginfo: install check OK 2022-Jan-17 16:42:53 :: [armh] #100 prosody: install check OK 2022-Jan-17 16:42:57 :: [ppc64le] #100 prosody-debuginfo: install check OK 2022-Jan-17 16:43:05 :: [armh] #100 prosody-debuginfo: install check OK 2022-Jan-17 16:43:18 :: [x86_64-i586] generated apt indices 2022-Jan-17 16:43:18 :: [x86_64-i586] created next repo 2022-Jan-17 16:43:26 :: [x86_64-i586] dependencies check OK 2022-Jan-17 16:43:27 :: gears inheritance check OK 2022-Jan-17 16:43:27 :: srpm inheritance check OK girar-check-perms: access to prosody DENIED for vseleznv: project `prosody' is not listed in the acl file for repository `p10', and the policy for such projects in `p10' is to deny check-subtask-perms: #100: prosody: needs approvals from members of @maint and @tester groups 2022-Jan-17 16:43:28 :: acl check FAILED 2022-Jan-17 16:43:36 :: created contents_index files 2022-Jan-17 16:43:45 :: created hash files: aarch64 armh i586 ppc64le src x86_64 2022-Jan-17 16:43:47 :: task #293655 for p10 EPERM
next reply other threads:[~2022-01-17 16:43 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-17 16:43 Girar awaiter (vseleznv) [this message] 2022-01-21 19:14 ` [#293655] p10 EPERM (try 2) prosody.git=0.11.12-alt2 Girar awaiter (vseleznv) 2022-01-26 16:41 ` [#293655] p10 DONE (try 3) prosody.git=0.11.12-alt2 Girar pender (amakeenk)
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.293655.1.1@gyle.mskdc.altlinux.org \ --to=girar-builder@altlinux.org \ --cc=devel@lists.altlinux.org \ --cc=girar-builder-p10@altlinux.org \ --cc=girar-builder-p10@lists.altlinux.org \ --cc=sisyphus-incominger@lists.altlinux.org \ --cc=vseleznv@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