Your message dated Sat, 22 Dec 2007 10:59:33 +0100 with message-id <200712221059.37674.seanius@debian.org> and subject line not a bug really 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 ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: build target cannot be run after interrupted
- From: Robert Millan <rmh@aybabtu.com>
- Date: Mon, 10 Dec 2007 16:41:02 +0100
- Message-id: <[🔎] 20071210154102.12340.69251.reportbug@thorin>
Package: compiz Version: latest Severity: important Tags: patch See attached patch. -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-amd64 Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)--- compiz-0.5.2.old/debian/rules 2007-12-10 16:20:21.000000000 +0100 +++ compiz-0.5.2/debian/rules 2007-12-10 15:49:32.000000000 +0100 @@ -44,7 +44,7 @@ build-stamp: dh_testdir - mkdir obj-$(DEB_BUILD_GNU_TYPE) + mkdir -p obj-$(DEB_BUILD_GNU_TYPE) chmod +x ./configure cd obj-$(DEB_BUILD_GNU_TYPE) && \ ../configure --prefix=/usr --sysconfdir=\$${prefix}/share $(confflags) \
--- End Message ---
--- Begin Message ---
- To: 455512-done@bugs.debian.org
- Subject: not a bug really
- From: sean finney <seanius@debian.org>
- Date: Sat, 22 Dec 2007 10:59:33 +0100
- Message-id: <200712221059.37674.seanius@debian.org>
hi robert, policy doesn't say anything about the bulid target needing to be idempotent by itself. it does say that you can require debian/rules clean to be run first-- which if you do should solve the problem with interrupted builds. there are many easily constructable situations where running build twice in a row might produce unwanted results (maybe if someone echo's or sed's onto files in the build target and undoes them in the clean target). therefore i close this bug. seanAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---