Bug#690822: caribou: architecture specific paths in arch-all package

2012-10-18 Thread Josselin Mouette 
Le jeudi 18 octobre 2012 à 05:14 +0200, Michael Biebl a écrit : 
 Since caribou installs the introspection files and python modules in the
 default system paths, it seems to me that it actually doesn't really
 matter that much that GI_TYPELIB_PATH and PYTHONPATH point to
 non-existing directories.

If packages from another architecture are installed in these paths (e.g.
for cross-building), the paths will exist and this is going to fail in
spectacular ways.

 We could just as well drop those environment variables (including
 LD_LIBRARY_PATH).

I agree this is the best course of action.

 So it's mostly a cosmetic issue, imo, definitely not RC.

I’m not sure it doesn’t need to be RC. In all cases it would be better
to fix that for wheezy.

Cheers,
-- 
 .''`.  Josselin Mouette
: :' :
`. `'
  `-


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#690822: caribou: architecture specific paths in arch-all package

2012-10-17 Thread Paul Wise 
Package: caribou
Version: 0.4.4-1
Severity: important
Usertags: archspecificpaths

I'm not sure if this bug should be RC or not, but the caribou and
caribou-preferences bash scripts are hard-coding multi-arch library
paths. They are also setting a PYTHONPATH that does not exist on Debian.

caribou:

  export 
PYTHONPATH=/usr/lib/python2.7/site-packages${PYTHONPATH:+:$PYTHONPATH}
  export 
GI_TYPELIB_PATH=${prefix}/lib/x86_64-linux-gnu/girepository-1.0${GI_TYPELIB_PATH:+:$GI_TYPELIB_PATH}

caribou-preferences:

  datadir=$(/usr/bin/python -c from gi.repository import GLib; print 
':'.join(GLib.get_system_data_dirs()))
  export 
PYTHONPATH=/usr/lib/python2.7/site-packages${PYTHONPATH:+:$PYTHONPATH}
  export 
GI_TYPELIB_PATH=${prefix}/lib/x86_64-linux-gnu/girepository-1.0${GI_TYPELIB_PATH:+:$GI_TYPELIB_PATH}
  export 
LD_LIBRARY_PATH=${prefix}/lib/x86_64-linux-gnu${LD_LIBRARY_PATH:+:LD_LIBRARY_PATH}
  export XDG_DATA_DIRS=${prefix}/share${datadir:+:$datadir}

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (700, 'testing'), (600, 'unstable'), (550, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages caribou depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-2
ii  gconf-gsettings-backend [gsettings-backend]  3.2.5-1+build1
ii  gir1.2-caribou-1.0   0.4.4-1
ii  gir1.2-clutter-1.0   1.10.8-2
ii  gir1.2-glib-2.0  1.32.1-1
ii  gir1.2-gtk-3.0   3.4.2-4
ii  python   2.7.3~rc2-1
ii  python-dbus  1.1.1-1
ii  python-gi3.2.2-1
ii  python-pyatspi2  2.5.3+dfsg-2

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#690822: caribou: architecture specific paths in arch-all package

2012-10-17 Thread Michael Biebl 
Hi,

On 18.10.2012 04:48, Paul Wise wrote:
 
 I'm not sure if this bug should be RC or not, but the caribou and
 caribou-preferences bash scripts are hard-coding multi-arch library
 paths. They are also setting a PYTHONPATH that does not exist on Debian.
 
 caribou:
 
   export 
 PYTHONPATH=/usr/lib/python2.7/site-packages${PYTHONPATH:+:$PYTHONPATH}
   export 
 GI_TYPELIB_PATH=${prefix}/lib/x86_64-linux-gnu/girepository-1.0${GI_TYPELIB_PATH:+:$GI_TYPELIB_PATH}
 
 caribou-preferences:
 
   datadir=$(/usr/bin/python -c from gi.repository import GLib; print 
 ':'.join(GLib.get_system_data_dirs()))
   export 
 PYTHONPATH=/usr/lib/python2.7/site-packages${PYTHONPATH:+:$PYTHONPATH}
   export 
 GI_TYPELIB_PATH=${prefix}/lib/x86_64-linux-gnu/girepository-1.0${GI_TYPELIB_PATH:+:$GI_TYPELIB_PATH}
   export 
 LD_LIBRARY_PATH=${prefix}/lib/x86_64-linux-gnu${LD_LIBRARY_PATH:+:LD_LIBRARY_PATH}
   export XDG_DATA_DIRS=${prefix}/share${datadir:+:$datadir}

Since caribou installs the introspection files and python modules in the
default system paths, it seems to me that it actually doesn't really
matter that much that GI_TYPELIB_PATH and PYTHONPATH point to
non-existing directories.
We could just as well drop those environment variables (including
LD_LIBRARY_PATH).

So it's mostly a cosmetic issue, imo, definitely not RC.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature