Hi Florian, thanx a lot for kind reply!
I saw the wrapper you have, and found it quite intensive. I was trying much
more simple workarounds, and also similar macro redefinition, but withotu
success.
I'm, not sure I need any redefinition at all. The only thing I know is that rpm 4.1 is ignoring custom debuginfo pkg, but 4.20 is honoring that. Seeing changelog of 4.20, it seemed that 4.20 addressed exactly this, and that in 4.1x it was
usually resolved by macros redefinition, very often even on distribution level. Net search then popped out some old threads of yours, where you were altering debuginfo macros - only with different goals.
Happy hacking!
J.
On 6/2/25 12:34, Florian Weimer wrote:
* Jiri Vanek:
Florian, I saw you were playing with advanced debuginfo macros in past. Maybe
you may know?
TY!
J.
On 5/30/25 17:12, Jiri Vanek wrote:
Hello!
We had recently changed how we handle debuginfo in JDK:
https://src.fedoraproject.org/rpms/java-latest-openjdk/pull-request/147#request_diff
<https://src.fedoraproject.org/rpms/java-latest-openjdk/pull-request/147#request_diff>
Main change is, that we create debuginfo manually. Unluckily it was
developed with rpm 4.20, so it built fine in f41-f43, but during
porting to epels, I found it build in none. Just for curiosity I
tried also in f40, and it failed too. So my guessing pointed to rpm
4.20.
The failure in f41/epels is, that they ignore the manual |%package
debuginfo |(debugsource seems fine) and insted they later print:
error: Installed (but unpackaged) file(s) found:
/usr/lib/debug/usr/lib/jvm/java-24-openjdk/bin/jar.debuginfo
/usr/lib/debug/usr/lib/jvm/java-24-openjdk/bin/jarsigner.debuginfo
/usr/lib/debug/usr/lib/jvm/java-24-openjdk/bin/java.debuginfo
/usr/lib/debug/usr/lib/jvm/java-24-openjdk/bin/javac.debuginfo
....
Which is contnet of my debugfiles.list, which is in 4.20 correctly
used. In logs is visible that the debuginfo subpkg is not processed
at all:
ok: https://koji.fedoraproject.org/koji/taskinfo?taskID=133271306
<https://koji.fedoraproject.org/koji/taskinfo?taskID=133271306>
not ok: https://koji.fedoraproject.org/koji/taskinfo?taskID=133347836
<https://koji.fedoraproject.org/koji/taskinfo?taskID=133347836>
Anybody any thoughts please?
Sorry, I don't have an idea how to solve this. For glibc, we wrap
find-debuginfo to get the behavior we need.
Why do you need to override the behavior? So that fastdebug and
slowdebug builds do not get separated debuginfo? With debuginfod, is
this still necessary today? (I assume Fedora debuginfod covers EPEL.)
Thanks,
Florian
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
--
_______________________________________________
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
