Bug#637363: ***SPAM*** Re: Bug#637363: debootstrap 1.0.35 fails to accept --arch=amd64 on CentOS 5.6 system
Samuel Thibault wrote: clone 637363 -1 retitle -1 explain what target means severity -1 wishlist thanks Whit Blauvelt, le Wed 10 Aug 2011 16:21:00 -0400, a écrit : On Wed, Aug 10, 2011 at 09:52:36PM +0200, Samuel Thibault wrote: It can't be the target of debootstrap, since debootstrap is already running in it. Think of it (the host, Centos) as the hand which is holding the dart (debootstrap) to the target (the actual machine running the just-installed Debian, which may or may not be Centos). Once you've explained it, I understand your technical use of target to mean what you mean by it. I'm only suggesting it is ambiguous, so that other people may easily misunderstand it in the context of building in a chroot, where the target may be misinterpreted to mean the host of the chroot. Again, once you've clarified it, it's clear. But the term target, without the clarification, can confuse - as in I'm going to throw Debian into a chroot on this CentOS box. Ok, then cloning the bug. target is explaned in debootstrap's manual page, in the very first line of the description. -- see shy jo signature.asc Description: Digital signature
Bug#637363: ***SPAM*** Re: Bug#637363: debootstrap 1.0.35 fails to accept --arch=amd64 on CentOS 5.6 system
Joey Hess, le Mon 15 Aug 2011 13:56:26 -0400, a écrit : Samuel Thibault wrote: clone 637363 -1 retitle -1 explain what target means severity -1 wishlist thanks Whit Blauvelt, le Wed 10 Aug 2011 16:21:00 -0400, a écrit : On Wed, Aug 10, 2011 at 09:52:36PM +0200, Samuel Thibault wrote: It can't be the target of debootstrap, since debootstrap is already running in it. Think of it (the host, Centos) as the hand which is holding the dart (debootstrap) to the target (the actual machine running the just-installed Debian, which may or may not be Centos). Once you've explained it, I understand your technical use of target to mean what you mean by it. I'm only suggesting it is ambiguous, so that other people may easily misunderstand it in the context of building in a chroot, where the target may be misinterpreted to mean the host of the chroot. Again, once you've clarified it, it's clear. But the term target, without the clarification, can confuse - as in I'm going to throw Debian into a chroot on this CentOS box. Ok, then cloning the bug. target is explaned in debootstrap's manual page, in the very first line of the description. Not the target directory, but the meaning of target in the --arch option. Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637363: ***SPAM*** Re: Bug#637363: debootstrap 1.0.35 fails to accept --arch=amd64 on CentOS 5.6 system
target is explaned in debootstrap's manual page, in the very first line of the description. With all respect, it isn't described with debootstrap -h. Not every system with debootstrap installed has the man page installed. So my suggestion is only that debootstrap -h clarify the language, substituting something like system to install for target system. Also, --arch on the command line doesn't mean the same thing as ARCH in the code - where it refers to the system it's being installed from (which in a chroot install is also the system it's being installed on - a target in a sense). So when the code fails with an unable to determine the architecture error, and it's ARCH in the code that's having the problem, and there's an --arch flag at the prompt - well, as I said I'm not the only person who had ended up confused by that. Thanks, Whit -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637363: debootstrap 1.0.35 fails to accept --arch=amd64 on CentOS 5.6 system
Package: debootstrap Version: 1.0.35 debootstrap was install per the manual install method in section D.3.2. Install debootstrap of http://www.debian.org/releases/stable/i386/apds03.html.en The result: # /usr/sbin/debootstrap --arch=amd64 squeeze /mnt/deb /http://ftp.us.debian.org/debian E: Couldn't work out current architecture Removing the = makes no difference. This is on an up-to-date CentOS 5.6 system: # uname -a Linux xxx.yyy.local 2.6.18-194.11.4.el5 #1 SMP Tue Sep 21 05:04:09 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux I suggest that debootstrap should accept the --arch specification rather than try to work out what it is by whatever method. Or if its attempt to work out the architecture fails, it should offer the user a chance to over ride its failure and simply accept the architecture specified. Whit -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637363: debootstrap 1.0.35 fails to accept --arch=amd64 on CentOS 5.6 system
Whit Blauvelt, le Wed 10 Aug 2011 12:19:36 -0400, a écrit : # /usr/sbin/debootstrap --arch=amd64 squeeze /mnt/deb /http://ftp.us.debian.org/debian There is a spurious '/' in front of http:// Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637363: debootstrap 1.0.35 fails to accept --arch=amd64 on CentOS 5.6 system
That's spurious in my report because of not fully undoing my text editor's word wrap feature, which broke the line there and started the second line with # / - I only noticed the # part when I reunited it. Anyway, the bug occurred without the spurious /. Sorry that confused the report. Whit On Wed, Aug 10, 2011 at 08:06:09PM +0200, Samuel Thibault wrote: Whit Blauvelt, le Wed 10 Aug 2011 12:19:36 -0400, a écrit : # /usr/sbin/debootstrap --arch=amd64 squeeze /mnt/deb /http://ftp.us.debian.org/debian There is a spurious '/' in front of http:// Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637363: debootstrap 1.0.35 fails to accept --arch=amd64 on CentOS 5.6 system
Just to verify my memory, I checked the history, and all test invocations indeed were: /usr/sbin/debootstrap --arch=amd64 squeeze /mnt/deb http://ftp.us.debian.org/debian (aside from also trying --arch amd64) Sorry again for the stray / in the report. Whit -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637363: debootstrap 1.0.35 fails to accept --arch=amd64 on CentOS 5.6 system
retitle 637363 should fallback to uname to determine current architecture thanks Whit Blauvelt, le Wed 10 Aug 2011 12:19:36 -0400, a écrit : # /usr/sbin/debootstrap --arch=amd64 squeeze /mnt/deb /http://ftp.us.debian.org/debian E: Couldn't work out current architecture Removing the = makes no difference. This is on an up-to-date CentOS 5.6 system: # uname -a Linux xxx.yyy.local 2.6.18-194.11.4.el5 #1 SMP Tue Sep 21 05:04:09 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux I suggest that debootstrap should accept the --arch specification rather than try to work out what it is by whatever method. --arch is the target architecture, not the current architecture. It needs the latter to know how to deal with some details. debootstrap should probably resort to uname in such case. It used to provide an arch file providing the info but not any more at since 2005... Actually all we seem to need nowadays is linux vs freebsd vs hurd, so `uname` should be enough. Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637363: debootstrap 1.0.35 fails to accept --arch=amd64 on CentOS 5.6 system
On Wed, Aug 10, 2011 at 08:34:12PM +0200, Samuel Thibault wrote: --arch is the target architecture, not the current architecture. It needs the latter to know how to deal with some details. debootstrap should probably resort to uname in such case. Note in the default case (if I understand correctly now) debootstrap assumes that the current architecture shown by dpkg is also the target architecture. Why not also assume the reverse - that if the target architecture is specified through --arch and the current architecture is not discovered, the current architecture should be assumed the same as the target? Also note target is an ambiguous term - the target in normal English is the existing object which receives the new thing (as when the target is a dartboard, and the new element introduced the dart), so the use of target architecture in the --help screen misleads a number of people besides me - as I see from Googling the error message. Thanks, Whit -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637363: ***SPAM*** Re: Bug#637363: debootstrap 1.0.35 fails to accept --arch=amd64 on CentOS 5.6 system
Whit Blauvelt, le Wed 10 Aug 2011 15:09:15 -0400, a écrit : On Wed, Aug 10, 2011 at 08:34:12PM +0200, Samuel Thibault wrote: --arch is the target architecture, not the current architecture. It needs the latter to know how to deal with some details. debootstrap should probably resort to uname in such case. Note in the default case (if I understand correctly now) debootstrap assumes that the current architecture shown by dpkg is also the target architecture. Why not also assume the reverse - that if the target architecture is specified through --arch and the current architecture is not discovered, the current architecture should be assumed the same as the target? There's no reason why we shouldn't just trust uname. Also note target is an ambiguous term - the target in normal English is the existing object which receives the new thing That is the meaning here: on which machine you will run the installed debian system. (as when the target is a dartboard, and the new element introduced the dart), so the use of target architecture in the --help screen misleads a number of people besides me - as I see from Googling the error message. It's probably simply that nobody up to now reported the issue to get it actually fixed... Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637363: ***SPAM*** Re: Bug#637363: debootstrap 1.0.35 fails to accept --arch=amd64 on CentOS 5.6 system
On Wed, Aug 10, 2011 at 09:13:31PM +0200, Samuel Thibault wrote: Also note target is an ambiguous term - the target in normal English is the existing object which receives the new thing That is the meaning here: on which machine you will run the installed debian system. Ah, but when debootstrap is being used to install Debian into a chroot then the meaning of target can be mistaken to mean the architecture hosting the chroot - the one which is running debootstrap in this case - rather than the architecture to be used by Debian within the chroot. That is, with a CentOS machine installing Debian to a chroot, the target architecture can be misunderstood to be the CentOS architecture, rather than the architecture of what you're throwing onto that target, which is Debian. Whit -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637363: ***SPAM*** Re: Bug#637363: debootstrap 1.0.35 fails to accept --arch=amd64 on CentOS 5.6 system
Whit Blauvelt, le Wed 10 Aug 2011 15:49:23 -0400, a écrit : On Wed, Aug 10, 2011 at 09:13:31PM +0200, Samuel Thibault wrote: Also note target is an ambiguous term - the target in normal English is the existing object which receives the new thing That is the meaning here: on which machine you will run the installed debian system. Ah, but when debootstrap is being used to install Debian into a chroot then the meaning of target can be mistaken to mean the architecture hosting the chroot - the one which is running debootstrap in this case - rather than the architecture to be used by Debian within the chroot. It can't be the target of debootstrap, since debootstrap is already running in it. Think of it (the host, Centos) as the hand which is holding the dart (debootstrap) to the target (the actual machine running the just-installed Debian, which may or may not be Centos). Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637363: ***SPAM*** Re: Bug#637363: debootstrap 1.0.35 fails to accept --arch=amd64 on CentOS 5.6 system
On Wed, Aug 10, 2011 at 09:52:36PM +0200, Samuel Thibault wrote: It can't be the target of debootstrap, since debootstrap is already running in it. Think of it (the host, Centos) as the hand which is holding the dart (debootstrap) to the target (the actual machine running the just-installed Debian, which may or may not be Centos). Once you've explained it, I understand your technical use of target to mean what you mean by it. I'm only suggesting it is ambiguous, so that other people may easily misunderstand it in the context of building in a chroot, where the target may be misinterpreted to mean the host of the chroot. Again, once you've clarified it, it's clear. But the term target, without the clarification, can confuse - as in I'm going to throw Debian into a chroot on this CentOS box. | CentOS | || Debian | | chroot | | || || Now, is the target named CentOS, or named chroot? That's the ambiguity. Googling the --arch error shows I'm not the only one to take the wrong fork in the road of intrepretation there. Best, Whit -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637363: ***SPAM*** Re: Bug#637363: debootstrap 1.0.35 fails to accept --arch=amd64 on CentOS 5.6 system
clone 637363 -1 retitle -1 explain what target means severity -1 wishlist thanks Whit Blauvelt, le Wed 10 Aug 2011 16:21:00 -0400, a écrit : On Wed, Aug 10, 2011 at 09:52:36PM +0200, Samuel Thibault wrote: It can't be the target of debootstrap, since debootstrap is already running in it. Think of it (the host, Centos) as the hand which is holding the dart (debootstrap) to the target (the actual machine running the just-installed Debian, which may or may not be Centos). Once you've explained it, I understand your technical use of target to mean what you mean by it. I'm only suggesting it is ambiguous, so that other people may easily misunderstand it in the context of building in a chroot, where the target may be misinterpreted to mean the host of the chroot. Again, once you've clarified it, it's clear. But the term target, without the clarification, can confuse - as in I'm going to throw Debian into a chroot on this CentOS box. Ok, then cloning the bug. Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
