PA module support in PipeWire
by Lóránt Perger
Hi,
I would like to ask about the developers' stance towards supporting PulseAudio plugins when using `pipewire-pulseaudio`. On some other mainstream distributions this can easily be achieved as the modules are packaged with the PA pipewire replacement package, however, in Fedora they are currently packaged in the `pulseaudio` package (as reported by `dnf provides`), which conflicts with `pipewire-pulseaudio`.
My specific use-case was to use `module-echo-cancel` which is a module that does wonders to how my microphone sounds, however, I'm not able to do so, as the module is only available in the `pulseaudio` package. I asked the QA IRC channel for help, whom suggested moving back to PA for the time being and raising the issue here.
I'm aware that the PipeWire project has its own plans how to handle PulseAudio services in the future ( https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/PulseAudio#the-p... ), but until that happens I was wondering if the devs would be willing to consider decoupling these modules from the package and putting them in another that doesn't conflict with PipeWire. I'm of course also interested in any other workarounds possible if the request is not accepted.
Thank you for your time and I'm hoping the issue can be resolved swiftly.
Best,
Lóránt
3 years, 3 months
Automatizing package review process
by Mattia Verga
Hello folks,
during the last winter holidays I've started to write a new flask app to
automatize the new package submission process. The goals of this app
would be:
- Get rid of manually open and manage Bugzilla tickets. Have the ticket
filed in a web form (or maybe by CLI), and have the ticket workflow
managed automatically.
- Have tests (possibly all) run automatically upon submission instead of
rely on tests performed locally by a reviewer. This will make package
submission more secure, review results more consistent and, most of all,
will speed up the approval process (or at least will give the submitter
a quick answer whether or not their package adhere to Fedora
Guidelines). We may have some tests still performed and filed manually
by reviewers if we cannot make all tests performed automatically, but we
will not be blocked by a single reviewer.
- When all tests pass, have the package repository automatically created
in git, import the srpm and fire the build in Rawhide. This will ensure
that what is approved is what is packaged - later changes will be
tracked and noted. It will also avoid users to create releng tickets and
releng folks waste their precious time handling those tickets.
As this is my first flask project and I can only spend few hours per
week, the code is still in very early stage. I would have preferred to
write this announcement with something more "production ready", but
since this is such a big project I've already realized that I need help
from users with a lot more experience in flask development. Probably,
I've already made some mistake in the current code I should be ashamed
for... :-)
So, I've pushed the current code on a Pagure repository [1], it would be
nice to have some folks working on this together. If, of course, you
think it's a good idea.
Have a nice time,
Mattia
[1] https://pagure.io/feluca
3 years, 3 months
License field correction: giada changed from “GPLv3+” to “GPLv3+ and […]”
by Benjamin Beasley
I rescued the giada package after it was orphaned and have updated it to the latest upstream release, using the new CMake build system. The package now properly documents its pre-existing bundled dependencies (four direct and many indirect). Accordingly, the License field has changed from “GPLv3+” to “GPLv3+ and MIT and CC0 and GPLv3 and ISC and ASL 2.0 and BSD and zlib and IJG”.
It is my hope that, over time, the number of bundled dependencies can be reduced by submitting them to Fedora, where they are not already present, and by patching the build system where necessary, ideally in a way that can be submitted upstream.
3 years, 3 months
Don't update to the latest f33!
by Steve Dickson
Hello,
I just updated to latest Fedora 33 and
I no longer have any DNS name solution.
The network is up... but...
$ ping www.yahoo.com
ping: www.yahoo.com: Name or service not known
I changed nothing!
How would be the bet way to debug this???
steved.
3 years, 3 months