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 libkf5kiocore5 5.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 libkf5service5 5.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 libqt5gui5 5.12.0+dfsg-0+xneon+18.04+bionic+build53
ii libqt5widgets5 5.12.0+dfsg-0+xneon+18.04+bionic+build53
ii libstdc++6 8.2.0-1ubuntu2~18.04
plasma-browser-integration recommends no packages.
plasma-browser-integration suggests no packages.
-- no debconf information
Reply to: