Bug#923322: plasma-browser-integration: Incorrect installation directory for chrome config file
maxy gave an ok for a MR but I am unclear exactly what needs to be done. I don't like the sound of tricky! @mitya57 can you prepare this or point me to an example? Thanks, Scarlett -- Scarlett Gately Moore ( Formerly Clark ) Software engineer @ Blue Systems KDE Developer/Sysadmin Debian Contributor / Developer in training. IRC sgmoore signature.asc Description: This is a digitally signed message part.
Bug#923322: plasma-browser-integration: Incorrect installation directory for chrome config file
Hi David and all, On Tue, Feb 26, 2019 at 12:50:43PM +, David Edmundson wrote: > Plasma browser integration needs to install a file to /etc/opt > > Upstream does this. > > There was a concious decision in debian packaging to do something else, > but the move to break it cites a rule about installing into /opt > This does not apply as it refers to a completely different directory. > Note the /etc prefix. It was brought to my attention that the Plasma Integration extension for Chrome [1] has this note in its description: NOTE: This extension is not supported on Debian. As far as I understand, this extension works fine with Chromium from our repository, but does not work (out of the box) with Google Chrome when it is installed from Google's repository. On one hand, Debian's packages are not obliged to be compatible with third-party packages. On the other hand, people who use Google's builds may blame Debian if things are not working for them. > A solution has been found for chrome-gnome-shell using postinst/postrm > to copy the file into the correct location. > > Can we have the same system used here please. That system is a bit more complex than it sounds, as the postrm script actually needs to *recreate* /etc/opt directory after dpkg deletes it. See the bug [2] for details. The good news is that chrome-gnome-shell maintainers have already done the hard work, so we can just copy their logic (with the json file name changed, obviously) if we decide to go that way. Maxy, Scarlett, what do you think about this? I do not think we should fix this for Buster, as the fix would be quite tricky and if I were the release team I would not like it :) Also, users who are affected may follow the instruction that we ship in /usr/share/doc/plasma-browser-integration/README.Debian [1] and add the symlink manually. I wonder if maybe the extension description can mention that instruction (instead of just saying Debian is not supported)? [1]: https://chrome.google.com/webstore/detail/plasma-integration/cimiefiiaegbelhefglklhhakcgmhkai [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888549 [3]: https://salsa.debian.org/qt-kde-team/kde/plasma-browser-integration/blob/master/debian/README.Debian -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#923322: plasma-browser-integration: Incorrect installation directory for chrome config file
Package: plasma-browser-integration Version: 5.14.5+p18.04+git20190129.0259-0 Severity: important Dear Maintainer, Plasma browser integration needs to install a file to /etc/opt Upstream does this. There was a concious decision in debian packaging to do something else, but the move to break it cites a rule about installing into /opt This does not apply as it refers to a completely different directory. Note the /etc prefix. A solution has been found for chrome-gnome-shell using postinst/postrm to copy the file into the correct location. Can we have the same system used here please. -- System Information: Debian Release: buster/sid APT prefers bionic-updates APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 'bionic') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-45-generic (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-browser-integration depends on: ii libc6 2.27-3ubuntu1 ii libkf5activities5 5.54.0+p18.04+git20190203.0346-0 ii libkf5configcore5 5.54.0+p18.04+git20190205.0126-0 ii libkf5coreaddons5 5.54.0+p18.04+git20190203.0215-0 ii libkf5dbusaddons5 5.54.0+p18.04+git20190203.0212-0 ii libkf5i18n5 5.54.0+p18.04+git20190203.0213-0 ii libkf5kiocore55.54.1+p18.04+git20190204.1405-0 ii libkf5kiowidgets5 5.54.1+p18.04+git20190204.1405-0 ii libkf5notifications5 5.54.0+p18.04+git20190203.0231-0 ii libkf5runner5 5.54.0+p18.04+git20190203.0407-0 ii libkf5service55.54.0+p18.04+git20190203.0237-0 ii libqt5core5a 5.12.0+dfsg-0+xneon+18.04+bionic+build53 ii libqt5dbus5 5.12.0+dfsg-0+xneon+18.04+bionic+build53 ii libqt5gui55.12.0+dfsg-0+xneon+18.04+bionic+build53 ii libqt5widgets55.12.0+dfsg-0+xneon+18.04+bionic+build53 ii libstdc++68.2.0-1ubuntu2~18.04 plasma-browser-integration recommends no packages. plasma-browser-integration suggests no packages. -- no debconf information
