From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Hunting the culprit package Date: Wed, 31 Aug 2022 08:25:24 -0400 Message-ID: References: <87zgflc6m9.fsf@codeisgreat.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4538"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: Emacs Development Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 31 14:27:52 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oTMox-00013o-UE for ged-emacs-devel@m.gmane-mx.org; Wed, 31 Aug 2022 14:27:52 +0200 Original-Received: from localhost ([::1]:59290 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oTMow-0007TO-EJ for ged-emacs-devel@m.gmane-mx.org; Wed, 31 Aug 2022 08:27:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50356) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oTMmq-0005nL-MW for emacs-devel@gnu.org; Wed, 31 Aug 2022 08:25:41 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:14016) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oTMmn-0004ni-Nz for emacs-devel@gnu.org; Wed, 31 Aug 2022 08:25:39 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id C73E380355; Wed, 31 Aug 2022 08:25:34 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id D5FD48000E; Wed, 31 Aug 2022 08:25:32 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1661948732; bh=IdG6FZiMc8G+b3YTXwdKYWWT7C8NkMBt0p7+DG8IHxQ=; h=From:To:Subject:In-Reply-To:References:Date:From; b=kodtfkCIPjK6w5fYmAxfYhcn99eeCDEPDYakeKUZ+8otfV+IuAV2XZ9S83NtS32Wt XPsv8uODy2RDHSk8SLnoIMMxFOxn9WS86JoXAURgoaM5yehjHAOxVU8Kn7r3H3rU/i 4r2XiBQ9aHbYy890Sq7pKbPtj4EuZAyc06PMNV8jCkzjdE4makTr4Zv85jwRatSOIr dUabd631ZJ81X6542Rw0nl3WfxHLgJsq1PG/dRBbCR6ZJFXndZPEBG0Ca5DQH9aOBT kyrFGLaHIejDJEaA/QW8Hcd/1uurqxLcK1LNA6fMGsJWc2iVixnFo6XPlFAPE8Z8Yb xajbdgNUvsHRg== Original-Received: from pastel (unknown [45.72.195.111]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id B6BB9120796; Wed, 31 Aug 2022 08:25:32 -0400 (EDT) In-Reply-To: <87zgflc6m9.fsf@codeisgreat.org> (Pankaj Jangid's message of "Wed, 31 Aug 2022 11:11:18 +0530") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:294425 Archived-At: > Also, when I install all the packages afresh, then also emacs works fine > i.e. a freshly created ~/.emacs.d/elpa is *not* creating any issue. So > something is wrong in my old ~/.emacs.d/elpa. So I tried to figure out > what is happening in my old ~/.emacs.d/elpa directory. In my experience, the problem in such circumstances is most of the time a file that was miscompiled for some reason. > --8<---------------cut here---------------start------------->8--- > diff -r elpa/dash-20220608.1931/dash-autoloads.el elnew/dash-20220608.1931/dash-autoloads.el > 42c42 > < (fn &optional ARG)" t nil) > --- >> (fn &optional ARG)" t) > 66c66 > < (fn &optional ARG)" t nil) > --- >> (fn &optional ARG)" t) > 69c69 > < This allows Dash symbols to be looked up with \\[info-lookup-symbol]." t nil) > --- >> This allows Dash symbols to be looked up with \\[info-lookup-symbol]." t) Changes to `-autoloads.el` are normal: those files are generated locally during the package's installation, so they can be different depending on the version of Emacs used to install the package. The above differences should have no impact since they just add/remove explicit nil values for optional arguments. > diff -r elpa/yaml-mode-20220104.1503/yaml-mode-pkg.el elnew/yaml-mode-20220104.1503/yaml-mode-pkg.el > 2c2 > < (define-package "yaml-mode" "20220104.1503" "Major mode for editing YAML > files" '((emacs "24.1")) :commit > "535273d5a1eb76999d20afbcf4d9f056d8ffd2da" :authors '(("Yoshiki Kurihara" > . "clouder@gmail.com") ("Marshall T. Vandegrift" > . "llasram@gmail.com")) :maintainer '("Vasilij Schneidermann" > . "mail@vasilij.de") :keywords '("data" "yaml") :url > "https://github.com/yoshiki/yaml-mode") > --- >> (define-package "yaml-mode" "20220104.1503" "Major mode for editing YAML >> files" '((emacs "24.1")) :commit >> "a79d2a7b9281f8c56f461d717b1ba40fc58e22fd" :authors '(("Yoshiki Kurihara" >> . "clouder@gmail.com") ("Marshall T. Vandegrift" >> . "llasram@gmail.com")) :maintainer '("Vasilij Schneidermann" >> . "mail@vasilij.de") :keywords '("data" "yaml") :url >> "https://github.com/yoshiki/yaml-mode") > --8<---------------cut here---------------end--------------->8--- This is not expected: the `-pkg.el` files are not generated locally, they come straight from the tarballs (i.e. they're generated once and for all when the tarball is created). This said, this is a MELPA package and it may be that MELPA re-builds all its tarballs "all the time", so it's possible that the `yaml-mode-20220104.1503` from a month ago holds a different `-pkg.el` than the `yaml-mode-20220104.1503` from today if the scripts used to build that tarball have changed in-between. NOTE: I said "may be", because I don't know whether it's the case or not. On `elpa.(non)gnu.org` tarballs are not *re*built, so for (Non)GNU ELPA packages this should never happen. > Also, if this is not the correct way to approach then how to find which > the old package that was creating the issue. Do the usual debugging from the details of issue itself, walking our way back to its source? Stefan