Bug#814382: RFH: samba -- SMB/CIFS file, print, and login server for Unix
Le lun. 24 mai 2021 à 07:18, Abi <ad@abdha.com> a écrit :
>
> Hello again, thanks for responding.
>
> My skills include:
>
> An amateur understanding of Samba4 AD DC and file server. I manage a dozen or so installations ( addc and fs ), and I know how to spin up and manage installations as well as troubleshoot issues when they occur. I also read through the mailing list daily in order to have a better grasp possible issues.
> Identifying warnings/errors from log output within code. I wouldn't call myself an advanced C or Python developer ( I mostly write golang/php ), however I should be able to look through the source code and trace issues based off the output reporters provide.
>
> I'm also interested in debian packaging, but I know absolutely nothing apart from a few links I've read through. Would you be able to forward me some relevant reading so I'll be able to assist on that front ( if needed ) in the future?
You can take a look at https://wiki.debian.org/Packaging which starts
with basic guides up to advanced topics. Samba is a big package, using
recent packaging methods.
>
> By default, sending to nnn@bugs.debian.org won't be sent to the submitter,
> carefully read https://www.debian.org/Bugs/Developer#followup to ensure that
> both submitter and maintainer (pkg-samba list) have the mail (nnn +
> nnn-submitter)
>
> I read through that section that you've linked and I think I understand. Since you are the maintainer and the person I am replying to, this message will actually get to you twice. However, if you were not a maintainer and just a user in the bug report I was replying to, you would receive this once. If I wanted to reply directly to the bug submitter and maintainer, I would tag 814382@bugs.debian.org ( so the maintainer receives it ) and 814382-submitter@bugs.debian.org ( so the submitter receives it ) - I'm assuming it will only be filed in the bug report once. Alternatively, couldn't I just send a reply to 814382@bugs.debian.org and {submitter email address} ? or should I stick with nnn-submitter?
You can send to submitter address directly, they may receive the mail
twice if you do and they have subscribed to the bug (but twice is
better than none).
>
> Debian's bug tracker is managed thru mails, you can look at
> https://www.debian.org/Bugs/ and
> https://www.debian.org/Bugs/server-control to start with.
>
> I've gone ahead and read through both links ( and the links within those links ), and I think I have a good understanding of the various levels/tags that should be assigned to a report and what the standard operating procedure is, as well as the control request server commands.
>
> Tagging bugs and closing with the relevant version of the fix would help a lot!
>
> Sure, where should I start? I looked through https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=samba#_0_4_4 , and found: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765408 . I guess what needs to be changed is:
>
> Tag set to fixed-upstream
> Security level: important
> Add wheezy tag
Yes
> I'm assuming it's okay to close the bug report after that since the wheezy is EOL, and there is no hope for backporting?
Yes, you can also close jessie-only bugs for the same reason. For
stretch and buster, you can also close up to normal-severity bugs,
saying that we won't fix them. Having a list of commits that we should
cherry-pick for buster would be good (security fixes, stability fixes,
crashes). Also I think upgrade issues up to stretch can be closed.
> Am I on the right track, or totally off?
You're on the right track. Go ahead ! I'll receive notifications of
your changes and if you have any doubt, ask on the bug. Some users may
have created a bug and are no longer impacted, so pinging old bugs and
closing after a month without reply will also help.
Also, appart from samba, there are some bugs in cifs-utils (and one in
ldb, talloc, tevent):
https://qa.debian.org/developer.php?email=pkg-samba-maint%40lists.alioth.debian.org
>
> Let me know if there's a particular system you'd like me to follow when triaging. I can start right away.
You can sort by bug number, or by severity. Both ascending and
descending makes sense.
>
> Thanks!
>
>
> On 5/23/21 3:02 PM, Mathieu Parent wrote:
>
> Le dim. 23 mai 2021 à 04:33, Abi <ad@abdha.com> a écrit :
>
> Hello Mathieu,
>
> Hello Abi,
>
> I saw the help request submitted to the samba mailing list by A.
> Bartlett on 05/14 . I would love to help with triaging bug
> reports/improving tests . What steps would I need to take in order to
> get involved?
>
> Let me know. Thanks.
>
> Thanks for proposing your help.What are your skills?
>
> Debian's bug tracker is managed thru mails, you can look at
> https://www.debian.org/Bugs/ and
> https://www.debian.org/Bugs/server-control to start with.
>
> By default, sending to nnn@bugs.debian.org won't be sent to the submitter,
> carefully read https://www.debian.org/Bugs/Developer#followup to ensure that
> both submitter and maintainer (pkg-samba list) have the mail (nnn +
> nnn-submitter)
>
> Tagging bugs and closing with the relevant version of the fix would help a lot!
>
> On the test side, I have a WIP mrege request at:
> https://salsa.debian.org/samba-team/samba/-/merge_requests/6
>
> But we'll wait for bullseye to be released to start working on this.
>
> If you know about Debian packaging, there other possible tasks.
>
> Regards
>
> Mathieu Parent
--
Mathieu
Reply to: