[#247660] EPERM (try 3) chrooted.git=0.3.10-alt1

[Girar Builder awaiter robot]

http://git.altlinux.org/tasks/247660/logs/events.3.1.log

2020-Mar-11 18:06:30 :: task #247660 for sisyphus resumed by imz:
2020-Mar-11 18:06:30 :: message: fix_error_in_chrooted_affecting_mainly_running_chrooted_processes
#100 removed
#200 build 0.3.10-alt1 from /people/imz/packages/chrooted.git fetched at 2020-Mar-11 17:54:44
2020-Mar-11 18:06:31 :: [i586] #200 chrooted.git 0.3.10-alt1: build start
2020-Mar-11 18:06:31 :: [ppc64le] #200 chrooted.git 0.3.10-alt1: build start
2020-Mar-11 18:06:31 :: [aarch64] #200 chrooted.git 0.3.10-alt1: build start
2020-Mar-11 18:06:31 :: [x86_64] #200 chrooted.git 0.3.10-alt1: build start
2020-Mar-11 18:06:41 :: [x86_64] chrooted.git 0.3.10-alt1: remote: no need to rebuild
2020-Mar-11 18:06:41 :: [i586] chrooted.git 0.3.10-alt1: remote: no need to rebuild
2020-Mar-11 18:06:41 :: [i586] #200 chrooted.git 0.3.10-alt1: build OK
2020-Mar-11 18:06:41 :: [x86_64] #200 chrooted.git 0.3.10-alt1: build OK
2020-Mar-11 18:06:42 :: [aarch64] chrooted.git 0.3.10-alt1: remote: no need to rebuild
2020-Mar-11 18:06:42 :: [aarch64] #200 chrooted.git 0.3.10-alt1: build OK
2020-Mar-11 18:06:44 :: [ppc64le] chrooted.git 0.3.10-alt1: remote: no need to rebuild
2020-Mar-11 18:06:44 :: [ppc64le] #200 chrooted.git 0.3.10-alt1: build OK
2020-Mar-11 18:06:52 :: #200: chrooted.git 0.3.10-alt1: build check OK
2020-Mar-11 18:06:52 :: build check OK
2020-Mar-11 18:06:52 :: noarch check OK
2020-Mar-11 18:06:54 :: plan: src +1 -1 =17527, noarch +1 -1 =17688
2020-Mar-11 18:06:54 :: version check OK
#200 chrooted 0.3.9-alt1 -> 0.3.10-alt1
 Wed Mar 11 2020 Ivan Zakharyaschev <imz at altlinux> 0.3.10-alt1
 - Fixes:
   + OVE-20200311-0001 Normal update operations by root can corrupt/crash running processes through modifying libraries
     (Normally, the processes that can be affected are only the services
     already running in the chrooted environment being updated, if it is on
     a different filesystem than the system libraries, and hence they
     can't be hardlinked. Extraordinarily, if a file in a chrooted
     environment has been a hardlink to a system library, but ln hasn't
     succeeded this time for some reason, the affected processes are any
     already running processes system-wide.
 [...]
2020-Mar-11 18:06:54 :: chrooted: mentions vulnerabilities: OVE-20200311-0001
2020-Mar-11 18:07:28 :: generated apt indices
2020-Mar-11 18:07:28 :: created next repo
2020-Mar-11 18:07:59 :: dependencies check OK
2020-Mar-11 18:08:08 :: [i586] #200 chrooted: no need to repeat, install check SKIPPED
2020-Mar-11 18:08:08 :: [x86_64] #200 chrooted: no need to repeat, install check SKIPPED
2020-Mar-11 18:08:11 :: [ppc64le] #200 chrooted: no need to repeat, install check SKIPPED
2020-Mar-11 18:08:11 :: gears inheritance check OK
2020-Mar-11 18:08:11 :: srpm inheritance check OK
girar-check-perms: access to chrooted DENIED for imz: does not belong to approved builders list: ldv 
check-subtask-perms: #200: chrooted: Operation not permitted
2020-Mar-11 18:08:11 :: acl check FAILED
2020-Mar-11 18:08:11 :: task #247660 for sisyphus EPERM