* Yocto Project Status WW09'20
@ 2020-03-03 15:59 ` Stephen Jolley
0 siblings, 0 replies; 12+ messages in thread
From: sjolley.yp.pm @ 2020-03-03 15:59 UTC (permalink / raw)
To: yocto, openembedded-core
[-- Attachment #1: Type: text/plain, Size: 3459 bytes --]
Current Dev Position: YP 3.1 M3 - At Feature Freeze, build pending
Next Deadline: YP 3.1 M3 build date 2/24/2020
Next Team Meetings:
* Bug Triage meeting Thursday Mar. 5th at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
* Monthly Project Meeting Tuesday Mar. 3rd at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Weekly Engineering Sync Tuesday Mar. 10th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Twitch - See http://www.twitch.tv/letoatreidesthe2nd
Key Status/Updates:
* YP 2.7.3 and 3.0.2 have been released.
* YP 3.1 has been announced as an LTS release:
<https://www.yoctoproject.org/yocto-project-long-term-support-announced/>
https://www.yoctoproject.org/yocto-project-long-term-support-announced/
* We are now past M3 feature freeze. A number of key issues have been
addressed, thanks to everyone who contributed:
* psplash systemd race issues fixed (Thanks Scott)
* make mips issue root caused and glibc fix pulled in (Thanks
Victor/Khem)
* ltp upgrade resolved (Thanks Petr)
* util-linux update resolved (Thanks Pierre-Jean)
* Uninative tumbleweed issue resolved (Thanks Michael)
* libgpg-error upgrade (Thanks Alex)
* There were many other fixes and upgrades, thanks all!
* The remaining issues we need to look at addressing before we build
M3 are:
* bind upgrade (needs libuv maintainer fix and resend from Armin)
* coreutils ptest blocked on libmodule-build-perl reproducibility
issue
* Locked signature selftest failure
* SystemExit() intermittent selftest failure
* pseudo sysroot high priority bug
* gcc buildtools tarball solution for centos7 support
* Recipe upgrades are now much less likely to be accepted unless there
is a pressing need, ideally these should be held until 3.1 is released and
development for 3.2 is started. We do not have a tracking branch for 3.2 as
we'd like to focus people on 3.1 right now.
* Bug metrics are not good with a rise in WDD when typically it should
be falling for this point in a release cycle.
YP 3.1 Milestone Dates:
* YP 3.1 M3 build date 2/24/2020
* YP 3.1 M3 release date 3/6/2020
* YP 3.1 M4 build date 3/30/2020
* YP 3.1 M4 release date 4/24/2020
Planned upcoming dot releases:
* YP 3.0.3 build date 5/4/2020
* YP 3.0.3 release date 5/15/2020
* YP 2.7.4 build date 5/18/2020
* YP 2.7.4 release date 5/29/2020
Tracking Metrics:
* WDD 2720 (last week 2665) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1346 (last week 1356)
* Patches in the Pending State: 539 (40%) [last week 543 (40%)]
The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:
<https://wiki.yoctoproject.org/wiki/TSC>
https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at:
<https://wiki.yoctoproject.org/wiki/Weekly_Status>
https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you'd like to see on this
weekly status update, let us know!]
Thanks,
Stephen K. Jolley
Yocto Project Program Manager
* Cell: (208) 244-4460
* Email: sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 36694 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Yocto Project Status WW09'20
@ 2020-03-03 15:59 ` Stephen Jolley
0 siblings, 0 replies; 12+ messages in thread
From: Stephen Jolley @ 2020-03-03 15:59 UTC (permalink / raw)
To: yocto, openembedded-core
[-- Attachment #1: Type: text/plain, Size: 3459 bytes --]
Current Dev Position: YP 3.1 M3 - At Feature Freeze, build pending
Next Deadline: YP 3.1 M3 build date 2/24/2020
Next Team Meetings:
* Bug Triage meeting Thursday Mar. 5th at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
* Monthly Project Meeting Tuesday Mar. 3rd at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Weekly Engineering Sync Tuesday Mar. 10th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Twitch - See http://www.twitch.tv/letoatreidesthe2nd
Key Status/Updates:
* YP 2.7.3 and 3.0.2 have been released.
* YP 3.1 has been announced as an LTS release:
<https://www.yoctoproject.org/yocto-project-long-term-support-announced/>
https://www.yoctoproject.org/yocto-project-long-term-support-announced/
* We are now past M3 feature freeze. A number of key issues have been
addressed, thanks to everyone who contributed:
* psplash systemd race issues fixed (Thanks Scott)
* make mips issue root caused and glibc fix pulled in (Thanks
Victor/Khem)
* ltp upgrade resolved (Thanks Petr)
* util-linux update resolved (Thanks Pierre-Jean)
* Uninative tumbleweed issue resolved (Thanks Michael)
* libgpg-error upgrade (Thanks Alex)
* There were many other fixes and upgrades, thanks all!
* The remaining issues we need to look at addressing before we build
M3 are:
* bind upgrade (needs libuv maintainer fix and resend from Armin)
* coreutils ptest blocked on libmodule-build-perl reproducibility
issue
* Locked signature selftest failure
* SystemExit() intermittent selftest failure
* pseudo sysroot high priority bug
* gcc buildtools tarball solution for centos7 support
* Recipe upgrades are now much less likely to be accepted unless there
is a pressing need, ideally these should be held until 3.1 is released and
development for 3.2 is started. We do not have a tracking branch for 3.2 as
we'd like to focus people on 3.1 right now.
* Bug metrics are not good with a rise in WDD when typically it should
be falling for this point in a release cycle.
YP 3.1 Milestone Dates:
* YP 3.1 M3 build date 2/24/2020
* YP 3.1 M3 release date 3/6/2020
* YP 3.1 M4 build date 3/30/2020
* YP 3.1 M4 release date 4/24/2020
Planned upcoming dot releases:
* YP 3.0.3 build date 5/4/2020
* YP 3.0.3 release date 5/15/2020
* YP 2.7.4 build date 5/18/2020
* YP 2.7.4 release date 5/29/2020
Tracking Metrics:
* WDD 2720 (last week 2665) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1346 (last week 1356)
* Patches in the Pending State: 539 (40%) [last week 543 (40%)]
The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:
<https://wiki.yoctoproject.org/wiki/TSC>
https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at:
<https://wiki.yoctoproject.org/wiki/Weekly_Status>
https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you'd like to see on this
weekly status update, let us know!]
Thanks,
Stephen K. Jolley
Yocto Project Program Manager
* Cell: (208) 244-4460
* Email: sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 36694 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Yocto Project Status WW09'20
2020-03-03 15:59 ` Stephen Jolley
@ 2020-03-04 13:00 ` Alexander Kanavin
-1 siblings, 0 replies; 12+ messages in thread
From: Alexander Kanavin @ 2020-03-04 13:00 UTC (permalink / raw)
To: Stephen K Jolley; +Cc: Yocto discussion list, OE-core
[-- Attachment #1: Type: text/plain, Size: 177 bytes --]
On Tue, 3 Mar 2020 at 16:59, <sjolley.yp.pm@gmail.com> wrote:
> coreutils ptest blocked on libmodule-build-perl reproducibility issue
>
I sent a patch for this.
Alex
[-- Attachment #2: Type: text/html, Size: 581 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [OE-core] Yocto Project Status WW09'20
@ 2020-03-04 13:00 ` Alexander Kanavin
0 siblings, 0 replies; 12+ messages in thread
From: Alexander Kanavin @ 2020-03-04 13:00 UTC (permalink / raw)
To: Stephen K Jolley; +Cc: Yocto discussion list, OE-core, Richard Purdie
[-- Attachment #1: Type: text/plain, Size: 177 bytes --]
On Tue, 3 Mar 2020 at 16:59, <sjolley.yp.pm@gmail.com> wrote:
> coreutils ptest blocked on libmodule-build-perl reproducibility issue
>
I sent a patch for this.
Alex
[-- Attachment #2: Type: text/html, Size: 581 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Yocto Project Status WW09'20
2020-03-04 13:00 ` [OE-core] " Alexander Kanavin
@ 2020-03-04 22:42 ` Richard Purdie
-1 siblings, 0 replies; 12+ messages in thread
From: Richard Purdie @ 2020-03-04 22:42 UTC (permalink / raw)
To: Alexander Kanavin, Stephen K Jolley; +Cc: Yocto discussion list, OE-core
On Wed, 2020-03-04 at 14:00 +0100, Alexander Kanavin wrote:
> On Tue, 3 Mar 2020 at 16:59, <sjolley.yp.pm@gmail.com> wrote:
> > coreutils ptest blocked on libmodule-build-perl reproducibility
> > issue
> >
>
> I sent a patch for this.
Thanks!
Just FYI I think there may also be a couple of other packages coreutils
pulls in and they may also have reproducibility issues (gettext-ptest,
glibc-locale-* and procps*).
Cheers,
Richard
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [OE-core] Yocto Project Status WW09'20
@ 2020-03-04 22:42 ` Richard Purdie
0 siblings, 0 replies; 12+ messages in thread
From: Richard Purdie @ 2020-03-04 22:42 UTC (permalink / raw)
To: Alexander Kanavin, Stephen K Jolley; +Cc: Yocto discussion list, OE-core
On Wed, 2020-03-04 at 14:00 +0100, Alexander Kanavin wrote:
> On Tue, 3 Mar 2020 at 16:59, <sjolley.yp.pm@gmail.com> wrote:
> > coreutils ptest blocked on libmodule-build-perl reproducibility
> > issue
> >
>
> I sent a patch for this.
Thanks!
Just FYI I think there may also be a couple of other packages coreutils
pulls in and they may also have reproducibility issues (gettext-ptest,
glibc-locale-* and procps*).
Cheers,
Richard
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Yocto Project Status WW09'20
2020-03-04 22:42 ` [OE-core] " Richard Purdie
@ 2020-03-06 21:53 ` Alexander Kanavin
-1 siblings, 0 replies; 12+ messages in thread
From: Alexander Kanavin @ 2020-03-06 21:53 UTC (permalink / raw)
To: Richard Purdie; +Cc: Yocto discussion list, OE-core
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
On Wed, 4 Mar 2020 at 23:42, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
>
> Just FYI I think there may also be a couple of other packages coreutils
> pulls in and they may also have reproducibility issues (gettext-ptest,
> glibc-locale-* and procps*).
>
Patch for gettext also sent :) glibc-locale and procps I could not
reproduce :-/
Alex
[-- Attachment #2: Type: text/html, Size: 708 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [OE-core] Yocto Project Status WW09'20
@ 2020-03-06 21:53 ` Alexander Kanavin
0 siblings, 0 replies; 12+ messages in thread
From: Alexander Kanavin @ 2020-03-06 21:53 UTC (permalink / raw)
To: Richard Purdie; +Cc: Stephen K Jolley, Yocto discussion list, OE-core
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
On Wed, 4 Mar 2020 at 23:42, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
>
> Just FYI I think there may also be a couple of other packages coreutils
> pulls in and they may also have reproducibility issues (gettext-ptest,
> glibc-locale-* and procps*).
>
Patch for gettext also sent :) glibc-locale and procps I could not
reproduce :-/
Alex
[-- Attachment #2: Type: text/html, Size: 708 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Yocto Project Status WW09'20
2020-03-06 21:53 ` [OE-core] " Alexander Kanavin
@ 2020-03-07 16:58 ` Richard Purdie
-1 siblings, 0 replies; 12+ messages in thread
From: Richard Purdie @ 2020-03-07 16:58 UTC (permalink / raw)
To: Alexander Kanavin; +Cc: Yocto discussion list, OE-core
On Fri, 2020-03-06 at 22:53 +0100, Alexander Kanavin wrote:
> On Wed, 4 Mar 2020 at 23:42, Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
> > Just FYI I think there may also be a couple of other packages
> > coreutils
> > pulls in and they may also have reproducibility issues (gettext-
> > ptest,
> > glibc-locale-* and procps*).
>
> Patch for gettext also sent :) glibc-locale and procps I could not
> reproduce :-/
Thanks for that fix, it helps!
FWIW, what I'm seeing with glibc-locale is that these files "disappear"
from the packages in one of my builds:
./usr/share/locale/vi/LC_MESSAGES/libc.mo
./usr/share/locale/ko/LC_MESSAGES/libc.mo
./usr/share/locale/en_GB/LC_MESSAGES/libc.mo
./usr/share/locale/ca/LC_MESSAGES/libc.mo
./usr/share/locale/fr/LC_MESSAGES/libc.mo
./usr/share/locale/pl/LC_MESSAGES/libc.mo
./usr/share/locale/id/LC_MESSAGES/libc.mo
./usr/share/locale/hr/LC_MESSAGES/libc.mo
./usr/share/locale/uk/LC_MESSAGES/libc.mo
./usr/share/locale/ja/LC_MESSAGES/libc.mo
./usr/share/locale/gl/LC_MESSAGES/libc.mo
./usr/share/locale/es/LC_MESSAGES/libc.mo
./usr/share/locale/el/LC_MESSAGES/libc.mo
./usr/share/locale/pt_BR/LC_MESSAGES/libc.mo
./usr/share/locale/sl/LC_MESSAGES/libc.mo
./usr/share/locale/lt/LC_MESSAGES/libc.mo
./usr/share/locale/rw/LC_MESSAGES/libc.mo
./usr/share/locale/sv/LC_MESSAGES/libc.mo
./usr/share/locale/cs/LC_MESSAGES/libc.mo
./usr/share/locale/nl/LC_MESSAGES/libc.mo
./usr/share/locale/zh_CN/LC_MESSAGES/libc.mo
./usr/share/locale/ia/LC_MESSAGES/libc.mo
./usr/share/locale/fi/LC_MESSAGES/libc.mo
./usr/share/locale/be/LC_MESSAGES/libc.mo
./usr/share/locale/ru/LC_MESSAGES/libc.mo
./usr/share/locale/nb/LC_MESSAGES/libc.mo
./usr/share/locale/zh_TW/LC_MESSAGES/libc.mo
./usr/share/locale/tr/LC_MESSAGES/libc.mo
./usr/share/locale/de/LC_MESSAGES/libc.mo
./usr/share/locale/da/LC_MESSAGES/libc.mo
./usr/share/locale/pt/LC_MESSAGES/libc.mo
./usr/share/locale/hu/LC_MESSAGES/libc.mo
./usr/share/locale/eo/LC_MESSAGES/libc.mo
./usr/share/locale/it/LC_MESSAGES/libc.mo
./usr/share/locale/bg/LC_MESSAGES/libc.mo
./usr/share/locale/sk/LC_MESSAGES/libc.mo
I can conform they're not in the glibc stashed-locale sstate object so
they disappear somewhere before that in the glibc recipe itself.
Quite where/why I don't know as yet.
For procps, the timestamps in the output are different, that is the
only difference. That means something is indeterminate with the source
epoch for that recipe. Again, why, I don't know. The two stamps are:
2019-12-08·04:06:03
2019-12-08·04:05:49
This latter one could potentially be a bug in hashequiv (cc Joshua). It
may need that stamps patch I have fixed up to resolve it. The fix it
needs is to make it apply only to certain tasks.
Cheers,
Richard
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [OE-core] Yocto Project Status WW09'20
@ 2020-03-07 16:58 ` Richard Purdie
0 siblings, 0 replies; 12+ messages in thread
From: Richard Purdie @ 2020-03-07 16:58 UTC (permalink / raw)
To: Alexander Kanavin; +Cc: Stephen K Jolley, Yocto discussion list, OE-core
On Fri, 2020-03-06 at 22:53 +0100, Alexander Kanavin wrote:
> On Wed, 4 Mar 2020 at 23:42, Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
> > Just FYI I think there may also be a couple of other packages
> > coreutils
> > pulls in and they may also have reproducibility issues (gettext-
> > ptest,
> > glibc-locale-* and procps*).
>
> Patch for gettext also sent :) glibc-locale and procps I could not
> reproduce :-/
Thanks for that fix, it helps!
FWIW, what I'm seeing with glibc-locale is that these files "disappear"
from the packages in one of my builds:
./usr/share/locale/vi/LC_MESSAGES/libc.mo
./usr/share/locale/ko/LC_MESSAGES/libc.mo
./usr/share/locale/en_GB/LC_MESSAGES/libc.mo
./usr/share/locale/ca/LC_MESSAGES/libc.mo
./usr/share/locale/fr/LC_MESSAGES/libc.mo
./usr/share/locale/pl/LC_MESSAGES/libc.mo
./usr/share/locale/id/LC_MESSAGES/libc.mo
./usr/share/locale/hr/LC_MESSAGES/libc.mo
./usr/share/locale/uk/LC_MESSAGES/libc.mo
./usr/share/locale/ja/LC_MESSAGES/libc.mo
./usr/share/locale/gl/LC_MESSAGES/libc.mo
./usr/share/locale/es/LC_MESSAGES/libc.mo
./usr/share/locale/el/LC_MESSAGES/libc.mo
./usr/share/locale/pt_BR/LC_MESSAGES/libc.mo
./usr/share/locale/sl/LC_MESSAGES/libc.mo
./usr/share/locale/lt/LC_MESSAGES/libc.mo
./usr/share/locale/rw/LC_MESSAGES/libc.mo
./usr/share/locale/sv/LC_MESSAGES/libc.mo
./usr/share/locale/cs/LC_MESSAGES/libc.mo
./usr/share/locale/nl/LC_MESSAGES/libc.mo
./usr/share/locale/zh_CN/LC_MESSAGES/libc.mo
./usr/share/locale/ia/LC_MESSAGES/libc.mo
./usr/share/locale/fi/LC_MESSAGES/libc.mo
./usr/share/locale/be/LC_MESSAGES/libc.mo
./usr/share/locale/ru/LC_MESSAGES/libc.mo
./usr/share/locale/nb/LC_MESSAGES/libc.mo
./usr/share/locale/zh_TW/LC_MESSAGES/libc.mo
./usr/share/locale/tr/LC_MESSAGES/libc.mo
./usr/share/locale/de/LC_MESSAGES/libc.mo
./usr/share/locale/da/LC_MESSAGES/libc.mo
./usr/share/locale/pt/LC_MESSAGES/libc.mo
./usr/share/locale/hu/LC_MESSAGES/libc.mo
./usr/share/locale/eo/LC_MESSAGES/libc.mo
./usr/share/locale/it/LC_MESSAGES/libc.mo
./usr/share/locale/bg/LC_MESSAGES/libc.mo
./usr/share/locale/sk/LC_MESSAGES/libc.mo
I can conform they're not in the glibc stashed-locale sstate object so
they disappear somewhere before that in the glibc recipe itself.
Quite where/why I don't know as yet.
For procps, the timestamps in the output are different, that is the
only difference. That means something is indeterminate with the source
epoch for that recipe. Again, why, I don't know. The two stamps are:
2019-12-08·04:06:03
2019-12-08·04:05:49
This latter one could potentially be a bug in hashequiv (cc Joshua). It
may need that stamps patch I have fixed up to resolve it. The fix it
needs is to make it apply only to certain tasks.
Cheers,
Richard
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Yocto Project Status WW09'20
2020-03-07 16:58 ` [OE-core] " Richard Purdie
@ 2020-03-07 17:02 ` Richard Purdie
-1 siblings, 0 replies; 12+ messages in thread
From: Richard Purdie @ 2020-03-07 17:02 UTC (permalink / raw)
To: Alexander Kanavin; +Cc: Yocto discussion list, OE-core
On Sat, 2020-03-07 at 16:58 +0000, Richard Purdie wrote:
> On Fri, 2020-03-06 at 22:53 +0100, Alexander Kanavin wrote:
> > On Wed, 4 Mar 2020 at 23:42, Richard Purdie <
> > richard.purdie@linuxfoundation.org> wrote:
> > > Just FYI I think there may also be a couple of other packages
> > > coreutils
> > > pulls in and they may also have reproducibility issues (gettext-
> > > ptest,
> > > glibc-locale-* and procps*).
> >
> > Patch for gettext also sent :) glibc-locale and procps I could not
> > reproduce :-/
>
> Thanks for that fix, it helps!
>
> FWIW, what I'm seeing with glibc-locale is that these files
> "disappear"
> from the packages in one of my builds:
>
> ./usr/share/locale/vi/LC_MESSAGES/libc.mo
> ./usr/share/locale/ko/LC_MESSAGES/libc.mo
> ./usr/share/locale/en_GB/LC_MESSAGES/libc.mo
> ./usr/share/locale/ca/LC_MESSAGES/libc.mo
> ./usr/share/locale/fr/LC_MESSAGES/libc.mo
> ./usr/share/locale/pl/LC_MESSAGES/libc.mo
> ./usr/share/locale/id/LC_MESSAGES/libc.mo
> ./usr/share/locale/hr/LC_MESSAGES/libc.mo
> ./usr/share/locale/uk/LC_MESSAGES/libc.mo
> ./usr/share/locale/ja/LC_MESSAGES/libc.mo
> ./usr/share/locale/gl/LC_MESSAGES/libc.mo
> ./usr/share/locale/es/LC_MESSAGES/libc.mo
> ./usr/share/locale/el/LC_MESSAGES/libc.mo
> ./usr/share/locale/pt_BR/LC_MESSAGES/libc.mo
> ./usr/share/locale/sl/LC_MESSAGES/libc.mo
> ./usr/share/locale/lt/LC_MESSAGES/libc.mo
> ./usr/share/locale/rw/LC_MESSAGES/libc.mo
> ./usr/share/locale/sv/LC_MESSAGES/libc.mo
> ./usr/share/locale/cs/LC_MESSAGES/libc.mo
> ./usr/share/locale/nl/LC_MESSAGES/libc.mo
> ./usr/share/locale/zh_CN/LC_MESSAGES/libc.mo
> ./usr/share/locale/ia/LC_MESSAGES/libc.mo
> ./usr/share/locale/fi/LC_MESSAGES/libc.mo
> ./usr/share/locale/be/LC_MESSAGES/libc.mo
> ./usr/share/locale/ru/LC_MESSAGES/libc.mo
> ./usr/share/locale/nb/LC_MESSAGES/libc.mo
> ./usr/share/locale/zh_TW/LC_MESSAGES/libc.mo
> ./usr/share/locale/tr/LC_MESSAGES/libc.mo
> ./usr/share/locale/de/LC_MESSAGES/libc.mo
> ./usr/share/locale/da/LC_MESSAGES/libc.mo
> ./usr/share/locale/pt/LC_MESSAGES/libc.mo
> ./usr/share/locale/hu/LC_MESSAGES/libc.mo
> ./usr/share/locale/eo/LC_MESSAGES/libc.mo
> ./usr/share/locale/it/LC_MESSAGES/libc.mo
> ./usr/share/locale/bg/LC_MESSAGES/libc.mo
> ./usr/share/locale/sk/LC_MESSAGES/libc.mo
>
> I can conform they're not in the glibc stashed-locale sstate object
> so
> they disappear somewhere before that in the glibc recipe itself.
>
> Quite where/why I don't know as yet.
Just to save anyone digging, the difference is in configure, one has
msgfmt in the sysroot, one does not. It is there later in the build so
its probably task dependencies not being right.
Cheers,
Richard
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [OE-core] Yocto Project Status WW09'20
@ 2020-03-07 17:02 ` Richard Purdie
0 siblings, 0 replies; 12+ messages in thread
From: Richard Purdie @ 2020-03-07 17:02 UTC (permalink / raw)
To: Alexander Kanavin; +Cc: Yocto discussion list, OE-core
On Sat, 2020-03-07 at 16:58 +0000, Richard Purdie wrote:
> On Fri, 2020-03-06 at 22:53 +0100, Alexander Kanavin wrote:
> > On Wed, 4 Mar 2020 at 23:42, Richard Purdie <
> > richard.purdie@linuxfoundation.org> wrote:
> > > Just FYI I think there may also be a couple of other packages
> > > coreutils
> > > pulls in and they may also have reproducibility issues (gettext-
> > > ptest,
> > > glibc-locale-* and procps*).
> >
> > Patch for gettext also sent :) glibc-locale and procps I could not
> > reproduce :-/
>
> Thanks for that fix, it helps!
>
> FWIW, what I'm seeing with glibc-locale is that these files
> "disappear"
> from the packages in one of my builds:
>
> ./usr/share/locale/vi/LC_MESSAGES/libc.mo
> ./usr/share/locale/ko/LC_MESSAGES/libc.mo
> ./usr/share/locale/en_GB/LC_MESSAGES/libc.mo
> ./usr/share/locale/ca/LC_MESSAGES/libc.mo
> ./usr/share/locale/fr/LC_MESSAGES/libc.mo
> ./usr/share/locale/pl/LC_MESSAGES/libc.mo
> ./usr/share/locale/id/LC_MESSAGES/libc.mo
> ./usr/share/locale/hr/LC_MESSAGES/libc.mo
> ./usr/share/locale/uk/LC_MESSAGES/libc.mo
> ./usr/share/locale/ja/LC_MESSAGES/libc.mo
> ./usr/share/locale/gl/LC_MESSAGES/libc.mo
> ./usr/share/locale/es/LC_MESSAGES/libc.mo
> ./usr/share/locale/el/LC_MESSAGES/libc.mo
> ./usr/share/locale/pt_BR/LC_MESSAGES/libc.mo
> ./usr/share/locale/sl/LC_MESSAGES/libc.mo
> ./usr/share/locale/lt/LC_MESSAGES/libc.mo
> ./usr/share/locale/rw/LC_MESSAGES/libc.mo
> ./usr/share/locale/sv/LC_MESSAGES/libc.mo
> ./usr/share/locale/cs/LC_MESSAGES/libc.mo
> ./usr/share/locale/nl/LC_MESSAGES/libc.mo
> ./usr/share/locale/zh_CN/LC_MESSAGES/libc.mo
> ./usr/share/locale/ia/LC_MESSAGES/libc.mo
> ./usr/share/locale/fi/LC_MESSAGES/libc.mo
> ./usr/share/locale/be/LC_MESSAGES/libc.mo
> ./usr/share/locale/ru/LC_MESSAGES/libc.mo
> ./usr/share/locale/nb/LC_MESSAGES/libc.mo
> ./usr/share/locale/zh_TW/LC_MESSAGES/libc.mo
> ./usr/share/locale/tr/LC_MESSAGES/libc.mo
> ./usr/share/locale/de/LC_MESSAGES/libc.mo
> ./usr/share/locale/da/LC_MESSAGES/libc.mo
> ./usr/share/locale/pt/LC_MESSAGES/libc.mo
> ./usr/share/locale/hu/LC_MESSAGES/libc.mo
> ./usr/share/locale/eo/LC_MESSAGES/libc.mo
> ./usr/share/locale/it/LC_MESSAGES/libc.mo
> ./usr/share/locale/bg/LC_MESSAGES/libc.mo
> ./usr/share/locale/sk/LC_MESSAGES/libc.mo
>
> I can conform they're not in the glibc stashed-locale sstate object
> so
> they disappear somewhere before that in the glibc recipe itself.
>
> Quite where/why I don't know as yet.
Just to save anyone digging, the difference is in configure, one has
msgfmt in the sysroot, one does not. It is there later in the build so
its probably task dependencies not being right.
Cheers,
Richard
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2020-03-07 17:02 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-03-03 15:59 Yocto Project Status WW09'20 sjolley.yp.pm
2020-03-03 15:59 ` Stephen Jolley
2020-03-04 13:00 ` Alexander Kanavin
2020-03-04 13:00 ` [OE-core] " Alexander Kanavin
2020-03-04 22:42 ` Richard Purdie
2020-03-04 22:42 ` [OE-core] " Richard Purdie
2020-03-06 21:53 ` Alexander Kanavin
2020-03-06 21:53 ` [OE-core] " Alexander Kanavin
2020-03-07 16:58 ` Richard Purdie
2020-03-07 16:58 ` [OE-core] " Richard Purdie
2020-03-07 17:02 ` Richard Purdie
2020-03-07 17:02 ` [OE-core] " Richard Purdie
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.