From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 34909@debbugs.gnu.org, choroba@matfyz.cz
Subject: bug#34909: 26.1; Error refreshing packages under language environment
Date: Wed, 20 Mar 2019 15:09:38 +0200 [thread overview]
Message-ID: <83tvfxsne5.fsf@gnu.org> (raw)
In-Reply-To: <8736nhaf5a.fsf@gmail.com> (message from Noam Postavsky on Wed, 20 Mar 2019 08:45:05 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 34909@debbugs.gnu.org
> Date: Wed, 20 Mar 2019 08:45:05 -0400
>
> "E. Choroba" <choroba@matfyz.cz> writes:
>
> > Sorry, I noticed the behaviour is a bit different: it still displays
> > the "Bad Signature" error, but it doesn't ask for encoding anymore. So
> > it seems your fix helped a bit, but maybe there's a similar problem in
> > the epg package?
>
> Maybe this is Bug#33825 or Bug#25532/33045?
Could be. But 33825 talks about something that comes and goes,
whereas this present problem doesn't seem to be going anywhere. 25532
sounds like what I fixed, while 33045 is even more strange: it happens
in en_US.UTF-8 locale, where the bug reported here didn't rear its
head...
So I'm still confused. But thanks for bringing this up, it seems to
confirm that some other factor(s) is/are at work here.
next prev parent reply other threads:[~2019-03-20 13:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 21:32 bug#34909: 26.1; Error refreshing packages under language environment E. Choroba
2019-03-19 11:23 ` Eli Zaretskii
2019-03-19 11:57 ` E. Choroba
2019-03-19 12:29 ` Eli Zaretskii
2019-03-19 13:06 ` E. Choroba
2019-03-19 14:32 ` Eli Zaretskii
2019-03-19 14:43 ` Eli Zaretskii
2019-03-19 15:49 ` E. Choroba
2019-03-19 18:34 ` Eli Zaretskii
2019-03-20 7:00 ` Eli Zaretskii
2022-04-12 16:40 ` Lars Ingebrigtsen
2022-04-12 22:52 ` E. Choroba
2022-04-12 23:27 ` Lars Ingebrigtsen
2019-03-20 12:45 ` Noam Postavsky
2019-03-20 13:09 ` Eli Zaretskii [this message]
2019-03-19 16:27 ` Stefan Monnier
2019-03-19 18:44 ` Eli Zaretskii
2019-03-19 19:41 ` Stefan Monnier
2019-03-19 20:00 ` Eli Zaretskii
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=83tvfxsne5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34909@debbugs.gnu.org \
--cc=choroba@matfyz.cz \
--cc=npostavs@gmail.com \
/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).