From: Sharon Kimble <boudiccas@skimble.plus.com>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Old org.el ending up in current tar packages?
Date: Tue, 29 Aug 2017 10:29:28 +0100 [thread overview]
Message-ID: <87y3q2zpqf.fsf@skimble.plus.com> (raw)
In-Reply-To: <87h8wygwvz.fsf@alphapapa.net> (Adam Porter's message of "Wed, 23 Aug 2017 09:51:44 -0500")
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
Adam Porter <adam@alphapapa.net> writes:
> It seems that org.el in org-20170821.tar is out of date. Sharon Kimble
> noticed that something was wrong, and after much digging, we found that
> org-clock.el has been updated to have calls to
> org-time-string-to-seconds with 2 arguments, but the function definition
> in org.el only takes 1 argument.
>
> This is very strange, because the addition of the extra arg to
> org-time-string-to-seconds was made back on July 7, and that introduced
> a bug which was fixed in org-clock.el on August 5, yet the tarball from
> August 21 has the pre-July 7 org-time-string-to-seconds function.
>
> See
> https://github.com/Fuco1/org-clock-budget/issues/5#issuecomment-324331793
> for more details.
I have just updated to 'org-plus-contrib-20170828' and the original
problem still remains. I am still unable to use 'org-clock-budget'[1]
with the error report of "(wrong-number-of-arguments (1 . 1) 2) in
org-clock-sum", which was the original problem.
Sharon.
[1] https://github.com/Fuco1/org-clock-budget/issues/5
--
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
DrugFacts = https://www.drugfacts.org.uk
Debian 9.0, fluxbox 1.3.5-2, emacs 25.1.1, org-mode 9.0.9
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-08-29 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 14:51 Old org.el ending up in current tar packages? Adam Porter
2017-08-23 17:33 ` Achim Gratz
2017-08-29 9:29 ` Sharon Kimble [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3q2zpqf.fsf@skimble.plus.com \
--to=boudiccas@skimble.plus.com \
--cc=adam@alphapapa.net \
--cc=emacs-orgmode@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/org-mode.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).