Re: [gentoo-user] Emerge @system causing gcc downgrade

[White, Phil]

On 8 March 2017 at 11:29, Stroller  wrote:

>
> Could you `grep -i gcc /var/lib/portage/world*` please?
>
> A copy of the whole world file(s) would be great, in fact, ideally as
> plain text attachments.
>

Hi Stroller,
Thanks, (and apologies for the delay).
World file was empty at the time of the previous post - I was still working
on fixing @system.
As mentioned, I was careless with copying over /var from a previous
install. The problem wasn't with the world file, but with the db/pkg lists.
emerge -e did not immediately fix it. However, with patience and a few
continuous fixes, I now have @system back - and am currently waiting for my
previous world packages to finish. Hopefully by tomorrow morning, I should
be able to complete a depclean without issue...


> Also, any chance you could set your mailer to send only plain text emails
> to the list?
>

I wish! Sorry - until I have a 'proper' system working again, I am stuck
with webmail... :(

Thanks again for everyone's help.

Phil

Re: [gentoo-user] Emerge @system causing gcc downgrade

[White, Phil]

On 7 March 2017 at 19:38, Neil Bothwick  wrote:

>
> Please don't top post, it is disliked on this list.
>

Sorry - a consequence of moving away from a proper mail client, and on to a
web-based thing.


> If you copied over /var/db/pkg you have a rather confused and messed up
> system. The safest way to recreate it is probably to move the pkg
> directory elsewhere and then run "emerge -e @world".
>

Yep! I think that would be a polite way of putting it! ;)


> gcc is slotted, so emerging 4.9.4 will not touch your 5.4.0 installation,
> you use gcc-config to choose which one to use. What does gcc-config -l
> show?
>

Just the one line:
[1] i686-pc-linux-gnu-4.9.4

I *think*, that with little time and patience, I can now sort this out.
Thanks for the emerge -e hint. It doesn't seem to be in the emerge man
page, though. What is the long-option name?

Kind regards,

Phil

Re: [gentoo-user] Emerge @system causing gcc downgrade

[White, Phil]

Hi Neil,

Well, this is a new install.
Used Stage3-i686-20170214.tar.bz2
There is nothing in package.accept_keywords that is currently installed (as
far as I know - although it is possible that I might have added ~x86 to
gcc, although in this instance I don't believe that i did)
I have installed some packages, but removed them also (been having problems
with perl)
So currently, updating @world is the same as @system

OK - talking this through is helping. I *have* done something strange here.
The currently installed version is 4.9.4 (from gcc --version), except that
portage believes that 5.4.0 is installed.
My guess is that, since I am trying to rebuild an old system (due to a
hard-drive fail), I have accidentally copied over files that do not belong.
My guess is a completely useless /var/db/pkg/* is confusing the hell out of
portage/emerge.

So - any suggestions how to fix this mess?
Bite the bullet, emerge gcc, and then do a depclean - or can I convince
portage that gcc 4.9.4 is really here?

Thanks,
Phil

On 7 March 2017 at 15:38, Neil Bothwick <n...@digimed.co.uk> wrote:

> On Tue, 7 Mar 2017 15:07:32 +0000, White, Phil wrote:
>
> > I have a new install of Gentoo.
> > emerge -uDpv --newuse @system results in a new slot for gcc,
> > *downgrading* the current version (from 5.4.0 to 4.9.4)
> > No other package is selected for merging.
>
> 4.9.4 is the latest stable. Are you running a stable system with some
> packages in package.accept_keywords? If so, and you gave a specific
> version of gcc, it is possible that version is no longer in the tree -
> 5.4.0-r2 was recently removed.
>
> Use the ~ operator when specifying versions to allow for minor updates
>
> ~sys-devel/gcc-5.4.0
>
> or, in the case of gcc, you can specify a slot
>
> sys-devel/gcc:5.4.0
>
>
> --
> Neil Bothwick
>
> Despite the cost of living it remains popular.
>

Re: [gentoo-user] Emerge @system causing gcc downgrade

[White, Phil]

Sorry Alan, that results in no extra information from emerge.
Still only gcc listed for installation - and nothing else.

--
Phil

On 7 March 2017 at 15:08, Alan McKinnon <alan.mckin...@gmail.com> wrote:

> On 07/03/2017 17:07, White, Phil wrote:
> > Hi,
> >
> > I'm sorry. This is probably a really simple question.
> > I have a new install of Gentoo.
> > emerge -uDpv --newuse @system results in a new slot for gcc,
> > *downgrading* the current version (from 5.4.0 to 4.9.4)
> > No other package is selected for merging.
> >
> > Why??? What command line can I give to show why a new slot is being
> > pulled in?
> > (I wouldn't particularly mind, but as I am on an old x86 celeron, this
> > will take hours to complete, for no obvious benefit...)
> >
> > Thanks
> > Phil
> >
>
>
>
> Add -t option to the command
>
>
> --
> Alan McKinnon
> alan.mckin...@gmail.com
>
>
>

[gentoo-user] Emerge @system causing gcc downgrade

[White, Phil]

Hi,

I'm sorry. This is probably a really simple question.
I have a new install of Gentoo.
emerge -uDpv --newuse @system results in a new slot for gcc, *downgrading*
the current version (from 5.4.0 to 4.9.4)
No other package is selected for merging.

Why??? What command line can I give to show why a new slot is being pulled
in?
(I wouldn't particularly mind, but as I am on an old x86 celeron, this will
take hours to complete, for no obvious benefit...)

Thanks
Phil

Re: [gentoo-user] Rear & Genkernel

[White, Phil]

Hi Alan, Thanks for the reply.

First attempt at install was using emerge. This installs version 1.17.1.
This didn't work, so I removed it, and installed version 2.00 from Git, in
an attempt to fix the problem.

BOTH produce the same error - unable to find a kernel due to the naming
issue described previously.
So firstly I need to know whether Genkernel is incorrectly naming the
kernel, or whether Rear is looking for the wrong name.

Cheers,
Phil

On 6 March 2017 at 22:25, Alan McKinnon <alan.mckin...@gmail.com> wrote:

> On 06/03/2017 23:55, White, Phil wrote:
> > Hi,
> >
> > I'm not sure if this needs submitting as a bug, or if I just need a
> > little help in configuring...
> >
> > I have set up a new install of Gentoo. I use genkernel to create my
> > kernel and initrd.
> > The resulting /boot directory gives:
> >   kernel-genkernel-x86-4.9.6-gentoo-r1
> >
> > My chost is i686-pc-linux-gnu.
> >
> > Now, I also have installed rear (relax-and-recover) v2, from git
> > (app-backup/rear is 1.17.1)
> >
> > Problem: rear is looking for a kernel, and it expects it to be named:
> >   kernel-genkernel-i686-4.9.6-gentoo-r1
> > Since the name doesn't match, it bails out with an error. (This only
> > fails with my i686 machine. Running the same configuration on a 64-bit
> > machine works fine)
> >
> > Question: How am I going to fix this? I don't want to hard code anything
> > in the config file, as this will break when I update the kernel... Is
> > this a 'bug'?
>
>
> Please clarify what version of rear has this problem, and how you
> installed it.
>
> Either way, from the problem description one can see that rear needs
> patching, however:
>
> If it was installed by ortage from an ebuild, then you have a bug to be
> reported to b.g.o.
>
> If you installed from git outside of portage, the you get to patch rear
> yourself
>
> Or, perhaps a third option. Does rear have a config file where you can
> define the naming template for the kernel used? (I don't use rear and
> can't be bothered googling it, the idea just occurred to me)
>
>
> --
> Alan McKinnon
> alan.mckin...@gmail.com
>
>
>

[gentoo-user] Rear & Genkernel

[White, Phil]

Hi,

I'm not sure if this needs submitting as a bug, or if I just need a little
help in configuring...

I have set up a new install of Gentoo. I use genkernel to create my kernel
and initrd.
The resulting /boot directory gives:
  kernel-genkernel-x86-4.9.6-gentoo-r1

My chost is i686-pc-linux-gnu.

Now, I also have installed rear (relax-and-recover) v2, from git
(app-backup/rear is 1.17.1)

Problem: rear is looking for a kernel, and it expects it to be named:
  kernel-genkernel-i686-4.9.6-gentoo-r1
Since the name doesn't match, it bails out with an error. (This only fails
with my i686 machine. Running the same configuration on a 64-bit machine
works fine)

Question: How am I going to fix this? I don't want to hard code anything in
the config file, as this will break when I update the kernel... Is this a
'bug'?

Thanks in advance,

Phil