[Bug 1935063] Re: gnome-initial-setup: cannot build on RISC-V

2022-03-24 Thread Sebastien Bacher
That's fixed now, https://bugs.launchpad.net/ubuntu/+source/gnome- initial-setup/42~beta-1ubuntu1/+build/23176125 ** Changed in: gnome-initial-setup (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1935063] Re: gnome-initial-setup: cannot build on RISC-V

2021-09-10 Thread Heinrich Schuchardt
golang-1.16 (1.16.7-1ubuntu2) allows building dynamic link libraries (*.so) needed by ubuntu-report. https://github.com/ubuntu/ubuntu-report/pull/38 addresses remaining build problems on RISC-V. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1935063] Re: gnome-initial-setup: cannot build on RISC-V

2021-07-15 Thread Sebastien Bacher
We would accept a patch that disable the ubuntu report integration on riscv ** Changed in: gnome-initial-setup (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-initial-setup (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of

[Bug 1935063] Re: gnome-initial-setup: cannot build on RISC-V

2021-07-13 Thread Heinrich Schuchardt
** Tags added: riscv64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935063 Title: gnome-initial-setup: cannot build on RISC-V To manage notifications about this bug go to:

[Bug 1935063] Re: gnome-initial-setup: cannot build on RISC-V

2021-07-09 Thread Didier Roche
The report is one of the main ubuntu feature for us to our KPI and can’t be removed completely. I suggest disabling it for RISC-V for the time- being would be the most acceptable solution IMHO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1935063] Re: gnome-initial-setup: cannot build on RISC-V

2021-07-08 Thread William Wilson
I submitted https://github.com/golang/go/issues/47100 which doesn't immediately help us but is the best long term solution. ** Bug watch added: github.com/golang/go/issues #47100 https://github.com/golang/go/issues/47100 -- You received this bug notification because you are a member of