Your message dated Mon, 19 Jun 2006 18:57:44 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#336715: fixed in lsscsi 0.16-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: lsscsi
Version: 0.15-1
Severity: serious
Justification: Policy violation (4.8)

Lsscsi fails to build with sudo as root command, like in
dpkg-buildpackage -us -uc -B -rsudo
because the .deps/ directory is created with root permissions in the
clean target. The result is:

[...]
# Add here commands to compile the package.
/usr/bin/make
make[1]: Entering directory /home/ths/colo/lsscsi-0.15'
cd . && autoheader
/usr/bin/make  all-recursive
make[2]: Entering directory /home/ths/colo/lsscsi-0.15'
make[3]: Entering directory /home/ths/colo/lsscsi-0.15'
gcc -DHAVE_CONFIG_H -I. -I. -I.    -Wall -W -g -O2 -c lsscsi.c
lsscsi.c:1214: fatal error: opening dependency file .deps/lsscsi.pp: Permission 
denied
compilation terminated.
make[3]: *** [lsscsi.o] Error 1
make[3]: Leaving directory /home/ths/colo/lsscsi-0.15'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory /home/ths/colo/lsscsi-0.15'
make[1]: *** [all-recursive-am] Error 2
make[1]: Leaving directory /home/ths/colo/lsscsi-0.15'
make: *** [build-stamp] Error 2


Thiemo


--- End Message ---
--- Begin Message ---
Version: 0.17-1

On Wed, Jan 25, 2006 at 12:17:11AM -0800, Matt Taggart wrote:
>  lsscsi (0.16-1) unstable; urgency=low
>  .
>    * New upstream version
>    * Fix building with sudo, thanks Stefan Fritsch. Closes: #336715

For some reason, this changelog snippet is not included in the 0.17-1
package, which leaves the problem open in the BTS (it doesn't understand
that 0.17-1 incorporates the fixes from 0.16-1). I've checked that the fix
is indeed present in 0.17-1, so I'm marking it as fixed in that version as
well.

/* Steinar */
-- 
Homepage: http://www.sesse.net/

--- End Message ---

Reply via email to