Offline packages with / in the ID is translated to Windows-1252 encoding

We are using Offline packages drops for deployment in Octopus deploy, we get our packages from github
where the package ID will be lik CompanyName/PackageName.

When we doploy a release and get the offline packages, the package ID is translated to Windows-1252 encoding in the powershell scripts and in the zip file names created.

This behavior causes powershell script failing when trigger them on target machines.

Hi @mohammed.farwana,

Thanks for getting in touch!

I’ve run a quick test on this and believe I’m seeing the same problem.
I’m receiving a Unexpected file format error when the script runs, does that match what you’re experiencing?


yes, that is exactly what I get.


1 Like

Perfect, thanks for confirming that.

I’ve submitted an issue for this here; Package steps for Offline targets convert '/' characters to Windows-1252 encoding · Issue #7220 · OctopusDeploy/Issues · GitHub

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.