See bug 15326
Undesirable warnings when updating bind if the service is already running. Could be prevented with redirects to quash mv output.
2/4: bind ########
mv: â/var/lib/named/var/named/dataâ and â/var/named/dataâ are the same file
mv: â/var/lib/named/var/named/dynamicâ and â/var/named/dynamicâ are the same file
mv: â/var/lib/named/var/named/named.caâ and â/var/named/named.caâ are the same file
mv: â/var/lib/named/var/named/named.emptyâ and â/var/named/named.emptyâ are the same file
mv: â/var/lib/named/var/named/named.localhostâ and â/var/named/named.localhostâ are the same file
mv: â/var/lib/named/var/named/named.loopbackâ and â/var/named/named.loopbackâ are the same file
mv: â/var/lib/named/var/named/slavesâ and â/var/named/slavesâ are the same file
Steps to Reproduce:
Like I said, the bind mounting makes this more complicated than you realize, and you do *not* want to always silence error output from these commands.
Bug is not invalid and like I said, we *do not* expect unwarranted warning messages when updating packages.
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer
maintained, which means that it will not receive any further security or bug
Package Maintainer: If you wish for this bug to remain open because you plan to
fix it in a currently maintained version, simply change the 'version' to a later
Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't
able to fix it before Mageia 4's end of life. If you are able to reproduce it
against a later version of Mageia, you are encouraged to click on "Version" and
change it against that version of Mageia. If it's valid in several versions,
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
Although we aim to fix as many bugs as possible during every release's lifetime,
sometimes those efforts are overtaken by events. Often a more recent Mageia
release includes newer upstream software that fixes bugs or makes them obsolete.
If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program  or join the teams that fit you