Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12927 - [Monodevelop] - Broken dependencies

Attached to Project: Community Packages
Opened by andrey demidov (demas) - Saturday, 24 January 2009, 09:55 GMT
Last edited by Timm (gummibaerchen) - Sunday, 25 January 2009, 17:54 GMT
Task Type Support Request
Category
Status Closed
Assigned To Timm (gummibaerchen)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

I have upgraded mono to last version. During upgrading process I have removed monodoc (because it was incompatible with new version of mono) and monodevelop (because it has monodoc dependency).

Now when I trying to install monodevelop I get this error message:

demas@demashost:~$ sudo pacman -S monodevelop
resolving dependencies...
error: cannot resolve "monodoc>=1.0", a dependency of "monodevelop"
error: failed to prepare transaction (could not satisfy dependencies)
:: monodevelop: requires monodoc>=1.0
And I cannot find monodoc in the repositories:

demas@demashost:~$ pacman -Ss monodoc
extra/mono 2.2-1
Free implementation of the .NET platform including runtime and compiler
extra/mono-tools 2.2-1
collection of testing and development tools for use with mono (including monodoc browser)
How can I install monodoc with new version of mono?
Online

This task depends upon

Closed by  Timm (gummibaerchen)
Sunday, 25 January 2009, 17:54 GMT
Reason for closing:  Fixed
Additional comments about closing:  the monodevelop package now uses the latest snapshots, which work fine with mono 2.2. monodoc dep dropped.
Comment by Xavier (shining) - Saturday, 24 January 2009, 14:54 GMT
The new mono provides monodoc :
pacman -Qi mono | grep Prov
$ Provides : monodoc
But it does not provide any version of it, so it does not satisfy the >=1.0 dependency.

Three solutions :
1) change the deps mono>=1.1.10 monodoc>=1.0 to just mono>=2.2 (my favorite one, since arch is made for keeping system uptodates)
2) change the dep monodoc>=1.0 to just monodoc
3) report a bug against mono to change provides=('monodoc') to provides=("monodoc=$pkgver")

While looking at this problem, I read the following comment on AUR:
Comment by: Rulatir on 2008 11 10 [16:27:48]
Just a quick troubleshooter - the build system of this package doesn't like parallel make. Remove any -j flags from the MAKEFLAGS variable in /etc/makepkg.conf before building monodevelop from AUR.

From man PKGBUILD :
makeflags
Allow the use of user-specific makeflags during build as
specified in makepkg.conf(5). More useful in its negative form
!makeflags with select packages that have problems building
with custom makeflags such as -j2 (or higher).

So please also add options=(!makeflags).
Comment by James Munro (xen) - Saturday, 24 January 2009, 17:24 GMT
I also have this problem, just to confirm. It makes no difference whether you already have MonoDevelop installed before the update, as you are forced to remove it if you wish to proceed with the update.
Comment by Xavier (shining) - Saturday, 24 January 2009, 17:32 GMT
This should work as a workaround :
# pacman -Sd monodevelop
Comment by Isenmann Daniel (ise) - Saturday, 24 January 2009, 17:49 GMT
I'm the maintainer of mono, I would take solution 1). Mono includes monodoc, so this dependency is obsolote and should be deleted.
Comment by Timm (gummibaerchen) - Sunday, 25 January 2009, 11:33 GMT
Monodevelop 1.0 doesn't build anymore.

Can anyone confirm?
Comment by Timm (gummibaerchen) - Sunday, 25 January 2009, 12:01 GMT
As long as we don't want to ship an older mono 1.x, I think we have to switch to monodevelop-(alpha|snapshot).
On the other hand, the MD 1.0 binary packages still work, so maybe we should do the evil and remove the dependency by hand?
Comment by James Munro (xen) - Sunday, 25 January 2009, 12:51 GMT
I'm think this problem is related. After forcing MD (ignoring the monodoc dependency) I can't open files in existing MD projects. I get the following error:

Exception occurred: Object reference not set to an instance of an object

System.NullReferenceException: Object reference not set to an instance of an object
at MonoDevelop.Projects.Text.TextFile.Read (System.String fileName, System.String encoding) [0x00000]
at MonoDevelop.Projects.Text.TextFile.ReadFile (System.String fileName, System.String encoding) [0x00000]
at MonoDevelop.SourceEditor.Gui.SourceEditorBuffer.LoadFile (System.String fileName, System.String mime, System.String encoding) [0x00000]
at MonoDevelop.SourceEditor.Gui.SourceEditorDisplayBindingWrapper.Load (System.String fileName, System.String encoding) [0x00000]
at MonoDevelop.SourceEditor.Gui.SourceEditorDisplayBindingWrapper.Load (System.String fileName) [0x00000]
at MonoDevelop.Ide.Gui.LoadFileWrapper.Invoke (System.String fileName) [0x00000]

Do you think this is because MD needs rebuilding against the new mono build, can someone confirm this?
Comment by Timm (gummibaerchen) - Sunday, 25 January 2009, 14:27 GMT
The thing is, that you can not rebuild MD 1.0 against Mono 2.2 anymore.
Comment by Isenmann Daniel (ise) - Sunday, 25 January 2009, 15:43 GMT
@xen: I have the same issue on x86_64. On i686 everything is fine. I have build the 2.0 alpha2 of monodevelop and there everything is fine. Even a svn-snapshot of monodevelop from yesterday worked without any errors.

@Timm:
It's annyoing that MD can't be rebuild against mono 2.2. Best solution is to remove monodoc by hand and installing mono 2.2. I don't see any other possibility. Or you rebuild it against the old version of mono, if you have one, and delete the dependency to monodoc. I would say that removing monodoc manually is the best solution.
Comment by Timm (gummibaerchen) - Sunday, 25 January 2009, 16:47 GMT
Well the inability to open projects is a showstopper here.

What use is it then?

So, I read it as the only way to get a working MD is using 2.0-x.

I will prepare that then (and probably go with snapshots as the alphas are outdated and probably even buggier than the latest snaps).

Why aren't there any bugfix-releases upstream anyway...
Comment by Isenmann Daniel (ise) - Sunday, 25 January 2009, 17:02 GMT
I don't know why there are updates for MD 1.0, it should be there because this is the latest stable version of it. Nevertheless, the snapshot from yesterday worked without any know issues from my side. Everything I tried worked. So maybe it would be better to switch to the snapshots unless the stable 2.0 is released.
Comment by Timm (gummibaerchen) - Sunday, 25 January 2009, 17:49 GMT
Ok, I switched to the latest snapshot.

Now MD has a rather high version number, but I didn't wan't to mess with a new monodevelop-snapshot packages which provides and replaces the normal one.

If 2.0 comes out we will just enforce it's installation, this is especially no harm if they continue with 0 bug-fix releases after 2.0...

Loading...