From: Kei Kebreau <kei@openmailbox.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add orage.
Date: Mon, 27 Jun 2016 12:45:31 -0400 [thread overview]
Message-ID: <87eg7ieg2c.fsf@openmailbox.org> (raw)
In-Reply-To: <20160627154607.GA22515@jasmine> (Leo Famulari's message of "Mon, 27 Jun 2016 11:46:07 -0400")
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
Leo Famulari <leo@famulari.name> writes:
> On Sun, Jun 26, 2016 at 03:14:06PM -0400, Kei Kebreau wrote:
>> Leo Famulari <leo@famulari.name> writes:
>> > If this issue doesn't break the primary use case of Orage, or cause
>> > problems besides the failure of 'View > Globaltime', then this issue
>> > should not block packaging, in my opinion.
>>
>> So I can push Orage and figure out the issue with globaltime later?
>
> I think so, if it meets the conditions above.
>
> Of course it would be best if it worked. I didn't find the globaltime
> source but according to [0] it is part of Orage. Maybe it would be
> helpful to run Orage with strace and see how it's failing.
>
> [0]
> http://linux.die.net/man/1/globaltime
Interestingly enough, I just built orage on my machine and globaltime
works fine. I'll rebuild it a few more times to make sure that it is
reproducible. If so, it will be pushed later on.
Thank you!
--
Kei (GPG Key: 4096R/E6A5EE3C19467A0D)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2016-06-27 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 5:09 [PATCH] gnu: Add orage Kei Yamashita
2016-05-11 10:03 ` Ricardo Wurmus
2016-05-11 15:34 ` Kei Yamashita
2016-05-23 2:34 ` Leo Famulari
2016-05-23 22:07 ` Kei Kebreau
2016-06-25 17:39 ` Leo Famulari
2016-06-26 19:14 ` Kei Kebreau
2016-06-27 15:46 ` Leo Famulari
2016-06-27 16:45 ` Kei Kebreau [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eg7ieg2c.fsf@openmailbox.org \
--to=kei@openmailbox.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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/guix.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).