public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: richard.purdie@linuxfoundation.org, alex.kanavin@gmail.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] dpkg: Fix ADMINDIR
Date: Mon, 19 Jan 2026 15:53:03 -0600	[thread overview]
Message-ID: <a1c69479-0aa9-4d75-89a7-05580263cfbf@kernel.crashing.org> (raw)
In-Reply-To: <3d99b9245edf44f560cb198e7bb0cb2ed3ce8159.camel@linuxfoundation.org>

This has been sent to the upstream dpkg mailing list, and should eventually 
appear in the index at "https://lists.debian.org/debian-dpkg/2026/01/maillist.html"

--Mark

On 1/19/26 8:38 AM, Richard Purdie via lists.openembedded.org wrote:
> 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
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#229622): https://lists.openembedded.org/g/openembedded-core/message/229622
> Mute This Topic: https://lists.openembedded.org/mt/117320584/3616948
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [mark.hatle@kernel.crashing.org]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


  reply	other threads:[~2026-01-19 21:53 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
2026-01-19 21:53     ` Mark Hatle [this message]
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=a1c69479-0aa9-4d75-89a7-05580263cfbf@kernel.crashing.org \
    --to=mark.hatle@kernel.crashing.org \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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