unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Manheimer <ken.manheimer@gmail.com>
To: Daiki Ueno <ueno@gnu.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: ELPA updating properly?
Date: Fri, 22 Jan 2016 13:10:38 -0500	[thread overview]
Message-ID: <CAAT_zTGe0LSxkSR+NgoaZ=i3-LupG6UqBBmqbROtreqgvkP3fg@mail.gmail.com> (raw)
In-Reply-To: <87io2lakhg.fsf-ueno@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

On Fri, Jan 22, 2016 at 7:04 AM, Daiki Ueno <ueno@gnu.org> wrote:

> Ken Manheimer <ken.manheimer@gmail.com> writes:
>
> > Is ELPA failing to update, or am I doing something wrong with my
> > package?
>
> No, it was probably my fault, I'm sorry.  My new package gnome-c-style
> didn't have proper copyright header in the test script and that seems to
> have caused update-archive.sh to exit intermediately:
>
> http://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/admin/update-archive.sh#n70


Ah, ok - thanks for rectifying it.

(It sounds like the archive update process is too sensitive to problems
with individual packages? If I'm understanding correctly, then it should
report problems with a package, and move on to the next, rather than
disrupting the entire process. From only having glanced at the code, that
may require refactoring, and of course it takes someone who has time to do
that...)

Ken

Regards,
> --
> Daiki Ueno
>

[-- Attachment #2: Type: text/html, Size: 1729 bytes --]

  reply	other threads:[~2016-01-22 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21 19:11 ELPA updating properly? Ken Manheimer
2016-01-22 12:04 ` Daiki Ueno
2016-01-22 18:10   ` Ken Manheimer [this message]
2016-01-23  6:14     ` Stefan Monnier

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='CAAT_zTGe0LSxkSR+NgoaZ=i3-LupG6UqBBmqbROtreqgvkP3fg@mail.gmail.com' \
    --to=ken.manheimer@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=ueno@gnu.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).