Your message dated Fri, 28 Nov 2008 11:30:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: libupsclient1 ends up in /lib, not /usr/lib
has caused the Debian Bug report #505101,
regarding "libupsclient-dev points to /usr/lib not /lib"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
505101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505101
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Subject: libupsclient1 ends up in /lib, not /usr/lib
Package: libupsclient1
Severity: serious

libupsclient1 installs its shared libraries into /lib, not /usr/lib

[EMAIL PROTECTED]:/# dpkg -L libupsclient1
/lib/libupsclient.so.1.0.0

It appears all thats needed to fix is a change in the rules on 131-132
to change debian/lib to debian/usr/lib.
Michael

-- System Information:
Debian Release: lenny/sid
  APT prefers jaunty-updates
  APT policy: (500, 'jaunty-updates'), (500, 'jaunty-security'), (500, 'jaunty')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.27-7-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
fixed 505101 2.2.2-10
thanks

forgotten closes in 2.2.2-10 changelog...

-- Arnaud


--- End Message ---

Reply via email to