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 0EA60139694 for ; Tue, 25 Jul 2017 14:15:13 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0413BE0DC0; Tue, 25 Jul 2017 14:15:08 +0000 (UTC) Received: from foo.stuge.se (foo.stuge.se [212.116.89.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 6080AE0D43 for ; Tue, 25 Jul 2017 14:15:07 +0000 (UTC) Received: (qmail 18968 invoked by uid 1000); 25 Jul 2017 14:15:03 -0000 Date: Tue, 25 Jul 2017 14:15:03 +0000 From: Peter Stuge To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: [RFC] Future of gentoo's stable and unstable trees: what are your thoughts? Message-ID: <20170725141503.GZ12397@stuge.se> References: <20170724222223.6d359e47@sf> <10267d25-547b-cbe1-7fdd-40200e7bae4b@gentoo.org> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10267d25-547b-cbe1-7fdd-40200e7bae4b@gentoo.org> X-Archives-Salt: e0370bcd-ac70-47ac-ae6a-1620ac78d45f X-Archives-Hash: 3ac683e2c07cd7002e008803580ac4f8 Michael Palimaka wrote: > The 30 day waiting period is useful for smoking out major upstream bugs, > but can't replace stabilisation integration testing. For example, > package foobar may build fine in ~arch but fails in stable because it > needs a newer libbaz. So that's either because of an ebuild bug (incorrect DEPEND) or an upstream bug (e.g. incorrect PKG_CONFIG_CHECK in configure.ac), right? It seems to me that waiting (random()=30) days and then testing against (random()=current-version) libbaz in stable isn't amazing. :) The ebuild bug could be detected automatically for upstreams using configure.ac and maybe also cmake. The upstream bug, well, that's a bit more tricky. I'll try to write a thoughtful response in the other part of this thread later. Gotta run now. Thanks everyone for your insights! //Peter