From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python-2.7 && python-updater
Date: Sun, 27 Mar 2011 00:44:15 +0000 [thread overview]
Message-ID: <20110327004415.00739ed6@digimed.co.uk> (raw)
In-Reply-To: <AANLkTinVofoNTE2dSKzN+jp2WKOW9yuc_zrWkT0ZS6t5@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
On Sat, 26 Mar 2011 14:33:14 -0700, Mark Knecht wrote:
> > Aren't those manually added to the list by python-updater? So you
> > need to use -dmanual to prevent further rebuilding of them.
> I guess I'm not clear on the use of 'manual' here.
It's explained in the manual page (sorry :)
Manual means manually added to the list by python-updater, rather than
using any sort of detection.
> They are
> automatically added. If they are correctly rebuilt then they shouldn't
> need to be added a second time, correct? However they are. (Over and
> over...)
>
> Basically, it is my understanding that if everything is correctly
> updated then on the second pass it should say there's nothing to do,
> right?
If it can determine that that's the case, yes. Packages are added
manually because python-updater cannot tell for sure whether they should
be rebuilt this time. That's certainly true for ooo-bin and boost, lnd
prevented by -dmanual. app-emulation/emul-linux-x86-baselibs seems
different, I've just been hit by this one, so I ignored it after the
first build. I suspect a bug has already been reported.
--
Neil Bothwick
If at first you don't succeed, you'll get a lot of free advice from
folks who didn't succeed either.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-03-27 0:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 0:11 [gentoo-user] python-2.7 && python-updater Mark Knecht
2011-03-25 0:28 ` Dale
2011-03-25 3:42 ` Amankwah
2011-03-25 4:48 ` Paul Hartman
2011-03-25 9:37 ` Dale
2011-03-25 9:50 ` Neil Bothwick
2011-03-25 13:56 ` Mark Knecht
2011-03-25 14:26 ` Neil Bothwick
2011-03-25 18:14 ` [gentoo-user] humor: " James
2011-03-25 14:33 ` [gentoo-user] " Roman Zilka
2011-03-25 16:44 ` Dale
2011-03-25 14:33 ` Paul Hartman
2011-03-25 16:46 ` Dale
2011-03-28 13:22 ` KH
2011-03-28 15:02 ` Mark Knecht
2011-03-28 15:41 ` Roman Zilka
2011-03-29 8:26 ` KH
2011-03-25 13:02 ` [gentoo-user] " Simon Siemonsma
2011-03-25 16:50 ` Dale
2011-03-25 19:09 ` [gentoo-user] " Stéphane Guedon
2011-03-25 19:21 ` Grant
2011-03-25 20:38 ` Neil Bothwick
2011-03-26 19:10 ` Mark Knecht
2011-03-26 19:22 ` Mick
2011-03-26 19:56 ` Mark Knecht
2011-03-26 20:36 ` Bill Longman
2011-03-26 20:53 ` Mark Knecht
2011-03-26 21:12 ` Mick
2011-03-26 21:16 ` Neil Bothwick
2011-03-26 21:33 ` Mark Knecht
2011-03-26 23:06 ` Adam Carter
2011-03-27 0:44 ` Neil Bothwick [this message]
2011-03-27 15:26 ` Mark Knecht
2011-03-27 15:47 ` Jacques Montier
2011-03-27 19:25 ` Neil Bothwick
2011-03-27 19:50 ` Mark Knecht
2011-03-27 20:05 ` Neil Bothwick
2011-03-28 0:45 ` Adam Carter
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=20110327004415.00739ed6@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@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