all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mvoteiza@udel.edu, Lars Ingebrigtsen <larsi@gnus.org>,
	22570@debbugs.gnu.org
Subject: bug#22570: 24.5; [debbugs 0.9] encoding issue
Date: Sat, 06 Feb 2016 09:55:41 +0100	[thread overview]
Message-ID: <87lh6ykyk2.fsf@gmx.de> (raw)
In-Reply-To: <83fux6tfvx.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 06 Feb 2016 10:14:10 +0200")

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.





  reply	other threads:[~2016-02-06  8:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06  5:25 bug#22570: 24.5; [debbugs 0.9] encoding issue Mark Oteiza
2016-02-06  5:36 ` Lars Ingebrigtsen
2016-02-06  6:28   ` Mark Oteiza
2016-02-06  8:14   ` Eli Zaretskii
2016-02-06  8:55     ` Michael Albinus [this message]
2016-02-06  9:13       ` Eli Zaretskii
2016-02-06 15:19         ` Michael Albinus
2016-02-06  9:02   ` Andreas Schwab

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lh6ykyk2.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=22570@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=mvoteiza@udel.edu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.