Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 396439

Summary: Keep track of packages that need the kernel sources
Product: Portage Development Reporter: Gil Forcada <gforcada>
Component: Enhancement/Feature RequestsAssignee: Portage team <dev-portage>
Status: UNCONFIRMED ---    
Severity: enhancement    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Gil Forcada 2011-12-29 18:41:18 UTC
I just updated my kernel (from gentoo-sources-2.6.38 to gentoo-sources-3.0.6) and before restarting I already emerged virtualbox, networkmanager and upower because I remember seeing them looking at /usr/src/linux to compile.

I do not know if I'm missing something to be rebuilt, after restarting I will know :)

The idea here is that portage, or even better the ebuilds itself, should claim that they need the current kernel headers around so that after each kernel update a notice could be shown to the user to remember that (s)he needs to recompile the following list of packages before restarting/using the applications again with the new kernel.

Reproducible: Always
Comment 1 Arfrever Frehtes Taifersar Arahesis 2011-12-29 18:45:01 UTC
You can use `emerge -1 @module-rebuild` (supported by Portage 2.2).
Comment 2 Zac Medico gentoo-dev 2011-12-29 21:09:45 UTC
(In reply to comment #1)
> You can use `emerge -1 @module-rebuild` (supported by Portage 2.2).

For stable portage, use `emerge -1 /lib/modules`.
Comment 3 Zac Medico gentoo-dev 2011-12-29 21:16:14 UTC
(In reply to comment #0)
> I do not know if I'm missing something to be rebuilt, after restarting I will
> know :)

We might mark this as a duplicate of bug 192319, which is about triggering rebuilds to solve broken reverse run-time dependencies. In this case, the run-time dependencies of relevant packages are broken by the kernel upgrade, and they need to be rebuilt to be compatible with the new kernel.
Comment 4 Gil Forcada 2011-12-30 00:28:05 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > You can use `emerge -1 @module-rebuild` (supported by Portage 2.2).
> 
> For stable portage, use `emerge -1 /lib/modules`.

This command only pulled virtualbox while I had also to recompile NetworkManager and upower also.

I do use stable portage so I can not tell if @module-rebuild will pull those...
Comment 5 Zac Medico gentoo-dev 2011-12-30 00:46:36 UTC
(In reply to comment #4)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > You can use `emerge -1 @module-rebuild` (supported by Portage 2.2).
> > 
> > For stable portage, use `emerge -1 /lib/modules`.
> 
> This command only pulled virtualbox while I had also to recompile
> NetworkManager and upower also.

Right, it's only a partial solution. The problem is that we have a special kind of dependency, similar to an ABI dependency, which needs to be expressed in the ebuild metadata (as discussed in bug 192319).

> I do use stable portage so I can not tell if @module-rebuild will pull those...

It will not, because it's equivalent to `emerge -1 /lib/modules`.