Bug 949906
Summary: | Colons in automatically created names by gvfs-fuse cause problems | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | fedora |
Component: | gvfs | Assignee: | Tomáš Bžatek <tbzatek> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | alexl, bnocera, tbzatek, tsmetana |
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-04-09 09:19:19 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
fedora
2013-04-09 09:13:29 UTC
This should be fixed in those applications instead, it's a nice demonstration how broken they are. Please file respective bugreports for all affected components. Sorry, but how can I address *all* applications that allow an URI? Every application that allows an URI with "server://path" in addition to a pure file name will fail! I don't think all those applications are broken, I think gvfs-fuse is broken because it breaks all those applications that existed before this new naming scheme! URI is a standard!!! See https://en.wikipedia.org/wiki/Uniform_resource_identifier. By the way it would fix very easily, for example by using an underscore or minus character instead of the colon. Sooner or later somebody else will face the same issue, fixing it in gvfs is pointless, this is a larger issue. Anybody can create a path like this, even use it for mountpoints having homedirs etc. Colons and commas are allowed file name/path characters in POSIX world. Applications should detect the first path separator (a slash) indicating local absolute path. Alternatively you may want to pass local file scheme prefix "file://" that the applications expecting valid URI would interpret just fine (and you may want to URI-encode some characters). Btw. not sure how g_file_new_for_commandline_arg () behaves, it's worth testing it. Not on gvfsd-fuse generated paths since it's transparently translated to original URI. (In reply to comment #3) > By the way it would fix very easily, for example by using an underscore or > minus character instead of the colon. Yes, it's a oneliner, but you made a good test case, need to fix the root cause, not a consequence. (In reply to comment #4) > Alternatively you may want to pass local file scheme > prefix "file://" that the applications expecting valid URI would interpret > just fine (and you may want to URI-encode some characters). Good idea. git seems to run then. Nonetheless why make it unnecessary difficult when changing a single character ':' -> '_' could make life so much simpler? In 99% there would be no need for the prefix "file://". I would say many people have stumbled or will stumble over this. Why provoke problems that needn't be there in the first place? Sometimes it is not wise to do something just because you *can* do it. It is never wise to use ':' in a file name even if you are allowed to. |