Bug 15720 - Updating monodroid master makes the build fail
Summary: Updating monodroid master makes the build fail
Status: RESOLVED INVALID
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.10.1
Hardware: Macintosh Mac OS
: Normal enhancement
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2013-10-25 17:56 UTC by Mark Probst
Modified: 2017-07-03 06:07 UTC (History)
2 users (show)

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

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED INVALID

Description Mark Probst 2013-10-25 17:56:58 UTC
I cloned beaea12, which I got to build properly.  Then I fast-forwarded to 6fb15ea, after which "make world" failed with

    One or more modules needs update
    make: *** [check-versions] Error 1

"make reset-versions" did not change that.
Comment 1 Mark Probst 2013-10-25 18:29:27 UTC
Doing "make reset-mono" results in:

*** git fetch mono
remote: Counting objects: 29, done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 17 (delta 15), reused 17 (delta 15)
Unpacking objects: 100% (17/17), done.
From github.com:xamarin/mono
   4e0caa4..bf31be0  arm64      -> origin/arm64
*** git checkout master
M	mono/io-layer/processes.c
M	mono/metadata/console-unix.c
M	mono/metadata/sgen-os-posix.c
M	mono/mini/exceptions-arm.c
M	mono/mini/mini-posix.c
M	mono/mini/mini.c
M	mono/mini/mini.h
A	mono/utils/mono-signal-handler.h
Already on 'master'
Your branch and 'origin/master' have diverged,
and have 4605 and 2 different commits each, respectively.
  (use "git pull" to merge the remote branch into yours)
*** git reset --hard 6a2975513a49cae9d445ca3c5f5737f7b4c9a637
fatal: Could not parse object '6a2975513a49cae9d445ca3c5f5737f7b4c9a637'.
*** git submodule update --init --recursive
Warning: make reset-mono does not automatically clean up mono. You may have to run 'make clean-mono' separately.

Note that despite what look like an error, it does not fail.
Comment 2 Mark Probst 2013-10-31 17:11:15 UTC
What made "git reset" fail was the fact that its "origin" remote was still "xamarin/mono" rather than "mono/mono".  Correcting that made it work again.

Still, if "git reset" fails, "make reset-mono" should fail, too.
Comment 3 Prashant [MSFT] 2017-07-03 06:07:28 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Android. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.