From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: alex.kanavin@gmail.com, mark.hatle@kernel.crashing.org
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] dpkg: Fix ADMINDIR
Date: Mon, 19 Jan 2026 14:38:13 +0000 [thread overview]
Message-ID: <3d99b9245edf44f560cb198e7bb0cb2ed3ce8159.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj-fAJ4xS2GuHazHeExo7FQduObgdvjXYcq_wShv+sp4mQ@mail.gmail.com>
On Mon, 2026-01-19 at 13:30 +0100, Alexander Kanavin via lists.openembedded.org wrote:
> On Sat, 17 Jan 2026 at 21:57, Mark Hatle via lists.openembedded.org
> <mark.hatle=kernel.crashing.org@lists.openembedded.org> wrote:
> > +Subject: [PATCH] lib/dpkg/options-dirs.c: set_rootfs was not checking
> > + environment
> > +
> > +The set_rootfs function was using the hardcoded ADMINDIR (define). It
> > +should be checking the environment, and then falling back to the define
> > +if not set.
> > +
> > +This matches the behavior in db_dir.c.
> > +
> > +Upstream-Status: Pending
>
> Please no pending patches without a reason. This should be submitted
> upstream first.
I understand the sentiment however I should mention this is blocking
pseudo getting updated to resolve several bugs. I did queue and test
this overnight and can confirm it does fix problems in dpkg once we
merge the pseudo fixes...
Cheers,
Richard
next prev parent reply other threads:[~2026-01-19 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 20:57 [PATCH] dpkg: Fix ADMINDIR Mark Hatle
2026-01-19 12:30 ` [OE-core] " Alexander Kanavin
2026-01-19 14:38 ` Richard Purdie [this message]
2026-01-19 21:53 ` Mark Hatle
2026-01-20 17:18 ` Alexander Kanavin
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=3d99b9245edf44f560cb198e7bb0cb2ed3ce8159.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=mark.hatle@kernel.crashing.org \
--cc=openembedded-core@lists.openembedded.org \
/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