From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: bug#39949: [core-updates] rust@1.20 fails tests Date: Thu, 02 Apr 2020 21:16:27 +0200 Message-ID: <87d08pr94k.fsf@devup.no> References: <87pndplfie.fsf@devup.no> <87a73wvcx8.fsf@devup.no> <20200331214601.GA3602@LionPure> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:35251) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jK5Kq-0000Pt-9X for bug-guix@gnu.org; Thu, 02 Apr 2020 15:17:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jK5Ko-0008Dd-R0 for bug-guix@gnu.org; Thu, 02 Apr 2020 15:17:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:57479) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jK5Ko-0008DV-NE for bug-guix@gnu.org; Thu, 02 Apr 2020 15:17:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jK5Ko-0006AG-H6 for bug-guix@gnu.org; Thu, 02 Apr 2020 15:17:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20200331214601.GA3602@LionPure> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org Sender: "bug-Guix" To: Bengt Richter , 39949@debbugs.gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Bengt Richter writes: > Hi Marius, > > On +2020-03-31 16:04:03 +0200, Marius Bakke wrote: >> Marius Bakke writes: >>=20 >> > Rust 1.20 fails a test on core-updates, possibly because of the new >> > version of GNU Make (4.3). >> > >> > I suppose we can disable that test for the bootstrap builds as long as >> > it works for the latest version of Rust. >>=20 >> Fixed by giving Rust an earlier version of GNU Make in commit >> 47cd0febe957b698cc2ae28978bdc3bc89e787f9. > > ISTM this kind of "fixed" is not the same as e.g. an upstream upgrade that > "fixes" "the problem" -- so I'm wondering if work-flow-wise > you have a way to tell some upgrade-watching robot to notify you (or your= s/w[1]) > when the inevitable revision to your "fix" should be done. I don't know of any such service, but would probably use it if it exists! Often fixes are already available in upstream repositories, so it's a matter of locating it and checking the log on the file in question. In this case I was too lazy as Rust 1.20 is already ancient and there is work on bootstrapping 1.29 directly in another issue. > Are there any general standards for subscribing interest in being notified > when a particular package or file gets upgraded/revised/etc in any "distr= o" > your package may be dependent on? I do subscribe to a bunch of mailing lists and Atom feeds to get notified of new releases and encourage others to do the same for packages they care about. Pro tip: both GitLab and GitHub offers release feeds on these URLs: https://gitlab.com/project/package/tags?format=3Datom https://github.com/project/package/releases.atom > [1] Is there such a thing as a derivation/service that sits and waits for= such > a notification, and maybe sends you a patch when it does get notified? > > Just curious how the world works :) IME best way to learn how something works is to take part in it! I have learned a whole lot since I got involved with Guix, both personally and professionally, and don't intend to stop any time soon! :-) --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl6GOgsACgkQoqBt8qM6 VPojogf/cUXtno+s00U27mtHJXAJrS4nCgi9W6vVwfHOl8qy6SaE8P0QJ/RfIhwj //xnG5cwfMmjiGi5xdJDaAwi+brh9KgBQKW4gc15RNThm5QtDWU7ekfWFFDd6BPR gO0u8BAEYaEy7bHr+vh1Mw2smV7erlayCuAUGYs2Ha3UcQgd2Rb2qbeOTeT3emCD 41F8b6UJmzAp8rP+25Kj/PAPxTUlFgZEn349Fd+gybqq61i82LZrT50rFP/486L2 7VwGOsIR/YK0EPacQBNk8YyuUAj3dZjTLCOKvrQL4GaXdfmA1g0k2YHTiANWUfTf vVMCE1ywOsL9bK6sK/jTcUHEDW3RmA== =99UU -----END PGP SIGNATURE----- --=-=-=--