From: andry-dev <andry-dev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Samba aborts on Raspberry Pi 3B
Date: Sat, 02 Jan 2021 12:12:41 +0100 [thread overview]
Message-ID: <20210102111241.cgEWEiRJqzdhsSu1EOS3X_zH3EL8Y9ZUFEWaEYJYC-g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27565@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
New comment by andry-dev on void-packages repository
https://github.com/void-linux/void-packages/issues/27565#issuecomment-753460962
Comment:
By the way a new version of Samba was released in December (4.13.3), would it be possible to _also_ bump the package to `4.13.3_1`? That release is just about bug fixes ([changelog](https://www.samba.org/samba/history/samba-4.13.3.html)).
`4.13.3` compiles fine on my machine (x86_64; I just bumped the version and `xgensum`d the template) but I haven't had the chance to test it, it may be worthwhile to also test that with these changes. I can open the PR if @wangp doesn't want to, but I don't have any ARM device to test it with.
next prev parent reply other threads:[~2021-01-02 11:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 0:01 [ISSUE] " wangp
2020-12-31 3:56 ` ahesford
2020-12-31 5:39 ` ericonr
2020-12-31 14:10 ` Anachron
2020-12-31 14:11 ` Anachron
2020-12-31 15:56 ` ahesford
2020-12-31 17:18 ` hortimech
2020-12-31 17:44 ` ahesford
2021-01-01 7:54 ` wangp
2021-01-01 7:57 ` wangp
2021-01-01 13:53 ` Anachron
2021-01-01 13:58 ` ahesford
2021-01-01 14:03 ` hortimech
2021-01-01 14:15 ` Anachron
2021-01-01 14:27 ` ahesford
2021-01-01 18:30 ` Anachron
2021-01-01 18:40 ` hortimech
2021-01-02 0:28 ` wangp
2021-01-02 0:41 ` ericonr
2021-01-02 0:42 ` ericonr
2021-01-02 11:12 ` andry-dev [this message]
2021-01-02 13:12 ` wangp
2021-01-02 19:06 ` ahesford
2021-01-05 3:42 ` [ISSUE] [CLOSED] " ahesford
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=20210102111241.cgEWEiRJqzdhsSu1EOS3X_zH3EL8Y9ZUFEWaEYJYC-g@z \
--to=andry-dev@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).