Re: [Flightgear-devel] Aircraft failing to install

[James T. <ja...@fl...>]

> On 15 Apr 2020, at 10:04, Richard Harrison <rj...@za...> wrote:
> 
> I'm also getting these errors after the bad checksum
> 
> file remove failed: (Path "I:/FlightGear/Aircraft/org.flightgear.fgaddon.stable_2018/Aircraft/f-14b/Previews/F-14_01.jpg") reason: Permission denied
> failed to remove:Path "I:/FlightGear/Aircraft/org.flightgear.fgaddon.stable_2018/Aircraft/f-14b/Previews/F-14_01.jpg"
> Dir at:Path "I:/FlightGear/Aircraft/org.flightgear.fgaddon.stable_2018/Aircraft/f-14b/Previews" failed to remove children
> failed to remove:Path "I:/FlightGear/Aircraft/org.flightgear.fgaddon.stable_2018/Aircraft/f-14b/Previews"
> Dir at:Path "I:/FlightGear/Aircraft/org.flightgear.fgaddon.stable_2018/Aircraft/f-14b" failed to remove children
> file remove failed: (Path "I:/FlightGear/Aircraft/org.flightgear.fgaddon.stable_2018/Aircraft/f-14b") reason: Permission denied
> failed to install package:f-14b:6
> void __cdecl LauncherController::onAircraftInstallFailed(class QModelIndex,class QString) QVariant(QUrl, QUrl("package:org.flightgear.fgaddon.stable_2018.f-14b")) "A local file-system error occurred"
> 
> The image file above is locked by FG:
> 
> I:\FlightGear\Aircraft\org.flightgear.fgaddon.stable_2018\Aircraft\f-14b\Previews>move F-14_01.jpg ..
> The process cannot access the file because it is being used by another process.
>         0 file(s) moved.
> 
> after exiting the launcher
> 
> I:\FlightGear\Aircraft\org.flightgear.fgaddon.stable_2018\Aircraft\f-14b\Previews>move F-14_01.jpg ..
>         1 file(s) moved.
> 

Oh, that’s bad, I will figure out where/how and fix.

> >Yes, it’s because Merspieler’s mirror is not syncing - so the zip file MD5  does not match what’s in the catalog XML.
> 
> I can't help thinking that really we should be able to auto discard any server that hasn't updated (MD5 of the catalog hash or MD5 of the zip files) - or allow the user to control what servers are used for aircraft updates - but regardless of the solution there needs to be a way for the user to recover from this error as it is fairly certain that at some point in the LTS lifespan any given mirror could be out of date.
> 

Right, the auto-discard behaviour was added on ‘next’ last week, I need to back-port it to 2018.3 branch.

Kind regards,
James