help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Package installation broken in all repos with package unavailable


From: Pablo Wolter
Subject: Re: Package installation broken in all repos with package unavailable
Date: Thu, 10 Jun 2021 13:43:00 -0700

I have refactored my confit file using (use package <package> blah blah ...
) and it is working now, except some packages that it couldn't find (themes
that I installed manually (?) maybe).

Thanks!
Pablo.

On Thu, Jun 10, 2021 at 09:50 Pablo Wolter <pwolter@gmail.com> wrote:

> I am having the same results with  (add-to-list 'package-archives
> '("melpa" . "https://melpa.org/packages/";))
>
> So I don't know what is wrong ... if I remove it completely how I should
> do it?
>
> Thsi is the reevant part of my .emacs.d/init.el:
>
> ;; .emacs.d/init.el
> ;; Enables basic packaging support
>
> (require 'package)
>
> ;; Adds the Melpa archive to the list of available repositories
> (add-to-list 'package-archives '(
>              ("melpa" . "http://melpa.milkbox.net/packages/";)
>              ("org" . "http://orgmode.org/elpa/";)
>              ("elpa" . "http://elpa.gnu.org/packages/";)))
>
> ;; Initializes the package infrastructure
> (package-initialize)
>
> ;; If there are no archived package contents, refresh them
> (when (not package-archive-contents)
>   (package-refresh-contents))
>
> (package-refresh-contents)
>
> ;; Installs packages
> ;; myPackages contains a list of package names
> (defvar myPackages
>   '(
>     tron-legacy-theme               ;; Tron legacy theme
>     elpy                            ;; Emacs List Python Environment
>     flycheck                        ;; On the fly sintax check
>     blacken                         ;; Black formatting on save
>     ein                             ;; Emacs IPython Notebook
>     magit                           ;; Git integration
>     markdown-mode                   ;; Markdown mode suport
>     better-defaults                 ;; Set up some better Emacs defaults
>     counsel                         ;; Ivy, swiper and counsel
>     doom-modeline                   ;; Doom modeline-mode
>     which-key                       ;; Options for keys
>    ;; The following packages are now failing to install, the ones above
> this line installed ok some days ago
>     rainbow-delimiters              ;; Rainbow delimiters
>     ivy-rich                        ;; Ivy rich
>     helpful                         ;; Helpful (?)
>     projectile                      ;; project managment
>     )
> )
>
> ;; Scans the list in myPackages
> ;; If the package listed is not already installed, install it
> (mapc #'(lambda (package)
>           (unless (package-installed-p package)
>             (package-install package)))
>       myPackages)
>
>
> *Saludos,*
>
>
>
> *Pablo Wolterpwolter@gmail.com <pwolter@gmail.com>*
>
>
> On Thu, Jun 10, 2021 at 6:58 AM Stefan Monnier via Users list for the GNU
> Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
>> >> (setq package-archives '(("ELPA" . "http://tromey.com/elpa/";)
>> >>                           ("gnu" . "http://elpa.gnu.org/packages/";)
>> >>                           ("melpa" . "
>> http://melpa.milkbox.net/packages/";))
>> >> t)
>> >
>> > MELPA's address is "https://melpa.org/packages/"; now and, if i'm not
>> > mistaken,
>>
>> And Tom Tromey's archive is not in use any more.
>>
>> > GNU ELPA requires https to be used (at least that's the
>> > default with an empty init file).
>>
>> No, the `http` address is fine (and shouldn't suffer from the TLS
>> version problems alluded to by someone else).
>>
>> OTOH, the above setting overrides the default, so it hides the new
>> NonGNU archive that is enabled by default in Emacs-28.
>>
>> IOW either don't change `package-archives` at all, or use something like:
>>
>>     (add-to-list 'package-archives '("melpa" . "
>> https://melpa.org/packages/";))
>>
>> which will still give you the "gnu" archive, since it's enabled there by
>> default.
>>
>>
>> -- Stefan
>>
>>
>>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]