unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 24467@debbugs.gnu.org, SK Kim <tttuuu888@gmail.com>
Subject: bug#24467: 25.1; package
Date: Sun, 25 Sep 2016 00:28:54 +0200	[thread overview]
Message-ID: <87shspdja1.fsf@web.de> (raw)
In-Reply-To: <CAM-tV-8r77n0equ6Keokco62u6s+5ser1m-=iRu1_4Yj3m3h1g@mail.gmail.com> (Noam Postavsky's message of "Mon, 19 Sep 2016 18:01:37 -0400")

Noam Postavsky <npostavs@users.sourceforge.net> writes:

> merge 24467 21703
> quit
>
> On Mon, Sep 19, 2016 at 1:29 AM, SK Kim <tttuuu888@gmail.com> wrote:
> > After i set gnu and mepla for pacakage-archives in my init.el as
> > below,
> >
> > (package-initialize)
> > (setq package-archives
> >     '(("gnu" . "http://elpa.gnu.org/packages/")
> >      ("melpa" . "http://melpa.milkbox.net/packages/")))
> >
> > whenever i start package-list-packages, status of mepla packages is
> > always new.
>
> Seems to be the same as #21703 "25.0.50; package.el: Thousands of new
> packages each day", but I'm not able to reproduce.
>
> I put the above as my init.el in a temporary HOME dir, when I run
> package-list-packages melpa packages are all "available" for me.

Maybe it is different on the first run?

Hmm, anyway, I found out that with

 (package-initialize)
 (setq package-archives
     '(("gnu" . "http://elpa.gnu.org/packages/")
      ("melpa" . "http://melpa.milkbox.net/packages/")))

in my init file I see the issue.  But with

  (setq package-archives
        '(("gnu" . "http://elpa.gnu.org/packages/")
          ("melpa" . "http://melpa.milkbox.net/packages/")))
  (package-initialize)

it seems to be fixed (i.e. the same expressions just transposed).  With
other words, `package-archives' seemingly needs to be set before calling
`package-intialize' (@SK Kim, do you see the same?).

With the first version, after Emacs startup, `package-archive-contents'
only includes the "gnu" packages.  With the second version, it seems to
include "everything" (the list is too long to be printed in reasonable
time).  That variable is used to decide what packages are new.  That's
were the problem seems to come from.

I think the behavior is at least "surprising", a pitfall.


Regards,

Michael.





  reply	other threads:[~2016-09-24 22:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19  5:29 bug#24467: 25.1; package SK Kim
2016-09-19 22:01 ` Noam Postavsky
2016-09-24 22:28   ` Michael Heerdegen [this message]
2016-09-25  2:45     ` npostavs
2016-09-25 13:38       ` Michael Heerdegen
2018-11-03 15:07         ` Stefan Monnier
2019-01-22 22:56           ` Stefan Monnier
2021-08-16 12:26             ` bug#21703: adding package archives after calling package-initialize lists all their packages as "new" Lars Ingebrigtsen
2021-08-17 12:39               ` bug#24467: " Michael Heerdegen

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=87shspdja1.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=24467@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    --cc=tttuuu888@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).