From: Philip Kaludercic <philipk@posteo.net>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 59109@debbugs.gnu.org
Subject: bug#59109: 29.0.50; package-tests failing since feature/package+vc merge
Date: Tue, 15 Nov 2022 10:05:46 +0000 [thread overview]
Message-ID: <87bkp8ttvp.fsf@posteo.net> (raw)
In-Reply-To: <87h6z11bao.fsf@posteo.net> (Philip Kaludercic's message of "Mon, 14 Nov 2022 22:22:23 +0100")
Philip Kaludercic <philipk@posteo.net> writes:
> "Basil L. Contovounesios" <contovob@tcd.ie> writes:
>
>> Let me know if you'd like me to run anything else on my end.
>
> For some reason I suddenly keep getting `bad-signature' errors that
> should (?) be unrelated to the actual issue. I suspect that there might
> be some other misconfiguration on my system.
>
> What I was wondering is if you could run git bisect on the history
> between the merge commit and f3e7820b48 to identify where the issues
> appeared?
Scrap that, I figured out what the issue was. package-vc requests
package specifications from "elpa-packages.eld", and I added the file
without adding a signature. I've generated that, and now all the tests
pass. The code is still on scratch/package-vc-fixes, as I am still
awaiting a few people to check if other issues have been resolved. When
that has happened, I'll rebase the changes onto master.
next prev parent reply other threads:[~2022-11-15 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 19:34 bug#59109: 29.0.50; package-tests failing since feature/package+vc merge Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-07 19:42 ` Eli Zaretskii
2022-11-08 18:10 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-08 20:22 ` Philip Kaludercic
2022-11-11 18:21 ` Philip Kaludercic
2022-11-14 21:22 ` Philip Kaludercic
2022-11-15 10:05 ` Philip Kaludercic [this message]
2023-09-15 12:30 ` Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkp8ttvp.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=59109@debbugs.gnu.org \
--cc=contovob@tcd.ie \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).