From mboxrd@z Thu Jan 1 00:00:00 1970 From: Glenn Morris Subject: bug#31187: core-updates: url-fetch/tarbomb, url-fetch/zipbomb fail with "unbound variable: invoke" Date: Wed, 18 Apr 2018 17:27:44 -0400 Message-ID: References: <20180416205439.1644149e@centurylink.net> <871sfci9n7.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53047) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f8udT-0006DT-Hy for bug-guix@gnu.org; Wed, 18 Apr 2018 17:29:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f8udS-00069V-LE for bug-guix@gnu.org; Wed, 18 Apr 2018 17:29:03 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:51858) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f8udS-00069K-H5 for bug-guix@gnu.org; Wed, 18 Apr 2018 17:29:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1f8udS-0006JT-8Y for bug-guix@gnu.org; Wed, 18 Apr 2018 17:29:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <871sfci9n7.fsf@netris.org> (Mark H. Weaver's message of "Wed, 18 Apr 2018 15:42:36 -0400") 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.org@gnu.org Sender: "bug-Guix" To: Mark H Weaver Cc: 31187@debbugs.gnu.org, Eric Bavier Mark H Weaver wrote: > (1) This bug is not listed on , although > shows it as an open bug for Guix. There was a problem with the pagination. It's (now) on page 2. > (2) The original bug report was never delivered to me, although I'm > subscribed to . If Eric hadn't CC'd me on his > original submission, I might not have seen it. I would guess that you are subscribed to bug-guix with the "filter out duplicates" Mailman option, so it is precisely because you were cc'd that you did not get the mailing list copy (with the bug number). > I was unable to find out the bug number until I asked Eric directly, > so unfortunately the commit does not reference the bug number. (You could have searched for the bug by subject?) If Eric had used X-Debbugs-CC instead of Cc in the initial report, the mail you got would have included the bug number in the subject. I believe this is well documented (eg on the "how to report a bug" section on https://debbugs.gnu.org/). > I've reported these problems to the FSF sysadmins, and I'd like to give > them an opportunity to diagnose the problem before we change the status > of this bug. The FSF sysadmins don't maintain debbugs.gnu.org, so the help-debbugs list would have been better. I (debbugs.gnu.org maintainer) happened to see your mail although I don't normally read bug-guix.