> On Wed, May 15, 2024 at 6:23 PM Leigh Scott wrote:
>
> Does this mean "I'm against it" or "it would involve retiring two
> legacy NVidia driver packages"?
>
> Fabio
I'm indifferent to the legacy drivers.
--
_
> This message is meant as a heads up because I am considering upgrading
> Xwayland to version 24.1.0 in Fedora 40.
+1 for this in f40.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
> On Wed, May 15, 2024 at 4:31 PM Olivier Fourdan wrote:
>
> Not directly related, but hopefully not entirely off-topic:
> Are there plans to update the xorg-x11-server package itself to the
> new stable branch too?
>
> It's been stuck on the 1.20.14 release for a long time (on the last
>
+1 for adding this to f40, nvidia-470xx goes EOL September 2024.
> This message is meant as a heads up because I am considering upgrading
> Xwayland to version 24.1.0 in Fedora 40.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To
> Hi everyone,
>
> I'm revisting the topic of rpmautospec because I was doing some work
> on various packages, and it's annoying that some packages are using
> rpmautospec and others are not.
>
> All my packages have been converted, so in day-to-day work, I don't
> even think about %changelog.
I have untagged the latest nvidia 304xx builds for f40+ due to gcc-14
build failure.
On 28/03/2024 21:17, Nicolas Chauvet via rpmfusion-developers wrote:
Le mar. 26 mars 2024 à 16:16, Nicolas Chauvet a écrit :
Hi there,
Just a reminder that the final freeze is in one week (and this
Why didn't the cunt inform us instead of wasting my fucking time!
On 26/03/2024 07:31, Dominik 'Rathann' Mierzejewski via
rpmfusion-developers wrote:
On Tuesday, 26 March 2024 at 01:44, Leigh Scott wrote:
commit 18bfd88a84df92c3efb1d7729eab367a85247230
Author: Leigh Scott
Date: Tue Mar
F40 build is also dropped.
I think we should also consider compat-ffmep4 future.
On 23/03/2024 13:04, Sérgio Basto wrote:
And in F40 ? compat-ffmpeg5 will be dropped also ?
On Sat, 2024-03-23 at 13:00 +0100, Leigh Scott wrote:
commit b9f004a649292480fd6649f0123ca275b4cad6f1
Author: Leigh
Kodi is in a pitiful state due to their stale code, version 20 isn't a
good fit for any current fedora release.
1: it needs a dead ffmpeg version, I had to drop nvdec support recently.
2: it isn't compatible with current python without patching.
3: because of 2# the downloaded plugins aren't
+1 for new kodi for f40+, maybe f39 can be added later.
-1 for adding GLES
On 12/03/2024 04:12, Michael Cronenworth via rpmfusion-developers wrote:
Hi all,
Kodi 21 has its first release candidate now available.
Key features:
- HDR (It works, I've tested it!)
- Better Pipewire support
-
What is missing?
> Other then some missing RPMFusion packages
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
I have untagged the FTI packages.
1: EmptyEpsilon
2: etlegacy
package: EmptyEpsilon-2021.06.23-6.fc40.x86_64 from
rpmfusion-nonfree-rawhide
unresolved deps (5):
libsfml-audio.so.2.5()(64bit)
libsfml-graphics.so.2.5()(64bit)
libsfml-network.so.2.5()(64bit)
> Thanks for holding the push to testing, I have managed to patch nvidia 545.xx
> and
> 550.xx so
470.xx is also patched.
I think it is ok to push the new kernel to testing, the legacy nvidia drivers
shouldn't hold up the new kernel.
--
___
devel
> On Thu, Feb 1, 2024 at 1:45 AM Leigh Scott wrote:
>
> This is not accurate. The 6.7.3 (and 6.6.15) updates did break the
> nvidia driver. It has nothing to do with debugging being enabled. A
> proper and valid bugfix:
>
> 5ec8e8ea8b7783fab150cf86404fc38cb4db8800 m
> I can support that.
>
> But am I supposed to ignore the fact that kkofler is already bullying the KDE
> SIG into not
> breaking that one other package they maintain that occasionally breaks on kde
> updates? See
> example: https://bodhi.fedoraproject.org/updates/FEDORA-2023-977de87584
>
> Am
Kernel-6.7.3 still has debugging enabled which will break the nvidia driver
https://bugzilla.rpmfusion.org/show_bug.cgi?id=6859
https://forums.developer.nvidia.com/t/linux-6-7-beta-550-40-07-error-modpost-gpl-incompatible-module-nvidia-ko-uses-gpl-only-symbol-rcu-read-lock/280908
--
Have you looked at other distros to see how they worked around the flaws in the
upstream code?
https://gitlab.archlinux.org/archlinux/packaging/packages/materialx/-/blob/main/PKGBUILD?ref_type=heads#L32
--
___
devel mailing list --
> P.S.: opening three threads for a single thing with identical text is
> not nice. It can confuse archive readers, not finding answers they
> might be looking for. Try to avoid that in the future, please.
Chromium did the duplicates :-(
--
___
devel
I have unpushed the f38 build.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-68a2dba357
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
see https://github.com/GNOME/gtk/commit/77ebdd85091833a7869ece48c3114fa6d9966321
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Why isn't gtk3 a critical path package?
https://bugzilla.redhat.com/show_bug.cgi?id=2260068
https://bugzilla.redhat.com/show_bug.cgi?id=2260073
https://bugzilla.redhat.com/show_bug.cgi?id=2260074
https://bodhi.fedoraproject.org/updates/FEDORA-2024-5d8ac182bf
--
Why isn't gtk3 a critical path package?
https://bugzilla.redhat.com/show_bug.cgi?id=2260068
https://bugzilla.redhat.com/show_bug.cgi?id=2260073
https://bugzilla.redhat.com/show_bug.cgi?id=2260074
https://bodhi.fedoraproject.org/updates/FEDORA-2024-5d8ac182bf
--
Why isn't gtk3 a critical path package?
https://bugzilla.redhat.com/show_bug.cgi?id=2260068
https://bugzilla.redhat.com/show_bug.cgi?id=2260073
https://bugzilla.redhat.com/show_bug.cgi?id=2260074
https://bodhi.fedoraproject.org/updates/FEDORA-2024-5d8ac182bf
--
> Try adding 'BuildRequires: gcc-c++' to the specfile
>
> checking for x86_64-redhat-linux-gcc... gcc
> checking whether the C compiler works... no
> configure: error: in `/builddir/build/BUILD/hello-2.10':
> configure: error: C compiler cannot create executables
> See `config.log' for more
Try adding 'BuildRequires: gcc-c++' to the specfile
checking for x86_64-redhat-linux-gcc... gcc
checking whether the C compiler works... no
configure: error: in `/builddir/build/BUILD/hello-2.10':
configure: error: C compiler cannot create executables
See `config.log' for more details
--
I'm -1 for this change, it shouldn't be enabled by default as it will cause
issues for users using router mac filtering.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
It's probably due to the load from regen tasks currently running.
On 18/12/2023 13:01, Richard Shaw via rpmfusion-developers wrote:
I'm trying to do a pull on nonfree/unifi in master and it took about 3
minutes to complete.
Thanks,
Richard
___
sassc
rubygem-hrx
rubygem-linked-list
--
___
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/
> On Fri, Nov 24, 2023 at 12:07 PM David King wrote:
> - Out of the 13 packages that seem correlated but don't show obvious errors
> directly related to libxml2, there are still some quite suspicious ones,
> like cinnamon which fails due to a missing xml file.
> [1]
Try adding this to the file
#include
--
___
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/
I have untagged the broken build
$ koji-rpmfusion untag-build f38-free-updates-testing
shotcut-23.11.04-1.fc38
On 19/11/2023 10:15, Dan Horák via rpmfusion-developers wrote:
Hello,
seems the shotcut-23.11.04-1.fc38 build has been done with qt6 version
6.5 in the buildroot, but qt6 has
I have reassigned the task
$ koji-rpmfusion assign-task -f 614378 buildppcle-01.osuosl.rpmfusion.net
assigned task 614378 to host buildppcle-01.osuosl.rpmfusion.net
On 20/10/2023 13:12, Richard Shaw via rpmfusion-developers wrote:
I'm working on updating unifi but the f39 package seems to be
I have this simple review pending if you interested.
https://bugzilla.redhat.com/show_bug.cgi?id=2213540
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Use whatever you like as I wont be migrating to the new infra!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
> Am 08.09.23 um 22:32 schrieb Michel Lind:
>
> Are you sure it's working?
>
> [root ~]# dnf --enablerepo=updates-archive list firefox*
> Letzte Prüfung auf abgelaufene Metadaten: vor 0:04:10 am Sa 09 Sep 2023
> 09:39:57 CEST.
> Installierte Pakete
> firefox.x86_64 117.0-1.fc37
> Hi Leigh,
>
> On Fri, Aug 25, 2023 at 10:03 AM Leigh Scott wrote:
>
>
> As I'm on my laptop again, I was able to try to run the rebase again and
> for Philip it was about rpmfusion-nonfree-updates, but I'm hitting:
>
> error: Updating rpm-md repo 'rpmfusion-free-u
Those warnings should disappear once the 39 release rpm's are installed.
I have fixed the missing repodata for the unused updates repo's.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
> just a note rpmfusion free and nofree not ready
>
>
What is the issue?
I branched rpmfusion repo two weeks ago
$ sudo repoclosure --check rpmfusion-free --check rpmfusion-nonfree
Last metadata expiration check: 1:27:59 ago on Thu 24 Aug 2023 17:14:49 BST.
package:
> just a note rpmfusion free and nofree not ready
>
>
What do you mean?
I branched rpmfusion two week ago, the repo deps look fine to me.
$ sudo repoclosure --check rpmfusion-free --check rpmfusion-nonfreetanita999fly
Last metadata expiration check: 1:07:49 ago on Thu 24 Aug 2023 17:14:49
> On Mon, Aug 14 2023 at 07:19:05 PM +0200, Jan Drögehoff
>
> Unfortunately yes. There is more info here:
>
> https://www.hadess.net/2023/08/new-responsibilities.html
>
> Red Hat has instructed us to stop work on several core desktop
> components. All of these components need new maintainers
I have already worked around the koji issue.
https://koji.rpmfusion.org/koji/externalrepoinfo?extrepoID=168
On 18/08/2023 08:35, Nicolas Chauvet wrote:
Le ven. 18 août 2023 à 09:08, Leigh Scott a écrit :
How does changing our proxy fix broken mock?
It will not fix mock, but it should
2023 à 08:46, Leigh Scott via rpmfusion-developers
a écrit :
You can't be serious, an empty repo doesn't count as working.
https://codecs.fedoraproject.org/openh264/40/x86_64/os/
I can workaround the problem in our proxy (to point to 39 until fixed).
I will remove open264 support from our
You can't be serious, an empty repo doesn't count as working.
https://codecs.fedoraproject.org/openh264/40/x86_64/os/
I will remove open264 support from our ffmpeg package if this fedora
repo isn't fixed by Monday, it doesn't bother me if I break the fdora
obs-studio package.
On
Test.
On 08/08/2023 15:31, Sérgio Basto via rpmfusion-developers wrote:
no problem
I have already resubmitted the builds and they are completed
Thank you
On Tue, 2023-08-08 at 13:19 +, Andrew Bauer wrote:
Thanks Sergio. I just left town for work and will resubmit after i
return.
These are either retired,
Package: openmw
or moved to fedora.
Package: vo-amrwbenc
On 04/08/2023 03:15, Sérgio Basto via rpmfusion-developers wrote:
Hi,
Mass rebuild for F39 is complete .
And we have this failures :
https://www.serjux.com/rpms/failed_to_build.html
Failed builds:
You probably got removed for inactivity, see
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/UG3UOKBVJLUWZYEHWL52KPMITPEPEBNF/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
I have orphaned tint2.
https://src.fedoraproject.org/rpms/tint2
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
So this change is for workstation iso only?, the other spins wont have this
unwanted change.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
> sudo dnf -y in lightdm-autologin-greeter
>
>
> [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
> [+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=5256
> [+0.00s] DEBUG: Loading configuration dirs from
> /usr/share/lightdm/lightdm.conf.d
> [+0.00s] DEBUG: Loading
> Fedora 38 Cinnamon Desktop - LIGHTDM.SERVICE FAIL.. after last
> update
> don't know how to fix it
>
> please fix / test / update ...
It works fine here.
I haven't updated lightdm since f38 release so I doubt the issue is caused by
lightdm.
You could bootstrap dnf for the rebuild
https://src.fedoraproject.org/rpms/dnf/blob/rawhide/f/dnf.spec#_298
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
I have solved it with this
https://src.fedoraproject.org/rpms/mint-themes/c/85835bb3515a68babd4795cd34585ab6aaf8ff11?branch=rawhide
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
It builds fine for f39 and f38 local builds, it fails for f38 koji and copr
builders.
https://koji.fedoraproject.org/koji/taskinfo?taskID=101949820
Installed (but unpackaged) file(s) found:
/usr/share/themes/Mint-X-Aqua/index.theme
/usr/share/themes/Mint-X-Blue/index.theme
at 13:08 +0100, Leigh Scott via rpmfusion-developers
wrote:
Do we really need to keep this legacy player around?
Are you going to fix issues like this?
I will try , I like have a fallback
https://bugzilla.rpmfusion.org/show_bug.cgi?id=6692
The bug was opened today
Upstream is virtually dead
Do we really need to keep this legacy player around?
Are you going to fix issues like this?
https://bugzilla.rpmfusion.org/show_bug.cgi?id=6692
Upstream is virtually dead.
https://git.ffmpeg.org/gitweb/mplayer.git/shortlog
On 30/05/2023 11:09, Sérgio Basto via rpmfusion-developers wrote:
> Il 24/05/23 09:40, Jaroslav Mracek ha scritto:
>
> I've started to see failing tests upon Bodhi update submission like the
> following:
>
> Error:
> Problem: conflicting requests
> - nothing provides pkgconfig(lz4;pugixml;zlib) needed by
> libXISF-devel-0.2.5-1.fc39.x86_64 from
Maybe
%global numjobs 1
___
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:
Maybe ask https://github.com/mesonbuild/mocklibc
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
> On Mon, Apr 10, 2023 at 12:16 AM Samuel Sieb
>
> So we have pushed a change in Fedora where there is no nice way for a user
> to workaround it except by complaining to a company that probably doesn't
> care what normal users (e.g. non-paying customers) care about?
You can set LEGACY if you
libheif has been retired at rpmfusion due to koji issues.
https://bugzilla.rpmfusion.org/show_bug.cgi?id=6626
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
I have orphaned hstr today.
https://src.fedoraproject.org/rpms/hstr
It is currently non-functional due to kernel-6.2 changes, see
https://github.com/dvorka/hstr/issues/478
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an
I never enabled vaapi support by default, users need to enable that
themselves as chromium support for it is a mess.
Fedora chromium enables it by default.
Version Information
Data exported
2023-03-30T10:46:18.434Z
Chrome version
Chrome/111.0.5563.146
Operating system
Linux
> xine-lib and libheif are both fedora packages.
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/YMOLJESUIIFK5RZYPGWTE362CKZH7JXV/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email
> Hello everyone,
>
> I am planning a soname bump of jpegxl to 0.8.1 next week Saturday the 25th.
>
> Some of you will be affected by these changes.
> RPMFusion side, the following packages are affected:
>
> libheif
> xine-lib
>
xine-lib and libheif are both fedora packages.
I have orphaned libheif at rpmfusion as I have no desire to manage another
split package.
https://admin.rpmfusion.org/pkgdb/package/free/libheif/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
I can give sponsorship and acl's for the rpmfusion package.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
> Hey all,
>
> ffmpeg is getting upgraded to 6.0 for Fedora Linux 38 and Rawhide in
> order to remain compatible with prominent third-party repositories.
>
Thank you for keeping up.
___
devel mailing list -- devel@lists.fedoraproject.org
To
google-chrome rpm caused issues due to it's SHA1 signature.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
I wont be using the API again due to the 30 day limit.
If they change the password requirement again I will dump redhat bugzilla!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
I don't think a +2 release upgrade is a valid test case, I believe f37
is SHA256 signed.
On 19/02/2023 22:41, Sérgio Basto via rpmfusion-developers wrote:
Hi,
I spent this weekend understanding why when update my vm to F38
branched I got a lot of [1] the key ID d651ff2e is "our" key
> Posted the rpmfusion bug here:
> https://bugzilla.rpmfusion.org/show_bug.cgi?id=6573
Try learning to wait patiently, branching isn't a simple process.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
rpmfusion-
developers wrote:
Le ven. 10 févr. 2023 à 02:33, Leigh Scott via rpmfusion-developers
a écrit :
Too late, rpmfusion is branched,
On 08/02/2023 23:13, Sérgio Basto via rpmfusion-developers wrote:
On Wed, 2023-02-08 at 12:56 +0100, Nicolas Chauvet via rpmfusion-
developers wrote
rpmfusion mass branching was completed yesterday.
On 10/02/2023 12:03, Sérgio Basto via rpmfusion-developers wrote:
why is too late , I just notice we already got
https://dl.fedoraproject.org/pub/fedora/linux/development/38/
so is just point our rawhide to f38 and do the mass rebuild , before
Too late, rpmfusion is branched,
On 08/02/2023 23:13, Sérgio Basto via rpmfusion-developers wrote:
On Wed, 2023-02-08 at 12:56 +0100, Nicolas Chauvet via rpmfusion-
developers wrote:
As fedora has branched already ('or close'), here is the plan for
rpmfusion.
I'm proposing that we skip the
Here's the new list of packages with broken deps.
[leigh@mpd-pc ~]$ sudo repoclosure --releasever rawhide --disablerepo=*
--enablerepo=fedora,rpmfusion-free,rpmfusion-nonfree --check
rpmfusion-free --check rpmfusion-nonfree
Fedora rawhide - x86_64 6.2 MB/s | 66 MB 00:10
RPM Fusion for
I doubt there is enough freespace left on the harddrive for a mass
rebuild and branching, maybe kwizart can do a cleanup first.
On 08/02/2023 23:13, Sérgio Basto via rpmfusion-developers wrote:
On Wed, 2023-02-08 at 12:56 +0100, Nicolas Chauvet via rpmfusion-
developers wrote:
As fedora has
You dropped the annobin fix when you rebased.
Fixed.
https://pkgs.rpmfusion.org/cgit/free/kodi.git/commit/?id=cbdf249756ff02d2a463c94f01c5e5e543281c28
Build.
https://koji.rpmfusion.org/koji/buildinfo?buildID=24648
On 17/01/2023 17:14, Michael Cronenworth via rpmfusion-developers wrote:
On
Maybe add this link to each README.md
https://www.paypal.com/paypalme/rpmfusion
On 09/01/2023 21:06, Nicolas Chauvet wrote:
Hi there,
This was bring to my attention recently but some
end-users/contributors seems to miss to find their way to the
bugzilla.rpmfusion.org to report issue.
Is
I haven't got the time to waste on mesa pushes and untags.
We need to change our package replacement policy.
On 02/01/2023 17:09, Gary Buhrmaster wrote:
I suspect in this case the most viable (although
very ugly) solution is for the freeworld packager(s)
to request the rpmfusion admins untag
-1 for this change.
I will ignore it if it's accepted.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
> On Tue, 2022-02-08 at 15:12 -0500, Adam Jackson wrote:
>
> X Display Manager with support for XDMCP, host chooser
>
> what are the alternatives of "Display Manager" ? and "with support for
> XDMCP" ? only gdm ?
>
> And xdm is not abandoned https://gitlab.freedesktop.org/xorg/app/xdm ,
>
0.2.7-8.fc37 fedora
On Sat, 2022-12-17 at 12:34 +0100, Leigh Scott wrote:
Summary of changes:
be2c66a... Bump Pipewire version (*)
(*) This commit already existed in another branch; no separate mail
sent
___
rpmfusion-commits mailing list
Scratch builds are disabled, use mock instead.
On 15/12/2022 14:45, Martin Gansser wrote:
Hi,
I want to create a koji-rpmfusion build, this fails with the error message
[martin@fedora SPECS]$ koji-rpmfusion build --scratch rawhide-free
../SRPMS/vdr-burn-0.3.0-30.fc37.src.rpm
Uploading srpm:
> I have the same issue with mpv:
>
> /usr/bin/ld: /lib/libopenmpt.so.0: undefined reference to
> `mpg123_open_handle_64'
> /usr/bin/ld: /lib/libopenmpt.so.0: undefined reference to
> `mpg123_replace_reader_handle_64'
> /usr/bin/ld: /lib/libsndfile.so.1: undefined reference to `mpg123_seek_64'
It's a sub-package of mplayer
https://koji.rpmfusion.org/koji/buildinfo?buildID=23580
On 09/11/2022 13:57, zonexpertconsult...@outlook.com wrote:
Tracing down a dependency issue for mythtv -> mjpegtools -> mencoder
for el9, I noticed mencoder does not show in rpmfusion pkgdb.
However, the
Fixed.
On 07/11/2022 14:55, zonexpertconsult...@outlook.com wrote:
The following bug report went to the previous package maintainer,
Richard Shaw, rather than me when it was initially created:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=6463
Anyone know how to fix this for future bug
The new ffmpeg build with rtmp disabled fixes the issue.
https://koji.rpmfusion.org/koji/buildinfo?buildID=23950
On 20/10/2022 08:14, Nicolas Chauvet wrote:
Le jeu. 20 oct. 2022 à 01:49, a écrit :
ZoneMinder is failing to build, only on el9, with the following:
[100%] Linking CXX
> Lack of legal action is not evidence of no further legal action. There are
> multiple
> possible explanations:
>
> - they see no point because going after distros would waste time and money
> and bring bad
> PR
> - going after Redhat who would assume liability is a different story as
>
> Neal Gompa wrote:
>
> Considering that we have been shipping these hardware codec interfaces for
> years without any legal trouble, I find this absolutely ridiculous.
>
> Kevin Kofler
Just because it hasn't happened yet doesn't mean it can't.
I found this link very informative on the
> On Wed, 2022-09-28 at 08:24 +0200, Neal Gompa wrote:
>
> That seems to contradict this quote from
> https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/opengl...:
>
> it, also keeping the repo in sync with fedora isn't a priority for me.
Someone with the hardware and packaging
> On Thu, 2022-09-15 at 22:42 +0300, Otto Liljalaakso wrote:
>
> I found this: https://bugzilla.rpmfusion.org/show_bug.cgi?id=6410#c1
>
> Again, not a very friendly response. The short is that they are
> currently in freeze so no action can be taken ATM.
The rpmfusion f36 release repo isn't
I have started to ignore CVE bugs reports due to the low quality reporting.
An outdated ffmpeg CVE was filed against nv-codec-headers, WTF!!
It isn't the first time it's been totally bogus.
___
devel mailing list -- devel@lists.fedoraproject.org
To
> Also note that you will also need to create a kmod package for
> the also out of tree v4l2-loopback kernel driver. The closed-source
> userspace bits Intel provide only work with gstreamer. So the
> way this is used on other distros is with a little helper process
> which runs a
Separate drivers for the kernel aren't permitted in fedora, try submitting a
review request at rpmfusion.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
> On Mon, Sep 05, 2022 at 09:56:58PM +0200, Dominik 'Rathann' Mierzejewski
> wrote:
>
> There are 26 patches so that's a bit of a PITA. Is there not an
> easier way?
>
> Rich.
Try using autopatch.
# Apply patches up to #1000 from this spec.
%autopatch -M1000 -p1
I have patched to add the unversioned .so
https://src.fedoraproject.org/rpms/libid3tag/c/607d7abf709add3e39690adfd3aef871c50d37c2?branch=rawhide
I don't think there is a need to rebuild dependant packages.
[leigh@mpd libid3tag]$ abipkgdiff libid3tag-0.15.1b-37.fc37.x86_64.rpm
Switching upstream has increased the .so version from libid3tag.so.0 to
libid3tag.so.0.16.2
I plan to do the rebuilds myself after checking everything builds ok in copr.
Affected packages
Fedora:
audacity-0:3.1.3-5.fc37.x86_64
easytag-0:2.4.3-16.fc37.x86_64
gtkpod-0:2.1.5-21.fc37.x86_64
> I'm guessing I need to provide a separate common package containing the
> non-binary
> files - i.e. udev configs, license, readme, and so on. So the akmod, or the
> kmod package
> implicitly expects a corresponding common package to be made available?
> Anything need to
> be done specifically
> Here is a link to the code:
>
> https://github.com/cowboysmall-apps/hid-ite8291r3-kmod
>
> any help would be appreciated.
>
> Thanks in advance,
>
> J.K.
Drop the sub-package as it isn't correct to have it the kmod package.
> Thanks for the reply - I'll try this later.
>
> Can you point me at the documentation for the process please? I can find docs
> and
> tutorials on building standard RPMs - the hello tutorial for example - but I
> can't
> find any documentation anywhere for building RPMs for kernel module, or
1 - 100 of 503 matches
Mail list logo
