Re: Debootstrapping Debian-testing from http://ftp.fr.debian.org/debian/ and http://ftp.de.debian.org/debian/ fails -"faulty" package ifupdown_0.8.6_amd64.deb, no more file retrieval with apt-get install from inside chroot after base package retrieval
On 1/12/16, sbeck@secure.mailbox.org <sbeck@secure.mailbox.org> wrote:
> Hi Debian-testing members,
>
> (I'm not subscribed to the list, so please CC me. Thanks)
>
> I have encountered some problems while debootstrapping a Debian-testing
> installation into a chroot environment. First I debootstrapped first
> retrieving the files from (1) and then once again from (2), but with the
> same results. I did a check using lintian to learn more about the possibly
> "faulty" package. On the other hand, I could not retrieve any more files
> after the first debootstrap base package retrieval session. Is it worth
> filing a bug report?
> My system: debian-oldstable 32 bits (7.9.) on a 64 bit kernel (4.2.6).
> debootstrap version 1.0.48+deb7u4
>
>
> (1)# debootstrap --arch amd64 stretch /mnt/chroot/stretch_64
> http://ftp.fr.debian.org/debian/
> (2)# debootstrap --arch amd64 stretch /mnt/chroot/stretch_64
> http://ftp.de.debian.org/debian/
>
>
> (Shell output)
> (...)
> W: Failure while installing base packages. This will be re-attempted up
> to five times.
> W: See /mnt/chroot/stretch_64/debootstrap/debootstrap.log for details
> (possibly the package archive is at fault)
> W: Failure while installing base packages. This will be re-attempted up
> to five times.
> W: See /mnt/chroot/stretch_64/debootstrap/debootstrap.log for details
> (possibly the package archive is at fault)
> W: Failure while installing base packages. This will be re-attempted up
> to five times.
> W: See /mnt/chroot/stretch_64/debootstrap/debootstrap.log for details
> (possibly the package archive is at fault)
> W: Failure while installing base packages. This will be re-attempted up
> to five times.
> W: See /mnt/chroot/stretch_64/debootstrap/debootstrap.log for details
> (possibly the package archive is at fault)
> W: Failure while installing base packages. This will be re-attempted up
> to five times.
> W: See /mnt/chroot/stretch_64/debootstrap/debootstrap.log for details
> (possibly the package archive is at fault)
>
> debootstrap.log
> Errors were encountered while processing:
> /var/cache/apt/archives/ifupdown_0.8.6_amd64.deb (5 times)
>
> Debootstrap error message --> checking with lintian
> # lintian --check --verbose --show-overrides
> /mnt/chroot/stretch_64/var/cache/apt/archives/ifupdown_0.8.6_amd64.deb
>
> N: Using profile debian/main.
> N: Setting up lab in /tmp/temp-lintian-lab-8osJjdfKfW ...
> N: ----
> N: Processing binary package ifupdown (version 0.8.6, arch amd64) ...
> O: ifupdown: init.d-script-possible-missing-stop etc/init.d/networking 1
> ----------------------------------------------
> after accessing chroot environment for retrieving additional files (here:
> ssh)
>
< temporarily snipped for brevity >
>
> E: Failed to fetch
> http://debootstrap.invalid/pool/main/x/xauth/xauth_1.0.9-1_amd64.deb
> Could not resolve 'debootstrap.invalid'
>
> E: Unable to fetch some archives, maybe run apt-get update or try with
> --fix-missing?
>
> CHROOT-me@mymachine:/# apt-get install --fix-missing
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> I have the entire debootstrap log, if it is necessary. Here I just
> extracted the most important information.
>
> What can I do to install more packages? Should I file a bug report?
Hi, Stephan.. I just happened to have been in a debootstrap frame of
mind myself today. I'm used to it working with very little trouble so
all I can do is pretend I'm wearing your Shoes right now. I looked at
things like where your command ends ../debian/ and mine is ../debian.
That didn't make any difference, and I've since also seen that
trailing "/" in the online Wiki documentation.
I'm curious about where it seems to be pulling
http://debootstrap.invalid/pool/main/ out of its hat. That's the first
I've ever seen that. The "invalid" part is familiar as something
referenced within the debootstrap copy's hierarchy of
/var/lib/apt/lists. AND of course I just looked and can't find an
example in mine to share... as example. But I HAVE seen the word
"invalid" in there.. :)
Can you look in your copy's /var/lib/apt/lists, and see 1) how many
files are in there and 2) if any reference the word "invalid"?
THIS IS *NOT* a recommended method BUT... One of the things I have to
do with mine occasionally is go into that lists directory (*IN
DEBOOSTRAP'S COPY!*) and delete the two or three smaller files I find
in there. The ones I target for deletion are the ones that are under
~300kb in size.
It's just something I learned by trial and error via dialup access.
Those smaller files I delete occasionally are the "invalid" named
files. The reasons I run into for having to delete those smaller files
mostly involve errors regarding valid versus invalid release
signatures at the beginning of the debootstrap process...
My apologies that I don't have any more than that to offer. I LOVE
DEBOOTSTRAP, and my sessions go well.. If you're working on it in a
couple hours, I'll be back inside after finishing up some outside
evening chores. I'll be happy to take a deeper poke at the problem
then if no one else has any answers that work.
Also, you might try over at the Debian-User list. Fair warning is that
there's still not too many who go the deboostrap route (in case you
don't receive much response). I'm actually personally trying to change
that because it's a phenomenal accessibility/usability related Debian
installation tool for poverty level computer users.. :)
Cindy :)
--
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* #RIP, Ian. Thank you and to all who contribute to Debian. It's a
Life-affecting, Life-enhancing resource and tool in my usage case. *
Reply to: