[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Processed (with 1 errors): Re: Bug#787227: broken on armel due to broken RUNPATH: /usr/lib/ghc/bin/ghc: error while loading shared libraries: libHShaskeline-0.7.1.2-ghc7.8.4.so: cannot open shared object file: No such file or directory



Processing control commands:

> severity -1 wishlist
Bug #787227 [ghc] broken on armel due to broken RUNPATH: /usr/lib/ghc/bin/ghc: error while loading shared libraries: libHShaskeline-0.7.1.2-ghc7.8.4.so: cannot open shared object file: No such file or directory
Severity set to 'wishlist' from 'important'
> reassign -1 libc6
Bug #787227 [ghc] broken on armel due to broken RUNPATH: /usr/lib/ghc/bin/ghc: error while loading shared libraries: libHShaskeline-0.7.1.2-ghc7.8.4.so: cannot open shared object file: No such file or directory
Bug reassigned from package 'ghc' to 'libc6'.
No longer marked as found in versions ghc/7.8.4-8.
Ignoring request to alter fixed versions of bug #787227 to the same values previously set
> retitle -1 ld-linux.so loads libraries from . when /proc is not mounted
Bug #787227 [libc6] broken on armel due to broken RUNPATH: /usr/lib/ghc/bin/ghc: error while loading shared libraries: libHShaskeline-0.7.1.2-ghc7.8.4.so: cannot open shared object file: No such file or directory
Changed Bug title to 'ld-linux.so loads libraries from . when /proc is not mounted' from 'broken on armel due to broken RUNPATH: /usr/lib/ghc/bin/ghc: error while loading shared libraries: libHShaskeline-0.7.1.2-ghc7.8.4.so: cannot open shared object file: No such file or directory'
> affects -1 + ghc
Bug #787227 [libc6] ld-linux.so loads libraries from . when /proc is not mounted
Added indication that 787227 affects ghc
> summary -1 0
Failed to give 787227 a summary: Can't use string ("Received: (at 787227) by bugs.de"...) as an ARRAY ref while "strict refs" in use.


-- 
787227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787227
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems


Reply to: