On Wed, Jun 8, 2016 at 1:58 AM, Oleksandr Poznyak
wrote:
> Hi, Edward.
> Your approach is valid. But RREPLACES is not enough.
>
> You should define that your package and original ones are conflicting and
> that it provides the same as original one for other packages.
>
> So in your recipe:
>
> RPR
On 08-06-16 00:20, Richard Purdie wrote:
On Wed, 2016-06-08 at 09:24 +1200, Paul Eggleton wrote:
On Tue, 07 Jun 2016 17:20:12 Burton, Ross wrote:
On 7 June 2016 at 17:02, Burton, Ross
wrote:
It means the hash calculated my the bitbake master was different
to the
hash calculated when the work
Add a model to support setting a python command and virtualenv per
branch, which allows you to parse master with python3 and krogoth with
python2 for example.
Signed-off-by: Paul Eggleton
---
README | 22 ++-
layerindex/admin.py
Django 1.8 warns that the default for the "permanent" parameter to
RedirectView is changing in 1.9 from True to False, but I believe we
should be specifying False for these redirections - these are not just
redirections from old URLs and may in fact change in the future if the
site structure change
The old transaction API has been removed in Django 1.8 and was
deprecated at 1.6. There's no explicit open transaction, commit or
rollback now - we just wrap the layer operations in
"with transaction.atomic()"; if we need to roll back we just raise a
"dummy" exception.
Signed-off-by: Paul Eggleton
We need to be able to support Python 3 so that we can parse master of
OE-Core with bitbake (which now requires it). This now means the
interface itself and the update script require Python 3.4+.
Signed-off-by: Paul Eggleton
---
README | 6 --
layerindex/b
Django 1.8 does not allow DateFields that have both auto_now and default
set - since they are mutually exclusive; if you have auto_now you don't
need a default.
Signed-off-by: Paul Eggleton
---
layerindex/models.py | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/la
Newer versions of GitPython implement rename detection, which means that
such changes don't show up as adds and deletes anymore and you get a
bunch of ENOENT errors for renamed files. Add some code to explicitly
look for renames and process them appropriately.
Signed-off-by: Paul Eggleton
---
la
Stop using "d" (sometimes multiple levels!) and use proper descriptive
variable names instead.
Signed-off-by: Paul Eggleton
---
layerindex/update_layer.py | 40
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/layerindex/update_layer.py b/l
I'd like to be upgrading to 1.8 but that causes problems with South, and
we're not quite ready to dispense with our existing migrations yet.
Signed-off-by: Paul Eggleton
---
README | 18 +-
layerindex/forms.py| 1
We have to upgrade django-reversion to 1.8 due to upgrading Django, but
unfortunately in that same version the author has removed the type field
on Version model, without a particularly good explanation as to why. This
is really annoying as we were using it to provide a reasonable audit
including f
In order to try to avoid problems with leaking memory, context bleeding
from one layer to another, and lay the groundwork for supporting
updating all branches in one operation, split the updating of a single
layer out to its own internal script. This means that the tinfoil
instantiation and metadat
Fix a greedy regex in the recipe detail view resulting in the git recipe
listing all bbappends named *_git.bbappend as its bbappends (quite a few
in the public instance).
Signed-off-by: Paul Eggleton
---
TODO| 1 -
layerindex/views.py | 2 +-
2 files changed, 1 insertion(+), 2 de
Allow updating multiple branches, and if no branches are specified,
update all branches that have a new "updates_enabled" flag field set to
True. This avoids the need to have a separate shell script which runs
update.py for each branch (and thus has hardcoded knowledge of each
active branch in the
Fix "data truncated" warnings/errors when loading data for OE-Core:
* PROVIDES for recipe packagegroup-base is ~1452 characters
* LICENSE for recipe linux-firmware is ~1053 characters
(These aren't shown with SQLite, only with something like MariaDB where
column sizes are enforced.)
Signed-off-by
We were getting temporary paths appearing in the tarball that gets
created to allow you to download the patches for a bulk change operation
that crosses multiple layers - we don't need those.
Signed-off-by: Paul Eggleton
---
layerindex/bulkchange.py | 2 +-
1 file changed, 1 insertion(+), 1 dele
Refactor the update script to hopefully make it more robust, allow
multiple branches to be updated with one command, support Python 3
and Django 1.6 and fix a few other issues.
Changes since v1:
The Python 3 change hit while the original patchset was in review,
which has broken parsing of master.
If you're moving a short description value from DESCRIPTION to SUMMARY
then part of that is setting DESCRIPTION to blank, however that wasn't
possible - the code was assuming that a null value meant "keep the
original value". Change the logic so that the value in the bulk change
object is always se
I am building two out-of-tree KLMs with separate yocto recipes.
One of the KLMs depends on a data structure defined in the other one. At
present the structure definition is simply duplicated in both KLMs' source.
I would prefer to define it in a header that one KLM can export and the other
can #in
As recently discussed on the mailing list, bitbake now issues an error when the
task hash computed by the bitbake master differs from the task hash computed by
the bitbake worker. This usually happens when the task hash depends on the date
and time for some reason.
This affects IMAGE_CMD_rpi-sdimg
I got that taskhash mismatch too and much more often than once per
million. ;) I'm quite happy that you're discussing it here as I did not
know what it was.
Re-running the task a second time in a row makes the warning disappearing.
Regards,
Le 08/06/2016 11:18, Gary Thomas a écrit :
On 2016-
On Wed, 2016-06-08 at 20:59 +1200, Paul Eggleton wrote:
> On Tue, 07 Jun 2016 23:20:26 Richard Purdie wrote:
> > On Wed, 2016-06-08 at 09:24 +1200, Paul Eggleton wrote:
> > > On Tue, 07 Jun 2016 17:20:12 Burton, Ross wrote:
> > > > On 7 June 2016 at 17:02, Burton, Ross
> > > > wrote:
> > > > > It
On 8 June 2016 at 10:20, piotr.lewicki wrote:
> I actually want to enable systemd in all packages, but my current DISTRO
> is "poky".
> Can you point me some documentation where I can get information on how to
> create a distro file based on poky and add systemd there?
>
http://www.yoctoproject.
Thanks.
I actually want to enable systemd in all packages, but my current DISTRO
is "poky".
Can you point me some documentation where I can get information on how
to create a distro file based on poky and add systemd there?
Thanks,
Piotr
On 07.06.2016 15:53, Burton, Ross wrote:
On 7 June 20
On 2016-06-08 11:08, Mike Looijmans wrote:
On 08-06-16 00:20, Richard Purdie wrote:
On Wed, 2016-06-08 at 09:24 +1200, Paul Eggleton wrote:
On Tue, 07 Jun 2016 17:20:12 Burton, Ross wrote:
On 7 June 2016 at 17:02, Burton, Ross
wrote:
It means the hash calculated my the bitbake master was dif
On Tue, 07 Jun 2016 23:20:26 Richard Purdie wrote:
> On Wed, 2016-06-08 at 09:24 +1200, Paul Eggleton wrote:
> > On Tue, 07 Jun 2016 17:20:12 Burton, Ross wrote:
> > > On 7 June 2016 at 17:02, Burton, Ross
> > > wrote:
> > > > It means the hash calculated my the bitbake master was different
> > >
Hi, Edward.
Your approach is valid. But RREPLACES is not enough.
You should define that your package and original ones are conflicting and
that it provides the same as original one for other packages.
So in your recipe:
RPROVIDES_${PN} = "sysvinit-inittab"
RREPLACES_${PN} = "sysvinit-inittab"
RC
Hi Robert
2016-05-25 12:18 GMT+02:00 Robert P. J. Day :
>
> specifically in the context of powerpc systems, are there any
> suggestions for an image that could be used to boot an older powerpc
> system, running completely out of ram, and using that as an install
> utility which would then be res
28 matches
Mail list logo
