From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>,
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
Michael Halstead <mhalstead@linuxfoundation.org>
Subject: Re: [OE-core] Latest AB-INT unexplained mystery failure
Date: Wed, 23 Oct 2024 16:35:01 +0100 [thread overview]
Message-ID: <a9f2fa0b0a02f6a6d6db424f8e6830854086154a.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj-O5fBgkHmoMie-x9V4EVG5=aQ14oN2gj3NG7FmQmVDQQ@mail.gmail.com>
On Wed, 2024-10-23 at 17:33 +0200, Alexander Kanavin wrote:
> On Wed, 23 Oct 2024 at 17:29, Khem Raj <raj.khem@gmail.com> wrote:
>
> > > Yes, ideally we'd track it down and get it fixed properly but
> > > we're not
> > > really setup to debug Debian bugs in old releases and we have
> > > other
> > > more pressing problems.
> >
> >
> > I agree with this. I was wondering if there is some aspects that
> > Debian community can be made aware of the problem ?
>
> If we can't make it easy for them to reproduce (and we can't), then
> reporting is not likely to achieve much. WONTFIX WORKSFORME and all
> that.
It is also in Debian 11 (old stable), not Debian 12 so it is getting
fairly old now. I suspect there will be less interest in the older
release.
Cheers,
Richard
prev parent reply other threads:[~2024-10-23 15:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17FE0CA1425F2338.24631@lists.openembedded.org>
2024-10-14 13:46 ` [OE-core] Latest AB-INT unexplained mystery failure Richard Purdie
2024-10-22 13:30 ` Ross Burton
[not found] ` <17FE55BCAF4D83DD.4702@lists.openembedded.org>
2024-10-14 16:11 ` Richard Purdie
2024-10-14 20:40 ` Richard Purdie
2024-10-15 8:23 ` Richard Purdie
2024-10-15 10:09 ` Richard Purdie
2024-10-15 8:18 ` Richard Purdie
2024-10-19 11:05 ` Richard Purdie
[not found] ` <17FFD5DF016C394D.24795@lists.openembedded.org>
2024-10-19 21:48 ` Richard Purdie
2024-10-21 10:55 ` Alexander Kanavin
2024-10-22 9:58 ` Richard Purdie
2024-10-22 19:48 ` Michael Halstead
2024-10-23 15:28 ` Khem Raj
2024-10-23 15:33 ` Alexander Kanavin
2024-10-23 15:35 ` Richard Purdie [this message]
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=a9f2fa0b0a02f6a6d6db424f8e6830854086154a.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=mhalstead@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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