Re: [DNG] debootstrap requires key
On Mon, 25 Apr 2016, Haines Brown wrote: > On Mon, Apr 25, 2016 at 05:47:15PM +0200, parazyd wrote: > > On Mon, 25 Apr 2016, Haines Brown wrote: > > > > Perhaps my problem was that I unpacked the devuan.debian.tar.gz archive > > > on the target /mnt/debinist/usr/share. If instead I run > > > > > > # dpkg -i debootstrap_1.0.75-1+devuan1_all.deb > > > > > > I fear it will overwrite the debootstrap on my current Wheezy Debian > > > system and break it. > > > > The debootstrap from devuan is safe to install. It differs only in > > having a few bugfixes. Besides, you can always grab the package from > > wheezy and overwrite. > > Again, please excuse my ignorance. You appear to say that I can use dpkg > to install the dpkg -i debootstrap_1.0.75-1+devuan1_all.deb on my > running Wheezy system, for it is essentially the same. But when I do > that and run: > > # debootstrap -no-check-gpg jessie /mnt/debinst/ \ > http://packages.devuan.org/merged > E: No such script: http://packages.devuan.org/merged > > > Anyway, sorry if there is too much 'tech talk'. Try looking at this > > forum thread: > > http://www.linuxquestions.org/questions/debian-26/how-to-install-debian-using-debootstrap-4175465295/ > > Yes, thanks. What confused me was that when I did cross installation in > years past, there were no stages to worry about. But the immediate > problem is that I can't even get started with the above command. > "-no-check-gpg" should be "--no-check-gpg" What if you do this? # debootstrap --no-check-gpg --foreign --arch [architecture] jessie \ /mnt/debinst http://packages.devuan.org/merged -- ~ parazyd 6CB4 6C63 641D B1F1 F811 5B3A BB5E 2E35 B92E 373E pgpGhUhylX_f8.pgp Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
On Mon, Apr 25, 2016 at 05:47:15PM +0200, parazyd wrote: > On Mon, 25 Apr 2016, Haines Brown wrote: > > Perhaps my problem was that I unpacked the devuan.debian.tar.gz archive > > on the target /mnt/debinist/usr/share. If instead I run > > > > # dpkg -i debootstrap_1.0.75-1+devuan1_all.deb > > > > I fear it will overwrite the debootstrap on my current Wheezy Debian > > system and break it. > > The debootstrap from devuan is safe to install. It differs only in > having a few bugfixes. Besides, you can always grab the package from > wheezy and overwrite. Again, please excuse my ignorance. You appear to say that I can use dpkg to install the dpkg -i debootstrap_1.0.75-1+devuan1_all.deb on my running Wheezy system, for it is essentially the same. But when I do that and run: # debootstrap -no-check-gpg jessie /mnt/debinst/ \ http://packages.devuan.org/merged E: No such script: http://packages.devuan.org/merged > Anyway, sorry if there is too much 'tech talk'. Try looking at this > forum thread: > http://www.linuxquestions.org/questions/debian-26/how-to-install-debian-using-debootstrap-4175465295/ Yes, thanks. What confused me was that when I did cross installation in years past, there were no stages to worry about. But the immediate problem is that I can't even get started with the above command. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
On Mon, 25 Apr 2016, Haines Brown wrote: > I apologize for being so slow, but problems abound. I decided to try the > devuan installation with the installer ISO on a key. I used the > devuan-jessie-i386-alpha4-netboot.iso. However, when it came time to > download installation components from the devuan archive, it failed: > "Bad archive mirror". > > The archive it tried was us.mirror.devuan.org. Shouldn't it be > us.mirror.devuan.org? When I used debootstrap to produce the broken base > system, it created a sources.list with the entry: deb > http://debootstrap.invalid/ jessie main. > > As for your script, I remain lost (I'm not a programmer, but a social > scientist). I don't know what the variable "device-name" refers > to. Perhaps to the /dev/sda1 to which I'm trying to install devuan. I > assume that second and third stage refer to phases in the installation > process, but I have no idea what they are. If you are simply suggesting > I rerun debootstrap several times, I actually did it at least twice, and > still get the message that seems to imply my libc version is wrong. > > Perhaps my problem was that I unpacked the devuan.debian.tar.gz archive > on the target /mnt/debinist/usr/share. If instead I run > > # dpkg -i debootstrap_1.0.75-1+devuan1_all.deb > > I fear it will overwrite the debootstrap on my current Wheezy Debian > system and break it. The debootstrap from devuan is safe to install. It differs only in having a few bugfixes. Besides, you can always grab the package from wheezy and overwrite. Anyway, sorry if there is too much 'tech talk'. Try looking at this forum thread: http://www.linuxquestions.org/questions/debian-26/how-to-install-debian-using-debootstrap-4175465295/ A debootstrap system install has three stages, which you must complete to get a working system. It's not running debootstrap multiple times, but more like running debootstrap's flow(?) Perhaps it helps more :) -- ~ parazyd 6CB4 6C63 641D B1F1 F811 5B3A BB5E 2E35 B92E 373E pgpUOa1zhUHOa.pgp Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
On Mon, Apr 25, 2016 at 12:55:45PM +0200, parazyd wrote: > On Mon, 25 Apr 2016, Haines Brown wrote: > > > It installed a base system on the target disk mounted on > > /mnt/debinst. But that base system is apparently broken because of a > > version inconsistency: > > > > W: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version 'GLIB_2.17' not > > found (required by /lib-i386-linux-gnu/libmount.so.1) > > > > If you are implying the version clash is because I used the debian > > rather than the devuan debootstrap, that is not the case. I need to > > correct this problem in order to chroot into the new system to configure > > and develop it. > > > > > Also, for next steps, I'd recommend you to see how the ARM SDK works, > > > particularly the devuan profile: > > > https://git.devuan.org/devuan/arm-sdk/blob/master/arm/profiles/common-devuan > > > > This is a program you wrote. Much appreciated, but I have no idea what > > it is for or how to use it. > > > > Once you do debootstrap once, you also need to do the second and the > third stage, respectively, to get a working system. > > This is why I linked to "common-devuan" because in there you can see > what you have to do. Go to the bottom, and look at the for-loop. These > are the complete steps on how to get a fully bootable system. I apologize for being so slow, but problems abound. I decided to try the devuan installation with the installer ISO on a key. I used the devuan-jessie-i386-alpha4-netboot.iso. However, when it came time to download installation components from the devuan archive, it failed: "Bad archive mirror". The archive it tried was us.mirror.devuan.org. Shouldn't it be us.mirror.devuan.org? When I used debootstrap to produce the broken base system, it created a sources.list with the entry: deb http://debootstrap.invalid/ jessie main. As for your script, I remain lost (I'm not a programmer, but a social scientist). I don't know what the variable "device-name" refers to. Perhaps to the /dev/sda1 to which I'm trying to install devuan. I assume that second and third stage refer to phases in the installation process, but I have no idea what they are. If you are simply suggesting I rerun debootstrap several times, I actually did it at least twice, and still get the message that seems to imply my libc version is wrong. Perhaps my problem was that I unpacked the devuan.debian.tar.gz archive on the target /mnt/debinist/usr/share. If instead I run # dpkg -i debootstrap_1.0.75-1+devuan1_all.deb I fear it will overwrite the debootstrap on my current Wheezy Debian system and break it. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
On Mon, 25 Apr 2016, Haines Brown wrote: > On Sun, Apr 24, 2016 at 09:37:24PM +0200, parazyd wrote: > > > Yes, debootstrap works on any system. Note that if you wish to bootstrap > > devuan systems, use devuan's debootstrap (which was fixed): > > https://packages.devuan.org/devuan/pool/main/d/debootstrap/ > > Yes, I unarchived debootstrap_1.0.75-1+devuan1.debian.tar.gz in the > target disk (/mnt/debinst/usr/share) and ran: > > # debootstrap --no-check-gpg jessie /mnt/debinst \ > http://packages.devuan.org/merged > > It installed a base system on the target disk mounted on > /mnt/debinst. But that base system is apparently broken because of a > version inconsistency: > > W: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version 'GLIB_2.17' not > found (required by /lib-i386-linux-gnu/libmount.so.1) > > If you are implying the version clash is because I used the debian > rather than the devuan debootstrap, that is not the case. I need to > correct this problem in order to chroot into the new system to configure > and develop it. > > > Also, for next steps, I'd recommend you to see how the ARM SDK works, > > particularly the devuan profile: > > https://git.devuan.org/devuan/arm-sdk/blob/master/arm/profiles/common-devuan > > This is a program you wrote. Much appreciated, but I have no idea what > it is for or how to use it. > Once you do debootstrap once, you also need to do the second and the third stage, respectively, to get a working system. This is why I linked to "common-devuan" because in there you can see what you have to do. Go to the bottom, and look at the for-loop. These are the complete steps on how to get a fully bootable system. -- ~ parazyd 6CB4 6C63 641D B1F1 F811 5B3A BB5E 2E35 B92E 373E pgp7oa4x9i2K2.pgp Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
On Sun, Apr 24, 2016 at 09:37:24PM +0200, parazyd wrote: > Yes, debootstrap works on any system. Note that if you wish to bootstrap > devuan systems, use devuan's debootstrap (which was fixed): > https://packages.devuan.org/devuan/pool/main/d/debootstrap/ Yes, I unarchived debootstrap_1.0.75-1+devuan1.debian.tar.gz in the target disk (/mnt/debinst/usr/share) and ran: # debootstrap --no-check-gpg jessie /mnt/debinst \ http://packages.devuan.org/merged It installed a base system on the target disk mounted on /mnt/debinst. But that base system is apparently broken because of a version inconsistency: W: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version 'GLIB_2.17' not found (required by /lib-i386-linux-gnu/libmount.so.1) If you are implying the version clash is because I used the debian rather than the devuan debootstrap, that is not the case. I need to correct this problem in order to chroot into the new system to configure and develop it. > Also, for next steps, I'd recommend you to see how the ARM SDK works, > particularly the devuan profile: > https://git.devuan.org/devuan/arm-sdk/blob/master/arm/profiles/common-devuan This is a program you wrote. Much appreciated, but I have no idea what it is for or how to use it. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
On Sun, 24 Apr 2016, Haines Brown wrote: > On Sun, Apr 24, 2016 at 03:41:51PM +0100, dev1fanboy wrote: > > > When you say installed debootstrap on a new disk, you mean the host > > OS? What architecture is the host and the 'target' disk, are they > > different? > > Sorry I was not clearer. I meant debootstrap installed a base system on > a new disk. > ># debootstrap --no-check-gpg jessie /mnt/debinst \ > https://packages.devuan.org/devuan > > The host, my currently running machine, runs debootstrap, targetting a > new partitioned disk mounted on /mnt/debinst. I'm assuming debootstrap > can be run anywhere, and it installs a base system wherever it is told > to do it. Years ago I did cross installations, but the process has > gotten a lot more complicated. Yes, debootstrap works on any system. Note that if you wish to bootstrap devuan systems, use devuan's debootstrap (which was fixed): https://packages.devuan.org/devuan/pool/main/d/debootstrap/ Also, for next steps, I'd recommend you to see how the ARM SDK works, particularly the devuan profile: https://git.devuan.org/devuan/arm-sdk/blob/master/arm/profiles/common-devuan -- ~ parazyd 6CB4 6C63 641D B1F1 F811 5B3A BB5E 2E35 B92E 373E pgpevJeYAmW3y.pgp Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
On Sun, Apr 24, 2016 at 03:41:51PM +0100, dev1fanboy wrote: > When you say installed debootstrap on a new disk, you mean the host > OS? What architecture is the host and the 'target' disk, are they > different? Sorry I was not clearer. I meant debootstrap installed a base system on a new disk. # debootstrap --no-check-gpg jessie /mnt/debinst \ https://packages.devuan.org/devuan The host, my currently running machine, runs debootstrap, targetting a new partitioned disk mounted on /mnt/debinst. I'm assuming debootstrap can be run anywhere, and it installs a base system wherever it is told to do it. Years ago I did cross installations, but the process has gotten a lot more complicated. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
When you say installed debootstrap on a new disk, you mean the host OS? What architecture is the host and the 'target' disk, are they different? Cheers, chillfan On Saturday, April 23, 2016 9:04 PM, Haines Brown wrote: > On Sat, Apr 23, 2016 at 05:46:10PM +0100, dev1fanboy wrote: > >> If I remember right... You can parse the option --no-check-gpg to >> debootstrap, and you might need to use >> --exclude=devuan-keyring,gpgv,gnupg as well and just install >> devuan-keyring after the debootstrap to make sure you are using the >> gpg key for the install. >> >> Cheers, >> >> chillfan >> >> On Saturday, April 23, 2016 1:13 PM, Haines Brown >> wrote: > >> > This has come up before, but I still don't know the basic >> > procedure. I've installed debootstrap on a new disk and run: >> > >> > # debootstrap --arch amd64 jessie /mnt/debinst \ >> > https://packages.devuan.org/devuan > > Besides correcting my typo (removing --arch amd option), and adding the > --no-check-gpg option, debootstrap ran better. That is, a bunch of files > were validated and extracted. > > But at the end this appeared: > > W: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version 'GLIB_2.17' not > found (required by /lib-i3896-linux-gnu/libmount.so.1) > > And when I try > > # chroot /mnt/debinst > /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version > `GLIBC_2.15' not found (required by /bin/bash) > > I gather glibc is provided by libc. This looks like some kind of version > incompatibility. Hoever, While in target drive archive is > libc6_2.19-18+deb8u4_i386.deb, there's no libc* in target /lib. So > rather than version problem, it may be that libc was not installed > for some reason. If I simply do # dpkg -i libc_6.19-18+deb8u4_i386.deb > will it install on the target drive rather than messing up my current > Wheezy library? > > Haines Brown > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Take back your privacy. Switch to www.StartMail.com ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
On Sat, Apr 23, 2016 at 05:46:10PM +0100, dev1fanboy wrote: > If I remember right... You can parse the option --no-check-gpg to > debootstrap, and you might need to use > --exclude=devuan-keyring,gpgv,gnupg as well and just install > devuan-keyring after the debootstrap to make sure you are using the > gpg key for the install. > > Cheers, > > chillfan > > On Saturday, April 23, 2016 1:13 PM, Haines Brown > wrote: > > This has come up before, but I still don't know the basic > > procedure. I've installed debootstrap on a new disk and run: > > > > # debootstrap --arch amd64 jessie /mnt/debinst \ > > https://packages.devuan.org/devuan Besides correcting my typo (removing --arch amd option), and adding the --no-check-gpg option, debootstrap ran better. That is, a bunch of files were validated and extracted. But at the end this appeared: W: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version 'GLIB_2.17' not found (required by /lib-i3896-linux-gnu/libmount.so.1) And when I try # chroot /mnt/debinst /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /bin/bash) I gather glibc is provided by libc. This looks like some kind of version incompatibility. Hoever, While in target drive archive is libc6_2.19-18+deb8u4_i386.deb, there's no libc* in target /lib. So rather than version problem, it may be that libc was not installed for some reason. If I simply do # dpkg -i libc_6.19-18+deb8u4_i386.deb will it install on the target drive rather than messing up my current Wheezy library? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
If I remember right... You can parse the option --no-check-gpg to debootstrap, and you might need to use --exclude=devuan-keyring,gpgv,gnupg as well and just install devuan-keyring after the debootstrap to make sure you are using the gpg key for the install. Cheers, chillfan On Saturday, April 23, 2016 1:13 PM, Haines Brown wrote: > This has come up before, but I still don't know the basic > procedure. I've installed debootstrap on a new disk and run: > > # debootstrap --arch amd64 jessie /mnt/debinst \ > https://packages.devuan.org/devuan > > I: Retrieving Release > I: Retrieving Release.gpg > I: Checking Release signature > E: Release signed by unknown key (key id 94532124541922FB) > > No change when I downloaded and ran > > # dpkg -i devuan-keyring_2015.05.05_all.deb > > Do I have the right keyring? Was the alpha4 release date > c. 2015.05.05? > > In simple step by step terms, what do I do? > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Take back your privacy. Switch to www.StartMail.com ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
On Sat, 23 Apr 2016, Haines Brown wrote: > This has come up before, but I still don't know the basic > procedure. I've installed debootstrap on a new disk and run: > > # debootstrap --arch amd64 jessie /mnt/debinst \ > https://packages.devuan.org/devuan > > I: Retrieving Release > I: Retrieving Release.gpg > I: Checking Release signature > E: Release signed by unknown key (key id 94532124541922FB) > > No change when I downloaded and ran > > # dpkg -i devuan-keyring_2015.05.05_all.deb > > Do I have the right keyring? Was the alpha4 release date > c. 2015.05.05? > > In simple step by step terms, what do I do? > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng Maybe try signing the key locally: # gpg --lsign-key 94532124541922FB and/or add it to apt by doing: # gpg --export -a 94532124541922FB | apt-key add - -- ~ parazyd 6CB4 6C63 641D B1F1 F811 5B3A BB5E 2E35 B92E 373E pgpxctDTl1Eof.pgp Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] debootstrap requires key
This has come up before, but I still don't know the basic procedure. I've installed debootstrap on a new disk and run: # debootstrap --arch amd64 jessie /mnt/debinst \ https://packages.devuan.org/devuan I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature E: Release signed by unknown key (key id 94532124541922FB) No change when I downloaded and ran # dpkg -i devuan-keyring_2015.05.05_all.deb Do I have the right keyring? Was the alpha4 release date c. 2015.05.05? In simple step by step terms, what do I do? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
