[riscv-reports] [#68940] sisyphus_riscv64 DONE srpm=sudo-1.9.16p2-alt1.src.rpm
Girar sisyphus_riscv64 pender recycler
noreply at basealt.ru
Sun Jan 5 18:24:44 MSK 2025
http://web.build.srt.basealt.ru/tasks/archive/done/_67/68940/logs/events.1.1.log
subtask name riscv64
#100 sudo 5:47
2025-Jan-05 15:15:40 :: shared task #68940 for sisyphus_riscv64 started by recycler:
2025-Jan-05 15:15:40 :: message: sync_with_sisyphus
#100 build sudo-1.9.16p2-alt1.src.rpm
2025-Jan-05 15:15:46 :: [riscv64] #100 sudo-1.9.16p2-alt1.src.rpm: build start
2025-Jan-05 15:21:33 :: [riscv64] #100 sudo-1.9.16p2-alt1.src.rpm: build OK
2025-Jan-05 15:21:34 :: #100: sudo-1.9.16p2-alt1.src.rpm: build check OK
2025-Jan-05 15:21:34 :: build check OK
2025-Jan-05 15:21:35 :: noarch check OK
2025-Jan-05 15:21:35 :: plan: src +1 -1 =18446, noarch +1 -1 =19925, riscv64 +6 -6 =31446
#100 sudo 1.9.16-alt1 -> 1:1.9.16p2-alt1
Fri Dec 27 2024 Evgeny Sinelnikov <sin at altlinux.org> 1:1.9.16p2-alt1
- Update to latest stable bugfix release:
+ Sudo now passes the terminal device number to the policy plugin even if it
cannot resolve it to a path name (GitHub#421).
+ On Linux systems, sudo will now attempt to use the symbolic links in
/proc/self/fd/{0,1,2} when resolving the terminal device number.
+ Fixed the date used by the exit record in sudo-format log files.
This was a regression introduced in sudo 1.9.16 and only affected
file-based logs, not syslog (GitHub#405).
+ When a duplicate alias is found in the sudoers file, the warning message now
[...]
2025-Jan-05 15:21:55 :: patched apt indices
2025-Jan-05 15:21:57 :: created next repo
2025-Jan-05 15:22:05 :: duplicate provides check OK
2025-Jan-05 15:22:24 :: dependencies check OK
2025-Jan-05 15:22:39 :: [riscv64] ELF symbols check OK
2025-Jan-05 15:23:00 :: [riscv64.0] #100 sudo: install check start
2025-Jan-05 15:23:00 :: [riscv64.1] #100 sudo-devel: install check start
2025-Jan-05 15:23:00 :: [riscv64.2] #100 sudo-logsrvd: install check start
2025-Jan-05 15:23:00 :: [riscv64.3] #100 sudo-python: install check start
2025-Jan-05 15:23:57 :: [riscv64.0] #100 sudo: install check OK
2025-Jan-05 15:23:58 :: [riscv64.2] #100 sudo-logsrvd: install check OK
2025-Jan-05 15:23:58 :: [riscv64.1] #100 sudo-devel: install check OK
2025-Jan-05 15:24:05 :: [riscv64.3] #100 sudo-python: install check OK
2025-Jan-05 15:24:13 :: gears inheritance check OK
2025-Jan-05 15:24:13 :: srpm inheritance check OK
check-subtask-perms: #100: sudo: approved by superuser iv
2025-Jan-05 15:24:13 :: acl check OK
2025-Jan-05 15:24:29 :: created contents_index files
2025-Jan-05 15:24:32 :: created hash files: noarch riscv64 src
2025-Jan-05 15:24:33 :: task #68940 for sisyphus_riscv64 TESTED
2025-Jan-05 15:24:33 :: task is ready for commit
2025-Jan-05 15:24:34 :: repo clone OK
2025-Jan-05 15:24:34 :: packages update OK
2025-Jan-05 15:24:36 :: [riscv64 noarch] update OK
2025-Jan-05 15:24:36 :: repo update OK
2025-Jan-05 15:24:40 :: repo save OK
2025-Jan-05 15:24:40 :: src index update OK
2025-Jan-05 15:24:42 :: created /srpms/s/sudo.git branch `sisyphus_riscv64'
fatal: no tag exactly matches '1ab2dd5381d5c11ecb16144e9f64184a542b06fa'
2025-Jan-05 15:24:44 :: gears update OK
2025-Jan-05 15:24:44 :: task #68940 for sisyphus_riscv64 DONE
More information about the Riscv-reports
mailing list