From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 8156013877A for ; Mon, 18 Aug 2014 18:16:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 11B65E0BEF; Mon, 18 Aug 2014 18:15:59 +0000 (UTC) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0ED00E0BE2 for ; Mon, 18 Aug 2014 18:15:57 +0000 (UTC) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by gateway1.nyi.internal (Postfix) with ESMTP id 713D3243E2 for ; Mon, 18 Aug 2014 14:15:41 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Mon, 18 Aug 2014 14:15:55 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.co.uk; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; s=mesmtp; bh=n1IKGAHUlPGCDutDfZgNfoJA29A=; b=WGVXazeyD+jcLy01m9mrdZnC07kP avhA6S6U/wVCzOd18L/yCcF9ZyGnWfkpFHysH9z4YH+KNHPAEbj+dk1PPQjKeTGF UFij3GhDufo3LtWb078VqFac+NVCa6ysO6Bj1b/HpmTtJIDUZZnQZEc6K230/HzZ 9csWxEmGyTU4DDI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=n1IKGAHUlPGCDutDfZgNfo JA29A=; b=DrwQuboeGSoJye8Yu1l5ZyeL/ehb75y3dFhl2YVFKMZ5LBtwcIPWzt miQl3RkEt66kuoKXCgy0UugFgV5QsVUXdwFh+lvKj7AMQ32f7SUSd0xzyp2suTw0 6dJxoJ9ADsTJJqf+HMj13QFwk+ExL2lpViQ0jSHHaycfEfw0f63bY= X-Sasl-enc: a6ibfpa5F8EFtxWM4lBFn9tccqMVZwtMOVZVk42q2Z60 1408385741 Received: from [192.168.1.146] (unknown [77.101.146.254]) by mail.messagingengine.com (Postfix) with ESMTPA id 65573C0087C for ; Mon, 18 Aug 2014 14:15:41 -0400 (EDT) Message-ID: <53F242CD.8090907@fastmail.co.uk> Date: Mon, 18 Aug 2014 19:15:41 +0100 From: Kerin Millar User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Changing glibc References: <53F240BB.6050906@taydin.org> In-Reply-To: <53F240BB.6050906@taydin.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 2270f046-8d05-4528-995a-20735f14c319 X-Archives-Hash: e7acc64f97e5ae87e406aca492df167a On 18/08/2014 19:06, Timur Aydin wrote: > Hi, > > I am using a closed source software package on my 64 bit gentoo linux > system. The software package is "beyond compare" by scooter soft. > Because of the way this package is built, it needs a specially patched > version of glibc. I have patched my existing glibc version (2.18) and > have been avoiding updating my glibc since. Now I am wondering whether > the latest update of bcompare will work with the latest glibc (2.19). > > So, if I upgrade to 2.19 and the package doesn't work, how can I go back > to the working, patched 2.18? I know that portage issues the most scary > warnings when you try to downgrade glibc. So what does the community > recommend? > You should be able to downgrade glibc, provided that you haven't built and installed any new packages following the transition from glibc-2.18 to glibc-2.19. That said, I would suggest that you back up the root filesystem as a contingency measure. Still, why not test bcompare in a chroot? The latest stage3 tarball probably includes glibc-2.19 by now. --Kerin