[SOLVED] makepkg not working

TySpicer · 2025-09-07 00:57:10

I'm trying to install yay using this guide: https://itsfoss.com/install-yay-arch-linux

I cloned the repository, navigated to the directory, and ran "makepkg -si." It printed out a few lines that make it look like it's working, then printed some errors:

curl (7) Failed to connect to github.com port 443 after 36 ms: Could not connect to server
==> ERROR: Failure while downloading https://github.com/Jguer/yay/archive/v12.5.0.tar.gz
Aborting...

I'm connected to the internet, so I'm not sure what the issue could be. What can I do to figure this out?

Last edited by TySpicer (2025-09-09 14:11:07)

skunktrader · 2025-09-07 01:05:57

Why not do things "the arch way" and install this

TySpicer · 2025-09-07 01:09:43

Sure, I could try that. How do I install it? (Hence, newbie)

skunktrader · 2025-09-07 01:30:03

https://wiki.archlinux.org/title/Arch_User_Repository

TySpicer · 2025-09-07 18:38:32

I tried installing the package you sent, and I'm getting the same error. I made sure to run makepkg -s as well. It looks like it can't connect to github.com.

I'm looking at the troubleshooting section of the makepkg page on the wiki, and I'm not seeing anything that looks like this.

Any ideas as to what could be causing this?

seth · 2025-09-07 18:41:51

ping -c 1 github.com
curl -vL github.com > /dev/null 2>/tmp/curl.log
cat /tmp/curl.log | curl -F 'file=@-' 0x0.st
# edit, speculatively
ip a; ip r
ping -c1 8.8.8.8
ping -c1 _gateway

Last edited by seth (2025-09-07 18:42:29)

TySpicer · 2025-09-07 19:07:52

ping -c 1 github.com

outputs

ping: connect: Network is unreachable

The second command has no output.

cat /tmp/curl.log | curl -F 'file=@-' 0x0.st

outputs

http://0x0.st/Kqc3.txt

ip a; ip r

outputs

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    ...

There are several more lines there, should I type the rest out as well? I can't copy-and-paste from my other computer, so I'll have to type it out manually.

ping -c1 8.8.8.8

outputs

ping: connect: Network is unreachable

The last line looks like it works:

... icmp_seq=1 ttl=64 time=6.92 ms ...

cryptearth · 2025-09-07 19:15:53

TySpicer wrote:

ip a; ip r

outputs

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    ...

please provide the FULL output of that comment
your issue is "network unreachable" after successful dns resolving - so this hints to a routing issue - and for us to help you we need the output of

ip r

something like this

[main@main ~]$ ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp42s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP mode DEFAULT group default qlen 1000
    link/ether 04:7c:16:19:98:71 brd ff:ff:ff:ff:ff:ff
    altname enx047c16199871
3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 1e:4b:33:3b:e6:e4 brd ff:ff:ff:ff:ff:ff
4: br1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 2a:20:04:0b:8f:50 brd ff:ff:ff:ff:ff:ff
[main@main ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp42s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000
    link/ether 04:7c:16:19:98:71 brd ff:ff:ff:ff:ff:ff
    altname enx047c16199871
3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1e:4b:33:3b:e6:e4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.26/24 metric 1024 brd 192.168.178.255 scope global dynamic br0
       valid_lft 831595sec preferred_lft 831595sec
    inet6 2a0c:d242:3806:3800:1c4b:33ff:fe3b:e6e4/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 6778sec preferred_lft 3178sec
    inet6 fd9f:c123:5b95:0:1c4b:33ff:fe3b:e6e4/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 6778sec preferred_lft 3178sec
    inet6 fe80::1c4b:33ff:fe3b:e6e4/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
4: br1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 2a:20:04:0b:8f:50 brd ff:ff:ff:ff:ff:ff
[main@main ~]$ ip r
default via 192.168.178.1 dev br0 proto dhcp src 192.168.178.26 metric 1024 
192.168.178.0/24 dev br0 proto kernel scope link src 192.168.178.26 metric 1024 
192.168.178.1 dev br0 proto dhcp scope link src 192.168.178.26 metric 1024 
[main@main ~]$ ip n
192.168.178.1 dev br0 lladdr 0c:72:74:f5:67:0b REACHABLE 
fd9f:c123:5b95:0:e72:74ff:fef5:670b dev br0 lladdr 0c:72:74:f5:67:0b router STALE 
fe80::e72:74ff:fef5:670b dev br0 lladdr 0c:72:74:f5:67:0b router STALE 
2a0c:d242:3806:3800:e72:74ff:fef5:670b dev br0 lladdr 0c:72:74:f5:67:0b router STALE 
[main@main ~]$

seth · 2025-09-07 19:17:23

outputs …

not "dot dot dot", the details there matter a lot.
ideally redirect the output into a file and usb-walk that to a system w/ internet support or worst-case, link photos of your screen.

TySpicer · 2025-09-07 19:28:00

Great, I figured out how to copy text! I assumed I needed a clipboard manager, but it turns out my terminal already has copy-paste functionality.

Output of ip a; ip r:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a0:c5:89:77:61:ea brd ff:ff:ff:ff:ff:ff
    [removed this line]
       valid_lft 268sec preferred_lft 268sec
    inet6 fe80::a2c5:89ff:fe77:61ea/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever

Output of ping -c1 _gateway:

PING _gateway (fe80::fa5e:42ff:fe81:a800%wlan0) 56 data bytes
64 bytes from _gateway (fe80::fa5e:42ff:fe81:a800%wlan0): icmp_seq=1 ttl=64 time=8.97 ms

--- _gateway ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 8.968/8.968/8.968/0.000 ms

Last edited by TySpicer (2025-09-07 19:57:42)

seth · 2025-09-07 19:38:30

Obfuscate the line that starts w/ "inet6 2600:8804", it's a publically routable IPv6 assigned to Cox Communications, GA, Atlanta.
You don't seem to have an IPv4 lease and github.com doesn't have an AAAA entry, your _gateway is the https://en.wikipedia.org/wiki/Link-local_address

If you expect this kind of limitation from your ISP, see https://wiki.archlinux.org/title/IPv6_t … oker_setup - otherwise please post your system journal

sudo journalctl -b | curl -F 'file=@-' 0x0.st

TySpicer · 2025-09-07 20:01:44

seth wrote:

Obfuscate the line

Thanks, that's good to know.

seth wrote:

If you expect this kind of limitation from your ISP

I'm not sure what this means, so here's my system journal: http://0x0.st/KqTA.txt

I'm assuming that worked, I can get to it from my other computer.

seth · 2025-09-07 20:06:28

Sep 07 14:54:06 arch NetworkManager[778]: <info>  [1757274846.8603] dhcp4 (wlan0): state changed new lease, address=192.168.0.138, acd pending
Sep 07 14:54:06 arch wpa_supplicant[785]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-42 noise=9999 txrate=866700
Sep 07 14:54:07 arch NetworkManager[778]: <info>  [1757274847.0290] dhcp4 (wlan0): state changed new lease, address=192.168.0.138
Sep 07 14:54:07 arch NetworkManager[778]: <info>  [1757274847.0329] policy: set 'SETUP-A7FD' (wlan0) as default for IPv4 routing and DNS
Sep 07 14:54:07 arch systemd-resolved[304]: wlan0: Bus client set default route setting: yes
Sep 07 14:54:07 arch systemd-resolved[304]: wlan0: Bus client set DNS server list to: 68.105.28.11, 68.105.29.11, 68.105.28.12
Sep 07 14:54:07 arch NetworkManager[778]: <info>  [1757274847.0460] device (wlan0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Sep 07 14:54:07 arch NetworkManager[778]: <info>  [1757274847.0528] device (wlan0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Sep 07 14:54:07 arch NetworkManager[778]: <info>  [1757274847.0533] device (wlan0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Sep 07 14:54:07 arch NetworkManager[778]: <info>  [1757274847.0546] manager: NetworkManager state is now CONNECTED_SITE
Sep 07 14:54:07 arch NetworkManager[778]: <info>  [1757274847.0569] device (wlan0): Activation: successful, device activated.
Sep 07 14:54:07 arch NetworkManager[778]: <info>  [1757274847.0589] manager: startup complete
Sep 07 14:54:07 arch NetworkManager[778]: <info>  [1757274847.3968] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 07 14:54:08 arch NetworkManager[778]: <info>  [1757274848.3434] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Sep 07 14:54:08 arch NetworkManager[778]: <info>  [1757274848.3460] policy: set 'SETUP-A7FD' (wlan0) as default for IPv6 routing and DNS
Sep 07 14:54:08 arch NetworkManager[778]: <info>  [1757274848.3524] dhcp6 (wlan0): state changed new lease, address=2600:8804…

You actually do receive an IPv4 lease on 192.168.0.138 ?

ping -c1 192.168.0.138
ping -c1 192.168.0.1

Did the ouput of "ip a" change? "ip r" is empty?

TySpicer · 2025-09-07 20:18:08

Output of ping -c1 192.168.0.138:

PING 192.168.0.138 (192.168.0.138) 56(84) bytes of data.
64 bytes from 192.168.0.138: icmp_seq=1 ttl=64 time=0.015 ms

--- 192.168.0.138 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.015/0.015/0.015/0.000 ms

Output of ping -c1 192.168.0.1:

PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=7.38 ms

--- 192.168.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 7.383/7.383/7.383/0.000 ms

Output of ip a:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a0:c5:89:77:61:ea brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.138/24 brd 192.168.0.255 scope global dynamic noprefixroute wlan0
       valid_lft 172596sec preferred_lft 172596sec
    [removed this line]
       valid_lft 86198sec preferred_lft 86198sec
    [removed this line]
       valid_lft 299sec preferred_lft 299sec
    inet6 fe80::135f:27ac:39c3:8836/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

Output of ip r:

default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.138 metric 600 
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.138 metric 600

seth · 2025-09-07 20:23:42

And can you connect to github.com now?

TySpicer · 2025-09-07 20:26:01

I'm not sure what changed, but I tried makepkg again, and it worked! I've also been working on getting automatic wifi connection set up, so that could have changed it (maybe installing NetworkManager).

I'll finish the installation process for yay and post here again if I'm still having issues. Thanks for the help!

Edit - Yep, everything is working, and I installed a web browser with yay. Awesome!

Last edited by TySpicer (2025-09-07 20:31:41)

seth · 2025-09-08 07:19:48

I'm not sure what changed

getting automatic wifi connection set up

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2025-09-07 00:57:10

[SOLVED] makepkg not working

#2 2025-09-07 01:05:57

Re: [SOLVED] makepkg not working

#3 2025-09-07 01:09:43

Re: [SOLVED] makepkg not working

#4 2025-09-07 01:30:03

Re: [SOLVED] makepkg not working

#5 2025-09-07 18:38:32

Re: [SOLVED] makepkg not working

#6 2025-09-07 18:41:51

Re: [SOLVED] makepkg not working

#7 2025-09-07 19:07:52

Re: [SOLVED] makepkg not working

#8 2025-09-07 19:15:53

Re: [SOLVED] makepkg not working

#9 2025-09-07 19:17:23

Re: [SOLVED] makepkg not working

#10 2025-09-07 19:28:00

Re: [SOLVED] makepkg not working

#11 2025-09-07 19:38:30

Re: [SOLVED] makepkg not working

#12 2025-09-07 20:01:44

Re: [SOLVED] makepkg not working

#13 2025-09-07 20:06:28

Re: [SOLVED] makepkg not working

#14 2025-09-07 20:18:08

Re: [SOLVED] makepkg not working

#15 2025-09-07 20:23:42

Re: [SOLVED] makepkg not working

#16 2025-09-07 20:26:01

Re: [SOLVED] makepkg not working

#17 2025-09-08 07:19:48

Re: [SOLVED] makepkg not working

Board footer