Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 688 [details]
Screenshot for the bug.
Steps to reproduce:
1. Launch the MonoDevelop.
2. Start a New Solution or Open the Existing Solution.
3. Solution sidebar appears at the left panel.
4. Right Click on Solution/Project name.
5. Click on the option "Tools"
6. Click on the option "Create Package"
7. Select Tarball and click on Forward.
8. Click on Forward button.
9. Provide the path of Deploy directory and then Click on Create.
When try to create package using Tarball, error message appears, i.e.
"Solution could not be deployed:. An unspecified error occurred while running 'autogen.sh'". Refer to the attached screenshot.
Error should not appear and the solution should successfully get deployed.
Mac Lion and Snow Leopard.
Xcode 4.2 with iOS 5.0
michael, Is this something we want to support for monotouch/m4a apps or should it be hidden/disabled?
*** Bug 969 has been marked as a duplicate of this bug. ***
IMO we should remove the packaging addin completely, it's been barely maintained for years and its project model doesn't really make sense. I partially redesigned it back in '07 but we never had the resources to implement it.
This issue is still reproducible at our end.
Mac 10.7 and 10.6
Please suggest the further course of action. As of now we are reopening this issue dated 15th December, 2011.
Reopening this issue for now, please suggest if we can close it.
Agree with Michael, let us kill this feature.
Closing as this feature appears to have been killed