void-linux / void-linux/void-packages

Currently not installable packages

Open
#21,483 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Shell
Stars
3.4k
Forks
2.8k
Avg merge
2d 5h
Merged PRs (30d)
299

Description

So, I basically queried all available packages and ran "xbps-install -n" on them.

Here are the results:

ruby-travis-1.8.10_2/stderr:MISSING: ruby-faraday<1.0
ruby-faraday_middleware-0.13.1_2/stderr:MISSING: ruby-faraday<1.0

python3-pylibgen-2.0.1_2/stderr:MISSING: python3-requests>2.20.9<2.21.1

frr-reload-7.2.1_1/stderr:MISSING: python3-ipaddr>=0

cegui-devel-0.8.7_10/stderr:MISSING: boost-python>=0
  • ruby-travis seems completely broken
  • pylibgen should be tagged broken or updated
  • python3-ipaddr doesn't exist, maybe we can just remove from template
  • cegui-devel is searching for boost-python, but actual package name is boost-python1.72 No idea how to fix this one.
sssd-python3-2.0.0_3/stderr:sssd-python3-2.0.0_3: broken, unresolvable shlib `libsss_crypt.so'
sssd-python3-2.0.0_3/stderr:sssd-python3-2.0.0_3: broken, unresolvable shlib `libsss_debug.so'
sssd-python3-2.0.0_3/stderr:sssd-python3-2.0.0_3: broken, unresolvable shlib `libsss_util.so'
sssd-python-2.0.0_3/stderr:sssd-python-2.0.0_3: broken, unresolvable shlib `libsss_crypt.so'
sssd-python-2.0.0_3/stderr:sssd-python-2.0.0_3: broken, unresolvable shlib `libsss_debug.so'
sssd-python-2.0.0_3/stderr:sssd-python-2.0.0_3: broken, unresolvable shlib `libsss_util.so'

perl-Test-Simple-1.302174_1/stderr:perl-Net-SSLeay-1.88_3: broken, unresolvable shlib `libperl.so.5.30'

libvaladoc-0.46.3_1/stderr:libvaladoc-0.46.3_1: broken, unresolvable shlib `libvalaccodegen.so'
valadoc-0.46.3_1/stderr:libvaladoc-0.46.3_1: broken, unresolvable shlib `libvalaccodegen.so'
valadoc-0.46.3_1/stderr:valadoc-0.46.3_1: broken, unresolvable shlib `libvalaccodegen.so'
  • sssd-python probably only needs a rebuild
  • no idea, it can't find a shlib that's the exact current version in perl
  • no idea for valadoc

I can try to work on these later, but if anyone wants to tackle them already :)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by rerunning xbps-install -n for the listed packages and inspect the reported missing dependencies and shared libraries. Work through each package entry separately; done means the affected packages are no longer reported as unresolvable, broken, or missing required libraries.

Written by the indexing model from the issue text.

Assessment

Tech stack
perl, python, ruby, shell
Domain
build-system, tooling
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.