From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bengt Richter Subject: bug#39949: [core-updates] rust@1.20 fails tests Date: Tue, 31 Mar 2020 23:46:01 +0200 Message-ID: <20200331214601.GA3602@LionPure> References: <87pndplfie.fsf@devup.no> <87a73wvcx8.fsf@devup.no> Reply-To: Bengt Richter Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:43289) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJOit-0007iV-NG for bug-guix@gnu.org; Tue, 31 Mar 2020 17:47:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jJOis-0000IS-NS for bug-guix@gnu.org; Tue, 31 Mar 2020 17:47:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:53836) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jJOir-0000Gq-Oy for bug-guix@gnu.org; Tue, 31 Mar 2020 17:47:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jJOir-0006k0-Mf for bug-guix@gnu.org; Tue, 31 Mar 2020 17:47:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87a73wvcx8.fsf@devup.no> 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: 39949@debbugs.gnu.org, mbakke@fastmail.com Hi Marius, On +2020-03-31 16:04:03 +0200, Marius Bakke wrote: > Marius Bakke writes: > > > 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. > > 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. Are there any general standards for subscribing interest in being notified when a particular package or file gets upgraded/revised/etc in any "distro" your package may be dependent on? [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 :) -- Regards, Bengt Richter