• Bug#251460: discover depends on libdiscover2 but actually requires libd

    From Ian Murdock@1:229/2 to Tom Epperly on Tue Aug 17 23:30:18 2004
    From: [email protected]

    Tom,

    On Fri, 2004-05-28 at 08:42 -0700, Tom Epperly wrote:
    Package: discover
    Version: 2.0.4-5
    Severity: normal

    driftcreek:/home/epperly# ldd `which discover`
    libdiscover.so.1 => /usr/lib/libdiscover.so.1 (0x4002d000)
    libm.so.6 => /lib/libm.so.6 (0x4003e000)
    libc.so.6 => /lib/libc.so.6 (0x40060000)
    /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

    What's the output of `which discover` here? I suspect you're actually
    looking at a discover 1.x binary, based not only on the presence of libdiscover.so.1 but also on the lack of libcurl.so.1, libexpat.so.2,
    etc. which discover 2 links to.

    --
    Ian Murdock
    317-578-8882 (office)
    http://www.progeny.com/
    http://ianmurdock.com/

    "If they give you ruled paper, write the other way." --Juan Ram�n Jim�nez



    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Tom Epperly@1:229/2 to Ian Murdock on Wed Aug 18 23:20:06 2004
    From: [email protected]

    Ian Murdock wrote:

    Tom,

    On Fri, 2004-05-28 at 08:42 -0700, Tom Epperly wrote:


    Package: discover
    Version: 2.0.4-5
    Severity: normal

    driftcreek:/home/epperly# ldd `which discover`
    libdiscover.so.1 => /usr/lib/libdiscover.so.1 (0x4002d000)
    libm.so.6 => /lib/libm.so.6 (0x4003e000)
    libc.so.6 => /lib/libc.so.6 (0x40060000)
    /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)



    What's the output of `which discover` here? I suspect you're actually
    looking at a discover 1.x binary, based not only on the presence of >libdiscover.so.1 but also on the lack of libcurl.so.1, libexpat.so.2,
    etc. which discover 2 links to.



    driftcreek:/extra/epperly/pcgen# which discover
    /sbin/discover
    driftcreek:/extra/epperly/pcgen# ldd /sbin/discover
    libdiscover.so.1 => not found
    libm.so.6 => /lib/libm.so.6 (0x4002e000)
    libc.so.6 => /lib/libc.so.6 (0x40050000)
    /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) driftcreek:/extra/epperly/pcgen# dpkg --list '*discover*' Desired=Unknown/Install/Remove/Purge/Hold
    | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
    |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
    uppercase=bad)
    ||/ Name Version Description +++-==============-==============-============================================ ii discover 2.0.4-5 hardware identification system
    ii discover-data 2.2004.05.03-4 Data lists for Discover hardware
    detection s
    un discover1-data <none> (no description available)
    pn libdiscover-de <none> (no description available)
    un libdiscover0 <none> (no description available)
    un libdiscover0-d <none> (no description available)
    pn libdiscover1 <none> (no description available)
    pn libdiscover1-p <none> (no description available)
    ii libdiscover2 2.0.4-5 hardware identification library

    It appears that /sbin/discover wasn't removed when I upgraded or something. driftcreek:/extra/epperly/pcgen# dpkg --search /sbin/discover
    dpkg: /sbin/discover not found.
    Maybe I got the wrong discover when I recovered from backup after a hard
    disk failure.

    Thanks,

    Tom


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)