From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: upset message x86 - libmhash2 ...no "curr" binary?
Date: Thu, 19 Feb 2015 07:55:00 -0000 [thread overview]
Message-ID: <1424332549.3460.42.camel@cygwin.com> (raw)
In-Reply-To: <87y4nutn69.fsf@picasso.cante.net>
On Thu, 2015-02-19 at 08:45 +0200, Jari Aalto wrote:
> I received following while uploading:
>
> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error -
> package steghide requires
> nonexistent package libmhash2
>
> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error -
> package steghide requires
> package libmhash2 which has no "curr" binary
>
> The x86 seems to include libmhash2:
There was actually no libmhash2 on x86 until *after* you tried uploading
steghide and upset complained, which brought to my attention that mhash
(which is orphaned) was behind on x86. I then built and uploaded it,
and so your upload succeeded the next time around.
> What should I do?
You should use cygport to determine runtime dependencies rather than
trying to figure them out yourself.
--
Yaakov
prev parent reply other threads:[~2015-02-19 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 6:45 Jari Aalto
2015-02-19 7:55 ` Yaakov Selkowitz [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=1424332549.3460.42.camel@cygwin.com \
--to=yselkowitz@cygwin.com \
--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).