Bug 321 - dkms build error during urpmi --auto-update
Summary: dkms build error during urpmi --auto-update
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: http://pastebin.com/T2TNyuV6
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-09 23:24 CET by AL13N
Modified: 2011-07-15 22:55 CEST (History)
0 users

See Also:
Source RPM: dkms-vboxadditions
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description AL13N 2011-03-09 23:24:01 CET 
Description of problem:

from error log (in url):

Error! Your kernel source for kernel 2.6.37.2-desktop-1.mga cannot be found at /lib/modules/2.6.37.2-desktop-1.mga/build or /lib/modules/2.6.37.2-desktop-1.mga/source.


kernel-desktop-latest and kernel-deskop-2.6.37.3-1.mga is being pulled in to update, but kernel-devel or kernel-devel-latest isn't?

and 

dkms-vboxadditions is upgraded before kernel? seems odd...

Reproducible: 

Steps to Reproduce:
Comment 1 AL13N 2011-03-09 23:28:34 CET 
also very odd:

You should restart your computer for kernel-desktop-2.6.37.3-1.mga
writing /var/lib/rpm/installed-through-deps.list

The following packages:
  ed-1.5-1.mga1.x86_64
  ghostscript-dvipdf-9.00-4.mga1.x86_64
  jpeg-progs-8b-5.mga1.x86_64
  kernel-desktop-2.6.37-3.mga-1-1.mga1.x86_64
  kernel-desktop-devel-2.6.37-3.mga-1-1.mga1.x86_64
  lib64netpbm10-10.47.21-2.mga1.x86_64
  lib64rpm4.6-4.6.1-10.mga1.x86_64
  netpbm-10.47.21-2.mga1.x86_64
  plasma-desktoptheme-aya-4.6.1-1.mga1.noarch
  sam2p-0.44.14-5.mga1.x86_64
are now orphaned, if you wish to remove them, you can use "urpme --auto-orphans"


it looks to me that there is a problem with "-1-1.mga1" maybe?

also, why would kernel-desktop-devel be installed, but not kernel-desktop in that same version?
Comment 2 Manuel Hiebel 2011-07-14 21:07:32 CEST 
issue still present ?

ps; you should use kernel-desktop-latest and kernel-desktop-devel-latest
Comment 3 AL13N 2011-07-15 22:55:31 CEST 
i think this was during an upgrade during beta stages, but i'm afraid i hadn't described my problem accurately, in any case, i can't remember what i did to trigger, so i'm closing now...

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME
Note You need to log in before you can comment on or make changes to this bug.