Vscodium: Release 1.35.0 is missing AppImage

[JayAndCatchFire]

The latest release, while tagged, is missing binaries.

[stripedpajamas]

Looks like a transient problem during build. I've restarted the builds.

[stripedpajamas]

MS has moved from Node 8 to Node 10. Updating our build scripts 3f1e9ec9b4d8a7aed577ba835a5014de1d028c49

[antoniofagardo]

It seems like the darwin binaries are still missing, is it also part of the pipeline ?

[stripedpajamas]

The Mac install is having a different issue. I'm troubleshooting it -- you can have a look at the build logs here to see: https://travis-ci.com/VSCodium/vscodium/jobs/206168238

[tyu1996]

The AppImage binary is also missing in v1.35. Is there any issue found during the AppImage building process?

[eladcandroid]

brew cask upgrade vscodium
didn't upgrade to v1.35..

[stripedpajamas]

Brew cask downloads the Mac binary which does not exist yet. We are working on it.

[stripedpajamas]

Mac build has since succeeded, I will update the cask.

AppImage failed for an unknown reason, I will investigate.

[antoniofagardo]

brew cask upgrade vscodium worked !

Thank you for your help

[JayAndCatchFire]

It looks like the AppImage version is still missing from the binaries for 1.35.0. This doesn't affect me personally as I needed a deb file for arm64. Should I close this issue or leave it open for the AppImage version?

[ghost]

I'm on Kubuntu 19.04, sudo dpkg -i codium_1.35.0-1560135863_amd64.deb

(Reading database ... 223914 files and directories currently installed.)
Preparing to unpack codium_1.35.0-1560135863_amd64.deb ...
Unpacking codium (1.35.0-1560135863) ...
dpkg: error processing archive codium_1.35.0-1560135863_amd64.deb (--install):
trying to overwrite '/usr/share/pixmaps/com.visualstudio.code.oss.png', which is also in package vscodium 1.34.0-1558029460
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
codium_1.35.0-1560135863_amd64.deb

[JayAndCatchFire]

@ntilotta that happened to me as well. This is because the package name changed from vscodium to codium in this release (#176, #187). The solution is to uninstall the old version before installing the new version.

[stripedpajamas]

@JayAndCatchFire let's leave this open to track the missing AppImage.

[tyu1996]

Is it related to recent changing name from vscodium to codium? What if rename all the 'vscodium' to 'codium' in VSCodium-AppImage-Recipe.yml?

[stripedpajamas]

It is related to the name change, but I'm not sure which places should be changed to codium.

@probonopd can you help?

[probonopd]

This line needs to be changed for sure:

https://github.com/VSCodium/vscodium/blob/81ef7c6d8f1e835f8fd3e97447c611555d07b590/VSCodium-AppImage-Recipe.yml#L20

I don't know about these lines, they need to be changed in case the filenames have changed from vscodium to codium:

https://github.com/VSCodium/vscodium/blob/81ef7c6d8f1e835f8fd3e97447c611555d07b590/VSCodium-AppImage-Recipe.yml#L23-L35

[tyu1996]

As Job #599.1 in Travis build log, line 4526 showed the following error message:

sed: can't read usr/share/applications/vscodium.desktop: No such file or directory

It apparently is related to name changes that the recipe can't proceed to created AppImage.

I did an edit on the recipe file and pull a request. If it works on Travis build, this issue can be marked as solved and closed.

[stripedpajamas]

Fixed by @tyu1996 in #203 -- AppImage should return on next release.