public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: email-3.1.4
Date: Tue, 06 May 2014 15:23:00 -0000	[thread overview]
Message-ID: <20140506152321.GV30918@calimero.vinschen.de> (raw)
In-Reply-To: <trinity-0d6b296b-bed0-477e-a74e-119aa5f53014-1399387783008@3capp-gmx-bs13>

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

On May  6 16:49, axd@gmx-topmail.de wrote:
> On 6 May 2014 15:58, Corinna Vinschen wrote:
> > On May  6 15:40, axd wrote:
> > > On 5 May 2014 11:36, Corinna Vinschen wrote:
> > > > On Apr 21 11:10, axd wrote:
> > > > > The latest "email" on Cygwin is email-3.1.2-2, I get an error similar to this:
> > > > > https://github.com/deanproxy/eMail/issues/7
> > > > > 
> > > > > Meanwhile there is email-3.1.4 available:
> > > > > http://cleancode.org/downloads/email
> > > > > 
> > > > > Is it possible to provide current version? Thank you very much.
> > > > 
> > > > Just uploaded.
> > > 
> > > Thanks, but are you sure you uploaded the correct version?
> > > Now I get 3.1.3, which is newer but I expected 3.1.4
> > > (my problem is not fixed with this version)
> > 
> > The upstream source archive name is email-3.1.4.tar.gz, the directory
> > name in there is email-3.1.3.  I assumed this is just a naming glitch
> > by the upstream maintainer.
> 
> I just figured out that this archive is buggy
> 
>  
> > If you can point me to the fix for this version I will create a new
> > package, but I'm not going to debug this myself.
> 
> Would it be OK for you to get latest version directly from the repository?
> http://cleancode.org/projects/email/repository

I don't know in which state of stability the repo is so I'd prefer an
official upstream source archive.  I contacted the author.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-05-06 15:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 14:49 email-3.1.4 axd
2014-05-06 15:23 ` Corinna Vinschen [this message]
2014-05-16 11:36   ` Aw: email-3.1.4 axd
2014-05-16 11:37     ` Corinna Vinschen
2014-05-16 18:43       ` Corinna Vinschen
2014-05-18 15:17         ` Aw: " axd
2014-05-19  8:10           ` Corinna Vinschen
  -- strict thread matches above, loose matches on Subject: below --
2014-05-06 13:40 email-3.1.4 axd
2014-05-06 13:58 ` email-3.1.4 Corinna Vinschen
2014-04-21  9:10 email-3.1.4 axd
2014-05-05  9:37 ` email-3.1.4 Corinna Vinschen
2014-05-05  9:52 ` email-3.1.4 Corinna Vinschen

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=20140506152321.GV30918@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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.
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).