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 C1A8D138010 for ; Wed, 19 Sep 2012 05:39:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E941821C04E; Wed, 19 Sep 2012 05:39:38 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 84DC921C00D for ; Wed, 19 Sep 2012 05:38:49 +0000 (UTC) Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 018D533C2E1 for ; Wed, 19 Sep 2012 05:38:49 +0000 (UTC) From: Mike Frysinger Organization: wh0rd.org To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: ChangeLog profiles.desc Date: Wed, 19 Sep 2012 01:38:51 -0400 User-Agent: KMail/1.13.7 (Linux/3.5.0; KDE/4.6.5; x86_64; ; ) References: <20120828002311.815E120987@flycatcher.gentoo.org> <201209162206.19807.vapier@gentoo.org> <20120917092250.61d9f75a@gentoo.org> In-Reply-To: <20120917092250.61d9f75a@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: multipart/signed; boundary="nextPart5842337.C5ZS8jpaVK"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201209190138.52053.vapier@gentoo.org> X-Archives-Salt: 702328b0-5649-431d-a958-829a93d7f134 X-Archives-Hash: a130732a6a35891a028f2ac392420a72 --nextPart5842337.C5ZS8jpaVK Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Monday 17 September 2012 08:22:50 Alexis Ballier wrote: > On Sun, 16 Sep 2012 22:06:19 -0400 Mike Frysinger wrote: > > On Sunday 16 September 2012 11:01:00 Alexis Ballier wrote: > > > also, you are missing some bug # for the 'broken deps' part. > > > packages that have gained broken deps when the profile was marked > > > 'dev', or that you committed with your profile.desc locally > > > modified, do not count and are your fault actually... > >=20 > > wrong. if i'm version bumping a package and i see broken amd64-fbsd > > deps, that is not my problem. sounds like i'll simply de-keyword it > > in the future and let someone else pick up the pieces. >=20 > why do you want to treat amd64-fbsd different than other arches ? atm, i see amd64-fbsd as a toy arch that is impacting more negatively than = it=20 is positively. i don't know of anyone using it for real work. it doesn't= =20 have the large KEYWORDS deployment yet to not make it obnoxious for simple= =20 things. > just to make the work of those that want to maintain that arch a pain ? this is why i've kept some arches which are not large in dev profiles -- so= =20 that when a new dep does come up, other devs aren't blocked. i've also=20 communicated in the past that they should feel free to drop the keyword & f= ile=20 a bug later so that they aren't hung up on work they're focusing on. > > do a repoman on the tree. there are multiple packages coming back > > right now with broken amd64-fbsd deps. >=20 > if people do not file bugs and think it's fine to commit packages with > broken deps, or silently dekeyword just because they can like you > suggested in the first paragraph, this will not change anytime soon. >=20 > and no thanks, i wont be doing repoman checks on the tree, i had been > doing this for x86-fbsd, spending hours fixing the mess i could, and had > to re-do it every couple of months because every other dev was > committing packages with broken deps. except amd64-fbsd is no longer just a dev profile like x86-fbsd which means= =20 those broken deps are messing people up. people who had nothing to do with= =20 the breakage in the first place. =2Dmike --nextPart5842337.C5ZS8jpaVK Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQIcBAABAgAGBQJQWVpsAAoJEEFjO5/oN/WBpEkP/20k8bZbC/Eegch4zViwe5ey DTGx4tlAvF7LpKJSOrlts+UThNCx4Jk2C/I/8gQYV8InDdzVfnPGbWGEXaXbAtqT RUq/B8YRJTCyKH0h4cbjAM2HIHUHbXkN2uZkjOw0Gxm0hlB6YIS2woC8dd51EPEC pl4h9gkg4FtyrEQ/CMzve7iJ9UsUHaYuAxc2Zt6zJrYkOqLg3e6uTDnP6ovZIIO9 Oz83VI7S1TzXhK7HQPEugfVkdTJnuuYYwnIGdTt5P8UFtxEQq3o9epOFiO2v4w0R 27aibyrgSjGiit4e/T5odMQfIAyo+VuKyKSrCT8ir5tgN2JlTgriqXOAgcFExRc0 bphm+2xJJw5L+Wsgn3udN/K+Cg2Z7prF6QZQHFrjH8mrODeSmcCn1awnd6VDMgGF 8IEODN6kFBON/2L3VxkK49mJ5b4XFbpst2tjEMEchgMhBwzzYLXmbYuGsNM/Bv7z EHumPssORe/i+4VoO4g3DSYF2QaKL+3peIjMOCbqWBYdXoKji3ckMh2kli9Qt3UP K4CkqYyKtrfU8UcVKqCys4SIx1gMExqSeJQE5olnzNxSYUvXggHsoE5bqrEFW+jq 3rYO7vvIr7HB4KedgyvhpvSSYA23Bd0k74jvYOMUsn16bGvpO26rgACIAk5ACeKX tflbMeU78GzjLXiWv8MB =TJLO -----END PGP SIGNATURE----- --nextPart5842337.C5ZS8jpaVK--