From: Nathan Scott <nathans@sgi.com>
To: Lawrence Walton <lawrence@the-penguin.otak.com>,
John Hawkes <hawkes@sgi.com>, Luca <kronos@kronoz.cjb.net>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: unable to use dpkg 2.6.15-rc2
Date: Mon, 28 Nov 2005 11:23:50 +1100 [thread overview]
Message-ID: <20051128002350.GC841@frodo> (raw)
In-Reply-To: <20051122214443.GA781@frodo>
On Wed, Nov 23, 2005 at 08:44:43AM +1100, Nathan Scott wrote:
> On Tue, Nov 22, 2005 at 06:20:27PM +0100, Luca wrote:
> > (please CC me, I'm not subscribed)
> >
> > Nathan Scott <nathans@sgi.com> ha scritto:
> > >> It's reproducible in 2.6.15-rc1, 2.6.15-rc1-mm1, 2.6.15-rc1-mm2 and
> > >> 2.6.15-rc2.
> > >>
> > >> It does not occur in 2.6.14.
> > >>
> > >> Most easily triggered by "make clean" in the Linux source, for those of
> > >> you without access to dpkg. But both clean and dpkg will trigger it.
> > >
> > > So far I've not been able to reproduce this; I'm using "make clean"
> > > and it works just fine for me (I'm using the current git tree).
> >
> > Confirmed here with 2.6.15-rc1 an IDE disk. Kernel is UP with
> > CONFIG_PREEMPT and 8KB stack. The following debug options are enabled:
> >
>
> Keith Owens has managed to reproduce this locally, and has been
> working on tracking it back to a single change - so, we'll start
> trying to figure out whats gone wrong here shortly, and will get
> a fix merged as soon as we can.
FYI - this problem is now fixed in Linus' current git tree.
cheers.
--
Nathan
next prev parent reply other threads:[~2005-11-28 0:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 7:52 unable to use dpkg 2.6.15-rc2 Lawrence Walton
2005-11-20 23:08 ` Nathan Scott
2005-11-20 23:41 ` Chris Croswhite
2005-11-21 17:08 ` John Hawkes
2005-11-22 17:20 ` Luca
2005-11-22 21:44 ` Nathan Scott
2005-11-28 0:23 ` Nathan Scott [this message]
2005-11-29 16:21 ` Luca
2005-11-29 20:56 ` Nathan Scott
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=20051128002350.GC841@frodo \
--to=nathans@sgi.com \
--cc=hawkes@sgi.com \
--cc=kronos@kronoz.cjb.net \
--cc=lawrence@the-penguin.otak.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.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