SRCINFO | Dashboard library

The error happens on the remote side. Also, the error report doesn't look like a normal preconditions checking failure, it looks more like an internal bug.

So the only thing you can do with the error is to report it to the Arch repository maintainers and ask them to help you with resolving the issue.

According to the tcpdump manpage

The notation is first:last which means sequence numbers first up to but not including last

The first:last notation doesn't actually exist within the packet, therefore Scapy won't understand it. Tcpdump gives you this additional information based on the analysis of the TCP stream (and possible regrouping of the packets)

You should also note that your sequence numbers are probably relative, which means they don't really mean anything else than the order.

Using the first part of the number as a sequence number will probably be enough for your needs:

The error gives us the information we need:

tmp[0] = socket.gethostbyname(tmp[0])

Python's socket library is trying to do a hostname lookup with gethostbyname and it's failing.

For example, this is what usage of this function looks like:

"Resource temporarily unavailable" corresponds to EAGAIN. The Errors section of man recvfrom says that EAGAIN is set if:

a receive timeout had been set, and the timeout expired before data were received.

Your timeout seems to be too short.

According to RFC 1541, the client may retransmit the discover message no sooner than 4 seconds after the initial message has been transmitted. It implies that a reasonable timeout shall be in that ballpark.

Fortunately, neither did the solution require the editing of config files (which pains me deeply), nor did it require manual building (which also pains me). Instead, this was a two part problem.

First, the issue of the package not being supported, after doing some homework on it, turned out to simply boil down to a general warning (not even an error!) regarding the fact that AUR(Arch User Repository) packages are publicly produced, and therefore have the potential to be malicious. Of course we know imwheel does not fall into this category, so we may brush this first warning off unfazed, although I recommend to always vet your packages before making and/or installing them due to their very real malicious potential. So to recap the first problem (the warning about the package not being supported), there is no reason with the given package to fear it, therein rendering this error/warning no longer an obstacle to this installation.

Second, We have the daunting ERROR: pkgver is not allowed to contain colons, hyphens or whitespace. Anyone in the right mind would turn to editing an alleged syntactical error in the package buildfile, although this is also a deceiving error. Although this time around, the error is a brick wall in our installation, and not a mere mirage of a warning, it also leads us to a quite elegant (and by that I mean simple) solution. As it turns out, Arch with the latest Anarchy installer does not ship with all of the build tools you might have found in prior fresh installs with Arch-anywhere. Alas, all we need to do is install the packages core/make core/patch core/gcc core/autoconf core/automake core/binutils core/bison and core/fakeroot , which are all under the core repository, and all of which fall under the tag base-devel. In recap, all we needed were the following unmet prerequisite packages: core/make core/patch core/gcc core/autoconf core/automake core/binutils core/bison and core/fakeroot , which are all under the core repository, and all of which fall under the tag base-devel.

I hope I was of help for those like-minded linux noobs, and I wish all those who can apply this knowledge some happy hacking!