GNU bug report logs -
#68359
Can't pull my channel because of getaddrinfo -8 error
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 68359 in the body.
You can then email your comments to 68359 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#68359
; Package
guix
.
(Wed, 10 Jan 2024 01:11:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
"ShinyZero0" <shinyzero0 <at> tilde.club>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Wed, 10 Jan 2024 01:11:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Here is my channel i'm trying to pull and keep getting that "SERVICE not
supported for `ai_socktype'" error
```
(channel
(name 'zero)
(url "https://codeberg.org/shinyzero0/guix-packages.git")
(commit
"1eacb7d9e2eb96c9d45b96af006b069e443c9ebc"))
```
the full log is
```
(repl-version 0 1 1)
(exception getaddrinfo-error (value -8))
```
It seems to work well on just the previous commit and i also tried some
rebasing/amending to change the "breaking" commit. Sometimes it worked,
but when i added other ones skipping the "breaking" one it throwed the
same error. Of course the channel as well as the package the commit adds
work well in my GUIX_PACKAGE_PATH
There is my `guix describe`:
```
(list (channel
(name 'shepherd)
(url "https://codeberg.org/shinyzero0/shepherd.git")
(branch "main")
(commit
"10d8ad5050799ee91302a5ef7c92a9ba6afd8fa7"))
(channel
(name 'guix)
(url "https://git.savannah.gnu.org/git/guix.git")
(branch "master")
(commit
"08d94fe20eca47b69678b3eced8749dd02c700a4")
(introduction
(make-channel-introduction
"9edb3f66fd807b096b48283debdcddccfea34bad"
(openpgp-fingerprint
"BBB0 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA"))))
(channel
(name 'zero)
(url "https://codeberg.org/shinyzero0/guix-packages.git")
(branch "master")
(commit
"e0d813eb175adb422a6993b173c6a3767957035d"))
(channel
(name 'rde)
(url "https://git.sr.ht/~abcdw/rde")
(branch "master")
(commit
"d0cc15bbc47b8b218e712d1b7fc92fc63527e578")
(introduction
(make-channel-introduction
"257cebd587b66e4d865b3537a9a88cccd7107c95"
(openpgp-fingerprint
"2841 9AC6 5038 7440 C7E9 2FFA 2208 D209 58C1 DEB0")))))
;; warning: GUIX_PACKAGE_PATH="/home/zero/dev/guix-packages"
```
Information forwarded
to
bug-guix <at> gnu.org
:
bug#68359
; Package
guix
.
(Sat, 13 Jan 2024 11:51:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 68359 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi,
"ShinyZero0" <shinyzero0 <at> tilde.club> writes:
> Here is my channel i'm trying to pull and keep getting that "SERVICE not
> supported for `ai_socktype'" error
>
> ```
> (channel
> (name 'zero)
> (url "https://codeberg.org/shinyzero0/guix-packages.git")
> (commit
> "1eacb7d9e2eb96c9d45b96af006b069e443c9ebc"))
> ```
>
> the full log is
>
> ```
> (repl-version 0 1 1)
> (exception getaddrinfo-error (value -8))
> ```
Isn't that rather related to Codeberg being DDoS'd yesterday? Can you
retry now?
Best,
--
Josselin Poiret
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#68359
; Package
guix
.
(Sat, 13 Jan 2024 23:43:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 68359 <at> debbugs.gnu.org (full text, mbox):
Hi, Josselin. Thanks for replying!
Well, actually i encountered the problem at least 20 days ago so it
definitely isn't related to recent DDOS attacks. Even if there were some
before, i could and can build the commit
e0d813eb175adb422a6993b173c6a3767957035d as well as my shepherd channel
which is hosted on codeberg too
Best wishes, Paul
Information forwarded
to
bug-guix <at> gnu.org
:
bug#68359
; Package
guix
.
(Sun, 14 Jan 2024 13:34:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 68359 <at> debbugs.gnu.org (full text, mbox):
Hello again.
I retried the build from codeberg and it still crashes
on any commit above e0d813eb175adb422a6993b173c6a3767957035d.
Also i pushed the repo to github
https://github.com/shinyzero0/guix-packages and it still crashes with
the same error.
Best wishes,
Paul
Information forwarded
to
bug-guix <at> gnu.org
:
bug#68359
; Package
guix
.
(Thu, 18 Jan 2024 02:51:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 68359 <at> debbugs.gnu.org (full text, mbox):
Well, the issue seems to be with the commit that adds the transformed
polybar package like this:
```
(define-module (zero packages polybar))
(use-modules (guix packages)
(guix transformations)
(gnu packages wm))
(define-public
polybar-3.7.1
((options->transformation
'((with-version . "polybar=3.7.1"))) polybar))
```
Information forwarded
to
bug-guix <at> gnu.org
:
bug#68359
; Package
guix
.
(Mon, 11 Mar 2024 14:54:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 68359 <at> debbugs.gnu.org (full text, mbox):
Hi,
On jeu., 18 janv. 2024 at 05:50, "ShinyZero0" via Bug reports for GNU Guix <bug-guix <at> gnu.org> wrote:
> Well, the issue seems to be with the commit that adds the transformed
> polybar package like this:
>
> ```
> (define-module (zero packages polybar))
> (use-modules (guix packages)
> (guix transformations)
> (gnu packages wm))
> (define-public
> polybar-3.7.1
> ((options->transformation
> '((with-version . "polybar=3.7.1"))) polybar))
> ```
Well, the bug seems coming from your channel. Could you update it and
make it compliant with Guix proper.
Somehow, I am going to close this issue because it is not a bug. :-)
Is it fine? Let us know if more details are required.
Cheers,
simon
Information forwarded
to
bug-guix <at> gnu.org
:
bug#68359
; Package
guix
.
(Sun, 14 Apr 2024 10:49:09 GMT)
Full text and
rfc822 format available.
Message #23 received at 68359 <at> debbugs.gnu.org (full text, mbox):
Hi Simon, Paul,
I've also run into this bug and I believe it is due to the error being
cached. This is clearly undesirable so this issue should stay open until
that is resolved.
My reasoning for thinking it is a cache issues is:
- An issue with package transformations should never cause an
getaddrinfo error as Guix generally only goes up to servers for channels
and build packages.
- I ran into this after my gitlab instance had some outage, and
persisted since my server came back up.
- Pulling from a duplicate ref with the same hash succeeds, indicating
that the bug occurs before the checkout is fetched.
I'm happy to have a stab at working on this. Currently working on
reproducing this, it's not as simple as making the channel url point at
a closed port (eg. https://localhost:1212). I even tried binding a SCTP
server to the port, but I just get connection refused. Anyone have any
ideas about this?
Should the title be changed to something like "Guix can cache
getaddrinfo failures on `guix pull`"? (.. on the assumption that I'm
proven right ;-)
I'll assign this to myself, if there are no objections.
Kind regards,
Christina
bug closed, send any further explanations to
68359 <at> debbugs.gnu.org and "ShinyZero0" <shinyzero0 <at> tilde.club>
Request was from
Andreas Enge <andreas <at> enge.fr>
to
control <at> debbugs.gnu.org
.
(Mon, 07 Jul 2025 14:31:03 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 05 Aug 2025 11:24:24 GMT)
Full text and
rfc822 format available.
This bug report was last modified 3 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.