From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [samba-4.14.5_1] [armv6l] smbd failing to start
Date: Mon, 02 Aug 2021 19:38:30 +0200 [thread overview]
Message-ID: <20210802173830.STStVWhR1qFzF3eYMJ12FBcDCLReKI8p32Ckz8nHINA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32079@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/32079#issuecomment-891209190
Comment:
Samba is a known troublemaker for xbps-src. Building a package on a host that has samba-libs installed (even if a server isn't running!) can sometimes cause library dependencies to leak in, causing the resulting package to be totally broken. This kind of error seems to be symptomatic of these problems.
I'm not convinced the upgrade in #32300 isn't an accidental fix, but it would be good to test and that shouldn't block the update either way.
In the meantime, a couple of questions:
1. Is your samba package locally built?
2. If so, is the package natively built or cross-compiled?
If you do build your own package or are keen to test the update PR, best practice is to stop any samba services, completely uninstall samba and samba-libs (including any dependants necessary to make this possible) before building the package.
next prev parent reply other threads:[~2021-08-02 17:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 1:19 [ISSUE] " hk0O7
2021-07-21 18:17 ` Anachron
2021-07-21 19:26 ` hk0O7
2021-07-21 20:11 ` Anachron
2021-08-02 17:20 ` mvf
2021-08-02 17:38 ` ahesford [this message]
2021-08-02 18:27 ` mvf
2021-08-09 2:51 ` fosslinux
2021-08-09 2:52 ` fosslinux
2021-08-09 2:53 ` fosslinux
2021-08-13 16:25 ` KeepBotting
2022-05-27 2:12 ` github-actions
2022-06-10 2:13 ` [ISSUE] [CLOSED] " github-actions
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=20210802173830.STStVWhR1qFzF3eYMJ12FBcDCLReKI8p32Ckz8nHINA@z \
--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).