bug#22570: 24.5; [debbugs 0.9] encoding issue

bug#22570: 24.5; [debbugs 0.9] encoding issue

[Mark Oteiza]

With debbugs 0.9, doing M-x debbugs-gnu RET results in unknown symbol
spam (see Recent messages: below).

As an example, the first obvious problem I see in the *Emacs Bugs*
buffer is

22549 normal               [Óscar Fuentes      ] 25.0.50; Tooltips placed outside of screen limits

In GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu)
 of 2016-01-24 on svetlemodry
System Description:	Arch Linux

Configured using:
 `configure --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib
 --localstatedir=/var --without-x --without-sound 'CFLAGS=-march=x86-64
 -mtune=generic -O2 -pipe -fstack-protector-strong'
 CPPFLAGS=-D_FORTIFY_SOURCE=2
 LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro'

Important settings:
  value of $LC_COLLATE: C
  value of $LANG: en_US.UTF-8
  locale-coding-system: utf-8-unix

Major mode: Debbugs

Minor modes in effect:
  shell-dirtrack-mode: t
  show-paren-mode: t
  savehist-mode: t
  winner-mode: t
  tooltip-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  buffer-read-only: t
  size-indication-mode: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent messages:
Unknown symbol: ¡
Unknown symbol: ç
Unknown symbol: ©
Unknown symbol: 
Unknown symbol: ä
Unknown symbol: ¸
Unknown symbol: ¹
Unknown symbol: å
Unknown symbol: °
Unknown symbol: ¼
scroll-up-command: End of buffer

bug#22570: 24.5; [debbugs 0.9] encoding issue

[Lars Ingebrigtsen]

Mark Oteiza <mvoteiza@udel.edu> writes:

> With debbugs 0.9, doing M-x debbugs-gnu RET results in unknown symbol
> spam (see Recent messages: below).
>
> As an example, the first obvious problem I see in the *Emacs Bugs*
> buffer is
>
> 22549 normal               [Óscar Fuentes      ] 25.0.50; Tooltips placed outside of screen limits

I think Andreas fixed this in async.el in ELPA.  But perhaps a new
version hasn't been pushed?  What's required to do that?  Just update
the version number?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#22570: 24.5; [debbugs 0.9] encoding issue

[Mark Oteiza]

On 06/02/16 at 04:36pm, Lars Ingebrigtsen wrote:
> Mark Oteiza <mvoteiza@udel.edu> writes:
> 
> > With debbugs 0.9, doing M-x debbugs-gnu RET results in unknown symbol
> > spam (see Recent messages: below).
> >
> > As an example, the first obvious problem I see in the *Emacs Bugs*
> > buffer is
> >
> > 22549 normal               [Óscar Fuentes      ] 25.0.50; Tooltips placed outside of screen limits
> 
> I think Andreas fixed this in async.el in ELPA.  But perhaps a new
> version hasn't been pushed?  What's required to do that?  Just update
> the version number?

Oh, I see--thanks for pointing that out. Alas, I don't know the workings
of ELPA.

bug#22570: 24.5; [debbugs 0.9] encoding issue

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sat, 06 Feb 2016 16:36:05 +1100
> Cc: 22570@debbugs.gnu.org
> 
> Mark Oteiza <mvoteiza@udel.edu> writes:
> 
> > With debbugs 0.9, doing M-x debbugs-gnu RET results in unknown symbol
> > spam (see Recent messages: below).
> >
> > As an example, the first obvious problem I see in the *Emacs Bugs*
> > buffer is
> >
> > 22549 normal               [Óscar Fuentes      ] 25.0.50; Tooltips placed outside of screen limits
> 
> I think Andreas fixed this in async.el in ELPA.  But perhaps a new
> version hasn't been pushed?

It was pushed, see commit 9e186e9 in ELPA.  Maybe Mark is still using
the old version?

bug#22570: 24.5; [debbugs 0.9] encoding issue

[Michael Albinus]

Eli Zaretskii <eliz@gnu.org> writes:

>> > With debbugs 0.9, doing M-x debbugs-gnu RET results in unknown symbol
>> > spam (see Recent messages: below).
>> >
>> > As an example, the first obvious problem I see in the *Emacs Bugs*
>> > buffer is
>> >
>> > 22549 normal [Óscar Fuentes ] 25.0.50; Tooltips placed outside of
>> > screen limits
>> 
>> I think Andreas fixed this in async.el in ELPA.  But perhaps a new
>> version hasn't been pushed?
>
> It was pushed, see commit 9e186e9 in ELPA.  Maybe Mark is still using
> the old version?

There's a problem with a package located on different elpa servers. I've
also updated to async 1.6 from GNU ELPA. But some days later, this was
overwritten by automatic package upgrade with async 20160108.1249 from
melpa, which does not contain the fix of Andreas.

How could I pin async to be updated only from GNU ELPA? And no, I don't
want to remove melpa from package-archives; there are other packages I'm
interested in.

Best regards, Michael.

bug#22570: 24.5; [debbugs 0.9] encoding issue

[Andreas Schwab]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> I think Andreas fixed this in async.el in ELPA.

You also need the fixed soap-client.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

bug#22570: 24.5; [debbugs 0.9] encoding issue

[Eli Zaretskii]

> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>,  mvoteiza@udel.edu,  22570@debbugs.gnu.org
> Date: Sat, 06 Feb 2016 09:55:41 +0100
> 
> How could I pin async to be updated only from GNU ELPA? And no, I don't
> want to remove melpa from package-archives; there are other packages I'm
> interested in.

Take a look at the new features in package.el introduced lately, I
hope some of them will let you do what you want.  (I don't use
package.el, so I cannot give a precise recipe, sorry.)

bug#22570: 24.5; [debbugs 0.9] encoding issue

[Michael Albinus]

Eli Zaretskii <eliz@gnu.org> writes:

>> How could I pin async to be updated only from GNU ELPA? And no, I don't
>> want to remove melpa from package-archives; there are other packages I'm
>> interested in.
>
> Take a look at the new features in package.el introduced lately, I
> hope some of them will let you do what you want.  (I don't use
> package.el, so I cannot give a precise recipe, sorry.)

Adding "gnu" to `package-archive-priorities' does the job. Thanks!

Best regards, Michael.