mol-drivers-macsox not installable on gutsy

Bug #136555 reported by Marcus Comstedt
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mol-drivers-macosx (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: mol-drivers-macosx

The new version of mol available in gutsy/universe conflicts with mol-drivers-macosx << 0.9.72.1-1.
Therefore a newer version of mol-drivers-macosx is needed.

Revision history for this message
iroli (roland-lezuo) wrote :

Same bug here. Would be nice to see a fix.

Revision history for this message
fuoco (fuoco2-deactivatedaccount) wrote :

I see there was a newer version uploaded to hardy but it failed to build - and that was quite some time ago - nothing was done about it...

Revision history for this message
Nixblicker (el-lunatico) wrote :

Hi there,

same problem here on a Powerbook G4 ppc Hardy machine:

 "mol-drivers-macsox: depends on mol but won't be installed"

Please people, do something about it - i do need mol so desperately to skype with my girlfriend in china, because no ppc version of it is out there.

Please...

Kind Regards,
Nix

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 beta or later?

Changed in mol-drivers-macosx:
status: New → Incomplete
Revision history for this message
Marcus Comstedt (marcus-mc) wrote :

Well, the symptom is different, because now the package doesn't build, so there
is no candidate which would fail the dependency check... :-(

It's the compilation of bootx/main/init.S which fails.

Revision history for this message
Brian O'Keefe (okeefe) wrote :

Posting a comment to keep the bug open. I want MOL to run on Intrepid too!

Revision history for this message
Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in mol-drivers-macosx (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Marcus Comstedt (marcus-mc) wrote :

The problem seems to have been fixed in 9.04, but I don't get the part about
"lacking needed information as described in previous comments". The only
information requested was whether the problem existed in 8.10 beta, and I already
answered that...

Revision history for this message
Victor Vargas (kamus) wrote :

Thank for your reply Marcus, this report was invalidated because your report have a long time without activity, but any way is good to know that this issue was fixed in newer versions.

Best regards

Revision history for this message
kallewirsch (stefan-hunsicker) wrote :

I'm sorry to tell you that the problem is back in 9.10 karmic:

"mol-drivers-macsox: depends on mol but won't be installed"

mol version is 0.9.72.1~dfsg-1ububtu1 (karmic)
mol-drivers-macsox version is 0.9.71-1 (karmic)

My machine is a powerbook G4.

Changed in mol-drivers-macosx (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
chunky (chunky) wrote :

This impacts me, on PPC 9.04. I have mol and mol-drivers-linux installed. I also have enabled all the repositories available by default, and the system is fully up to date.

From a completely fresh install of ppc 9.04, go into synaptic and enable all the repositories that are offered [backports, testing, etc]. Run a full system update, reboot. Go into synaptic and install mol [which depends on mol-drivers-linux, so install that too]. Here's what happens when I try to install mol-drivers-macosx from the command-line:

chunky@goghlin:~$ sudo apt-get install mol-drivers-macosx
[sudo] password for chunky:
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:
  mol-drivers-macosx: Depends: mol (>= 0.9.68+20030225-1) but it is not going to be installed
E: Broken packages
chunky@goghlin:~$

Revision history for this message
Victor Vargas (kamus) wrote :

@Marcus, is this issue still affecting you? Additionally, if you are able to reproduce this problem in latest version included in your actual ubuntu version would be great, thanks in advance!

Revision history for this message
Marcus Comstedt (marcus-mc) wrote :

@Kamus: 0.9.72.1-1 of the package was released, fixing the dependency problem. However, this version does not compile, so there are no binary packages available. You could argue that the issue is a different one, but the problem that a binary package of 0.9.72.1-1 (or newer) does not exist remains.

I'm not sure what to make of your second question; the 0.9.72.1-1 package never compiled from source, and there hasn't been one released since. Trying to build the package on karmic gives exactly the same error as on earlier releases; see the build logs on https://launchpad.net/ubuntu/+source/mol-drivers-macosx/0.9.72.1-1.

Revision history for this message
Marcus Comstedt (marcus-mc) wrote :

Incidentally, here is a patch which fixed the compilation problem:

--- mol-drivers-macosx-0.9.72.1/config/Rules.make.orig 2010-01-06 21:41:07.000000000 +0100
+++ mol-drivers-macosx-0.9.72.1/config/Rules.make 2010-01-06 21:38:58.000000000 +0100
@@ -223,7 +223,7 @@
 M_ASMFLAGS = -D__ASSEMBLY__ $(ALTIVEC) $(ASMFLAGS)
 FILTERBIN = $(top_odir)/build/scripts/asfilter
 ASFILTER = $(shell if test -x $(FILTERBIN) ; then echo $(FILTERBIN) \
- ; else echo "tr ';' '\n'" ; fi)
+ ; else /bin/echo "tr ';' '\n'" ; fi)
 INVOKE_M4 = | $(M4) -s $(M4_NO_GNU) | $(ASFILTER)

 $(ODIR)/%.o: %.S Makefile

The problem is that the builtin "echo" in /bin/dash prints \n as newline, not as a backslash followed by the letter n. Using /bin/echo instead fixes the problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.