From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Thu, 19 Mar 2020 04:48:33 +0000 From: QA Team Robot To: sisyphus-cybertalk@lists.altlinux.org Message-ID: <20200319044833.GA28077@gyle.altlinux.org> Mail-Followup-To: sisyphus-cybertalk@lists.altlinux.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [cyber] I: p8/branch packages: +1 (18238) X-BeenThere: sisyphus-cybertalk@lists.altlinux.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: devel@lists.altlinux.org List-Id: ALT Linux Sisyphus cybertalk List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Mar 2020 04:48:33 -0000 Archived-At: List-Archive: 1 UPDATED package chrooted - The chrooted environment helper * Wed Mar 11 2020 Ivan Zakharyaschev 0.3.8-alt1.M80P.1 - 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. This could happen only as a result of actions initiated by root: for example, a package upgrade which included the old version of chrooted, or a package upgrade which included libraries in a system with the old version of chrooted, or an invocation of /sbin/update_chrooted.) * Fri Aug 24 2012 Dmitry V. Levin 0.3.8-alt1 Total 18238 source packages.