From: Tassilo Horn <tsdh@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: "Clément Pit--Claudel" <clement.pit@gmail.com>,
"Stefan Monnier" <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Why is GNU AUCTeX 11.89.6 not available from ELPA yet?
Date: Mon, 17 Oct 2016 18:39:22 +0200 [thread overview]
Message-ID: <87zim3udz9.fsf@gnu.org> (raw)
In-Reply-To: <871szfyzdo.fsf@gnu.org> (Tassilo Horn's message of "Mon, 17 Oct 2016 13:43:31 +0200")
Tassilo Horn <tsdh@gnu.org> writes:
>>> Could it be that ./auctex/style/bidi.el is missing a copyright
>>> header, which would have broken the ELPA build?
>>
>> Yes, it seems that elpa doesn't build because of that (I already
>> wondered why). Can please somebody have a look and fix the problem?
>
> I'll try to do it this evening. And now I also noticed the mail
> telling us AUCTeX devs about the problem.
Ok, the problem was that the new bidi.el had a slightly wrong Copyright
header. It was
;; Copyright (C) Free Software Foundation
but should have been
;; Copyright (C) 2016 Free Software Foundation, Inc.
I don't know if the missing year or "Inc." caused the problem.
Anyway, when fixing that I also added the missing "Inc." to
multi-prompt.el, and then
$ make externals check_copyrights
failed because the original exception for multi-prompt.el hasn't been
used anymore. So I removed the exception from elpa/copyright_exceptions
(Stefan, I hope that's been ok), and now I hope that I've been faster
than the ELPA release building task.
So I hope that GNU AUCTeX 11.89.6 will be available within a few hours.
Bye,
Tassilo
next prev parent reply other threads:[~2016-10-17 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 17:17 Why is GNU AUCTeX 11.89.6 not available from ELPA yet? Tassilo Horn
2016-10-16 20:37 ` Clément Pit--Claudel
2016-10-17 10:19 ` Michael Heerdegen
2016-10-17 11:43 ` Tassilo Horn
2016-10-17 16:39 ` Tassilo Horn [this message]
2016-10-17 16:53 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zim3udz9.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=clement.pit@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
--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.