all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: 52950@debbugs.gnu.org
Cc: Jonas Bernoulli <jonas@bernoul.li>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#52950: Non-GNU ELPA: make sync no longer pushes
Date: Sun, 2 Jan 2022 09:25:34 -0500	[thread overview]
Message-ID: <CADwFkmk7OONyDFDgjP+4oMb7UycMeqeLg+_-PhJf+0hpLnG1UA@mail.gmail.com> (raw)

The "make sync" step in the Non-GNU ELPA instructions no longer push
to remote.  From nongnu/README.org:

  - Push the package's code to the repository =nongnu.git=:

    #+begin_src sh
      make sync/<pkgname>
    #+end_src

The output of that command is simply:

  $ make sync/toc-org
  emacs --no-site-lisp --batch -l admin/elpa-admin.el -f
elpaa-batch-fetch-and-push "toc-org"
  Fetching updates for toc-org...
  New package toc-org hasn’t been pushed to origin yet

However, no push is carried out AFAICT.

I suspect that this happened with 76c74a11effe (but I might be wrong; I
didn't yet investigate it very closely):

  commit 76c74a11effee3435b43210b673c36eaf0572068
  Author: Jonas Bernoulli <jonas@bernoul.li>
  Date:   Wed Oct 20 01:43:58 2021 +0200

      * elpa-admin.el (elpaa--fetch): Show no log before push to origin

This is not the end of the world, as the autosyncer anyways seems to
synchronize it.  However, it is sort of nice if the person adding the
package is shown on the mailing list instead of the autosyncher.  It
makes it more clear who added a package for future reference.

(I didn't test any of this on GNU ELPA.)





             reply	other threads:[~2022-01-02 14:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-02 14:25 Stefan Kangas [this message]
2022-01-02 18:33 ` bug#52950: Non-GNU ELPA: make sync no longer pushes Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=CADwFkmk7OONyDFDgjP+4oMb7UycMeqeLg+_-PhJf+0hpLnG1UA@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=52950@debbugs.gnu.org \
    --cc=jonas@bernoul.li \
    --cc=monnier@iro.umontreal.ca \
    /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.