From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C8466138330 for ; Tue, 30 Aug 2016 07:47:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 96B16E0B52; Tue, 30 Aug 2016 07:47:26 +0000 (UTC) Received: from smarthost03c.mail.zen.net.uk (smarthost03c.mail.zen.net.uk [212.23.1.22]) by pigeon.gentoo.org (Postfix) with ESMTP id 737D0E0B32 for ; Tue, 30 Aug 2016 07:47:24 +0000 (UTC) Received: from [82.69.83.178] (helo=mail.digimed.co.uk) by smarthost03c.mail.zen.net.uk with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1bedlT-0005UM-Aw for gentoo-user@lists.gentoo.org; Tue, 30 Aug 2016 07:47:23 +0000 Received: from digimed.co.uk (fenchurch.digimed.co.uk [192.168.1.6]) by mail.digimed.co.uk (Postfix) with ESMTPA id D8CDA52B28C for ; Tue, 30 Aug 2016 08:47:22 +0100 (BST) Date: Tue, 30 Aug 2016 08:47:22 +0100 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: What's happened to gentoo-sources? Message-ID: <20160830084722.009963a1@digimed.co.uk> In-Reply-To: <20160830083455.739cc9a1@jupiter.sol.kaishome.de> References: <3719941.fjHdSEpZyq@peak> <3696924.CMMy0m93A0@peak> <20160830083455.739cc9a1@jupiter.sol.kaishome.de> Organization: Digital Media Production X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.30; x86_64-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/RA69ey4AwL.ZZaiHre01O9B"; protocol="application/pgp-signature" X-Originating-smarthost03c-IP: [82.69.83.178] Feedback-ID: 82.69.83.178 X-Archives-Salt: 41894782-43df-4758-8c1f-efc9705ca4b0 X-Archives-Hash: 52f59e3ff118f33b2d5d5e7c85466a40 --Sig_/RA69ey4AwL.ZZaiHre01O9B Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 30 Aug 2016 08:34:55 +0200, Kai Krakow wrote: > Surprise surprise, 4.7 has this (still not fully fixed) oom-killer bug. > When I'm running virtual machines, it still kicks in. I wanted to stay > on 4.6.x until 4.8 is released, and only then switch to 4.7. Now I was > forced early (I'm using btrfs), and was instantly punished by doing so: No one forced you to do anything. You 4.6 kernel was still in boot, your 4.6 sources were still installed. The ebuild was only removed fro the portage tree, nothing was uninstalled from your system unless you did it. Even the ebuild was still on your computer in /var/db/pkg. --=20 Neil Bothwick The cow is nothing but a machine which makes grass fit for us people to eat. --Sig_/RA69ey4AwL.ZZaiHre01O9B Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iEUEARECAAYFAlfFOgoACgkQum4al0N1GQMr5ACYp40HS33bdL+7ymuEh7oBYTsA sQCePZ9yLWVqv+y2PTWDPwW5LmNKWck= =BbBM -----END PGP SIGNATURE----- --Sig_/RA69ey4AwL.ZZaiHre01O9B--