Bug 1463967 - chrome-remote-desktop creates a conflicting directory symlink
Summary: chrome-remote-desktop creates a conflicting directory symlink
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-22 07:30 UTC by Pete Walter
Modified: 2017-07-18 06:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-17 21:05:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pete Walter 2017-06-22 07:30:13 UTC
I am working on a new package, chrome-gnome-shell. It uses the native messaging hosts interface and installs files in /etc/opt/chrome/native-messaging-hosts/ directory. When chrome-remote-desktop is installed we get a file conflict as chrome-remote-desktop has replaced the directory with a symlink. This is caused by the following lines in chromium.spec:

pushd %{buildroot}%{_sysconfdir}/opt/chrome/
ln -s ../../chromium/native-messaging-hosts native-messaging-hosts
popd

Please remove this so that other programs can also use the directory. Thanks.


$ sudo dnf install chrome-remote-desktop-56.0.2924.87-3.fc25.x86_64 
...
Error: Transaction check error:
  file /etc/opt/chrome/native-messaging-hosts from install of chrome-remote-desktop-56.0.2924.87-3.fc25.x86_64 conflicts with file from package chrome-gnome-shell-8.2-1.fc25.noarch

Comment 1 Tom "spot" Callaway 2017-06-22 17:19:41 UTC
Easy enough. I'll change it to be a dir rather than a symlink. You might also consider ensuring that your files are visible from both paths:

/etc/opt/chrome/native-messaging-hosts
/etc/chromium/native-messaging-hosts

That should ensure that your code works with both Google Chrome and Chromium (as packaged in Fedora).

Comment 2 Tom "spot" Callaway 2017-07-17 21:05:42 UTC
This should be fixed now in rawhide.

Comment 3 Pete Walter 2017-07-18 06:47:32 UTC
Thanks!


Note You need to log in before you can comment on or make changes to this bug.