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

Publish Linux ARM deb & rpm repositories #106473

Closed
7 of 10 tasks
joaomoreno opened this issue Sep 11, 2020 · 9 comments
Closed
7 of 10 tasks

Publish Linux ARM deb & rpm repositories #106473

joaomoreno opened this issue Sep 11, 2020 · 9 comments
Assignees
Labels
engineering VS Code - Build / issue tracking / etc. help wanted Issues identified as good community contribution opportunities linux Issues with VS Code on Linux
Milestone

Comments

@joaomoreno
Copy link
Member

joaomoreno commented Sep 11, 2020

  • Deb
    • Create working deb packages
    • Publish to MS repos
    • Migrate x64 repo over the new one
  • RPM
    • Create working rpm packages - Thanks, @psgreco
    • Publish to MS repos
  • Snap 🔴
    • Create working snap packages probably need ARM machines to build these
    • Publish to snap store
@joaomoreno joaomoreno added the engineering VS Code - Build / issue tracking / etc. label Sep 11, 2020
@joaomoreno joaomoreno added this to the September 2020 milestone Sep 11, 2020
@joaomoreno joaomoreno self-assigned this Sep 11, 2020
@m-roberts
Copy link

+1 for this!

@gizmotronic
Copy link

Any chance of publishing as a snap, as well?

@joaomoreno joaomoreno changed the title Publish Linux ARM deb and rpm to repositories Publish Linux ARM deb, rpm and snap to repositories Oct 9, 2020
@joaomoreno joaomoreno added the feature-request Request for new features or functionality label Oct 13, 2020
@0x011011110
Copy link

This would definitely be nice - something I noticed is that the debs currently install a vscode.list in /etc/apt/sources.list.d/ but it is limited to [arch=amd64] so it would be nice to have a sources.list that is correct

@joaomoreno
Copy link
Member Author

@0x011011110 Yeah that's the biggest problem right now, we're looking into a good option right now.

@joaomoreno
Copy link
Member Author

Snap packages are now created but they simply segfault:

joao@joao-ubuntu-rpi:~/Downloads$ gdb /snap/code-insiders/current/usr/share/code-insiders/code-insiders 
GNU gdb (Ubuntu 9.2-0ubuntu2) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /snap/code-insiders/current/usr/share/code-insiders/code-insiders...
(No debugging symbols found in /snap/code-insiders/current/usr/share/code-insiders/code-insiders)
(gdb) r
Starting program: /snap/code-insiders/x1/usr/share/code-insiders/code-insiders 

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000008 in ?? ()
joao@joao-ubuntu-rpi:~/Downloads$ uname -a
Linux joao-ubuntu-rpi 5.8.0-1007-raspi #10-Ubuntu SMP PREEMPT Thu Nov 5 17:52:40 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux
joao@joao-ubuntu-rpi:~/Downloads$ file /snap/code-insiders/current/usr/share/code-insiders/code-insiders 
/snap/code-insiders/current/usr/share/code-insiders/code-insiders: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /snap/core/current/lib/ld-linux-aarch64.so.1, BuildID[sha1]=644557efd63781717386f34776877ca4e9fd0104, for GNU/Linux 3.7.0, stripped

@joaomoreno
Copy link
Member Author

@flexiondotorg: As tweeted in https://twitter.com/joaomoreno/status/1329704593366847488:

Hitting some issues. I thought that using build-on: amd64 and run-on: arm64 would get us there: https://github.com/microsoft/vscode/pull/111008/files#diff-74c4ea7e8a7229121137b67faf75b6808d948fbbd120adb7b0f763a52b975dedR9-R12 But the resulting snap still has an amd64 base system, so code segfaults.

Aside from snapcraft remote-build it seems we can only get ARM snaps if we run it on ARM hardware, did I get that right?


Because of this snap ARM are currently blocked.

@joaomoreno joaomoreno added info-needed Issue requires more information from poster help wanted Issues identified as good community contribution opportunities and removed info-needed Issue requires more information from poster labels Nov 23, 2020
@joaomoreno
Copy link
Member Author

joaomoreno commented Nov 23, 2020

We also need some help figuring out how to list RPM dependencies for ARM, since the current approach doesn't seem to work, when testing on CentOS 7 for Raspberry Pi 4 aarch64. The RPM package fails to install due to missing dependencies. So if there are some RPM fans in the community out there, any help is appreciated.

@joaomoreno
Copy link
Member Author

Thanks to @psgreco, we now have working ARM RPM packages 🎆

Screenshot from 2020-11-25 11-09-00

@bpasero
Copy link
Member

bpasero commented Jan 11, 2021

@joaomoreno let me know if you need any help

@joaomoreno joaomoreno changed the title Publish Linux ARM deb, rpm and snap to repositories Publish Linux ARM deb & rpm repositories Jan 18, 2021
@joaomoreno joaomoreno removed the feature-request Request for new features or functionality label Jan 25, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Mar 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
engineering VS Code - Build / issue tracking / etc. help wanted Issues identified as good community contribution opportunities linux Issues with VS Code on Linux
Projects
None yet
Development

No branches or pull requests

5 participants