ffmpeg
https://src.fedoraproject.org/rpms/ffmpeg/c/db2acb3681a85baed6bbc897cdac792d4b7d7c5f?branch=rawhide
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
> 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.
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:
> 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
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 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
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
> 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
> 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
> 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
-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 ,
>
> 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'
> 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
I'm inclined to vote -1, if everyone keeps DT_HASH around I doubt Epic will
fix the issue.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
> Hi,
>
> I’m just testing the new 20220813 branch end encounter several issues.
>
> One of them is image factory, which I need to install to test building a
> server image.
>
> # dnf install imagefactory
> Last metadata expiration check: 1:35:08 ago on Sat 13 Aug 2022 05:57:29 PM
> CEST.
>
IMO it would be worthwhile doing test builds to see how many of the dependent
packages actually still use external asio.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora
Shouldn't asio package be retired as it's provided by boost-devel?
/usr/include/boost/asio/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
> On Sat, Aug 6, 2022 at 10:11 AM Zbigniew Jędrzejewski-Szmek
>
> As the maintainer of rpmdevtools, I will probably not accept changes
> upstream to change to rpmautospec in the templates, since rpmautospec
> doesn't work outside of Fedora and there's been no advocacy to make
> rpmautospec a
Fixed
https://src.fedoraproject.org/rpms/graphlcd-base/c/eff3f3c0a0817bd5bdfad4d95eabb4a87bab9440?branch=rawhide
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
Is this some sick joke?
https://bugzilla.redhat.com/show_bug.cgi?id=2104255
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
> On Thu, 2022-06-09 at 03:51 +0200, Kevin Kofler via devel wrote:
>
> The linking happens on the user machine, no? For Fedora only akmods are
> available, which generate kernel-specific kmod RPMs on the user
> machine. Which causes its own issues since that means you can't boot
> with Secure
> On Tue, Jun 7 2022 at 10:24:46 AM +0200, Vitaly Zaitsev via devel
>
> For avoidance of doubt, Fedora Legal has decided we may use flathub but
> not rpmfusion. As I explained to you previously, they have also decided
> not to share their reasoning for this.
>
> Michael
> On Tue, Jun 7 2022
> That is also blatantly false. The idea was posted by Andreas on
> rpmfusion-developers list in November 2021 and I (one of the FFmpeg
> maintainers) was the only one who responded. The other maintainers made
> no comments in that thread.
>
> In other words, Kevin, please stop spreading lies.
>
The Cinnamon spin (kickstart and comps) are managed by Dan Book.
https://fedoraproject.org/wiki/Changes/Cinnamon_Spin#Owner
I'm the only fedora developer working on Cinnamon.
I don't have any spare time to do more things including testing.
___
devel
> On 12/05/2022 07:43, Miro Hrončok wrote:
>
> I think these kernel modules should be upstreamed directly to the Linux
> kernel.
That would block the use of 390xx, 470xx and mai, see
http://us.download.nvidia.com/XFree86/Linux-x86_64/515.43.04/README/kernel_open.html
I don't think Nvidia has any intention to add this to mainline kernel as it
would block use of the propriety driver.
I zero interest in packaging it for rpmfusion as it's so limited, see
http://us.download.nvidia.com/XFree86/Linux-x86_64/515.43.04/README/kernel_open.html
Try redefining optflags
%global optflags %(echo %{optflags} | sed 's@-g @-g1 @')
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Why post something that has expired?
___
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
> On Wed, Apr 6, 2022 at 6:31 PM Chris Murphy wrote:
>
>
> We have not set up an infrastructure for it, but in all honesty, there
> is no technical reason that any 3rd party repository building and
> packaging the driver could not have done such a thing a couple of
Rpmfusion doesn't provide
> On Thu, 2022-03-10 at 00:15 +0200, Otto Urpelainen wrote:
>
> Continuing I brought the corrections to Fedora 36
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-db793ad26c
>
> Now only 4 packages more gtk1+ depends on glib
>
> Depending packages (rawhide) (5): bubblemon gtk+ manedit
> On Mon, 2022-03-07 at 12:12 -0500, Ben Cotton wrote:
>
> Why isn't this as simple as:
>
> 1) Create an f37-multilib-build build tag with all supported arches + i686,
> and an f37-multilib{,-candidate} build targets to use it (with destination tag
> of f37-updates-candidate);
>
> 2) Drop i686
> On Wed, Mar 09, 2022 at 09:06:01 -0600,
> Chris Adams
> The Fedora 36 beta is likely to slip because firefox was not building
> successfully on i686, but was on other arches.
That is a very poor excuse for a slip, why would any one need it?
Why not add an ExcludeArch to fix?
> On Tue, 2022-03-08 at 16:01 +0000, Leigh Scott wrote:
>
> Hi Leigh ,
> yes , it looks like glib-devel is not needed , I'm curious , how do you
> find these mistakes ?
>
> Thank you
I checked the built rpm requires and
> Sérgio Basto kirjoitti 7.3.2022 klo 18.17:
> Crossfire and freedroidrpg are games, so "is it needed?" and
> "does it
> have a replacement?" are not good questions to ask. A better question
> would be "does anybody want to play it?". Games do not really ever
> become obsolete, each is a unique
> On Mon, 07 Mar 2022 10:29:02 -0600
> Michael Catanzaro
>
> I'm not unwilling to retire them, I just want their users to be retired
> first so I don't leave a bunch of broken dependencies behind.
>
> Paul.
dillo, alsa-tools, gnubg, and tilda don't rely on glib or gtk+, the package
> Fedora cannot use the default tarball due to legal restrictions.
> Additionally, Fedora uses
> GCC (intentionally) which requires patch work for each release, but improves
> the quality
> of the resulting package.
So GCC needs 125Gb of Ram to build chromium?
> VAAPI hasn't worked for a long time on chromium. In "chrome://gpu" it shows
> "Video Decode: Software only. Hardware acceleration disabled" and it cannot be
> changed in "chrome://flags" either. This is the case for Fedora's packaged
> chromium and rpmfusion's chromium-freeworld. I encourage you
> On Wed, 2022-02-16 at 08:32 +0000, Leigh Scott wrote:
>
> By building I meant it'll probably prevent the *image* from composing,
> because blueberry is a 'mandatory' package in the group, and its
> dependencies will no longer be satisfied, so liveimage-creator will
> choke on
Hi Adam,
I'm not the blueberry maintainer anymore.
This change wont prevent the cinnamon spin from building as blueberry is a
python app.
https://src.fedoraproject.org/rpms/blueberry/blob/rawhide/f/blueberry.spec#_23
I will raise the issue with the team.
Regards,
Leigh
> Hi Miro,
>
>
> a few users have opened a bugzilla ticket [1] with the request to "Add
> support for
> Windows VSTs by building the Wine bridges" unfortunately I don't know how to
> do
> this at the moment and need help.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=2038747
>
>
> Try
>
> fedpkg mockbuild
>
> or
>
> mock -r fedora-36-x86_64 /path/to/carla.srpm
Add your user name to the mock group
sudo usermod -a -G mock myusername
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
> the problem is that I don't know how to build the program with mock build.
Try
fedpkg mockbuild
or
mock -r fedora-36-x86_64 /path/to/carla.srpm
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
Why?, your build flags are set for Windows compilation.
/usr/bin/make -O -j2 V=1 VERBOSE=1 win32 CC=i686-w64-mingw32-gcc
CXX=i686-w64-mingw32-g++
You should be compiling it in mock build.
> i have installed the missing 32bit package, but then the compilation fails
> again with this
> error
1 - 100 of 279 matches
Mail list logo
