From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Mark Karpov <markkarpov@openmailbox.org>
Cc: 20817@debbugs.gnu.org
Subject: bug#20817: 25.0.50; Problems with upgrading of packages
Date: Thu, 18 Jun 2015 13:50:17 +0100 [thread overview]
Message-ID: <CAAdUY-K8Ze8HUzKi11czu=F829tGL7+B47kA_Btj7kz+BGe88g@mail.gmail.com> (raw)
In-Reply-To: <87r3p9pkvo.fsf@openmailbox.org>
Your melpa address is outdated. Try changing it to melpa.org/packages
2015-06-18 7:54 GMT+01:00 Mark Karpov <markkarpov@openmailbox.org>:
>
> After a recent fix, packages are still unavailable for me, but error
> message has changed to:
>
> error in process filter: peculiar error: 404
>
> I'm sorry that I didn't investigate the problem immediately. Previously,
> it seemed like even when I start Emacs with -Q flag the problem is
> there. Now, when I start it without my configuration file it works fine.
>
> So, there is something in my configuration file that conflicts with the
> recent changes. I have to say that it worked until now, so theoretically
> it should work after the improvements too.
>
> I've found out that this code suffices to break package
> upgrading/displaying (all the stuff is quite trivial):
>
> (setq
> package-selected-packages
> ;; I prefer setting it explicitly, I even filter arguments of
> ;; ‘package-install’ so it never adds anything to this list,
> ;; but that advice doesn't cause the problem
> '(ace-window
> aggressive-indent
> auctex
> avy
> buffer-move
> cider
> common-lisp-snippets
> fix-word
> flycheck
> flycheck-haskell
> ghc
> gitignore-mode
> haskell-mode
> ido-hacks
> ido-ubiquitous
> ido-vertical-mode
> magit
> markdown-mode
> multiple-cursors
> prolog
> rainbow-delimiters
> smartparens
> smex
> solarized-theme
> whole-line-or-region
> yasnippet))
>
> (require 'package)
>
> (add-to-list
> 'package-archives '("melpa" . "http://melpa.milkbox.net/packages/"))
>
> (package-initialize)
>
> (unless package-archive-contents
> (package-refresh-contents))
>
> ;; I know about new function ‘package-install-selected-packages’, but
> ;; I don't like it, it asks questions and I don't remember now, but
> ;; there were other problems with it, so I do install stuff manually
>
> (dolist (package package-selected-packages)
> (unless (package-installed-p package)
> (package-install package)))
>
> You can now build Emacs, evaluate buffer with this code and try it. The
> problem can be further narrowed, I'm sure, but I have no idea what's
> going on under the hood, so you can do it better than me. Tell me if
> this code doesn't reproduce the problem for you.
>
> Also, answering question from the previous email,
> ‘package-refresh-contents’ works fine.
>
>
>
next prev parent reply other threads:[~2015-06-18 12:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 11:55 bug#20817: 25.0.50; Problems with upgrading of packages Mark Karpov
2015-06-17 16:01 ` Artur Malabarba
2015-06-18 6:54 ` Mark Karpov
2015-06-18 12:50 ` Artur Malabarba [this message]
2015-06-18 13:29 ` Mark Karpov
2015-06-18 13:31 ` bruce.connor.am
2015-06-18 13:51 ` Mark Karpov
2015-06-18 14:05 ` bruce.connor.am
2015-06-18 14:21 ` Mark Karpov
2015-06-18 15:07 ` Artur Malabarba
2015-06-18 15:23 ` Mark Karpov
2015-06-18 15:41 ` Artur Malabarba
2015-06-18 15:58 ` Mark Karpov
2015-06-18 17:26 ` Artur Malabarba
2015-06-18 17:34 ` Mark Karpov
2015-06-18 17:59 ` Artur Malabarba
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='CAAdUY-K8Ze8HUzKi11czu=F829tGL7+B47kA_Btj7kz+BGe88g@mail.gmail.com' \
--to=bruce.connor.am@gmail.com \
--cc=20817@debbugs.gnu.org \
--cc=markkarpov@openmailbox.org \
/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).