From: Kai Krakow <hurikhan77@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: What's happened to gentoo-sources?
Date: Fri, 2 Sep 2016 02:33:12 +0200 [thread overview]
Message-ID: <20160902023312.356b1695@jupiter.sol.kaishome.de> (raw)
In-Reply-To: 20160901225631.20714da4@phoucgh.digimed.co.uk
[-- Attachment #1: Type: text/plain, Size: 2106 bytes --]
Am Thu, 1 Sep 2016 22:56:31 +0100
schrieb Neil Bothwick <neil@digimed.co.uk>:
> > - 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.
The following happened:
# emerge -DNua world
Reinstalled 4.4 for me. Problem here: I didn't exactly distinguish that
4.4.something is not 4.6.something in the result list. So I continued
with:
# emerge --depclean -a
# cd /usr/src/linux && make oldconfig && ... the usual stuff
Wow, that went fast. Then, I realized why: I just depcleaned my 4.6 and
4.4 compile objects were still there, I tried to reinstall 4.6,
it failed - of course: The package is no longer in portage.
I thought: Okay, there's probably a reason, let's get to 4.7.2 then -
what should possibly go wrong? It's not 4.7.0 and I still have 4.6
in /boot. Yeah, what should go wrong... I shouldn't have asked. TL;DR:
I restored from backup.
This must be coincidence. I wanted to go to stable kernel at next
opportunity. But forward in version, not backward. ;-)
But let's get back to the point:
Depclean does remove multi-slotted kernel sources. It does it with
every multislot package except there's an explicit slot dependency or
you explicitly mention the slot in the world file.
Since I cannot remember such a surprise-removal* happened anytime
before and put me in such a situation, this was completely new to me.
(10+ years of Gentoo usage)
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)
*: This is subjective, I know.
--
Regards,
Kai
Replies to list-only preferred.
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-09-02 0:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 9:12 [gentoo-user] What's happened to gentoo-sources? Peter Humphrey
2016-08-21 9:55 ` Rich Freeman
2016-08-21 10:20 ` Peter Humphrey
2016-08-21 11:28 ` Rich Freeman
2016-08-21 14:23 ` Peter Humphrey
2016-08-21 14:34 ` Alarig Le Lay
2016-08-21 14:50 ` Rich Freeman
2016-08-21 15:06 ` Peter Humphrey
2016-08-23 9:00 ` Tom H
2016-08-30 6:34 ` [gentoo-user] " Kai Krakow
2016-08-30 7:47 ` Neil Bothwick
2016-09-01 20:08 ` Kai Krakow
2016-09-01 20:57 ` Alan McKinnon
2016-09-01 21:56 ` Neil Bothwick
2016-09-02 0:33 ` Kai Krakow [this message]
2016-09-02 9:11 ` Neil Bothwick
2016-09-02 2:38 ` »Q«
2016-09-01 20:14 ` Kai Krakow
2016-08-21 10:38 ` [gentoo-user] " Alarig Le Lay
2016-08-22 11:19 ` Alan Mackenzie
2016-08-22 13:23 ` Peter Humphrey
2016-08-22 13:52 ` Alan Mackenzie
2016-08-23 7:25 ` J. Roeleveld
2016-08-23 8:30 ` Peter Humphrey
2016-08-23 8:53 ` J. Roeleveld
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=20160902023312.356b1695@jupiter.sol.kaishome.de \
--to=hurikhan77@gmail.com \
--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