Hi. I have this problem since the begin of Mageia development. My wireless card need iwlwifi-agn-ucode to work, but this module is always orphaned when I do a kernel update. If I remove the orphans, I need to connect my computer in cable internet to intall iwlwifi-agn-ucode again. Is it possible stop the iwlwifi-agn-ucode orphanization? (I did put iwlwifi-agn-ucode for not orphaned again, my question is to Mageia current default behaviour change for not orphaned iwlwifi-agn-ucode) Reproducible: Steps to Reproduce:
Running "urpmi iwlwifi-agn-ucode", after it's already installed, will mark it as a manually installed package, that will not be auto-orphaned, in the future. I'm not sure what should be done to ensure other's don't run into the same problem. Anyone using urpme --auto-orphans, is expected to know, how to prevent an orphaned package from being removed, but this bug report makes it clear, that is not the case.
CC: (none) => davidwhodgins
Hm, Thierry... I added this a couple of weeks ago: http://gitweb.mageia.org/software/drakx/commit/?id=26b5fcd0b10715f1d0d085a1f9db5907a10185f2 Do I need to update some other code too?
CC: (none) => tmbAssignee: bugsquad => thierry.vignaud
(In reply to Dave Hodgins from comment #1) > Running "urpmi iwlwifi-agn-ucode", after it's already installed, > will mark it as a manually installed package, that will not be > auto-orphaned, in the future. Sure, it is correct. But if I update the kernel, I will need run "urpmi iwlwifi-agn-ucode" again. My question is, is it possible prevent the iwlwifi-agn-ucode orphanization for the kernel update case? > I'm not sure what should be done to ensure other's don't > run into the same problem. Anyone using urpme --auto-orphans, > is expected to know, how to prevent an orphaned package > from being removed, but this bug report makes it clear, that > is not the case. For my case, I configured iwlwifi-agn-ucode for don't be orphaned again. My worry is just for users with little technical expertise in this area. Thanks;
Is this problem still present Filipe? Thierry, there was a question from tmb in comment #2.
Keywords: (none) => NEEDINFO
The commit referenced in comment 2 fixed the issoe
Status: NEW => RESOLVEDResolution: (none) => FIXED