On 04/16/2013 04:53 PM, Neil Bothwick wrote:
> On Tue, 16 Apr 2013 13:18:51 -0500, Paul Hartman wrote:
>
>>> It's unfortunate there's no tool to perform as revdep-rebuild,
>>> except checking that, e.g. a package was built with the current
>>> CHOST or CFLAGS set. The fact that I can run 'emerge
On Tue, 16 Apr 2013 13:18:51 -0500, Paul Hartman wrote:
> > It's unfortunate there's no tool to perform as revdep-rebuild, except
> > checking that, e.g. a package was built with the current CHOST or
> > CFLAGS set. The fact that I can run 'emerge --info $atomname' to get
> > the build environment
On Tue, Apr 16, 2013 at 1:09 PM, Michael Mol wrote:
>
> It's unfortunate there's no tool to perform as revdep-rebuild, except
> checking that, e.g. a package was built with the current CHOST or CFLAGS
> set. The fact that I can run 'emerge --info $atomname' to get the build
> environment for a giv
On 04/16/2013 02:03 PM, Tanstaafl wrote:
> On 2013-04-16 12:12 PM, Michael Mol wrote:
>> I must have missed where you ran emerge -e @world. Oops. :)
>
> I didn't... I was replying to your comment that implied that I thought I
> had rebuilt my entire 'system', when in fact I specified '@system',
>
On 2013-04-16 12:12 PM, Michael Mol wrote:
I must have missed where you ran emerge -e @world. Oops. :)
I didn't... I was replying to your comment that implied that I thought I
had rebuilt my entire 'system', when in fact I specified '@system',
meaning, only those packages in @system... :)
On 04/16/2013 12:43 PM, Bruce Hill wrote:
> On Fri, Apr 12, 2013 at 04:48:25PM +, Grant Edwards wrote:
>>
>> Yea, I always had problems with that. I'd edit the LILO config file,
>> forget to run the update command, reboot, then spend an embarassing
>> amount of time trying to figure out why my
On Fri, Apr 12, 2013 at 04:48:25PM +, Grant Edwards wrote:
>
> Yea, I always had problems with that. I'd edit the LILO config file,
> forget to run the update command, reboot, then spend an embarassing
> amount of time trying to figure out why my new kernel behaved exactly
> like my old kerne
On 04/16/2013 11:50 AM, Tanstaafl wrote:
> On 2013-04-16 11:28 AM, Michael Mol wrote:
>> To be clear, you didn't rebuild the entire system. You rebuilt core
>> packages. To rebuild the entire system, it'd be:
>>
>> emerge -e @world
>
> Correct - which is why I said @system... ;)
>
>> # Plus what
On 2013-04-16 11:28 AM, Michael Mol wrote:
To be clear, you didn't rebuild the entire system. You rebuilt core
packages. To rebuild the entire system, it'd be:
emerge -e @world
Correct - which is why I said @system... ;)
# Plus whatever else there is.
Hmmm... are there really packages tha
On 04/16/2013 11:23 AM, Tanstaafl wrote:
> On 2013-04-15 2:02 PM, Michael Mol wrote:
>> Were this one of my systems (none of which is in a prod scenario, so
>> take it with a grain of salt), I'd emerge -e --keep-going @system, and
>> then emerge --resume a few times. You're stuck in something not
On 2013-04-15 2:02 PM, Michael Mol wrote:
Were this one of my systems (none of which is in a prod scenario, so
take it with a grain of salt), I'd emerge -e --keep-going @system, and
then emerge --resume a few times. You're stuck in something not unlike a
bootstrap scenario.
Ok, well, the DB wa
11 matches
Mail list logo
