Mat
The double backslashes are not a problem, it's just the way they happen to be represented in the error message: https://stackoverflow.com/questions/11924706/how-to-get-rid-of-double-backslash-in-python-windows-file-path-string/11924842 > or overall filepath\name too long It's most likely...
> @mathiascode is working on bypass functionality To clarify, I was talking about bypassing the 260 character limit on Windows (which should be possible). The scanner should already recover after...
I can confirm that paths longer than 260 characters currently trigger the "The system cannot find the path specified" error.
@jpdillingham I see you removed the warning. How did you end up handling the issue?
CC @kiplingw @pabs3
> Debian devs have updated the open bug about this at link: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990852 > > On there, Kip Warner [[email protected]](mailto:[email protected]) (Senior Software Engineer) seems very interested to package a...
> either have to run version 1.2.16 from their oldoldstable repo (which has stopped working now) Which is a shame, since these old Nicotine+ versions contain a lot of bugs...
> I ended up with over 1.5Gb of runtimes including 'org.freedesktop.Platform.GL.default/x86_64/20.08' which seems excessive just for running one single application. For some reason my Flatpak apps do not respect my...
> Whilst the some underground nature of the project is somewhat endearing, it is a pain to come accross old versions left by the previous developers everywhere, and this damages...
Let us know if there's anything we can improve in our own Debian packaging (best practices etc) as the package inclusion process continues. Ideally our packaging would be as close...