12624 2018-03-24 07:29:01 +0000 Release information for Rocko 2.4.2 incorrectly states libc update which is not present 2018-12-03 23:58:59 +0000 1 1 5 Infrastructure Website web-content Production x86 Multiple RESOLVED FIXED Medium normal Q3 1 jburgess777 tracy.graydon jefro mhalstead richard.purdie srifenbark stephano tracey.m.erway tracy.graydon --- --- No (bug/feature does not impact docs) oldest_to_newest 79973 0 jburgess777 2018-03-24 07:29:01 +0000 The first lines of the Rocko 2.4.2 release information says: --------------- Fixes --------------- glibc: Update to tip of 2.26 ... This likely refers to the following commit in git which is not actually present in the 2.4.2 release. https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=rocko&id=5ba69a97ab5faa8f3866aaeab1d6eaa3cb8149ed > glibc: Update to tip of 2.26 This view makes it more obvious that the commit was merged several revisions after the yocto-2.4.2 tag: https://git.yoctoproject.org/cgit/cgit.cgi/poky/log/?h=rocko 2018-02-27 glibc: Update to tip of 2.26 ... 2018-02-20 linux-yocto: update genericx86* SRCREVs for v4.12 yocto-2.4.2 rocko-18.0.2 My guess is that the release information was based on the commits in the rocko branch at the time it was released instead of those in the yocto-2.4.2 build tag. 80051 1 srifenbark 2018-03-30 18:32:04 +0000 Hi, Where is the release information referred to in this bug? There are many references to "glibc" throughout the YP documentation. Are you referring to rocko release notes? Can you provide a link to the information generating the confusion here? Thanks, Scott 80058 2 jburgess777 2018-03-31 01:23:57 +0000 Go to https://www.yoctoproject.org/software-overview/downloads/ Click the blue button with the text “RELEASE INFORMATION - YP CORE - ROCKO 2.4.2” The text which pops up in the new window contains the problem, under the ‘Fixes’: YP CORE - ROCKO 2.4.2 ----------------- Known Issues ----------------- https://bugzilla.yoctoproject.org/show_bug.cgi?id=12587 Runtime providers were sometimes changing order during builds, resulting in non-deterministic build results. Example: DEBUG: providers for lib32-initd-functions are: ['lib32-lsbinitscripts', 'lib32-initscripts'] or DEBUG: providers for lib32-initd-functions are: ['lib32-initscripts', 'lib32-lsbinitscripts'] This can lead to test failures. This is fixed with Bitbake rev: 223a0f68530571d2280f526bddbc718fa803a3dc This change ensures we don't rely on the random order of dictonaries in memory and act deterministically. --------------- Fixes --------------- glibc: Update to tip of 2.26 glibc: Adapt do_install_append_aarch64() for usrmerge libtirpc: refresh patches libtirpc: stop dropping in NIS headers libunwind: Fix multilib header conflict - libunwind.h libmpc: fix SRC_URI ... 80137 3 srifenbark 2018-04-05 11:10:06 +0000 Thanks Jon for the additional tracking. I am assigning this to Tracey Erway as it involves the YP website, which I do not maintain. Scott 81859 4 mhalstead 2018-10-15 17:33:18 +0000 Tracy, Looks like we have a releasenotes issue. What do you think about writing and signing new releasenotes with this correction and a note about the change? 82371 5 mhalstead 2018-11-30 17:19:07 +0000 I've removed the following line from the release notes on the website at https://www.yoctoproject.org/software-overview/downloads/archived-releases/ and http://downloads.yoctoproject.org/releases/yocto/yocto-2.4.2/RELEASENOTES. "glibc: Update to tip of 2.26" Is there more to do? 82386 6 tracy.graydon 2018-12-03 23:58:59 +0000 The webpage content and the release notes have both been fixed. I haven't confirmed yet, but I do believe that Jon is spot on that this came from using the branch (and not the tag) to generate the release notes. Typically we use previous relevant release and HEAD on the release branch. That leaves room for exactly this kind of thing. Think the release notes generation should actually happen against previous release and the actual poky hash of the build. I will look into making that change.