On Thu, Apr 16, 2020 at 9:36 PM Denys Dmytriyenko <denis@... <mailto:denis@...>> wrote:
I doubt people that actually send emails to the list use #hashtags.
But the new list server provides this posting feature for anyone to
address
the list and requests poster to add #hashtags - very annoying, indeed:
https://lists.yoctoproject.org/g/yocto/post
there is that. And looking at the history on the server, most of the existing tags came from the web. But a hashtag is created automatically when using '#' in the email subject. that's how #define was created:
https://lists.yoctoproject.org/g/yocto/message/48686
and this email created #hashtags ;-)
I haven't found a way to disable it.. from what I can see we can
1. force every message to have at least one hashtag...
2. bounce message with a new hashtag in $subject
3. remove new hashtag when used in $subject

I think we will need to do some tests to see what #3 does.. But in any case, I don't think we can prevent users from creating hashtags from the web..
Is that causing any issues with patches workflow?

--
Denys
On Thu, Apr 16, 2020 at 03:18:34PM -0400, Randy MacLeod wrote:
> FYI:
>
> I don't know if I missed the memo/tweet about the email archive
feature
> but I just noticed that the new archive site will index emails
> by hashtag:
>
> https://lists.yoctoproject.org/g/yocto
>
> https://lists.yoctoproject.org/g/yocto/hashtags
>
> I thought it was an annoying new behaviour coming from Twitter users
> but now I understand why there are hashtags on my lawn^Hsubject
lines.
>
> ;-)
>
> --
> # Randy MacLeod
> # Wind River Linux

>

There was a gutenprint recipe back in OE-Classic:
https://layers.openembedded.org/layerindex/oe-classic/recipe/12076/
But currently there is no gutenprint available for Yocto.

I tried to build my own recipe. But I got stuck at the stage where the
build process wants to call some generated binaries:
    | ./extract-strings `cat xml-stamp | sed -e
's;^;../../../gutenprint-5.2.11/src/xml/;'` > xmli18n-tmp.h.tmp
    | /lib/ld-linux-armhf.so.3: No such file or directory
So, I introduced a "native" recipe, which just compiles the
"extract-strings" for me:
----------------------------------------------------------------------------------------------------------
SECTION = "libs"
require gutenprint_${PV}.bb
DEPENDS = "gettext-native"
inherit native autotools
EXTRA_OECONG = "\
        --disable-libgutenprintui2 \
            --disable-samples \
        --without-gimp2 \
        --without-doc \
        --disable-nls \
        --disable-nls-macos \
        --without-foomatic \
        --without-foomatic3 \
        --disable-escputil \
        --disable-test \
        --disable-testpattern \
        --without-cups \
               "
do_compile() {
    oe_runmake -C src/xml/ extract-strings
}
-----------------------------------------------------------------------------------------------------------------
The next step is quite unclear for me? How can I tell the build system
not to generate the extract-strings again and use the native instead?
As reference I used the build scripts from openwrt and buildroot. But
I'm not able to translate this build steps to Yocto.
https://github.com/FranciscoBorges/openwrt-printing-packages/blob/master/net/gutenprint/Makefile
https://github.com/buildroot/buildroot/blob/master/package/gutenprint/gutenprint.mk

On 4/15/20 3:25 PM, Paul Eggleton wrote:

Release notes draft attached, including a dedication to Scott
(wasn't sure where to put that so I've just left it at the top) and
contributors list. Let me know if you notice anything
missing/incorrect.

Thanks for pulling this together.

I've also sent out the 3.1 migration guide for the reference
manual, Richard has just merged the changes:

I see the review window is down to an hour before merging. Is code
review by twitter the next new thing ; )

Release notes draft attached, including a dedication to Scott (wasn't sure where to put that so I've just left it at the top) and contributors list. Let me know if you notice anything missing/incorrect. 

I've also sent out the 3.1 migration guide for the reference manual, Richard has just merged the changes:

  http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=dunfell&id=c31ddaba1f3181c577fdaa3ce519a42b6f8f2d9a

Publishing to the website is still TBD, but some review there would be great as well.

Cheers,
Paul

I'm working on a set of platforms that have a FIPs certified OpenSSL.  We are at version 1.0.2l.

I've found that the new version of python in Zeus (2.7.17) requires a newer version of OpenSSL (1.1).

We really don't want to go through a new round of certification, so we want to keep our current OpenSSL (1.0.2l).

I think the easiest solution is to downgrade python 2 back to the version used by Sumo (2.7.15).

I know how to downgrade simple recipes, but python is far from simple.

Can someone give me some guidance on how to approach the downgrade of python2 in Zeus?

Thanks, Mike

Hi Randy,
In my image most of the size is consumed by heavy size packages.
So i have given this task of image size reduction to application team.
If i will remove the dependencies then may be some feature get disabled which could be needed.
Till now i am able to remove only python3 from dependencies.

Thanks,
Ajam Ali
------------------------------------------------------------------------
*From:* Randy MacLeod <randy.macleod@...>
*Sent:* Monday, April 13, 2020 11:18 PM
*To:* Ajam Ali <AjamA@...>; yocto@... <yocto@...>; gley-yocto@m.gmane-mx.org <gley-yocto@m.gmane-mx.org>
*Subject:* Re: [yocto] Image size reduction
**[CAUTION: This Email is from outside the Organization. Do not click links or open attachments unless you trust the sender.]
On 2020-04-04 12:27 p.m., Ajam Ali wrote:

Hi All,

Thanks for your suggestions. I am working on your suggestions.
I will let you know if it did not work for me.

Ajam,
It would be useful if you could reply either way.
If there's still a problem then perhaps someone can help.
If you are able to resolve the issue, then a brief summary
of what you did could help the next person who has a similar
issue.
Thanks,
../Randy

Regards,
Ajam Ali


------------------------------------------------------------------------
*From:* yocto@... <mailto:yocto@...> <yocto@...> <mailto:yocto@...> on behalf of Gmane Admin via lists.yoctoproject.org <gley-yocto=m.gmane-mx.org@...> <mailto:gley-yocto=m.gmane-mx.org@...>
*Sent:* Saturday, April 4, 2020 9:36 PM
*To:* yocto@... <mailto:yocto@...> <yocto@...> <mailto:yocto@...>
*Subject:* Re: [yocto] Image size reduction
[CAUTION: This Email is from outside the Organization. Do not click links or open attachments unless you trust the sender.]

Op 29-03-2020 om 18:28 schreef Ajam Ali:

Hi All,

Actually my current image size is 3.9GB because of heavy size packages
required by my project and without project required packages my image
size in Yocto is 800MB.

So your project adds 3.1GB right

I want to reduce the image size as maximum as possible.

3.1GB is huge. Compare to f.i. Libreoffice (installed 0.5GB or so).
Either your own code has a lot of fat, or you are pulling in lots of
packages you don't really need. But is there no way to advise you
without knowing more.

Please suggest the best possible way so that I could reduce the maximum
possible size(desirable below 1.5 GB).


Thanks in advance,
Ajam Ali


Sent from Outlook Mobile <https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fblhgte&;data=02%7C01%7Cajama%40hcl.com%7Cf719cb14fe674f86f02408d7d8b236b0%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637216132261322392&amp;sdata=8in2t%2B6mXtrsRwa7GmgGQDl69uRzL7g4smj%2Ba3QG9gU%3D&amp;reserved=0

<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fblhgte&data=02%7C01%7Cajama%40hcl.com%7C128e3933213f473fc34a08d7dfd2da33%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637223969041569087&sdata=gY%2FoAEw1u9iOH8l9146xlNknKSslGAhehsRsWa83%2F10%3D&reserved=0>>

::DISCLAIMER::
------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and
intended for the named recipient(s) only. E-mail transmission is not
guaranteed to be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
may contain viruses in transmission. The e mail and its contents (with
or without referred errors) shall therefore not attach any liability on
the originator or HCL or its affiliates. Views or opinions, if any,
presented in this email are solely those of the author and may not
necessarily reflect the views or opinions of HCL or its affiliates. Any
form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior
written consent of authorized representative of HCL is strictly
prohibited. If you have received this email in error please delete it
and notify the sender immediately. Before opening any email and/or
attachments, please check them for viruses and other defects.
------------------------------------------------------------------------

--
# Randy MacLeod
# Wind River Linux

This is the full report for yocto-3.1.rc2:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

======= Summary ========
No high milestone defects.
No new defects are found in this cycle.

Note: Few failures are observed. These are setup issue since running
tests remotely, not real yocto issue.