unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 21925@debbugs.gnu.org
Subject: bug#21925: Additional information for bug report: 21925
Date: Mon, 16 Nov 2015 23:08:03 +0200	[thread overview]
Message-ID: <20151116230803.5b545467@debian-netbook> (raw)
In-Reply-To: <CAEKzfHk24d0jxF1SqnY054T4CSDLpfGVov-KW6Ftp-qGtSEMBw@mail.gmail.com>

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

On Sun, 15 Nov 2015 02:19:24 -0800
Chris Marusich <cmmarusich@gmail.com> wrote:

> Hi,
> 
> I've noticed that I also experience similar failures when I try to
> install certain packages. For example, I cannot install ncurses or
> autoconf:
> 
> marusich@garuda ~$ guix package -i autoconf
> guix package: error: socket: Protocol not supported
> marusich@garuda ~$ guix package -i ncurses
> guix package: error: socket: Protocol not supported
> 
> However, I CAN install python:
> 
> marusich@garuda ~$ guix package -i python
> The following package will be installed:
>    python	3.4.3	/gnu/store/y5x6c38fzrbfl80jxrgjd6py2k88x12a-python-3.4.3
> [... I've omitted the rest of the output ...]
> 
> I've noticed that ncurses and autoconf both use the "mirror://" pseudo
> protocol; perhaps this is somehow related to the problem?
> 
> gnu/packages/ncurses.scm:
> ...
>     (package
>      (name "ncurses")
>      (version "6.0")
>      (source (origin
>               (method url-fetch)
>               (uri (string-append "mirror://gnu/ncurses/ncurses-"
>                                   version ".tar.gz"))
> ...
> gnu/packages/autotools.scm:
> ...
> (define-public autoconf
>   (package
>     (name "autoconf")
>     (version "2.69")
>     (source
>      (origin
>       (method url-fetch)
>       (uri (string-append "mirror://gnu/autoconf/autoconf-"
>                           version ".tar.xz"))
> ...
> 
> However, the python module uses "https://":
> 
> gnu/packages/python.scm
> ...
> (define-public python
>   (package (inherit python-2)
>     (version "3.4.3")
>     (source (origin
>               (method url-fetch)
>               (uri (string-append "https://www.python.org/ftp/python/"
>                                   version "/Python-" version ".tar.xz"))
> ...
> 
> If there's any way I can provide more information, please let me know.
> I'm having trouble debugging this any further because I'm just
> starting to learn Guile; no matter what I do I can't seem to make guix
> give me additional information beyond "Protocol not supported."
> 
> I hope this information helps.
> 
> - Chris
> 
> 
> 
copied from the end of your log:

+ guix package --bootstrap -p t-profile-21455 -e '(@@ (gnu packages commencement) gnu-make-boot0)'
accepted connection from pid 21586, user marusich
looking for the latest release of GNU make-boot0...\r                                                   \rguix package: error: socket: Protocol not supported

"looking for latest release" is the automagic checker looking for a new
upstream release of GNU make (i think), and the other two, ncurses and
autoconf, I believe also trip the autochecker to see if there's a new
upstream release.

As to the actual error, I'm not sure

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

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

      parent reply	other threads:[~2015-11-16 21:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-14 20:42 bug#21925: "make check" fails: "guix package: error: socket: Protocol not supported" Chris Marusich
2015-11-15 10:19 ` bug#21925: Additional information for bug report: 21925 Chris Marusich
2015-11-16 16:44   ` Ludovic Courtès
2015-11-17  5:11     ` Chris Marusich
2015-11-17  8:46       ` Ludovic Courtès
2015-11-16 21:08   ` Efraim Flashner [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=20151116230803.5b545467@debian-netbook \
    --to=efraim@flashner.co.il \
    --cc=21925@debbugs.gnu.org \
    --cc=cmmarusich@gmail.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.
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).