* ERROR: media-plugins/vdr-autosort-0.1.3::gentoo failed (preinst phase): * fowners failed * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-gnome_libressl_20180820-193302 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-8.2.0 * Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python2.7 (fallback) [4] jython2.7 (fallback) Available Ruby profiles: [1] ruby23 (with Rubygems) [2] ruby25 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.8.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv media-plugins/vdr-autosort [ebuild N ] media-plugins/vdr-autosort-0.1.3
Created attachment 545122 [details] emerge-info.txt
Created attachment 545124 [details] emerge-history.txt
Created attachment 545126 [details] environment
Created attachment 545128 [details] etc.portage.tbz2
Created attachment 545130 [details] logs.tbz2
Created attachment 545132 [details] media-plugins:vdr-autosort-0.1.3:20180826-150116.log
cp: cannot stat 'etc/vdr/channels.conf': No such file or directory chown: cannot access '/var/tmp/portage/media-plugins/vdr-autosort-0.1.3/image/etc/vdr/channels.conf.autosort.bak': No such file or directory for me, it looks like, tinderbox failed in this case, as tinderbox has not a configured/running vdr setup on first start of vdr, it will created an emtpty channels.conf so the plugin will copy, move or install all files without any problems
(In reply to Joerg Bornkessel from comment #7) But if a user does not install and run vdr first and later installs the plugin - it will fail, or?
hmm, i will think about this, maybe this plugin is finaly another candidat for removal iam on the way to remove all the old crap from the tree...
pmasked for removal on bug 665136