From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [Attention Maintainer] gdal-2.2.1-1
Date: Sun, 16 Jul 2017 14:50:00 -0000 [thread overview]
Message-ID: <87a844jv0x.fsf@Rainer.invalid> (raw)
In-Reply-To: <fbd46f59-5c90-7094-fa1f-b9391dc5803e@gmail.com> (Marco Atzeri's message of "Sun, 16 Jul 2017 13:26:01 +0200")
Marco Atzeri writes:
> the lack of debuginfo on 32bit was intentional,
> as the bug on binutils made impossible to build it.
[…]
> The package was empty as otherwise calm will comply
> of missing of current version as previous version has it
No, you've provided an empty file, not an empty package. That will make
setup trying to install it each time and fail. An empty tar should
have worked, on the other hand.
> I will upload a version 2 later on.
Thank you.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
prev parent reply other threads:[~2017-07-16 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 8:28 Achim Gratz
2017-07-16 11:26 ` Marco Atzeri
2017-07-16 14:50 ` Achim Gratz [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a844jv0x.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@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).