Bug 16569

I can confirm this bug, too--it's currently preventing me from working on an asp.net project in Mageia.

CC: (none) => steve

the quoted bug does not provide a solution, just said it has been fixed in update.
I cannot investigate it atm, do you know the fixing? something to enable during building?

I poked around in the github repository for commits around that time period.  I didn't see anything specific to the asp.net fix the packager refers to.  I found the same problem reported on stackoverflow, too (http://stackoverflow.com/questions/27955046/monodevelop-aspnet-v5-7-missing), but same thing, just describing an updated package.

What would it take to bump the monodevelop version to something later than 5.7.0?  Is there a policy about keeping to the same version within a given release?  I would be happy to test out a newer package.  The MonoDevelop project had several more releases in the 5.7 branch, this looks like the latest one:  https://github.com/mono/monodevelop/releases/tag/monodevelop-5.7.2.7

i using monodevelop 5.9.6 builded from sources with mono from our repo and it work fine.

Replying on comment #4 Does that fix this problem?

Replying on comment #3 
Well policy does not allow new version but in some special cases. Monodevelop Changelog is not so clear to understand, I mean if it's all bug fixing or not
and often forward to Xamarin one.
I'm not using monodevolop for my daily job any more, but i'm still able to
work on it if i'm supported by people that do instead, so if you are able to
test new packages (when in testing) either for i586 or x86_64 and also provide
a test case for this bug we could probably make an exception, since i also used
new versions when it was important for my job... (Waiting for your reply I will ask if we can do that)

> Does that fix this problem?
yes, i builded my http://monosim.integrazioneweb.com and http://themonospot.integrazioneweb.com/ asp.net websites that are online with md 5.9.6

(In reply to Angelo Naselli from comment #5)
> Replying on comment #4 Does that fix this problem?
> 
> Replying on comment #3 
> Well policy does not allow new version but in some special cases.
> Monodevelop Changelog is not so clear to understand, I mean if it's all bug
> fixing or not
> and often forward to Xamarin one.
> I'm not using monodevolop for my daily job any more, but i'm still able to
> work on it if i'm supported by people that do instead, so if you are able to
> test new packages (when in testing) either for i586 or x86_64 and also
> provide
> a test case for this bug we could probably make an exception, since i also
> used
> new versions when it was important for my job... (Waiting for your reply I
> will ask if we can do that)

I can test new versions.  Let me know when there's one in testing and I'll install it and let you know.

thank you!!

Hi,

Since you both are using monodevelop more than me, could you please pointing
me to the right version? 
From http://www.monodevelop.com/download/ They say that
"The latest stable release is 5.9.7 Stable (5.9.7.9)" But that release is not
present here
http://download.mono-project.com/sources/monodevelop/
while the last release seems to be 5.10.0.704...
And if you could also tell me which of the old related packages is still valid
(such as monodevelop-database and monodevelop-debugger-gdb)

Thanks in advance.

Hi Angelo,
here can see commits from 5.9.6.23 (present under http://download.mono-project.com/sources/monodevelop/ ) and latest 5.9.7.9
https://github.com/mono/monodevelop/compare/monodevelop-5.9.6.23...monodevelop-5.9.7.9

i don't see significant changes, fix or features, so i think that we could use 5.9.6.23

Just to say i haven't forgotten this bug, i'm having some troubles in building monodevelop either for cauldron with last 5.10.x or for mga5 with 5.9.7.9.

Hi Angelo, thank you for the update, I really appreciate your hard work on this!

I tried to compile from source myself, just to install to /opt/monodevelop, to see if I could.  I ran into problems too, so I can relate to your difficulty.

Still, thank you so much for working on Monodevelop!

Hi Armando & Steve

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

(In case this report needs to stay open for a supported release: Reassigning to anaselli, who worked on this and who became tour official maintainer of monodevelop)

Assignee: matteo.pasotti => anaselli
CC: (none) => marja11

@Marja as far as i remember 5.10.x is in mageia 6 while i wasn't able to build 5.9.x in mageia 5... but it was really time ago :)

(In reply to Angelo Naselli from comment #13)
> @Marja as far as i remember 5.10.x is in mageia 6 while i wasn't able to
> build 5.9.x in mageia 5... but it was really time ago :)

Thanks for the reply, 5.10.0 is indeed in Mageia 6, so this report won't need to stay open for a still supported Mga release.

Closing as OLD, since Mga5 is EOL.

Status: NEW => RESOLVED
Resolution: (none) => OLD