Re: [gentoo-user] Re: What's happened to gentoo-sources?

[Neil Bothwick]

On Fri, 2 Sep 2016 02:33:12 +0200, Kai Krakow wrote:

> Am Thu, 1 Sep 2016 22:56:31 +0100
> schrieb Neil Bothwick :
> 
> > > - so my next upgrade would "force" me into deciding going way down
> > > (probably a bad idea) or up into unknown territory (and this showed:
> > > can also be a problem). Or I can stay with 4.6 until depclean
> > > removed it for good (which will, by the way, remove the files
> > > from /usr/src).
> > 
> > Depclean won't remove it if you add it to world.  
> 
> Multi-slot packages ARE removed by depclean except the last stable
> version - which jumped backwards for me because I used an ~arch kernel
> that was removed from portage.

Not if you specify the version.

> Lesson learned: Keep your eyes open. Maybe I put the kernel slot
> into my world file, with the opposite downside this has. (note to
> myself)

That's exactly what I did before I started using sets.conf. There is no
downside because I don't want depclean to remove a kernel source package,
that's for me to decide on.


-- 
Neil Bothwick

"Two things are infinite: the universe and human stupidity;
 and I'm not sure about the the universe."
 (Albert Einstein)


pgpgTezVDfTlB.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Re: What's happened to gentoo-sources?

[Neil Bothwick]

On Thu, 1 Sep 2016 22:08:19 +0200, Kai Krakow wrote:

> > No one forced you to do anything. You 4.6 kernel was still in boot,
> > your 4.6 sources were still installed. The ebuild was only removed
> > fro the portage tree, nothing was uninstalled from your system unless
> > you did it. Even the ebuild was still on your computer
> > in /var/db/pkg.  
> 
> Of course nobody forced me. I just can't follow how the 4.7 ebuild
> kind-of replaced the 4.6 (and others) ebuild in face of this pretty
> mature oom-killer problem.
> 
> Removal of a 4.6 series ebuild also means there would follow no updates

Are there any updates to the 4.6 series or was is 4.7 considered its
successor by the kernels devs? If the former, I can understand your
point. If the latter, there would be no updates so there is no point.

> - so my next upgrade would "force" me into deciding going way down
> (probably a bad idea) or up into unknown territory (and this showed:
> can also be a problem). Or I can stay with 4.6 until depclean removed
> it for good (which will, by the way, remove the files from /usr/src).

Depclean won't remove it if you add it to world. Or you can add this
to /etc/portage/sets.conf to prevent depclean removing any kernels

[kernels]
class = portage.sets.dbapi.OwnerSet
world-candidate = False
files = /usr/src

Running old or out of date kernels is not an issue with Gentoo. I had a
machine running the same kernel for at least a year, long after it was
removed from the tree, because I had some hardware for which the driver
wouldn't compile with newer kernels.


-- 
Neil Bothwick

[unwieldy legal disclaimer would go here - feel free to type your own]


pgpBTBBqUi0BV.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Re: What's happened to gentoo-sources?

[Alan McKinnon]

On 01/09/2016 22:08, Kai Krakow wrote:

Am Tue, 30 Aug 2016 08:47:22 +0100
schrieb Neil Bothwick :


On Tue, 30 Aug 2016 08:34:55 +0200, Kai Krakow wrote:


Surprise surprise, 4.7 has this (still not fully fixed) oom-killer
bug. When I'm running virtual machines, it still kicks in. I wanted
to stay on 4.6.x until 4.8 is released, and only then switch to
4.7. Now I was forced early (I'm using btrfs), and was instantly
punished by doing so:


No one forced you to do anything. You 4.6 kernel was still in boot,
your 4.6 sources were still installed. The ebuild was only removed
fro the portage tree, nothing was uninstalled from your system unless
you did it. Even the ebuild was still on your computer in /var/db/pkg.


Of course nobody forced me. I just can't follow how the 4.7 ebuild
kind-of replaced the 4.6 (and others) ebuild in face of this pretty
mature oom-killer problem.

Removal of a 4.6 series ebuild also means there would follow no updates
- so my next upgrade would "force" me into deciding going way down
(probably a bad idea) or up into unknown territory (and this showed:
can also be a problem). Or I can stay with 4.6 until depclean removed
it for good (which will, by the way, remove the files from /usr/src).

I think masking had been a much more fair option, especially because
portage has means of displaying me the reasoning behind masking it.

In the end, I simply was really unprepared for this - and this is
usually not how Gentoo works and always worked for me. I'm used to
Gentoo doing better.

Even if the 4.6 series were keyworded - in case of kernel packages they
should not be removed without masking first. I think a lot of people
like to stay - at least temporary - close to kernel mainline because
they want to use the one or other feature.

And then my workflow is always like this: If an ebuild is removed, it's
time to also remove it from my installation and replace it with another
version or an alternative. I usually do this during the masking phase.



Was the ebuild removed from arch or ~arch?

If arch, then you have a point.
If ~arch, then you don't have a point. Gentoo has pretty much always 
expected you to deal with $WHATEVER_HAPPENS on ~arch. There has never 
been a guarantee (not even a loose one) that anything will ever stick 
around in ~arch.


Alan

Re: [gentoo-user] Re: What's happened to gentoo-sources?

[Neil Bothwick]

On Tue, 30 Aug 2016 08:34:55 +0200, Kai Krakow wrote:

> Surprise surprise, 4.7 has this (still not fully fixed) oom-killer bug.
> When I'm running virtual machines, it still kicks in. I wanted to stay
> on 4.6.x until 4.8 is released, and only then switch to 4.7. Now I was
> forced early (I'm using btrfs), and was instantly punished by doing so:

No one forced you to do anything. You 4.6 kernel was still in boot, your
4.6 sources were still installed. The ebuild was only removed fro the
portage tree, nothing was uninstalled from your system unless you did it.
Even the ebuild was still on your computer in /var/db/pkg.


-- 
Neil Bothwick

The cow is nothing but a machine which makes grass fit for us people to
eat.


pgpM_9_S_O6Mh.pgp
Description: OpenPGP digital signature