Skip to content
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

Closed
seiry opened this issue Apr 2, 2024 · 4 comments · Fixed by #108
Closed
Assignees
Labels
bug Something isn't working

Comments

@seiry
Copy link

seiry commented Apr 2, 2024

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
image

And I unpacked the spk file AirConnect-dsm7-x86_64-1.8.3-20240327.spk in mac.

image image

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.

image image

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

  • package name: AirConnect-dsm7-x86_64-1.8.3-20240327.spk
@seiry seiry added the bug Something isn't working label Apr 2, 2024
@seiry seiry changed the title the bin file airupnp and aircast in AirConnect-dsm7-x86_64-1.8.3-20240327.spk is broken the bin file airupnp and aircast in AirConnect-dsm7-x86_64-1.8.3-20240327.spk are broken Apr 2, 2024
@eizedev
Copy link
Owner

eizedev commented Apr 2, 2024

Thanks @seiry, some other users also realized this. I need to find a few minutes to investigate the problem.
There may be two problems, one in the detection in the start-stop-status (src/dsm7/scripts subfolder) script and one in the binary itself, as you suspect.
Therefore i changed it to pre-release until i investigated it.(Only a "problem" due to time (Easter etc.))

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.

Trackback: #106 #79 #105

@eizedev eizedev pinned this issue Apr 2, 2024
@seiry
Copy link
Author

seiry commented Apr 2, 2024

oh hey @eizedev , I did some research and It's release-downloader broke the extract files.
downgrade it to robinraju/release-downloader@v1.8 would fix.
robinraju/release-downloader#689

And thank you for your cool work! lol

@eizedev
Copy link
Owner

eizedev commented Apr 2, 2024

Really cool find! Thanks @seiry
Would you like to open a pull request? Then i can merge it and you will be named as contributor. if not, i will just "install" the fix later on that day (robinraju/release-downloader@v1.8)

@seiry
Copy link
Author

seiry commented Apr 2, 2024

yeah, I've already opened one.
#108
Also, I enhanced the publish flow. Now when publish a tag, will trigger the build pipeline, and then add the spks to the release.
@eizedev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
2 participants