-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
the bin file airupnp
and aircast
in AirConnect-dsm7-x86_64-1.8.3-20240327.spk
are broken
#107
Comments
airupnp
and aircast
in AirConnect-dsm7-x86_64-1.8.3-20240327.spk
is brokenairupnp
and aircast
in AirConnect-dsm7-x86_64-1.8.3-20240327.spk
are broken
Thanks @seiry, some other users also realized this. I need to find a few minutes to investigate the problem. Also, the GitHub action is not completely finished, I would like to publish releases automatically and add some more validation. That's why I'm currently only making it available for me in the artifacts (and not publishing the packages automatically) until I'm finished with it. |
oh hey @eizedev , I did some research and It's release-downloader broke the extract files. And thank you for your cool work! lol |
Really cool find! Thanks @seiry |
Describe the bug
I downloaded the spk from the pre-release, and it won's start after I installed. And with no log.
https://github.com/eizedev/AirConnect-Synology/releases/tag/1.8.3-20240327
I checked the bin file in the dsm, which showed it was not a valid ELF
And I unpacked the spk file
AirConnect-dsm7-x86_64-1.8.3-20240327.spk
in mac.both of the 2 files are not valid ELF bins.
other context
to compare, the bin file in https://github.com/eizedev/AirConnect-Synology/releases/tag/1.7.0-20240115 and #106 (comment) is good.
And I checked the artifacts in https://github.com/eizedev/AirConnect-Synology/actions/runs/8448579672 , I think there may be something wrong in the action pipeline.
Package
https://github.com/eizedev/AirConnect-Synology/releases/tag/1.8.3-20240327
AirConnect-dsm7-x86_64-1.8.3-20240327.spk
The text was updated successfully, but these errors were encountered: