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 1F6A4138247 for ; Sun, 3 Nov 2013 07:54:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C26B5E0B3E; Sun, 3 Nov 2013 07:54:27 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D2C27E086E for ; Sun, 3 Nov 2013 07:54:26 +0000 (UTC) Received: from [IPv6:2a01:4f8:191:22ca::2:1000] (vpn-c0.not-your-server.de [IPv6:2a01:4f8:191:22ca::2:1000]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ercpe) by smtp.gentoo.org (Postfix) with ESMTPSA id 7DCC533F09D; Sun, 3 Nov 2013 07:54:25 +0000 (UTC) Message-ID: <5276012E.6080006@gentoo.org> Date: Sun, 03 Nov 2013 08:54:22 +0100 From: Johann Schmitz User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec References: <5274FB3D.8080508@gentoo.org> <20131102145126.3c1f6cd7@TOMWIJ-GENTOO> <20131102160330.0e6eaa5e@gentoo.org> <52755089.6090808@gentoo.org> <20131102213530.24388cda@gentoo.org> <52756723.9090300@gentoo.org> In-Reply-To: X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 456b95b6-8f2c-44dc-a569-a6aa9c35b44d X-Archives-Hash: d073cbc86a5911220d3c64109f07d750 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I do not believe we have discovered any useful pattern, other than > that is seems to happen more frequently with people who do not run > full world updates. I don't think that running a world update should be valid solution to solve blocking issues. At work, we have some servers with pretty ancient package-sets because with newer versions third party apps are broken. I bump parts of the systems where it's neccessary and leave the rest alone. As a result i have to deal with all kinds of strange blockers or blockers which i haven't seen for years. I'm strongly against this, but it is how it is. So i have to totally agree with mgorny on > I was considering writing a news item for it but we discussed it on > IRC and decided that users are really expected to be able to > handle themselves, especially wrt to: > > 1. using 'emerge -Du @world' to upgrade their systems, > > 2. reading the blocker output to see that it states > ' which suggests: what if I > upgrade to 10000? > Gentoo isn't a click-and-play distribution. I totally prefer automatic blocker resolution (as nearly all blockers can nowadays), but if something can't be solved automatically, everyone should be able to fix this manually. As long as it doesn't happen every week, i don't think that it's such a big thing. >>>> Autobuilds break, gentoo can't be installed, the distro dies. >>>> I know, sounds like I'm making something out of nothing but >>>> every time people look at the stages and notice they are >>>> months out of date we find another blog post announcing how >>>> gentoo is dead. I totally understand your point, but if i throw "gentoo python-exec blocker" into google, the second hit is this thread and the first post has the solution. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSdgEuAAoJEKCEBkJ3xQHtPH0H/0jZYUgYW1RB2LhSVM67dm+4 5Y76A5APck+cEnDcFBH7S5CQe93yeGwGWmgzBas8A3mvgI80d/IR1x/1iAVjZ9mW zjtC3gNGjkrqo8ciIOZUIQY4+iA+8XDtTezYGBdGn2H+LZGoqjycwT05Vf8+R06D CnlL9wyIVaY6VoA0QTSCez0EBd6Pnf7SxVwQHUwI/wt1fi4/hu8NkjFMC6QxLNQh oBCtI3P/akHrBs8GdZwaXqFTkGRdLUEF0BNljJS4TSg7mum3ZcoU2WgRj8DYL8Ty /wQX9JERjYb6hU5F6aXrJglUpJ5DKE7KESI6oDOK7DmxORMfndke1i8AKlXaKV8= =Dzg9 -----END PGP SIGNATURE-----