[m-dev.] I have been making Debian packages

Paul Bone paul at bone.id.au
Sun Mar 26 21:45:32 AEDT 2017


On Sat, Mar 25, 2017 at 01:31:44PM +0000, Sebastian Godelet wrote:
> Hello Paul,
> 
> When I ran this on Windows 10 1607 “Ubuntu on Windows” (which is Ubuntu 14.01), I got the following error:
> 
> sudo apt-get mercury-recommended
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
> mercury-recommended : Depends: mercury-hlcpar-dev but it is not going to be installed
>                                                Depends: mercury-llcpar-dev but it is not going to be installed
> 
> Do you know if there is a way (command line switch, etc.) to say exactly why it couldn’t find those?

I don't know, I thought it usually says why something "is not going to be
installed".  Could it be the difference between "apt-get <packagename>" and
"apt-get install <packagename>"?

> sudo apt-get mercury-devel resolved fine.
> 
> Are the packaging scripts/instructions open-source?

They will be,  I'll publish them either later this evening or tomorrow.

Whatever you do you may still run into problems with Ubuntu on Windows.  At
YesLogic (where we use Mercury commercially) we have received some reports
that Mercury programs crash (we're using the hlc.par.gc grade FWIW).
We have simply instructed our customers to download the windows version if
they're running windows.  We suspect that Microsoft's emulation simply isn't
perfect.


-- 
Paul Bone
http://paul.bone.id.au


More information about the developers mailing list