<html><head></head><body><div class="yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div class="ydp11b58905yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div dir="ltr" data-setdir="false">I DO NOT WANT AUDACITY FIXED!!! I want it PURGED from the repository until it is fixed.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I want the repository to NOT contain packages which fail to link. </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">The issue is the INTEGRITY of the repositories.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I am contributing $100 USD/month to support the repository. Broken packages are not acceptable. So much so I have offered to pay a decent rate for fixing the specific issue I have raised.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Fixing this requires systematically installing ALL the packages in the repositories the cooperative maintains on a clean release image, running ldd(1) across all the executables and flagging any packages with failures for removal until they are fixed. It's a few hours work for someone with basic admin skills to automate that process. After that it's part of the release process.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I taught big oil staff to do this 30 years ago when we were installing from 8mm tape. As manual tape handling and hours of terminal interaction with undocumented install scripts were needed, I never automated the process beyond a script on an alternate disk pack which used dd(1) to copy the base OS install image to the test system disk for the next application. And after each install I ran filesystem wide checks of the MD5 checksums and similar to determine what the install script had done. The task is much easier in this case.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I know what I am asking for. It is not complex, difficult nor large. Merely boring. It needs to be done.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Reg</div><div><br></div>
</div><div id="ydp3b0fdf9dyahoo_quoted_1059422949" class="ydp3b0fdf9dyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;">
<div>
On Tuesday, September 22, 2026 at 01:00:51 PM CDT, Till Wegmüller <toasterson@gmail.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Hi<br></div><div dir="ltr"><br></div><div dir="ltr">Happy if you take it, and no worries about jumping in thats what safe environments and community is about aswell.<br></div><div dir="ltr">I agree that I don’t want to see them succeed but I also have seen that they are not going to. <br></div><div dir="ltr">The Subscription is subsidized and costs them money rather than earning them money. So I am not concerned about them having the money considering we are helping to bleed them dry.<br></div><div dir="ltr">Packaging is not a complex task rather a long and tedious task requiring knowledge of unfortunately arcane Scripting languages. Programming languages that are trivial for any model Automation. <br></div><div dir="ltr"><br></div><div dir="ltr">I can see that people don’t trust that idea of spending money with such a big company. For the full automation I am also aiming for a local ran Automation. But that does require 5 to 7k investment into Computer hardware. Unless you have some ECC Memory and a motherboard laying around.<br></div><div dir="ltr">Even previous generation Hardware is still in use now due to the shortage. I am still investing into that though and want to do any larger automation initiative with Automation that run on my own hardware rather than a big tech corps one.<br></div><div dir="ltr"><br></div><div dir="ltr">As for community in general we do have an active one. I loved to see Xfce work but people stop short of packaging. And this is not the only time this happened. btop is still earlier in the port and these kind of show and tells are lovely to see.<br></div><div dir="ltr"><br></div><div dir="ltr">-Till<br></div><div dir="ltr"><br></div><div dir="ltr">> On 22 Sep 2026, at 19:28, gemelen via oi-dev <<a href="mailto:oi-dev@openindiana.org" rel="nofollow" target="_blank">oi-dev@openindiana.org</a>> wrote:<br></div><div dir="ltr">> <br></div><div dir="ltr">> Sorry to jump into, but I'd like to comment on the Till's suggestion - this is exactly the<br></div><div dir="ltr">> kind of solutions that, in my opinion, should be weed out:<br></div><div dir="ltr">> paying for all problematic tech solution to a bigtech company instead of waging it to a person, that might be in a need to pay for the life supporting needs.<br></div><div dir="ltr">> <br></div><div dir="ltr">> That's up to the Reginald in this case and to a person in need of a problem to be solved,<br></div><div dir="ltr">> in general, but I believe we want a community here first of all?<br></div><div dir="ltr">> <br></div><div dir="ltr">> In order to provide an alternative, if nobody would vouch themselves, I'd rather do the<br></div><div dir="ltr">> requested change myself, even if I've never looked into the Audacity beyond occasional<br></div><div dir="ltr">> use.<br></div><div dir="ltr">> <br></div><div dir="ltr">> On Tue Sep 22, 2026 at 2:00 PM -03, Till Wegmüller wrote:<br></div><div dir="ltr">>> Hi Reginald<br></div><div dir="ltr">>> <br></div><div dir="ltr">>> Considering modern Tooling that I have tested recently the price for an individual Package is far less than this.<br></div><div dir="ltr">>> 200 Dollar gets you access to a Tool from either China or the US that can read the documentation and make that package and have Usage leftover to handle maintenance of X11 in the background, port a simple driver to rust run and test it over SSH. In the process accidentally cross compile said module and install and test it.<br></div><div dir="ltr">>> <br></div><div dir="ltr">>> I am currently testing how well an independent GPU runnable version can do this but at current speed, that capability is only a couple of months out. If we could get this with a clean conscience that would be the best but it is what it is. There is a real risk of spam, but give it a high quality description what to do (best an onboarding guide like our docs) and perform rigorous local QA and it will produce good output. <br></div><div dir="ltr">>> With 200 dollar I would grab a Codex subscription and make the package based on the newest Audacity which has a lot of improvements.<br></div><div dir="ltr">>> <br></div><div dir="ltr">>> At this moment the project needs people that continuously keep a set of packages maintained and if that is with Automation thats ok. Contributors are more likely to not feed the docs to their AI and then the AI get the package wrong but simply feed the Computer the docs and it works. <br></div><div dir="ltr">>> Spam and low quality will be handled but I am not preventing needed automation and helping out new automation efforts.<br></div><div dir="ltr">>> <br></div><div dir="ltr">>> -Till<br></div><div dir="ltr">>> <br></div><div dir="ltr">>>> On 21 Sep 2026, at 00:07, Reginald Beardsley via oi-dev <<a href="mailto:oi-dev@openindiana.org" rel="nofollow" target="_blank">oi-dev@openindiana.org</a>> wrote:<br></div><div dir="ltr">>>> I find the audacity link failure intolerable.<br></div><div dir="ltr">>>> I should like for someone sufficiently familiar with the repository code to implement a filter which prevents deposition in the repositories of packages which have run time linker issues. And also purge the repositories of packages which fail to link. For the work I propose a payment via the OI cooperative of $200 USD to whomever performs the task. For OI to survive it needs to develop a gig economy. This is a first stumble at doing it.<br></div><div dir="ltr">>>> Have Fun!<br></div><div dir="ltr">>>> Reg<br></div><div dir="ltr">>>> _______________________________________________<br></div><div dir="ltr">>>> oi-dev mailing list<br></div><div dir="ltr">>>> <a href="mailto:oi-dev@openindiana.org" rel="nofollow" target="_blank">oi-dev@openindiana.org</a><br></div><div dir="ltr">>>> <a href="https://openindiana.org/mailman/listinfo/oi-dev" rel="nofollow" target="_blank">https://openindiana.org/mailman/listinfo/oi-dev</a><br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <D79C930A5F78FC5C.asc>_______________________________________________<br></div><div dir="ltr">> oi-dev mailing list<br></div><div dir="ltr">> <a href="mailto:oi-dev@openindiana.org" rel="nofollow" target="_blank">oi-dev@openindiana.org</a><br></div><div dir="ltr">> <a href="https://openindiana.org/mailman/listinfo/oi-dev" rel="nofollow" target="_blank">https://openindiana.org/mailman/listinfo/oi-dev</a><br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">_______________________________________________<br></div><div dir="ltr">oi-dev mailing list<br></div><div dir="ltr"><a href="mailto:oi-dev@openindiana.org" rel="nofollow" target="_blank">oi-dev@openindiana.org</a><br></div><div dir="ltr"><a href="https://openindiana.org/mailman/listinfo/oi-dev" rel="nofollow" target="_blank">https://openindiana.org/mailman/listinfo/oi-dev</a><br></div></div>
</div>
</div></div></body></html>