Description of problem: The installation of virtualbox 6.1.26 triggers the installation of kernel 5.13 under mageia 8 when using rpmdrake. The problem does not occur when installing via urpmi. The strange thing is that I don't see how rpmdrake is able to download the 5.13 kernel given the active repositories. [root@solar ~]# urpmq --list-media active --list-url Core Release (distrib1) http://ftp.free.fr/mirrors/mageia.org/distrib/8/x86_64/media/core/release Core Updates (distrib3) http://ftp.free.fr/mirrors/mageia.org/distrib/8/x86_64/media/core/updates Nonfree Release (distrib11) http://ftp.free.fr/mirrors/mageia.org/distrib/8/x86_64/media/nonfree/release Nonfree Updates (distrib13) http://ftp.free.fr/mirrors/mageia.org/distrib/8/x86_64/media/nonfree/updates Tainted Release (distrib21) http://ftp.free.fr/mirrors/mageia.org/distrib/8/x86_64/media/tainted/release Tainted Updates (distrib23) http://ftp.free.fr/mirrors/mageia.org/distrib/8/x86_64/media/tainted/updates Core 32bit Release (distrib31) http://ftp.free.fr/mirrors/mageia.org/distrib/8/i586/media/core/release Core 32bit Updates (distrib32) http://ftp.free.fr/mirrors/mageia.org/distrib/8/i586/media/core/updates Nonfree 32bit Release (distrib36) http://ftp.free.fr/mirrors/mageia.org/distrib/8/i586/media/nonfree/release Nonfree 32bit Updates (distrib37) http://ftp.free.fr/mirrors/mageia.org/distrib/8/i586/media/nonfree/updates Tainted 32bit Release (distrib41) http://ftp.free.fr/mirrors/mageia.org/distrib/8/i586/media/tainted/release Tainted 32bit Updates (distrib42) http://ftp.free.fr/mirrors/mageia.org/distrib/8/i586/media/tainted/updates Version-Release number of selected component (if applicable): How reproducible: We are at least 2 to reproduce the problem. Steps to Reproduce: 1. Launch rpmdrake et install virtualbox 6.1.26 for 64 bits 2. 3.
Created attachment 12908 [details] Capture of problem in rpmdrake
Thank you for the report, and apologies for the angst. This is a duplicate of bugs 29169/29148, which indicate that rpmdrake is using Backports even when that is not active, and pulling in kernel from there. > The problem does not occur when installing via urpmi This is important to note, since users can easily avoid the issue. *** This bug has been marked as a duplicate of bug 29148 ***
Resolution: (none) => DUPLICATEStatus: NEW => RESOLVED