From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?QmrDtnJuIEjDtmZsaW5n?= Subject: Re: Policy to remove obsolete packages Date: Tue, 5 Feb 2019 11:24:43 +0100 Message-ID: <20190205112443.41fd031b@alma-ubu> References: <20190204100318.208254da@alma-ubu> <20190204180635.GB8736@jurong> <20190204221804.GA8806@jasmine.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/Pk_6rDalCowqVUqD.BgGcYS"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:60351) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gqxuN-0000cc-2x for guix-devel@gnu.org; Tue, 05 Feb 2019 05:24:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gqxuM-0005qd-4G for guix-devel@gnu.org; Tue, 05 Feb 2019 05:24:51 -0500 Received: from m4s11.vlinux.de ([83.151.27.109]:60008 helo=bjoernhoefling.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gqxuK-0005m7-W4 for guix-devel@gnu.org; Tue, 05 Feb 2019 05:24:49 -0500 In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: zimoun Cc: guix-devel --Sig_/Pk_6rDalCowqVUqD.BgGcYS Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, 5 Feb 2019 00:47:42 +0100 zimoun wrote: > To me the question is more about how to automatically detect that a > patch breaks another package than a policy to remove a broken package. >=20 > I mean if we are able to automatically detect 6 months later that a > package is broken, why are we not able to report the failure earlier? > And if it is not automatic, this means that someone reports the > failure by hand, so somehow this patch is important to them and then > why remove it? 1. To check that A has dependency B and upgrading A breaks B: We discussed on Guix-Days on how to automate this and there are some ideas around, but nothing fully-automated is there yet. Current state: When updating A, developers can call "guix refresh -l" and see which B's are affected and can build them too (if not too much). Also, the build farms are evaluating them eventually and you can manually look up if something went wrong (though this is tedious and errors can slip through). So, no, there currently is no automatic notification/report. Thus, someone does this by hand. If it is a package of interest to that person, they at least write a bug report or have ideas on how to fix it. It could also be a person that has no direct interest or is not an expert for that package. For example, I sometimes just go through the errors of the latest evaluations (https://hydra.gnu.org/evals) and see if anything can be done. Then I notice that it probably broke because of some qt-update, nobody cared, nobody still cares, I'm looking on how to fix it, upstream has no patches since months/years, project was forked, totally restructured etc. If then after a post to the list still nobody shouts up, I find it reasonable to remove the package. Sure the period of 6 months is just a rough notion. Bj=C3=B6rn --Sig_/Pk_6rDalCowqVUqD.BgGcYS Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQiGUP0np8nb5SZM4K/KGy2WT5f/QUCXFlkawAKCRC/KGy2WT5f /eyPAJ9XczB2NaYKyn1QkyQKRjWyB2/RLACbB2o7F5s/pWigJZbg4h/hikjKLxE= =JCOj -----END PGP SIGNATURE----- --Sig_/Pk_6rDalCowqVUqD.BgGcYS--