All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Jack.Fewx@dell.com
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: [pseudo] Pseudo 1.8+ xattr sqlite corruption
Date: Wed, 22 Aug 2018 10:41:16 +0200	[thread overview]
Message-ID: <CANNYZj8A22yL9VU0Wp3OOXwZU6yR=fQXqeWSfKykDp_kkL6ZGQ@mail.gmail.com> (raw)
In-Reply-To: <6a084eda5fcb4423a647bb998471e26d@AUSX13MPC104.AMER.DELL.COM>

2018-08-20 20:45 GMT+02:00  <Jack.Fewx@dell.com>:
> We are encountering a build problem after migrating to Poky 2.3 and Pseudo 1.8.1, and need help to resolve this.
> It is hampering our development efforts, forcing us to rebuild images frequently.
>
> Background:
> Our build applies SELinux file contexts, during build time since our rootfs is read-only
> In Poky 2.0, using Pseudo 1.6.2 this works perfectly 100% of the time

Pseudo is not an integral part of poky, and comes via a recipe build
like anything else. You can play with that recipe, and establish which
commit in pseudo's upstream git repo broke this. Also 2.3 is better
than 2.0 but still kind of old. Do try this on the latest yocto
release, or even on the master branch.

Alex


  reply	other threads:[~2018-08-22  8:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20 18:45 [pseudo] Pseudo 1.8+ xattr sqlite corruption Jack.Fewx
2018-08-22  8:41 ` Alexander Kanavin [this message]
2018-08-22 13:58   ` Jack.Fewx
2018-08-22 14:41     ` Joshua Watt
2018-08-22 14:54       ` Jack.Fewx
2018-08-22 15:09         ` Richard Purdie
2018-08-22 15:32           ` Jack.Fewx
2018-09-18 20:26           ` Jack.Fewx
2018-09-18 21:09             ` Seebs
2018-09-18 21:16               ` Joshua Watt
2018-09-18 21:20                 ` Seebs
2018-09-19 11:33                   ` Burton, Ross
2018-09-19 14:39                     ` Seebs
2018-09-19 16:25                       ` Jack.Fewx
2018-09-20 19:16                     ` Seebs
2018-09-20 20:41                       ` Jack.Fewx
2018-09-20 20:46                         ` Seebs
2018-09-20 20:50                         ` Seebs
2018-09-21 12:50                           ` Burton, Ross
2018-09-23 13:23                             ` Martin Jansa
2018-08-22 16:41         ` Seebs
2018-08-22 14:44     ` 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='CANNYZj8A22yL9VU0Wp3OOXwZU6yR=fQXqeWSfKykDp_kkL6ZGQ@mail.gmail.com' \
    --to=alex.kanavin@gmail.com \
    --cc=Jack.Fewx@dell.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.