Hi,
Am 12.05.2018 um 17:40 schrieb Markus Koschany: > Hello Patrick, > > Am 12.05.2018 um 16:19 schrieb James Cowgill: > [...] >> I think this is a bug in libphysfs 3.0.1. It seems that in this version >> (unlike 2.0.3), PHYSFS_setWriteDir has the side effect of creating an >> empty file if the path it is given does not exist. This will later cause >> PHYSFS_mkdir to fail even if it's given the right path. >> >> This would also explain why this bug is not present in stretch. > A bug was reported against lincity-ng but it looks more like this is a > regression/bug in libphysfs 3.0.1. The setWriteDir function creates an > empty file which makes the mkdir function fail later on. Shall I > reassign this bug report to libphysfs? > > Regards, > > Markus Maybe upstream can say something about it? :) =>: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898483 -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
signature.asc
Description: OpenPGP digital signature
