Comment 3 for bug 2015778

Just ran into this on a test upgrade of the raspi desktop image. The card was originally flashed with kinetic and I noted /etc/gprofng.rc was *not* present initially (@zhsj is correct this doesn't *ship* with kinetic), but appeared after the initial upgrade required before do-release-upgrade (in other words /etc/gprofng.rc is introduced by the version of binutils-common in kinetic-updates).

The /etc/gprofng.rc file was unmodified before proceeding to do-release-upgrade, yet I was prompted to merge changes during the upgrade (which was otherwise uneventful), despite there being no local changes to the file, and the only diff being that shown in the description above (a change in the copyright notice in the header).

Some issue in the configuration merge mechanism, perhaps? Or maybe something iffy being done to the config file in the binutils-common maintscripts (if any)?