From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Anders Oleson <anders@openpuma.org>,
openembedded-core@lists.openembedded.org
Subject: Re: bug with dpkg-native and sstate-cache mirrors
Date: Wed, 11 Jan 2017 08:22:26 +0000 [thread overview]
Message-ID: <1484122946.4367.170.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAKTo2Em1Lcs19L0M=WpGOJv3aQkQLJuetFsgm6nq_0sVix1X3A@mail.gmail.com>
On Fri, 2016-12-16 at 11:31 -0800, Anders Oleson wrote:
> Does this sound like I'm on the right track or like something that
> could be included? I'd like to fix this so that it doesn't sneak up
> on someone else.
>
> I'm willing to take a hack at it and test it in the scenario where
> this bit us. It would involve steps:
> 1. develop a patch to dpkg to add the option
> 2. develop a patch for OE to change the configure for dpkg-native
> 3. a patch for OE to pass --configdir to dpkg in all the right
> places.
> I could use help to insure I find them all.
This does sound like a genuine bug and something we need to fix. You do
sound like you're on the right track with it. Adding a workaround patch
to dpkg-native only would be one way to move forward but fixing it
properly as you describe is much more desirable if upstream will take
such a patch. I appreciate you taking the time to do that!
The lack of response isn't lack of interest but partly the holidays and
partly that you're on the right check so replies would mainly be "yes,
sounds good" which people tend not to post against everything they
agree with.
Cheers,
Richard
prev parent reply other threads:[~2017-01-11 8:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 19:31 bug with dpkg-native and sstate-cache mirrors Anders Oleson
2016-12-21 3:45 ` Anders Oleson
2017-01-09 16:45 ` Anders Oleson
2017-01-11 8:24 ` Richard Purdie
2017-01-12 5:02 ` [PATCH] dpkg: workaround for sstate contamination Anders Oleson
2017-01-11 8:22 ` Richard Purdie [this message]
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=1484122946.4367.170.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=anders@openpuma.org \
--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