public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: libsqlite3-devel install uninstalls openssl-devel just to install again??
Date: Mon, 23 Jul 2018 15:45:00 -0000	[thread overview]
Message-ID: <27e6a986-5ac1-3f9f-0cb3-172563b5c99f@gmail.com> (raw)
In-Reply-To: <3e317103-ba6d-05cd-04f4-fb6e4bb52557@gmail.com>

On 7/21/2018 3:51 PM, Marco Atzeri wrote:
> Am 21.07.2018 um 21:22 schrieb Takashi Yano:
>> On Sat, 21 Jul 2018 14:44:57 -0400
>> cyg Simple wrote:
>>> Uninstall openssl-devel 1.0.2o-1 (automatically added)
>>> Install libsqlite3-devel 3.21.0-1
>>> Install openssl-devel 1.0.2o-1
>>
>> I can't reproduce this.
>>
>> $ cygcheck -c openssl-devel
>> Cygwin Package Information
>> Package              Version        Status
>> openssl-devel        1.0.2o-1       OK
>>
>> Then installing libsqlite3-devel says just:
>> Install libsqlite3-devel 3.21.0-1
>>
> 
> that is expected as the only dependency is
> 
>   requires: libsqlite3_0
> 
> Ken's hypothesis is the most likely: setup was asked to
> re-install openssl-devel

No, I did not ask to reinstall openssl-devel, I simply started
setup-x86_64.exe and searched for libsqlite3-devel, selected it for
install then clicked the Next button.  Since others cannot reproduce
this then I'll just leave it as is and take it as a surprise for just me.

-- 
cyg Simple

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2018-07-23 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-21 19:51 cyg Simple
2018-07-21 23:36 ` Ken Brown
2018-07-22  0:38 ` Takashi Yano
2018-07-22  3:25   ` Marco Atzeri
2018-07-23 15:45     ` cyg Simple [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=27e6a986-5ac1-3f9f-0cb3-172563b5c99f@gmail.com \
    --to=cygsimple@gmail.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).