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

haskell-devscripts bug: failures when the same package is installed multiple times



Hello,

I have HSP 0.5.2 installed in my global package index, and in my local ~/.cabal. This causes dh_haskell_depends to generate a .substvars file with a dependency that lacks a name, but has a version number that is 1.5MB long :p

Here is a snippet of things going wrong: 

providing_package_for_ghc6_prof hsp-0.5.2-bdfd213b33219825eba1d5f48fd2c83e
+ local package
+ local dep
+ local dir
+ local dirs
+ local lib
+ strip_hash hsp-0.5.2-bdfd213b33219825eba1d5f48fd2c83e
+ echo hsp-0.5.2-bdfd213b33219825eba1d5f48fd2c83e
+ sed s/-................................$//
+ dep=hsp-0.5.2
+ grep -i ^library-dirs
+ cut -d: -f 2
+ ghc-pkg6 field hsp-0.5.2 library-dirs
+ dirs= /home/stepcut/.cabal/lib/hsp-0.5.2/ghc-6.13
/usr/lib/haskell-packages/ghc6/lib/hsp-0.5.2/ghc-6.13
+ ghc-pkg6 field hsp-0.5.2 hs-libraries
+ grep -i ^hs-libraries
+ sed -e s|hs-libraries: *\([^ ]*\).*|\1|
+ lib=HShsp-0.5.2
HShsp-0.5.2
+ [ -e /home/stepcut/.cabal/lib/hsp-0.5.2/ghc-6.13/libHShsp-0.5.2
HShsp-0.5.2_p.a ]
+ [ -e /usr/lib/haskell-packages/ghc6/lib/hsp-0.5.2/ghc-6.13/libHShsp-0.5.2
HShsp-0.5.2_p.a ]
+ echo
+ pkg=
+ dependency
+ local package
+ local version
+ local next_upstream_version
+ package=
+ dpkg-query --showformat=${Version} -W
+ version=2.6.6-0ubuntu12.<truncated version number, was 1.5MB long>

I believe the problem is this line:

$ ghc-pkg6 field hsp-0.5.2 hs-libraries
hs-libraries: HShsp-0.5.2
hs-libraries: HShsp-0.5.2

it is expecting only one line, but gets two, which results in the lib being all wrong (contains a line breaks, etc). This cascades until we get to the call to dpkg-query which lacks a package name, and appears to simply contain every package version on my local system (or something to that effect).

I have not included a patch.

I would guess that other functions are vulnerable to this same issue, I have not checked.

I am using:

 haskell-devscripts  0.7.9-27+seereason1~jaunty1

(It seems highly unlikely this issue is due to anything we have changed.)

- jeremy

Reply to: