@savoury1 Thanks for the fix and also for bringing the ffmpeg-git PPA to my attention. I might try that on one of my systems, although -- if the ffmpeg5 PPA can be considered more stable -- I still might use that for livecd ISO-s. ___
On the SavOS part, writing such frustrations out of your system could help in itself (from a psychological perspective), although, honestly -- if you would allow some constructively meant remarks --, I don't think the place/mode of presentation was well targeted or formatted. This looks to me like blog-post material. Here, in a bug-report, IMHO, it will reach only a negligible amount of people, those who were not just affected by but additionally are actively dealing with this specific issue (possibly only Pieter and me): I might be mistaken here, but in my experience, only a small amount of the users of a PPA...or generally software (and the more tech-savvy at that) take the effort to deal with bugs and bug-reports themselves -- hell, even I am sometimes "lazy" or otherwise engaged and just "idly" (from the bug's perspective) wait for a fix if my system is not falling apart --, and even from those people, only those read a bug-report who are currently experiencing the problem (and are sufficiently bothered by it), and even from those people, few will read through such a huge amount of text, especially one not (directly) helping in the resolution of the specific bug. And after a fix, no one will read it again until a regression happens. At least that is my experience. I see bug-reports as a very focused medium. As a side-note, this -- based on my very superficial impression -- seems strongly connected to your general reaching-people issue... (advertising/marketing/website/team-seeking/fund-raising) Allocating a bit more resources (investing) this way might help a lot. Unfortunately I myself have also near-to-no experience in (reasonable, modern) website building or packaging or public interfacing for that matter. However, I have been looking at some CMS / website generators based on git and markdown which might scratch your itch with relatively low investment (both initial AND long-term). E.g. Jekyll or Hugo or a lot of simpler github projects. I don't remember the specifics of my research (earlier), but e.g. both Hugo and Jekyll seem to integrate well together with the "GitHub Pages" service: https://gohugo.io/hosting-and-deployment/hosting-on-github/ https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll Then, I would stress again to attack the issues plaguing the SavOS ecosystem from multiple fronts. It seems to me that you enjoy working on SavOS, and it's great if you can afford to do just that. But, IMHO, irrespective of whether you can afford to work only on that or not, in your place I would make a BIG priority decreasing the effort it takes to keep SavOS alive as much as possible. As I see it, it pays off in EVERY scenario (given you want to keep it alive). With respect to upgrading OS and HW, I *can* see advantages to it. Risking re-stating what you might already know, maybe I can enrich (not necessarily change) your perspective. Let me just point out 1 thing for each: - From a HW perspective, shorter upgrading cycles finances development. The results include needing significantly less energy/power to perform the same amount of computation and/or allowing new ways to perform computations better (e.g. parallelization). Without it, IMO, development would slow down significantly. On the other hand, I think (more?) optimal upgrade intervals could be found, but they probably depend on the specific needs of businesses/userbases and the specific abilities/capabilities of HW development companies, so it would probably be hard to calculate for a specific circumstance, and possibly infeasible for the general case; - From an OS perspective, as I (with my quite limited understanding) see it, there are pros and cons to both point-release (release-cycle-based) and rolling-release OS release strategies. To over-simplify it, * release cycles give a higher degree of confidence that contained software and its feature-frozen versions works together smoothly due to more testing, while * rolling releases give more freedom and cutting-edge features for the price of less reliability for the whole to play nice together. In the Linux ecosystem, fortunately, we can find and choose both types, better even, distros do exist which offer both at the same time. Ubuntu, specifically, did not offer a rolling-release for a long time, although Debian (its base) kind-of does (see: unstable/sid). So, in a sense, by choosing to use Ubuntu, you chose point releases. On the bright side, based on popular request, even that actually seems to change (at least somewhat). At the time of writing, the most recent article I found on the subject: https://hothardware.com/news/ubuntu-linux-rolling-release-rhino I myself actually did not mind that much point releases, because it kind of made me start with a clean slate regularly, keeping clutter, bloat and occasional system-screw-ups of my own doing at bay and not to accumulate out of scope. It also can certainly be advocated that perhaps my user-/maintenance-habits should be improved instead. :) Additionally, it provided a way to get introduced to new applications which were probably justifiably chosen to replace old ones by people with more experienced and/or perspective than me (with which I probably would agree, given that I chose my distro well), and I did not have to do the research, while usually still allowing to install the old applications if I wanted to. You addressed a lot of things here, and at length. The above were the points I remembered to comment on after finding the time and actually getting it done---both reading your side and writing mine. It might also be worthwhile to put some more effort in to shorten such long texts to help along more people reading it and/or being able to address more points you raise. This obviously takes additional time and skill. As you can clearly see, I am subject to this as well. :) So I actually do not expect anyone else reading this than you. :) Finally, again, I wish you all the best with your situation and your project. Take care! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965181 Title: ffmpeg: FFmpeg 5.0 (ppa:savoury1/ffmpeg5) uninstallable -- plus general SavOS discussion To manage notifications about this bug go to: https://bugs.launchpad.net/savos/+bug/1965181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
