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

Bug#305152: marked as done (clean target doesn't remove object files)

Your message dated Mon, 12 Apr 2010 14:29:26 +0200 (CEST)
with message-id <Pine.LNX.4.62.1004121426570.10720@sci.felk.cvut.cz>
and subject line ufsutils - clean target doesn't remove object files
has caused the Debian Bug report #305152,
regarding clean target doesn't remove object files
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 owner@bugs.debian.org
immediately.)


-- 
305152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=305152
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: ufsutils
Version: 0.0+2004.06.26-4
Severity: important

Well, that's it.  Clean target doesn't remove object files.

I suggest you switch to upstream makefiles which would handle the job.  There's
a freebsd5-buildutils package you can use for that.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: kfreebsd-i386 (i686)
Kernel: GNU/kFreeBSD 5.3-9
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)

Versions of packages ufsutils depends on:
ii  libc0.1               2.3-1+kbsd.9       GNU C Library: Shared libraries an
ii  libedit2              2.9.cvs.20040827-1 BSD editline and history libraries
ii  libncurses5           5.3.20030719-5     Shared libraries for terminal hand
ii  libufs2               0.0+2004.06.26-4   UFS filesystem shared library

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 7.2-3

The clean target now works,
may be even since 7.0-1.

Petr

--- End Message ---
Reply to: