ALT Linux Girar Builder robot reports
 help / color / mirror / Atom feed
From: Girar Builder pender robot <girar-builder@altlinux.org>
To: Ivan Zakharyaschev <imz@altlinux.org>
Cc: sisyphus-incominger@lists.altlinux.org, girar-builder-p9@altlinux.org
Subject: [#247878] p9 DONE (try 2) chrooted.git=0.3.10-alt1
Date: Tue, 24 Mar 2020 15:08:09 +0000
Message-ID: <20200324150809.GA32129@gyle.altlinux.org> (raw)

http://git.altlinux.org/tasks/archive/done/_242/247878/logs/events.2.1.log

2020-Mar-24 15:04:28 :: task #247878 for p9 resumed by sotor:
2020-Mar-24 15:04:28 :: message: fix_error_in_chrooted_affecting_mainly_running_chrooted_processes
#100 build 0.3.10-alt1 from /gears/c/chrooted.git fetched at 2020-Mar-15 17:48:11
2020-Mar-24 15:04:29 :: [ppc64le] #100 chrooted.git 0.3.10-alt1: build start
2020-Mar-24 15:04:29 :: [i586] #100 chrooted.git 0.3.10-alt1: build start
2020-Mar-24 15:04:29 :: [aarch64] #100 chrooted.git 0.3.10-alt1: build start
2020-Mar-24 15:04:29 :: [x86_64] #100 chrooted.git 0.3.10-alt1: build start
2020-Mar-24 15:04:52 :: [i586] #100 chrooted.git 0.3.10-alt1: build OK
2020-Mar-24 15:04:54 :: [x86_64] #100 chrooted.git 0.3.10-alt1: build OK
2020-Mar-24 15:04:59 :: [ppc64le] #100 chrooted.git 0.3.10-alt1: build OK
2020-Mar-24 15:05:08 :: [aarch64] #100 chrooted.git 0.3.10-alt1: build OK
2020-Mar-24 15:05:16 :: #100: chrooted.git 0.3.10-alt1: build check OK
2020-Mar-24 15:05:16 :: build check OK
2020-Mar-24 15:05:16 :: noarch check OK
2020-Mar-24 15:05:18 :: plan: src +1 -1 =17874, noarch +1 -1 =18637
2020-Mar-24 15:05:18 :: version check OK
#100 chrooted 0.3.9-alt1 -> 0.3.10-alt1
 Wed Mar 11 2020 Ivan Zakharyaschev <imz@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-24 15:05:18 :: chrooted: mentions vulnerabilities: OVE-20200311-0001
2020-Mar-24 15:05:52 :: generated apt indices
2020-Mar-24 15:05:52 :: created next repo
2020-Mar-24 15:06:29 :: dependencies check OK
2020-Mar-24 15:06:43 :: [i586] #100 chrooted: install check OK
2020-Mar-24 15:06:43 :: [x86_64] #100 chrooted: install check OK
2020-Mar-24 15:06:45 :: gears inheritance check OK
2020-Mar-24 15:06:45 :: srpm inheritance check OK
girar-check-perms: access to @maint ALLOWED for cas: member of approved group
girar-check-perms: access to @tester ALLOWED for sotor: member of approved group
check-subtask-perms: #100: chrooted: approved by cas, approved by sotor
2020-Mar-24 15:06:47 :: acl check OK
2020-Mar-24 15:07:31 :: created contents_index files
2020-Mar-24 15:07:40 :: created hash files: noarch src
2020-Mar-24 15:07:42 :: task #247878 for p9 TESTED
2020-Mar-24 15:07:42 :: task is ready for commit
2020-Mar-24 15:07:49 :: repo clone OK
2020-Mar-24 15:07:49 :: packages update OK
2020-Mar-24 15:07:51 :: [noarch] update OK
2020-Mar-24 15:07:51 :: repo update OK
2020-Mar-24 15:08:02 :: repo save OK
2020-Mar-24 15:08:02 :: src index update OK
2020-Mar-24 15:08:02 :: updated /gears/c/chrooted.git branch `p9'
2020-Mar-24 15:08:09 :: gears update OK
2020-Mar-24 15:08:09 :: task #247878 for p9 DONE


                 reply	other threads:[~2020-03-24 15:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200324150809.GA32129@gyle.altlinux.org \
    --to=girar-builder@altlinux.org \
    --cc=girar-builder-p9@altlinux.org \
    --cc=imz@altlinux.org \
    --cc=sisyphus-incominger@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 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