Bug 15336

Summary:	Add redirects to prevent warnings on bind updates
Product:	Mageia	Reporter:	claire robinson <eeeemail>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	Normal
Version:	4
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description claire robinson 2015-02-21 18:37:18 CET

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



Reproducible: 

Steps to Reproduce:

Comment 1 David Walser 2015-02-21 18:53:58 CET

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.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 2 claire robinson 2015-02-22 18:39:22 CET

Bug is not invalid and like I said, we *do not* expect unwarranted warning messages when updating packages.

Status: RESOLVED => REOPENED
Resolution: INVALID => (none)

Comment 3 Samuel Verschelde 2015-09-21 13:21:57 CEST

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 
fix updates.

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 
Mageia version.

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 [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Comment 4 claire robinson 2015-09-21 14:40:33 CEST

Closing wontfix.

Status: REOPENED => RESOLVED
Resolution: (none) => WONTFIX