From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JBSvO-0004bA-UM for garchives@archives.gentoo.org; Sun, 06 Jan 2008 10:40:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3E5DDE012F; Sun, 6 Jan 2008 10:40:13 +0000 (UTC) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by pigeon.gentoo.org (Postfix) with ESMTP id D7759E012F for ; Sun, 6 Jan 2008 10:40:12 +0000 (UTC) Received: by ug-out-1314.google.com with SMTP id j3so3431399ugf.49 for ; Sun, 06 Jan 2008 02:40:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:sender; bh=OyvUdRdPjoYQRjhhQEAh+deQXN64sG6GH2R6nKx/sZk=; b=vIabMbhbK1k9boGNELcZMGQbIu1XMXOEdremYq8ONG5obUK2kzXsbmMlnXvAArgv3Dj9CyF5mBPlZsIbsCpdXp9cIUtw8e1Bv3QroXbvI5B0vOEwwPufyvwXdj0PhuKwui75qqfWD+RoA5CJczPcfY8GJiuIlSS8bQYEiWHMuzU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:sender; b=sygI/AX6VVtBnJN3wtPwGAKGSRaMIbucgS+xA0Ocp15nMmZnnT0sOuCaJJ378hFy/SCTjichhVncTICgTbzhXU69ALjmI6s0/6tZo2I6j5LC3OJZVNTj8jRM5FHUsIAM4anR8oOzF480T1iM3w24j7v68eFX7TFgusIONABV6WQ= Received: by 10.67.32.7 with SMTP id k7mr3750318ugj.46.1199616011792; Sun, 06 Jan 2008 02:40:11 -0800 (PST) Received: from ?192.168.1.33? ( [80.86.244.168]) by mx.google.com with ESMTPS id 27sm58829823ugp.19.2008.01.06.02.40.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 06 Jan 2008 02:40:10 -0800 (PST) Subject: Re: [gentoo-dev] Re: Monthly Gentoo Council Reminder for January From: Peter Volkov To: gentoo-dev@lists.gentoo.org In-Reply-To: References: <20080101103002.083C4652C4@smtp.gentoo.org> <54551.192.168.2.159.1199365359.squirrel@www.aei-tech.com> <477D75CA.1030003@gentoo.org> <20080104000155.23e056b4@snowcone> <20080104004653.039f488e@snowcone> <20080104012750.63f4f23a@snowcone> <63044.68.54.223.178.1199445791.squirrel@www.aei-tech.com> <20080104210213.50a99e6b@snowcone> <1199506450.7609.23.camel@inertia.twi-31o2.org> <477FBC0E.2090906@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-JoztaWiBF3uhoB8zL+lo" Date: Sun, 06 Jan 2008 13:40:01 +0300 Message-Id: <1199616001.25565.28.camel@localhost> 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 X-Mailer: Evolution 2.12.2 Sender: Peter Volkov X-Archives-Salt: cc0b6eea-9e2a-4ad1-8413-eadaedba10cf X-Archives-Hash: 8df709da40a58e20d74c0263cead8c28 --=-JoztaWiBF3uhoB8zL+lo Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable =D0=92 =D0=A1=D0=B1=D1=82, 05/01/2008 =D0=B2 18:17 -0600, Ryan Hill =D0=BF= =D0=B8=D1=88=D0=B5=D1=82: > I don't know, I can kinda see both sides. Alt arches tend to be finicky=20 > so it's important that updates are well tested on them. Also they're=20 > more prone to break during upgrades, not only because they're more=20 > fragile but because upstream is far less likely to have tested on them,=20 > so I can see why having a stable tree is important. If this is an issue arch developers should tell us that. Problems with having slacker archs are: open bugs in bugzilla and old ebuilds which are unsupported by maintainer[1]. Open bug just takes my time and attention to open it and to find out that we already fixed that bug and wait for arch to take their action. Old ebuilds they leave me without satisfaction and lie to our users - I know that they are broken, but they are still in the tree and are marked as stable. Open bugs problem can't be solved until we fix problem with old ebuilds because ordinary for broken/old ebuilds I keep herd/myself in CC of bug until it's closed to drop old ebuild from the tree. And for me the problem with old ebuilds could be solved if I could drop keywords from old ebuilds. Then I could remove herd/myself from CC to bug. Also if council decide this way I'd like to see recommendation for slacker arch to drop old ebuild (with none keywords except ~arch) from the tree by themselves as soon as they stabilize new version. [1] And security problem could be solved by labeling arch as security unsupported. --=20 Peter. --=-JoztaWiBF3uhoB8zL+lo Content-Type: application/pgp-signature; name=signature.asc Content-Description: =?UTF-8?Q?=D0=AD=D1=82=D0=B0?= =?UTF-8?Q?_=D1=87=D0=B0=D1=81=D1=82=D1=8C?= =?UTF-8?Q?_=D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D1=8F?= =?UTF-8?Q?_=D0=BF=D0=BE=D0=B4=D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=B0?= =?UTF-8?Q?_=D1=86=D0=B8=D1=84=D1=80=D0=BE=D0=B2=D0=BE=D0=B9?= =?UTF-8?Q?_=D0=BF=D0=BE=D0=B4=D0=BF=D0=B8=D1=81=D1=8C=D1=8E?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQBHgLABz6tlgEWSarMRAqx1AJ46UR/Ym9zwN9J5q0x5hBeP5TxXHwCfaDiR 69esbfpQoBhIFPn2kcpfdok= =SGBt -----END PGP SIGNATURE----- --=-JoztaWiBF3uhoB8zL+lo-- -- gentoo-dev@lists.gentoo.org mailing list