From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] make_dirs error in latest wireplumber package
Date: Fri, 02 Jun 2023 22:46:16 +0200 [thread overview]
Message-ID: <20230602204616.QHi29DSAGu2k6Ar_iVeM05js65dam6Er5Jx9PGpzcgI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44231@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
Closed issue by TeusLollo on void-packages repository
https://github.com/void-linux/void-packages/issues/44231
Description:
### Is this a new report?
Yes
### System Info
Void 5.15.114_1 x86_64 GenuineIntel uptodate FFFFFF
### Package(s) Affected
wireplumber-0.4.14_5 & wireplumber-0.4.14_6
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
Can't find anything.
### Expected behaviour
No idea actually. I don't use pipewire. What does that directory do? See below...
### Actual behaviour
Something funky going on with the `make_dirs` part of the latest wireplumber packages during their relevant _config_ phase.
Here's the relevant output:
```
wireplumber-0.4.14_5: configuring ...
chown: invalid user: ‘_pipewire:_pipewire’
Failed to set perms 0755 _pipewire:_pipewire to ./var/lib/wireplumber!
Updating MIME database...
wireplumber-0.4.14_5: updated successfully.
```
This has also happened again onto the newest version:
```
wireplumber-0.4.14_6: configuring ...
chown: invalid user: ‘_pipewire:_pipewire’
Failed to set perms 0755 _pipewire:_pipewire to ./var/lib/wireplumber!
Updating MIME database...
wireplumber-0.4.14_6: updated successfully.
```
Indeed, by reading the relevant package template on https://github.com/void-linux/void-packages/blob/master/srcpkgs/wireplumber/template, the string `make_dirs="/var/lib/wireplumber 0755 _pipewire _pipewire"` seems relevant.
No idea about this. Output of `ls` on the directory:
```
ls -a /var/lib/wireplumber
. ..
```
This may be related to the fact that I don't really have pipewire installed (Nor it ever was installed), since I'm on pure ALSA. Wireplumber has been pulled by the following dependencies:
```
xbps-query --revdeps wireplumber
Waybar-0.9.17_1
```
### Steps to reproduce
1. You probably need a system that has not pipewire installed, thus having wireplumber pulled down by a dependency (By waybar, in my case)
2. Update to either wireplumber-0.4.14_5 & wireplumber-0.4.14_6 and see the output for yourself.
prev parent reply other threads:[~2023-06-02 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 20:33 [ISSUE] " TeusLollo
2023-06-02 20:46 ` Duncaen [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=20230602204616.QHi29DSAGu2k6Ar_iVeM05js65dam6Er5Jx9PGpzcgI@z \
--to=duncaen@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).