Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#58334 - mirrors.evowise.com -- There isn't libnsl in Core

Attached to Project: Arch Linux
Opened by Bogdan Kushnir (Wise_Deer) - Tuesday, 24 April 2018, 12:18 GMT
Last edited by Florian Pritz (bluewind) - Friday, 27 April 2018, 12:35 GMT
Task Type Bug Report
Category Mirrors
Status Closed
Assigned To Florian Pritz (bluewind)
Johannes Löthberg (demize)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Was being upgraded today and got this:

:: Starting full system upgrade...
resolving dependencies...
warning: cannot resolve "libnsl", a dependency of "libpurple"
warning: cannot resolve "libnsl", a dependency of "libuv"
warning: cannot resolve "libnsl", a dependency of "net-snmp"
warning: cannot resolve "libnsl", a dependency of "python"
warning: cannot resolve "libnsl", a dependency of "python2"
warning: cannot resolve "libnsl", a dependency of "python2"
warning: cannot resolve "libnsl", a dependency of "smbclient"
:: The following packages cannot be upgraded due to unresolvable dependencies:
libpurple libuv net-snmp python python2 smbclient

Trying to find libnsl and there is only package from multilib repo:

$ pacman -Ss libnsl
multilib/lib32-libnsl 1.2.0-1
Public client interface library for NIS(YP) and NIS+
This task depends upon

Closed by  Florian Pritz (bluewind)
Friday, 27 April 2018, 12:35 GMT
Reason for closing:  Fixed
Comment by Dave Reisner (falconindy) - Tuesday, 24 April 2018, 12:33 GMT
Definitely exists in [core]...

https://www.archlinux.org/packages/core/x86_64/libnsl/

Bad mirror? Bad repo config?
Comment by Bogdan Kushnir (Wise_Deer) - Tuesday, 24 April 2018, 12:48 GMT
> Bad mirror?
I use these:

## Worldwide
Server = http://mirrors.evowise.com/archlinux/$repo/os/$arch
Server = http://mirror.rackspace.com/archlinux/$repo/os/$arch

>Bad repo config?
Is used default config except multilib.
Comment by Eli Schwartz (eschwartz) - Tuesday, 24 April 2018, 13:00 GMT Comment by Bogdan Kushnir (Wise_Deer) - Tuesday, 24 April 2018, 13:05 GMT
It's Strange. On my another arch PC all's well. :\
Comment by Bogdan Kushnir (Wise_Deer) - Tuesday, 24 April 2018, 13:08 GMT
Eli Schwartz, I've tried many times. The result is the same.
Comment by Bogdan Kushnir (Wise_Deer) - Tuesday, 24 April 2018, 13:13 GMT
Here's a terminal screenshot.
Comment by Bogdan Kushnir (Wise_Deer) - Tuesday, 24 April 2018, 13:16 GMT
I've deleted multilib in this screenshot.
Comment by Dave Reisner (falconindy) - Tuesday, 24 April 2018, 13:22 GMT
The mirror is broken -- their core.db doesn't contain a libnsl entry.
Comment by Bogdan Kushnir (Wise_Deer) - Tuesday, 24 April 2018, 13:28 GMT
True. Have setted up another mirrors and it works correct. Thank.
Comment by Florian Pritz (bluewind) - Tuesday, 24 April 2018, 13:47 GMT
The evowise mirror is actually a CDN so it's difficult to tell what is broken. It seems to be fine for me, but I'll send them a mail.
Comment by Eli Schwartz (eschwartz) - Tuesday, 24 April 2018, 13:54 GMT
Well, I see a few things missing in core.db community.db but their extra.db matches the one I synced from mirror.lty.me

They seem to have the old versions still available, too.
Comment by Florian Pritz (bluewind) - Wednesday, 25 April 2018, 18:35 GMT
It this still broken? If so, please run the command below and check 1) if it finds libnsl and 2) which IP address you connected to.

curl -sv http://mirrors.evowise.com/archlinux/core/os/x86_64/core.db.tar.gz | tar tzf - | grep libnsl
Comment by Eli Schwartz (eschwartz) - Wednesday, 25 April 2018, 21:03 GMT
* Connected to mirrors.evowise.com (104.19.135.75) port 80 (#0)

Currently works for me, I guess. It matches my default rit.edu mirror exactly from my current location, which is the same one that had issues before.

Loading...