> On Feb 19, 2016, at 5:32 AM, Otavio Salvador
> wrote:
>
> On Fri, Feb 19, 2016 at 1:46 AM, Khem Raj wrote:
>>> On Feb 18, 2016, at 10:33 AM, Fabio Berton
>>> wrote:
>>> I noticed that a few days ago were
On Fri, Feb 19, 2016 at 03:04:14PM +0100, Martin Jansa wrote:
> * this should be part of the upgrade to 5.7, but the changes
> are important and separate change has higher chance to be
> noticed
> * it's highly recommended to read:
>
>
Signed-off-by: Martin Jansa
---
.../avahi/{avahi_0.6.31.bbappend => avahi_%.bbappend} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename meta-systemd/oe-core/recipes-connectivity/avahi/{avahi_0.6.31.bbappend
=> avahi_%.bbappend} (100%)
diff
Create gpg signed ipk package feeds using the gpg backend if configured.
Signed-off-by: Ioan-Adrian Ratiu
---
meta/classes/sign_package_feed.bbclass | 12 +++-
meta/lib/oe/package_manager.py | 17 +++--
2 files changed, 26 insertions(+), 3
Starting from v2.1 passing passwords directly to gpg does not work
anymore [1], instead a loopback interface must be used otherwise
gpg >2.1 will error out with:
"gpg: signing failed: Inappropriate ioctl for device"
gpg <2.1 does not work with the new --pinentry-mode arg and gives an
invalid
Add support for multiple types of signatures (binary or ascii)
in export_pubkey(). There is no change in behaviour for the function,
the previous implicit default is the new parameter "armor" default.
Signed-off-by: Ioan-Adrian Ratiu
---
meta/lib/oe/gpg_sign.py | 6 --
Implement ipk signing inside the sign_ipk bbclass using the gpg_sign
module and configure signing similar to how rpm does it. sign_ipk uses
gpg_sign's detach_sign because its functionality is identical to package
feed signing.
IPK signing process is a bit different from rpm:
- Signatures are
This patch series extends the gpg_sign module to support ipk signing.
v6 implements Markus' feedback. The most notable change is the sign_ipk
and detach_sign merger, as they were almost identical in functionality.
This also meant a refactoring for detach_sign and a bug fix for the
STDIN file
>
> Could you try:
>
> git clone http://code.ossystems.com.br/meta-python-flask
>
> It should just work ;-)
Thx, that works :)
Cheers,
Sven
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
On 16-02-19 11:32 -0200, Otavio Salvador wrote:
> Agreed but this is a specific framework which is not 'core' to python.
> Do you think we ought to merge those on meta-python or keep them split
> out?
Things that are really core to python are already in OE-Core,
built as part of the python
* this should be part of the upgrade to 5.7, but the changes
are important and separate change has higher chance to be
noticed
* it's highly recommended to read:
http://blog.qt.io/blog/2016/01/13/new-agreement-with-the-kde-free-qt-foundation/
to find out how you're affected check which
On Fri, Feb 19, 2016 at 9:29 AM, Sven Ebenfeld wrote:
...
> Unfortunately I'm unable to get access to the meta-python-flask layer. As
> stated in the commit message, I don't know if all dependencies are fulfilled
> for the flask recipes are fulfilled when building these
On Fri, Feb 19, 2016 at 1:46 AM, Khem Raj wrote:
>> On Feb 18, 2016, at 10:33 AM, Fabio Berton
>> wrote:
>> I noticed that a few days ago were added some python-flask recipes.
>>
>> I've been maintaining a layer with python-flask recipes,
Hello,
On Thu, Feb 18, 2016 at 4:33 PM, Fabio Berton
wrote:
> So, do I send recipes from meta-python-flask to meta-python or we move all
> python-flask recipes from meta-python to meta-python-flask, using a layer
> only for Flask web framework?
I am in favor of
On Thu, Feb 18, 2016 at 6:43 PM, Christopher Larson wrote:
> I think the convention is to add such workarounds to no-static-libs.inc,
> not the recipe, at this time.
For OE-Core, yes. For Meta-OE? I think the recipe is the easiest to
notice when doing the upgrade.
--
Otavio
* 5.7 branch was created in qtsystems and then removed again
OE @ ~/projects/qt-project/qtsystems $ git remote prune origin
Pruning origin
URL: git://code.qt.io/qt/qtsystems.git
* [pruned] origin/5.3
* [pruned] origin/5.7
Signed-off-by: Martin Jansa
---
* fixes following QA:
WARNING: qtwebkit-5.6.99+5.7.0-alpha+gitAUTOINC+e9b369b16f-r0 do_package_qa:
QA Issue: qtwebkit rdepends on libxcomposite, but it isn't a build dependency?
[build-deps]
Signed-off-by: Martin Jansa
---
recipes-qt/qt5/qtwebkit_git.bb | 14
On Fri, Feb 19, 2016 at 6:06 AM, Samuli Piippo wrote:
> On 04.02.2016 13:19, Otavio Salvador wrote:
>>
>> On Wed, Feb 3, 2016 at 1:12 PM, Samuli Piippo
>> wrote:
>>>
>>> Each Qt module's examples can now be enabled with PACKAGECONFIG.
>>>
First I would like to mention why I added these recipes.
Currently I'm working on my Master-Thesis for my studies in Applied IT
Security. The subject is to implement some security scans during image
creation.
This work shall help to prevent rolling out vulnerable firmware images.
One of the tasks
* fonts were removed from qtbase in:
commit c5ceabb9a1caf6b9b7615a28c3097f221772f645
Author: Laszlo Agocs
Date: Mon Aug 17 18:32:41 2015 +0200
Purge all fonts
Signed-off-by: Martin Jansa
---
* xvideo and xinerama were removed in:
commit e824abd987d77efaa085fe1f9fb514d270798d55
Author: Alexander Volkov
Date: Tue Oct 13 18:43:25 2015 +0300
configure: Remove unused options -xvideo and -xinerama
-xvideo was not used even by Qt 4 for a long time.
Signed-off-by: Martin Jansa
---
recipes-qt/qt5/nativesdk-qtbase_git.bb | 2 +-
recipes-qt/qt5/qt5-git.inc | 6 +-
recipes-qt/qt5/qtbase-native_git.bb| 2 +-
.../qt5/qtbase/0001-Add-linux-oe-g-platform.patch | 63
Signed-off-by: Martin Jansa
---
classes/qmake5_base.bbclass | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/classes/qmake5_base.bbclass b/classes/qmake5_base.bbclass
index 5b2633b..c2a8498 100644
--- a/classes/qmake5_base.bbclass
+++
In data giovedì 18 febbraio 2016 17:23:15, Diego Rondini ha scritto:
> Default config of the mysql Webmin module uses paths of a manually installed
> MySQL. This commit adjusts paths to the ones used by MariaDB in OE.
>
Please disregard this version of the patch, patch is for meta-webserver as
Default config of the mysql Webmin module uses paths of a manually installed
MySQL. This commit adjusts paths to the ones used by MariaDB in OE.
Signed-off-by: Diego Rondini
---
.../webmin/files/mysql-config-fix.patch| 50 ++
On 04.02.2016 13:19, Otavio Salvador wrote:
On Wed, Feb 3, 2016 at 1:12 PM, Samuli Piippo
wrote:
Each Qt module's examples can now be enabled with PACKAGECONFIG.
Replace the webkit patch with a PACKAGECONFIG option and follow
common practice by not building
26 matches
Mail list logo