OLD: Fedora-Rawhide-20221224.n.0
NEW: Fedora-Rawhide-20221225.n.1
= SUMMARY =
Added images:1
Dropped images: 0
Added packages: 5
Dropped packages:0
Upgraded packages: 58
Downgraded packages: 0
Size of added packages: 972.14 KiB
Size of dropped packages:0
On my laptop when I tried to do a dnf system-upgrade from f36->37 I ended
up getting a conflict with mlocate and plocate.
Since I remember the thread I just did a "dnf swap" which solved the issue
but it could be confusing to users not aware.
Was this supposed to happen automagically?
Thanks,
Ri
This roc-toolkit-0.1.5^20221224git2017450a-1.fc38 build of roc-toolkit:
https://koji.fedoraproject.org/koji/buildinfo?buildID=2103819
bumps the soname of libroc from libroc.so.0.1 to libroc.so.0.2 . That
breaks nearly everything, because pipewire requires libroc.so.0.1 and
pretty much every desktop
On Sun Dec 25, 2022 at 09:02 -0500, Sam Varshavchik wrote:
> rpm -E '%__global_ldflags'
>
> is also needed for LDFLAGS.
%__global_ldflags is deprecated. You should use %build_ldflags
instead[1]. Also, %build_cflags, %build_cxxflags, and friends are
preferred to %optflags AFAIK.
[1]:
https://src.
Vitaly Zaitsev via devel writes:
On 23/12/2022 19:21, Vít Ondruch wrote:
Working with upstream on one issue [1], it seems that the culprit is in the
Fedora compiler options. Is there some convenient way to set them up?
rpm -E %optflags
rpm -E '%__global_ldflags'
is also needed for LDFLAGS
On 23/12/2022 19:21, Vít Ondruch wrote:
Working with upstream on one issue [1], it seems that the culprit is in
the Fedora compiler options. Is there some convenient way to set them up?
rpm -E %optflags
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
