New packages: sing geoip and geosite

[hesam-init]

Testing the changes

• I tested the changes in this PR: YES

New package

• This new package conforms to the package requirements: YES

Local build testing

• I built this PR locally for my native architecture, (x86_64-glibc)

[Clos3y]

Both packages have scheduled, automated releases, so I think this probably isn't inline with the packaging requirements,

void-packages/CONTRIBUTING.md

Lines 28 to 29 in dae26c0

	Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
	Betas, arbitrary VCS revisions, templates using tip of development branch taken at build time and releases created by the package maintainer won't be accepted.

but I could be wrong

EDIT: You also need to squash your commits.

[hesam-init]

Both packages have scheduled, automated releases, so I think this probably isn't inline with the packaging requirements,

void-packages/CONTRIBUTING.md

Lines 28 to 29 in dae26c0

	Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
	Betas, arbitrary VCS revisions, templates using tip of development branch taken at build time and releases created by the package maintainer won't be accepted.

but I could be wrong
EDIT: You also need to squash your commits.

I will close this request due to a lint issue and will open a new one.

[hesam-init]

Both packages have scheduled, automated releases, so I think this probably isn't inline with the packaging requirements,

void-packages/CONTRIBUTING.md

Lines 28 to 29 in dae26c0

	Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
	Betas, arbitrary VCS revisions, templates using tip of development branch taken at build time and releases created by the package maintainer won't be accepted.

but I could be wrong
EDIT: You also need to squash your commits.

I also should mention These packages are requirements for the Nekoray client. After merging these two packages, I will push the Nekoray template.

[classabbyamp]

don't close and open new PRs, amend and force push instead. new PRs are lots of noise and they separate the review history

if you're adding dependencies of a package, add them and the package that needs them in one PR.

#51326