[yocto] Yocto Project Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 296 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-mingw] Windows SDK build fails using meta-qt5

[Joshua Watt]

On Mon, 2019-03-18 at 13:58 +, IGI - Moritz Porst wrote:
> Hello everyone,
> 
> I am trying to compile a windows sdk for my image. I use meta-mingw
> and meta-qt, the target machine is based on meta-intel (corei7-64)
> and the distribution based on poky. My build machine is an ubuntu
> 16.04. I have checked
>  out all layers on their thud branch, except for meta-qt (master). I
> set SDK_MACHINE in local.conf to "x86_64-mingw32" "bitbake core-
> image-minimal -c populate_sdk" results on a clean rebuild (deleted
> sstate-cache and tmp) in (2 errors of this kind):
> 
> """ [...] x86_64-nativesdk-mingw32-pokysdk-mingw32/nativesdk-
> qtbase/5.12.0+gitAUTOINC+13ed06640c-
> r0/git/qmake/library/ioutils.cpp:249:31: error: cannot convert
> 'wchar_t*' to 'LPCSTR' {aka 'const char*'}
> 
> 
> 
> 
> [...] | Makefile:213: recipe for target 'ioutils.o' failed [...]
> 
> [...] ERROR: Task (/opt/thudPoky/meta-qt5/recipes-qt/qt5/nativesdk-
> qtbase_git.bb:do_configure) failed with exit code '1' [...] """

AFAIK, no one is building Qt host tools into the MinGW SDK. That's not
to say it *can't* be done, just that it probably hasn't.

> 
> So I decided to remove sdk tools, hoping to be able to cross compile
> them later, by commenting out in my image:  #inherit populate_sdk_qt5
> 
> 
> 
> This build also failed because the build system tried to invoke
> "cmake --install" on a non-cmake directory. commenting out "inherit
> cmake" however solved the problem and the sdk was created (1.1GB
> .tar.gz file BUT without meta-qt sdk tools). I needed cmake
>  only for a previous cross-compilation, thus commenting out was (at
> least now) no problem.

FYI: There is a known issue that nativesdk-cmake won't actually work on
MinGW if included in the SDK. I don't think this affects you, just be
aware of it. The problem AFAICT is that cmake only accepts unix style
path separators ("/"), but our toolchain environment setup uses the
windows style ("\"). I think it might be possible to switch our
toolchain setup over to use the unix style because Windows is supposed
to accept them as valid for everything but UNC paths, but I haven't
done it because 1) It's a somewhat dangerous change 2) No one has yet
asked to run cmake from the SDK.
> Is meta-mingw capable of compiling an sdk with meta-qt ? Could this
> be a bug ? If yes, should I rather refer to the meta-mingw
> maintainers or the meta-qt5 maintainers ?

It depends on what changes need to made to get it to work. Some changes
might be appropriate for meta-mingw, while others might be more
appropriate for meta-qt5. Getting the Qt maintainers involved to get
their thoughts would be good either way; they might have some ideas on
alternate ways to accomplish what you want.

> Best regards
> 
> Moritz
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> IGI mbH
> 
> Moritz Porst, 
> 
> 
> 
> Langenauer Str. 46
> 
> 57223 Kreuztal, Germany
> 
>  
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Tel.:
> +49 2732 5525 0
> 
> 
> Fax:
> +49 2732 5525 25
> 
> 
> E-mail:
> m.po...@igi-systems.com
> 
> 
> Web:
> www.igi-systems.com
> 
> 
> Follow us:
>  
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Upcoming Events:
> 
> GeoBusiness 2019 London
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Sitz der Gesellschaft / Company domiciled in: Kreuztal
> 
> Handelsregister / Register: Siegen HRB 1975
> 
> Ust ID Nr. / VAT Reg. No.: DE 126 580 027
> 
> Steuer Nr. / Tax No.: 342 / 5873 / 3332
> 
> Geschaeftsfuehrer / Managing Director: Christian GRIMM & Philipp
> GRIMM
> 
> 
> 
> DISCLAIMER
> 
> The information sent by means of this e-mail message is intended for
> the use of the addressee only! Publication, duplication, distribution
> and/or forwarding to third parties of this message, as well as use of
> the information by other persons than the intended
>  recipient, is strictly prohibited. If you have received this
> communication in error, please notify the sender
> immediately by returning it.
> 
> 
> 
-- 
Joshua Watt 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to produce Release.gpg

[Alexander Kanavin]

On Mon, 18 Mar 2019 at 08:14, Mauro Ziliani  wrote:
> Is it possible to sign Release automatically from bitbake?

At the moment signing deb repositories is not supported (but it is
supported for rpm and opkg).
You are welcome to add the missing support,
meta/lib/oe/package_manager.py is where it happens.

Alex
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to produce Release.gpg

[Mauro Ziliani]

Hi all.

I have a system based on Debian package-management.

I need to sign the Release index in Release.gpg when the debian-like 
repository is made.



If I do

bitbake system-image


in tmp/deploy/deb subfolders a Debian repository is saved, but 
Release.gpg missing. Only Release file is present.



Is it possible to sign Release automatically from bitbake?


Best regards,

  MZ

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto