MJW also says not needed, closing.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/171#issuecomment-285035471___
Rpm-maint mailing list
Closed #171.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/171#event-991302904___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
I have tested the current rpm4 debugedit within the Yocto Project environment
-without- the patch, with the known binary doing cross-compiled work (little to
big endian) and have not been able to reproduce the issue.
Either debugedit has had a tweak over the years or elfutils has had a bug
Another issue that might make debugedit.c more portable is similar to inlining
DW_FORM* instead of
`#include `
Instead of using EU version dependent #defines for strtab_init() etc (which
needs -lebl), it may be more "portable" to just inline the routines and
maintain a copy in debugedit.c.
Re: https://patchwork.openembedded.org/patch/46887
The bug and related information are available at:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4089
I am currently working through this to see if the current rpm (4) version
suffers from the same failure. I will update this if it does or
Yes all the patches were reversed.
Meanwhile I just sorted the first patch with Mark Hatle (aka "fray"). The
segfault is not reproducible with EU-0.168.
The hex printing was an attempt to avoid pgpHexStr() which differs between
rpm.org and rpm5.org.
You explained away the valid_file() check
@n3npq For what it's worth, to make it all unformatted text, use ` ``` ` at the
top of the block, and ` ``` ` at the bottom of the block. That way, it looks
like patches or code. :)
In addition, you can tell it to be diff style by doing ` ```diff ` for the top
of the block.
--
You are
