https://bugzilla.redhat.com/show_bug.cgi?id=2320142

Petr Menšík <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|[email protected]    |[email protected]
              Flags|                            |fedora-review?
                 CC|                            |[email protected]



--- Comment #3 from Petr Menšík <[email protected]> ---
I am not sure how wfserver should be used exactly. But if that is indeed a
service, it should have either system or user systemd service packaged too. At
least from its name it seems so.

It seems resampler/ contains similar header as
speexdsp-devel-1.2.1-5.fc39.x86_64 package. Are they compatible?

Should be speexdsp be used during build and local copy deleted? At least
resampler/COPYING contains outdated GNU Temple address. If it contains
non-trivial local changes, it should be included in spec with Provides:
bundled(speexdsp). Ideally with version of bundled copy, if known. I think
issue should be created at upstream to try reuse system speexdsp library, if it
has version high enough.


-- 
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2320142

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202320142%23c3

-- 
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to