Bug 783788

Summary: cp: cannot stat `/usr/share/davfs2/davfs2.conf': No such file or directory
Product: [Fedora] Fedora Reporter: Tobias Mueller <fedora-bugs>
Component: davfs2Assignee: Will Woods <wwoods>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: nikt, projects.rg, reinouts, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 18:49:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tobias Mueller 2012-01-22 14:34:09 UTC
Description of problem:
enter davfs details in /etc/fstab and ~/.davfs2/secrets
mount the share as user
see it complaining:
 $ mount ~/empty/
cp: cannot stat `/usr/share/davfs2/davfs2.conf': No such file or directory
 $ 

I would have expected no complaints.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Met Merilius 2012-01-25 17:50:24 UTC
I confirm the behavior.
The warning occurs also when mounting from nautilus.

The davfs2.conf in Fedora is not located in /usr but in
/etc/davfs2/davfs2.conf

Comment 2 Reinout van Schouwen 2012-03-15 11:59:57 UTC
+1, I was just about to file the same bug.

Comment 3 Johann Bauer 2012-05-15 10:17:27 UTC
Hi,

I confirm the behaviour for davfs2 1.4.6-1.fc16.

The cause for the behaviour seems to be that mount.davfs tries to create davfs2.conf and secrets (with permission 600) in ~/.davfs2, if they do not exist (as described in the man mount.davfs). This seems to be done by copying the missing files there, i.e. /usr/share/davfs2/davfs2.conf and /usr/share/davfs2/secrets.

A work-around for this bug is to create the files in question manually, i.e. touch ~/.davfs2/davfs2.conf and ~/.davfs2/secrets and set permission 600.

Regards,
Johann

Comment 4 Will Woods 2012-06-02 18:36:07 UTC
*** Bug 770245 has been marked as a duplicate of this bug. ***

Comment 5 Will Woods 2012-06-02 18:38:21 UTC
This is probably a simple packaging error - I wasn't including the files in /usr/share/davfs2.

I should have updated packages available for testing soon.

Comment 6 Fedora End Of Life 2013-01-17 01:57:58 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Tobias Mueller 2013-01-17 21:04:50 UTC
Seems to be still an issue:

$ rpm -ql davfs2 | grep conf
/etc/davfs2/davfs2.conf
/usr/share/man/de/man5/davfs2.conf.5.gz
/usr/share/man/es/man5/davfs2.conf.5.gz
/usr/share/man/man5/davfs2.conf.5.gz

Comment 8 Fedora End Of Life 2013-07-04 07:06:01 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Reinout van Schouwen 2013-07-04 12:33:22 UTC
(In reply to Tobias Mueller from comment #7)
> Seems to be still an issue:
> 
> $ rpm -ql davfs2 | grep conf
> /etc/davfs2/davfs2.conf
> /usr/share/man/de/man5/davfs2.conf.5.gz
> /usr/share/man/es/man5/davfs2.conf.5.gz
> /usr/share/man/man5/davfs2.conf.5.gz

In my current F19 setup, there's a davfs2.conf both in /etc/davfs2 and /usr/share/davfs2.

Comment 10 Fedora End Of Life 2013-08-01 18:49:49 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.