Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] xbps-install -Su fails with "python3-3.12.0_1: broken, unresolvable shlib `libcrypt.so.1'"
Date: Sun, 04 Feb 2024 07:26:00 +0100	[thread overview]
Message-ID: <20240204062600.32A9920CAE@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47922@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

Closed issue by michael-ball on void-packages repository

https://github.com/void-linux/void-packages/issues/47922

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.67-rt20_1 x86_64 GenuineIntel uptodate hold rrrmDFFFF

### Package(s) Affected

python3-3.12.0_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

`xbps-install -Su` completes without error

### Actual behaviour

Running `xbps-install -Su` results in the following error:

```
python3-3.12.0_1: broken, unresolvable shlib `libcrypt.so.1'
Transaction aborted due to unresolved shlibs.
```

### Steps to reproduce

1. On a system with python3 already installed, run `sudo xbps-install -Su`
2. OR try to install python3 with `sudo xbps-install -S python3`

      parent reply	other threads:[~2024-02-04  6:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-27 10:38 [ISSUE] " michael-ball
2023-12-27 13:42 ` michael-ball
2023-12-27 14:09 ` classabbyamp
2023-12-27 14:09 ` classabbyamp
2023-12-27 16:10 ` michael-ball
2023-12-30  0:31 ` Sheape
2023-12-30  2:21 ` Sheape
2024-02-04  6:26 ` ahesford [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240204062600.32A9920CAE@inbox.vuxu.org \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).