[UNMETDEPS] illuminator has unmet dependencies

Bug #65388 reported by Sivan Greenberg
14
Affects Status Importance Assigned to Milestone
illuminator (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 affects distros/ubuntu/illuminator
 status confirmed
 subscribe motu

text:
A run of
  LC_ALL=C apt-cache -i unmet | grep ^Package | cut -d' ' -f2 | sort -u | \
     xargs apt-cache showsrc | grep Package | sed 's/Package\:\ //g' | sort -u
indicates that the source package illuminator has binary packages that are not
installable at the moment.

Please have a look and make sure it's installable again.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFFLPWs/GNOP6hwhMIRAklVAJ9kHSMCVBqFlFT3YhBSV8hKbch5WgCgxcGd
i1o3Ya0zsD472nvtfUdHH/4=
=c7iQ
-----END PGP SIGNATURE-----

Related branches

Revision history for this message
Caroline Ford (secretlondon) wrote :

illuminator (0.10.0-2) build depends on libffm-dev [alpha] (not available)

libluminate-dev (0.10.0-2) depends on libpetsc2.3.0-dev (>= 2.3.0-3)

illuminator-demo (0.10.0-2) depends on libpetsc2.3.0

libluminate7 (0.10.0-2) depends on libpetsc2.3.0

Revision history for this message
Michael Bienia (geser) wrote :

Trying to rebuild illuminator with petsc 2.3.2 leads to a FTBFS. It's the same problem as reported in Debian bug #402784.

Revision history for this message
Matti Lindell (mlind) wrote :

I'm not sure why petsc upstream is breaking API's this way when version number indicates a stable maintenance release (2.3.2). Change is documented on http://www-unix.mcs.anl.gov/petsc/petsc-as/documentation/changes/232.html

I'm attaching a debdiff with small patch that should work with petsc >= 2.3.0 and is backwards-compatible, it's untested though and I'm not sure if it even works. There's something weird going on with petsc librairies, tsview --help just gives me bunch of petsc errors..

Changed PetscRandomCreate is documented in http://www-unix.mcs.anl.gov/petsc/petsc-as/snapshots/petsc-current/docs/manualpages/Sys/PetscRandomCreate.html#PetscRandomCreate. If anyone with more brain wants to poke this around.

Revision history for this message
Vassilis Pandis (pandisv) wrote :

This has been fixed in 0.10.0-3 which is not yet in Feisty:

 illuminator (0.10.0-3) unstable; urgency=low
 .
   * Rebuilding against new PETSc 2.3.2 (closes: #376890).
   * Fixed chts.c for new PetscRandom API (closes: #402784).

Revision history for this message
Andrew Mitchell (ajmitch) wrote :

Filed a sync request as bug 82589, was easier to set as a separate bug & use requestsync. I'll close this one once synced.

Revision history for this message
Matti Lindell (mlind) wrote :

recently synced illuminator 0.10.0-4 fixes this issue

Changed in illuminator:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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