Control: severity -1 normal Hallo,
thanks for the report. As far as I can see, libdrizzle0 is a different codebase than libdrizzle4. though they seem to share the same roots. Libdrizzle0 was indeed removed and is no longer available in Debian, one reason was that there was drizzle and also no reverse dependencies on libdrizzle0. So I assume you are talking about some private software which is broken by libdrizzle4... However, the code looks to me as there is no UDS support in libdrizzle4? Can you provide a testcase so I can approach upstream more efficiently? Thanks! -- Tobias Am Donnerstag, den 27.02.2014, 11:49 +0100 schrieb Botond Botyanszki: > Package: libdrizzle4 > Version: 1:7.1.36-stable-1 > Severity: important > > There is a bug in libdrizzl4 which effectively makes > it useless when using a unix domain socket: > https://bugs.launchpad.net/libdrizzle/+bug/1098855 > The old libdrizzle0 worked properly and was available > in squeeze but has been removed from stable. > Trying to force users upgrading to a broken lib is not > very nice. > > > -- System Information: > Debian Release: jessie/sid > APT prefers stable > APT policy: (500, 'stable'), (10, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: > LC_ALL set to en_US.UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages libdrizzle4 depends on: > ii libc6 2.17-97 > ii libgcc1 1:4.8.2-10 > ii libstdc++6 4.8.2-10 > > libdrizzle4 recommends no packages. > > libdrizzle4 suggests no packages. > > -- no debconf information > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
