Re: Cfitsio soname bump

[Mattia Verga via devel]

Il 16/12/22 01:22, Sergio Pascual ha scritto:

> Hello, I'm going to update to cfitsio 4.2 in Rawhide. This involves a soname 
> bump.
>
> Affected packages:
>
> ...
> indi-gphoto
> ...

This package was retired, it is now obsoleted by indi-3rdparty-drivers.

Mattia___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Linking problem with ncurses on rawhide, not f37

[Florian Weimer]

* Ron Olson:

> In Rawhide the ncurses libs are at 6.3-4.20221126, while f37 is
> 6.3-3.20220501. I recall seeing some messages go by related to ncurses
> on the list here regarding the -compat library, but I’m not sure if
> that’s related to my issue. It seems weird that some of the functions
> it’s unable to find are part of the library (e.g. wtimeout is a valid
> function, according to the man pages).
>
> Could there be something weird with rawhide’s copy of ncurses or was
> there some big update that removed all these functions?

Recently, ncurses introduced symbol versioning at run time, but not at
link time (bug 1875587).  I missed that ncurses constitutes of multiple
shared objects that depend on each other.  What seems to happen here is
that some other object in that link depends on libncurses, which results
in linker using the versioned libncurses (the run-time version).  The
versioned libncurses depends on the versioned libtinfo because it uses
versioned symbol references.  But -ltinfo uses a linker script to link
against the unversioned libtinfo, so that the application sticks to the
Fedora ncurses ABI, and that is not suitable for resolving the symbol
references in the versioned libncurses.

It may work to use this for libtinfo.so:

GROUP (/usr/lib64/ncurses-novs/libtinfo.so.6 AS_NEEDED 
(/usr/lib64/ncurses-novs/libncurses.so.6))

But the AS_NEEDED might come too late to have an effect, after the
versioned libncurses has been loaded.  It's also possible that the build
system for this particular package has an explicit reference to
/usr/lib64/libncurses.so.6 somewhere that we cannot easily get rid of
from the outside.  In the latter case, even a special directory for
unversioned, link-time search objects, a directory that is injected into
the build using -rpath-link (via the default linker flags in
redhat-rpm-config) would fail to hide the versioned libncurses variant.

Miroslav, we may have to revert the versioning change if the AS_NEEDED
approach does not work.  This is also not something that would have been
solved by a stub generator.  Linking versioned libncurses against
unversioned libtinfo etc. would solve this, but I don't know how it
would to get to this point.

Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

CPE Weekly Update – Week 50 2022

[Lenka Segura]

*Hi everyone,*

*Reminder: This is the last email we are sending! If you want to stay in
touch with the CPE updates, please follow the instructions at the bottom.*







*This is a weekly report from the CPE (Community Platform Engineering)
Team.The report could be found at
https://communityblog.fedoraproject.org/cpe-weekly-update-week-50-2022/
If
you want to receive weekly reports by email in the future, please subscribe
to either https://communityblog.fedoraproject.org/
 or
https://discussion.fedoraproject.org/c/news/commblog/61
. We will stop
sending them in 2023.Regards,CPE Team*
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

colorful license change

[Artur Frenszek-Iwicki]

Hey all,

colorful had a new major release, v2.0, which brought in a licensing change.
I took this as an opportunity to also migrate the License: tags to SPDX.

Old v1.3 license: zlib with acknowledgement

New v2.0 licenses:
- colorful: GPL-3.0-only AND (MPL-2.0 OR Zlib)
- colorful-data: zlib-acknowledgement

Cheers,
A.FI.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora rawhide compose report: 20221216.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20221215.n.0
NEW: Fedora-Rawhide-20221216.n.0

= SUMMARY =
Added images:2
Dropped images:  0
Added packages:  7
Dropped packages:0
Upgraded packages:   88
Downgraded packages: 0

Size of added packages:  8.54 MiB
Size of dropped packages:0 B
Size of upgraded packages:   5.78 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -196.64 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Container_Base docker s390x
Path: 
Container/s390x/images/Fedora-Container-Base-Rawhide-20221216.n.0.s390x.tar.xz
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-Rawhide-20221216.n.0.iso

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: ipa-exgothic-fonts-004.01-13.fc38
Summary: Japanese Gothic-typeface OpenType font by IPA
RPMs:ipa-exgothic-fonts
Size:3.32 MiB

Package: ipa-exmincho-fonts-004.01-13.fc38
Summary: Japanese Mincho-typeface OpenType font by IPA
RPMs:ipa-exmincho-fonts
Size:4.55 MiB

Package: python-gbinder-1.1.1-1.fc38
Summary: Python bindings for libgbinder
RPMs:python3-gbinder
Size:242.22 KiB

Package: python-jupyterlab-server-2.16.3-1.fc38
Summary: A set of server components for JupyterLab and JupyterLab like 
applications
RPMs:python3-jupyterlab-server
Size:125.73 KiB

Package: rust-cargo_metadata0.12-0.12.3-1.fc38
Summary: Structured access to the output of `cargo metadata`
RPMs:rust-cargo_metadata0.12+default-devel rust-cargo_metadata0.12-devel
Size:32.07 KiB

Package: rust-pulldown-cmark0.8-0.8.0-1.fc38
Summary: Pull parser for CommonMark
RPMs:rust-pulldown-cmark0.8+default-devel 
rust-pulldown-cmark0.8+gen-tests-devel rust-pulldown-cmark0.8+getopts-devel 
rust-pulldown-cmark0.8+simd-devel rust-pulldown-cmark0.8-devel
Size:129.78 KiB

Package: rust-sysinfo0.23-0.23.13-1.fc38
Summary: Library to get system information
RPMs:rust-sysinfo0.23+c-interface-devel rust-sysinfo0.23+debug-devel 
rust-sysinfo0.23+default-devel rust-sysinfo0.23+multithread-devel 
rust-sysinfo0.23+rayon-devel rust-sysinfo0.23-devel
Size:160.71 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  NetworkManager-1:1.41.7-1.fc38
Old package:  NetworkManager-1:1.41.6-1.fc38
Summary:  Network connection manager and user applications
RPMs: NetworkManager NetworkManager-adsl NetworkManager-bluetooth 
NetworkManager-cloud-setup NetworkManager-config-connectivity-fedora 
NetworkManager-config-server NetworkManager-dispatcher-routing-rules 
NetworkManager-initscripts-ifcfg-rh NetworkManager-initscripts-updown 
NetworkManager-libnm NetworkManager-libnm-devel NetworkManager-ovs 
NetworkManager-ppp NetworkManager-team NetworkManager-tui NetworkManager-wifi 
NetworkManager-wwan
Size: 25.03 MiB
Size change:  -17.24 KiB
Changelog:
  * Thu Dec 15 2022 Lubomir Rintel  - 1:1.41.7-1
  - Update to 1.41.7 release (development)


Package:  SIMVoleon-2.1.0-1.fc38
Old package:  SIMVoleon-2.0.3-9.fc37
Summary:  Volume rendering library for Coin
RPMs: SIMVoleon SIMVoleon-devel
Size: 1.97 MiB
Size change:  36.44 KiB
Changelog:
  * Thu Dec 15 2022 Ralf Cors??pius  - 2.1.0-1
  - Upgrade to 2.1.0.
  - Convert license to SPDX.
  - Remove bogusly installed /usr/share/info/SIMVoleon2.
  - Fix broken handling of non-utf8 sources.
  - Switch off HTML_TIMESTAMPs.


Package:  SoQt-1.6.0-11.fc38
Old package:  SoQt-1.6.0-9.fc37
Summary:  High-level 3D visualization library
RPMs: SoQt SoQt-devel
Size: 4.45 MiB
Size change:  32.13 KiB
Changelog:
  * Thu Dec 15 2022 Ralf Cors??pius  - 1.6.0-10
  - Convert license to SPDX.
  - Remove bogusly installed /usr/share/info/SoQt1.
  - Fix broken handling of non-utf8 sources.

  * Thu Dec 15 2022 Ralf Cors??pius  - 1.6.0-11
  - Switch off HTML_TIMESTAMPs.


Package:  ansible-collection-chocolatey-chocolatey-1.4.0-1.fc38
Old package:  ansible-collection-chocolatey-chocolatey-1.3.0-2.fc37
Summary:  Ansible collection for Chocolatey
RPMs: ansible-collection-chocolatey-chocolatey
Size: 52.81 KiB
Size change:  -1.20 KiB
Changelog:
  * Fri Dec 16 2022 Orion Poplawski  - 1.4.0-1
  - Update to 1.4.0
  - Use current ansible collection packaging style
  - Use SPDX License tag


Package:  ansible-lint-1:6.10.0-1.fc38
Old package:  ansible-lint-1:6.9.1-1.fc38
Summary:  Best practices checker for Ansible
RPMs: python3-ansible-lint
Size: 504.64 KiB
Size change:  16.78 KiB
Changelog:
  * Wed Dec 14 2022 Maxwell G  - 1:6.10.0-1
  - Update to 6.10.0.


Package:  archlinux-keyring-20221213-1.fc38
Old package:  archlinux-keyring-20221123-1.fc38
Summary:  GPG keys used by Arch distribution to sign packages
RPMs: archlinux-keyring
Size: 1.12 MiB
Size change:  7.82 KiB
Changelog:
  * Thu Dec 15 2022 Frantisek Sumsal  20221123-2
  - Run integrity & consistency checks

  * Thu

Re: F39 proposal: Replace DNF with DNF5 (System-Wide Change proposal)

[Jaroslav Mracek]

I've rewritten the proposal to make it clear what it is about including 
additional information that were unknown before. I hope that I've addressed 
community suggestions and remove the confusion with original proposal. Please 
feel free to comment the new proposal and discuss the new content of the 
proposal.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Linking problem with ncurses on rawhide, not f37

[Miroslav Lichvar]

On Fri, Dec 16, 2022 at 09:55:11AM +0100, Florian Weimer wrote:
> Miroslav, we may have to revert the versioning change if the AS_NEEDED
> approach does not work.

Ok, I reverted that change, at least until I have more time for
testing the possible fixes.

>   Linking versioned libncurses against
> unversioned libtinfo etc. would solve this, but I don't know how it
> would to get to this point.

I don't know much about ELF. Is it possible to remove versions from
specific symbols in the symbol table after the libraries are built,
maybe with some tool like chrpath?

-- 
Miroslav Lichvar
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F39 proposal: Replace DNF with DNF5 (System-Wide Change proposal)

[Dominik 'Rathann' Mierzejewski]

On Wednesday, 23 November 2022 at 11:38, Jaroslav Mracek wrote:
[...]
> > I understand that deprecation warning has their own issues, but if you 
> > already put some thoughts into that topic, I'd like you to elaborate 
> > more then just provide statements like above.
> 
> DNF in early versions (1.1) provided a warning when `yum` was called.
> It was nice and transparent way how to send a message about
> redirection to DNF, but we got very strong negative feedback about
> that, therefore we removed it. I don't think we should repeat that
> approach. Personally I don't feel comfortable with education of our
> users using warnings, because they have value at first occurrence but
> then they are annoying.

Why don't you make them one-time only, then? I.e. drop a file in user's
home directory, e.g. ~/.config/dnf5/dnf-warning-displayed or something
and not display the warning if the file is there.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: colorful license change

[Kevin Kofler via devel]

Artur Frenszek-Iwicki wrote:
> colorful had a new major release, v2.0, which brought in a licensing
> change. I took this as an opportunity to also migrate the License: tags to
> SPDX.
> 
> Old v1.3 license: zlib with acknowledgement
> 
> New v2.0 licenses:
> - colorful: GPL-3.0-only AND (MPL-2.0 OR Zlib)
> - colorful-data: zlib-acknowledgement

In case people wonder (as I did): This is a leaf package:
https://svgames.pl/en/down
https://github.com/suve/LD25/
> Colorful is a simple 2D side-shooter game
so the license change to a more restrictive license should not be an issue.

Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Linking problem with ncurses on rawhide, not f37

[Ron Olson]

If you’re interested in testing any changes/fixes with Swift, you can 
use my Swift-for-Fedora repo 
(https://github.com/tachoknight/swift-lang-packaging-fedora). 
`setup-container.sh` does what you think it does in case you’re using 
podman or docker, and `justbuild.sh` actually does all the work to 
actually create the artifacts.


Hope that helps!

Ron

On 16 Dec 2022, at 5:24, Miroslav Lichvar wrote:


On Fri, Dec 16, 2022 at 09:55:11AM +0100, Florian Weimer wrote:
Miroslav, we may have to revert the versioning change if the 
AS_NEEDED

approach does not work.


Ok, I reverted that change, at least until I have more time for
testing the possible fixes.


  Linking versioned libncurses against
unversioned libtinfo etc. would solve this, but I don't know how it
would to get to this point.


I don't know much about ELF. Is it possible to remove versions from
specific symbols in the symbol table after the libraries are built,
maybe with some tool like chrpath?

--
Miroslav Lichvar___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Self Introduction: Hussein K.

[h-k-81]

Hello everyone


This mail should serve as my self introduction to the devel community.

I am a (soon to be) computer science graduate, that has been working
in the Linux / open source world for about 6 years. I first started working
as a python developer in the GIS (geographic information system) domain.
After some time I also began to perform some system administration tasks.
And before I knew I started to do a bit of everything.
So to describe my current work, I do

- Python development
- System administration
- Kubernetes administration (or whatever you want to call it)
- A little bit of javascript
- Devops (Automatic deployments via CI / CD pipelines, mainly using 
Gitlab CI)


Oh, I also picked up rust a couple years ago and have been using it for 
Uni and

private projects.

Now the reason for why I want to get more involved in the Fedora package 
maintainer community
is because I want to get a better understanding on how applications are 
packaged and

distributed to end-users in a secure and stable manner.
And from my experience, the best way to learn, is to get your hands dirty.
Naturally, I also want to give back to the community, that has doing amazing
work at developing Fedora and keeping everything working, and I want to 
become a part of it.



In the last week, I have been reading a lot of documentation on RPM 
packaging

and I have created my first package. I am currently looking for a sponsor
to help me with my first package review: 
https://bugzilla.redhat.com/show_bug.cgi?id=2154124



This concludes my introduction and I hope this was not too much to read :D


Best wishes
Hussein K.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Accidental conflicting packages: python mysql client

[Richard Shaw]

On Thu, Dec 15, 2022 at 11:57 AM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:

> On Mon, Dec 12, 2022 at 09:57:01PM -0600, Richard Shaw wrote:
> > There's a python-mysql and python-mysqlclient packages and it's been an
> > issue for a while but now causing upgrade issues.
> >
> > Can we get some help in BZ:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1929101
> >
> > Please make sure I have not mis-spoken.
>
> Yes, Obsoletes/Provides should be added. This can (and should) be done
> even in released Fedora (36, 37), and then the old package retired.
> Since this is causing problems during upgrade paths, it'd be great to
> do this quickly.
>
> Please let me know if you need some provenpackager help.
>

I'm PP as well, but it looked like the package owners were somewhat
involved in the BZ ticket so I was hesitant to interfere, but that hasn't
led to action as of yet...

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

SPDX Statistics - Advent edition

[Miroslav Suchý]

16 days ago we had:


23084  spec files in Fedora

> 29041 license tags in all spec files
24865  tags have not been converted to SPDX yet - it is much higher compared to previous run because last time my script 

actually counted packages instead of tags.
> 10325 tags can be trivially converted using `license-fedora2spdx`

Today we have:

23148 spec files in Fedora

29121 license tags in all spec files

24483 tags have not been converted to SPDX yet

10099 tags can be trivially converted using `license-fedora2spdx`

This is for the the first time I did not make any change in the counting script. So the change from 24865 to 24483 gives 
us 382 converted packages in last two weeks. Just in Fedora's dist-git. I am aware that some conversions happens in 
upstream and will take some time to propagate to downstream.


The list of packages needed to be converted is again here:

https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-final.txt

Any question? Please check

https://fedoraproject.org/wiki/Changes/SPDX_Licenses_Phase_1#Questions_from_the_mailing_list_discussion

Miroslav
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Self Introduction: Hussein K.

[Sandro Mani]

Welcome!

On 16.12.22 15:15, h-k...@hotmail.com wrote:

Hello everyone


This mail should serve as my self introduction to the devel community.

I am a (soon to be) computer science graduate, that has been working
in the Linux / open source world for about 6 years. I first started 
working

as a python developer in the GIS (geographic information system) domain.
After some time I also began to perform some system administration tasks.
And before I knew I started to do a bit of everything.
So to describe my current work, I do

- Python development
- System administration
- Kubernetes administration (or whatever you want to call it)
- A little bit of javascript
- Devops (Automatic deployments via CI / CD pipelines, mainly using 
Gitlab CI)


Oh, I also picked up rust a couple years ago and have been using it 
for Uni and

private projects.

Now the reason for why I want to get more involved in the Fedora 
package maintainer community
is because I want to get a better understanding on how applications 
are packaged and

distributed to end-users in a secure and stable manner.
And from my experience, the best way to learn, is to get your hands 
dirty.
Naturally, I also want to give back to the community, that has doing 
amazing
work at developing Fedora and keeping everything working, and I want 
to become a part of it.



In the last week, I have been reading a lot of documentation on RPM 
packaging

and I have created my first package. I am currently looking for a sponsor
to help me with my first package review: 
https://bugzilla.redhat.com/show_bug.cgi?id=2154124



This concludes my introduction and I hope this was not too much to 
read :D



Best wishes
Hussein K.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: SPDX Statistics - Advent edition

[Richard Shaw]

On Fri, Dec 16, 2022 at 8:52 AM Miroslav Suchý  wrote:

> The list of packages needed to be converted is again here:
>
>
> https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-final.txt
>

I appreciate the effort so I hate to ask, but can we get a similar list but
grouped by maintainer? I don't have a lot of free time these days and it
would make my life easier :)

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: SPDX Statistics - Advent edition

[Miroslav Suchý]

Dne 16. 12. 22 v 15:59 Richard Shaw napsal(a):
I appreciate the effort so I hate to ask, but can we get a similar list but grouped by maintainer? I don't have a lot 
of free time these days and it would make my life easier :)


I can write it on my TODO list.

At the same time - this is for sure already present in bunch of other scripts. If anyone can point me to the code I can 
copy then you make my life easier. (ie. function that gets maintainers for given package name).


Miroslav
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Self Introduction: Hussein K.

[Peter Lemenkov]

Hello!
It's always nice for me to see more people with GIS background!

On Fri, Dec 16, 2022 at 3:16 PM  wrote:
>
> Hello everyone
>
>
> This mail should serve as my self introduction to the devel community.
>
> I am a (soon to be) computer science graduate, that has been working
> in the Linux / open source world for about 6 years. I first started working
> as a python developer in the GIS (geographic information system) domain.
> After some time I also began to perform some system administration tasks.
> And before I knew I started to do a bit of everything.
> So to describe my current work, I do
>
> - Python development
> - System administration
> - Kubernetes administration (or whatever you want to call it)
> - A little bit of javascript
> - Devops (Automatic deployments via CI / CD pipelines, mainly using
> Gitlab CI)
>
> Oh, I also picked up rust a couple years ago and have been using it for
> Uni and
> private projects.
>
> Now the reason for why I want to get more involved in the Fedora package
> maintainer community
> is because I want to get a better understanding on how applications are
> packaged and
> distributed to end-users in a secure and stable manner.
> And from my experience, the best way to learn, is to get your hands dirty.
> Naturally, I also want to give back to the community, that has doing amazing
> work at developing Fedora and keeping everything working, and I want to
> become a part of it.
>
>
> In the last week, I have been reading a lot of documentation on RPM
> packaging
> and I have created my first package. I am currently looking for a sponsor
> to help me with my first package review:
> https://bugzilla.redhat.com/show_bug.cgi?id=2154124
>
>
> This concludes my introduction and I hope this was not too much to read :D
>
>
> Best wishes
> Hussein K.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 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/devel@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue



-- 
With best regards, Peter Lemenkov.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [Fedocal] Reminder meeting : ELN SIG

[Stephen Gallagher]

On Thu, Dec 15, 2022 at 9:40 AM Stephen Gallagher  wrote:
>
> On Thu, Dec 15, 2022 at 7:00 AM  wrote:
> >
> > Dear all,
> >
> > You are kindly invited to the meeting:
> >ELN SIG on 2022-12-16 from 12:00:00 to 13:00:00 US/Eastern
> >At fedora-meet...@irc.libera.chat
> >
> > The meeting will be about:
> >
>
> Current Agenda Items:
>
> The Final Countdown: We are down to only 15 failed builds in ELN. How
> do we get that to zero?


=
#fedora-meeting: ELN (2022-12-16)
=


Meeting started by sgallagh at 17:00:07 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2022-12-16/eln.2022-12-16-17.00.log.html
.



Meeting summary
---
* init process  (sgallagh, 17:00:07)

* The Final Countdown  (sgallagh, 17:04:22)
  * We probably need rust-rav1e for RHEL 10, the others unlikely.
(sgallagh, 17:12:51)
  * We're fairly confident that six of the remaining seven packages will
not be in RHEL 10, so we'll engage with the maintainers to get that
cleaned up  (sgallagh, 17:30:48)

* Open Floor  (sgallagh, 17:33:17)
  * Thank you to everyone who got involved with ELN this year. It has
been a tremendous success and every one of you were a part of that!
(sgallagh, 17:34:18)
  * outstanding ELN PRs:  (yselkowitz[m], 17:36:21)
  * LINK: https://src.fedoraproject.org/rpms/rsyslog/pull-request/35
(yselkowitz[m], 17:36:23)
  * LINK:
https://src.fedoraproject.org/rpms/texlive-base/pull-request/10
(yselkowitz[m], 17:36:38)
  * LINK: https://src.fedoraproject.org/rpms/unbound/pull-request/9
(yselkowitz[m], 17:36:40)
  * LINK:
https://src.fedoraproject.org/rpms/xorg-x11-drv-vmware/pull-request/1
(yselkowitz[m], 17:36:48)
  * LINK: https://src.fedoraproject.org/rpms/ruby/pull-request/143
(yselkowitz[m], 17:36:58)
  * LINK:
https://src.fedoraproject.org/rpms/python-cryptography/pull-request/18
(yselkowitz[m], 17:37:19)
  * LINK: https://pagure.io/releng/issue/11186   (yselkowitz[m],
17:37:34)
  * The above tickets may be merged and built by a provenpackager if the
maintainer has not responded.  (sgallagh, 17:39:12)

Meeting ended at 17:46:23 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* sgallagh (64)
* yselkowitz[m] (44)
* zodbot (9)
* tdawson (9)
* yselkowitz (0)




Generated by `MeetBot`_ 0.4

.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

duktape soname bump

[Frantisek Zatloukal]

I wish I could write that I am going to build duktape 2.7.0 which bumps the
soname. However, my brain kind of misfired and I didn't, for some reason,
announce this upfront. The changes are minor, ABI changing stuff, I've
taken care of rebuilding all the dependencies (main maintainers of those
are in BCC):
- gerbera
- libproxy
- polkit
- python-dukpy

I am terribly sorry if it caused any trouble. I'll pay far more attention
to announce bumps before next time!

-- 

Best regards / S pozdravem,

František Zatloukal
Senior Quality Engineer
Red Hat
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Linking problem with ncurses on rawhide, not f37

[Florian Weimer]

* Miroslav Lichvar:

> On Fri, Dec 16, 2022 at 09:55:11AM +0100, Florian Weimer wrote:
>>   Linking versioned libncurses against
>> unversioned libtinfo etc. would solve this, but I don't know how it
>> would to get to this point.
>
> I don't know much about ELF. Is it possible to remove versions from
> specific symbols in the symbol table after the libraries are built,
> maybe with some tool like chrpath?

It's an allocated section, and patching those is always a bit tricky.
In this case, we'd remove data from it, so it might work.  I'm still on
the fence whether we should have some form of proper link editor support
for that, or if it's too obscure to matter.

Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora elections voting now open

[Ben Cotton]

Remember that voting in the Fedora Linux 37 elections is open through
23:59 UTC on Thursday 22 December. Go to the Elections app[1] to cast
your vote. Voting closes at 23:59 UTC on Thursday 22 December. Don't
forget to claim your "I Voted" badge when you cast your ballot. Links
to candidate interviews are in the Elections app and on the Community
Blog[2].

[1] https://elections.fedoraproject.org/
[2] https://communityblog.fedoraproject.org/f37-elections-voting-now-open/

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
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/devel-annou...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: MuseScore 4.0

[Iñaki Ucar]

On Thu, 15 Dec 2022 at 19:40, Jerry James  wrote:
>
> MuseScore is music composition and notation software, currently
> available from Fedora in the mscore package. Version 4.0 was just
> released.  If anybody would like to try it out, it is available from
> this COPR: https://copr.fedorainfracloud.org/coprs/jjames/MuseScore4/.
> I do not intend to build for Fedora until some issues have been worked
> out.

Thanks for this! Testing while watching the latest Tantacrul video. :)

> WARNING!  WARNING!  WARNING!
> DO NOT TRY THIS IN A WAYLAND SESSION. It will run for anywhere from a
> few seconds to a few minutes, then abruptly exit with a "Protocol
> error".  Run an X session to try MuseScore 4.0.
> WARNING!  WARNING!  WARNING!
>
> WARNING!  WARNING!  WARNING!
> Configuration for MuseScore 3.x and 4.x differs in some important
> respects.  You may have to do a "factory reset" when switching
> versions.  Run "mscore -R" or "mscore -F" if it won't start.  This
> will clear out your list of recently opened scores, for example, so
> backup your configuration before you do this.
> WARNING!  WARNING!  WARNING!
>
> To try it out, run:
>
> sudo dnf copr enable jjames/MuseScore4
> sudo dnf install musescore
>
> Please try the video export option, which has bitrotted upstream. I
> have attempted to update it for current ffmpeg. Please let me know if
> it does or does not work for you. If it works well, I will submit my
> patch upstream.  Do this: "mscore --score-video  -o
> filename.mp4", and optionally try the --resolution and --fps
> arguments.  Run "mscore --help" for more information.  This
> functionality does not seem to be available via the GUI.
>
> Upstream bundles fluidsynth, apparently for the sole purpose of
> implementing a caching soundfont loader that uses internal fluidsynth
> APIs. I have unbundled fluidsynth for this repository, which means
> there is no soundfont cache. If you switch soundfonts frequently,
> please let me know if the performance is acceptable. If you are
> familiar with the fluidsynth API and can implement a caching soundfont
> loader using only public APIs, please do so and submit it upstream.

Unfortunately, the playback seems to be broken. The mixer doesn't show
SoundFonts and there's no audio at all. :(

Iñaki

> Several other products are bundled (beatroot-vamp, dtl, intervaltree,
> rtf2html, and KDDockWidgets).  Each of them has either been altered by
> the MuseScore developers or, in the case of KDDockWidgets, internal
> APIs are used so extensively that I cannot see how to unbundle
> successfully.  Thoughts on how any of these products might be
> unbundled are welcome.
>
> The COPR version makes a long-requested change: the package name
> changes from mscore to musescore.  Let me know if you encounter any
> problems arising from that change.
>
> A new font package is needed to build version 4.0 for Fedora.  I would
> appreciate a review from anybody who feels competent to review a font
> package: https://bugzilla.redhat.com/show_bug.cgi?id=2152347.  There
> is a question about the appropriate foundry name.  If you can help
> answer that question, please chime in.
>
> Regards,
> --
> Jerry James
> http://www.jamezone.org/
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 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/devel@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue



-- 
Iñaki Úcar
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Looking for advice - ffmpeg-free and wf-recorder

[Bob Hepple]

I am the packager for wf-recorder (a wl-roots/wayland screen recorder)
which presently resides in rpmfusion - it uses proprietary ffmpeg codecs by
default (libx246).

Now that we have ffmpeg-free we have an opportunity to move wf-recorder to
the mainstream and change the default codec to the non-proprietary
libopenh264. This woud be in rawhide/f38 and on.

This all works fine in testing on f37. The fly in the ointment is that if
ffmpeg/rpmfusion is installed in place of ffmpeg-free, then wf-recorder can
no longer access libopenh264 and fails with an error. There is a workaround
in the use of the option -c libx264.

Several solutions occur to me and I'm looking for guidance on which path to
take:

0. leave wf-recorder where it is, in rpmfusion as in f37 and earlier.
A. compile wf-recorder as shipped by upstream with the default libx264 -
the '-c libopenh264' workaround would be needed if ffmpeg-free is
installed. This annoys users who install stock fedora.
B. compile wf-recorder with libopenh264 as the default - the '-c libx264'
workaround would be needed if ffmpeg/rpmfusion is installed and would annoy
those users.
C. leave wf-recorder in rpmfusion and create a wf-recorder-free package by
analogy to ffmpeg (this might be obscure as it's not likely to get much
publicity - and annoy everyone sooner or later)
D. the best option might be to choose a codec common to both ffmpeg and
ffmpeg-free. I'm not terribly au fait with the various codecs so which
would I choose? These codecs appear to be in both packages:

 h263_v4l2m2m V4L2 mem2mem H.263 encoder wrapper (codec h263)
 h264_amf AMD AMF H.264 Encoder (codec h264)
 h264_nvenc   NVIDIA NVENC H.264 encoder (codec h264)
 h264_qsv H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (Intel
Quick Sync Video acceleration) (codec h264)
 h264_v4l2m2m V4L2 mem2mem H.264 encoder wrapper (codec h264)
 h264_vaapi   H.264/AVC (VAAPI) (codec h264)
 hevc_amf AMD AMF HEVC encoder (codec hevc)
 hevc_nvenc   NVIDIA NVENC hevc encoder (codec hevc)
 hevc_qsv HEVC (Intel Quick Sync Video acceleration) (codec
hevc)
 hevc_v4l2m2m V4L2 mem2mem HEVC encoder wrapper (codec hevc)
 hevc_vaapi   H.265/HEVC (VAAPI) (codec hevc)
 libaom-av1   libaom AV1 (codec av1)
libopenjpeg  OpenJPEG JPEG 2000 (codec jpeg2000)
 librav1e librav1e AV1 (codec av1)
 libsvtav1SVT-AV1(Scalable Video Technology for AV1) encoder
(codec av1)
 libtheoralibtheora Theora (codec theora)
 libvpx   libvpx VP8 (codec vp8)
 libvpx-vp9   libvpx VP9 (codec vp9)
 libwebp_anim libwebp WebP image (codec webp)
 libwebp  libwebp WebP image (codec webp)
 mjpeg_qsvMJPEG (Intel Quick Sync Video acceleration) (codec
mjpeg)
 mjpeg_vaapi  MJPEG (VAAPI) (codec mjpeg)
 mpeg2_qsvMPEG-2 video (Intel Quick Sync Video acceleration)
(codec mpeg2video)
 mpeg2_vaapi  MPEG-2 (VAAPI) (codec mpeg2video)
 mpeg4_v4l2m2mV4L2 mem2mem MPEG4 encoder wrapper (codec mpeg4)
 vp8_v4l2m2m  V4L2 mem2mem VP8 encoder wrapper (codec vp8)
 vp8_vaapiVP8 (VAAPI) (codec vp8)
 vp9_qsv  VP9 video (Intel Quick Sync Video acceleration)
(codec vp9)
 vp9_vaapiVP9 (VAAPI) (codec vp9)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Looking for advice - ffmpeg-free and wf-recorder

[Samuel Sieb]

On 12/16/22 21:29, Bob Hepple wrote:
I am the packager for wf-recorder (a wl-roots/wayland screen recorder) 
which presently resides in rpmfusion - it uses proprietary ffmpeg codecs 
by default (libx246).


Now that we have ffmpeg-free we have an opportunity to move wf-recorder 
to the mainstream and change the default codec to the non-proprietary 
libopenh264. This woud be in rawhide/f38 and on.


This all works fine in testing on f37. The fly in the ointment is that 
if ffmpeg/rpmfusion is installed in place of ffmpeg-free, then 
wf-recorder can no longer access libopenh264 and fails with an error. 
There is a workaround in the use of the option -c libx264.


Several solutions occur to me and I'm looking for guidance on which path 
to take:


0. leave wf-recorder where it is, in rpmfusion as in f37 and earlier.
A. compile wf-recorder as shipped by upstream with the default libx264 - 
the '-c libopenh264' workaround would be needed if ffmpeg-free is 
installed. This annoys users who install stock fedora.
B. compile wf-recorder with libopenh264 as the default - the '-c 
libx264' workaround would be needed if ffmpeg/rpmfusion is installed and 
would annoy those users.
C. leave wf-recorder in rpmfusion and create a wf-recorder-free package 
by analogy to ffmpeg (this might be obscure as it's not likely to get 
much publicity - and annoy everyone sooner or later)
D. the best option might be to choose a codec common to both ffmpeg and 
ffmpeg-free. I'm not terribly au fait with the various codecs so which 
would I choose? These codecs appear to be in both packages:


Can you have it try the alternate codec if the first option fails to load?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Looking for advice - ffmpeg-free and wf-recorder

[Aleksei Bavshin]

On 12/16/22 21:29, Bob Hepple wrote:
I am the packager for wf-recorder (a wl-roots/wayland screen recorder) 
which presently resides in rpmfusion - it uses proprietary ffmpeg codecs 
by default (libx246).


Now that we have ffmpeg-free we have an opportunity to move wf-recorder 
to the mainstream and change the default codec to the non-proprietary 
libopenh264. This woud be in rawhide/f38 and on.


Thanks for considering that!
f37 would be nice too. ffmpeg-free is available in this release, so 
nothing prevents moving wf-recorder to Fedora 37 repos.



This all works fine in testing on f37. The fly in the ointment is that 
if ffmpeg/rpmfusion is installed in place of ffmpeg-free, then 
wf-recorder can no longer access libopenh264 and fails with an error. 
There is a workaround in the use of the option -c libx264.


Several solutions occur to me and I'm looking for guidance on which path 
to take:


0. leave wf-recorder where it is, in rpmfusion as in f37 and earlier.
A. compile wf-recorder as shipped by upstream with the default libx264 - 
the '-c libopenh264' workaround would be needed if ffmpeg-free is 
installed. This annoys users who install stock fedora.
B. compile wf-recorder with libopenh264 as the default - the '-c 
libx264' workaround would be needed if ffmpeg/rpmfusion is installed and 
would annoy those users. > C. leave wf-recorder in rpmfusion and create a wf-recorder-free package
by analogy to ffmpeg (this might be obscure as it's not likely to get 
much publicity - and annoy everyone sooner or later)


Option C sounds like too much maintenance burden for a default option value.

D. the best option might be to choose a codec common to both ffmpeg and 
ffmpeg-free. I'm not terribly au fait with the various codecs so which 
would I choose? These codecs appear to be in both packages:


  h263_v4l2m2m         V4L2 mem2mem H.263 encoder wrapper (codec h263)
  h264_amf             AMD AMF H.264 Encoder (codec h264)
  h264_nvenc           NVIDIA NVENC H.264 encoder (codec h264)
  h264_qsv             H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (Intel 
Quick Sync Video acceleration) (codec h264)

  h264_v4l2m2m         V4L2 mem2mem H.264 encoder wrapper (codec h264)
  h264_vaapi           H.264/AVC (VAAPI) (codec h264)
  hevc_amf             AMD AMF HEVC encoder (codec hevc)
  hevc_nvenc           NVIDIA NVENC hevc encoder (codec hevc)
  hevc_qsv             HEVC (Intel Quick Sync Video acceleration) (codec 
hevc)

  hevc_v4l2m2m         V4L2 mem2mem HEVC encoder wrapper (codec hevc)
  hevc_vaapi           H.265/HEVC (VAAPI) (codec hevc)
  libaom-av1           libaom AV1 (codec av1)
libopenjpeg          OpenJPEG JPEG 2000 (codec jpeg2000)
  librav1e             librav1e AV1 (codec av1)
  libsvtav1            SVT-AV1(Scalable Video Technology for AV1) 
encoder (codec av1)

  libtheora            libtheora Theora (codec theora)
  libvpx               libvpx VP8 (codec vp8)
  libvpx-vp9           libvpx VP9 (codec vp9)
  libwebp_anim         libwebp WebP image (codec webp)
  libwebp              libwebp WebP image (codec webp)
  mjpeg_qsv            MJPEG (Intel Quick Sync Video acceleration) 
(codec mjpeg)

  mjpeg_vaapi          MJPEG (VAAPI) (codec mjpeg)
  mpeg2_qsv            MPEG-2 video (Intel Quick Sync Video 
acceleration) (codec mpeg2video)

  mpeg2_vaapi          MPEG-2 (VAAPI) (codec mpeg2video)
  mpeg4_v4l2m2m        V4L2 mem2mem MPEG4 encoder wrapper (codec mpeg4)
  vp8_v4l2m2m          V4L2 mem2mem VP8 encoder wrapper (codec vp8)
  vp8_vaapi            VP8 (VAAPI) (codec vp8)
  vp9_qsv              VP9 video (Intel Quick Sync Video acceleration) 
(codec vp9)

  vp9_vaapi            VP9 (VAAPI) (codec vp9)



I'm not an expert enough to tell what to choose, but at least I can tell 
what should be avoided:


 - anything h264 or HEVC - these are patented and Fedora won't ship a 
software implementation of the encoder for these. (except libopenh264, 
but OSTree-based systems won't have even that).
 - anything with words vaapi, qsv, v4l2m2m or amf - these only work 
with a specific hardware

 - image formats - jpeg or webp might be a bad choice for a screen recorder

Next I'm going to suggest to exclude Theora (a bit outdated) and AV1 
(which is _slow_ and less widespread, especially in hw decoders).


Huh, that leaves us with VP8 and VP9. I don't know how these compare in 
real-time encoding speed but I hope that VP9 encoder is fast enough for 
hardware released after 2013 :)


Please, also consult with the upstream - wf-recorder includes default 
parameters for libx264/libx265[1], so they could add a good preset for a 
royalty-free encoder.


[1]: 
https://github.com/ammen99/wf-recorder/blob/master/src/frame-writer.cpp#L47



___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: