Hi! On Sat, 2018-01-27 at 00:14:21 +0100, Holger Levsen wrote: > Package: base,chrome-gnome-shell > Severity: important
> from #debian-edu and #-release just now: > > <h01ger> > https://piuparts.debian.org/sid/fail/education-desktop-gnome_2.10.14.log > fails with > <h01ger> 17m25.6s ERROR: FAIL: After purging files have disappeared: > <h01ger> /etc/opt/ owned by: chrome-gnome-shell > <h01ger> hmm. thats not coming from src:debian-edu > <h01ger> yeah, > https://piuparts.debian.org/sid/fail/chrome-gnome-shell_9-2.log is to blame > <jbicha> h01ger: I don't think it's chrome-gnome-shell's fault > <jbicha> FAIL: After purging files have disappeared: /etc/opt/ owned by: > chrome-gnome-shell > <jbicha> that directory is created by base-files but chrome-gnome-shell is > the first Debian package to include something there > <jbicha> I don't know enough about this situation to know how to fix the issue > <h01ger> we should probably file a bug against base,chrome-gnome-shell > <jbicha> chrome-gnome-shell uses that directory because that's where the > official Google Chrome looks for overrides > <jbicha> maybe dpkg? I don't know > <jbicha> I'm fine with you filing a chrome-gnome-shell bug. I'm guessing that > the ultimate fix will be somewhere else > > Filing this with severity important as this introduces a piuparts > regression which becomes a britney migration blocker. The problem is that base-files does not own those pathnames (in the dpkg sense), it just creates them from its postinst, so when chrome-gnome-shell gets installed, from dpkg's PoV, it's the only one owning them, and on purge they get removed on last reference. Thanks, Guillem
