<div dir="auto">Hi David,<div dir="auto"><br></div><div dir="auto">the case you describe is substantially different: in april 2021 SBo closed submissions and start adapting things to build on current to start getting ready for the soon-to-come 15.0 (rc1 had been already released).</div><div dir="auto">When we close submissions, differently from the normal developmrnt cycle, we admins patch everything needed without getting in touch with the single maintainers (accepting patches from maintainers and third parties) because it's not possibile to get in touch with everybody for every script with thousands of scripts to fix moving from one stable release of Slackware to another so the goal is to handle at least the build process for most of them so that at least they can be tested for functionality by the respective maintainers (we also accept patches from them at some point).</div><div dir="auto">That's the reason why rogue has been patched in may 2021.</div><div dir="auto"><br></div><div dir="auto">Matteo</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il ven 3 giu 2022, 12:09 David Chmelik <<a href="mailto:davidnchmelik@gmail.com">davidnchmelik@gmail.com</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Someone pushed a patch for previous rogue.tar.gz version on GitHub.com, <br>
which I don't (and won't) even use for my SlackBuilds. I only found out <br>
when sbopkg & sbotools said Rogue was already updated on SBo without me <br>
having updated Rogue. I didn't obscure/anti-spam my email in <a href="http://rogue.info" rel="noreferrer noreferrer" target="_blank">rogue.info</a> <br>
nor was inactive--in fact was aware of the problem because of testing my <br>
builds on Slackware-current--perhaps people were just catching up after <br>
Slackware 15. I thanked the person for patch but asked them in future <br>
to email first.<br>
<br>
On 6/3/22 1:20 AM, Matteo Bernardini wrote:<br>
> hi David,<br>
><br>
> could you please detail when and how this happened so we could try to <br>
> give an answer?<br>
><br>
> Matteo<br>
><br>
> Il giorno ven 3 giu 2022 alle ore 10:08 David Chmelik <br>
> <<a href="mailto:davidnchmelik@gmail.com" target="_blank" rel="noreferrer">davidnchmelik@gmail.com</a> <mailto:<a href="mailto:davidnchmelik@gmail.com" target="_blank" rel="noreferrer">davidnchmelik@gmail.com</a>>> ha scritto:<br>
><br>
> It happened to me once also. A patch was needed, but the person who<br>
> submitted it didn't even try to contact me, so didn't know I was also<br>
> updating to newer source code that didn't need the patch.<br>
><br>
> On 6/3/22 12:59 AM, Matteo Bernardini wrote:<br>
> > hi Chris,<br>
> ><br>
> > I suppose there has been a misunderstanding as nothing changed<br>
> in our<br>
> > general policy.<br>
> ><br>
> > Matteo<br>
> ><br>
> ><br>
> > Il giorno ven 3 giu 2022 alle ore 01:19 Christoph Willing<br>
> > <<a href="mailto:chris.willing@linux.com" target="_blank" rel="noreferrer">chris.willing@linux.com</a> <mailto:<a href="mailto:chris.willing@linux.com" target="_blank" rel="noreferrer">chris.willing@linux.com</a>><br>
> <mailto:<a href="mailto:chris.willing@linux.com" target="_blank" rel="noreferrer">chris.willing@linux.com</a> <mailto:<a href="mailto:chris.willing@linux.com" target="_blank" rel="noreferrer">chris.willing@linux.com</a>>>><br>
> ha scritto:<br>
> ><br>
> > I just noticed one of the SlackBuilds that I maintain<br>
> sitting in the<br>
> > pending queue even though I'd made no changes.<br>
> ><br>
> > When discussing this with the person who made the<br>
> submission, pointing<br>
> > out the need to first contact the maintainer, they said that:<br>
> > "I've gotten some different advice from one of the<br>
> admins<br>
> > for certain<br>
> > situations"<br>
> ><br>
> > Is this a new policy - that "for certain situations" anyone can<br>
> > arbitrarily submit changes for a SlackBuild?<br>
> ><br>
> ><br>
> > chris<br>
><br>
<br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org" target="_blank" rel="noreferrer">SlackBuilds-users@slackbuilds.org</a><br>
<a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer noreferrer" target="_blank">https://slackbuilds.org/faq/</a><br>
<br>
</blockquote></div>