public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stuart Buckland <stuart@nightime.org.uk>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Strange bug at catalyst2 rc45
Date: Wed, 10 May 2006 11:54:17 +0100	[thread overview]
Message-ID: <1147258457.21430.34.camel@murmur.salmon> (raw)
In-Reply-To: <cc04c5eb0605100335x722f2a90kb9949e7fe2eb842a@mail.gmail.com>

It could be awhile until 2.1 is marked stable.  I haven't seen any
projected time lines for it but I don't tend to follow these things too
closely.

I tried portage-2.0.54-r2 and that seemed to resolve the issue.  I ran
into another issue on the next package to be built but I don't believe
it's at all related.

Stu

On Wed, 2006-05-10 at 07:35 -0300, Douglas Campos wrote:
> They say at the bugreport that it will be marked stable at 2.1
> Let's wait :(
> 
> On 5/10/06, Stuart Buckland <stuart@nightime.org.uk> wrote:
>         On Wed, 2006-05-10 at 08:07 +0100, Stuart Buckland wrote: 
>         > On Tue, 2006-05-09 at 17:44 -0300, Douglas Campos wrote:
>         > > I've got a infinite loop when building stage3 target
>         > >
>         > > it goes well then starts to emerge everything again (from
>         already 
>         > > built pkg's)
>         > >
>         > > does anyone have seen this?
>         >
>         > Funny you should mention this.  I haven't used catalyst in
>         over a year
>         > but came to back to it yesterday in the guise of looking
>         into GNAP. 
>         >
>         > Using the supplied GNAP spec files and snapshot everything
>         builds and
>         > works perfectly.  I took a new snapshot, left everything
>         else the same
>         > and the build got stuck in a infinite loop of emerging the
>         same packages 
>         > again and again.
>         >
>         > Unfortunately I can't offer any help yet as I only
>         discovered it 10
>         > minutes ago.  You're not alone though.
>         >
>         > Stu
>         >
>         >
>         > --
>         > Stuart Buckland < stuart@nightime.org.uk>
>         >
>         
>         Replying to my own message but looks like I've found the
>         problem.  It
>         appears to be a long standing bug in portage.
>         
>         http://forums.gentoo.org/viewtopic-t-457692-highlight-catalyst
>         +loop.html
>         http://bugs.gentoo.org/show_bug.cgi?id=131207
>         
>         Looks like it has been resolved in portage-2.0.54-r2 and there
>         is also a
>         patch available for portage-2.0.54-r1.
>         
>         I haven't tried either yet as I'm (supposed to be) working. :)
>         
>         HTH
>         Stu
>         
>         
>         --
>         Stuart Buckland <stuart@nightime.org.uk>
>         
>         --
>         gentoo-catalyst@gentoo.org mailing list
>         
> 
-- 
Stuart Buckland <stuart@nightime.org.uk>

-- 
gentoo-catalyst@gentoo.org mailing list



      reply	other threads:[~2006-05-10 10:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 20:44 [gentoo-catalyst] Strange bug at catalyst2 rc45 Douglas Campos
2006-05-09 21:03 ` Jonas Bernoulli
2006-05-10  7:07 ` Stuart Buckland
2006-05-10  8:36   ` Stuart Buckland
2006-05-10 10:35     ` Douglas Campos
2006-05-10 10:54       ` Stuart Buckland [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=1147258457.21430.34.camel@murmur.salmon \
    --to=stuart@nightime.org.uk \
    --cc=gentoo-catalyst@lists.gentoo.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