[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#846622: marked as done (debootstrap: refers to log that is already deleted)

Your message dated Mon, 25 Jun 2018 16:55:19 +0545
with message-id <d1632d743a7bff63053e99b2ff68f8811bfa909e.camel@debian.org>
and subject line Re: Bug#846622: debootstrap: refers to log that is already deleted
has caused the Debian Bug report #846622,
regarding debootstrap: refers to log that is already deleted
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

846622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846622
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.87
Severity: important

Here's a case. debootstrap operation has failed. Now debootstrap
mentions to look at the logs to determine the cause of the failure. But
this log file is inside the chroot. The same chroot that debootstrap
removes as part of cleanup, because of the failure.

So even before the user could act of the message, it is already deleted.
debootstrap should put the log in an absolute path on the Host OS.

I: Unpacking libblkid1:mips...
I: Unpacking libfdisk1:mips...
I: Unpacking libmount1:mips...
I: Unpacking libsmartcols1:mips...
I: Unpacking libuuid1:mips...
I: Unpacking mount...
I: Unpacking util-linux...
I: Unpacking liblzma5:mips...
I: Unpacking zlib1g:mips...
W: Failure while unpacking required packages.  This will be attempted up
to five times.
W: See //debootstrap/debootstrap.log for details (possibly the package
/var/cache/apt/archives/debconf_1.5.59_all.deb is at fault)

I: Unpacking libacl1:mips...
I: Unpacking libattr1:mips...
I: Unpacking libaudit-common...
I: Unpacking libaudit1:mips...
I: Unpacking base-files...
I: Unpacking base-passwd...
I: Unpacking bash...
I: Unpacking libbz2-1.0:mips...
I: Unpacking libdebconfclient0:mips...
I: Unpacking coreutils...
I: Unpacking dash...
I: Unpacking libdb5.3:mips...
I: U

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (990, 'testing-debug'), (990, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.11+ (SMP w/4 CPU cores)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debootstrap depends on:
ii  wget  1.18-4

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2014.3
ii  gnupg                   2.1.16-2

debootstrap suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi Hideki,

On Mon, 2018-06-25 at 19:36 +0900, Hideki Yamane wrote:
> Hi,
>  Unfortunately, there's not enough information to reproduce and
> investigate
>  this bug. So, if you cannot provide additional info, I'll close it.

I don't have the necessary information now. I think the problem was
that when the debootstrap process failed (like say a 404 HTTP error for
any one of the packages), it would later bail out. The logs used to get
stored under the chroot target path, but as part of the clean-up, the
target path used to get wiped.

But there's a comment from Cyril about --keep-debootstrap-dir option.
Maybe I didn't pay close attention to the options back then.

And I can't reproduce it right now. So let's close this for now. If
this is really a common bug, it'll show up again.


Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

Attachment: signature.asc
Description: This is a digitally signed message part

--- End Message ---

Reply to: