:: Re: [DNG] debootstrap requires key
トップ ページ
このメッセージを削除
このメッセージに返信
著者: Haines Brown
日付:  
To: 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
> <haines@???> 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