Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Neal Gompa <ngompa13@gmail.com>
Cc: Mark Wielaard <mjw@redhat.com>,
	OpenEmbedded Core Mailing List
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] rpm: update to 4.14.0
Date: Wed, 8 Nov 2017 15:14:29 +0200	[thread overview]
Message-ID: <0afcb034-1acf-3a4b-b27a-010b7073a308@linux.intel.com> (raw)
In-Reply-To: <CAEg-Je-MW3k897aKZmmjh4Q-eFD8Kko=7FLRByv19sGYK1ZxRg@mail.gmail.com>

On 11/07/2017 11:17 PM, Neal Gompa wrote:

>> Thanks, this is the offending commit:
>>
>> https://github.com/rpm-software-management/rpm/commit/88989572fff1f31e0c4f972a6895585e4742ef4b
>>
>> Looks like they added sophisticated in-place processing/rewriting of the
>> actual binary (that is not possible to switch off). And it fails in case of
>> grub modules.
>>
>> We, on the other hand, only need to extract the list of debug source code
>> files. Any hint on how to do that without the use of rpm/debugedit? Perhaps
>> something from binutils/elfutils?
>>
> 
> This is the first time I'm hearing of this. Has anyone talked to Mark
> Wielaard (CC'd to this email) about fixing this properly for you guys?
We don't have any particular interest in debugedit though. It is only 
used as a crutch to extract the debug source locations. If readelf can 
do the same thing, we'll use that - please do understand that reporting 
issues upstream costs time, especially if upstream replies with 
NEEDINFO, WORKSFORME or WONTFIX type of thing, so we prioritize what's 
truly critical :)

Alex


  reply	other threads:[~2017-11-08 13:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 12:14 [PATCH] rpm: update to 4.14.0 Alexander Kanavin
2017-11-03 10:14 ` Alexander Kanavin
2017-11-03 16:21   ` Khem Raj
2017-11-03 17:58   ` Mark Hatle
2017-11-06 16:00     ` Alexander Kanavin
2017-11-06 16:54       ` Mark Hatle
2017-11-07 14:53         ` Alexander Kanavin
2017-11-07 15:50           ` Otavio Salvador
2017-11-07 16:41           ` Mark Hatle
2017-11-07 21:17       ` Neal Gompa
2017-11-08 13:14         ` Alexander Kanavin [this message]
     [not found]           ` <1510153768.10879.80.camel@klomp.org>
2017-11-08 15:31             ` Mark Hatle
2017-11-09 13:19               ` Alexander Kanavin
2017-11-09 16:49               ` Alexander Kanavin
  -- strict thread matches above, loose matches on Subject: below --
2017-12-18 16:00 Alexander Kanavin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0afcb034-1acf-3a4b-b27a-010b7073a308@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=mjw@redhat.com \
    --cc=ngompa13@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox