<!DOCTYPE html><html><head><title></title></head><body><div style="font-family:Arial;">Just in case it gets removed, I do keep signal-desktop mostly up to date in my (very) modest Slackware repo, basically made for my own convenience: <a href="https://slack.osh.id.au/">https://slack.osh.id.au/</a></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">It does a binary repack of signal-desktop (checks the signatures first though, so it's not a blind download/repackage).</div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">--</div><div style="font-family:Arial;">Dave</div><div style="font-family:Arial;"><br></div><div>On Tue, 11 Aug 2026, at 5:38 AM, Greg Tourte wrote:</div><blockquote type="cite" id="qt" style=""><div dir="ltr"><div class="qt-gmail_default" style="font-family:monospace, monospace;font-size:x-small;">Willy,</div><div class="qt-gmail_default" style="font-family:monospace, monospace;font-size:x-small;"><br></div><div class="qt-gmail_default" style="font-family:monospace, monospace;font-size:x-small;">does that include package which explicitly state in the README that the package require the newer GLIBC?</div><div class="qt-gmail_default" style="font-family:monospace, monospace;font-size:x-small;"><br></div><div class="qt-gmail_default" style="font-family:monospace, monospace;font-size:x-small;">I maintain one such script (signal-desktop) and it would be a shame to see it removed from the repo.</div><div class="qt-gmail_default" style="font-family:monospace, monospace;font-size:x-small;"><br></div><div class="qt-gmail_default" style="font-family:monospace, monospace;font-size:x-small;">Cheers</div><div class="qt-gmail_default" style="font-family:monospace, monospace;font-size:x-small;"><br></div><div class="qt-gmail_default" style="font-family:monospace, monospace;font-size:x-small;">Greg</div></div><div><br></div><div class="qt-gmail_quote qt-gmail_quote_container"><div dir="ltr" class="qt-gmail_attr">On Mon, 10 Aug 2026 at 15:23, Willy Sudiarto Raharjo <<a href="mailto:willysr@slackbuilds.org">willysr@slackbuilds.org</a>> wrote:</div><blockquote class="qt-gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204, 204, 204);padding-left:1ex;"><div>Hi all</div><div> <br></div><div> We noticed that some applications require newer version of libraries or modules</div><div> that is already provided by Slackware core packages. This is normal as</div><div> Slackware 15.0 is now 4 years old and upstream are bumping requirements as they</div><div> develop new version with more features. Patrick has been kind enough to provide</div><div> some new version of some packages into testing/ which helps people to keep</div><div> updating to the latest version of the software they often use daily.</div><div> <br></div><div> We just to want to remind everyone that SBo is designed to be tested against</div><div> latest Slackware Stable releases with latest patches. It doesn't include extra/</div><div> or testing/ which requires manual intervention and not part of the full</div><div> installation. Our CI is NOT designed to test against custom installation, which</div><div> includes packages from extra or testing.</div><div> <br></div><div> That said, moving forward, we will start scanning our repository for scripts</div><div> that requires newer libraries/packages, such as GLIBC and start</div><div> removing them. Urchlay will add GLIBC detection at sbo-maintainer-tools package</div><div> soon, which will help CI to test against new PR that requires newer GLIBC.</div><div> <br></div><div> Maintainers, please ensure that your scripts are tested against clean</div><div> environment of Slackware 15.0, not -current or custom installation.</div><div> Our FAQ is also updated to clarify this issue</div><div> <a href="https://slackbuilds.org/faq/#full" rel="noreferrer" target="_blank">https://slackbuilds.org/faq/#full</a></div><div> <br></div><div> <br></div><div> --</div><div> Willy Sudiarto Raharjo</div><div> _______________________________________________</div><div> SlackBuilds-users mailing list</div><div> <a href="mailto:SlackBuilds-users@slackbuilds.org" target="_blank">SlackBuilds-users@slackbuilds.org</a></div><div> <a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a></div><div> Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a></div><div> FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer" target="_blank">https://slackbuilds.org/faq/</a></div></blockquote></div><div>_______________________________________________</div><div>SlackBuilds-users mailing list</div><div><a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a></div><div><a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a></div><div>Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a></div><div>FAQ - <a href="https://slackbuilds.org/faq/">https://slackbuilds.org/faq/</a></div><div><br></div><div><br></div></blockquote><div style="font-family:Arial;"><br></div></body></html>