Bug 51534 - flatpak: No such branch 'app/com.xamarin.MonoDevelop/i386/stable' in repository summary
Summary: flatpak: No such branch 'app/com.xamarin.MonoDevelop/i386/stable' in reposito...
Status: REOPENED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Linux Packaging (show other bugs)
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: Future Cycle (TBD)
Assignee: Jo Shields
URL:
Depends on:
Blocks:
 
Reported: 2017-01-14 06:02 UTC by duval.guerby
Modified: 2017-08-21 20:57 UTC (History)
5 users (show)

See Also:
Tags:
Is this bug a regression?: ---
Last known good build:


Attachments

Description duval.guerby 2017-01-14 06:02:39 UTC
I am trying to install Monodevelop on a Debian distribution using flatpak, but I am getting this error: No such branch 'app/com.xamarin.MonoDevelop/i386/stable' in repository summary.

Here is the command:
flatpak install --from https://download.mono-project.com/repo/monodevelop.flatpakref --user

The result:
Installing: com.xamarin.MonoDevelop/i386/stable
Installing: com.xamarin.MonoDevelop/i386/stable from com.xamarin.MonoDevelop-1-origin
error: No such branch 'app/com.xamarin.MonoDevelop/i386/stable' in repository summary
Comment 1 Jo Shields 2017-01-15 00:00:03 UTC
This seems about right, I'm currently only doing x86_64 builds of MonoDevelop. Honestly didn't think many people were still running i386 for development machines - amd64 shipped in 2003
Comment 2 duval.guerby 2017-01-15 11:17:05 UTC
That means, there is no way, I can install MonoDevelop 6.x.x on my i386 processor PC?
Comment 3 Jo Shields 2017-01-15 13:31:14 UTC
Um... Not right now? I didn't think there was any demands. I'll have to research cross-compiling in FlatPak
Comment 4 Herb 2017-06-29 18:17:14 UTC
same here, not installing on ubuntu 16.04 
/Documents/Projects$ flatpak install --user --from https://download.mono-project.com/repo/monodevelop.flatpakref
Installing: com.xamarin.MonoDevelop/i386/stable
Warning: Can't find dependencies: No entry for app/com.xamarin.MonoDevelop/i386/stable in remote summary flatpak cache 
Installing: com.xamarin.MonoDevelop/i386/stable from com.xamarin.MonoDevelop-1-origin
error: No such ref 'app/com.xamarin.MonoDevelop/i386/stable' in remote com.xamarin.MonoDevelop-1-origin
any suggestion how to fix it?
Comment 5 duval.guerby 2017-06-29 22:50:22 UTC
Use the legacy http://www.mono-project.com/download/#download-lin-ubuntu or change to a 64 bits.
Comment 6 duval.guerby 2017-06-29 22:55:16 UTC
After installing mono do one of this.
Install monodevelop-nunit to get the MonoDevelop NUnit addin, so you can run unit tests inside the IDE.
Install monodevelop-versioncontrol to add Git and SVN integration to the IDE.
Install monodevelop-database to add the database addin to the IDE.

using apt install.
From http://www.monodevelop.com/download/linux/
Comment 7 Dale 2017-08-11 15:09:37 UTC
We also are developing for 32 bit targets (think about embedded systems) and have failed to install the recent MonoDevelop onto Ubuntu 16.04 32 bit.

What makes this situation worse is the now-a-days getting a successful build of MonoDevelop on Linux is difficult due to the expanded number of dependencies that have been added. This forces us to Ubuntu 16.04 (from 14.04... which flatpak isn't supported on even though it's an active release!) 

I figured we'd be good-to-go with 16.04 32-bit but no Joy.

Please consider covering these platforms too. In the embedded space Intel type devices are mostly 32 bit.

Dale
Comment 8 Dale 2017-08-11 15:10:56 UTC
I just noticed that this was tagged as resolved.

So the solution is to "do nothing"?

Dale
Comment 9 Jo Shields 2017-08-11 15:19:35 UTC
Wasn't one of us that closed it - it's a reasonable request, just not something I've been able to prioritize.

I'm trying to fix up the current bad state of MonoDevelop builds, with any luck I can flip the switch to enable this with minimal fuss (a few hardcoded places that need un-hardcoding)
Comment 10 Dale 2017-08-11 20:53:24 UTC
Thanks for the response and update!

Dale

Note You need to log in before you can comment on or make changes to this bug.