I use slim and have realized that it is retired/no longer supoorted from F31.
So, I got the src.rpm from teh F30 stable and was trying to rebuild it at least to see what the issues were.
However, the rpmbuild
$ rpmbuild -bb slim.spec
error: This macro requires some arguments
I have never had experience with passing such macros. I looked into the spec file but can not figure out how to do this. Here is the spec file:
UNTITLED - CentOS Pastebin Service
UNTITLED - CentOS Pastebin Service
You are kindly invited to the meeting:
Modularity Team (weekly) on 2019-12-31 from 15:00:00 to 16:00:00 UTC
The meeting will be about:
Meeting of the Modularity Team.
More information available at: [Modularity Team Docs](https://docs.pagure.org/modularity/)
The agenda for the meeting is available as flagged tickets [in the Modularity repository](https://pagure.io/modularity/issues?status=Open&tags=Meeting).
I'd need to report this issue but I don't know which component to file it on.
Basically, I upgraded my MacBook Pro 11.1 from Fedora 29 to Fedora 31,
but the EFI boot manager now has both entries (Fedora and Macintosh)
pointing to OSX.
If you also have ideas about how to proceed and fix it it would be
most useful :D
I'm attempting to compile the latest minor update of Kodi and debug generation
appears to be broken in Fedora 32. The update successfully compiles in Fedora 31.
Is anyone aware of what has changed in Fedora 32 that could cause the errors below?
warning: Could not find DWO CU
CMakeFiles/kodi-xrandr.dir/xbmc-xrandr.c.dwo(0xc444049b4814c563) referenced by CU at
offset 0x0 [in module
Error while writing index for
Cannot use an index to create the index
Full build output: http://koji.rpmfusion.org/kojifiles/work/tasks/6536/376536/build.log
annobin = 8.78-2.fc31
gcc/g++ = 9.2.1-1.fc31
annobin = 8.92-1.fc32
gcc/g++ = 9.2.1-1.fc32.3
I think I found a bug and am hoping someone here can point me in the
right direction as to where to report it. I think this is rpmbuild, but
am not certain.
Anyway, I have a private package that generates a bunch of desktop files
for our users. Both the filename and Name= values inside the desktop
file contain a parenthetical hint to the user. Builds prior to F31 have
had no issue, but with F31 now things fail. Here's an example desktop
file that fails:
# PICAPS 0001-Mason (Michigan).desktop
Name=PICAPS 0001-Mason (Michigan)
The failure I see in Koji's build.log looks like this:
+ cp -pr CHANGELOG.md
+ cp -pr README.md
++ jobs -p
+ exit 0
error: No rich dependencies allowed for this type: (Idaho).desktop)
error: No rich dependencies allowed for this type: (Michigan).desktop)
Child return code was: 1
Traceback (most recent call last):
line 95, in trace
result = func(*args, **kw)
File "/usr/lib/python3.7/site-packages/mockbuild/util.py", line 746,
raise exception.Error("Command failed: \n # %s\n%s" % (command,
mockbuild.exception.Error: Command failed:
# /usr/bin/systemd-nspawn -q -M 2145c769ea5744e7b70b9eb2ca4e7029 -D
/var/lib/mock/f31-build-8562-11880/root -a --capability=cap_ipc_lock
--setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock
--setenv=PS1=<mock-chroot> \s-\v\$ --setenv=LANG=en_US.UTF-8 -u
mockbuild bash --login -c /usr/bin/rpmbuild -bb --target noarch --nodeps
I haven't done a ton with rich deps yet but I cannot imagine these are
being driven from desktop files now ... or are they? Another thing odd I
see here is the trailing ')' in the error message. It doesn't seem to
have a mate and I'm guessing it comes from the format string for
printing this error.
I've worked around this problem by avoiding the parenthesis like so:
# PICAPS 0001-Mason, Michigan Test.desktop
Name=PICAPS 0001-Mason, Michigan Test