Re: [yocto] Per image customizations

2016-06-08 Thread Edward Wingate
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.

Re: [yocto] What's this

2016-06-08 Thread Mike Looijmans
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

[yocto] [layerindex-web][PATCH v2 12/15] Handle Python 2 and Python 3 branches in the same index

2016-06-08 Thread Paul Eggleton
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 ++-

[yocto] [layerindex-web][PATCH v2 15/15] Explicitly specify temporary redirection

2016-06-08 Thread Paul Eggleton
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

[yocto] [layerindex-web][PATCH v2 14/15] update_layer.py: use new-style transaction API

2016-06-08 Thread Paul Eggleton
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

[yocto] [layerindex-web][PATCH v2 09/15] Support (and require) Python 3

2016-06-08 Thread 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

[yocto] [layerindex-web][PATCH v2 13/15] Preemptive auto_now fix for Django 1.8

2016-06-08 Thread Paul Eggleton
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(+),

[yocto] [layerindex-web][PATCH v2 11/15] update_layer.py: fix handling of renames with newer GitPython

2016-06-08 Thread Paul Eggleton
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

[yocto] [layerindex-web][PATCH v2 10/15] update_layer.py: rename confusing loop variables

2016-06-08 Thread Paul Eggleton
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

[yocto] [layerindex-web][PATCH v2 07/15] Upgrade to Django 1.6+

2016-06-08 Thread Paul Eggleton
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

[yocto] [layerindex-web][PATCH v2 08/15] Fix for changes in modern django-reversion

2016-06-08 Thread Paul Eggleton
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

[yocto] [layerindex-web][PATCH v2 02/15] update.py: refactor into two separate scripts

2016-06-08 Thread Paul Eggleton
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

[yocto] [layerindex-web][PATCH v2 04/15] Fix listing *_git.bbappend as appends for git recipe

2016-06-08 Thread Paul Eggleton
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

[yocto] [layerindex-web][PATCH v2 03/15] update.py: allow updating all branches with one command

2016-06-08 Thread Paul Eggleton
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

[yocto] [layerindex-web][PATCH v2 05/15] Increase size of Recipe provides and license fields

2016-06-08 Thread Paul Eggleton
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.)

[yocto] [layerindex-web][PATCH v2 06/15] bulkchange: drop temp paths in multi-patch tarball

2016-06-08 Thread Paul Eggleton
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

Re: [yocto] DISTRO_FEATURES modification from image recipe?

2016-06-08 Thread piotr.lewicki
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

Re: [yocto] What's this

2016-06-08 Thread Gary Thomas
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

Re: [yocto] What's this

2016-06-08 Thread Paul Eggleton
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

Re: [yocto] Per image customizations

2016-06-08 Thread Oleksandr Poznyak
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"

Re: [yocto] any pointers to a yocto-based image to use as a live install utility?

2016-06-08 Thread Christian Ege
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