From: Randolph Sapp <rs@ti.com>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
<rs@ti.com>, <richard.purdie@linuxfoundation.org>,
<alex@linutronix.de>, <otavio@ossystems.com.br>,
<kexin.hao@windriver.com>
Cc: <afd@ti.com>, <detheridge@ti.com>, <denis@denix.org>,
<reatmon@ti.com>, <openembedded-core@lists.openembedded.org>,
<vijayp@ti.com>
Subject: Re: [oe-core][PATCHv13 1/6] emptty: add version 0.15.0
Date: Fri, 16 Jan 2026 18:25:07 -0600 [thread overview]
Message-ID: <DFQFQV6K1PGE.22299JJM7Y6C2@ti.com> (raw)
In-Reply-To: <DF8AN2WTCZLA.1VLMF7YHDLPPO@bootlin.com>
On Fri Dec 26, 2025 at 10:37 AM CST, Mathieu Dubois-Briand wrote:
> On Tue Dec 23, 2025 at 11:01 PM CET, rs wrote:
>> From: Randolph Sapp <rs@ti.com>
>>
>> Add emptty, a "Dead simple CLI Display Manager on TTY". This is a
>> relatively lightweight display manager that supports x11 as well as
>> wayland through both a CLI and an automatic login mechanism.
>>
>> This can effectively replace the custom init scripts for both x11
>> (xserver-nodm-init) and wayland (weston-init) with a single tool with
>> more verbose logging capabilities.
>>
>> This is split into two recipes. The emptty package provides the binary
>> and various agnostic configs while the emptty-conf package provides the
>> default configuration for the application itself. This RPROVIDES
>> virtual-emptty-conf, allowing other recipes to provide their own
>> configurations to override the default behavior.
>>
>> Signed-off-by: Randolph Sapp <rs@ti.com>
>> ---
>
> Hi Randolph,
>
> Thanks for your patch, it got way better.
>
> It looks like the last error is some reproducibility issues:
>
> AssertionError: The following deb packages are different and not in exclusion list:
> /srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/emptty-conf-dbg_1.0-r0_amd64.deb
> /srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/emptty-conf-dev_1.0-r0_amd64.deb
> /srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/emptty-conf_1.0-r0_amd64.deb
> /srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/emptty-dbg_0.15.0-r0_amd64.deb
> /srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/emptty-dev_0.15.0-r0_amd64.deb
> /srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/emptty-doc_0.15.0-r0_amd64.deb
> /srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/emptty-src_0.15.0-r0_amd64.deb
> /srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/emptty_0.15.0-r0_amd64.deb
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/3100
>
> Diffoscope output can be found here:
> https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20251226-g95kquv4/packages/diff-html/
>
> Can you have a look at this?
>
> Thanks,
> Mathieu
Well, it appears to be an issue with cgo applications as a whole. Bug raised
upstream.
https://github.com/golang/go/issues/77218
- Randolph
next prev parent reply other threads:[~2026-01-17 0:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 22:01 [oe-core][PATCHv13 0/6] Display manager proposal for x11 and wayland rs
2025-12-23 22:01 ` [oe-core][PATCHv13 1/6] emptty: add version 0.15.0 rs
2025-12-26 16:37 ` Mathieu Dubois-Briand
2026-01-17 0:25 ` Randolph Sapp [this message]
2025-12-23 22:01 ` [oe-core][PATCHv13 2/6] weston-init: convert to virtual-emptty-conf rs
2025-12-23 22:01 ` [oe-core][PATCHv13 3/6] weston: remove deprecated weston-start scripts rs
2025-12-23 22:01 ` [oe-core][PATCHv13 4/6] xserver-nodm-init: convert to virtual-emptty-conf rs
2025-12-23 22:01 ` [oe-core][PATCHv13 5/6] xuser-account: merge with xserver-nodm-init rs
2025-12-23 22:01 ` [oe-core][PATCHv13 6/6] xsessions: add unique desktop entries rs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DFQFQV6K1PGE.22299JJM7Y6C2@ti.com \
--to=rs@ti.com \
--cc=afd@ti.com \
--cc=alex@linutronix.de \
--cc=denis@denix.org \
--cc=detheridge@ti.com \
--cc=kexin.hao@windriver.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=reatmon@ti.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=vijayp@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox