Note: I thought abt DNS issue and added two more lines in /etc/resolve.conf
“nameserver 8.8.8.8”
“nameserver 8.8.8.9”
However, the same issue still poping up.
Regards
Ameen
Ameen Al-Azzawi
unread,
Jul 16, 2021, 12:44:09 PM7/16/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to opkg-devel
Sorry, I meant (8.8.4.4) not (8.8.8.9)
Alex Stewart
unread,
Jul 16, 2021, 1:19:54 PM7/16/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to opkg-...@googlegroups.com, Ameen Al-Azzawi
Hi Ameen,
A few things...
This mailing list is for the yocto project's fork of opkg [1]. Unless
you've intentionally switched to this fork in your OpenWRT build, I
expect that you're using the LEDE fork of opkg [2].
Our projects share a historical ancestor, but they're diverged. Any help
that this ML could provide about your OpenWRT configuration is
incidental. I assume OpenWRT has their own mailing lists, which could
probably help you better.
> headers: Couldn't resolve host name.
> diak@AFTR:~$
>
>
>
> Note: I thought abt DNS issue and added two more lines in
> /etc/resolve.conf
> *“nameserver 8.8.8.8”*
> *“nameserver 8.8.8.9”*
>
> However, the same issue still poping up.
You're asking opkg-LEDE to download package indexes from a subdomain of
`example.com` - which is a placeholder domain [3].
I would guess that some step in the OpenWRT build or configuration
process would have asked you to write in the package mirror you prefer,
and it would be substituted in place of that `example.com` TLD.
But as I said above, OpenWRT's lists will probably have a better idea of
how to fix that misconfiguration.