Your message dated Mon, 21 Apr 2008 22:20:21 +0100 with message-id <1208812821.23742.40.camel@holly.codehelp> and subject line Unsuitable for fixing. has caused the Debian Bug report #476928, regarding dpkg-cross: Please make the -a option consistent with dpkg-buildpackage 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.) -- 476928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476928 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: dpkg-cross: Please make the -a option consistent with dpkg-buildpackage
- From: Jonas Meyer <quitte@gmail.com>
- Date: Sun, 20 Apr 2008 11:09:49 +0200
- Message-id: <20080420090949.32260.3148.reportbug@amd64.openworlddomination.de>
Package: dpkg-cross Version: 2.2.1 Severity: minor Hi Please change dpkg-cross to accept -aarch,too. I still add a space when using dpkg-buildpackage and forget the space with dpkg-cross after hundreds of invocations. Thanks, Jonas
--- End Message ---
--- Begin Message ---
- To: 476928-done@bugs.debian.org
- Subject: Unsuitable for fixing.
- From: Neil Williams <codehelp@debian.org>
- Date: Mon, 21 Apr 2008 22:20:21 +0100
- Message-id: <1208812821.23742.40.camel@holly.codehelp>
Version: 2.2.1 quit > Please change dpkg-cross to accept -aarch,too. I still add a space when > using dpkg-buildpackage and forget the space with dpkg-cross after hundreds > of invocations. Sorry - dpkg-cross is already scheduled for integration into dpkg-dev (although this will now happen after Lenny) and this change is not as simple as it would appear - far from it. dpkg-cross already includes debconf and user-specific support for not having to specify -a $ARCH at all. The only situations where -a is actually needed are where one specific user is preparing -cross packages for more than one cross architecture at the same time. I think that is really quite rare and does not warrant changing the option handling in a package that is already being migrated into dpkg-dev. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---