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 DA9AA138334 for ; Tue, 29 Oct 2019 16:44:13 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D6452E0856; Tue, 29 Oct 2019 16:44:09 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (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 920B8E0826 for ; Tue, 29 Oct 2019 16:44:09 +0000 (UTC) Received: from katipo2.lan (unknown [203.86.205.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: kentnl) by smtp.gentoo.org (Postfix) with ESMTPSA id 4E09134C54A for ; Tue, 29 Oct 2019 16:44:08 +0000 (UTC) Date: Wed, 30 Oct 2019 05:43:59 +1300 From: Kent Fredric To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [PATCH 2/3] virtual/cargo: drop virtual Message-ID: <20191030054359.2105bd89@katipo2.lan> In-Reply-To: <20191028153440.GA15356@whubbs1.dev.av1.gaikai.org> References: <20191025220340.2715-3-gyakovlev@gentoo.org> <20191026165918.104a631e@katipo2.lan> <4f83359a01c27e3c4afeb6b69a127cccb43b59ad.camel@gentoo.org> <20191026223555.GA16818@linux1.home> <30114cca-2851-4c22-31f6-575eb851ac88@veremit.xyz> <20191026235511.GB16818@linux1.home> <20191027203647.2b1b10ed@katipo2.lan> <20191027170502.GA19730@linux1.home> <20191028101817.19b43ed9@katipo2.lan> <20191028153440.GA15356@whubbs1.dev.av1.gaikai.org> Organization: Gentoo X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-pc-linux-gnu) 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/E_5yWYB9CgbS=8pK2cASkbW"; protocol="application/pgp-signature"; micalg=pgp-sha256 X-Archives-Salt: b81b1436-5226-469b-b02d-5b87208b9fa4 X-Archives-Hash: 0ae3e314b2ad0c68c509dee2e0a20426 --Sig_/E_5yWYB9CgbS=8pK2cASkbW Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 28 Oct 2019 10:34:40 -0500 William Hubbs wrote: > Let's go ahead and do the change and file bugs against portage if there > are issues. Any time I find something that I'd imagine portage could fix, I file a bug. But I already have so many open bugs for things portage does wrong that have been languishing for years, that I have to revert to the "assume portage just wont do the right thing" mentality. I'm literally tired of filing these kind of bugs, and tired of having to spoon-feed users in #gentoo with workarounds to get their systems working. Progress here on the problems I see seems *glacial*. --Sig_/E_5yWYB9CgbS=8pK2cASkbW Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEgdrME8Lrmai3DXYJda6SGagVg7UFAl24bE8ACgkQda6SGagV g7VBgg/+MKIIaFGF3wpOkT1YiLv480UKaX2kh8l3RuGXX3gcfFrSTDxMyhcORpPt EoZmHz1IZO2JZ57w4MIPgwgpkObdqmGaxYZz1MJsMxRlV7Y4X9oyaeHTOjSu0Q4r UwzxyQIw3UFvxUQ6rd99D2jeYyDhQNpKQFcpQYFV/dAFriz9T1ZReUc3crv9OvAi 2dwjaNCVYPj9ljpf+7i0ZW6m6xJ1v+dqRJs78wbdVp38QxOA8AOVzSiQVNPBmaIn zYZcgREd3J0KSUoaZaWAwGQ//jfARG8dr3bbxO8plemtYqsEwAbDDHRfJRcRJ8iq iBZymKY/qF563O/12T8FlTGyDqHe9R0/VRVKKiTMnI1c2itCu4iXusQaOWzxa2ZO jAZ9T9rSv9exbJZvpaMRFnUm1BUGMV1GcgP6fc4L4ZPHsocfGjeX/nnccxsToCbO VyLM94b9kzyGub8gR2hlDCtBsGepsTAwTjItSwhyiW/kF8+5mzd0JOYauBSLgczT WWgeg/JSDL8euzFsVWc2Cmj+ruDsguTodEd8IetsLiYJHW1mvT5l0bghw7dOKFof 6SYlc+md7ebuixn5TWY+pjj6MDzgFaT1lj8A6Y5TmG8tkaZGL2TrWgq5RHEzURq6 RlfEEoRVTrFRiGTNy0WzpGlDo+HkWEZG7gnF8W3QgEbp/gnjrWc= =afyR -----END PGP SIGNATURE----- --Sig_/E_5yWYB9CgbS=8pK2cASkbW--