Upgrading alsa-utils from 1.0.19-r2 to 1.0.20-r4. It doesn't resolve an obsolete config file normally. Obsolete config at /etc/modules.d/alsa which it wants to move to /etc/modprobe.d/alsa.conf Reproducible: Always Steps to Reproduce: 1. have previous version of alsa-utils 2. emerge --sync 3. emerge -av1 alsa-utils OR emerge -uaDNv world Actual Results: These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] media-sound/alsa-utils-1.0.20-r4 [1.0.19-r2] USE="nls -doc -minimal" 0 kB Total: 1 package (1 upgrade), Size of downloads: 0 kB Would you like to merge these packages? [Yes/No] >>> Verifying ebuild manifests >>> Emerging (1 of 1) media-sound/alsa-utils-1.0.20-r4 * alsa-utils-1.0.20.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * Obsolete config /etc/modules.d/alsa found. * * ERROR: media-sound/alsa-utils-1.0.20-r4 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * alsa-utils-1.0.20-r4.ebuild, line 34: Called die * The specific snippet of code: * die "Move /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf." * The die message: * Move /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf. * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/media-sound/alsa-utils-1.0.20-r4/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-sound/alsa-utils-1.0.20-r4/temp/die.env'. * Expected Results: successful upgrade
This is intentional. portage won't move/rename config files for you. You have to do it yourself. To ensure that you do it, this error gets triggered. No bug but a feature.
